NDIS invoicing from your Google Calendar

NDIS work has a particular kind of admin overhead. The support itself is straightforward — you turn up, you do the job. The paperwork is where the time goes: finding the right support item number, checking it against the current price limit for your state, making sure the claim matches what was actually delivered, and then reconciling the remittance when it eventually lands.

Most providers do that lookup by hand, from a PDF price guide, one line at a time. This guide covers doing it from the calendar you already roster in.

The idea: the roster is the claim

If a support is in your calendar with the participant and the type of support attached, then everything the invoice needs is already recorded at the moment the work is scheduled. The invoice is a rendering of the roster, not a separate act of data entry.

That only works if the calendar event knows which participant it belongs to and which support items apply. Both are solved with setup you do once per participant.

Step 1: Set up the participant once

Each participant gets a group code — (NDISABC) style, the NDIS prefix marking it as an NDIS participant rather than a private or company client. The code goes in the calendar event title, and it is what routes the job into your NDIS log rather than one of the other logs, with NDIS invoicing rules applied.

Then you attach that participant's support items. This is where the built-in catalogue does the work: item numbers, descriptions, registration groups, units and price limits by state are already there, so you search the real catalogue rather than typing an item number from memory and hoping it is current.

Step 2: Group the items under keywords

This is the part that makes it work across a varied caseload, and it is worth understanding.

A participant rarely receives one kind of support. You might do lawn mowing for them one week and take them shopping the next, and those claim different items. So instead of a single static list per participant, items are grouped under a keyword — “Lawn Mowing”, “Shopping”, “Transport” — with up to four items in each group.

When supports are imported, the event's text is matched against that participant's keywords, longest keyword first and case-insensitively. A calendar event titled “Lawn Mowing (NDISABC)” pulls the lawn mowing bundle; the shopping trip pulls the shopping bundle. One participant, correct items either way, nothing typed.

Step 3: Import the week

Pull Services over a date range reads your calendar and writes each support into the NDIS log with its support items already attached.

When an event does not match any of that participant's keywords, nothing is guessed. The row is flagged for manual review instead of having a plausible-looking item number attached to it. That behaviour is deliberate: a wrong item number on an NDIS claim is worse than a blank one, because the blank one gets fixed and the wrong one gets claimed.

Only events carrying a registered group code are imported at all, so your own admin appointments, team meetings and personal calendar entries never end up in the log.

Step 4: Invoice

Bulk Create Invoices over the same date range generates NDIS invoices from the log rows, on your own template, with the support items and rates as recorded. NDIS invoices are generated through their own path rather than being a general invoice with different words on it.

Invoices are emailed from your own Gmail account, grouped so a plan manager receives one email rather than a dozen, and moved to a Processed folder once sent so the next run does not send them twice.

Step 5: Reconcile the remittance

This is the part most calendar-based approaches never reach. When payment comes back, you get a remittance — often an RCTI covering many participants and many dates, as a PDF.

Rather than ticking those off by hand, the remittance PDF is read and matched line by line against your logs by invoice number, marking off what has been paid. It works across all your logs at once, so a provider paying for both NDIS and aged care work reconciles in one pass.

What this does not do

Worth being straight about the boundaries. Calendar Force is not a claiming portal — it does not lodge claims into the NDIS payment system for you, and it is not a plan management or participant records system. It produces correct invoices from correctly rostered work and reconciles the money coming back.

You are also still responsible for the accuracy of what you claim. A built-in catalogue means you are choosing from real item numbers with real state price limits rather than remembering them, which removes a class of transcription error. It does not decide what support was delivered — you do.

Summary

1. Give each participant a group code like (NDISABC) and put it in the event title.
2. Attach their support items from the built-in catalogue, with state price limits already applied.
3. Group those items under keywords matching the kinds of support you deliver.
4. Pull Services to import the week; review anything flagged.
5. Bulk Create Invoices, then email them from your own Gmail.
6. Match the remittance PDF when payment lands.

Calendar Force is a Google Workspace Marketplace add-on plus a web app, built by a provider who got tired of the paperwork. The same rostered events can also send SMS reminders to participants. See pricing or start with 20 free invoice tokens.