SB 999 amends state law to change the Franchise Tax Board’s annual deadline for reporting information about household health coverage penalties and related subsidy reconciliations from March 1 to June 1. The bill does not add new reporting items; it adjusts only when the existing report is due to the Legislature.
The shift is procedural but meaningful: the report contains county-level and income-class breakdowns, exemption counts, federal-poverty-category tallies, and reconciliation amounts that legislative staff, budget offices, and health agencies use to evaluate program performance and to plan fiscal actions. Moving the date affects when those stakeholders can access updated, reconciled data for analysis and decision-making.
At a Glance
What It Does
The bill amends the Revenue and Taxation Code to change the annual due date for the Franchise Tax Board’s report from March 1 to June 1. It leaves intact the report’s required content — the six enumerated data elements that break penalties, dependents, exemptions, and subsidy reconciliations down by county, adjusted gross income class, and federal poverty level categories.
Who It Affects
Primary actors are the Franchise Tax Board (FTB), legislative fiscal and policy staff who consume the report, and state health agencies that reconcile subsidies and monitor coverage penalties. County officials, researchers, and advocacy groups that rely on the report for local analysis will also see later access to the data.
Why It Matters
The extra three months can let the FTB finalize reconciliations and improve data accuracy, but it delays the information that drives budget decisions and program oversight. For professionals who schedule analyses or legislative briefings around March reporting, the calendar change may force workflow and timeline adjustments.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
Section 61050 currently directs the Franchise Tax Board to compile an annual report on penalties imposed under state health-coverage statutes and to break those penalties down in several specific ways. SB 999 does one thing: it pushes the annual deadline for that report from March 1 to June 1.
The statute’s list of required data elements — county-level counts, adjusted gross income (AGI) class splits, total penalty amounts, statewide totals, exemption counts and reasons, counts by federal poverty level (FPL) categories, and state subsidy and reconciliation amounts — remains unchanged.
The report’s substance matters because it links tax-filing data to program administration: FTB uses tax returns to identify households that paid penalties, tally dependents, estimate FPL categories using AGI and household size, and compute reconciliation adjustments for state subsidies. The six enumerated items produce both cross‑sectional counts (who paid, where, and in which income bands) and dollar figures (penalty totals and subsidy adjustments) that other agencies use for program evaluation and budget work.Practically, moving the deadline can change the trade-offs in the data pipeline.
A later deadline gives FTB more time to process returns, incorporate late filings and amended returns, and complete reconciliation runs that affect subsidy accounting. That can reduce measurement error in the published figures.
On the other hand, analysts who plan around a March release must shift schedules; legislative committees and budget offices that need contemporaneous data for spring budget processes may receive reconciled numbers after key deadlines.SB 999 also leaves the mechanics of delivery intact by referencing Government Code Section 9795 as the submission route to the Legislature. That means the report will continue to follow the state’s statutory reporting pathway (format and posting procedures controlled by Section 9795), but stakeholders should expect the report to appear on a different cadence in the annual calendar.
The Five Things You Need to Know
SB 999 amends Section 61050 of the Revenue and Taxation Code — the statutory home of the FTB’s annual health-coverage-penalty report.
The statute requires six discrete data elements: (1) counts of applicable households and dependents by county and AGI class; (2) penalty totals by county and AGI class; (3) the statewide penalty total; (4) the number of exemptions and the most common exemption qualifications; (5) counts of households and dependents by four federal poverty level categories; and (6) the amounts of state subsidies paid and reconciliation adjustments by county and FPL category.
The federal poverty level categories the bill uses for reporting are explicitly defined as: 0–138%, 139–266%, 267–400%, and 401% and above (estimated from AGI and tax-household size).
The statute directs the FTB to submit the report pursuant to Government Code Section 9795, i.e.
via the state’s legislatively prescribed report-submission mechanism.
SB 999 does not alter the annual frequency or the content of the report — only the calendar due date when the compiled report must reach the Legislature.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Change the report’s due date
This provision replaces the March 1 due date language with a June 1 due date for the annual report. Mechanically it is a one-line substitution in the statute; operationally it shifts when FTB must complete its annual data runs and deliver the report to the Legislature. That simple edit affects downstream timelines for anyone who schedules analyses, briefings, or budget actions around the prior March release.
Counts and penalty-dollar reporting
Paragraphs (1)–(3) require FTB to produce granular counts of applicable households and dependents, and to report penalty amounts both by county and by adjusted gross income class with a statewide aggregate. The practical implication is that the report supports cross-tabulations (geography × income) that enable targeted policy questions, but it depends on FTB’s ability to match tax returns to program definitions and to bucket AGI into statutorily meaningful classes.
Exemptions, federal-poverty categories, and subsidy reconciliations
Paragraph (4) asks for exemption counts and common grounds; (5) defines four FPL bands (estimated from AGI and household size) for counts of households and dependents; (6) requires reporting of state subsidy payments and reconciliation adjustments by county and FPL category. These items tie tax-year data to program eligibility and fiscal reconciliation; the FPL-estimation method (using AGI) is explicit in the statute and is a point where methodological choices affect reported results.
Submission pathway to the Legislature
This short subsection requires that the FTB submit the report pursuant to Government Code Section 9795. That ties the report to the statutory process for delivering and, where applicable, publishing reports for legislative use, which affects how the report will be formatted, transmitted, and made accessible to the public and committees.
This bill is one of many.
Codify tracks hundreds of bills on Finance across all five countries.
Explore Finance 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
- Franchise Tax Board staff tasked with producing the report — the later deadline eases scheduling pressure and allows more time to incorporate late or amended returns and to complete reconciliation runs, which can improve data accuracy.
- State program administrators and reconciliation teams (e.g., departments that track subsidy disbursements) — they receive data potentially closer to finalized reconciled figures, reducing the chance that early estimates will need revision.
- Data consumers prioritizing accuracy — researchers, policy analysts, and legislative offices that prefer reconciled, less-error-prone datasets will find the June delivery yields cleaner inputs for in-depth analysis.
Who Bears the Cost
- Legislative fiscal staff and committees that rely on March-period reporting for spring budget work — they will get reconciled figures later and may need to use preliminary estimates instead, disrupting timing for hearings and analyses.
- County public health and local planning agencies that schedule programs and outreach based on the prior March release — later data can complicate local planning cycles and reporting deadlines.
- Advocacy organizations and journalists who produce timely public reporting around March — delayed publication reduces the window for public-facing analysis tied to early-year policy debates.
Key Issues
The Core Tension
The central dilemma is straightforward: allow the tax agency more time to produce more accurate, reconciled statistics, or keep an earlier deadline so policymakers and budget staff receive information sooner. SB 999 resolves that by prioritizing accuracy/timing flexibility for the FTB at the cost of delayed access for data users — a trade-off with legitimate arguments on both sides.
The bill is narrowly focused on timing, but that narrowness concentrates two implementation questions. First, accuracy versus timeliness: giving FTB extra time likely produces cleaner reconciliation figures, but it also postpones when those figures become available to decision-makers.
Which outcome is more valuable depends on whether users prefer preliminary estimates early in the budget cycle or finalized figures later.
Second, the statutory method for estimating federal poverty level using AGI and tax-household size is deterministic in the statute but not immune to measurement error; late filings, amended returns, and household composition changes can alter placements across the four FPL buckets. The change to June 1 may reduce volatility in those buckets, but it does not address methodological limitations.
Finally, the bill makes no provision for additional funding or staffing for FTB to handle reconciliation and reporting work; if the agency faces competing deadlines or resource constraints, the practical improvement in data quality the bill anticipates may not materialize without corresponding administrative adjustments.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.