• Claims being submitted for visits where the EVV record was not verified first -- resulting in Medicaid denials that could have been caught before the claim left the system?

  • Prior authorisation hours running out mid-month and the billing team only discovering it when a claim is rejected -- by which point multiple visits have been delivered without an authorised hour to bill against?

Home Care Medicaid and Medicare Billing Software

Home care billing is a multi-payer problem. Medicaid managed care organisations, Medicare, private long-term care insurance, and private pay each have different rates, billing units, and prior authorisation requirements. A single billing workflow built for one payer will create errors, denials, and compliance exposure when applied to the others.

We build custom billing software for home care agencies that need payer-specific configuration across the full payer mix. EVV-linked claim generation, prior authorisation hour tracking, multi-payer rate management, and denial handling -- built around the actual authorisation and verification requirements your payers impose.

  • EVV-linked claim generation

  • Prior authorisation hour tracking

  • Multi-payer rate management

  • Remittance posting and denial management

RaftLabs builds custom Medicaid and Medicare billing software for home care agencies. The system generates claims only from EVV-verified visit records, converting visit duration to billable units by payer rate table and holding unverified visits in a pre-submission review queue. Prior authorisation hours are tracked against a running balance per client per payer, with alerts when a client approaches the authorised hour limit. Multi-payer rate tables cover Medicaid fee-for-service, Medicaid managed care organisations, Medicare, long-term care insurance, and private pay -- each with payer-specific billing unit definitions and effective date tracking. Remittance posting from 835 files is automatic, with a denial rework queue by denial code and secondary billing for dual-eligible clients. Fixed cost, 12 to 14 week delivery.

Vodafone
Aldi
Nike
Microsoft
Heineken
Cisco
Calorgas
Energia Rewards
GE
Bank of America
T-Mobile
Valero
Techstars
East Ventures
Medicaid + MedicareMulti-payer
EVV-linkedClaim generation
FixedCost delivery
12-14Week delivery cycles

Home care billing built for Medicaid managed care, Medicare, and multi-payer complexity

Home care billing is harder than most healthcare billing because the units of complexity are different. Where a physician practice bills by CPT code and diagnosis, a home care agency bills by units of service -- typically 15-minute increments -- derived from a visit duration that must first be verified by an EVV record. The EVV verification step is not optional for Medicaid: an unverified visit cannot be billed, and submitting a claim without a valid EVV record is a compliance exposure the agency cannot afford. Prior authorisation adds another layer: every hour delivered must sit within an authorised block of hours that is finite and tracked against a running balance, with no automatic notification when that balance runs low.

Generic medical billing software handles CPT codes and fee schedules. It does not handle units of service derived from EVV visit duration, prior authorisation hour consumption tracking, or the rate differences between Medicaid fee-for-service and each managed care organisation the agency is contracted with. Agencies trying to manage multi-payer home care billing in a generic system end up with a combination of the billing software, a separate spreadsheet for prior auth tracking, and a manual EVV reconciliation step before each claims batch. Each handoff between those three systems is a place where errors enter and denials follow. We build the system that removes those handoffs.

What we build

EVV-linked claim generation

Claims are generated only from EVV-verified visit records -- a visit without a verified EVV record cannot produce a claim until the exception is resolved. Visit duration from the EVV check-in and check-out is converted to billable units by the payer's rate table, with rounding rules applied per payer specification. Visits with unresolved EVV exceptions are held in a pre-submission review queue visible to the billing team, with the exception type displayed so the coordinator or caregiver can resolve it without the billing team needing to investigate manually. Claim generation can be triggered automatically when a visit is verified or run as a manual batch by the billing team at the end of a billing period.

Prior authorisation management

Each client has an authorisation record per payer covering the approved hours, service type, and validity period for that authorisation. Authorised hours are consumed as visits are verified and billed -- the running balance updates with each verified visit so the remaining authorised hours are always current. Remaining hours are visible on the client record and in the scheduling view when a new visit is being assigned, so coordinators can see whether the client has hours available before the visit is scheduled rather than after the claim is rejected. An alert fires when a client is within a configurable threshold of exhausting their authorised hours, giving the agency time to submit a renewal request before the authorisation runs out. Prior authorisation renewal requests are tracked with submission date, payer response, and new authorisation details recorded when approved.

Multi-payer rate management

Rate tables are configured per payer: Medicaid fee-for-service, Medicaid managed care organisations by plan, Medicare, long-term care insurance, and private pay. Service codes and rates are managed per payer with effective date tracking so rate updates are applied from the correct date without requiring manual correction of past claims. Payer-specific billing unit definitions are configured at the payer level -- some payers bill in 15-minute increments, others at a daily rate or a per-visit rate -- and the claim generation logic applies the correct unit definition per payer without the billing team selecting it manually for each claim. When a contracted rate is updated, an alert notifies the billing team before the new rate takes effect so rate changes are not missed until a claim is paid at the wrong amount.

