Home care agencies (non-medical home care and home health alike) have an operational core — caregiver scheduling, visit verification, care plans — that belongs in dedicated home care software, usually with Electronic Visit Verification (EVV) built in because several US states mandate it by law. Acumatica's honest role is payroll-adjacent back office and multi-location financial consolidation, not the caregiver-facing app.
EVV is a legal requirement Acumatica does not provide
The 21st Century Cures Act requires Electronic Visit Verification for Medicaid-funded personal care and home health services in the US, tracking who provided the service, what service, for whom, the date, and the location and time it began and ended. This is specialized, state-integrated software — EVV systems submit directly to state Medicaid aggregators. Acumatica has no EVV capability and does not integrate with state EVV aggregators. Any home care agency scoping Acumatica needs its EVV system already chosen and separate.
Where Acumatica fits: caregiver payroll complexity and multi-branch billing
Home care agencies have payroll and billing complexity that outgrows basic tools fast: caregivers paid at different rates for different service types, multiple payers per client (private pay, Medicaid, long-term care insurance) each with different billing rates for the same service, and often a multi-branch or franchise structure. That is squarely ERP territory, and Acumatica's project/task costing and multi-currency, multi-branch structure map reasonably well onto "cost center per branch, bill rate matrix per payer."
EVV / scheduling system
| approved visit: caregiver, client, service code, hours, date
| (client PHI/PII stays here)
v
Integration service — aggregates approved visits by
client-payer-service_code-period, drops caregiver/client identity
v
Acumatica REST API
-> AR invoice line per payer per period (private pay client:
may need a summarized "care services — March" line rather
than a named line per visit, to limit PHI exposure)
-> AP / payroll import for caregiver hours (via payroll system,
not Acumatica's own payroll if a specialized caregiver payroll
provider is already in use)
The private-pay tension: clients often want visit-level invoices
Unlike the Medicaid/insurance case where summary billing is both sufficient and preferable, private-pay home care clients (or their families) often expect an invoice itemizing each visit — date, duration, caregiver name. That is a legitimate business requirement that reintroduces some identifiable detail into Acumatica's AR. If an agency needs this, it is a deliberate, scoped exception: restrict the fields to what a family member reasonably needs to see (visit date, duration, caregiver first name), not full care-plan or health-condition detail, and apply the same field-level encryption and role restriction guidance covered in the HIPAA piece.
Franchise home care operations (a national brand, locally owned territories) often need each territory as its own legal entity for Acumatica's company structure, while still sharing a payer-rate matrix and reporting templates centrally. Get the company/branch decision right in design — retrofitting a single-company setup into multi-entity after go-live is a much bigger project than deciding it up front.
Wrapping up
Home care's clinical and scheduling core — and any EVV-mandated workflow — lives in dedicated home care software; Acumatica has no claim there. Its real fit is the payer-rate billing matrix and multi-branch/franchise financial consolidation, fed by summarized visit data from the scheduling system, with private-pay itemized billing handled as a deliberate, minimally-detailed exception.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.