Integrations

Rostery connects to Xero over OAuth and pushes invoices as individual line items, so travel, transport and each support type land in your accounts separately rather than as a single total.

• Connect your Xero organisation once; Rostery refreshes the token itself from then on.
• Push invoices for a chosen date range, with each support line kept as its own line item.
• Push approved payroll figures across to Xero rather than rekeying them.
• Set the account code and tax treatment used for NDIS supports, so GST-exempt lines post correctly.
• See the last sync time and how many records went across, so a partial sync is visible.

A direct QuickBooks Online connection with the same invoice and payroll push as Xero, for providers whose accountant works in QuickBooks.

• OAuth connection to your QuickBooks Online company file.
• Invoice sync with per-line detail preserved.
• Payroll figures pushed from approved timesheets.
• Disconnect cleanly without touching what has already posted.

Rostery generates a MYOB-format CSV for accounts receivable, and for plan managers a MYOB-format bill file for provider payments.

• Export invoices as a CSV MYOB imports directly into accounts receivable.
• For plan management, export provider bills in MYOB’s format alongside Xero and QuickBooks options.
• Choose your accounting package once in settings; exports follow that choice.

Rostery builds the NDIS bulk payment request file from approved invoices, validated against the current price guide and the participant’s remaining budget before you upload it.

• Generate the bulk upload CSV in the structure the portal expects.
• Validate every line against the loaded Support Catalogue before the file is produced.
• Check remaining funds in the right budget category, so an underfunded line is caught early.
• Record the result of every claim line, so a formatting failure is distinguishable from a funding failure.
• Reconcile the remittance back against what was claimed — automatically, or by hand when a file cannot be read.

PRODA is the Australian Government identity service you use to reach the NDIS provider portal. Rostery produces the files you upload through it and keeps the claim results against your records.

• Works alongside your existing individual PRODA accounts — no shared credentials.
• Produces claim files ready for portal upload.
• Stores per-line claim results against the originating invoice for audit.

For providers approved for NDIA B2B Connector access, Rostery can submit claims directly to the NDIA API instead of uploading a CSV by hand.

• Direct claim submission against the NDIA provider API.
• Sandbox and production environments, so you can validate before going live.
• Requires your own B2B Connector registration with the NDIA.

Send approved timesheet data to Employment Hero for payroll processing, so award interpretation happens once in Rostery and the result flows through.

• Push approved timesheets for a pay period.
• Keeps SCHADS interpretation in Rostery rather than duplicating rules in two systems.
• Records what was sent and when.

A connection for providers using Pay Cat for payroll, sending approved pay data across from Rostery’s award interpretation.

• Push approved pay data for a period.
• Configured with your own API credentials in settings.

Sync staff records to intelliHR so people data stays consistent between your HR system and the roster.

• Push staff records to intelliHR.
• Keeps the roster and the HR system working from the same employee list.

Push the roster into Google Calendar so shifts appear in the calendar your team already checks, with participant, time and instructions carried across.

• OAuth connection to a Google account, refreshed automatically.
• Sync shifts for a chosen period into a calendar.
• Carries staff name, shift type and instructions onto the event.

Connect a shared mailbox through Microsoft Graph so provider invoices emailed to your plan-management inbox are read into Rostery without anyone forwarding them.

• Modern authentication through Microsoft Graph, so it works after basic-auth IMAP was retired.
• Reads a shared or team mailbox on a schedule.
• Attachments are pulled in and attached to the invoice they belong to.

Rostery runs a remote MCP server, so your organisation can connect Claude or ChatGPT to its own data and ask operational questions in plain language.

• Ask about rosters, participants, progress notes and incidents conversationally.
• Per-organisation OAuth — one org’s assistant never reaches another org’s data.
• Operations only: money, payroll, timesheets and invoices are deliberately excluded.
• Respects the connecting user’s role and permissions.

Sync participant and enquiry contact details into HubSpot for providers who run intake and marketing through a CRM.

• Push active participant contacts into HubSpot CRM.
• Uses your own HubSpot private app token.
• Existing contacts are matched rather than duplicated.

Bring participants, staff, shifts, notes and funding across from another care system using a guided import that maps columns with AI assistance and can be reversed.

• Reads exports from other NDIS care systems including ShiftCare, Brevity and Lumary.
• Suggests column mappings rather than requiring an exact template.
• Resolves relationships between participants, staff and shifts.
• Dry-run the whole import, review it, then commit — or undo it.