When Your State's Childcare Subsidy System Fails: Lessons from Missouri and Michigan

Missouri, December 2023: $191 Million Stranded

Missouri switched its CCDF billing vendor in December 2023. The transition failed.

Of $215 million in CCDF funds, $191 million were left undistributed. Not temporarily delayed — undistributed for weeks, during the period when providers most need payment to cover end-of-year operating costs and December payroll.

The providers hardest hit were those who had no independent billing records. Their claim data lived in the state system. When the system failed, they could not tell regulators exactly what they were owed, when they submitted, or what the correct payment should have been. They were dependent on the failed system to eventually produce the records they needed to recover from the failed system.

Providers who ran their own billing software — tracking claims, attendance, and payment in a system they controlled — were in a different position. They had timestamped documentation of what was submitted and when. They could produce a claims register that showed the gap between what was billed and what arrived. That documentation gave them an independent basis for engaging state officials and accelerating resolution.

Missouri’s situation did not end in December 2023. In January 2026, a federal CCDF payment freeze hit the state again. This time, $20 million was frozen, affecting 1,723 providers — 53% of Missouri’s entire subsidy provider base. The lesson from 2023 had not fully landed: most of the affected providers still did not have independent billing documentation sufficient to manage the dispute.

Michigan’s MiLEAP: 11,000 Complaints and a Provider Paid for 19 of 59 Children

Michigan’s MiLEAP system was intended to modernize state childcare subsidy administration. Instead, it generated more than 11,000 call center inquiries following billing errors.

One documented case stands out. A provider was billed for 59 children — meaning the state system showed 59 children enrolled and authorized. The provider received payment for 19. That is a 40-child discrepancy. At typical CCDF rates, that represents thousands of dollars in missing payment per billing period.

The provider caught the error because they had their own enrollment records and could compare what the state system claimed against their actual enrollment. Without that independent record, the billing mismatch would have gone undetected until the discrepancy either surfaced in an audit or the provider noticed their revenue had inexplicably dropped.

Michigan’s MiLEAP errors were not isolated to one provider. The 11,000+ inquiry volume suggests systematic billing mismatches across the provider network. The cases that got resolved fastest were the ones where providers could walk into the state agency with their own documentation: here is our enrollment as of this date, here is the attendance record for each child, here is what the state system shows versus what we actually billed.

The Common Lesson Both Crises Confirm

Missouri and Michigan are different system failure modes. Missouri’s was a vendor transition that left funds stranded in transit. Michigan’s was data errors in a new system that generated incorrect billing records. But both produced the same differentiated outcome.

Providers with independent records recovered faster. Providers relying entirely on the state system for their billing data had no independent basis for disputing errors or documenting what they were owed.

This is not a theoretical risk. These failures happened in two of the country’s larger childcare subsidy markets. Other states have experienced similar issues at smaller scale. State billing systems are built by government agencies on procurement schedules — they are not maintained with the uptime and reliability expectations of commercial software.

What “Audit-Ready Records” Actually Means

The phrase comes up in compliance contexts, but it applies equally to system failure recovery. Audit-ready records are records that let you reconstruct every billing decision without needing access to the state system.

That means:

Daily attendance records with enough detail to support a billing claim. Timestamped digital check-in is the most defensible format. Paper sign-in sheets are acceptable if they are complete and retained. The record must show who was present on which day, verifiable with parent signature where required by state policy.

Billing claims by period — what you submitted, when you submitted it, and the total claimed per child and per period. If the state system loses your submission, you need your own record of it.

Authorization documentation — current authorization for each subsidized child, including the authorized start and end date, authorized hours, and authorized rate. If the state system shows the wrong authorization, you need your own copy to dispute it.

Payment records — what arrived from the state for each billing period, matched against the claim. The Missouri case required providers to show the gap between claim and payment. Without a payment ledger that matches against claims by period, that calculation requires rebuilding from scratch.

Co-payment collection records — documentation that the family portion was collected, by what amount and on what date. This protects against both audit findings and dual-billing disputes.

None of this is complicated. It is organized record-keeping. The problem is that most providers do not organize it this way — they rely on the state portal to hold the billing history, and on their memory or paper records for the rest.

What Childcare Management Software Provides as a Failsafe

The value of purpose-built childcare management software in this context is not primarily efficiency — though that matters. It is that the records exist independently of the state system.

When you log attendance in your own software, that record is timestamped, linked to the child’s enrollment, and available to you regardless of what the state portal shows. When you generate a billing claim from your software, the claim history stays in your system after submission. When a payment arrives, reconciliation in your software creates a record of what matched and what didn’t.

This is the recovery asset that Missouri and Michigan providers needed. Not a backup of the state database — just an independent record of their own transactions.

When evaluating childcare management software, ask directly: where does my billing data live? Can I export it? What happens if I need to produce claim records without using your system or the state portal? The answer should be that your records are yours — exportable, complete, and independent of any state system.

The Missouri and Michigan situations will happen again. State billing systems are complex, underfunded, and politically managed. The next transition, upgrade, or vendor change will produce errors. The directors who recover fastest will be the ones who maintained their own records through the disruption — not because they anticipated this specific failure, but because they built the habit of keeping independent documentation as part of normal operations.