Codify — Article

California AB 2077 (Protect the Promise Act) tightens Medi‑Cal eligibility verification

Requires documented verification, routine data-matching, and regular redeterminations to reduce improper Medi‑Cal payments and increase accountability across state and county systems.

The Brief

AB 2077—the Protect the Promise Act—directs the Department of Health Care Services (DHCS), working with counties, to verify Medi‑Cal eligibility using documented evidence and available data sources rather than relying solely on self-attestation. The bill adds a statutory framework requiring systematic data matches, ongoing residency monitoring, scheduled eligibility redeterminations, error correction, recovery of improper payments (as federal law permits), and formal accountability reporting to the Legislature.

The measure targets program integrity: it prescribes specific verification streams, cross-references federal and state data on a set cadence, sets start dates for automated residency checks, mandates six‑ and 12‑month redetermination cycles for defined populations, and creates enforceable reporting and oversight tools. For county eligibility workers, DHCS IT teams, managed care plans, and beneficiaries, the bill reshapes intake, renewal, and data‑sharing practices and establishes a statewide compliance baseline tied to federal improper‑payment standards.

At a Glance

What It Does

The bill requires DHCS and counties to verify applicants’ Medi‑Cal eligibility using documentary evidence and available authoritative data sources; it forbids accepting only self‑attestation for core factors except where federal law allows. It mandates scheduled data matches and redeterminations, continuous residency monitoring, corrective action for confirmed errors, and public reporting on outcomes.

Who It Affects

Directly affects DHCS, county human services/eligibility offices, managed care organizations (for address/data feeds), state agencies that hold income or incarceration data (SSA, FTB, EDD, IRS, HUD, CDCR), and Medi‑Cal beneficiaries—especially adults covered under the adult expansion group. It also implicates CMS for federal data exchanges and oversight.

Why It Matters

By codifying frequent, automated matches and repeat redeterminations, the bill aims to reduce billions in questionable payments flagged by audits and reduce California’s exposure to federal improper‑payment penalties. It also shifts workload and technical requirements onto counties and state IT systems and increases the risk that people lacking documentation could face coverage interruptions unless implementation is carefully managed.

More articles like this one.

A weekly email with all the latest developments on this topic.

Unsubscribe anytime.

What This Bill Actually Does

AB 2077 replaces routine acceptance of self‑attestation with a verification‑first approach for core Medi‑Cal eligibility factors: income, residency, identity, household composition, and citizenship/immigration status. Where federal law provides narrow exceptions, applicants may still rely on attestation; otherwise the department must seek documentary evidence or corroborating data before approving enrollment.

That alters the typical intake flow: eligibility workers will need to consult stated data streams and request documents rather than closing cases on applicant statements alone.

The bill specifies technical and operational data actions. DHCS must conduct monthly cross‑checks with national Medicaid enrollment databases to find duplicate enrollments and submit a one‑time complete enrollment data package to CMS by October 1, 2029.

On a quarterly cadence the department must review records from several federal and state sources (including SSA, the National Directory of New Hires and other HHS data, HUD housing assistance, FBI fleeing‑felon data, CDCR incarceration records, and employment/wage records from EDD and FTB). The department must also perform annual reviews of tax data (FTB and IRS) to confirm income and household composition.To keep addresses current, AB 2077 requires DHCS to maintain continuous residency monitoring using the USPS National Change of Address system, returned mail indicators, and address files supplied by managed care plans.

That residency verification program must begin January 1, 2027. Redeterminations are likewise stricter: the department must trigger reviews at least every six months for nonelderly adults covered under the cited federal adult‑expansion provision and at least every 12 months for other beneficiaries, with immediate corrective action when data indicate changes.

