NDIS fraud reporting and SDA: A signal-register checklist

The NDIS fraud and non-compliance page says the Agency is trying to make it easier to get it right and harder to get it wrong. It also describes improvements such as more claim-supporting information, ABNs and evidence, a fraud tip-off form, manual reviews for plan manager payments and stronger portal identity controls. That is a clear signal for SDA teams: integrity work needs to be built into ordinary workflow, not left until a payment review or complaint arrives.

SDA has particular exposure because the claim does not stand alone. A single payment line may depend on an enrolled dwelling address, a design category, a building type, participant plan evidence, service agreement terms, provider relationship status, move-in and move-out dates, vacancy handling, RRC records and owner reporting. If those facts live in separate inboxes, the provider may struggle to distinguish an honest data error from a serious concern.

A signal register gives teams a middle step before escalation. It lets finance record an unusual claim pattern, operations record a disputed move-in date, intake record an authority concern, compliance record a conflict issue and leadership see whether the matter is an error, a privacy issue, a complaint, suspected non-compliance or a potential fraud report.

NDIS non-compliance guidance separates errors, misuse, conflict of interest and dishonest behaviour. That distinction matters in SDA. A wrong support date, duplicate invoice number or outdated postcode may be a fixable mistake. A pattern of claiming before move-in, claiming for a non-enrolled dwelling, fabricating evidence, hiding a related-party referral payment or charging outside agreed terms may need a different level of response.

The register should avoid loaded labels at the first sign of a mismatch. Use neutral states such as error under review, evidence mismatch, participant dispute, authority unclear, conflict disclosure required, claim hold, privacy risk, complaint pathway, suspected misuse or suspected dishonest conduct. The language matters because staff need to act quickly without defaming a person, exposing private information or collapsing ordinary correction work into a fraud allegation.

This also protects participants. A resident, nominee or family member may raise a concern because they do not recognise a claim, disagree with a date, believe a service agreement was not explained, or feel pressured by a provider relationship. Those concerns should be recorded respectfully, linked to consent and authority evidence, and triaged before the provider decides whether to correct a claim, pause future claims, make an enquiry, lodge a complaint or report suspected fraud.

Use this checklist when a team member spots a suspicious payment pattern, evidence mismatch, disputed service date, identity concern, conflict pressure, owner-income inconsistency, referral irregularity or participant allegation.

The NDIS guide to getting paid says providers must make sure claim details are accurate and in line with the participant's approved funding. It also says claims can be reviewed before or after payment and that providers may need to supply information within review timeframes. The debt recovery page says incorrect claiming can include supports that were not delivered, evidence that does not match the claim, made-up reports or invoices, repeated non-compliant claiming and criminal matters such as fraud.

For SDA teams, that means the signal register should be connected to claim ageing, batch status, correction actions and repayment decisions. Do not let a suspected issue sit as a private note while the same participant, dwelling or owner portfolio continues through ordinary claim runs. At the same time, do not stop every unrelated payment because one claim line is being reviewed.

Useful controls include affected-claim scoping, related-claim search, duplicate check, participant-date verification, enrolled-address verification, price-source versioning, my provider status check, RRC separation, owner statement hold and documented approval before resubmission. The point is to make the next claim decision visible and evidence-led.

Fraud and complaint handling can quickly pull sensitive material into too many places. NDIS information-sharing guidance treats details such as legal names, nominees, disability evidence, current supports, plan management type and bank account details as protected information. A signal register should therefore show enough for the accountable team to act, but not expose plan files, NDIS numbers, health details or family allegations to owners or unrelated staff.

Owner reporting needs an especially firm boundary. Owners may need to know that an income item is held, a claim is under review, a vacancy state is being checked, a repayment may affect a statement, or a compliance matter is unresolved. They usually do not need the participant's NDIS number, nominee dispute, fraud tip-off details, plan evidence, health information or the identity of a complainant.

Use owner-safe states such as claim evidence under review, payment held by NDIA, correction pending, repayment under assessment, vacancy date being verified or compliance matter restricted. That wording keeps commercial reporting factual without turning participant protection work into gossip or unsupported allegation.

StepFree SDA can help providers keep fraud and non-compliance signals connected to the operational records that matter: participant authority, service agreements, my provider status, enrolled dwellings, claim batches, invoices, RRC ledgers, owner statements, payment exceptions and audit evidence.

The goal is not to make every staff member an investigator. It is to give intake, tenancy, finance, compliance and owner-reporting teams a shared source of truth so suspicious signals are triaged consistently, ordinary errors are corrected quickly and serious concerns reach the right channel with the right evidence.