Problems
The NDIA paid less than I invoiced
Three different things make an NDIA deposit smaller than the invoice behind it. The claim was paid at the support item's price limit, it was paid down to what was left in the participant's plan, or a line was rejected rather than trimmed. The remittance says which, because every row carries both the amount claimed and the amount paid.
Key facts
- What tells you which cause you have
- The remittance carries the claimed amount and the amount paid as separate fields on every row, and the two differ when a claim was only partly approved.4
- The cap a claim line cannot pass
- The claim file carries one unit price column, the price per unit sold or the hourly price of the service, and the portal pays no more than the maximum catalogue price for the item.1
- What the ceiling sits on
- Where GST applies to a support, the price limit for that support item is inclusive of GST.9
- What happens to a rejected line
- Each uploaded line comes back as its own result. A rejected item is corrected and sent again in a new bulk upload rather than repaired inside the old one.5
- Why claims reject, in a provider's words
- Over budget, expired plans, wrong item numbers, duplicate lines8
- Where a written off gap posts
- Account 605, Funder shortfalls and write-offs, carrying the tax type of the original invoice line rather than a fixed Xero code3
- Whether the gap is written off at all
- A practice level choice. The canonical template attaches a BAS agent note to the account rather than settling it, because leaving the balance outstanding is the other valid answer.3
- Why one participant can be short paid and not another
- Price limits differ by the participant's location band, standard, remote or very remote, so the same support item can sit under different ceilings inside one batch.6
- The check that says you are finished
- Once every line on the remittance has been allocated, the balance for that batch returns to nil.4
Start with the two columns on the remittance
The Payee Payment Remittance Advice is one row per claim line rather than one row per invoice, and every row carries the amount claimed beside the amount paid. That pair is the whole diagnosis. Where the two match, the line was approved in full. Where the paid figure is lower, the agency approved less than the claim asked for. Where a row you expected is not there at all, nothing was approved and the money was never coming in this batch.
Sort the remittance by the gap between the two columns and split the exceptions into two piles: lines paid at less than the claim, and lines that are missing. The two piles need opposite entries, and treating them alike leaves an invoice closed that should be open.
A provider that reconciles remittances weekly knows its true revenue and its true debtors.8
Three causes behind one short deposit
The three sit behind a single number in the bank feed, which is why a short deposit feels like one problem. It is not. Two of the three are approvals at a lower figure and one is not an approval at all.
| What happened | How the remittance shows it | What the invoice needs |
|---|---|---|
| The claim sat above the support item's price limit | The line is there, with the paid amount under the claimed amount | A part payment for what was approved, then a decision on the gap |
| The participant's plan had less left in it than the claim | The same shape: a paid line worth less than the claimed line | A part payment, then the gap chased before it is written off |
| The whole line was rejected | No paid row for that line, or a rejected result against it | Nothing posted. The line stays open and goes back in a new file |
Paid at the support item's price limit
The portal guide is blunt about the cap: where the amount entered is above the maximum per unit catalogue price for the item, the portal pays only up to that price. The limit itself is inclusive of GST where GST applies to the support. A claim lodged above the limit is funded up to the limit rather than at the amount asked for, so the gap surfaces in the deposit rather than in the file. What has usually drifted is the practice's own rate card, because the limits moved and the practice management system did not.
This cause tends to repeat. If one participant's therapy line came back short, the other lines on that support item in the batch usually came back short too, because they met the same cap. One exception is worth knowing before you rule the price limit out: the limits differ by the participant's location band, standard, remote or very remote, so one participant can sit under a higher ceiling than the rest of the batch.
Fixing the ledger is the small half of the job. Until the item is repriced the same gap arrives every fortnight, and each one is another exception somebody has to work.
Paid down to what was left in the plan
The second cause looks identical in the ledger and is a different conversation. The claim was inside the price limit, but the participant's plan did not hold enough in the relevant support budget to cover it, so the agency approved what was left and stopped. Nothing was priced wrongly. The funding ran out.
It shows up on one participant rather than across an item, and it tends to arrive near the end of a plan period. It is also the one cause where the gap may still be collectable: the service was delivered under an agreement, and who carries the balance is a question for that agreement rather than for the ledger. Writing it off on the day it appears closes a conversation that has not happened yet.
A line that was rejected, not trimmed
The third cause is the one most often mistaken for a short pay, because the bank line looks the same: less money than the invoices said. The difference is that no partial approval happened. A line that fails validation is paid nothing, and the fix is a resubmitted claim rather than an adjusted invoice.
Claims reject: over budget, expired plans, wrong item numbers, duplicate lines.8
The practice management systems handle this the same way. A rejected item is corrected and sent again in a new bulk upload, and splose adds a step people miss: an item that sat in an earlier upload has to be removed from that upload before it becomes available again, so a corrected line does not appear in the new file until it is.
Three things that look like a short pay and are not
- A reversal. A line paid in an earlier batch and taken back in this one arrives as a negative row netted against this deposit, so the deposit is short by money that was never about these invoices. It takes a credit note against the original invoice, which is what keeps the batch total equal to the deposit. Negative lines on an NDIS remittance works that case through.
- A split settlement. One remittance can be paid across two bank credits, and the first credit is short of the remittance total simply because the rest has not arrived. Check the remittance total against the sum of the credits before deciding any line was short paid.
- A missing batch. Two batches in the same week, one reconciled and one not, reads as a short pay against a week of invoices. This is why the check runs per remittance rather than per week.
All three are ruled out by the same discipline: reconcile one remittance at a time and expect its own lines to account for its own deposit. How an NDIA batch lands in Xero covers the batch mechanics behind that.
Why a taxable support at the same limit earns less
There is a fourth way a batch comes in under expectation, and it is not a short pay. Because the price limit is inclusive of GST where GST applies, a support that carries tax leaves less on the revenue line than a support that does not, claimed at the very same limit. The difference is one eleventh, and it belongs to the activity statement rather than to the practice.
A practice that budgeted at the limit and claimed on the taxable code will read the shortfall as a funder problem when it is an arithmetic one. Whether a given support is GST free turns on the four tests the ATO sets out, the plan, the supports, the written agreement and the determination, rather than on who paid, and NDIS price limits and GST works through them. Nothing on this page decides a treatment for a practice.
The entry each cause takes in Xero
The canonical templates carry all of this on one rail. The NDIA rail has three components: the paid lines, which land in the settlement account for the rail, the short payments, which post the gap to account 605 on the original line's tax type, and rejections and clawbacks, which carry no account of their own because that entry belongs against the original invoice line. A line rejected before any money moved is the case the rail has nothing to post for, because nothing was paid.
| Cause | Entry against the invoice | Where the gap goes |
|---|---|---|
| Paid at the price limit | Receipt the approved amount on the payment date the remittance states | Account 605, on the original line's tax type, or left outstanding |
| Paid to the remaining budget | The same receipt, on the same date | Chased under the service agreement first, then 605 if the practice writes it off |
| Line rejected | No payment against that line at all | Nowhere. The invoice stays open until a corrected claim pays it |
| Reversal in a later batch | A credit note against the original invoice line | Nowhere. The credit note is what keeps the later batch equal to its deposit |
The receipt goes to the settlement account for the rail, coded BAS excluded, because the revenue was recognised when the invoice was raised and the deposit only moves money. Reconcile a part payment runs the mechanics of the partial receipt itself.
Decide the write off once, not per deposit
Whether an approved gap is written off at all is a practice decision, and the canonical template says so rather than settling it: the shortfall account carries a BAS agent note, because leaving the balance outstanding against the participant is the other valid answer. Made once and written down, it stops being a judgement call at every month end.
When the gap is written off, the tax type on the write off follows the original invoice line rather than a fixed code, because the write off is a partial reversal of that supply. That is why the template records a rule there instead of a Xero code.
The standing check is the settlement account itself. Once every line on a remittance has been allocated, the balance for that batch returns to nil, so anything left is a line nobody worked. A clearing account that will not clear sorts those leftovers by cause.
What Ledger Map does with a short paid batch
Ledger Map posts one balanced document set per deposit and leaves one exact match in the bank feed. A line paid at less than it was claimed at is posted as a part payment with the gap held as its own item, a rejected line is posted as nothing and raised as a question, and a negative row is posted as a credit note so the batch still equals the money that arrived.
The accounts and tax rates come from the canonical template the practice starts from, and the practice approves its map before an invoice syncs. The short paid lines leave the deposit as a named list with a cause on each one.
Questions
Why did the NDIA pay less than I invoiced?
Usually one of three things happened: the claim was above the price limit for that support item, the participant's plan had less left in it than the claim, or the line was rejected outright and paid nothing. Compare the claimed amount with the amount paid on each remittance row: the first two show a paid line worth less than the claim, and the third shows no paid line at all.
How do I tell a short payment from a rejected claim?
The test is whether the line was paid at all. A short payment is an approval at a lower figure, so the row is on the remittance with a paid amount under the claimed amount. A rejection pays nothing, so there is no paid row for that line. The first needs a part payment against the invoice, the second needs the invoice left open and the claim sent again.
Should I write the difference off?
Only an approved short payment is a candidate, and only once the practice has decided its policy. The canonical templates put a written off gap in account 605, Funder shortfalls and write-offs, on the original invoice line's tax type, and attach a BAS agent note because leaving the balance outstanding is the other valid choice. A rejected line is not written off at all.
Why does the same support item come back short every fortnight?
That pattern points at the price limit rather than at any one participant. The unit price on a payment request cannot exceed the published limit for the support item, so a rate card that has drifted above the limit produces the same gap on every claim for that item until the item is repriced.
Can a provider charge more than the NDIS price limit?
Not on an agency managed claim: the portal pays no more than the maximum catalogue price for the support item, so a claim lodged above the limit comes back short of what was invoiced rather than paid in full. The limits also differ by the participant's location band, standard, remote or very remote, so the ceiling is not the same for every participant on the same item.
The deposit is short but every line was paid in full. What now?
Look for a negative row from an earlier batch netted into this deposit, or for a remittance settled across two bank credits. Both make the money arriving smaller than the invoices without any line being short paid, and both are ruled out by checking the remittance total against the credits before working any invoice.
Read next
Sources
Open questions
- No price limit appears anywhere on this page. The pricing arrangements were read here for the rule that the limit includes GST, not for any support item's figure, so the rate strip works a round tax inclusive unit price instead and that number is not a limit.
- Whether an approved gap is written off, or left outstanding against the participant, is a practice and BAS agent decision. The canonical template attaches that note to the shortfall account rather than settling it, and this page does the same.
- The unit price rule here comes from the June 2025 edition of the portal guide, which the corpus holds as the payment request column rules because the guide's own address returned an automated fetch refusal on 3 Sep 2026. Whether a later edition supersedes it was not confirmed.
- Whether an approved gap can still be claimed later is not settled here. Provider Choice, a plan manager, says an invoice that outran the plan's funds can be re-invoiced under an alternative line item, or sent to the agency as a manual payment request once the plan has ended, with payment at the agency's discretion. That is the plan managed path, and the agency managed equivalent was not confirmed, so writing the gap off on the day it appears can be early.
- Bulk payment requests, self help guide for providers, myplace provider portal, June 2025 edition
National Disability Insurance Agency. Retrieved 1 Oct 2025. Source updated June 2025.
primary
- GST and health, National Disability Insurance Scheme
Australian Taxation Office. Retrieved 3 Sep 2026. Source updated 13 Jun 2024.
primary
- The canonical configuration templates, allied health by funding source and NDIS provider
Ledger Map. Retrieved 3 Sep 2026.
primary
- NDIS remittance processing in Xero, a guide
RemitClear. Retrieved 3 Sep 2026. Source updated 15 Apr 2026.
secondary
- My invoice has been partially paid due to being over the price cap or limit, what does this mean?
Provider Choice. Retrieved 3 Sep 2026.
secondary
- My invoice cannot be processed due to insufficient funds, what does this mean?
Provider Choice. Retrieved 3 Sep 2026.
secondary
- NDIS pricing arrangements and price limits 2025-26, version 1.1, read through an Internet Archive capture
National Disability Insurance Agency. Retrieved 4 Sep 2026. Source updated 14 Oct 2025.
primary
Review
Last reviewed 3 Sep 2026 by Shane
General information for Australian allied health practices, not tax advice. Confirm a treatment with your BAS agent or accountant before you post it.
Guided onboarding
Run one real month before you go live.
Sign up, connect Zanda and Xero, and replay a month you already closed. The map is reviewed with whoever owns the books, and nothing posts until you approve it.
Every practice starts from a template. Nothing posts until the map is approved.