Processing NDIS Remittances in Xero: A Guide for Australian Providers

NDIS remittances look different from every other kind of remittance an Australian accounts team will see. The line items are claims, not invoices. The references are claim IDs and participant numbers, not your invoice numbers. And the payment you receive is almost never a clean match for what you billed. This guide explains how NDIS payments actually work, what is on a remittance, where the reconciliation pain comes from, and how providers handle it inside Xero.

It is aimed at Australian NDIS providers and the bookkeepers who support them, written to be useful whether you are setting up your first participant or managing a practice with dozens of NDIS clients. This is the "how the system works" piece. If you already know the mechanics and just want to see how automation handles it, skip ahead to the NDIS remittance matching page.

How NDIS payments actually reach providers

There are three funding management types in the NDIS, and each one produces a different kind of remittance:

• Agency-managed (the NDIA pays you directly). You claim through the NDIA portal (PRODA), and the NDIA sends a bulk payment with an accompanying remittance listing every claim line. Remittances are generated by the NDIA system and arrive as CSV or PDF.
• Plan-managed (a plan manager pays you on behalf of the participant). You invoice the plan manager, they claim from the NDIA on the participant's behalf, and they remit to you once they have been paid. Plan managers include MyIntegra, Plan Partners, Leap in!, and many others. Each plan manager has its own remittance format.
• Self-managed (the participant or their nominee pays you directly). You invoice the participant, they claim through the NDIA, and they pay you. Remittances here are often minimal: sometimes just a proof of bank transfer, sometimes nothing at all.

A single provider can have participants across all three funding types simultaneously. The AR ledger in Xero has to handle all three, which is part of why NDIS reconciliation ends up complicated.

What is on an NDIA or plan manager remittance

A typical remittance contains one row per claim line, not per invoice. That distinction matters more than it sounds. A single invoice you raised for Jane Smith's fortnightly support might correspond to five, ten, or twenty claim lines on the remittance, one per service date or one per support item delivered.

Each claim line typically includes:

• Participant NDIS number (the 9-digit reference).
• Support item number (the code for the type of service, e.g. 04_104_0125_6_1 for "Access Community Social and Rec Activities").
• Service date or date range.
• Quantity (usually hours or units).
• Unit price, from the NDIA price guide.
• Claimed amount and amount paid, which may differ if the claim was partially approved.
• Status, indicating whether the claim was paid, rejected, or cancelled.

The total at the bottom of the remittance is the sum of paid amounts and should match the lump-sum payment on your bank feed. If it does not, there is usually a bank fee, a netted-off adjustment from a previous batch, or a split payment that needs investigation.

Why NDIS remittances are unusually hard to reconcile

Reconciling a B2B remittance in Xero is already manual; NDIS adds four structural complications on top.

Granularity mismatch between claims and invoices

Your Xero ledger is organised by invoice. The remittance is organised by claim. You will rarely have a clean 1:1 mapping between the two. The tighter your invoice structure mirrors the service cycle (one invoice per participant per billing period), the easier the reconciliation. The looser it is (one invoice per participant per month with many services inside), the more Excel work is needed to tie the lines back.

Long and unfamiliar references

Participant numbers and claim IDs do not appear on your Xero invoices by default. If your invoice template references only an internal invoice number, you cannot search for a remittance line using the participant number the NDIA or plan manager used. Teams that add participant NDIS numbers to the invoice description or to a tracking field reconcile significantly faster.

Claim adjustments from previous batches

Rejected or cancelled claims can appear on a later remittance as negative lines. A claim you submitted three weeks ago, allocated to an invoice two remittances ago, may be reversed on today's remittance. That means the current bank credit is net of the reversal, and you need to either raise a credit note against the original invoice or reverse the earlier payment allocation.

High line counts

A fortnightly NDIA remittance for a mid-sized provider commonly runs to 100 to 300 lines across 30 to 80 participants. Plan manager remittances tend to be smaller individually but arrive from multiple plan managers on different cycles, producing a steady stream of reconciliation work rather than a single large batch.

The manual Xero workflow, start to finish

1. Invoice structure first

Before you can reconcile anything, your invoicing approach has to support it. Most established NDIS providers settle on one of two patterns:

• One invoice per participant per billing period, with service lines inside. Easiest for agency-managed claims because participants map cleanly to remittance groupings.
• One invoice per participant per support item per period, so each invoice covers a single support item type. Higher invoice volume, but cleaner when support items are priced very differently.

