Funders
How NDIA agency-managed payments land in Xero
The NDIA pays one electronic funds transfer per payment batch, covering many participants and many claim lines at once. A valid claim from a provider recorded as a my provider is usually paid in two to three business days. The payee payment remittance advice explains the batch, one row per claim line, with a system suffix added to your own reference. Post the batch through an NDIA clearing account.
Key facts
- Who pays
- The agency itself, one lump sum electronic funds transfer per payment batch, covering many participants and many claim lines13
- How the claim is lodged
- A bulk payment request file uploaded to the myplace provider portal, sixteen columns in a fixed order4
- Time to funds
- Usually two to three business days for a valid claim from a provider recorded as a my provider, and about ten business days where the provider is not recorded as one or the agency checks the claim9
- Breakdown file
- The payee payment remittance advice, one row per claim line, keyed by payment request number5
- What happens to your reference
- The agency appends a system identifier, so an invoice sent as INV-29802 returns as INV-29802-zt99134862m55401775
- Typical batch size
- A fortnightly batch for a mid sized provider commonly runs to 100 to 300 lines across 30 to 80 participants6
- Clearing account in the allied health template
- 102 NDIA clearing, BAS Excluded13
- Revenue account in the allied health template
- 404 Clinical services, NDIS agency-managed, on GST Free Income13
- Where a short payment goes
- 605 Funder shortfalls and write-offs, on the tax type of the original invoice line13
- GST basis
- GST free under s38-38 only where all four tests hold: a plan in effect, a reasonable and necessary support specified in the statement of supports, a written agreement, and coverage by a table in the supports determination1
One payment, one batch, many claim lines
The agency does not pay invoice by invoice. A registered provider uploads a payment request file, the agency processes the lines inside it, and one electronic funds transfer arrives covering many participants and many claim lines at once. The bank feed shows a single credit with no detail behind it. The detail that explains it sits in a separate file.
The scale is what makes this awkward. A fortnightly batch for a mid sized provider commonly runs to 100 to 300 lines across 30 to 80 participants, and a single invoice covering a participant's week of services can appear as 6, 8 or 12 separate rows.
The file you sent decides what comes back
Under PACE, individual claims are replaced by bulk uploads, and a provider has to be recorded as a my provider for the participant before it can claim against the plan. The upload is the bulk payment request, a fixed order file the practice system produces. Four of its columns decide what the remittance can be matched on later, so they are worth understanding before a batch goes out.
| Column | What it carries | Why the ledger cares |
|---|---|---|
| ClaimReference | Free text up to fifty characters, where a practice system puts its invoice number | It is the field that ties a claim line back to an invoice, it is optional to the portal, and it is the field the agency modifies |
| SupportNumber | The support item code for the line | It decides which revenue account the line belongs in once the batch is posted |
| UnitPrice | The unit charge, which cannot exceed the price limit for the item and region | Claiming above the limit is one of the ways a line comes back paid short |
| GSTCode | The tax status of the support as claimed | It has to agree with the tax rate the invoice carries in Xero, or the BAS and the claim tell different stories |
The payee payment remittance advice
The remittance is the document that turns one credit back into a set of claims. It arrives by email and can be downloaded, and it is keyed by payment request number rather than by invoice, because the agency's unit of work is the claim line.
Your reference comes back with a suffix on it
This is the detail that breaks automated matching. An invoice sent as INV-29802 in the ClaimReference column returns on the remittance as INV-29802-zt99134862m5540177. The trailing block is an agency system identifier the practice has no use for, and Xero's find and match only knows the invoice number it holds, so the row will not match on reference.
- Out. The practice system writes the invoice number into ClaimReference on the bulk payment request, up to fifty characters of free text.
- Back. The remittance returns the same value with a system identifier appended, one row per claim line.
- Matched. A prefix match on the known invoice number closes the right invoice, which is what a person is doing by eye when they read past the suffix.
Claim lines are not invoices
Most of the difficulty on this page comes back to one mismatch. The practice keeps a ledger of invoices. The agency keeps a ledger of claim lines. A remittance is the agency's ledger, so the two do not line up row for row, and ticking them off one by one does not make them.
- One invoice, many rows. A week of supports for one participant is one invoice in Xero and one row per support item on the remittance.
- One deposit, many invoices. The credit covers every participant in the batch, so the invoices it closes are spread across the whole debtor ledger.
- One batch, more than one bank line. A batch can settle across two credits, and RemitClear reads Xero as having no field on an invoice or a batch payment that records that the remittance was settled by both.
- One remittance, more than one Xero batch. The three remittance guides read for this page put Xero's batch payment ceiling at two hundred invoices, enforced at the API, while the plan manager guide behind the canonical templates records fifty. A large remittance is posted as several batches whichever figure holds.
The support item code is the field that would tie the two ledgers together, and it does not always reach Xero. Zanda states that the NDIS participant number and the NDIS support item code are not included anywhere in its Xero export, so a practice on that system carries the code across in the service name or matches from the remittance instead.
Short payments and reversals
Two things make a deposit smaller than the claim, and they are treated differently. A short payment is a line the agency approved at less than the invoiced amount, usually because the claim sat above the price limit or the remaining budget. A reversal is a line paid in an earlier batch and taken back in this one, and it arrives as a negative row netted against the deposit.
The canonical templates encode both. A short payment posts to 605, Funder shortfalls and write-offs, on the tax type of the original invoice line, and the template carries a BAS agent note that writing the gap off at all is a practice level choice rather than a given. A reversal is not a write-off.
Rejections after payment come back as negative lines in a later remittance and must be posted as a credit note against the original invoice, on the original line's account and tax type, so the batch total still equals the deposit.13
The Xero pattern behind a single bank line
The pattern the templates encode is a clearing account for the agency. In the allied health template the NDIA rail posts its paid lines to 102, NDIA clearing, coded BAS Excluded. The NDIS provider template posts the same rail to 100, and the psychology template folds the agency and the plan managers into one NDIS rail at 104, so the code follows whichever chart the practice started from.
- Each invoice the remittance closes is receipted to the NDIA clearing account on the payment date the remittance states.
- The credit in the bank feed is matched as a transfer out of the clearing account, which leaves one exact match rather than a hundred.
- The clearing account balance is the money the agency has approved that the bank has not yet delivered, and it returns to nil once the batch lands.
- A balance that will not clear is a claim line paid but not matched, or matched but not paid, and both are worth chasing while the remittance is still to hand.
Practice systems point the same way. Splose tells Xero users to reconcile the lump sum in Xero against the remittance first, then mark the claim as finalised in splose with no payment applied, so the money is accounted for once rather than twice.
GST on an agency managed support
Agency managed funding does not decide the GST treatment on its own. A supply to a participant is GST free under s38-38 only where four things hold together: a plan in effect under section 37 of the NDIS Act, a reasonable and necessary support specified in the statement of supports in that plan, a written agreement between the provider and the participant or another person acting for them, and coverage by one of the tables in the supports determination. Who pays the invoice is not one of the four.
A listed health service stands on its own footing under s38-10, where a recognised health professional in that service performs it and the profession generally accepts it as necessary for the appropriate treatment of the recipient, so the four tests bite hardest on supports that are not listed. The ATO's own worked example is exercise physiology delivered to a participant at a clinic rather than a hospital, with no Medicare benefit payable: the first three tests are met, the fourth is not, and the supply is not GST free. The canonical NDIS provider template models this directly: the funding source default is GST free income, and a non-listed support category row overrides it to taxable with a BAS agent note attached.
One consequence is easy to miss. Where GST applies to a support, the agency's price limit for it is inclusive of GST, so a taxable support claimed at the limit yields one eleventh less net revenue than a GST free support at the same limit. The revenue line and the claim have to agree on that, or the practice's own reporting will overstate what the batch earned.
What Ledger Map does with an NDIA batch
Ledger Map holds one standing map for the practice, approved before anything syncs. A claim line resolves to its account and its tax rate through that map, the batch is posted as one balanced document set against the NDIA clearing account, and the bank feed is left with one exact match to accept. A line the map cannot resolve becomes a question with the options laid out, not a silent posting.
No treatment on this page is one Ledger Map chose. The accounts and the tax rates come from the canonical template the practice starts from, and the practice approves the map first. The way Medicare bulk bill and NDIS plan managed work through the same clearing pattern is worth reading beside this, because a practice with all three sees three deposits that behave differently. The product walkthrough shows the map and the question queue.
Questions
Why does my NDIA remittance have more lines than invoices?
Because the agency pays claim lines and you raised invoices. A single invoice covering a participant's week of supports can appear as six, eight or twelve rows on the remittance, one per support item claimed. Collapse the rows to one amount per invoice before you try to match anything.
Why does the NDIA change my invoice number?
It appends its own system identifier to the reference you sent, so INV-29802 returns as INV-29802-zt99134862m5540177. The suffix carries no meaning for the practice, and Xero's find and match only knows the invoice number it holds, so match the known invoice number as a prefix of the returned reference.
How long does the NDIA take to pay a payment request?
The agency's own guidance says a valid claim from a provider recorded as a my provider is usually paid within two to three business days. It says payment can take about ten business days where the provider is not recorded as a my provider, or where the agency checks the claim is accurate, and a claim held for review is paid within two to three business days once it is approved.
Why is the NDIA payment less than the amount I claimed?
Either a line was approved at less than the invoiced amount, usually against the price limit or the remaining budget, or a claim paid in an earlier batch was reversed and netted against this one. The remittance status column tells you which, and the two are posted differently: a shortfall to the shortfall account, a reversal as a credit note against the original invoice.
Is NDIS agency-managed income GST free?
Only where all four s38-38 tests hold: a plan in effect, a reasonable and necessary support specified in the statement of supports, a written agreement with the participant or with someone acting for them, and coverage by one of the tables in the supports determination. A listed health service stands on its own footing under s38-10, where a recognised health professional performs it and the profession accepts it as necessary for the appropriate treatment of the recipient. On the ATO's own example, exercise physiology delivered to a participant at a clinic with no Medicare benefit payable is not GST free.
Sources
Open questions
- Xero's batch payment ceiling is unsettled. The three remittance guides read for this page put it at two hundred invoices and describe it as an API level limit, while the plan manager guide behind the canonical templates records fifty. Neither figure was confirmed against Xero's own documentation.
- The GST codes the bulk payment request accepts are unsettled. The research corpus records three codes, taxable, GST free and out of scope, while Teiro's current validator page describes two.
- The suffix example rests on one worked case in one vendor guide. Whether the shape is stable across batches and providers has not been tested against a real remittance.
- No bank narration is stated for an NDIA batch, because the research could not confirm one from a primary source. The matcher learns descriptor patterns from the practice's own bank feed instead.
- GST and health, National Disability Insurance Scheme
Australian Taxation Office. Retrieved 3 Sep 2026. Source updated 13 Jun 2024.
primary
- GST and health, other health services
Australian Taxation Office. Retrieved 3 Sep 2026. Source updated 12 Jun 2024.
primary
- NDIS remittance processing in Xero
RemittanceGo. Retrieved 2 Sep 2026. Source updated 2 Jun 2026.
secondary
- NDIS remittance processing in Xero, a guide
RemitClear. Retrieved 2 Sep 2026. Source updated 15 Apr 2026.
secondary
- Xero's 200 invoice batch payment limit
RemitClear. Retrieved 3 Sep 2026. Source updated 23 Apr 2026.
secondary
- Reconciling a remittance settled across two bank deposits in Xero
RemitClear. Retrieved 3 Sep 2026. Source updated 25 May 2026.
secondary
- Guide to getting paid, payment terms, read through an Internet Archive capture of 20 August 2026
National Disability Insurance Agency. Retrieved 4 Sep 2026.
primary
- NDIS pricing arrangements and price limits 2025-26, version 1.1
National Disability Insurance Agency. Retrieved 4 Sep 2026. Source updated 14 Oct 2025.
primary
- The canonical configuration templates, allied health by funding source and NDIS provider
Ledger Map. Retrieved 2 Sep 2026.
primary
- myplace provider portal and resources
National Disability Insurance Agency. Retrieved 2 Sep 2026.
unverified
Review
Last reviewed 4 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.