A Service Note Is Not Enough: What to Check Before Invoicing

A service note confirms that a support was documented. It does not automatically confirm that the service can be invoiced correctly.

Before an NDIS provider sends an invoice or submits a payment claim, the administrator should check more than the worker’s note. The service needs to be matched against the participant’s agreement, roster, actual hours, support type, applicable pricing and other relevant records.

The NDIS requires providers to keep complete and accurate records of supports delivered, including invoices, support logs, rosters, case notes and service agreements. Providers are also responsible for making sure payment claims are complete, truthful and accurate.

That means the real question before invoicing is not:

“Do we have a service note?”

It is:

“Do all the available records support what we are about to invoice?”

---

Why a Service Note Alone Is Not Enough

A service note can tell you what a support worker says happened during a shift.

For example:

“Provided personal care and community access to the participant from 9:00 am to 1:00 pm.”

That is useful information.

But before creating an invoice, an administrator may still need to check:

• Was the shift actually rostered for 9:00 am to 1:00 pm?
• Did the worker actually work those hours?
• Does the service agreement cover the support?
• Is the support type correct?
• Is the participant’s funding available for the support?
• Is the correct NDIS support item being used?
• Is the rate correct?
• Does the claim comply with applicable NDIS pricing arrangements?
• Is there a cancellation, travel, transport or other charge that needs separate consideration?
• Does the documentation support the quantity being claimed?

This is why invoicing should be treated as a verification process, not simply a data-entry task.

The NDIS expects providers to request payment only after an NDIS support has been delivered and to ensure claim details are accurate and aligned with approved funding and applicable pricing arrangements.

---

The NDIS Pre-Invoice Verification Process

A reliable NDIS invoicing workflow can be structured as:

Service Note → Roster → Actual Service → Service Agreement → Participant Funding → Support Item → Rate → Claim Type → Invoice → Final Review

Each step answers a different question.

Let’s look at what an NDIS administrator should check before an invoice is submitted.

---

1. Check the Participant Details

Start with the basics.

Before creating an invoice, verify:

• Participant name
• Participant NDIS number or relevant reference
• Correct participant record
• Correct service period
• Correct provider information
• Relevant plan or funding information

The NDIS record-keeping requirements include participant details, dates of support, support type and the amount or quantity of support delivered.

A simple data-entry mistake can create problems later.

For example, invoicing the correct service against the wrong participant record can result in reconciliation problems and unnecessary follow-up.

---

2. Check the Service Date and Time

Next, compare the service note with the actual service date and time.

For example:

Service note:
9:00 am – 1:00 pm

Roster:
9:00 am – 1:00 pm

Timesheet or support record:
9:00 am – 1:00 pm

If all three agree, the administrator has stronger evidence supporting the quantity being invoiced.

But imagine the service note says four hours while the roster shows three hours.

That should trigger a review.

The administrator should not simply invoice four hours because that is what appears in the service note.

The discrepancy needs to be investigated and resolved before invoicing.

---

3. Compare the Service Note With the Roster

The roster is an important part of the provider’s records.

Compare:

• Participant
• Worker
• Date
• Start time
• Finish time
• Support type
• Scheduled hours

Example

Record	Time
Roster	10:00 am – 2:00 pm
Service note	10:00 am – 2:00 pm
Timesheet	10:00 am – 1:30 pm

The administrator now has a 30-minute discrepancy.

That does not automatically mean the invoice is wrong.

It means someone needs to determine what actually happened before the invoice is finalised.

Perhaps:

• The roster wasn’t updated.
• The worker stayed an additional 30 minutes.
• The participant requested a change.
• The service note contains an error.
• The timesheet is incorrect.

The discrepancy should be resolved rather than ignored.

---

4. Confirm That the Service Was Actually Delivered

The NDIS expects providers to request payment only after the support has been delivered.

Before invoicing, confirm that the service actually occurred.

Depending on the provider’s systems, supporting records may include:

• Service notes
• Support logs
• Rosters
• Timesheets
• Attendance records
• Participant confirmations
• Other relevant service records

The exact evidence will depend on the support type and provider’s processes.

The administrator should never assume that a scheduled shift automatically means the service was delivered.

---

5. Check the Service Agreement

The next question is:

Was this support agreed with the participant?

A service agreement can establish the supports being delivered, how they will be delivered, costs, payment arrangements and other responsibilities.

Compare the invoice against the current agreement.

Check:

• Support being provided
• Agreed arrangements
• Applicable rates
• Frequency of support
• Relevant fees or charges
• Payment arrangements
• Cancellation arrangements where applicable

