Every funded support sits on the agreement as a line item: the NDIS code, unit price, quantity and budget, entered once. Shifts, invoices and claims all draw from those same lines.
Short demonstrations in the real product, using made-up data. Choose a part to watch it here.
Watch the full series on YouTube (opens YouTube in a new tab)
Build agreements from the real NDIS catalogue, so supports and codes are correct.
Set funded amounts per support, the foundation for budget tracking and claims.
Line items flow into budget burn and claim data, with nothing entered twice.
Line items entered once on the agreement carry through to reviewable invoice drafts.
Funded supports usually live in a plan PDF and a spreadsheet, then get retyped into the agreement, the roster and the invoice separately. Every retype is a chance for a wrong code, an out-of-date price or a mismatch between what was agreed and what gets billed. Keeping budgets honest across all of that by hand is close to impossible.
Add each funded support to the agreement from the NDIS catalogue, which BondiByte keeps up to date for you. The item code, name, unit and price come across automatically, and you can enter a custom line when something sits outside the catalogue.
Bring in a set of lines at once with the BondiByte CSV template, matched to your catalogue, or, where your organisation has that capability enabled, capture them from a screenshot of an existing agreement or plan. Either way, the lines land as a review step, not a save.
Give each line a quantity, a funded budget amount, optional start and end dates and notes. The agreement's supports table and budget total build themselves from the lines.
The price is captured on the line the moment you add it, so the agreement keeps saying what was agreed even after catalogue prices change.
When an agreement reaches its start date it automatically becomes the client's active agreement, its line items appear for shifts and Smart Rostering, and your admins are notified.
Billing lines on shifts point back to agreement line items, and invoices generate from delivered shifts, so what you bill is always anchored to what was agreed.
Choose from the NDIS catalogue, which BondiByte keeps up to date for you, and the code, support name, unit and price fill in for you.
Not everything fits a catalogue item. Add a manual line with its own code, name, unit and price, and it behaves like any other.
Record the funded amount for each support and watch the agreement total add itself up.
Give individual lines their own date ranges and notes when supports start or stop at different times.
Deactivate a line that no longer applies and reactivate it later if needed. Nothing disappears from the record.
Active agreement lines are what shift billing offers and what invoices generate from, so nothing is entered twice.
Bring in a batch of line items with the BondiByte CSV template, matched against your NDIS catalogue for review before anything saves.
Where your organisation has the capability enabled, a screenshot of an existing agreement or plan can be read into draft lines, reviewed the same way as an import.
Once an agreement is signed, its line items are locked. Changes go into a new agreement, which keeps the trail clean.
The catalogue keeps line items consistent, but confirming supports and prices against the current NDIS Pricing Arrangements and Price Limits stays with you.
When an agreement reaches its start date and goes active, admins are notified, so line items never start driving billing silently.
From the NDIS catalogue, which BondiByte keeps up to date for you. When you add a line, the price at that moment is captured on the line, and you confirm it against the current NDIS Pricing Arrangements before relying on it.
Lines already on agreements keep the price that was agreed. BondiByte keeps the catalogue up to date for you, and new lines pick up the new prices.
Yes. Enter the code, name, unit and price yourself and the line works exactly like a catalogue-backed one.
Yes. Import a batch with the BondiByte CSV template, matched against your catalogue, or use screenshot-assisted capture where your organisation has that capability enabled. Neither one saves automatically: you review the catalogue match, quantities and budgets first.
No. A signed agreement is read-only, including its lines. If supports change, you set up a new agreement that reflects the change and send it for signature, and the signed original stays intact.
Active agreement lines are what you attach to a client's shifts as billing lines. Invoice drafts then generate from those delivered shifts, so every invoice traces back to the agreement.
From a configurable template with auto-filled details and funded-supports line items to a signed, locked PDF, in one flow.
Agreements & BillingWrite your agreement once, in your words and with your logo. Every client agreement then fills itself with their details, plan manager, dates and funded supports, ready to preview, publish and send for signature.
Agreements & BillingSend agreements and contracts for E-signature straight from the record. Clients and staff sign on any device without an account, and the exact document they signed is stored, timestamped and locked.
Agreements & BillingShifts become draft timesheets carrying pay levels and sleepover components, ready for approval and payroll.
Agreements & BillingShift billing line items flow into draft invoices, with PDFs, invoice email and your payment details.
Agreements & BillingCatalogue item numbers on every agreement and billing lines on every delivered shift feed your invoices, and coordination time is claimed in batches into a claim file (CSV) per participant. When it is time to prepare your NDIS claims, the numbers are already there and they trace back to delivered support.
Start your free trial, or book a demo to see it with your own operation in mind.
Hi, I can help with BondiByte features, pricing, setup and more.
Please don’t include sensitive participant or personal information.