For NDIS providers
NDIS software, without the spreadsheet safety net.
Corella is NDIS software for providers who would rather deliver supports than chase paperwork: rostering, participant records, claiming and the registers the NDIS Commission expects, in one system you own. It carries the Scheme's specifics natively — item numbers and caps in the price book, funding lanes in the invoice run, claim files in the portal's own template.


Here, the people you support are participants and your team are support workers.
Participant and support worker in the menus, headings and reports — one setting, with every web address kept as it is.
How your words workWhat's in it
The Scheme, handled natively
- Price book by time band — each band carries its own NDIS item number, checked against the 2026-27 NDIS price limits
- Budgets by support category, with spend measured against the funding released so far
- NDIA bulk payment requests in the exact 16-column CSV
- The NDIA's outcome file read back: paid, part-paid or rejected, line by line
- Nine SCHADS-style award checks on the draft roster, each breach flagged while the week can still change
- Plan-managed and self-managed invoices from the same delivery record
- Cancellations coded properly, short-notice billable included
- Reportable incidents with a 24-hour flag and a five-business-day countdown
- Restrictive practices register with a monthly CSV of recorded uses
- Travel time and kilometres recorded on the shift and paid — and billed to the funder too, once you switch that on
Claiming
What you claimed — and what you actually got paid.
Corella reads the NDIA's answer back, line by line — paid, part-paid or rejected, with the reason the file gives — so a rejected line is found and claimed again instead of lost in a spreadsheet.

1 · Export
The bulk payment file
48 lines in the NDIA’s 16-column template, from your issued invoice lines. You upload it in the provider portal.
2 · Bring back
What the NDIA actually paid
Upload the outcome file and every line is recorded as paid, part-paid or rejected — with the NDIA’s own reason.
45 paid · 2 part-paid · 1 rejected
3 · Re-claim
Just the line that bounced
Release the rejected line under a fresh reference once it’s fixed — instead of rebuilding the whole batch.
Watch it
See it in 65 seconds.
How it works
The detail, on the real screens.
Claims that match the portal, column for column
Choose the dates the supports were delivered and Corella gathers every unclaimed line with an NDIS item number from issued invoices for agency-managed participants into the bulk payment request, exactly as the myplace portal expects — 16 columns, GST codes, claim types, a compliant file name. A draft invoice, a waived line and a line charged at $0 stay out. Before the batch builds, Corella checks your NDIS registration number is in Settings, every participant's NDIS number is in the NDIA's format and every support item is in the Pricing Schedule for the day it was delivered — and names each one that needs fixing. Each line claims what you actually charged per unit, on the day the support was delivered — a short-notice cancellation as a cancellation with its NDIS reason code, transport as travel — and its claim reference is made once, so downloading the file again gives the same references. You upload it in the provider portal, and what used to be an afternoon of VLOOKUP is a download.

What you got paid, not just what you claimed
When the NDIA's outcome file comes back, you upload it and Corella records, per claim line, what was actually paid — paid, part-paid or rejected, with the NDIA's own rejection reason. Then you release just the rejected lines to re-claim under a fresh reference, instead of rebuilding the whole batch.

Budgets you can defend at review time
An NDIS plan's money is released in funding periods, and Corella measures spend against what has been released, not the plan total. Record each period's dates and released amount on the participant's service agreement, and the Funding tab says how much of the released money is still available, which period you're in and how many days it has left, above category bars that move with every invoice run. Money left from an earlier period carries forward, so an underspent first quarter doesn't read as an overspend in the second. Book a shift and the drawer warns if that participant's released funding is tight or used up on the shift's date; the 07:00 sweep tells the office when a plan is projected to run out, has used 85% of what's been released (a setting you can change), or, in its last 90 days, is heading for at least 20% unspent — because a plan that ends with money unspent is support the participant never received.

Rosters that know the award before the week is worked
Nine SCHADS-style checks run over the draft roster — minimum engagement, breaks between shifts, broken shifts, span, daily and weekly overtime, and the three sleepover rules — and flag a breach while it is still a draft. Each one states its reason and leaves the decision with you, because sometimes a provider has to wear the overtime knowingly. Shift matching ranks who should work a shift and shows its working: availability, checks and training, skills, continuity with that participant, and whether the shift would create an award problem.