This becomes particularly important when the provider is delivering a support that wasn’t part of the original arrangement.

If the service agreement and the proposed invoice don’t appear to match, stop and investigate before sending the invoice.

---

6. Check the Participant’s Funding and Support Category

Having a service note does not automatically mean that the support is claimable.

The administrator should check whether the support aligns with the participant’s available funding and the relevant support category.

The NDIS expects providers to ensure claims are accurate and in line with the participant’s approved funding.

This means the administrator needs to understand what is actually being claimed, rather than simply copying the description from the service note.

---

7. Verify the Correct NDIS Support Item

One of the most important invoicing checks is the support item.

A service note might say:

“Community access support — 3 hours.”

That description alone doesn’t tell the administrator which NDIS support item should be claimed.

The administrator should verify:

• Correct support category
• Correct support item/reference
• Correct claiming arrangement
• Correct unit
• Correct rate
• Applicable day/time rules where relevant

The support item reference and price are important components of a provider payment request.

---

8. Check the Rate Before Invoicing

The rate on the invoice should be checked against the applicable pricing requirements and the provider’s agreed arrangements.

Do not simply copy the previous invoice.

Rates and pricing arrangements can change, and different supports can have different pricing rules.

The administrator should check:

• Support item
• Applicable price limit
• Agreed rate
• Day of week
• Time of day
• Relevant loading or pricing rules
• GST treatment where applicable

This is particularly important when the provider is processing a large volume of invoices.

A small pricing error repeated across hundreds of claims can become a significant financial issue.

---

9. Check the Hours or Quantity Being Invoiced

Suppose the service note says:

4 hours

Before invoicing four hours, verify that the supporting records agree.

Check:

Start time + finish time = actual duration

Then consider whether any applicable breaks, travel or other arrangements require separate treatment.

The quantity on the invoice should be supported by the provider’s records.

The NDIS record-keeping requirements include the amount and quantity or hours of support delivered.

---

10. Check Travel, Transport and Other Charges Separately

Not every charge should simply be added to the support worker’s service hours.

Where travel, transport or other charges apply, the administrator should determine:

• What was actually provided?
• Is the charge permitted?
• Is it covered by the relevant agreement?
• Is the correct rate being used?
• Is supporting documentation available?
• Is it being claimed under the appropriate arrangement?

These charges deserve separate attention rather than being automatically copied into an invoice.

---

11. Check Cancellations and Non-Standard Services

A cancelled shift should not automatically be treated as an ordinary delivered support.

If a cancellation charge or other non-standard claim is being considered, the administrator should verify that the applicable requirements and provider-participant arrangements support the charge.

This is another situation where:

“There is a service note.”

does not necessarily mean:

“We can invoice this as a standard support.”

The administrator needs to understand what actually happened.

---

12. Check the Claim Type

The administrator should verify the appropriate claim type before finalising the invoice.

The process can differ depending on how the participant’s NDIS funding is managed.

For example:

• Self-managed
• Plan-managed
• NDIA-managed

The administrator should therefore confirm where the invoice or payment request needs to go and whether the claim is being processed through the correct channel.

---

13. Check the Invoice Details

Once the underlying service has been verified, review the actual invoice.

A final invoice review should include:

• Correct participant
• Correct provider
• Correct ABN
• Correct invoice number
• Correct service dates
• Correct support item
• Correct claim type
• Correct quantity
• Correct rate
• Correct total
• GST treatment where applicable
• Appropriate supporting records

The invoice should form part of a complete record rather than exist as an isolated document.

---

The 15-Point NDIS Pre-Invoice Checklist

Before an invoice leaves your organisation:

• Correct participant
• Correct service date
• Service was actually delivered
• Service note reviewed
• Roster checked
• Timesheet/support log checked where applicable
• Service agreement checked
• Funding/support category checked
• Correct support item verified
• Correct rate verified
• Correct quantity verified
• Travel/other charges checked separately where applicable
• Correct claim type confirmed
• Invoice details reviewed
• Supporting records complete

If any important item is unclear, the invoice should be reviewed before submission.

---

Example: When the Service Note Looks Fine but the Invoice Is Not Ready

Imagine a support worker submits:

Participant: John
Date: 12 August
Support: Community access
Time: 9:00 am – 1:00 pm
Duration: 4 hours

At first glance, everything looks fine.

But the administrator checks the other records.

Roster

9:00 am – 12:00 pm

Timesheet

9:00 am – 12:00 pm

Service Agreement

Community access support is included.

Proposed Invoice

4 hours.

Now there is a problem.

