The NDIS Billing Problems That Do Not Show Up Until After the Money Is Gone

What makes a billing blind spot

A billing blind spot is a failure that the system does not detect -- and therefore does not surface to the billing officer or coordinator until the damage is done. This is different from a hold, which is a problem the billing system catches and flags before submission. Blind spots are the category of errors that slip through.

The six problems below share a common characteristic: they produce zero revenue, an aged receivable, or a compliance finding, but at no point does the software produce an error message. The system processes the action without complaint. The problem emerges later, in a bank statement, an audit report, or a compliance assessment.

Blind spot 1: Self-managed participant with no email

What happens. An invoice is generated for a self-managed participant and the system marks it Sent. But there is no valid email address on the participant record. The invoice is either not delivered or bounces silently. The participant never receives it, never pays, and never lodges a reimbursement claim with NDIA.

Why most tools miss it. The billing run completes without error. The invoice status updates to Sent. Nothing in the workflow prompts the billing officer to verify that delivery succeeded.

What it costs. The invoice ages unnoticed in the receivables ledger. If the participant's plan year ends before the error is discovered, the funding may no longer be available. The provider has delivered the service but will not be paid.

What a proactive system does. Teiro flags self-managed participants with no email address before a billing run is created -- not after the invoice fails to send. This surfaces the data gap at the point where it can be fixed, not after the invoice is already overdue.

Blind spot 2: Service agreement coverage gap

What happens. A coordinator rosters a worker to deliver a support that the participant's SA does not cover. The shift is delivered. At billing time, the claim line is held for "no SA line covering the activity type." By this point, the service has already been delivered and the worker has been paid. The organisation bears the cost with no ability to claim it.

Why most tools miss it. The coverage gap is a billing-time check, not a rostering-time check. The scheduler sees nothing when the shift is created. The problem only surfaces when the billing officer creates a billing run, which may be weeks after the shift.

What it costs. Unclaimable delivered services are a direct cost. For a provider delivering 100 hours per week, even one uncovered support category can represent thousands of dollars per billing period.

What a proactive system does. Surface the SA coverage gap at the point of rostering, not at billing time. When a shift is being created for a support type that is not covered by the participant's current SA, the coordinator should be warned before the shift is confirmed -- not after the service has been delivered.

Blind spot 3: Service agreement expiry mid-run

What happens. A billing period spans an SA expiry date. Services delivered before the expiry date are claimable. Services delivered after are not. If the billing system does not check dates at the line level, the entire run may appear clean until the post-expiry lines are rejected by NDIA or flagged in reconciliation.

Why most tools miss it. Some billing systems check whether an SA exists but do not check whether each service date falls within the SA validity period. An SA that expired on the 15th of the month may still appear as "active" in the system when a billing run is created on the 30th, because the SA record exists -- it is just expired.

What it costs. Post-expiry services cannot be claimed. If the SA was not renewed in time and services continued for several weeks, the uncovered period can represent a significant unclaimable amount.

What a proactive system does. Check the service date on each claim line against the SA validity dates, not just whether an SA record exists. Hold any line where the service date falls outside the SA period, and alert coordinators when an SA is within 30 days of expiry.

Blind spot 4: Worker screening lapse between rostering and delivery

What happens. A worker's NDIS Worker Screening Check expires after they are rostered but before the shift date. The shift appears in the roster and is delivered. At billing time, the claim is held because the worker was unscreened at the time of service. The hold cannot be cleared by renewing the check.

Why most tools miss it. The rostering system checked screening status at the time of assignment, not at the time of delivery. A check that was current at 9am on the booking date may have lapsed by the time the shift runs three weeks later.

What it costs. Where the role is risk-assessed, delivering a shift without a current worker screening clearance is a violation of the NDIS Worker Screening Rules. The claim cannot be submitted. The organisation has a compliance exposure and an unrecovered cost.

What a proactive system does. Re-check worker screening status at shift confirmation time, not only at booking time. Alert coordinators when a screened worker's check will expire before a rostered shift date -- before the shift is delivered, not after.

Blind spot 5: Plan year boundary

What happens. A participant's NDIS plan year ends and a new plan begins. The old plan has no remaining budget. Services delivered in the first weeks of the new plan year may be routed to the old SA (because it has not yet been updated in the billing system), or to no SA at all if the new plan SA has not been created. Claims fail silently or are held.

Why most tools miss it. Plan year boundaries require action from the coordinator or billing officer to update the SA in the system. If this update is not prompted, it does not happen. The system continues delivering services as if the old plan is still active.

What it costs. Services delivered in the gap between plan years are unclaimable if no valid SA exists. Budget visibility for the old plan shows inflated remaining funds because services are not being attributed to it correctly.

What a proactive system does. Alert coordinators and billing officers 30 days before an SA expires, with a prompt to set up the new plan SA. Prevent new shifts from being confirmed for a participant whose SA expires within the confirmed shift's service date range.

Blind spot 6: Duplicate participant records

What happens. A participant is entered into the system twice -- perhaps once by a coordinator and once during a data migration, or once under a formal name and once under a preferred name. Billing and shifts are split across both records. Budget tracking is fragmented. Some claim lines go to one record, others to the other. Neither record shows the full picture.

Why most tools miss it. Duplicate records look like two different participants. Neither record throws an error. Claims process normally on both records. The problem is only visible when a billing officer or coordinator notices the two records and recognises they are the same person.

What it costs. Budget visibility is unreliable on both records. Coordinators making rostering decisions based on remaining budget may be seeing only half the picture. In a worst case, the same service is billed under both records -- a genuine duplicate claim.

What a proactive system does. Flag potential duplicates at participant record creation time based on matching NDIS participant numbers, names, or date of birth. Block the creation of two records with the same NDIS number.

The pattern behind the blind spots

Every one of these failures shares the same root cause: the billing system checks what it is built to check, and only at the stage in the workflow where it was designed to check. A system that only checks at billing time will miss problems that originated at rostering time. A system that only checks SA existence will miss SA expiry and SA coverage gaps. A system that sends invoices without verifying delivery will not know when an invoice bounces.

Proactive billing software does not wait for the billing run to surface these problems. It pushes alerts upstream, to the coordinator and the billing officer, at the earliest point where the problem can be fixed without cost.

Book a demo to see how Teiro surfaces these issues before the money is gone, or sign up free for organisations with 5 or fewer active users.