NDIS Integrity Portal and SDA: An evidence-upload checklist

An evidence portal changes the operating rhythm because the request may arrive before payment is made. A provider that waits until the request appears is already behind if its claim facts live across a finance export, a tenancy file, an owner email thread, a maintenance note and a portal screenshot.

SDA claims have more dependencies than a generic service line. A defensible claim may need to connect the participant, NDIS number, enrolled dwelling, address and postcode, support item, claim type, claim dates, price source, funding management, service agreement, occupancy state, my provider relationship, vacancy evidence and correction history.

The better control is to prepare the evidence pack as part of claim readiness. The upload channel can change over time, but the evidence spine should remain stable inside the SDA operating record.

The September integrity release describes stronger controls, pre-payment checks, manual reviews and suspicious-claim detection. That does not mean every evidence request is a fraud allegation. Providers should use neutral internal states such as evidence requested, pre-payment check, manual review, duplicate check, pricing mismatch, relationship check, plan-date check, correction required or claim not supported.

Neutral language helps staff act without overreacting. A wrong postcode, stale price, missing service agreement date or old my provider state may be an administrative defect. A pattern of claiming for non-enrolled dwellings, unsupported dates, fabricated documents or knowingly duplicated claims may need escalation. The record should make the distinction visible.

This also protects participants. Evidence upload work often includes sensitive identifiers, plan details, addresses and private correspondence. Keep the response pathway controlled so the evidence goes to the NDIA channel that requested it, not into owner packs, broad team chats or informal referral notes.

Use this checklist before submitting high-value, corrected, older, vacancy, first-claim, plan-transition or unusual SDA claims, and whenever an Integrity Portal, pre-payment check or manual review request arrives.

NDIS record keeping guidance says providers need complete and accurate records of supports delivered, and lists invoices, support logs, rosters, case notes and service agreements as examples. It also says SDA invoices need address and postcode details, support item, claim type and total amount on top of minimum identifying information.

For SDA, that means the evidence pack should not depend on someone remembering where a PDF was saved. Store searchable fields for participant identifier, dwelling address, support dates, support item, quantity, amount, claim type, agreement version, invoice number, funding pathway, price source, claim batch and final outcome.

Searchability matters during pre-payment checks because a response deadline can arrive while finance is also running ordinary claims. If evidence has to be rebuilt manually, the provider increases the chance of sending too much, sending the wrong version or missing a simple correction.

The NDIS also announced a multi-system outage for 26 September 2026 affecting my NDIS and myplace portals, the Integrity Portal and several gateway services. Even when outages are routine and temporary, SDA providers should treat portal availability as a claim-run dependency.

Before a planned outage, export or record the claim states the team will need: pending uploads, evidence requests, payment enquiries, relationship checks, dwelling enrolment tasks, rejected rows and manual review due dates. After the outage, reconcile what changed rather than assuming every item is still in the same state.

This is not about building a shadow portal. It is about keeping enough internal state to avoid missing an evidence response, resubmitting a duplicate, promising owner income too early or losing a support-provider handoff because a portal task was unavailable for a day.

Owner reports should reflect payment certainty, not evidence detail. Suitable states include claim submitted, evidence requested, pre-payment check, response submitted, payment pending, claim paid, claim rejected, correction pending, repayment under assessment or owner forecast on hold.

Do not include the participant's NDIS number, plan screenshots, health details, nominee correspondence, fraud-control language or Integrity Portal attachments in owner-facing material unless an existing permission model clearly allows the disclosure. Most owner questions can be answered with property-level cashflow status and action ownership.

When a claim remains unpaid, separate the commercial effect from the private reason. For example: claim under NDIA evidence review is safer than a narrative about participant records, support disputes or portal identity checks.

StepFree SDA can help providers keep claim evidence, participant-dwelling records, service agreements, provider relationships, payment batches, review responses, corrections and owner-safe reporting connected in one SDA-specific workflow.

The value is not replacing the NDIA portal. It is having a clean operating record before the portal request arrives, so finance, operations, compliance and owner-reporting teams can respond from the same facts.