OWNA Virtual Assistant: a VA who runs the CCS grind so your director stays on the floor

Nobody searches “owna virtual assistant” because things are going well. You search it the week three session reports bounce, a family’s subsidy stops because their enrolment slipped back to pending, and your director, who is meant to be leading the preschool room, spends Tuesday in the office fixing attendance data instead. In most Australian services the person running OWNA’s admin side is the director or the owner, and every hour they spend in the back office is an hour the service pays for twice: once in wages, once in whatever they were supposed to be doing.

OWNA calls itself Australia’s number one all-in-one CCMS, and since October 2025 the claim has teeth: it acquired Juice Technologies, which folded Kidsoft, Kindyhub, Kangarootime AU, Smart Central and Infocare NZ into the same group. If your service runs on any of those, you are in OWNA’s world now. The software is genuinely all-in-one, which is exactly the problem. When one platform holds enrolments, CCS, billing, the waitlist, incident records and the parent app, one platform generates all the admin, and someone has to sit in it every day.

The daily rhythm a VA runs in your OWNA

Morning, before the phones warm up: attendances. Yesterday’s sign-in and sign-out data gets reconciled against booked sessions, and the gaps get fixed. A parent who forgot to sign out at pickup is not a small thing in a CCMS; it is a session report that will not match, which is subsidy that will not pay. Your VA chases the missing sign-outs with the room leaders, corrects the records, then submits the session reports to CCS through OWNA.

Then the rejections. Anyone who has run a service knows session reports do not all sail through. Enrolment date mismatches, a session reported outside the enrolment period, a CRN that Centrelink disagrees with by one digit. Each rejection is a small investigation: find the cause, fix the underlying record, resubmit. Left for Friday, these compound into a subsidy shortfall and a very awkward conversation with a family about a gap fee that tripled. Worked daily, they are ten quiet minutes.

Enrolments run alongside. New families come through OWNA’s digital enrolment forms, and your VA checks the details that actually break things: the CRN and date of birth exactly as Centrelink holds them, the immunisation history statement attached, the start date inside the enrolment period. The Complying Written Arrangement gets generated and chased for signature, and here is the step services lose money on constantly: the family still has to confirm the enrolment in their own myGov. Enrolments sitting in PENDING CONFIRMATION do not attract subsidy, so your VA keeps a list and nudges those families until every one flips to confirmed.

Money has its own cadence. The billing run goes out on schedule, gap fees collect through OWNA’s integrated direct debit, and the dishonours, because there are always dishonours, get followed up the day they bounce rather than when someone notices the ledger. Family statements go out, and aged fee debt gets worked on a chasing cadence you approved in writing, so the tone is yours even when the follow-up is not. Weekly, the CCS payment advice gets reconciled against what actually arrived, because entitlement percentages change, activity test results change, and the difference between estimated and actual subsidy is exactly the kind of slow leak that only shows up at BAS time if nobody is watching.

The waitlist rounds it out. Every enquiry entered into OWNA’s waitlist module with age and preferred days, tours booked and confirmed, and when a Wednesday spot opens in the toddler room, the list gets filtered by age group and the offers go out that day. A waitlist worked weekly is occupancy; a waitlist nobody opens is a spreadsheet of people who enrolled somewhere else. And through all of it, the parent app hums along: absence messages logged, reminders scheduled, the newsletter actually sent, with anything sensitive escalated to you under a written rule rather than answered by guesswork.

The honest bit

Three things worth saying plainly.

First, OWNA transmits session reports; it does not fix them. The CCS side of the government system has its own moods, and a rejected report is a person’s job, not a feature’s. Buying the software solved the transmission problem. The reconciliation, the chasing, the resubmission: that was always going to be someone’s hours, and right now the someone is probably your director.

Second, the acquisition cuts both ways. Being part of one of the biggest childcare software groups in the country is good for OWNA’s longevity, but if you came in through Kidsoft, Kindyhub or Kangarootime AU, you may be looking at a platform migration at some point, and migrations are admin-heavy: enrolment data checked record by record, direct debit details re-confirmed, families re-onboarded to a new app. A VA who owns your admin is the difference between a migration project and a migration crisis.

Third, and this one is almost funny: OWNA itself sells an accounts admin service to its own customers. Read that as proof, not competition. The vendor looked at its user base and concluded that owners are drowning in exactly this work and will pay to hand it off. The difference with a placed VA is scope and loyalty: one person who does the whole admin surface, session reports to waitlist to parent app, works your hours, learns your families’ names, and works for you rather than for the software company.

What stays with you

Childcare is a regulated industry and the line needs to be drawn in ink, not implied.

Your VA does operational admin only. Everything that belongs to the approved provider or the responsible person stays exactly where the National Law puts it: serious incident notifications to your state regulatory authority (the VA can have the incident record complete in OWNA within the hour, but the decision to notify, and the notification itself, are yours), ACCS child wellbeing certificates, anything touching a child protection concern, staffing and ratio decisions, fee setting, and enrolment refusals. Anything a parent raises through the app that sounds like a complaint, a custody issue or a safety concern escalates to you immediately under a written rule, no judgement calls made on your behalf.

The permission model backs the policy. OWNA’s role-based logins mean the VA’s profile is an office admin one: enrolments, CCS, billing, waitlist, yes; educator programming, observations and children’s daily journals, no. It is a boundary the software enforces, not one you have to remember to police.

What it costs and where to start

OWNA admin sits on DotVA’s admin tier at $12-17 AUD an hour excl GST, and a single service typically lands at 10-15 hours a week, roughly $500-1,100 a month. That usually covers the daily attendance and session report run, the enrolment pipeline, the billing cycle and the waitlist, which is most of what keeps a director trapped in the office.

Placement takes 7-10 business days, and the first 5-7 days are supervised inside your OWNA before any solo work, starting with attendances and session reports because that is where errors cost real money. A $500 refundable deposit credits against your first month, there is a 30-day recalibrate-or-replace guarantee, and no lock-in beyond 14 days notice, which matters in a sector where occupancy can move under you.

If you want the wider picture for your sector, the childcare and early learning page covers the industry beyond the software, the invoice chasing page goes deeper on the fee debt side, and the VA cost guide lays out the full pricing model. Otherwise book a discovery call with Jenn, and bring your session report rejection count from last month. It is usually the fastest way to see the business case.