Confirmed eligibility errors must be identified promptly and corrected within 30 calendar days where federal law allows, and improper payments must be recovered consistent with federal rules.Finally, AB 2077 builds an accountability structure: DHCS must publish annual reports to the Legislature (per Government Code §9795) on error rates, cases detected and resolved, amounts prevented or recovered, and corrective actions. The bill requires DHCS to name responsible officials, set remediation timelines, and subjects lack of measurable progress to legislative oversight hearings.

The statute instructs implementation to the maximum extent permitted by federal law and to align state practice with federal improper‑payment and eligibility‑integrity standards.

The Five Things You Need to Know

1

The bill bars accepting only self‑attestation for income, residency, identity, household composition, and citizenship/immigration status, except where federal law (e.g.

2

42 C.F.R. §435.952) provides a narrow exception.

3

DHCS must cross‑reference beneficiary records with national Medicaid enrollment databases at least monthly to detect and resolve duplicate enrollments and must submit a one‑time complete enrollment data package to CMS by October 1, 2029.

4

DHCS must run quarterly reviews against specific federal and state systems—SSA, HHS (including the National Directory of New Hires), HUD, FBI fleeing‑felon records, CDCR incarceration data, and EDD/FTB wage records—and run annual tax‑data checks with the FTB and IRS.

5

Residency monitoring must be continuous and implemented starting January 1, 2027, using USPS National Change of Address data, returned‑mail triggers, and address files provided by managed care organizations.

6

The department must carry out systematic redeterminations—at least every six months for the specified nonelderly adult expansion group and at least every 12 months for other beneficiaries—prohibit automatic indefinite renewals, require data‑triggered reviews, and correct confirmed errors within 30 calendar days where federal law permits.

Section-by-Section Breakdown

Every bill we cover gets an analysis of its key sections. Expand all ↓

Section 14042.5

Name and legislative intent

This opening provision brands the statute the Protect the Promise Act and sets the Legislature’s objectives: reducing improper payments, increasing verification, and protecting taxpayer funds. It frames program integrity as the statutory touchstone without changing covered benefits; the language signals that enforcement and verification—not benefit cuts—are the policy levers.

Section 14042.51

Verification requirement and attestation limitation

This section requires DHCS, alongside counties, to verify eligibility before approving enrollment whenever authoritative data exist. It explicitly disallows acceptance of self‑attestation alone for five core eligibility factors, subject only to limited federal exceptions. Practically, counties must design intake workflows that either connect to verification sources or require documentary proof before enrollment.

Section 14042.52

Required data matches, one‑time CMS submission, and residency monitoring

This is the operational core: it mandates monthly cross‑checks with national Medicaid enrollment databases, a one‑time full enrollment submission to CMS by October 1, 2029, quarterly reviews of named federal and state databases, and annual tax‑data reconciliation. It also establishes continuous residency monitoring using USPS NCOA, returned mail, and managed care address files with a January 1, 2027 start date. Implementers will need to scope interfaces, data‑use agreements, and matching logic to operationalize these streams.

4 more sections
Section 14042.53

Redetermination cadence and triggers

The statute prescribes redetermination frequency: at least every six months for the nonelderly adult expansion subgroup identified by the federal code citation, and at least every 12 months for other beneficiaries. It forbids blanket or indefinite renewals, requires data‑triggered renewals from the matches in Section 14042.52, and mandates immediate corrective action for confirmed discrepancies—meaning counties must build automated triggers and exception workflows.

Section 14042.54

Error correction, payment prevention, and recovery

DHCS and counties must promptly identify eligibility errors, correct confirmed errors within 30 calendar days where federal law permits, stop ongoing payments to ineligible individuals, and pursue recovery of improper payments consistent with federal rules. That creates a compressed operational timeline for investigation, notice, and financial recovery procedures tied to federal constraints.

Section 14042.55

Reporting, accountability, and oversight

The department must produce annual public reports to the Legislature on error rates, flagged/resolved cases, amounts prevented or recovered, and compliance failures, designate officials responsible for remediation, and develop timelines to address weaknesses the State Auditor previously identified. The provision also exposes the program to legislative oversight hearings if measurable progress is not shown, increasing political and administrative pressure to demonstrate results.

