Bookkeeping for NDIS Providers: Keeping Claims Reconciled and Records Audit-Ready

Running an NDIS provider organisation means operating at the intersection of care delivery, government funding compliance, and small business finance — all at once. The financial administration side of that equation — submitting payment requests through the NDIA’s myplace provider portal, reconciling remittances against submitted claims, coding GST correctly across different support categories, maintaining records that could withstand a Quality and Safeguards Commission audit — is genuinely complex, and it compounds as your participant base grows.

This guide covers two specific obligations that NDIS providers consistently struggle with: keeping NDIA claims accurately reconciled, and keeping financial records audit-ready. Neither is optional. Unreconciled claims mean revenue gaps that go unnoticed. Records that don’t support your payment claims create repayment obligations to the NDIA.

The NDIA payment cycle — and where reconciliation breaks down

When a registered NDIS provider submits a payment request through the NDIA’s myplace provider portal, the process moves through several steps before funds arrive in your account. Each step is an opportunity for a discrepancy to appear between what was claimed and what was paid — and without systematic reconciliation, those discrepancies accumulate silently.

The NDIA Claim Cycle

① Submit claim via myplace portal
② NDIA processes request
③ Remittance issued
④ Payment received in bank
⑤ Reconcile remittance against original claim

Step five — reconciling the remittance against the original claim — is where most providers fall behind. NDIA remittances identify each payment, but matching them back to the correct service bookings and portal submissions is a manual, transaction-by-transaction process. When it’s done regularly, it’s manageable. When it’s left to month-end or longer, the backlog grows quickly, and rejected or underpaid claims can go unnoticed for weeks.

Common reconciliation gaps include: payments received but not matched to a specific submission; claims submitted with no corresponding payment received and not followed up; remittance amounts differing from claimed amounts due to a price guide change or portal error; and duplicate submissions paid only once. Each of these is fixable — but only if you’re reviewing claim outcomes frequently enough to catch them promptly.

Free My Cloud bookkeeping team supporting NDIS providers

Support item numbers — the most common cause of rejected NDIA claims

The NDIS Pricing Arrangements and Price Limits assigns a support item number (SIN) to every claimable support. Payment requests submitted with an incorrect SIN, an amount exceeding the current price limit, or a claim date outside the participant’s active plan period are rejected by the NDIA system — which means the payment doesn’t arrive and the error has to be identified and resubmitted before revenue is recovered.

⚠ Common NDIA Claim Rejection Reasons

Each rejected claim is a revenue delay — and a record-keeping task

  • Incorrect support item number for the service type delivered
  • Amount exceeds the current NDIS price limit for that support
  • Claim date falls outside the participant’s current plan period
  • Duplicate claim for the same service booking already processed
  • Participant’s plan funds exhausted in that support category
  • Registered provider claiming for a support not in their registration scope

Keeping the support item register current — updating SINs when the NDIS Price Guide changes, typically annually in July — is a bookkeeping maintenance task that directly affects claim acceptance rates and cash flow predictability.

What “audit-ready” actually means under the NDIS framework

“Audit-ready” is used loosely. For NDIS providers it has a specific meaning tied to two oversight bodies: the NDIS Quality and Safeguards Commission, which can audit registered providers as part of its compliance function, and the NDIA’s Provider Payment Assurance Program, which reviews payment claims against service delivery records to confirm that claimed supports were actually delivered.

Both require a clear, documented link between four things: a support being delivered; a service agreement authorising that support for that participant; a payment request submitted to the NDIA or plan manager for that support; and a payment received matching that claim. When financial records don’t align with service delivery records — because timesheets, service notes, and invoices are held in separate systems that aren’t regularly reconciled — that chain of evidence breaks down.

NDIS Record-Keeping Requirements

  • Signed service agreements for each participant
  • Records of supports delivered — timesheets, service notes, attendance records
  • Invoices and payment records aligned to delivered supports
  • NDIA remittances matched to submitted payment requests
  • Accounts receivable records for plan-managed and self-managed participants
  • SCHADS payroll records for all support worker employees
  • All records retained for a minimum of 5 years

The five-year retention requirement is firm. Records that cannot be produced for an audited period create an automatic substantiation gap — and substantiation gaps can result in the NDIA requiring repayment of claims that cannot be verified against delivery records, regardless of whether the supports were actually provided.

Plan management types and their different reconciliation demands

How you submit claims and collect payment depends on each participant’s plan management type — and each type creates a different reconciliation task. NDIA-managed participants are the most straightforward from a claims perspective: you submit payment requests directly through the myplace portal and reconcile remittances from the NDIA. Plan-managed participants require you to invoice a third-party plan manager, then reconcile plan manager payments against issued invoices — payment timing and reference data varies significantly between plan managers. Self-managed participants pay you directly, creating an accounts receivable process and the need to follow up overdue invoices.

