Inclusi

Integrations

What Inclusi connects to, what is in beta, and what is a file a person uploads.

What it does

  • Xero (beta)Issued invoices sent once each with mapped accounts and tax codes, credit notes, and payments pulled back. Granular scopes only.
  • MYOB and QuickBooks Online (beta)Contacts and invoices. Test with your own file before you rely on them.
  • Single sign-on (beta)OpenID Connect or SAML 2.0 with Microsoft Entra ID, Google Workspace, Okta or another provider.
  • Webhooks and API keysSigned, retried webhooks for shifts, enquiries, agreements, incidents, claims, invoices and participants; scoped, revocable API keys; a public API with participant and enquiry writes and subscribe-and-unsubscribe hooks for tools such as Zapier.
  • AI assistant connector (off by default)A read-only connector for an AI assistant your organisation chooses, inside an API key's access, with every question in the audit log.
  • Files for other systemsNDIA bulk claim files, Services Australia claim files, ABA bank files and payroll exports, each with a recorded upload.

Where Inclusi stops

  • Claims are files a person uploads. The direct NDIA, Services Australia and Tyro Health claiming adapters are built but switched off, and have been tested only against Inclusi's own mocks.
  • Each accounting connection starts once Inclusi's app is registered with that provider, and stays beta until it has been tested against the real service.

Works with

  • Billing and NDIS claiming

    Invoices from delivered shifts, checked against claiming rules, price limits, agreements and funding, with NDIA bulk claim files, credit notes and reconciliation.

  • Timesheets and payroll

    Timesheets from attendance, an award engine with a SCHADS rule-set template, leave accrual, Payday Super, pay slips and payroll export with STP Phase 2 columns.

  • For larger organisations

    Multi-branch organisations: branches and regions, custom roles, single sign-on, API keys and webhooks, and audited support access.