Sections 14042.56–14042.57

Alignment with federal standards and implementation limits

These sections require DHCS to align eligibility practices with federal improper‑payment and verification standards and to implement the article ‘to the maximum extent permitted by federal law,’ specifically citing Subpart J of 42 C.F.R. Part 435. This ties California’s policy choices to federal permissibility and signals that some verification elements may be curtailed where preempted or restricted by federal Medicaid rules.

At scale

This bill is one of many.

Codify tracks hundreds of bills on Healthcare across all five countries.

Explore Healthcare 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 fiscal managers and budget offices — better data and systematic matches reduce the risk of large improper‑payment findings and potential federal penalties, improving fiscal predictability.
  • DHCS program integrity and audit teams — centralized reporting requirements and mandated data feeds give these teams clearer metrics and tools to find and fix eligibility errors.
  • Managed care plans and providers — fewer downstream billing reversals and retrospective payment recoveries if eligibility is verified up front, which stabilizes provider revenues and contracting risk.
  • Eligible beneficiaries with complete documentation — those already able to produce verification should see faster, cleaner enrollments and fewer later retroactive adjustments when matches confirm eligibility.
  • Federal partners (CMS) — clearer state data exchange commitments and a one‑time enrollment submission improve federal oversight and reconciliation efforts.

Who Bears the Cost

  • Counties’ eligibility offices — the bill creates additional verification work, more frequent redeterminations, IT integrations, and staffing needs; these are state‑mandated local costs unless reimbursed.
  • DHCS IT and data teams — required to build interfaces, perform monthly/quarterly/annual matches, and maintain continuous residency monitoring; implementation and maintenance will be resource‑intensive.
  • Managed care organizations — obligated to supply address and contact data to support residency monitoring, which may require new data‑sharing and privacy controls.
  • Medi‑Cal applicants lacking documentation or stable housing — stricter documentary and data requirements raise the risk of enrollment delays or churn for those without records or consistent addresses.
  • State budget/program administrators — if implementation lapses or matches produce false positives, the state may incur recovery workload, appeals, and possible litigation costs.

Key Issues

The Core Tension

The bill pits fiscal and administrative integrity—preventing improper payments through aggressive verification and automated data matching—against equitable access to care for vulnerable populations who may lack the documents or stable contact information the law now demands; resolving that dilemma requires technical safeguards, procedural protections, and likely funding to avoid turning integrity gains into coverage losses.

AB 2077 creates a classic tradeoff between program integrity and access. Strengthening verification and automated matches will likely reduce improper payments, but it also increases the chance that people without formal records—recently arrived immigrants, people experiencing homelessness, or informal workers—will face coverage interruptions.

The statute attempts to limit that risk by deferring to federal exceptions, but the bill leaves implementation choices (e.g., match thresholds, notice procedures, and appeals timing) to DHCS and counties, where design choices determine real‑world effects.

Operationally, the bill imposes tight technical demands with fixed start dates and a distant‑but‑firm deadline for a one‑time federal submission. Integrating diverse data sources (federal criminal/income files, USPS NCOA, MCO address databases) requires robust matching logic and data‑use agreements; mismatches or false positive matches could trigger wrongful terminations and costly appeals.

Privacy and legal safeguards around sensitive data sharing are not spelled out in detail, so DHCS will need to balance data minimization and security against the statute’s aggressive verification goals.

Finally, the statute increases county duties without specifying full funding beyond the Commission on State Mandates reimbursement process; that creates uncertainty about who pays for IT upgrades and staffing. The bill also depends on federal permissibility—some verification actions may be restricted by CMS rules—so the actual on‑the‑ground program could look materially different depending on negotiated federal waivers or CMS guidance.

Try it yourself.

Ask a question in plain English, or pick a topic below. Results in seconds.