How to Generate NDIS Invoices Without Spreadsheets

Why Manual NDIS Invoicing Is Risky

The common manual invoicing process looks like this: a manager exports shift data from the rostering tool, opens Excel, looks up the NDIS Price Guide for the correct item code and rate, builds a spreadsheet with a row per shift, formats it for PRODA, and submits. Then tracks whether it was accepted or rejected.

Every step in this process is a point of failure:

• Item code errors — wrong code for the support type, time of day, or participant's plan type
• Rate errors — using last year's rates, especially after the July annual update
• Missing shifts — if a shift is accidentally excluded, revenue is lost
• PRODA rejection — formatting errors cause claims to bounce
• No visibility — no easy way to see which invoices have been submitted, accepted, or are outstanding

How Automatic NDIS Invoice Generation Works

When shift data and NDIS pricing are in the same system, invoice generation becomes a matter of selecting a participant, choosing a date range, and clicking generate. The system does the rest.

Here is what happens in the background:

1. Shifts are matched to item codes. Each completed shift is mapped to the correct NDIS support item code based on the support type, day of week, and time of day. Weekday daytime, weekday evening, Saturday, Sunday, and public holiday all attract different item codes and rates.
2. Current rates are applied. The system uses the current NDIS Price Guide rates. When rates update each July, the system is updated to match — you don't need to manually update spreadsheet lookups.
3. Line items are generated. Each shift or group of shifts becomes a line item on the invoice with the participant's name, support item code, quantity (hours), unit price, and line total.
4. The invoice is reviewed. A manager reviews the generated lines before submission. Anything unusual can be flagged or adjusted.
5. PRODA CSV is exported. A correctly formatted bulk payment request file is generated for upload to PRODA.

NDIS Support Item Codes — Getting Them Right

Item code errors are the most common reason NDIS claims are rejected or under-scrutinised. The correct code depends on:

• Support purpose — Assistance with Daily Life, Community Participation, Capacity Building, etc.
• Day type — weekday standard, weekday evening, Saturday, Sunday, public holiday
• Claiming method — agency managed (NDIA), plan managed (plan manager), or self managed

For example, a weekday daytime personal care shift uses a different code from the same shift on a Sunday. Using the weekday code for a Sunday shift will result in underbilling — you bill less than you could claim.

Understanding NDIS Claiming Methods

There are three claiming methods under NDIS, and each affects how invoices are submitted:

Agency Managed (NDIA)

The most common method for registered providers. Invoices are submitted directly to the NDIA via PRODA. Payment arrives from the NDIA. This requires the correct PRODA bulk payment file format.

Plan Managed

The participant's plan manager handles the financial administration. Your invoice goes to the plan manager (typically a registered organisation), who verifies it against the participant's plan and pays you. You need the plan manager's name, email, and ABN.

Self Managed

The participant or their nominee manages the funding and pays providers directly from their NDIS funding. You invoice them directly and they claim reimbursement from the NDIA.

Tracking Claim Status

Once an invoice is submitted to PRODA, you need to track what happens to it. Claims can be:

• Accepted — payment will be processed
• Rejected — error in the claim that needs to be corrected and resubmitted
• Partial — some line items accepted, others rejected

Tracking this manually in a spreadsheet creates a reconciliation problem. A proper invoicing system maintains claim status per invoice and per line item, so you always know what has been paid, what is outstanding, and what needs to be resubmitted.

Common NDIS Invoicing Mistakes to Avoid

• Using last year's rates after 1 July. NDIS rates update on 1 July each year. Invoices submitted after 1 July at old rates will be underbilled.
• Wrong item code for the day type. Always check whether Saturday, Sunday, or public holiday codes apply to weekend and holiday shifts.
• Billing for cancelled shifts. Cancellations with less than the required notice may be claimable under the NDIS cancellation policy — but only if documented correctly.
• Not reconciling accepted payments. Just because a PRODA claim was submitted doesn't mean it was accepted. Check the claim status report regularly.
• Over-billing against the participant's plan budget. Track participant budgets so you don't accidentally invoice more than the plan covers — this creates compliance issues.