How to reconcile NDIS plan manager remittances in Xero: a provider guide

NDIS providers live a particular version of the reconciliation problem. A plan manager pays you one lump sum, and behind it sits a remittance with hundreds of claim lines: some paid in full, some paid in part, some rejected and shown as negatives, all referenced by claim IDs that do not match your invoice numbers. This guide is about turning that document into a balanced set of payments in Xero without spending the day on it.

Why NDIS remittances are harder than a normal payment run

A wholesale payment run is long but usually clean: each line pays one invoice in full. NDIS remittances break that assumption in three specific ways.

• Prefixed claim IDs: lines are keyed by a claim reference, often with a prefix, that does not tie directly to the invoice number in your Xero ledger.
• Negative rejected lines: rejected or clawed-back claims appear as negative amounts, so the remittance total is a net figure, not a simple sum of positives.
• Volume: a single run can carry 500 or more rows, well beyond the point where line-by-line matching is reasonable.

Set up your invoicing so claims can be found

The single biggest time saver happens before the remittance arrives: make your invoices matchable. If the claim reference the plan manager will pay against appears somewhere structured on your invoice, ideally the invoice number or the reference field, then matching a claim line back to an invoice becomes a lookup rather than a hunt.

• Put the NDIS participant or claim reference in the Xero invoice Reference field consistently.
• Keep one invoice per claimable item where practical, so a claim line maps to an invoice rather than a fraction of one.
• Use a naming convention you never deviate from, so last month's approach still works this month.

Reconciling the run, step by step

With invoices raised and the remittance in hand, the manual process looks like this. It works; it is just slow.

• Confirm the net deposit: sum the approved lines, subtract the rejected negatives, and check it equals the amount that hit your bank.
• Match approved lines to open invoices by claim reference, recording full payments and part-payments as they fall.
• Handle rejected lines deliberately: decide whether the invoice stays open for resubmission, gets credited, or is written off, and record that, do not just ignore the negative.
• Batch the settled invoices, respecting Xero's 50-invoice-per-batch cap, which means splitting a 500-line run into many batches.
• Reconcile the single bank deposit against the batches once every batch balances.

Where automation earns its place

The NDIS run is the clearest case for automating the matching. The rules are deterministic: claim references map to invoices, negatives net against the deposit, part-pays leave a balance. A tool can parse the prefixed IDs, net the rejected lines, propose the allocation across every open invoice, and flag the rejections for a human decision, then hand back a batch that already balances to the net deposit. The provider's job shrinks to reviewing the exceptions and approving.

Whether you automate or not, hold the same invariant NDIS itself implies: the approved lines minus the rejected lines must equal the money received, exactly, before you post. On a 500-line run that is not a target, it is the definition of done.