NDIS billing software: a practical guide for Australian providers

What NDIS billing actually involves

The billing lifecycle for an NDIS provider follows a fixed sequence. A shift is delivered and the worker checks out. Attendance evidence is captured. The coordinator or billing officer verifies the shift. A billing run is created, grouping verified shifts by participant and funding type. Claim lines are reviewed and any holds are resolved. For agency managed participants, a bulk payment request (BPR) CSV is exported and uploaded manually to the NDIA myplace portal. For plan-managed participants, an invoice is sent to the plan manager. For self-managed participants, an invoice is sent directly to the participant. Payment arrives. The remittance is imported and reconciled against open claims.

Each of these three management types works differently, and most providers support all three simultaneously.

Many participants have mixed management: some supports are agency managed, others are plan-managed. A billing system that cannot track management type at the service agreement line level will route claims incorrectly.

The service agreement as the source of truth

Every NDIS claim traces back to an active, correctly configured service agreement. The service agreement is the contract between the provider and the participant: it specifies which supports will be delivered, at what rates, and what the funding cap is for each support category.

Most billing failures originate here, not in the billing system itself. The upstream errors that most often cause payment failures are:

• →The service agreement is expired. Services delivered after the agreement end date are not covered, regardless of whether the work was done.
• →The service agreement exists but does not include a line item for the support category delivered. A participant might have a core supports agreement that does not cover capacity building. If a capacity building shift is delivered and billed, it will be rejected.
• →The agreed rate on the SA exceeds the current NDIS Pricing Arrangements and Price Limits cap. NDIA will pay the Pricing Arrangements cap, not the agreed rate. The provider absorbs the difference.
• →The SA covers the correct support category but has exhausted its budget. Claims can still be created and submitted -- but NDIA will not pay once the funding bucket is empty. Note: budget tracking and near-limit warnings in Teiro currently apply to agency managed lines. For plan-managed and self-managed participants, budget visibility is managed through the plan manager or participant directly.

A billing system that checks SA validity before a claim line is created catches these problems at the right moment: before you have already done the work, invoiced the client, and submitted to NDIA.

Pre-submission hold logic: what good billing software catches before you submit

Most billing software documentation describes what you can claim. Very few describe what should be blocked before you submit. Pre-submission holds are the mechanism that prevents bad claims from reaching NDIA, plan managers, or participants -- where they become rejection notices, compliance findings, or audit flags.

In Teiro, claim lines are automatically held before submission when any of the following conditions are detected:

Holds are not failures. They are the system doing its job. A billing officer reviews held lines, resolves the underlying issue, and releases the line for submission. Lines that cannot be resolved are removed from the run. This is the correct workflow.

SCHADS rates and the NDIS Pricing Arrangements: how they interact

The SCHADS Award and the NDIS Pricing Arrangements and Price Limits (PAPL) operate on the same shift but serve different purposes. Understanding how they interact is essential for providers managing margins.

SCHADS sets the minimum you must pay workers. The Award specifies ordinary time rates, penalty rates for evenings, weekends, and public holidays, broken shift allowances, and travel time. These are legal minimums -- you cannot pay less.

The NDIS Pricing Arrangements and Price Limits sets the maximum you can claim from NDIA for a given support item. Price limits are set by support item code and shift type. NDIA will not pay above these limits regardless of what is on the service agreement.

The spread between the two figures is the provider's margin. When SCHADS rates increase (which they do annually, usually from 1 July) and the Pricing Arrangements do not increase by the same amount, margin compresses. When a Pricing Arrangements update lags a SCHADS increase, some support items run at negative margin for part of the year.

Submitting to NDIA: bulk payment requests

For agency managed participants, providers submit claims through a bulk payment request (BPR) file. The BPR is a CSV file with a specific format required by NDIA. It contains one row per claim line, with the following fields: provider ABN, participant NDIS number, support item code from the NDIS support catalogue, service start and end dates, quantity (hours or units), unit price, total amount, and a provider claim reference that is unique to each line.

In Teiro, the BPR file is generated automatically from a completed billing run. Once the billing officer has reviewed the run, resolved holds, and approved the claim lines, the export button produces a correctly formatted CSV.

The provider claim reference in each row is critical. It is the identifier that links the NDIA payment response back to the original claim line when you reconcile. A BPR where claim references are not unique, or where they change between submission and reconciliation, breaks automated matching.

Payment reconciliation

