Billing & payroll
From delivered shift to banked claim, nothing re-keyed.
Every re-key between systems is an error waiting for an audit. In Corella the shift you rostered is the timesheet you approved, the line you invoiced, the row in the NDIA claim file and the hours in the payroll export — one chain, one system.
How it flows
Five funding lanes, two claim paths, one source of truth — and payment closes its own loop.
A price book that knows the caps
Services carry per-time-band rates, and each band owns its NDIS item number and price cap, seeded so you are not keying rates in by hand. Client-specific overrides are explicit and visible. Service agreements allocate budgets by support category, with utilisation bars that show you funds moving before they run out.
Quote the work, then turn it into the agreement
Work usually starts with a price, not an invoice. Quotes are numbered, carry the NDIS item number on every line and a description that shows the recurrence a funder actually reads, and they require an expiry date — because a quote with no expiry is a price promise nobody agreed to hold. When one is accepted it converts into the funded service agreement and keeps the link back to the quote it came from, so there is a trail from the offer to the commitment. Line totals are stored rather than recalculated, so a quote you sent in June still shows June's numbers after the price book moves on 1 July.
Invoice runs by funding lane
Runs group delivered, approved shifts per client and funding type — NDIA-managed, plan-managed, self-managed, Support at Home, private — with bill-to routing to plan managers, printable tax invoices with your bank details, partial payments, and voids that release shifts back for rebilling.
Aged by who actually owes you, not by who you support
Thirty, sixty and ninety days, with a CSV — and aged by debtor rather than by participant, which sounds like a detail until you try to chase it. The person you support is often not the party that owes you money, so the report separates four kinds: the payer, the plan manager, a named bill-to, and the participant themselves. Age runs from the due date; an invoice that never had one is aged from its issue date plus your terms and labelled as inferred, on screen and in the export, rather than quietly assumed. And outstanding is the total minus what has actually been paid — so an invoice somebody marked PAID after a short payment still appears, which is exactly the one you would otherwise never find.
A price rise you have to look at before it happens
When the NDIA publishes a new schedule, updating your price book is the moment a year of billing can quietly go wrong. So it is deliberately not one click. The screen opens with an audit nobody asks for: lines over the cap and under it, a stored limit that is stale because it is checking last year’s ceiling, items that are unknown or legacy, participant overrides sitting above the cap, and — the one that matters — invoice lines you have already billed above it, separated into merely invoiced and actually claimed, because a line that has gone out in an NDIA claim file needs a correction rather than a price edit. Nothing is pre-ticked. The plan is computed and shown before anything is written, the same code answers “is this over cap” for both the audit and the change so the two cannot disagree, and applying it is recorded in the audit log.
NDIA bulk claims in the exact template
One export produces the 16-column bulk payment request CSV exactly as the portal expects — GST codes, claim types for cancellations, travel and reports, and even the filename constraint handled. Download, upload, done.
Xero connected, payroll exported
The Xero connector pushes invoices with the proof-of-support PDF attached and marks them paid when Xero's payment webhook fires — per-organisation OAuth, no shared credentials. Payroll runs on clearly-labelled simplified bands — weekend and public-holiday multiples, sleepovers, kilometres, travel time — and exports the CSV your payroll software imports.
Plan management and support coordination, first-class
Plan managers get an invoice inbox, provider records, claims with an ABA bank file for payment runs, and participant statements. Support coordinators get billable case notes that become claims, and coordination reports — the same claim engine, pointed at their lane.
Fair questions
Asked about this, often.
Does Corella claim directly through PRODA?
Does it replace our payroll software?
What does the Xero connector actually do?
Can one client have multiple funding types?
See your organisation in Corella.
A 30-minute walkthrough with the people who built it — your workflows, your terminology, not a canned demo.