Switching Systems This EOFY? Here's What to Look For in Care Management Software

If you are going to change your care management software, the end of financial year is the right time to do it — but only if you choose a system built for the post-November 2025 reality of Support at Home, the NDIS's new computer system, and a SCHADS Award that has become one of the most complex in the country. Get the criteria right and EOFY gives you a clean budget line, a tax-deductible subscription, and a 1 July go-live that lines up with the new financial year. Get them wrong and you will spend FY27 doing manual workarounds on a platform that cannot keep up.

EOFY is the natural switching window because budget cycles reset on 1 July, SaaS care software is fully tax-deductible as an operating expense in the year you incur it, and a 1 July go-live aligns with the annual SCHADS wage increase and new-financial-year planning. The pain driving most switches is structural: administration now consumes 25.6% of home care revenue while margins have collapsed — StewartBrown's December 2025 survey puts year-to-date home care EBITDA at just $760 per client per annum, which it describes as 'a low point and at this level it is not investable.'

The non-negotiable evaluation criteria for 2025–26 are compliance-led: B2G/PRODA integration and conformance-assessed Support at Home claiming; NDIS bulk-upload claiming and Practice Standards workflows; embedded SCHADS award interpretation; clean data migration; payroll/accounting integration; genuine mobile/field functionality; and vendor stability. If a vendor cannot demonstrate these, nothing else matters.

Switching risk is real but manageable — data loss, downtime, and retraining are the top fears — and the differentiator is implementation support, not features. Insist on a dedicated implementation manager, mapped data migration, parallel running, and reference calls with providers your size. Treat 6–12 month implementations and 'disappear after go-live' vendors as red flags.

Six findings should shape your evaluation before you read further. First: the financial case for change has never been more urgent — StewartBrown's December 2025 survey recorded year-to-date home care EBITDA of $760 per client per annum, described as 'a low point and at this level it is not investable,' down from $1,557 a year earlier. Second: Support at Home fundamentally changed claiming, and manual processing is now a compliance risk — providers must submit per-service claims within 60 days, issue monthly statements to every participant, and manage quarterly budgets with strict rollover caps. Third: B2G integration is the single most important technical criterion — conformance-assessed software is the difference between a two-hour month-end and a two-day one. Fourth: NDIS administrative load is documented and severe — NDS found that 81% of providers say they cannot keep delivering NDIS services at current prices, and only 3% say NDIS systems are working well. Fifth: SCHADS is a structural compliance risk that software must absorb — the award split into separate streams in January 2025, intentional underpayment became a criminal offence, and the Fair Work Ombudsman recovered $40.5 million for 22,000 underpaid aged care workers in 2023–24. Sixth: the tax treatment favours EOFY timing — SaaS subscriptions are deductible operating expenses, not capital assets, and prepaying up to 12 months before 30 June can bring the deduction into the current year.

End of financial year concentrates procurement decisions across Australian business, and care is no exception. Three forces converge on 30 June.

Budget cycles reset. Most care organisations set annual operating budgets aligned to the financial year. EOFY is when boards and executives review performance against budget and approve the next year's capital and operating plan, making it the natural decision point for a software commitment.

Tax timing is favourable. The ATO treats software subscription fees as operating expenses deductible in the year incurred — its guidance explicitly lists 'client management software' as an example. SaaS subscriptions are not depreciating assets and sit outside the instant asset write-off, but they are fully deductible as ordinary operating expenses. Under the 12-month prepayment rule, a small business can prepay up to 12 months of a subscription before 30 June and claim it in the current year.

A 1 July go-live aligns with everything else. The annual SCHADS wage increase takes effect from the first full pay period on or after 1 July, so a new-financial-year cutover means your new system carries the new award rates from day one rather than mid-cycle. New plans, budgets, and reporting periods also align cleanly with a 1 July start.

The countervailing reality: 30 June to August is also the busiest compliance period for Support at Home providers. Q4 claims are due within 60 days of quarter end, and care management account claims must be finalised by 29 August. The smart pattern is to contract and migrate in the April–June window and go live on 1 July — before the end-of-quarter claiming crunch.

