Your software checks the invoice. TrueBlue Scout checks who sent it.

It's payment day. Your software says the price is right and the budget is there. It won't always tell you the provider was banned the week the support was delivered.

That's not your software doing a bad job. It was built for a different question.

What your software is built for

Plan management and invoice software checks the invoice: the participant's plan, the price limits, the budget, the claim. Those checks need the participant's details, so they belong in your own system.

The gap: who sent the invoice, on the day

The other question is about the provider, and the answers sit in three public registers. The Invoice check reads them for every row of your file, as they were on that row's service date:

1. ABN active? An ABN can be cancelled while invoices keep coming. 619 registered providers' ABNs showed as cancelled on 26 October 2026.
2. The name on record? Is the name on the invoice one of the names held for that ABN?
3. GST right? An invoice that charges GST should come from an ABN registered for GST.
4. Registered, if it needs to be? Is the NDIS registration in force, or did it end before the service date?
5. Any compliance action in force that day? A banning order, a revoked registration, a notice. 703 banning orders were in force on 27 October 2026.
6. The same invoice twice? Repeats in the same file are shown.

Why the date matters

Records change. A check you did in March tells you about March. If a support was delivered on 3 October and a banning order took effect on 1 October, today's search and the service date can give different answers. The Invoice check uses the date on each row, so you see the record as it stood when the support was delivered.

Three steps, one cup of tea

• Drop in this week's invoices. An export from your software or the NDIA bulk payment request file. It's read on your device: only the providers' ABNs are sent, never NDIS numbers, amounts or anything about a participant.
• Each row, on its date. Matched against the Australian Business Register, the NDIS provider register and the NDIS Commission's compliance actions.
• See what to ask about. Rows that match, rows to take a look at, each with its source and date, and a CSV to keep.

Try the Invoice check, free for a few providers. Solo covers payment runs of up to 300 providers, Team up to 3,000, and both save every check to a dated Check log for your auditor or the plan management panel.

Every payment run, without lifting a finger: the API

For big payment runs, the TrueBlue Scout API lets your software ask before it pays:

• Send ABNs or invoice rows with service dates; up to 3,000 providers in one call.
• Get back the same answers as the website (matches, take a look, or not enough to compare), each with its source and date.
• The rows you send aren't stored.

Team includes the API for your own list. NDIS software that checks for many businesses uses the API plans, priced by checks a month.

Plug it in once. We keep watch. How the API works.

Questions people ask

Does it replace my software? No. It sits beside it. Your software checks the invoice; TrueBlue Scout checks who sent it.

Does "take a look" mean don't pay? No. It means the invoice and a record say different things. A business may trade under another name or have a new ABN. Ask the provider, kindly. Something that doesn't match is a reason to ask, not proof of anything.

Is a provider with nothing published fine to pay? Nothing published means no compliance action published as of the date shown. It isn't a recommendation. Six checks before you pay covers the rest.

Paste it once. We keep watch.