Either is fine, but pick one and stay consistent. Changing invoice structure mid-year makes historical reconciliation much harder.

2. Group remittance lines by participant

When a remittance arrives, the first pass is usually in Excel: sort by participant number, sum the paid amounts, produce a participant-level total. Each total is what you need to find in Xero.

3. Match participant totals to Xero invoices

For each participant total, find the corresponding open invoice in Xero. Verify the amount matches (or note the difference), and use Find and Match on the bank reconciliation screen to allocate.

4. Handle claim reversals

For every negative line on the remittance:

• Identify the invoice the reversed claim was originally allocated to.
• Raise a credit note against that invoice (or reverse the payment and re-raise).
• Include the credit note in the current reconciliation so the bank total still balances.

5. Reconcile the bank line

When your participant-level payments plus any credit notes equal the exact bank credit, Xero lets you reconcile. If you are off by a dollar, start with the most recent reversal; it is almost always where the arithmetic went wrong.

Using an NDIS clearing account in Xero

Many providers do not reconcile the NDIA bulk payment straight against participant invoices. They route it through a dedicated clearing account, sometimes called a holding or suspense account, in Xero. The bulk credit is posted to the clearing account the day it lands, and individual participant payments are allocated out of that account afterwards, as each remittance line is matched.

The point of the clearing account is to separate two things that happen on different timelines. The bank line can be reconciled the moment the money arrives, against a single transfer into the clearing account, so the bank feed is never held up. The slower work, allocating each claim line to the right invoice, then happens against the clearing account without a half-reconciled bank statement hanging over it.

In practice the workflow runs like this:

• Create a clearing account in the chart of accounts. Providers who want to use Xero's reconciliation screen against it set it up as a bank-type account.
• When an NDIA or plan manager payment lands, code the bank line to the clearing account, and reconcile the bank statement straight away.
• Work through the remittance, allocating each participant payment out of the clearing account against the relevant open invoice.
• Once every line on the remittance has been allocated, the clearing account returns to nil for that batch.

A clearing account does not remove the matching work, it quarantines it from the bank feed. The line-by-line allocation, the reversals, the granularity mismatch between claims and invoices, all of that still has to happen. That is the part automation removes: RemitClear posts each matched payment to whichever Xero account you nominate, a clearing account included, so the account clears down as invoices are allocated rather than being worked by hand. The NDIS remittance reconciliation page covers how that runs end to end.

Common mistakes providers make

• Processing out of order. Remittances reference each other through adjustments. Processing them chronologically is much easier than processing them in the order they arrive.
• Ignoring small discrepancies. A one-cent rounding difference is fine to write off; a ten-dollar discrepancy is almost always a misallocation you will pay for at month-end. Treat every unexplained gap as a reconciliation issue until proven otherwise.
• Not recording participant numbers on invoices. The single highest-leverage change for anyone doing manual NDIS reconciliation. It turns name-based searches into number-based searches and cuts reconciliation time significantly.
• Leaving rejected claims unreconciled. Rejected claims do not disappear, they come back as reversals. If you do not track them, you will not recognise the reversal when it lands.

When to stop doing it manually

The honest answer depends on volume and on what your time is worth. Rough signals that the manual process is costing more than it needs to:

• You or your staff spend more than four hours a week on remittance reconciliation.
• You are paying a bookkeeper more than A$4,000 a month for NDIS AR work.
• Your month-end routinely runs long because remittances are still being reconciled.
• Staff who do the reconciliation describe it as the worst part of their job.

If more than one of these is true, the cost of automation has almost certainly already crossed the threshold of being worth it. For a product-side view of what that looks like in practice (tested formats, batch splitting for 200+ line remittances, integration into Xero), see the NDIS remittance matching page.

Summary

NDIS reconciliation in Xero is not really a reconciliation problem; it is a structural mismatch problem. Claims and invoices are the same data described at different levels, and the work is in bridging them. The providers who find it manageable share a few habits: they invoice at a granularity close to the claim structure, they tag every invoice with the participant NDIS number, they process remittances in chronological order, and they treat every small discrepancy as a reconciliation issue until proven otherwise.

For the broader Xero workflow that sits underneath NDIS-specific reconciliation, see our step-by-step guide to reconciling remittance advices in Xero.