Support at Home compliance is non-negotiable. The system must handle per-service claim generation, PRODA/ACPP reconciliation, automated monthly statement production (issued by the last day of the following month, even with zero services delivered), quarterly budget tracking with correct rollover logic ($1,000 or 10% of quarterly budget, whichever is greater), and the mandatory 10% care management account. It must also support the requirement to deliver and document at least one direct care management activity of at least 15 minutes per participant per month.

B2G API integration is the most important technical criterion. Confirm the product is on the B2G Conformance Register maintained by the Australian Digital Health Agency, or has a clear, dated roadmap to conformance. Ask specifically about PRODA device registration support — B2G device activations expire every six months — and ACPP integration.

NDIS compliance covers bulk payment request generation and validation for the myplace/PACE environment, support across all 15 support categories and item codes, incident reporting workflows, worker screening clearance tracking, restrictive practices documentation (the Commission's enforcement priority), and 7-year audit-ready record retention. With the NDIS Amendment (Integrity and Safeguarding) Act 2025 introducing civil penalties up to $15 million and mandatory SIL/platform registration from 1 July 2026, audit-readiness is now existential.

Rostering and SCHADS compliance require the system to embed award interpretation — minimum engagement, broken shifts, sleepovers, overtime triggers, penalty rates — across both aged care and disability home care streams (separated since January 2025), flag compliance risks before a shift is published, and calculate true roster cost including travel and cancellation. Verify the vendor updates rates automatically each 1 July.

Data migration and onboarding support is where switches succeed or fail. Insist on documented data mapping from your legacy system, a test migration on a subset, validation of record counts and financial totals reconciled, and a defined cutover plan. Expect 24–48 hours of reduced access during cutover and plan for parallel running.

Integration with payroll, accounting, and other systems cannot be an afterthought. Award-interpreted rostering must flow to payroll; claims and participant contributions must reconcile to your accounting system. Avoid platforms that export CSVs you then manually re-key.

Mobile and field worker functionality is the single biggest lever on front-line admin. Care workers absorb up to two hours of admin per day. Genuine mobile functionality — schedules, care notes (ideally voice-to-text), shift records, and incident capture in the field — is essential, not optional.

Vendor stability and longevity — you are committing years of operational dependency. Assess financial stability, Australian sector focus, track record through the Support at Home and NDIS transitions, and product roadmap including AI-assisted claiming and rostering. A vendor that does not understand PRODA, ACPP, DEX, and SCHADS in detail is not a serious candidate.

Support at Home compliance is non-negotiable. The system must handle per-service claim generation, PRODA/ACPP reconciliation, automated monthly statement production (issued by the last day of the following month, even with zero services delivered), quarterly budget tracking with correct rollover logic ($1,000 or 10% of quarterly budget, whichever is greater), and the mandatory 10% care management account. It must also support the requirement to deliver and document at least one direct care management activity of at least 15 minutes per participant per month.

B2G API integration is the most important technical criterion. Confirm the product is on the B2G Conformance Register maintained by the Australian Digital Health Agency, or has a clear, dated roadmap to conformance. Ask specifically about PRODA device registration support — B2G device activations expire every six months — and ACPP integration.

NDIS compliance covers bulk payment request generation and validation for the myplace/PACE environment, support across all 15 support categories and item codes, incident reporting workflows, worker screening clearance tracking, restrictive practices documentation (the Commission's enforcement priority), and 7-year audit-ready record retention. With the NDIS Amendment (Integrity and Safeguarding) Act 2025 introducing civil penalties up to $15 million and mandatory SIL/platform registration from 1 July 2026, audit-readiness is now existential.

Rostering and SCHADS compliance require the system to embed award interpretation — minimum engagement, broken shifts, sleepovers, overtime triggers, penalty rates — across both aged care and disability home care streams (separated since January 2025), flag compliance risks before a shift is published, and calculate true roster cost including travel and cancellation. Verify the vendor updates rates automatically each 1 July.

Data migration and onboarding support is where switches succeed or fail. Insist on documented data mapping from your legacy system, a test migration on a subset, validation of record counts and financial totals reconciled, and a defined cutover plan. Expect 24–48 hours of reduced access during cutover and plan for parallel running.

Integration with payroll, accounting, and other systems cannot be an afterthought. Award-interpreted rostering must flow to payroll; claims and participant contributions must reconcile to your accounting system. Avoid platforms that export CSVs you then manually re-key.

Mobile and field worker functionality is the single biggest lever on front-line admin. Care workers absorb up to two hours of admin per day. Genuine mobile functionality — schedules, care notes (ideally voice-to-text), shift records, and incident capture in the field — is essential, not optional.

Vendor stability and longevity — you are committing years of operational dependency. Assess financial stability, Australian sector focus, track record through the Support at Home and NDIS transitions, and product roadmap including AI-assisted claiming and rostering. A vendor that does not understand PRODA, ACPP, DEX, and SCHADS in detail is not a serious candidate.

The fears are predictable: data loss, downtime, staff retraining burden, and cost overrun. They are also manageable — and the differentiator is implementation support, not features.

Real implementation support means a dedicated project manager and professional services consultant assigned from contract signing, mapped and migrated data, a structured training program, and a post-go-live stabilisation period spanning at least one or two complete billing and payroll cycles before handover to account management. Best practice includes running the old and new systems in parallel for at least two weeks before full cutover, and nominating an internal champion who owns the rollout.

Typical timelines vary by scope. A single module for a mid-sized provider can be done in four to six weeks; a full multi-module, multi-site rollout is more typically eight to twelve weeks. Enterprise platforms with complex organisations can run three to six months — independent software-review (G2) benchmark data puts one large platform's average time-to-go-live at around six months. Use these as sanity checks against vendor promises.

To evaluate track record, ask for reference calls with two or three providers of similar size and complexity. Ask them specifically about the implementation timeline, support responsiveness, and what surprised them. Ask the vendor how many providers they migrated through the November 2025 Support at Home transition — and ask for references from those migrations.

The fears are predictable: data loss, downtime, staff retraining burden, and cost overrun. They are also manageable — and the differentiator is implementation support, not features.

Real implementation support means a dedicated project manager and professional services consultant assigned from contract signing, mapped and migrated data, a structured training program, and a post-go-live stabilisation period spanning at least one or two complete billing and payroll cycles before handover to account management. Best practice includes running the old and new systems in parallel for at least two weeks before full cutover, and nominating an internal champion who owns the rollout.

Typical timelines vary by scope. A single module for a mid-sized provider can be done in four to six weeks; a full multi-module, multi-site rollout is more typically eight to twelve weeks. Enterprise platforms with complex organisations can run three to six months — independent software-review (G2) benchmark data puts one large platform's average time-to-go-live at around six months. Use these as sanity checks against vendor promises.

To evaluate track record, ask for reference calls with two or three providers of similar size and complexity. Ask them specifically about the implementation timeline, support responsiveness, and what surprised them. Ask the vendor how many providers they migrated through the November 2025 Support at Home transition — and ask for references from those migrations.

The regulatory environment is at an inflection point. Support at Home commenced 1 November 2025 under the Aged Care Act 2024, replacing Home Care Packages and Short-Term Restorative Care; CHSP transitions no earlier than 1 July 2027 and continues its DEX reporting in the meantime. The NDIS is mid-reform: the Amendment (Integrity and Safeguarding) Act 2025, mandatory SIL/platform registration from 1 July 2026, and a claims and payments system uplift beginning July 2026. SCHADS has split streams, criminalised intentional underpayment, and faces a gender-undervaluation classification overhaul.

Financial pressure is acute. StewartBrown's data is the clearest evidence: home care operating results nearly halved over four years before Support at Home, admin and support costs run at a quarter of revenue, and the sector's post-reform EBITDA is described as 'not investable.' StewartBrown's December 2025 report states operators 'will have to increase service prices by an average of 35% and 40%' to maintain margins — actual median service-price increases between HCP and Support at Home already averaged 38%.

The government's digital agenda is unambiguous. The Aged Care Data and Digital Strategy 2024–2029 commits to digitising, automating, and connecting aged care, backed by roughly $1 billion in the 2024 Budget for digital systems. The Royal Commission's Recommendation 68 called for universal adoption of interoperable digital care management systems and found the sector 'deeply analogue and well behind other sectors in the use and application of technology.'

Technology adoption remains low — and that is the opportunity. The ACIITC report found the sector scored an average digital maturity of 58.4 out of 109 across 165 providers representing 56,000 places. Only 14% of aged care providers use fully integrated software systems, and three-quarters had no digital literacy criteria in recruitment. Providers that modernise now will pull ahead of a largely analogue field.

Budget: treat the subscription as an operating expense in next year's budget. Capture any one-off implementation or migration cost in the current year if it can be incurred before 30 June.

Tax: SaaS subscriptions are deductible operating expenses — not instant asset write-off items. Under the 12-month prepayment rule, a small business can prepay up to 12 months before 30 June and claim it in the current year. Confirm with your accountant for your entity and circumstances.

Go-live timing: contract and migrate April–June; go live 1 July to align with the SCHADS wage increase and new budgets, and to clear the system before the Q4 Support at Home claiming deadline and the 29 August care management account finalisation.

Procurement and tender: larger and government-funded providers may run formal tenders. Start early — allow 3–6 months lead time — define compliance must-haves up front (B2G conformance, SCHADS interpretation, SAH statements), and weight implementation support and references heavily over headline licence price.

Budget: treat the subscription as an operating expense in next year's budget. Capture any one-off implementation or migration cost in the current year if it can be incurred before 30 June.

Tax: SaaS subscriptions are deductible operating expenses — not instant asset write-off items. Under the 12-month prepayment rule, a small business can prepay up to 12 months before 30 June and claim it in the current year. Confirm with your accountant for your entity and circumstances.

Go-live timing: contract and migrate April–June; go live 1 July to align with the SCHADS wage increase and new budgets, and to clear the system before the Q4 Support at Home claiming deadline and the 29 August care management account finalisation.

Procurement and tender: larger and government-funded providers may run formal tenders. Start early — allow 3–6 months lead time — define compliance must-haves up front (B2G conformance, SCHADS interpretation, SAH statements), and weight implementation support and references heavily over headline licence price.

Recommendations

Now (April–June): shortlist on compliance, not features. Disqualify any vendor that is not B2G conformance-assessed (or without a dated roadmap), cannot demonstrate live Support at Home claiming and monthly statements, and cannot show embedded SCHADS award interpretation across both home care streams. These are pass/fail criteria.

Before you sign: pressure-test implementation. Require a written implementation plan with a named project manager, a mapped data-migration approach with a test migration, parallel-running provision, and a fixed implementation cost. Complete two to three reference calls with same-size providers. If the vendor quotes 6–12 months or treats migration as your problem, walk away.

Time the cutover deliberately. Contract and migrate in the lead-up to 30 June; schedule go-live for 1 July to capture the new SCHADS rates, the new budget year, and the tax-deductible subscription — while staying clear of the Q4 claiming crunch.

Confirm the tax position with your accountant before committing, specifically whether to prepay up to 12 months of the subscription before 30 June to bring the deduction forward.

The benchmarks that should change your decision: if a shortlisted vendor cannot show it migrated providers through the November 2025 Support at Home transition, downgrade it. If references report support that 'disappeared after go-live,' remove it. If implementation cost is open-ended or migration is excluded, treat the headline licence price as fiction. If the platform requires you to manually maintain award rates, it will create the exact SCHADS underpayment exposure you are trying to eliminate.

A note on caveats: most implementation-timeline figures come from vendors with incentives to claim fast, easy migration — treat specific week/month claims as marketing until verified through references. The tax treatment information above is general, not advice — confirm with your accountant. StewartBrown's December 2025 Support at Home data covers only two months of post-reform data and its March 2026 quarter report will be more informative. The regulatory environment is still moving: Support at Home price caps were deferred, the NDIS claims system uplift runs to 2030, and the SCHADS gender-undervaluation classification restructure is provisional. Build for change, and favour vendors who treat regulatory updates as their job, not yours.