Correct an NDIS Invoice After a Payment Query
When an NDIS invoice is queried for dates, units or references, verify your records first, then issue a clearly labelled correction.
If an NDIS invoice is queried for a missing or incorrect date, unit count or reference, do not start by making a fresh invoice from memory. First verify your delivered-support records against the original invoice, then correct only the field that is actually wrong. That keeps the change traceable and reduces the risk of duplicate billing.
The payment route matters. The official NDIS guide to getting paid distinguishes self-managed, plan-managed and NDIA-managed arrangements. A plan manager may review a PDF invoice, but a PDF alone is not the NDIA payment request process for NDIA-managed supports. So before you resend anything, confirm who the invoice should go to, what support was delivered, and whether the original document actually contained an error.
A structured NDIS invoice template can help you rebuild the corrected invoice clearly, but the template does not determine funding eligibility or prove that payment should be made.
Check the original records before changing the invoice
Start with your own records, not the payer's assumption. The official NDIS record-keeping requirements require complete and accurate records of delivered supports. Those records should identify the participant, their NDIS number, the support delivered, date and quantity, alongside the other details required by the official guidance.
For a payment query about dates, units or references, confirm:
- the participant and recipient details
- the service date or date range actually delivered
- the quantity delivered in the correct unit
- the support record or internal reference linked to that service
- whether any payment has already been received
If your records show the original invoice was correct, respond with the supporting information rather than issuing a changed invoice. If the records show an error, correct the invoice in a way that leaves the original visible in your files.
Use official guidance for the payment path and invoice fields
Two official sources do most of the work here. The NDIS guide to getting paid explains who to invoice under different funding-management arrangements and notes that plan-managed invoicing generally requires a valid ABN unless an exemption applies with a supplier statement. The Current NDIS pricing arrangements are the reference point when item descriptions, units or prices must match the service date and circumstances.
That does not mean every payer request justifies changing the support item or claim-related field. An administrative query about a missing reference is not the same thing as reclassifying the support. Use the official guidance to answer three separate questions:
- Was the support delivered as recorded?
- Did the invoice reflect that record accurately?
- Does the payment pathway require a corrected field or different document format?
Keeping those questions separate helps you fix administrative mistakes without creating a second claim for the same support.
A safe workflow for correcting an NDIS invoice
A simple correction workflow usually works better than rewriting the whole billing file.
| Step | What to do | Why it matters |
|---|---|---|
| Keep the original | Retain the original invoice number, date and PDF in your records. | You need a traceable history. |
| Verify source records | Check delivered date, quantity, participant details and reference logs. | Corrections should match what was actually delivered. |
| Identify the exact error | Note whether the issue is a date, unit count, recipient detail or reference. | Narrow fixes reduce new mistakes. |
| Prepare the correction | Issue a revised or replacement invoice clearly linked to the original. | The recipient can see what changed. |
| Prevent duplicate processing | State that the corrected invoice replaces the earlier one if the earlier one is unpaid. | This helps avoid both versions being processed. |
| Send through the right pathway | Send to the participant, plan manager or NDIA process as required. | Correct content still fails if sent the wrong way. |
| Record the outcome | Log when the query arrived, what changed and whether payment status was checked. | You need a resolution trail. |
If your process uses a credit-and-reissue method, keep the linked documents together in your records. If it uses version labels instead, make the relationship obvious on the corrected document.
What to change, and what not to change
A good correction is specific. It fixes the wrong field and leaves verified information alone.
Common correction areas include a transposed service date, an incorrect quantity copied from a support log, a missing participant reference requested by the payer, or incomplete recipient details. Those are administrative issues.
Use more caution with support items, units, rates, ABN details and any claim-related field. Check the applicable Current NDIS pricing arrangements for the actual service date and circumstances, and do not guess. If a payment pathway requires a specific claim-related field, check the official NDIS guidance for that field and replace any placeholders before resending.
Also remember that plan-managed funding is not itself the claim type. And if the issue is really a disagreement about whether a support should be funded, that goes beyond a straightforward invoice correction.
For formatting basics, an NDIS invoice template can help you include business details, participant details, line items and payment instructions consistently, but your supporting records still sit outside the invoice.
Worked example: correcting units without changing the support delivered
Below is a fictional example of a quantity correction that keeps the underlying support record intact.
| Field | Original invoice | Verified record | Corrected invoice |
|---|---|---|---|
| Participant | Jordan P | Jordan P | Jordan P |
| Service date | 12 Aug 2026 | 12 Aug 2026 | 12 Aug 2026 |
| Support item | [LOOK UP APPLICABLE ITEM/CODE] | [same] | [same] |
| Unit type | hour | hour | hour |
| Quantity | 3.0 | 2.5 | 2.5 |
| Rate | [LOOK UP APPLICABLE RATE FOR DATE] | [same] | [same] |
| Line total | 3.0 x rate | 2.5 x rate | 2.5 x rate |
| Reference | missing | Support log SV-0826-14 | Support log SV-0826-14 |
Assume the support log shows attendance from 9:00 to 11:30, so the delivered support was 2.5 hours. The payer queried both the quantity and the missing reference, and no part-payment has been received.
A clear note on the corrected invoice could say:
Corrected invoice replacing INV-1048. Changes made: quantity amended from 3.0 hours to 2.5 hours to match delivered-support record dated 12 Aug 2026; reference added: SV-0826-14. Please do not process INV-1048 if unpaid.
That wording does two useful things: it identifies the exact correction and signals that the earlier invoice should not also be processed.
Two edge cases that need extra care
Partial payment has already been received
If part of the original invoice has already been paid, do not simply resend the full corrected amount. Reconcile the payment against your actual payment records and any remittance information first. Then decide how to document the remaining amount without double counting what has already been received. Invoice status tracking can help you monitor the document, but payment truth comes from your payment records.
The payer asks for a different item or claim-related field
This is higher risk than correcting a date or reference. Check the service date, support circumstances and official pricing guidance before changing any item or related field. Do not alter a support code merely to obtain payment if your records do not support that classification. An administrative correction should not become a re-description of the support delivered.
For nearby issues, the sibling guides on Plan-Managed NDIS Invoices: A Preparation Checklist and NDIS Invoices for Repeated Support Visits cover setup and repeat-visit documentation rather than post-query corrections.
Keep the audit trail in your own records
The invoice should stay readable, but the full correction history belongs in your operational records. A simple resolution log can include:
| Record | Example purpose |
|---|---|
| Original invoice number and date | Identify the first document |
| Query received date | Show when the issue was raised |
| Who raised the query | Track the contact point |
| Issue identified | Date, quantity, reference or recipient detail |
| Records checked | Support log, delivery note, internal register |
| Correction made | What changed and what stayed the same |
| Corrected invoice number or version label | Link old and new documents |
| Resend date and payment follow-up | Track the outcome |
If you use InvoiceSonic, it supports creating an invoice with business and client details, line items, tax and currency settings, payment instructions, a PDF, saved client details and invoice status tracking. Stored invoice view or open timestamps can help you monitor whether the document was seen, but views do not prove payment. Support logs, approval records and other evidence remain part of your separate operational workflow.
A clear email to send with the correction
You do not need legal language. You need a short message that explains the change and points back to the original invoice.
Subject: Corrected invoice for [Participant Name] replacing [Original Invoice Number]
Body:
Replace all bracketed placeholders before sending.
Hello [Recipient Name],
Thank you for your query about invoice [Original Invoice Number]. We checked our delivered-support records and have attached a corrected invoice.
Changes made:
- [Correct service date / corrected quantity / added reference]
- Original invoice reference: [Original Invoice Number]
- Corrected invoice reference: [New Invoice Number or version label]
This correction relates to the same delivered support and is intended to replace the earlier invoice if that earlier invoice has not been paid. If any part-payment has already been processed, please let us know so we can match our records before any further billing action.
Kind regards,
[Name]
[Business Name]
[ABN if applicable]
The practical standard is straightforward: verify the delivered-support record, correct only the field that is wrong, label the corrected invoice clearly, and track whether the original was superseded, rejected or partly paid. That keeps an administrative query from turning into a duplicate invoice problem.
Check the payment pathway before sending
Confirm who receives the invoice and what records they require for the participant’s funding-management arrangement. Match the invoice to delivered, agreed supports and current requirements.
NDIS invoice template and billing checklist →