Skip to main content

Funders

Plan-managed NDIS payments in Xero

A plan-managed provider invoices the plan manager, not the agency and not the participant. The plan manager checks the invoice against the budget, claims from the agency, waits for the funds to be released, then pays. Money arrives as one transfer per plan manager, batched across many invoices. The deposit lands in a plan manager clearing account, BAS excluded. The revenue leg behind it is GST free.

Key facts

Who pays
The plan manager, from the participant's funds it holds, once the agency has released them2
Deposit shape
One electronic funds transfer per plan manager per run, batched across many invoices3
Claiming cadence
Approved invoices go to the agency twice a day at one large plan manager2
Time to funds
Most payments complete within three to five days of the invoice reaching one large plan manager, and up to six days when the agency is slower to release2
Written terms
Common payment terms of 14, 30 or 45 days from invoice date, since each plan manager sets its own1
Breakdown file
The plan manager's own remittance, keyed by a claim reference that often carries a prefix3
Rejections and short pays
Rejected or clawed back lines return as negative amounts on a later run, so the run total is a net figure rather than the sum of the claims it lists3
GST treatment
GST Free Income is the tax rate on the plan-managed revenue row of all three canonical templates, which put that revenue in two different accounts10

Five stages, and the practice owns one

Plan management puts a business between the practice and the agency. The participant's funds are held and paid out by a plan manager, so the invoice goes to a company with its own approval step, its own claiming cadence and its own bank run. The agency still supplies the money. It just pays the plan manager first.

That is why plan-managed work settles later than agency-managed work without anybody being slow. Five stages sit between raising the invoice and reconciling the bank line. The practice owns the first one. The other four are a budget check, a claim, a release and a payment run, each running on somebody else's clock.

Plan-managed NDIS money, invoice to bank lineFive stages from the practice invoice to the bank line: the plan manager checks the invoice against the budget, claims from the agency twice a day, waits for the funds to be released, then pays one batched transfer into the plan manager clearing account.Plan-managed NDIS money, invoice to banklineDay of the claim runYou invoice the plan managerThe invoice carries the participantnumber, the support item codes and theservice dates, and the plan manager isthe debtor.Before the next of two daily runsChecked against the budgetThe plan manager checks the invoiceagainst the participant's plan budgetand the published price limits.Twice a day at NDSPClaimed from the agencyApproved invoices are lodged with theagency in batches rather than one at atime.Two to three days at mostFunds releasedThe agency releases the money to theplan manager, which does not pay theprovider before that happens.One to two days, bank dependentPaid to the practiceOne transfer per run, batched acrossevery invoice that plan manager settledin the cycle.Lands in101 Plan manager clearing
Plate 1The hops between an invoice and a plan-managed deposit, and who is holding the money at each one. The account code is the NDIS plan-managed template's, where 101 is the plan manager clearing account; the allied health chart holds the same rail at 103.

Who owes the practice the money

The plan manager is the debtor. That is the whole difference from the other two management types, and it changes the debtor ledger rather than the invoice. Under agency managed the agency pays the practice against a claim it lodged itself. Under self managed the participant pays like a private client. Plan managed is the only one where a commercial third party holds the money and sets the terms.

Each plan manager is its own debtor with its own remittance layout, its own claim cycle and its own responsiveness. A practice seeing participants across a dozen plan managers is carrying a dozen accounts receivable relationships, not one funder.

Where the days actually go

The hops between an invoice and a plan-managed deposit, timed separately21
HopWho is holding itTypical time
Invoice reaches the plan managerThe practiceDay of the claim run
Budget and price limit checkThe plan managerBefore the next of two daily runs
Claim lodged with the agencyThe plan managerTwice a day at NDSP
Funds released to the plan managerThe agencyTwo to three days at most
Payment run to the practiceThe plan managerOne to two days, bank dependent

Timing a plan-managed payment as one number hides which hop is slow. NDSP describes its own cycle as most payments landing within three to five days, and up to six when the agency is slower to release. Split that way, a payment sitting at eight days is a question for the plan manager, and a whole batch sitting at eight days is a question for the agency.

Why the quoted timings disagree

Three ranges are in print for the same rail, and they do not contradict each other so much as measure different things.

  • Three to five days is one large plan manager describing its own processing, measured from the day it receives the invoice.
  • Several days to a couple of weeks is a bookkeeping practice describing the market it sees across many providers, which includes the slow half.
  • Commercial terms of 14, 30 or 45 days from invoice date are what some plan managers put in writing, and terms are a ceiling rather than a habit.

None of the three is a published service standard, so none belongs in a cash flow forecast as a rule. What does belong there is the practice's own aged receivables by plan manager, which is a thing the ledger can answer once each plan manager is a separate contact.

One lump, many claim lines

