Log billable work as you go
Each billable case note already carries its date, duration, support item and rate, because it was booked against a funded plan line when it was written. There is nothing to reconstruct at claim time.
Clients & Coordination
Claim coordination time in a click.
Turn billable coordination activity into an NDIS bulk-payment-ready export.
What you get with Coordination claims (CSV).
- Unclaimed to claimed in one action
Turn billable coordination time into a claim in a single step.
- NDIS bulk-claim CSV
Export a bulk-payment-ready CSV that matches the NDIS format.
- Includes the registration number
Your registration number is included automatically, so claims are ready to lodge.
Why it exists
The problem it solves.
Claiming coordination time usually means rebuilding a spreadsheet from case notes at the end of the month: finding what has not been claimed yet, matching it to support items, and retyping it all into the NDIS layout. It is slow, and one duplicated row can hold up the whole payment request.
How it works
Create the claim
One action gathers every unclaimed billable activity for the participant into a claim, summarised by support item with activity counts, minutes and dollar totals.
Review the summary
Check the support items, counts and totals on screen before anything is exported. Nothing leaves the workspace unreviewed.
Export the file
Download a CSV in the NDIS bulk payment request layout: your NDIS registration number, the participant's NDIS number, delivery dates, support item, hours, unit price and a unique claim reference on every row.
Lodge with the NDIS
Upload the file through your existing NDIS claiming process. Claimed activities stay claimed, so the next cycle starts from a clean slate.
What you can do.
Unclaimed to claimed in one action
Every billable, unclaimed activity for the participant is gathered into a claim in a single step, so nothing gets missed and nothing needs retyping.
NDIS bulk payment layout
The export follows the bulk payment request column layout, including registration number, NDIS number, delivery dates, support item, quantity, hours, unit price and GST code.
Registration number filled in for you
Your NDIS registration number is drawn from your organisation settings and stamped on every row.
One row per activity, each with a reference
Every activity exports as its own row with a unique claim reference, so queries from the NDIA can be traced back to the exact piece of work.
Claim cycles that stay separate
Each claim creates its own batch and the export covers the latest one, so earlier cycles are never re-exported by accident.
How it connects.
- Billable case notes
- Funds & budget burn
- Claim created
- CSV exported
- Lodged with the NDIS
You stay in control.
Nothing is claimed automatically. A manager or coordinator creates the claim, sees the summary and decides to export.
Non-billable notes and work without a funded line item never enter a claim, so the file only ever contains claimable time.
The file downloads for your review and is lodged through your existing NDIS process. BondiByte does not submit anything to the NDIA on your behalf.
Learn how to use this feature.
Frequently asked questions.
Is the export really in the NDIS bulk claim format?
The CSV follows the bulk payment request layout: registration number, NDIS number, supports delivered dates, support number, claim reference, quantity, hours, unit price and GST code, with supports marked GST-free. Review the file before lodging, as you would any claim.
Can the same time be claimed twice?
No. Creating a claim marks those activities as claimed in their own batch, and the export covers the latest batch, so earlier cycles do not reappear in later files.
Where does the registration number come from?
From your organisation settings. Enter your NDIS registration number once and every claim row carries it automatically.
Does BondiByte submit the claim to the NDIA?
No. You download the file, review it and lodge it through your existing NDIS claiming process. The decision to submit always stays with you.
What about non-billable case notes?
They stay on the participant's record for context but are never included in a claim. Only billable activities booked against funded line items are claimable.
More in Clients & Coordination.
Clients & Coordination
Participant Management
Participant onboarding, representatives and consent, billing profiles, and a full history and audit trail: the detail NDIS operations need, entered once.
Clients & CoordinationParticipant onboarding
Create the participant record once, properly: identity and NDIS number, contact and communication preferences, the people around them, plan management, and the rostering model that matches how they receive support. Everything downstream draws on it.
Clients & CoordinationRepresentatives & consent
Record a participant's representative and exactly what they're authorised to do.
Clients & CoordinationClient billing profile
Every participant pays differently: agency managed, plan managed or self managed. The billing profile holds who pays, where the invoice goes and how it should arrive, and BondiByte checks it is complete before an invoice can be sent.
Clients & CoordinationClient history & audit trail
Key changes to a participant are recorded with who did it and when.
Clients & CoordinationSupport Coordination
The whole coordination job in one workspace: the caseload, billable case notes, plan budgets and burn, goals, tasks, referrals, reports and NDIS-ready claims, with a clear record of who did what for every participant.
See Coordination claims (CSV) in BondiByte
Start your free trial, or book a demo to see it with your own operation in mind.