Problems
Negative lines on an NDIS remittance advice
A negative row is a claim the agency or a plan manager paid in an earlier batch and has taken back in this one. The deposit that arrives is already net of it. The canonical templates post it as a credit note against the original invoice, on that line's own account and tax type, so the batch total still equals the money in the bank.
Key facts
- What a negative row is
- A claim paid in an earlier batch and taken back in this one. Rejected or cancelled claims appear on a later remittance as negative lines.2
- What it does to the deposit
- The remittance total is a net figure rather than a sum of positives, so the credit that arrives is the approved lines less the negatives.3
- The check before anything is posted
- The approved lines less the rejected lines equal the money received, exactly.3
- What the canonical templates post
- A credit note against the original invoice, on that line's own account and tax type, so the batch total still equals the deposit1
- The account code a reversal carries
- None. The rejections and clawbacks component in both canonical templates has no account code, where a short payment has one.1
- Where a reversal comes from
- The bulk payment request the practice uploads has no field for reversing a claim already paid, so a negative row is the agency's own entry rather than something a provider can send.6
- The row that hides
- A rejected or adjusted claim can arrive as a zero dollar row as well as a negative one, and a zero dollar row is easy to scroll past.4
- How far back a reversal reaches
- A claim submitted weeks ago and allocated to an invoice two remittances ago can be reversed on today's file.2
- What happens to the claim itself
- A corrected line goes out in a new bulk upload rather than being repaired inside the old one, and an item held in an earlier batch is released before it can be claimed again.5
What a negative row on a remittance is
It is money going the other way. Every other row on the file is a claim the funder approved and paid. A negative row is a claim it approved and paid in an earlier batch and has now taken back, usually because the line failed a check after the money went out. The funder does not send an invoice for it. It simply pays you less this time.
That is what makes it hard to see. The reversal is not attached to any invoice on the file you are holding. It belongs to an invoice you closed weeks ago, in a batch you have already reconciled, and it arrives in the middle of a long list of ordinary approved lines.
Rejected or cancelled claims can appear on a later remittance as negative lines.2
Why the deposit is already net of it
The total at the bottom of the remittance is the figure that should equal the bank credit, and that total is a net one. The reversals are subtracted from the approved lines and the difference is what gets transferred, so the money comes out of this batch rather than arriving later as a demand for it back.
So the deposit is smaller than the approved lines on the same file, and every line on it may still have been paid in full. That is a different problem from a claim paid at less than it was invoiced for, which the NDIA paid less than I invoiced works through.
Where a reversal shows on the file
The remittance is one row per claim line rather than one row per invoice, so a reversal is one line among many and carries no flag of its own beyond its amount. These are the fields it shows up in, and the reason each one is easy to read past.
A reversal is not a short payment
Both make a deposit smaller than the invoices behind it, and they are opposite events. A short payment is an approval at a lower figure on a claim that stands. A reversal is the withdrawal of an approval that was already made and already banked. Treating one as the other is the entry that does the damage.
| What happened | How the remittance shows it | What the ledger takes |
|---|---|---|
| The claim was approved at less than it was invoiced for | The line is there in this batch, with a paid amount under the claimed amount | A part payment for what was approved, then a decision about the gap |
| A claim paid in an earlier batch was taken back | A row below zero in this batch, belonging to an invoice already closed | A credit note against the original invoice, allocated inside this batch |
| The line was rejected before any money moved | No paid row for the line at all | Nothing. The invoice stays open until a corrected claim pays it |
The entry the canonical templates post
Both canonical templates carry a rejections and clawbacks component on the agency's rail, and it is written as a rule rather than as a posting. There is no account code on it, and its tax type is the original invoice line's tax type rather than a fixed Xero code. The short payment component beside it does carry an account, 605, which is the difference the file is drawing.
- Find the invoice the reversed claim was originally allocated to, using the invoice number as a prefix of the reference on the earlier remittance.
- Raise a credit note against that invoice, on the same revenue account and the same tax rate the original line carried.
- Allocate the credit note inside this batch, so the value of the batch drops by the reversal and matches the deposit.
- Leave the claim itself in the resubmission queue if it can be corrected and sent again.
The credit note is what keeps the two sides equal. It reverses the revenue that was recognised on the original supply, it carries that supply's own tax treatment rather than a new one, and it takes the batch down to the money that actually arrived. Reconcile a credit note covers the mechanics in Xero.
Why a write off is the wrong answer
The quick fix is to force the batch to balance by posting the difference to an expense account and moving on. It reconciles, and it hides three things at once: which invoice lost its money, whether the claim can be sent again, and whether the revenue on the original supply is still overstated in a period that has been reported.
The check that proves the batch
One arithmetic check does most of the work, and it runs before anything is posted rather than after. The approved lines less the negatives should equal the money received, exactly, and the negatives are the part people skip.
- Total the positive rows on the remittance.
- Total the negative rows, and count the zero dollar rows while you are there.
- Subtract the second from the first and compare the result to the credit in the bank, since the payment date on the file is not the date the money settles.
- If the two agree, every row is accounted for and the batch can be posted. If they do not, a row has been missed rather than mispriced.
A batch posted without that check leaves a balance in the clearing account that nobody can name later, which is the ordinary way a clearing account will not clear starts.
The ledger either way
The two columns cost the same amount of work on the day. They differ three months later, when somebody asks which participant the money came back on and only one version can answer.
When the reversal lands in a closed period
This is the part the guides leave out. The invoice a reversal belongs to was usually paid and reconciled in an earlier month, and often in a period that has been reported. The credit note is dated in the period the reversal arrives, so the revenue moves out in this period rather than out of the one that recognised it.
- Where the earlier period is closed, the credit note sits in the current one and the earlier report stands as filed. Whether that period needs revisiting is a question for the practice and its accountant, not for the reconciliation.
- Where a lock date blocks the document entirely, the item queues rather than being re-dated quietly. Lock dates and sync covers what a blocked document looks like.
- Where the practice reports on a cash basis, the reversal lands with the credit note rather than with the original invoice, which is worth knowing before the numbers are compared across two months.
Plan manager negatives read differently
The same event arrives in a different file when the participant is plan managed. Each plan manager is its own debtor with its own remittance layout, and the columns that carry the reference and the status are named differently in each one, so the negative row is found by reading the amounts rather than by looking for a known column.
- The reference is the plan manager's claim reference, which often does not tie to your invoice number, so the trace back to the original invoice is longer.
- The template treats the event the same way: the plan manager rail carries its rejected lines with no account code and the original line's tax type.
- A long run can force more than one Xero batch for a single remittance, and the negative belongs to whichever batch keeps that batch equal to its own share of the deposit.
How an NDIA batch lands in Xero and NDIS plan managed payments set out the two money flows behind these files.
What Ledger Map does with a negative row
Ledger Map reads the whole remittance before it posts anything, so a negative row is part of the batch rather than a difference discovered at the end. The reversal is posted as a credit note against the invoice the original claim was allocated to, on that line's own account and tax rate, and the batch is posted as one balanced document set that leaves one exact match in the bank feed.
A negative row that cannot be traced back to an invoice becomes a question with the candidates listed, not a silent posting. The accounts and tax rates come from the canonical template the practice starts from, and the practice approves its map before anything syncs. The product walkthrough shows the map and the question queue.
Questions
What is a negative line on an NDIS remittance advice?
It is a claim that was paid in an earlier batch and has been taken back in this one, usually because the line failed a check after the money went out. It belongs to an invoice you have already closed, and the deposit for this batch is reduced by it.
Why is my NDIS deposit smaller than the lines on the remittance?
Because the total at the foot of the file is a net figure. The funder subtracts the reversed claims from the approved ones and transfers the difference, so every line in this batch can have been paid in full and the credit still arrives short.
How do I post an NDIA clawback in Xero?
As a credit note against the invoice the original claim was allocated to, carrying that line's own revenue account and tax rate, allocated inside the batch you are reconciling. That takes the batch down by the reversal so it equals the deposit, and it leaves a document that names the invoice the money came back on.
Should I write the reversed claim off?
A reversal is not a shortfall, so the shortfall account is the wrong home for it. Account 605 holds an approved short payment the practice has decided not to chase. A reversed claim may still be correctable and payable, so it stays visible until somebody decides whether it is resubmitted or credited for good.
Can I claim a reversed line again?
Often yes, where the reason it failed can be fixed. A corrected line goes out in a new bulk upload rather than being repaired inside the old one, and an item held in an earlier batch has to be released before it can be claimed again, which is why a corrected claim sometimes fails to appear in the new file.
Read next
- ProblemsThe NDIA paid less than I invoiced
- FundersHow NDIA agency-managed payments land in Xero
- FundersPlan-managed NDIS payments in Xero
- Xero how toHow to reconcile a credit note in Xero
- Practice systemsSplose Xero integration and the NDIS lump sum
- FundersSelf-managed NDIS clients: payment and GST
- HubProblems
Sources
Open questions
- Whether the remittance carries a distinct status value for a reversed line, or only an amount below zero. The agency's own site refuses automated fetches, so there is no primary field list for the payee payment remittance advice behind this page.
- Whether a plan manager nets a reversal into its next run or pays it separately. Formats differ per plan manager and the research corpus records no single answer.
- Xero's batch payment ceiling is unsettled in the sources read for this corpus, at fifty invoices in one guide and two hundred in others, which decides how many batches a long remittance needs.
- Whether Xero accepts a credit note inside a batch payment or requires it allocated separately. Xero Central returned no content to an automated fetch on 3 September 2026, so this page describes the outcome rather than the click path.
- What to do about an earlier reported period when a reversal lands against an invoice inside it is a practice and accountant decision, and this page leaves it open rather than settling it.
- The canonical configuration templates, allied health by funding source and NDIS provider
Ledger Map. Retrieved 3 Sep 2026.
primary
- How to process NDIS remittances in Xero, provider guide
RemitClear. Retrieved 3 Sep 2026. Source updated 15 Apr 2026.
secondary
- Reconcile NDIS plan manager remittances in Xero
ToTheCent. Retrieved 3 Sep 2026. Source updated 8 Jul 2026.
secondary
- NDIS remittance processing in Xero
RemittanceGo. Retrieved 3 Sep 2026. Source updated 2 Jun 2026.
secondary
- 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
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.