The deposit is one bank line. Behind it sits a remittance that can run to five hundred rows or more, because a row is a claim line rather than an invoice. One invoice for a fortnight of support can carry a row for each support item on each date.

Xero records payments against invoices rather than against a remittance, so the run has to be taken apart before it can be posted. The remittance total is the check: approved lines less rejected negatives has to equal the money that arrived before anything is posted against an invoice.

The claim reference is not the invoice number

This is the part that breaks automated matching. A plan manager keys its remittance on its own claim reference, and that reference is not the number on the invoice in Xero.

Lines are keyed by a claim reference, often with a prefix, that does not tie directly to the invoice number in your Xero ledger.3

It is not one convention with one fix either. Each plan manager writes its own prefix, its own column order and its own header names, so a practice with several plan managers needs a column mapping per plan manager rather than one parser. That is a per-payer setting, and it is the reason a tool that matches one plan manager cleanly can miss the next one.

Negatives and short pays are two different problems

A run can arrive under the invoiced total two ways, and the ledger treats them differently.

  1. A rejected line comes back as a negative on a later remittance, netted against that run. The claim was not valid as lodged, so it is corrected and reclaimed. The invoice stays open, and nothing is written off.
  2. A short pay is an approved payment at a lower amount, because the remaining budget or the price limit was lower than the invoice. The claim is settled. What is left is a decision about the shortfall, and the templates give it a home rather than folding it into income.

Rejections are not exceptional events to be handled when noticed; they are a standing queue that someone owns weekly, exactly like bounced super contributions.8

Both patterns are in the canonical templates as separate components of the same rail, which is what lets a deposit be posted without deciding on the spot whether a gap is a rejection or a shortfall.

What the canonical templates post

The plan manager rail, component by component, in the templates that model it1011
TemplateComponentWhere it posts
allied-health-by-funding-sourceGross paid103 Plan manager clearing, at BAS Excluded
allied-health-by-funding-sourceShort paymentsNeeds review: Component short_payments needs a fixed account and tax type; original-invoice matching is not supported yet.
allied-health-by-funding-sourceRejected linesNeeds review: Component rejected_lines needs a fixed account and tax type; original-invoice matching is not supported yet.
ndis-provider-plan-managedGross paid101 Plan manager clearing, at BAS Excluded
ndis-provider-plan-managedShort paymentsNeeds review: Component short_payments needs a fixed account and tax type; original-invoice matching is not supported yet.
ndis-provider-plan-managedRejected linesNeeds review: Component rejected_lines needs a fixed account and tax type; original-invoice matching is not supported yet.

The gross payment lands in a plan manager clearing account, which is a bank type account in Xero. The clearing balance is money the plan manager has approved and the bank has not yet delivered, so it returns to nil once each run lands. A balance that will not clear is a claim receipted and not yet paid, or paid and not yet matched.

Deposit coded to income beside Deposit coded through the mapThe same five accounts read twice: a plan manager deposit coded straight to income, and the same deposit coded through a plan manager clearing account with short payments split out.Deposit codedto incomeDeposit codedthrough themapBank, planmanager depositOne incomelineMatchedtransfer101 PlanmanagerclearingNot usedNil per run403 NDISplan-managed,listed supportsOne lumpOne line perclaim605 Fundershortfalls andwrite-offsNot separatedShort paysonlyAccountsreceivableLeft openClosed onpaid date
Plate 2What a clearing account changes about the accounts around a plan-managed deposit, read in the NDIS plan-managed template.

One caution about batch size, because the two tools that write about it disagree. ToTheCent describes a Xero cap of 50 invoices per batch, which would split a 500 line run into many batches. RemitClear describes a cap of 200. Xero Central served no page when this was checked, so treat the cap as something to test in the practice's own file rather than a number to plan around.

GST: the plan manager pays, the participant receives

Being paid by a plan manager does not change who the supply is made to. The supports are supplied to the participant, so the same tests decide the tax rate as for any other management type, and the four conditions of s38-38 are set out on the self managed page.

Under normal circumstances, supplies of NDIS supports are made to the participant, not to the plan manager.5

The written agreement the third condition asks for can still be held with the plan manager. The tax office names a plan management provider registered with the agency among the people who can enter that agreement on the participant's behalf, and accepts a combination of documents as the written evidence, including letters between the parties and the receipts or invoices the practice issues, in electronic form or on paper.

Plan-managed clinical revenue, as each canonical template posts it101112
TemplateRevenue accountTax rate
allied-health-by-funding-source405 Clinical services, NDIS plan-managedGST Free Income
ndis-provider-plan-managed403 NDIS plan-managed, listed supportsGST Free Income
psychology-with-booking-deposits403 Clinical services, NDIS plan-managedGST Free Income

