Agreements & Billing

Claim data, ready for the NDIS.

Claim-ready data assembles itself as you work: catalogue item numbers on every agreement, billing lines on every delivered shift, and coordination time claimed in batches. When it is time to lodge, the numbers are already there and they trace back to delivered support.

Start free trial Explore Agreements & Billing

What you get with NDIS payment requests.

NDIS line-item catalogue
Work from the current NDIS catalogue, so claim data uses valid items and prices.
Claim data from delivered support
Claims build from the support you actually delivered, not a separate spreadsheet.
Bulk-claim exports
Export claimed support coordination time as a CSV in the NDIS bulk payment request layout, ready to lodge.

Why it exists

The problem it solves.

Preparing NDIS payment requests usually means rebuilding a month of delivery in a spreadsheet: looking up support item numbers, matching prices, adding up hours and hoping it reconciles with what was actually rostered. It is slow, and a single wrong code can bounce a whole claim. The data already exists in your roster and agreements, and it should not need re-typing.

How it works

Keep the catalogue current

Upload the NDIS support catalogue into your workspace, covering current and legacy support items with pricing for every state and remote area. Claim data then works from valid item numbers and prices.

Anchor supports in the agreement

Each client's funded supports sit on their agreement as line items with the code, unit price, quantity and budget captured, so every downstream number traces back to something agreed.

Capture delivery once

Shifts carry billing lines drawn from the client's active agreement, so delivered support becomes billable data as the roster runs, not in an end-of-month scramble.

Draft, review, send

Generate invoice drafts from delivered shifts for plan-managed and self-managed participants, review and edit every line, then download the PDF or send the invoice.

Export claims in the NDIS format

For billable support coordination time, claim outstanding activities in one step and download a CSV laid out for the NDIS bulk payment request upload, with your registration number already filled in, ready for you to lodge.

What you can do.

The NDIS catalogue in your workspace

Load the official support catalogue, search current and legacy items, and see pricing across states, remote and very remote areas.

Claim lines that trace to delivery

Payment-request data builds from billing lines on delivered shifts and claimed coordination activities, each tied to an agreement line item, never a separate spreadsheet.

One-step coordination claiming

Turn unclaimed billable coordination activities into a claim batch in a single action, totalled by line item, hours and amount.

Bulk-payment-request CSV

Download a CSV for claimed coordination activities that matches the NDIS bulk payment request layout: registration number, participant NDIS number, delivery dates, support item number, quantity, hours and unit price.

Registration number included

Your NDIS registration number comes from your organisation profile and is filled into every export automatically.

Invoices from the same data

Plan-managed and self-managed supports invoice from the same delivered-support records, addressed to the plan manager or the participant's billing contact.

BondiByte invoice detail for a demo client showing NDIS line items with catalogue rates, recipient and payment details, and draft actions — Delivered supports become reviewable lines with NDIS item codes and catalogue rates before anything is sent or claimed.

How it connects.

NDIS catalogue

Line items & budgets

Shift billing

Invoicing

Coordination claims (CSV)

Funds & budget burn

You stay in control.

Nothing lodges itself

BondiByte prepares the claim data and the export file. You review it and lodge it with the NDIS yourself, so nothing reaches the agency without your sign-off.

Batches stop double-claiming

Each claim run creates its own batch and the CSV export is scoped to that batch, so earlier cycles are never claimed again.

Invoices only pick up uninvoiced work

Generating an invoice draws in shift billing lines that have not been invoiced before, and every draft is yours to review, edit or regenerate before it goes anywhere.

Pricing stays your call

Catalogue data keeps codes and prices consistent, and you confirm them against the current NDIS Pricing Arrangements and Price Limits.

Learn how to use this feature.

View guide

Frequently asked questions.

Does BondiByte lodge claims with the NDIS for me?

No. BondiByte prepares claim-ready data and a bulk-payment-request CSV. You review the file and lodge it through your NDIS provider portal, so you always keep the final check.

What does the bulk claim export contain?

Everything the NDIS bulk payment request upload expects, one row per claimed activity: your registration number, the participant's NDIS number, delivery dates, the support item number, quantity, hours, unit price and GST code.

Where does the claim data come from?

From work already recorded: the NDIS catalogue in your workspace, line items on each client's agreement, billing lines on delivered shifts and billable support coordination activities. Nothing is re-typed.

Can something be claimed twice by mistake?

Claiming creates a batch and the export is scoped to it, so earlier claim cycles are not picked up again. On the invoicing side, generation only draws in billing lines that have not already been invoiced.

How are plan-managed and self-managed participants handled?

Their delivered supports become invoice drafts addressed to the plan manager or the participant's billing contact, generated from the same shift billing data and reviewed before sending.

More in Agreements & Billing.