NDIS & Disability Services · NDIS care management
Lumary
integration & API.
Enterprise NDIS care management built on Salesforce — we add bespoke participant portals and reporting.
L What is Lumary?
Lumary in plain English.
Lumary is an Australian-built, Salesforce-native NDIS and aged care management platform used by larger Australian disability services and aged care providers. Lumary handles participant management, support worker rostering, NDIA claim submission via the NDIA API Integration Module, and audit-ready record-keeping aligned with the Aged Care Act 2024 Strengthened Quality Standards. Particularly strong for multi-program enterprise providers serving both NDIS and aged care funding streams. Public APIs available via the underlying Salesforce platform, with documented integration partner programme.
What businesses use it for
Common Lumary
use cases.
- 01 NDIS participant management for multi-program providers
- 02 Support worker rostering with qualification matching
- 03 NDIA claim submission and reconciliation
- 04 Audit-ready record-keeping for ASIC and NDIS Quality and Safeguards Commission
- 05 Service planning and progress tracking
- 06 Multi-program operational reporting
Why custom?
Beyond the default Lumary integrations.
Lumary is the leading enterprise NDIS care management platform in Australia, built on Salesforce. We build the bespoke layer enterprise NDIS providers need: branded participant portals, claim automation tailored to the provider's service catalogue, and reporting that pulls cleanly across programs.
What we build with Lumary
Common Lumary integrations.
Branded participant portals on top of Lumary records
Claim automation tailored to specific service catalogues
Cross-program reporting that consolidates across Lumary data
Salesforce-native customisation for NDIS-specific workflows
Integration between Lumary and accounting / payroll systems
AI-assisted case note summarisation respecting Lumary data boundaries
Commonly paired with
Lumary works with the rest of your stack.
How we build
Production-grade.
Not Zapier in a trench coat.
Every Lumary integration we ship handles failure properly: idempotent jobs, retry logic, dead-letter queues for unrecoverable cases, and observability so you can see exactly where data is at any moment.
Tested
Real test suite, real edge cases. Not just "it worked once."
Observable
You see what is happening — events logged, errors surfaced.
Maintainable
Documented, version-controlled, handed over properly.
More NDIS & Disability Services
Other ndis & disability services platforms we connect.
A AlayaCare
Dominant ANZ home care and residential aged care platform — we build bespoke participant portals, family portals and B2G reporting layers.
B Brevity
Mid-market NDIS platform with strong rostering — we build participant portals and bespoke automation.
S ShiftCare
Rostering-focused care platform popular with NDIS support coordinators — we add participant portals and integration depth.
C Carelink+
Long-running Australian care management platform with broad NDIS adoption — we add the bespoke supporter-facing layer.
FAQ
Common questions about Lumary integration.
Do you replace Lumary?
No — Lumary handles the regulatory engine well. We build the bespoke layer (participant portals, claim automation, reporting) alongside it.
Can you customise Lumary directly?
Yes — Lumary is built on Salesforce, so we can extend it via Salesforce customisation as well as building external bespoke layers that integrate via API.
How do you handle Privacy Act and NDIS Quality and Safeguards Commission requirements?
Privacy is foundational. Australian data residency, encryption, audit logging, and explicit access controls appropriate to participant data are engineered from the schema up.
Related reading
Thinking we’ve published on this kind of work.
Cliniko API integrations: practitioner's guide for AU clinics
A practitioner's view of the Cliniko API surface — what it covers, where it stops, and the integration patterns Australian allied-health practices use to build the layer Cliniko doesn't ship natively.
Mindbody to Cliniko migration: technical realities for AU clinics
The technical realities of moving an Australian wellness, recovery or multi-modality clinic off Mindbody and onto Cliniko — what transfers cleanly, what doesn't, where the workarounds live, and what timeline to plan against.
simPRO API integrations: connecting AU trades to the stack
A practical view of the simPRO API surface — what it covers, where it stops, and the integration patterns Australian commercial trades operators use to build the layer simPRO doesn't ship natively.
Get started
Ready to wire up
Lumary?
A 30-minute scoping call — no pitch deck, no hard sell. Tell us what you're trying to connect and we'll tell you straight whether it's a fit.