The three templates agree on the tax rate and put that revenue in two different accounts, which is worth knowing before a chart of accounts is copied from one practice to another. The tax rate is the part that follows the service: a support the agency funds that is not itself one of the tax office's listed health services has to satisfy all four s38-38 conditions, the supports determination included, and the plan-managed template posts it as taxable on its own row rather than under the funder.

What Ledger Map does with it

Ledger Map holds one standing map for the practice, approved once. A plan-managed line resolves to its account and tax rate through that map. Each remittance run is posted as one balanced document set against the plan manager clearing account, so the bank feed is left with one exact match rather than a pile of part payments to hunt through.

Where the map cannot resolve a line, it becomes a question with the options laid out, rather than a posting nobody chose. Nothing on this page is a treatment the product picked: the accounts and the tax rates come from the canonical template the practice starts from, and the practice approves the map before any invoice syncs. You can see the shape of that in how it works.

Questions

  • How long does a plan manager take to pay?

    One large plan manager describes most payments as landing within three to five days of receiving the invoice, and up to six when the agency is slower to release funds. A bookkeeping practice looking across the market puts plan-managed collection at several days to a couple of weeks, and written terms of 14, 30 or 45 days from invoice date exist. Treat the range as the market and track your own by plan manager.

  • Do I invoice the plan manager or the agency?

    The plan manager. It holds the participant's funds, checks the invoice against the plan budget and the price limits, then claims from the agency itself. The invoice still carries the participant number, the support item codes and the service dates, because the plan manager needs them to lodge the claim.

  • Why does the remittance not match my invoice numbers?

    Because a plan manager keys its lines on its own claim reference, often with a prefix, and that reference does not tie to the invoice number in Xero. Each plan manager writes its own format, so matching is a per-payer column mapping rather than one rule for the rail.

  • Why is the deposit less than the invoices the remittance lists?

    Either rejected lines came back as negatives netted against that run, or lines were paid short at the remaining budget or the price limit. A rejection is corrected and reclaimed with the invoice left open. A short pay is settled, and what remains is a shortfall the templates keep in its own account.

  • Is plan-managed NDIS work GST free?

    The plan manager pays, but the tax office says the supply is still made to the participant, so the same four s38-38 conditions decide it. All three canonical templates post plan-managed clinical work as GST free income. A support the agency funds that is not a listed health service has to satisfy all four of those conditions, the supports determination included, and the template posts it as taxable on its own row, so the treatment follows the service rather than the payer.

Sources

Open questions

  • Xero's batch payment cap could not be confirmed first hand. ToTheCent states 50 invoices per batch and RemitClear states 200, and central.xero.com served no content for its batch payment articles on 2 Sep 2026 and again on 3 Sep 2026, so the page states the disagreement rather than a number.
  • The bank narration on a plan manager deposit is not confirmed by any primary source. The research corpus records descriptor strings as unverified and says only that the deposit carries the plan manager's business name, so the matcher learns the pattern from the practice's own feed.
  • The end to end timings come from a plan manager describing itself, a bookkeeping practice describing the market, and a billing guide quoting commercial terms. None is a published service standard, and the three do not agree.
  • Whether a given support is covered by the supports determination is a judgement about that support, and the tax office's own example of a therapy that fails the fourth condition in a clinic and passes it in a residential setting shows how fine the line is. The page states the test and the templates' default rather than a verdict on any one support item.
  1. NDIS plan managed billing guide

    Teiro. Retrieved 29 Aug 2026.

    secondary

  2. How we pay your providers

    NDSP Plan Managers. Retrieved 29 Aug 2026.

    secondary

  3. Reconcile NDIS plan manager remittances in Xero

    ToTheCent. Retrieved 29 Aug 2026.

    secondary

  4. GST and health

    Australian Taxation Office. Retrieved 29 Aug 2026. Source updated 13 Jun 2024.

    primary

  5. GST and health: National Disability Insurance Scheme

    Australian Taxation Office. Retrieved 3 Sep 2026. Source updated 13 Jun 2024.

    primary

  6. GST and health: recipient of the supply

    Australian Taxation Office. Retrieved 3 Sep 2026. Source updated 12 Jun 2024.

    primary

  7. GST and health: other health services

    Australian Taxation Office. Retrieved 3 Sep 2026. Source updated 12 Jun 2024.

    primary

  8. NDIS provider bookkeeping

    ScaleSuite. Retrieved 2 Sep 2026. Source updated Jul 2026.

    secondary

  9. The Xero 200 invoice batch payment limit

    RemitClear. Retrieved 2 Sep 2026. Source updated 23 Apr 2026.

    secondary

  10. NDIS provider, plan managed, the canonical template

    Ledger Map. Retrieved 2 Sep 2026.

    primary

  11. Allied health by funding source, the canonical template

    Ledger Map. Retrieved 2 Sep 2026.

    primary

  12. Psychology with booking deposits, the canonical template

    Ledger Map. Retrieved 2 Sep 2026.

    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.