NDIS claiming, start to finish: from a finished shift to money in the bank

If you coordinate rostering, finance or plan management for an NDIS provider, you already know the claim doesn’t happen in one step. It happens in six, across different systems and different people, and money stalls wherever one of those steps is skipped or delayed. This guide walks the whole chain in order, so you can see where your own process has a gap.

Most “how to claim NDIS” content starts at the invoice. That’s the middle of the process, not the start. The real chain looks like this:

1. A shift is worked and its notes are finished.
2. The timesheet is approved.
3. Each line is priced from a price book, checked against the current national price limits.
4. The invoice run sends each line down the right funding route — NDIA-managed, plan-managed or self-managed.
5. The NDIA-managed lines go into the bulk payment file and are uploaded by hand in the provider portal.
6. The outcome comes back — paid, part-paid or rejected — and gets reconciled line by line.

Skip step six and you’ll never know how much of what you claimed actually landed. Skip step one’s timing and you may not get to claim at all.

A completed shift produces a timesheet and, ideally, a progress note finished before the worker clocks off. From 1 December 2026, timing stops being a best-practice nicety: under the NDIS Act 2013, s45A, claims must be made within 90 days of the support being delivered. A note finished days late doesn’t just look sloppy, it can be the difference between a claimable line and an unclaimable one. Build the habit at the note, not at the invoice run — by the time finance is chasing a claim, the 90-day window may already be most of the way gone.

Nothing should be priced or invoiced from an unapproved timesheet. This is the checkpoint where someone confirms the shift actually happened as logged — right worker, right times, right client — before it becomes a billable line. Bulk-approving a week of clean timesheets and pulling out the exceptions for a closer look is the fastest way through this step without rubber-stamping errors into your claims.

Every approved line needs a price, and that price has to sit inside the relevant NDIS support item’s current national limit. Price books drift out of date quietly — a new plan year lands, limits change, and a line that was compliant in June can be over the cap in July. This is exactly the kind of error that gets caught at reconciliation (step 6) rather than at the point of claiming, which means you find out weeks later instead of on the day. If you want the actual numbers for the current plan year, that’s a job for a pricing-specific reference, not this guide — see the 2026–27 price schedule guide for the detail.

This is where “NDIS claiming software” and “NDIS invoicing software” searches usually converge, because one invoice run has to handle three different destinations:

• NDIA-managed lines go into the bulk payment file for upload to the NDIA provider portal.
• Plan-managed lines go out as a standard tax invoice to the plan manager.
• Self-managed lines go to the participant or whoever handles billing on their behalf.

The complication most teams hit isn’t any one of these routes — it’s that a single participant’s plan can mix all three by budget category. Core supports might be NDIA-managed while capacity building is plan-managed, or a participant might self-manage one category and have a plan manager handle the rest. An invoice run that can’t split a plan by category means someone is manually re-sorting lines before they go out, every cycle. For the full mechanics of each route, the invoicing-by-management-type guide covers that ground in detail.

Partial payments are worth planning for here too — a participant or plan manager might pay part of an invoice now and the remainder later, and your records need to hold that without losing track of what’s still owed.

NDIA-managed lines are compiled into the bulk payment file — the NDIA’s 16-column format — and that file is uploaded in the provider portal by a person. On this route the file has to leave your system, land on someone’s desk (yours), and get uploaded through the portal. Build that upload into your claim cycle as a deliberate, scheduled step, not something that happens whenever someone remembers.

Here’s the part of the chain that genuinely gets missed. The NDIA returns a payment-request outcome file after you’ve claimed, and that file tells you, line by line, what actually happened: paid, part-paid, or rejected, with the NDIA’s own reason for each rejected line.

Most providers stop at “we submitted the claim” and never go back to check what was actually paid against what was claimed. That gap is where money quietly disappears — a handful of rejected lines sitting unclaimed because nobody read the outcome file closely enough to notice they needed re-submitting under a fresh reference.

Reading that file line by line, matching it against what you sent, and re-claiming only the rejected lines (not the whole batch) is the difference between “we submitted a claim” and “we got paid what we were owed.” If you’re dealing with a batch of rejections right now, the rejections guide walks through common reason codes and what to do about each one.

Every step in this chain depends on the one before it. A note finished late undermines the 90-day window before pricing even happens. A price checked against last year’s limits produces a line that gets rejected at step six, no matter how clean the invoice run was. An invoice run that can’t split a mixed-management plan creates manual rework that delays the bulk file going up, which delays the outcome file coming back, which delays reconciliation. Treat claiming as one chain with six links, and the weak link becomes obvious. Treat it as six separate jobs done by different people in different systems, and it rarely is.

Corella carries a claim the whole way through this chain in one place: a price book checked against the 2026–27 national limits, invoice runs that send each line by its funding route — NDIA bulk file, plan-manager tax invoice, or participant invoice, even when one plan mixes all three — and partial payments recorded against what’s actually come in. The NDIA’s 16-column bulk payment file is generated ready for upload, and once you’ve uploaded the outcome file back, Corella reads it line by line and shows what was paid, part-paid or rejected, with the NDIA’s own reason, so rejected lines can be released and re-claimed under a fresh reference. For providers who also run their accounts through Xero, the connector pushes each invoice, with its PDF, to your Xero.