A provider with twenty participants spread across all three plan management types is running three parallel reconciliation processes simultaneously. Without participant-level income tracking — knowing exactly what was claimed, what was paid, and what is outstanding for each participant in each support category — aggregate income figures in the accounts are not sufficient to identify gaps.

SCHADS payroll records and your audit exposure

Most NDIS support workers are employed under the Social, Community, Home Care and Disability Services Industry Award 2010 (SCHADS Award). Processing payroll correctly under SCHADS — correct classifications, penalty rates for evenings, weekends and public holidays, broken shift allowances — is one obligation. Keeping the records that demonstrate you did it correctly is a separate, equally important one.

Fair Work can audit payroll records going back up to seven years. The records that need to be maintained and readily producible include: employment agreements with correct SCHADS Award classification; timesheets recording ordinary, overtime, and penalty hours by date; pay slips issued for every pay event; STP Phase 2 lodgements matching each payroll run; and superannuation contribution records. From 1 July 2026, Payday Super requires superannuation to be paid with every payroll cycle rather than quarterly — tightening the record-keeping requirement further. Our outsourced payroll service handles SCHADS Award processing and STP lodgement as a standard part of the engagement.

Free My Cloud team handling NDIS provider bookkeeping and reconciliation

Bringing the bookkeeping together — a practical approach

The financial obligations of an NDIS provider — NDIA claim reconciliation, GST-free income coding, participant-level tracking, SCHADS payroll, BAS preparation, and audit-ready record-keeping — don’t reduce by themselves. They accumulate in direct proportion to the number of participants, support workers, and service types you manage. The providers who stay on top of this are those who have separated bookkeeping from delivery — someone is responsible for the financial records specifically, doing it consistently, every week.

What a FreeMyCloud NDIS bookkeeper manages — every week

✓ NDIA remittance reconciliation
✓ GST-free income coding
✓ SCHADS Award payroll + STP
✓ Plan manager invoice tracking
✓ Participant-level income reporting
✓ Quarterly BAS preparation
✓ Audit-ready records maintained
✓ Input tax credits captured

FreeMyCloud provides NDIS providers with a dedicated, university-qualified graduate accountant — pre-trained in NDIS provider bookkeeping including GST-free coding, SCHADS payroll, and NDIA reconciliation — ready to work in your Xero, MYOB, or QuickBooks from day one. The cost is typically 50–70% less than a local bookkeeper hire, with no lock-in contracts and no setup fees. Use our savings calculator to estimate the cost for your organisation, or get in touch to discuss your setup directly.

How often should NDIS providers reconcile NDIA payment claims?

Weekly or at least fortnightly. Leaving NDIA remittance reconciliation to month-end allows rejected or underpaid claims to go unnoticed for extended periods, creating revenue gaps and a growing backlog of unmatched transactions. Regular reconciliation also means claim errors — incorrect support item numbers, amounts exceeding price limits — are caught and corrected promptly before they affect cash flow.

What records does the NDIS Quality and Safeguards Commission require providers to keep?

Registered NDIS providers must maintain records that substantiate every payment claim — including signed service agreements, delivery records (timesheets, service notes, attendance records), invoices, and payment documentation. Records must demonstrate a clear link between a support being authorised in a service agreement, delivered, invoiced, and paid. All records must be retained for a minimum of five years.

What causes NDIA payment requests to be rejected?

The most common causes are: an incorrect support item number for the service type; an amount exceeding the current NDIS price limit; a claim date outside the participant’s active plan period; a duplicate submission already processed; and plan funds exhausted in the relevant support category. Each rejection needs to be identified, corrected, and resubmitted — which requires monitoring claim outcomes regularly through the myplace provider portal.

Can NDIS providers claim input tax credits even though most NDIS income is GST-free?

Generally yes. Most NDIS disability supports are GST-free, but NDIS providers can still claim input tax credits on business expenses that carry GST — office supplies, software subscriptions, vehicle costs, and professional services. Many providers miss this, leaving ATO refunds unclaimed quarter after quarter. Correct expense coding ensures all available ITCs are captured in the BAS. For confirmation of your specific entitlements, speak with your registered tax agent.

What is the NDIS Provider Payment Assurance Program?

The NDIA’s Provider Payment Assurance Program reviews registered providers’ payment claims against their service delivery records to verify that claimed supports were actually delivered. It is a compliance mechanism separate from the NDIS Quality and Safeguards Commission. Providers selected for review need to produce records — service agreements, delivery documentation, invoices — that match their submitted payment requests. Claims that cannot be substantiated may result in repayment obligations to the NDIA.

Julian Mahoney — Founder, Free My Cloud

Julian Mahoney

Founder, Free My Cloud

Julian is the founder of Free My Cloud, an Australian firm specialising in offshore bookkeeping and accounting services for small and medium businesses. With years of experience helping Australian businesses reduce overhead and improve financial visibility through outsourcing, Julian and his team connect business owners with skilled professionals in the Philippines.

Leave a Reply