Skip to content

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.

A young woman in a wheelchair laughing with a friend in a park
A claim batch in Corella's NDIS demo: the NDIA bulk payment request for August 2026, 3 lines, not yet exported, $1,324.44, with its CSV and an Import NDIA outcome button
Bulk payment file, builtThe NDIA's 16-column template
Outcome file read back45 paid · 2 part-paid · 1 rejected

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 work

What'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.

Two colleagues at a laptop showing Corella's NDIS bulk payment requests screen, with the NDIA's payment advice printed on the desk

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.

1 line released · new claim reference

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.

The claim batches card in Corella's NDIS demo: an NDIA bulk payment request for 1 to 31 August 2026 — 3 lines, not yet exported, $1,324.44 — with its CSV and Import NDIA outcome, and a tip that file names are kept under the portal's 20 characters and that the NDIA's results are imported to record what was actually paid
A claim batch: its file to upload, and the outcome to import when the NDIA answers (NDIS demo)

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.

A woman checking figures on her computer against printed papers

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.

The Corella forecast: staffing week by week, with plans running out or heading for underspend counted above
Staffing ahead, with plan warnings on top

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.

Award warnings on the week board in Corella, from the NDIS demo: a red banner saying 8 shifts on this week's roster sit past a SCHADS limit, and a warning triangle on each shift concerned
Award checks on the draft roster (NDIS demo)

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.

The incidents register in Corella
Incidents, with the report deadlines tracked

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.

A participant's record in the NDIS demo, with the need-to-know section marked visible to support workers, the office-only AI summary, and the allied health team beside it
One record: what carers see, and what stays with the office (NDIS demo)

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.

Settings → NDIS prices in Corella's NDIS demo: where your prices stand against the NDIS Pricing Schedule 2026-27 — 21 priced rates across 6 NDIS services checked, nothing over or under the limit, no stale stored limit, no unknown or legacy item — then three separate actions to update the price book to a schedule, none ticked, with nothing written until the changes are previewed and applied
Your prices against the 2026-27 limits, and three actions that write nothing until you apply them (NDIS demo)

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.

A new invoice run in Corella's NDIS demo for 31 August to 6 September 2026: 32 billable shifts found, one invoice per client per funding type, with NDIA-managed invoices feeding the NDIS claim batch afterwards; nine shifts held back because their required aged-care invoice form isn't filled in yet, each named with an Open form link
One invoice per person and funding type — and the shifts held back, by name (NDIS demo)

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.

A support worker's phone in Corella's NDIS demo: Goals — what did you see today?, recorded in the worker's name on this shift for the office; two of a participant's goals, each with its strategy and five fixed sentences from Didn't happen today to Did it on their own
How each goal's strategy went, as one of five fixed sentences (NDIS demo)
A young man in a power wheelchair taking a selfie with a friend outdoors
Supports that look like a life, not a timesheet.
A big smiling group of friends and support staff celebrating together
Group programs with enrolment and attendance.
A young man in a wheelchair high-fiving a friend in the street
Community access, rostered and recorded in one place.

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.

Fair questions

What people in this sector ask us.

What is NDIS software?
Software that runs an NDIS provider's day: rostering support workers, recording what was delivered, pricing it from a price book you check against the NDIS price limits, and claiming it — through the NDIA's bulk payment file for agency-managed participants, or as tax invoices to plan managers and self-managed participants. Corella does all of that in one system, with the incident, restrictive-practice, complaint and risk registers beside it. Corella builds the claim file, you upload it in the provider portal, and the NDIA's outcome file comes back into Corella line by line.
Which lines go into the NDIA bulk claim file?
Every unclaimed line with an NDIS item number from an issued invoice for an agency-managed participant, delivered between the dates you pick. Draft invoices, waived lines and lines charged at $0 stay out. Before the batch builds, Corella checks your NDIS registration number is set, every 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.
What happens when the NDIA rejects a line?
Import the outcome file and the batch shows what was paid, what wasn't, and each rejected line with the NDIA's code and reason. Fix the cause — a participant's NDIS number or your registration number, both read afresh when the file is built, or the line itself: correct its item, quantity or unit price, checked against the Pricing Schedule for the day of service — then release the rejected lines and they join the next batch that covers their dates, each under a new claim reference.
Is spend measured against released funding or the whole plan?
Against released funding, once you record how the plan is released: each funding period's dates and amount go on the service agreement, and spend is measured against every period that has started, so money carried over from an earlier period still counts. The Funding tab, the forecast's warnings, the booking warning and the budget utilisation report all use that rule.
How does the price book handle NDIS prices — and what happens when they change?
You set each service's price and NDIS item number per time band, and Settings → NDIS prices checks every priced line against the NDIS price limits Corella holds for 2026-27. When the NDIA publishes a new schedule, it reaches Corella in an update and the same screen shows where your book differs; nothing changes until you choose an action, preview the exact changes and press Apply.
How are short-notice cancellations claimed?
Cancel the shift as a short-notice cancellation and pick one of the NDIA's four reason codes, and it bills with that code as a cancellation claim; a provider cancellation or an ordinary client cancellation bills nothing. As you cancel, Corella counts the notice — from when the family asked, where they asked on the portal — against the payer's rule or your own policy — seven clear days unless you change it — and suggests a code, and you decide, including whether the worker is paid.
Can we bill provider travel?
Yes. Workers record kilometres and travel minutes on the shift until the timesheet is approved, and payroll pays them. Kilometres driven with a participant bill as activity-based transport at your per-kilometre item, and with one switch in Settings, the drive to a shift and the travel time bill too, claimed against the visit's own support item with ceilings you set. A participant's own record can also keep provider travel off their invoices.
We're unregistered, or our participants are plan- or self-managed — does Corella fit?
Yes. The invoice run addresses plan-managed invoices to the plan manager on the participant's agreement and self-managed ones to the participant or their billing contact, as tax invoices with the delivery records behind them; you need an NDIS registration number only to build an NDIA claim file. A budget category can be NDIA-, plan- or self-managed apart from the rest of the plan, and the invoice run bills each line on its own route.
How are NDIS worker screening checks tracked?
Add the check as a mandatory requirement with an expiry and file each worker's check on their profile. The worker and the office are reminded as it nears expiry, booking someone whose check is missing or expired warns, and shift matching counts checks and training when it ranks who should work a shift. A worker sends a renewed check from their phone; the office confirms it once, and the roster's warning clears.
Does Corella handle SIL?
Yes. Each house keeps its rooms, tenancies and an indicative staffing grid beside the ordinary roster, and sleepovers are a shift type the award checks understand — sleepover length and the rest owed after one, with a limit you set on how often they fall.
What does it cost for an NDIS provider?
$19 per staff user per month, no GST, everything included, with a $149 monthly minimum; texts are the one thing charged by use, at 10c a part. Participant and family portal logins are free and are never counted as seats.

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.