The service note says four hours, but the roster and timesheet show three.

The administrator should not simply invoice four hours.

The discrepancy needs to be investigated.

Maybe:

• The roster wasn’t updated.
• The worker stayed an additional hour.
• The participant requested an extension.
• The service note contains an error.
• The timesheet is incorrect.

The administrator needs to establish what actually happened and ensure the records accurately reflect the service before invoicing.

This is why a service note should be treated as one part of the evidence, not the entire invoicing approval.

---

What Should an NDIS Administrator Do When Records Don’t Match?

Don’t immediately invoice.

Step 1: Identify the discrepancy

For example:

Service note: 4 hours
Timesheet: 3 hours

Step 2: Check the source records

Review:

• Roster
• Service note
• Timesheet
• Support log
• Service agreement
• Other relevant records

Step 3: Contact the Relevant Person

Depending on the situation, this could be:

• Support worker
• Team leader
• Service coordinator
• Participant
• Operations manager

Step 4: Correct the Records

The records should accurately reflect what happened.

Step 5: Recheck the Invoice

Only after the discrepancy has been resolved should the invoice proceed.

This creates an important principle:

If the evidence doesn’t agree, the invoice isn’t ready.

---

Why This Process Matters

Accurate invoicing isn’t just about getting paid.

It creates a clear connection between:

What was agreed → What was scheduled → What was delivered → What was documented → What was invoiced → What was claimed

When those records align, the provider has a much stronger audit trail.

The NDIS can review provider records to assess whether payment claims are compliant. Maintaining complete and accurate records therefore becomes an important part of the provider’s administrative controls.

---

Common NDIS Invoicing Mistakes

1. “The Service Note Is There, So Invoice It”

A service note is important evidence, but it isn’t the entire invoice approval process.

2. Copying Hours Without Checking the Roster

The administrator should compare documented hours with other relevant records.

3. Using the Previous Invoice Without Checking

Previous invoices can contain errors too.

4. Not Checking the Current Service Agreement

The provider should ensure the invoice reflects the current arrangement.

5. Using the Wrong Support Item

A general description in a service note isn’t enough to determine the correct claim item.

6. Ignoring Small Time Differences

A 15- or 30-minute discrepancy can indicate that the records need clarification.

7. Combining Different Charges Without Checking Them

Travel, transport, cancellation and other charges may have different requirements.

8. Treating Every Participant the Same

Different participants can have different funding arrangements, agreements and support requirements.

9. Invoicing Before the Service Is Delivered

Providers should request payment only after the relevant support has been delivered.

10. Failing to Keep Supporting Records

An invoice should form part of a broader record-keeping system rather than exist as an isolated document.

---

A Better NDIS Invoicing Workflow

Instead of:

Service Note → Invoice

use:

Service Delivered
↓
Service Note Received
↓
Roster Checked
↓
Timesheet/Support Log Checked
↓
Service Agreement Checked
↓
Funding & Support Category Checked
↓
Support Item Verified
↓
Rate & Quantity Checked
↓
Claim Type Confirmed
↓
Invoice Created
↓
Final QA Review
↓
Invoice/Claim Submitted

This workflow creates a stronger administrative control and gives the provider a clear audit trail.

---

Final NDIS Pre-Invoice Review

Before an invoice leaves your organisation, ask:

Does the invoice match what was actually delivered?

Then verify:

Participant

Is this the correct participant?

Date

Did the support happen on this date?

Time

Do the documented hours match the supporting records?

Service

Was the support actually delivered?

Agreement

Is the support covered by the relevant arrangement?

Funding

Is the support aligned with the participant’s available funding?

Support Item

Is the correct item being used?

Rate

Is the rate correct?

Quantity

Is the number of hours or units accurate?

Claim Type

Is the claim being submitted correctly?

Invoice

Does the invoice contain the required information?

Evidence

Can the provider demonstrate how the invoice amount was calculated?

If any important answer is “I’m not sure,” the invoice should be reviewed before submission.

---

Final Thoughts

A service note is an important part of NDIS service documentation.

But it should not be the only checkpoint between service delivery and invoicing.

A stronger process connects the service note with the roster, support records, service agreement, participant funding, support item, rate and invoice.

The goal is simple:

Don’t invoice because a service note exists. Invoice because the complete record supports the claim.

For NDIS providers, this approach can help reduce avoidable invoice errors, improve record accuracy and make the relationship between service delivery and billing easier to review.

If your team is spending hours checking service notes, rosters, invoices and supporting records manually, an experienced NDIS administration team can help standardise the workflow and manage recurring back-office work.