The Commission's registers, kept as you work
A support worker reports an incident from their own shift screen, with the visit attached, and everyone who manages incidents is told at once. Reportable incidents carry a 24-hour notification flag and a countdown to the five-day report, and everyone who manages incidents is reminded before each date falls due. Where your practice requires it, closing one waits for a named sign-off, and closing with follow-up actions open needs a reason. Behaviour support plans and restrictive practices sit in one register with a monthly CSV of recorded uses, alongside complaints — each resolved with a recorded outcome — risk assessments and a documents library with expiry alerts and read-and-acknowledge. When an auditor asks, the evidence is already where it should be.

Participant records with real walls
Each participant's record separates need-to-know information from office-only information, so a support worker sees what the office has marked need-to-know, not the whole file. Structured support plans, goals that attach to shifts, and progress notes with their own privacy settings sit in the same record — and the participant portal shows a participant their funding, their schedule and, where you manage their plan, invoices to approve or decline.

Your prices, checked against the NDIS limits
Corella holds the NDIS price limits — for 2026-27, the national figure for 1,017 support items, taken from the NDIA's published catalogue — and checks your price book against them whenever you open Settings → NDIS prices. It lists prices over and under the limit, a stored limit that isn't this year's, item numbers missing from the catalogue or on its Legacy sheet, participant prices above the limit, and lines already billed above it, marked invoiced or claimed, because a claimed line needs a correction rather than a price edit. Three actions follow, each chosen on its own: update the stored limits, bring prices above the limit down, or lift prices that sat on last year's limit. Nothing is written until you have previewed the changes and pressed Apply, and every run is recorded. When the NDIA publishes a new schedule, it reaches Corella in an update.

Three lanes from one invoice run
An invoice run turns the period's delivered shifts and short-notice cancellations into one invoice per participant and funding type. Agency-managed invoices feed the next NDIA claim batch; plan-managed ones are addressed to the plan manager named on the participant's active agreement; self-managed ones go to the participant or their billing contact, as tax invoices. A budget category can be NDIA-, plan- or self-managed apart from the rest of the plan, and the run bills each line on its own route. A standing charge — a fixed weekly, fortnightly or monthly amount — is billed by each run too. A shift whose required form isn't approved yet is held back and named, and bills in a later run once it is. Turn on draft review and invoices open as drafts, so a line can be amended, discounted or waived with a reason before anything is issued. If you also plan-manage or coordinate, those lanes keep their own inbox, claim files and statements beside yours.

Evidence for a plan review
When a plan review comes round, most of what you'll be asked for is already in the record. On the shift, workers record how each goal's strategy went as one of five fixed sentences, in their own name. The goals report lists each participant's goals with the progress your office has set and how many observations were recorded in the period, with the latest; the goal observations report lists every one of them word for word, with who recorded it and on which shift. A progress or outcome report starts with the plan dates, the active goals and the share of the plan invoiced already filled in, and becomes a PDF under your logo once your team has written the rest. The budget utilisation and cancellations reports export beside them.




Photographs are licensed stock images of models, not Corella customers.
The live demo
See it on its own instance.
Every NDIS module switched on, with made-up participants, rosters, notes and claims.
It runs at demo.corellacare.com.au — made-up people, reset every night at 3:00 am Melbourne time.
Guides for this
Written for the person who has to get it right.
- NDIS claimingThe 2026-27 NDIS price guide: every official file, and what changedEvery official 2026-27 pricing file in one place, linked from the NDIA. Then what changed: some caps fell, some rose, the document has a new shape, and since 24 September 2026 the same prices have been set by a ministerial determination — and how to check your price book before the next invoice run.
- NDIS claimingWhy NDIA bulk payment requests get rejected (and how to stop it)The usual causes of a bounced bulk claim in plain English — the header row, item numbers, retired catalogue items and untraceable claim references — what to check before you re-upload, and every rejection code explained.
- NDIS claimingAgency, plan-managed or self-managed: how the invoice actually differsThree funding lanes, three destinations. Agency-managed goes to the NDIA as a bulk payment request, plan-managed to a plan manager as a tax invoice, self-managed to the participant. What each needs on its face, what evidence sits behind it, and the mixed-funding trap that catches even experienced finance staff.
Fair questions
What people in this sector ask us.
What is NDIS software?
Which lines go into the NDIA bulk claim file?
What happens when the NDIA rejects a line?
Is spend measured against released funding or the whole plan?
How does the price book handle NDIS prices — and what happens when they change?
How are short-notice cancellations claimed?
Can we bill provider travel?
We're unregistered, or our participants are plan- or self-managed — does Corella fit?
How are NDIS worker screening checks tracked?
Does Corella handle SIL?
What does it cost for an NDIS provider?
Bring your own roster to the conversation.
We'll walk through the parts of Corella that matter for your service — on a live instance, in your words.