Claim submission and tracking

Electronic claim submission to Medicaid and Medicare via 837P transaction or state-specific billing portal, configured for the submission method required by each payer. Each claim has a tracked status -- accepted, pending, rejected, and paid -- updated as payer responses are received. A rejection alert includes the denial reason code and the resubmission guidance relevant to that code so the billing team knows immediately what action is required. Claims are managed in batches with a submission log per batch: submission date, number of claims, total billed amount, and confirmation numbers from the payer so the billing team can reconcile what was sent against what was acknowledged.

Remittance posting and denial management

835 remittance files from each payer are processed automatically with payment and adjustment amounts posted to the corresponding claims. Denial reason analysis groups denied claims by denial code into a rework queue so the billing team can see where the same denial is recurring across multiple claims rather than working each denial individually. For clients with dual eligibility -- covered by both Medicaid and Medicare -- secondary billing is generated after the primary payment posts, with the client liability calculated from the combined primary and secondary payment. Payment reconciliation reports match posted payments against deposit records so the billing manager can confirm the bank deposit matches the remittance totals.

Billing reporting and cash flow

Accounts receivable by payer with aging buckets -- current, 30 days, 60 days, 90 days, and over 90 -- so the billing team can see where collections are running behind and which payers are slow to pay. Denial rate by payer and by service code over a rolling period identifies systemic billing problems rather than one-off errors. Collection rate by payer shows what percentage of billed amounts are being collected from each payer over time, which informs contract renegotiation and payer mix decisions. Revenue per authorised hour measures how efficiently the agency is using its prior authorisation capacity. Cash flow forecast based on claims submitted and the average payment timeline per payer gives the finance team a forward view of receivable collections.

Frequently asked questions

EVV linkage makes the billing workflow more accurate at the cost of requiring a verification step before any claim is generated. In a linked system, the billing team cannot accidentally submit a claim for a visit that was never verified -- the claim simply does not exist until the EVV record is confirmed. Visits with EVV exceptions appear in a pre-submission queue where the exception type is visible: a visit where the caregiver's GPS location didn't match the client's address, a visit where check-out was not recorded, or a visit where the visit duration in the EVV system differs from the scheduled duration. The billing team or coordinator resolves the exception before the claim is generated, which means Medicaid denials for EVV non-compliance are caught before submission rather than after the payer rejects the claim.

The answer depends on the state and the aggregator the state uses for EVV data -- Santrax, HHAeXchange, Authenticare, and FirstData are the most common. We build the integration for the EVV aggregator or state portal your agency is already enrolled with. For 837P electronic claim submission, we configure the transaction to the clearinghouse your agency uses -- Availity, Change Healthcare, and Waystar are the most common -- which handles the onward submission to each state Medicaid programme. If your agency bills a Medicaid managed care organisation directly rather than through fee-for-service, we configure the submission method that MCO requires, which may be a portal submission or a direct EDI connection rather than a clearinghouse.

Dual-eligible billing follows a coordination of benefits sequence: Medicare is billed first as the primary payer, and after the Medicare payment and any Medicare-determined patient liability posts, the secondary Medicaid claim is generated for the remaining balance. The system tracks the primary payment and adjustment amounts from the 835 remittance and uses them to calculate the secondary claim amounts, so the billing team does not need to manually calculate what Medicaid owes after Medicare pays. The client's own liability -- the amount remaining after both payers have paid -- is calculated from the combined remittance and posted to the client account. The dual-eligible billing workflow is configured at the client record level so it applies automatically every time a dual-eligible client's claims are processed.

A billing system covering EVV-linked claim generation, prior authorisation management, multi-payer rate tables, electronic claim submission, and remittance posting typically takes 12 to 14 weeks from requirements sign-off to go-live. Adding denial management workflows, dual-eligible coordination of benefits, and detailed cash flow reporting extends the timeline to 16 to 18 weeks. Integrations with a state EVV aggregator or a specific MCO billing portal add time depending on the technical specifications of the payer's system. Cost is fixed and agreed before development starts based on the payer mix, EVV aggregator, clearinghouse, and reporting requirements scoped in discovery. We run parallel billing on the new and existing systems for at least two claims cycles before the agency switches over so the billing team can verify the output before going live.

Related senior care software

Talk to us about your home care billing project.

Tell us your payer mix, current billing workflow, and where claims are being denied. We will scope a billing system built around your authorisation and EVV requirements.