The short version
- The five-system stack — rostering app, shared drive, accounting, HR tool, spreadsheets — is never chosen on purpose; it accretes, and so does its cost.
- The real cost isn't the subscriptions. It's the double entry between systems, the reconciliation to make them agree, the errors that surface late, and the hours spent tending the seams.
- Every one of those costs lives in a seam between two systems — remove the seams and you remove the cost.
- One client record, the proof-of-support-to-invoice chain, billing that flows to the NDIA file and Xero, and a per-tenant instance you own turn a stack of tools into one system.
01
The stack nobody chose on purpose
Almost no provider sat down and decided to run five systems. It accreted. You started with a rostering app because shifts had to be covered. Client files went on a shared drive because they had to live somewhere. An accounting package came in for the books, a separate HR tool for staff, and a handful of spreadsheets grew up in the gaps to make the others line up. Each decision was sensible on its own.
The result is a stack held together by re-typing and goodwill. And because no one ever chose it, no one owns its total cost — which is exactly why that cost is so easy to underestimate.
02
Cost one: double entry
The most visible cost is entering the same fact more than once. A new client is created in the rostering app, then again on the shared drive as a folder, then again in accounting as a payer. A delivered shift is recorded in the roster, then re-keyed into a claim spreadsheet. Hours travel from the rostering app, into a spreadsheet, into payroll.
Every hop is someone’s time, and every hop is a chance to drop a digit, transpose a date or miss a line. Double entry doesn’t only cost the minutes to type it twice — it costs the time spent later finding the one place it went in wrong.
03
Cost two: reconciliation, and no single source of truth
When the same information lives in several systems, they drift apart — and then someone has to make them agree. Which client list is current? Why does the roster show a service the plan doesn’t? Why don’t the invoiced hours match the rostered ones?
Answering those questions is reconciliation, and it’s pure overhead — hours spent making systems consistent instead of doing the work the systems are supposed to support. The root cause is simple: there’s no single record of a client that everything else refers to, so each system keeps its own slightly different version of the truth.
04
Cost three: the errors you don't see until later
Some costs stay hidden until the worst possible moment:
- A price that drifted above the cap, caught by the claims portal at month-end.
- A claim that can’t be substantiated because the proof of support is in another system, or nobody’s.
- A staff check that lapsed because the reminder lived in a spreadsheet no one opened.
- A payroll line that didn’t match the shift that was actually worked.
None of these feel like costs day to day. They surface at month-end, at payroll, or at audit — when they’re most expensive to fix and least convenient to discover.
05
Cost four: the admin hours, and the fragility
Then there’s the maintenance. Integrations between tools break or change format. An export that worked last quarter quietly starts dropping a column. The spreadsheet that holds it all together encodes logic only one person understands — and when they’re on leave or they resign, it walks out with them.
On top of that, your data is scattered across several vendors, in formats and on terms you don’t control. Getting a straight answer to “show me everything about this client” means visiting four systems and hoping they agree.
06
One system you own
The alternative isn’t a bigger tool — it’s fewer seams. When rostering, care records, documents and billing share one system, the costs above don’t get optimised; they disappear, because the gaps they lived in are gone:
- One client record everything refers to, role-scoped so the office sees all of it and field staff see the need-to-know — no more reconciling four versions of the same person.
- The proof-of-support to invoice chain — an approved shift form becomes the evidence and releases the shift for billing in a single step, so a whole re-keying job simply isn’t there.
- Billing that flows from delivery — the NDIA bulk claim file comes straight from delivered shifts, and the Xero connector pushes invoices and their attachments across, so the money side isn’t a second round of data entry.
- A system you actually own — a per-tenant isolated instance and database on Australian soil, a copy of everything yours to take whenever you want it, rather than spread across vendors on their terms.
If you are weighing up products to replace the stack, our guide to what “care management software” actually covers in Australia is the checklist of six things that one system has to do.
There’s a pricing version of the same point. Instead of a stack of subscriptions you can’t easily total, plus the invisible admin cost of holding them together, it’s one predictable line — $19 per staff user per month, everything included, with no safety features held behind a higher tier and no charge for participant or family portal logins.
Consolidating is real work up front, and we help with migration: what to export and in what order, how it comes into Corella — your client list through its spreadsheet import, every row shown before it’s added — and checking what has come across with you. Do that once, and the juggle you pay for every single week is behind you.
Where this lives in Corella
