Tuesday morning brings six emails from four plan managers. Two carry the list of paid invoices in the body of the email with nothing attached. One is a multi-page PDF that prints the plan manager's own invoice number beside yours. One is a single line saying one invoice has been paid. The bank feed shows four credits, none of them equal to any one email. This is the plan-managed side of an NDIS ledger, and it arrives in pieces.
This guide is for Australian NDIS providers with plan-managed participants, support work, allied health, gardening, cleaning and assistive technology among them, and for the bookkeepers who look after their Xero files. The NDIA's own fortnightly advice is a different document with different problems, covered in the guide to processing NDIS remittances in Xero. This one is about the money that comes through plan managers.
How plan-managed payments reach you
Under plan management you invoice the plan manager, not the participant and not the NDIA. The plan manager checks the invoice against the participant's plan and the NDIS Pricing Arrangements, submits a payment request to the NDIA on the participant's behalf, and pays you once the NDIA has paid them. The NDIA's guidance to plan managers is to pay providers within two business days of receiving the money. A valid invoice is therefore usually settled within a couple of weeks, on that plan manager's own payment day.
Every plan manager pays on its own cycle, so a provider with thirty plan managers on its ledger receives thirty streams of small remittances rather than one large run. Many of those plan managers run on the same handful of software platforms, so the layouts repeat across senders. Once you can read one platform's email you can read every plan manager that uses it.
Participants also move, between plan managers at a plan review and between agency-managed and plan-managed funding. An invoice raised to one plan manager is sometimes paid by another, and one you expected in the NDIA run arrives from a plan manager instead.
The four shapes of plan manager remittance
The table in the email body. The most common shape. An automated email lists the invoices paid in that run, with your invoice number, the participant and the amount, and nothing attached. Some platforms put the table only in the formatted version of the email and leave the plain-text version as a heading and a total, so a copy forwarded from the wrong mail client can arrive with the table missing. Keep the original.
The payment-run PDF. Several pages, one row per invoice or per service line, subtotalled by participant, with a total that should equal one bank credit. These often carry the plan manager's own internal invoice number in a column next to yours, and a long number wraps across two lines when the column is narrow.
The single-invoice notice. One email per invoice, sent when that invoice clears. Ten invoices paid on the same day means ten emails, and the money can arrive as one credit or as ten.
The portal export. A CSV of payments over a date range, downloaded from the plan manager's provider portal. It is usually the only place a claim-level breakdown is available.
Whichever shape arrives, the bank credit does not always equal the document. A plan manager can batch two runs into one transfer, or split one run across two transfers when a payment fails and is re-sent.
What makes them different from an NDIA advice
An NDIA advice is keyed to claim lines and participant numbers, and the work is bridging claims to invoices. A plan manager remittance is keyed to your invoice number, which sounds easier and mostly is. The difficulties are different ones.
- Your number, altered. Their system stores whatever was read from your invoice, so a prefix is dropped, a hyphen vanishes, or their own reference sits beside yours and gets picked up in its place. If you have ever changed numbering series, expect invoices on the old series to keep being paid for months after the change.
- Fragmentation, not size. The problem is rarely a three-hundred-line document. It is thirty documents of ten lines each, from a dozen payers on a dozen cycles. An allied health practice paid by a few dozen plan managers can see a dozen remittance emails a day; the figure is illustrative, the shape is typical.
- Short payments the plan caused. A plan manager pays what the plan will fund. The budget in that support category is exhausted, the unit price is above the Pricing Arrangements limit, or a service date falls before the plan started. The accepted amount is paid and the rest is left with you to query.
- Rounding. Unit price multiplied by quantity in a claims portal can land a cent away from the same sum on your invoice. A cent out is not a short payment, and it should not stall a reconciliation.
Setting Xero up for plan-managed participants
Plan manager remittances reward preparation at invoicing time. Four habits do most of the work.
- One contact per plan manager, not per participant. The plan manager is the debtor and the payer, so it is the contact. The participant is identified on the invoice, by name and NDIS number in the Reference field or the line description, which is what the plan manager validates against and what you search on later.
- Invoice numbers that survive their systems. One prefix, one series, no reliance on leading zeros, and no restart when the financial year turns. The number has to be recognisable after it has been retyped or truncated.
- Send each invoice the way that plan manager asks. Most want one invoice per participant, with the NDIS number, the support item number, the service dates and the quantity on every line, sent to their invoicing address rather than a person's inbox. Invoices that fail validation are the ones that come back short or late.
- One place for the remittances. A mailbox rule that forwards every payment notification to a single address, a shared reconciliation inbox or the forwarding address of the tool you use. The day's emails then sit in one queue rather than with whoever happened to be copied.
Short payments, rounding, reversals and double payments
Short payments. Allocate the cash as a part-payment and leave the balance open, so the invoice stays on the aged receivables report, then query the plan manager quoting their reference. Do not credit the balance until the plan manager confirms the plan will not fund it; a budget exhausted in one period is sometimes topped up at the next review.
Rounding. For a cent either way, match the invoice in Find & Match and add a minor adjustment for the difference, coded to a rounding account, rather than leaving a one-cent invoice open for a year.
Reversals. A plan manager that paid an invoice the NDIA later declined can net the amount off a later run as a negative line. Match the negative line to the original invoice with a credit note, so the current run still ties to its bank credit, and re-invoice or write off once the dispute is settled.
Double payments. The same invoice paid by two plan managers after a participant switched, or paid twice by one, is recorded as an overpayment on the paying contact with the invoice number in the reference. Refund it or hold it against the next invoice. The insurance-payer guide walks through the Xero steps, and they are identical here.
Reconciling the day's emails in Xero
Work by plan manager, not by arrival order. Gather the day's emails from one payer and open that payer's bank credit in the reconciliation screen. Use Find & Match to tick off each invoice on the remittance, searching by your invoice number and checking the amount as you go. Where the credit covers two runs, work both documents against it. Where one run was split across two credits, match the invoices the first credit covers and leave the rest for the second. The general routine is the one-payment-many-invoices reconciliation in Xero, repeated once per payer.
Providers who route the NDIA run through a clearing account can do the same with plan manager credits. Code each credit to the clearing account on the day it lands and allocate invoices out of it as the remittances are worked; the clearing-account section of the NDIS guide covers the setup. The residual balance at the end of the day is the list of invoices still to find.
Where RemitClear fits
RemitClear reads the remittance in whatever form the plan manager sends it: the table in the email body, the payment-run PDF, the portal CSV or a forwarded email. Every line is matched against your open invoices in Xero. Matching handles exact, partial and prefix-based invoice numbers, so a dropped prefix or an altered number still finds its invoice. The review screen shows which invoice each line matched before anything posts. Every plan manager lands in the same workspace, so the routine is the same whether four payers or forty send you money in a week.
- A line referencing an invoice already paid in Xero is flagged Already Paid, with a link through to it, and is left out of the allocation. That is how a second plan manager's payment after a switch gets caught.
- A short-paid invoice is allocated as a part-payment, left open for the balance and flagged for review. It waits for a person, because deciding what a plan manager's short payment means is a business judgement.
- A line a cent out from the invoice is matched and the difference is shown, so rounding is visible without holding up the run.
- Each payment posts to the Xero bank or clearing account you nominate, so a clearing account clears down as invoices are matched rather than being worked by hand.
Forwarding the plan manager's email as it arrives is the usual setup, through the email remittance capture inbox. The NDIS remittance reconciliation page covers the workflow end to end.
Summary
Plan manager remittances are keyed to your invoice number, arrive in four shapes from many payers on many cycles, and pay what the plan will fund rather than what you billed. Make the plan manager the contact and the participant the reference, keep invoice numbers stable, route every notification to one queue, and reconcile by payer rather than by arrival. Allocate short payments as part-payments, adjust rounding rather than chasing it, and record a second payment on the same invoice as an overpayment. The step-by-step guide to reconciling a remittance advice in Xero covers the underlying mechanics.
