The bill adds two targeted amendments to the Affordable Care Act. First, it requires the Secretary to build, within 60 days, a process that checks whether an incoming enrollee’s Social Security number (SSN) is already in use for the same coverage period across any Exchange and to prevent duplicate advance premium tax credit (APTC) payments when identical SSNs are found.
Second, it requires that enrollments submitted by agents or brokers in the individual and small-group markets only take effect after the individual or employer gives consent directly through a mechanism the Secretary creates; broker attestation is explicitly disallowed as proof of consent.
These changes are narrow in scope but consequential in practice. The SSN-deduplication requirement forces new cross-Exchange data-matching and operational controls intended to reduce improper APTC payments and enrollment fraud.
The consent mandate inserts a centralized authentication step into broker-assisted workflows starting with plan years beginning January 1, 2027, which will change how producers, Exchanges, and employers coordinate enrollments and may introduce enrollment friction for some consumers and small employers.
At a Glance
What It Does
The bill directs the Secretary to create an SSN-matching process to detect identical Social Security numbers among Exchange enrollees and to stop duplicate advance premium tax credit payments. It also requires a Secretary-operated consent mechanism so no agent- or broker-assisted enrollment is effective without direct consent from the individual or employer; broker attestation cannot substitute.
Who It Affects
Federally facilitated and state-based Exchanges, CMS (as the Secretary’s implementing agency), insurers in the individual and small-group markets, agents and brokers who facilitate enrollments, the IRS (through APTC reconciliations), and consumers and small employers who enroll through producers.
Why It Matters
The bill centralizes two enrollment controls that currently rely on a mix of verification processes and broker practices, potentially reducing some types of fraud and improper subsidy payments while creating new operational, data-sharing, and consumer-authentication requirements for Exchanges and brokers.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
Section 2 requires the Secretary to stand up, within 60 days of enactment, a program element that checks whether the SSN provided for a new or changing enrollment matches any SSN already enrolled in any Exchange for the same coverage period. If the systems find identical SSNs, the Secretary must act to prevent duplicate advance premium tax credit payments.
The statute does not prescribe the exact blocking, suspension, or notification steps; it focuses on detection and preventing duplicate APTC disbursements.
Section 3 reorganizes and supplements the existing Exchange enrollment procedures to require direct consent for enrollments submitted by agents or brokers. For plan years beginning on or after January 1, 2027, no agent- or broker-submitted enrollment in the individual or small-group market takes effect until the person or employer gives consent through a mechanism the Secretary builds.
The statute expressly forbids treating an agent’s or broker’s attestation as equivalent to the enrollee’s own consent, shifting responsibility for authentication away from producers and toward a Secretary-operated channel.Together, the two changes are procedural rather than substantive changes to eligibility rules: they add verification and authentication gates to existing enrollment flows. In practice, Exchanges will need to modify IT systems and intake workflows to do real-time or near-real-time SSN deduplication across jurisdictions and to integrate the Secretary’s consent mechanism into agent-assisted paths.
Those operational requirements intersect with subsidy reconciliation at the IRS, producer commission timing, and consumer experience; the bill leaves those downstream mechanics to implementation guidance, rather than statutory detail.Because the bill focuses on SSNs and direct consent, it raises follow-on questions about authentication standards (what constitutes sufficient consent), handling of false positives or shared/erroneous SSNs, appeal or remedial processes when legitimate enrollments are blocked, and privacy or data-sharing safeguards between federal and state Exchanges. The text creates requirements but delegates nearly all technical choices to the Secretary, making implementation the decisive factor for how disruptive or effective the changes will be.
The Five Things You Need to Know
The Secretary must create an SSN-matching process within 60 days of enactment to detect identical Social Security numbers across any Exchange for the same coverage period.
If identical SSNs are identified, the Secretary must take actions to ensure duplicate advance premium tax credit payments are not made; the bill does not prescribe the specific operational response.
For plan years beginning January 1, 2027, no enrollment submitted through an agent or broker in the individual or small-group market is effective without the individual’s or employer’s direct consent through a Secretary-established mechanism.
The consent mechanism may not accept an attestation from the enrolling agent or broker as proof of consent; the statute centralizes validation with the Secretary rather than leaving it to producers.
The bill applies to all Exchanges “under this title,” which encompasses federally facilitated and state-based Exchanges, thereby requiring cross-jurisdiction data matching and coordination.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
This one-line section names the measure the 'Stop ACA Enrollment Fraud Act of 2026.' It contains no operative requirements but frames the bill’s purpose for statutory interpretation and implementation documents.
SSN deduplication and prevention of duplicate premium tax credit payments
The bill adds a new subsection to 42 U.S.C. 18081 directing the Secretary to add to the Exchange program a process that checks whether an enrollee's Social Security number matches any SSN already used by an enrollee for the same coverage period across any Exchange. The statute sets a 60-day deadline for the Secretary to establish that capability and requires action to stop duplicate APTC disbursements when matches occur. Practically, Exchanges will need to exchange and compare PII across state and federal systems, decide whether matching triggers automated blocking, manual review, or consumer outreach, and coordinate with IRS reconciliation processes to avoid duplicate subsidy payments.
Direct consent requirement for agent- and broker-assisted enrollments
The bill restructures the existing enrollment-procedure provision and inserts a new, explicit condition: enrollments executed through agents or brokers in the individual and small-group markets are not effective until the enrollee or employer consents using a mechanism the Secretary creates. The amendment bars using a broker’s attestation as evidence of consent. Implementation will require the Secretary to design an authentication channel (portal, digital signature, recorded call, etc.), determine how consent is logged and retained for audits, and integrate that channel with existing producer workflows and commission payment systems.
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
- Federal government and taxpayers — by creating a statutory requirement to detect and stop duplicate APTC payments, the bill aims to reduce improper subsidy outlays and the fiscal exposure associated with duplicate enrollments.
- Consumers whose identities are misused — SSN deduplication can intercept some fraudulent enrollments that use a real person’s SSN without consent, protecting those victims from surprise coverage conflicts or tax reconciliation headaches.
- Exchanges seeking data integrity — clearer statutory authority to run cross-Exchange matching can support more consistent verification practices and reduce downstream enrollment disputes for carriers and administrators.
Who Bears the Cost
- CMS and Exchanges (federal and state) — they must design, build, and operate the SSN-matching capability and the Secretary-run consent mechanism, absorb IT, staffing, and process-integration costs, and handle increased call center or manual-review workload.
- Agents and brokers — producers will need to change enrollment workflows, may face delayed effective dates and commission timing, and must adapt to the Secretary’s consent channel that they cannot substitute for with their own attestations.
- Consumers and small employers dependent on broker assistance — added authentication steps can introduce delays or require digital access and literacy, disproportionately affecting people with limited internet access, non-English speakers, and those needing immediate coverage.
Key Issues
The Core Tension
The bill forces a trade-off between preventing subsidy abuse and preserving smooth, timely access to coverage: stronger, centralized verification reduces some fraud risks but increases operational complexity and the chance that legitimate enrollments will be delayed or blocked, particularly for vulnerable populations who rely on broker assistance.
The statute mandates capabilities (SSN matching and a Secretary-controlled consent mechanism) but leaves nearly all technical design choices, authentication standards, exception handling, and remedial procedures to the Secretary. That delegation shifts the real policy outcomes to rulemaking and system design: whether matching is real-time versus batch, how many false positives are tolerated, what identity-document thresholds trigger manual review, and how blocked enrollments are appealed will determine whether the bill curtails fraud or simply creates new enrollment friction.
Operationally, cross-Exchange SSN matching raises privacy, data-sharing, and state-federal coordination questions. State-based Exchanges may have differing IT maturity and legal constraints; centralizing consent with the Secretary could conflict with state workflows.
The text also assumes SSNs are a reliable unique key — but SSN errors, shared SSNs due to historical administrative practices, or identity-theft scenarios can produce matches that block legitimate coverage. Finally, the bill is silent on timelines for consumer notification, transitional coverage when a match triggers a hold, and on whether a failed consent step suspends special enrollment rights, leaving important access and equity issues unresolved.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.