SDA claim evidence register: A payment integrity checklist

SDA claims can look simple because the support is recurring and linked to an enrolled dwelling. In practice, the evidence is scattered across service agreements, move-in records, enrolment details, pricing assumptions, my provider relationships, plan management status, invoices, vacancy notes, payment enquiries and owner reporting packs.

The NDIS troubleshooting guidance tells providers to check my provider status, funding management type, available budget, plan dates, pricing arrangements and duplicate claims before escalating a rejected claim. The payment request guidance also says claim validation can fail because of incorrect information such as date, price or fund management type. Those are not abstract errors for SDA. They are usually signs that the operating record, portal record and claim file no longer match.

A claim evidence register gives operations and finance one place to prove what was claimed, why it was claimable, what source was used, what changed, and how the outcome was resolved.

Build the register around claimable events rather than documents. For SDA, the event is normally a participant residing in an enrolled SDA dwelling for a defined period, or a specific vacancy payment scenario where current NDIS rules and guidance allow the provider to claim.

Each event should link the participant, dwelling, agreement, support item, pricing year, claim dates, occupancy or vacancy state, funding management type, portal pathway, submitted amount, payment status and evidence pack. If the participant moved in, moved out, changed plan management, changed provider relationship or had a plan variation, that event should have its own state rather than being hidden in notes.

This makes corrections easier. When a claim is rejected for dates, price, budget, duplicate status, ABN, bank setup or my provider status, the team can correct the source record before resubmitting instead of patching the upload file and leaving the same error available for next month.

The NDIS record keeping page says providers need complete and accurate records of supports delivered, including invoices, support logs, rosters, case notes and service agreements. It also lists minimum identifying information such as participant name, NDIS number, support dates, amount or quantity, and support type. For SDA invoices, it specifically includes the participant address and postcode, support item number, claim type, total amount and GST component if applicable.

For a provider portfolio, those fields should be structured. Do not rely on a PDF name to carry the meaning of a claim. Store the invoice number, support item, dwelling address, postcode, provider number, ABN, participant identifier, claim dates, rate source, claim quantity, claim type, funding pathway and source document links as searchable fields.

Add a confidence state for each item: verified, awaiting participant, awaiting plan manager, portal mismatch, pricing review, vacancy review, manual review, corrected, cancelled or repaid. This gives managers a live exception view without exposing participant-sensitive evidence in owner reports.

The NDIS troubleshooting page says a provider can cancel a mistaken payment request when it is pending or paid. It also says most claim payment errors can be corrected in the myplace provider portal, including administrative errors, duplicate claims, missing banking or ABN details, and unit prices above the maximum price.

That means SDA teams need a correction workflow, not just a rejection workflow. Record who detected the issue, whether money was paid, whether the claim was cancelled, whether a corrected claim was submitted, whether a repayment or recovery matter exists, and whether the owner statement needs adjustment. A payment correction should not be treated as a quiet finance note when it changes reported income or participant billing history.

The NDIA's debt and recovery information also makes clear that payment integrity work includes education, self-correction, compliance and investigations. For practical SDA operations, the safest posture is to self-correct cleanly, keep the evidence trail readable, and separate genuine administrative errors from patterns that need management review.

Manual payment reviews are already part of the NDIS payment environment. The NDIS page says a manual payment review checks claims before payment when there are concerns about how NDIS funds have been used. It also says payments stop while supporting evidence is received and assessed, and that providers may be asked to show that the claim is for an NDIS support, in line with the participant's plan, not a duplicate, delivered as claimed, and legally claimable.

A useful SDA register should be able to generate a review pack without rebuilding the claim history manually. That pack should include the service agreement, dwelling enrolment reference, pricing source, participant move-in or vacancy evidence, portal relationship status, invoice, claim line, correction history, related payment enquiries and communication log.

For monthly claim runs, review readiness should be checked before submission. For older claims, plan transitions and corrections, review readiness should be checked before escalation because the cashflow risk is higher if the claim is held.

The current Health, Disability and Ageing page on NDIS changes says payment reforms will improve visibility of claims and payments, and that providers will have time to develop filing and storage systems and strategies for new record requirements. It also says payment-system uplift began from July 2026 and will roll out by the end of 2030.

That is enough to justify practical preparation, but it is not a reason to invent final process details before official guidance is released. SDA providers should track reform assumptions separately from current claiming rules. Use fields such as official source URL, date checked, implementation date, affected support categories, system impact, evidence impact and operational owner.

This keeps the provider ready without creating unsupported claims to owners, participants or plan managers about exactly how future payment thresholds will operate.

StepFree SDA can help providers connect participant occupancy, enrolled dwellings, service agreements, claim schedules, payment outcomes, correction states, RRC records and owner-safe reporting. The goal is not to replace NDIS guidance or provider portals. It is to keep the operational evidence in one structured workflow so claim corrections and reviews do not depend on memory, inbox searches or disconnected spreadsheets.

For providers managing multiple SDA dwellings, a claim evidence register turns payment integrity from a reactive audit exercise into a monthly operating control.