This bill amends the Child Care and Development Block Grant Act of 1990 by adding a new required element to state CCDBG plans: a written description of the State’s internal controls, fraud investigation and recovery processes (including sanctions), and procedures to document and verify eligibility. The description must also explain how the State uses data from other State and local agencies that oversee child care providers serving children who receive CCDBG assistance.
The change targets program integrity and transparency rather than funding or federal enforcement mechanics. It forces states to clarify operational practices and data links that detect and respond to improper payments—creating audit trails and compliance work for state agencies and operational impacts for providers, IT systems, and privacy frameworks.
At a Glance
What It Does
The bill inserts a new subparagraph into 42 U.S.C. 9858c(c)(2) requiring each State CCDBG plan to include a description of: (i) internal controls for program integrity; (ii) processes to investigate and recover fraudulent payments and to impose sanctions; and (iii) procedures to document and verify eligibility, including use of data across state and local agencies.
Who It Affects
State agencies that administer CCDBG programs must prepare and maintain the new descriptions; HHS/ACF reviewers will receive more detailed operational information. Child care providers and recipients will be affected indirectly through enhanced oversight, sanction frameworks, and any operational changes states adopt to comply.
Why It Matters
The bill formalizes transparency around fraud controls and cross‑agency data use, which can tighten detection and recovery of improper payments. At the same time it creates administrative and technical burdens for states without adding federal funding or prescribing uniform standards, so implementation will vary by jurisdiction.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The Stop Child Care Fraud Act makes a narrow but consequential change to the CCDBG state plan requirements. It does not change who is eligible for assistance or how much funding a state receives; rather, it requires states to spell out, within the plan they submit under existing law, how they keep the program honest and how they use data to do so.
States must describe their internal control systems—think separation of duties, audit trails, reconciliations—and the policy or technical safeguards they rely on to prevent, detect, and respond to misuse of funds.
The bill also forces states to document the lifecycle of fraud response: how they investigate suspected improper payments, the mechanisms they use to recover funds, and the sanctions they apply to clients or providers. Because the text explicitly asks for an explanation of how data from other state and local agencies is used, the amendment effectively pushes states to disclose whether they match CCDBG records against licensing databases, unemployment insurance, child welfare, or other administrative sources, and to describe the governance around those exchanges.Operationally, compliance officers and program managers should expect concrete follow‑ups: states will need to inventory data sources, check legal authorities for sharing (and confidentiality constraints under laws like HIPAA, FERPA, or state privacy statutes), update memoranda of understanding, and probably upgrade IT matching and audit capabilities.
The bill does not set federal performance standards, timelines, or funding for these changes; it requires transparency in the plan that the federal government already reviews, leaving enforcement and the substance of controls largely to state discretion.Because the requirement lives in the state plan, changes will surface at plan submission or renewal and during routine federal reviews of CCDBG plans. States that already have robust program integrity frameworks will mostly document existing practices; other states will need to build descriptions from scratch—an administrative task that could also surface substantive gaps in fraud detection and recovery.Finally, the mandate to describe sanctions and recovery processes will create visibility into how states treat providers and families when fraud is suspected.
That visibility is useful for oversight, but it also raises questions about proportionality, due process, and the potential chilling effect of aggressive sanction regimes on providers who serve high‑need communities.
The Five Things You Need to Know
The bill adds a new subparagraph (W) to 42 U.S.C. 9858c(c)(2), making program integrity disclosures a formal element of each State’s CCDBG plan.
States must describe three categories of controls in their plan: internal controls, processes to investigate and recover fraudulent payments (including sanctions), and procedures to document and verify eligibility.
The amendment explicitly requires states to explain how they use data from other State and local agencies for oversight of providers serving CCDBG children, which pushes data‑sharing into the state plan narrative.
The statute changes disclosure requirements only: it does not create new federal penalties, allocate additional funding for implementation, or prescribe specific technical or legal standards for the described processes.
Because the new requirement sits in the state plan, it will be reviewed through existing CCDBG plan approval and monitoring channels, meaning implementation timing will follow state plan submission cycles rather than an independent timetable.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
This section names the legislation the 'Stop Child Care Fraud Act.' The short title signals focus for drafters and reviewers but does not affect legal obligations; it will appear on the amended Act and any subsequent citations.
Adds program integrity disclosure to State CCDBG plans
Section 2 amends 42 U.S.C. 9858c(c)(2) by inserting a new required disclosure (subparagraph (W)) into the list of items states must include in their CCDBG plans. Practically, the insertion converts what might previously have been a best practice into a mandatory element of the federally‑reviewed plan document. States will need to include written descriptions satisfying the statutory text every time they submit or update their plan.
Internal controls: describe systems and safeguards
The new clause (i) requires the plan to describe the State’s internal controls to ensure program integrity and accountability. Compliance teams will have to convert operational practices—staff roles, reconciliation routines, audit logs, procurement checks—into a documented narrative that can be read by federal reviewers and auditors. That forces states to reconcile policy with practice and may expose weak or undocumented control areas.
Fraud processes, sanctions, eligibility verification, and data use
Clause (ii) asks states to describe how they investigate and recover fraudulent payments and how they impose sanctions; clause (iii) requires documentation and verification procedures for eligibility and a description of how states leverage data from other agencies. Together these provisions require states to map investigative workflows, recovery mechanisms (offsets, recoupments, civil or administrative actions), sanction tiers for clients and providers, and the data exchanges used to support those actions. The text does not define acceptable recovery methods or sanction standards, leaving those substantive choices to state policy-makers but making them transparent in the plan.
This bill is one of many.
Codify tracks hundreds of bills on Social Services across all five countries.
Explore Social Services in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- State and federal auditors — They gain standardized, written descriptions that make audits and reviews more efficient by surfacing control processes and data sources.
- Families and taxpayers — Improved documentation and cross‑agency data use can lead to faster detection and recovery of improper payments, protecting program dollars for eligible children.
- HHS/ACF reviewers — The agency receives clearer operational information in state plans, which can streamline federal monitoring and highlight jurisdictions needing technical assistance.
- Compliant providers — Providers that already operate with strong controls get clearer rules of engagement and documentation that can protect them in investigations.
- Policy-makers and legislators — The requirement increases transparency, enabling targeted oversight and informed decisions about funding or technical support.
Who Bears the Cost
- State CCDBG agencies — They must inventory controls, draft plan language, negotiate data‑sharing agreements, and potentially upgrade IT and staff capacity without allocated federal funds.
- Local child care providers — Providers may face more frequent audits, documentation requirements, or sanctions depending on state practices, increasing administrative burden.
- State IT and data teams — Implementing reliable cross‑agency matches, secure transfers, and audit logs will likely require systems work and ongoing maintenance resources.
- Privacy and child welfare offices — These offices will need to reconcile increased data use with legal confidentiality obligations, creating negotiation and compliance work.
- Families under review — Households subject to eligibility verification and sanction regimes may experience delays in benefit access or burdensome documentation requirements.
Key Issues
The Core Tension
The central dilemma is between strengthening program integrity by encouraging aggressive data‑driven detection and preserving access, fairness, and privacy: the bill pushes states to use administrative data and sanctions to recover improper payments, but it does not fund the technical or legal work required to do that responsibly, nor does it set guardrails to prevent disproportionate burdens on providers and families.
The bill increases transparency but leaves key substantive choices to states. It compels disclosure of what controls and processes exist without establishing minimum standards, enforcement mechanisms, or funding to build weak systems.
That design means the amendment will expose variation across states—some will simply document robust, mature programs; others will document gaps but lack resources to close them. For federal reviewers, the utility of the new disclosures depends on how granular states are willing or able to be.
The explicit focus on cross‑agency data use raises immediate legal and operational questions. States will have to evaluate whether existing statutory authorities permit the proposed matches (for example, between licensing, welfare, child welfare, or unemployment systems) and whether privacy laws restrict those exchanges.
Building lawful, secure data‑sharing arrangements takes time and money; the bill assumes states can either already do this or will cover the cost themselves. Finally, making sanction regimes visible is useful for oversight but could encourage states to deploy harsher penalties absent standardized due‑process protections, disproportionately affecting small providers and families with limited administrative capacity.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.