After NDIA processes a BPR, they return a myplace upload results CSV. This file contains one row per claim line showing the amount requested, the amount approved, and a response code. The provider claim reference from the original BPR is included, which is how each row is matched to the original claim.

Partial payments are common. NDIA applies its own rate cap at processing, so if your submitted rate was above the current Pricing Arrangements cap, NDIA pays the cap and the difference is written off. If a participant's funding bucket is exhausted, that line receives zero payment. Response codes indicate the reason for any reduction.

In Teiro, the myplace upload results CSV is imported into the billing module. Lines with matching provider claim references are automatically reconciled. Lines where the paid amount differs from the submitted amount are flagged for review. Lines with no match -- where the claim reference in the results file does not correspond to any submitted line -- are surfaced for manual investigation.

Manual reconciliation -- printing the results file, pulling up the original BPR in a spreadsheet, and matching by reference number line by line -- is one of the most time-consuming billing tasks at mid-to-large providers. For an organisation with 50 active agency managed participants, this process runs to three to five hours per payment cycle without software support.

Billing for different provider types

The three funding management types create three parallel billing workflows. Providers who support all three -- which is most registered providers of meaningful size -- need a system that can run all three from the same billing run without manually separating lines.

Agency managed participants are the simplest operationally: NDIA pays quickly and consistently. The main errors are SA configuration problems and rate cap mismatches. The BPR export must match NDIA's current file format and use current support item codes -- codes that were valid last year may have been retired.

Plan-managed participants introduce a private entity (the plan manager) into the payment chain. Different plan managers have different invoice requirements: some require the NDIS support item code on the invoice; most require the participant's NDIS number; some have their own reference numbers they want included. Payment terms vary by plan manager and can be 14 to 45 days. When a participant changes plan managers mid-plan -- which happens -- invoices must be directed to the new plan manager from the changeover date, not the old one.

Self-managed participants have the longest and least predictable payment cycle. The participant claims the funds from NDIA themselves and pays you directly. The provider has no visibility into when the participant has lodged their claim with NDIA. A common failure: the participant has no valid email address in the system, the invoice is never sent, and the debt ages silently.

Mixed-management participants require the billing system to correctly separate claim lines by funding type within the same billing run. A participant whose core supports are agency managed but whose capacity building is plan-managed should have two separate billing outputs. Getting this wrong does not always produce an error -- it may produce a clean submission to the wrong entity, which is worse.

What to look for in NDIS billing software

When evaluating billing tools for an NDIS provider, the questions that matter are not about the feature list. They are about whether the system handles the scenarios where billing goes wrong. Specific things to verify:

• QDoes the system support all three funding management types -- agency managed, plan-managed, and self-managed -- from a single billing run, or does it require separate workflows for each?
• QDoes it run pre-submission hold checks before a claim line reaches the export stage, and does it name the specific hold reason, or just flag a generic error?
• QIs billing connected to the roster? Can a shift move directly from verified to billable without re-keying dates, hours, and support items into a separate system?
• QDoes the BPR export match the current NDIA myplace portal format? Has the vendor updated it after the last NDIA support catalogue version change?
• QDoes it import the myplace upload results CSV and auto-match by provider claim reference, or is reconciliation manual?
• QDoes it flag self-managed participants with no email address before a billing run is created, not after an invoice fails to send?
• QDoes it alert on SA coverage gaps -- participant has shifts scheduled for a support type not covered by their current SA?

Why is my NDIS claim held before submission?

A held claim line means the billing system has detected a condition that prevents safe submission. The most common causes: no active service agreement for the participant as of the service date, no SA line item covering the support category delivered, or no attendance evidence recorded for the shift. In Teiro, each held line names the specific cause so a billing officer can resolve it before anything is sent to NDIA. See the full breakdown in Why NDIS claims get held before submission.

What is a bulk payment request (BPR)?

A bulk payment request is the CSV file that registered NDIS providers submit to the NDIA myplace portal to claim payment for agency managed participants. Each row represents one claim line: participant NDIS number, support item code, service start and end dates, quantity, unit price, and a unique provider claim reference. NDIA processes the file and returns a results CSV showing approved amounts and any line-level rejections. The provider claim reference is how each payment is matched back to the original submitted line during reconciliation. NDIA typically processes BPR submissions within 2-3 business days. Teiro generates the BPR CSV automatically from a completed billing run; the billing officer uploads it manually to the myplace portal.