ACA1 creates a Budget Stabilization Account (BSA) inside the General Fund and sets a formula and schedule for annual transfers from the General Fund into that account. The amendment requires the Controller to move a statutorily specified percentage of estimated General Fund revenues each year and directs the Department of Finance to calculate how much of those revenues are attributable to personal income taxes paid on net capital gains and how much of that portion exceeds an 8 percent threshold.
The text contains two numeric placeholders ("1.5 ____ percent" and "10 20 percent") that leave important dollar-flow limits ambiguous as written.
Between the 2015–16 fiscal year and 2029–30, ACA1 mandates that half of certain identified transfer amounts go into the BSA and that the other half be appropriated by the Legislature for defined uses—unfunded pre‑2014 obligations, budgetary loans outstanding as of 2014, old mandated‑cost claims, and pension/OPEB prefunding above base amounts. From 2030–31 onward transfers default to the BSA, although the Legislature may appropriate up to 50 percent for the same listed obligations.
The amendment also caps the account balance (the operative cap text reads "10 20 percent"), restricts excess transfer uses to infrastructure, and authorizes limited temporary use of BSA funds for daily cashflow management.
At a Glance
What It Does
Creates a Budget Stabilization Account in the General Fund and requires annual transfers from the General Fund calculated from Budget Act estimates and special capital‑gains adjustments; transfers are scheduled by the Director of Finance and executed by the Controller. For 2015–16 through 2029–30 designated transfer amounts are split 50/50 between the BSA and legislative appropriations for enumerated liabilities; after 2030 transfers go to the BSA by default but the Legislature may appropriate up to half.
Who It Affects
The Controller and Department of Finance bear new operational duties; the Legislature’s appropriations choices are constrained by the required split and caps; state pension plans and prefunding programs, agencies with unpaid mandated claims, and entities holding budgetary loans are direct potential beneficiaries; General Fund program areas face reduced discretionary revenue when transfers occur.
Why It Matters
ACA1 changes the mechanics of California’s rainy‑day policy by tying transfers (in whole or part) to the volatile capital gains component of income tax receipts and by channeling windfalls into either reserves or specific liabilities. That shifts fiscal discretion and creates new reporting, reconciliation, and timing challenges that affect long‑term solvency, pension prefunding, and near‑term budget flexibility.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
ACA1 constitutionalizes a Budget Stabilization Account and builds a multi‑layered transfer regime around annual Budget Act revenue estimates. The Controller must move a percentage of estimated General Fund revenues into the BSA on October 1 of each relevant year; the amendment text shows the transfer rate as "1.5 ____ percent," leaving the precise rate indeterminate in the provided draft.
Parallel to that nominal transfer, the Department of Finance must produce detailed estimates each Budget Act cycle: overall General Fund proceeds of taxes, the portion coming from personal income tax net capital gains, and how much of that capital‑gains portion exceeds an 8 percent threshold. Finance must also calculate the impact of including those capital‑gains amounts on the state’s funding obligation under Section 8 and identify prior appropriations drawn from those funds.
The amendment directs a specific path for the identified capital‑gains excess. For fiscal years 2015–16 through 2029–30, the law requires that fifty percent of both the baseline transfer amount and the calculated capital‑gains excess be deposited into the BSA; the remaining fifty percent must be appropriated by the Legislature for a short list of purposes: unpaid pre‑2014 General Fund obligations under Section 8, outstanding budgetary loans as of January 1, 2014, payable mandated costs incurred before 2004–05 that are eligible for multi‑year payment, and additional prefunding of state‑level pension and OPEB liabilities above defined base amounts.
Beginning with 2030–31, both identified amounts are transferred to the BSA by default, though the Legislature is given the authority to appropriate up to 50 percent for the same specified obligations.ACA1 builds reconciliation and adjustment mechanics into the regime. The Department of Finance must provide updated estimates and retroactive recalculations for the two prior fiscal years in certain early‑implementation years (notably in 2016–17 with respect to 2015–16, and in 2017–18 and thereafter for the two preceding years).
Those recalculations feed a formula that can trigger additional transfers into the BSA or transfers back from the BSA to the General Fund. Transfers may also be suspended or reduced under the amendment’s cross‑reference to Section 22.
The measure caps transfers so that a BSA deposit cannot produce a balance above a stated percentage of General Fund proceeds of taxes—here written as "10 20 percent" in the draft—and any proceeds that would otherwise have been transferred but are blocked by that cap are limited to infrastructure spending as defined by Government Code Section 13101 as of January 1, 2014. Finally, the Controller may temporarily use BSA funds to smooth daily cashflow when those funds are not needed for the account’s purposes, and the amendment declares such transfers are not appropriations subject to Article XIII B limits.
The Five Things You Need to Know
The Controller must transfer, by October 1 each applicable year, a sum equal to the draft’s specified percentage of estimated General Fund revenues—written in the text as "1.5 ____ percent," leaving the rate unresolved in this draft.
From 2015–16 through 2029–30 the identified transfer amounts are split 50/50: half goes into the BSA and half is appropriated by the Legislature for listed obligations (pre‑2014 Section 8 shortfalls, 2014-era budgetary loans, pre‑2004–05 mandated claims payable over time, and pension/OPEB prefunding above base amounts).
Beginning in 2030–31 the full identified amounts are transferred to the BSA by default, but the Legislature may still appropriate up to 50 percent of those amounts for the same enumerated obligations.
The statute caps the BSA balance so transfers cannot raise it above a stated share of General Fund proceeds of taxes (the draft reads "10 20 percent"); proceeds that would have been transferred but would exceed the cap may be spent only on infrastructure as defined by Government Code §13101 (2014 version).
The Department of Finance must estimate the share of General Fund proceeds that come from personal income taxes on net capital gains, calculate any portion above an 8 percent threshold, and reconcile those calculations retroactively for prior fiscal years; excesses can trigger additional transfers in or returns to the General Fund.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Creation of the Budget Stabilization Account and base transfer instruction
Subdivision (a) places the Budget Stabilization Account in the General Fund and instructs the Controller to transfer a fixed percentage of estimated General Fund revenues each year no later than October 1. The draft text shows the transfer rate as "1.5 ____ percent," which is mechanically important because it determines the baseline flow into the BSA and interacts with later capital‑gains calculations and caps. This subsection also links the initial transfer requirement to the annual Budget Act estimates, tying execution to the Budget Act timetable.
Department of Finance reporting and capital‑gains adjustments
Subdivision (b) tasks the Department of Finance with producing a set of estimates for the Legislature each Budget Act cycle: total General Fund proceeds of taxes that may be appropriated under Article XIII B, the portion derived from personal income tax net capital gains, and the amount of that portion exceeding an 8 percent threshold. The subsection then requires Finance to calculate how including that excess affects the state’s Section 8 funding obligation and to net out any related appropriations so the Legislature can see a residual amount available for transfer. It further requires retroactive recalculations for prior fiscal years in early implementation years, creating a reconciliation path that can produce additional transfers or refunds.
Transfer schedule and 50/50 split (2015–16 through 2029–30)
Subdivision (c) establishes the practical transfer schedule for the early decades: for each fiscal year from 2015–16 through 2029–30 the Director of Finance provides a schedule and the Controller executes transfers. The statutory rule is a 50/50 split—half of the identified amounts goes into the BSA and half is appropriated by the Legislature for four narrowly described uses (pre‑2014 Section 8 obligations, 2014-era budgetary loans, pre‑2004–05 mandated claims payable over time, and pension/OPEB prefunding beyond base amounts). The text is precise about eligibility for pension/OPEB prefunding—appropriations must supplement, not supplant, existing required contributions.
Post‑2030 default to BSA with optional legislative appropriations
Starting in the 2030–31 fiscal year, subdivision (c)(2) shifts the default: both the baseline transfer amount and the capital‑gains residual are moved into the BSA. The Legislature retains the discretion to appropriate up to 50 percent of those amounts for the same list of purposes, but the default is accumulation rather than split distribution. Practically, this means a structural ramp toward reserve accumulation unless the Legislature elects to divert half for liabilities.
Adjustment mechanics, transfers back, and reconciliation
Subdivision (d) describes how reconciliations work: if retroactive recalculations indicate more should have been transferred, the Controller moves the additional amount from the General Fund to the BSA; if the BSA had received more than the reconciled figure, the excess is returned to the General Fund. All transfers follow a schedule from the Director of Finance and remain subject to suspension or reduction under the cross‑referenced Section 22 mechanism. This creates a two‑way flow and embeds retroactive adjustment risk into both the Controller’s and the Legislature’s budgeting calculus.
Account cap, infrastructure fallback, and other operational rules
Subdivision (e) limits transfers so that a deposit cannot produce a BSA balance exceeding a stated percentage of General Fund proceeds of taxes—written in the draft as "10 20 percent," which requires resolution. If transfers would exceed that cap, the law restricts the use of those otherwise blocked proceeds to infrastructure projects as defined by Government Code §13101 (as of January 1, 2014). Other operational clauses let the Controller temporarily use BSA funds for daily cashflow management and state that transfers under this section do not count as Article XIII B appropriations, which affects how the transfers interact with constitutional spending limits.
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
- State treasury and fiscal stability: The BSA creates an institutionalized reserve that, if funded as intended, provides the state with a larger rainy‑day pool to smooth revenue volatility.
- State pension and OPEB prefunding programs: The measure expressly allows appropriations to prefund state‑level pension and postemployment benefits above defined base amounts, giving those programs a legal pathway to additional contributions.
- Claimants with long‑outstanding mandated costs and holders of pre‑2014 budgetary loans: The legislatively directed 50 percent appropriation can be used to pay eligible mandated costs and outstanding budgetary loans identified in the text, accelerating payment of those legacy obligations.
- Infrastructure projects and contractors: The statute restricts excess, cap‑blocked proceeds to infrastructure uses, creating a guaranteed funding channel for projects defined under Government Code §13101 (2014), which could increase construction and maintenance activity.
- Budget and finance offices: The Department of Finance and the Controller receive clearer statutory mandates and estimates that, if implemented cleanly, improve transparency about the capital‑gains component of receipts and the size of potential transfers.
Who Bears the Cost
- General Fund program areas and discretionary budgets: Mandatory transfers reduce the pool of revenues available for other legislative priorities in years when transfers occur.
- The Legislature’s discretionary fiscal control: The 50/50 split (through 2029–30) and post‑2030 default to the BSA narrow the Legislature’s ability to allocate windfalls entirely at its own discretion.
- Administrative staff at the Controller and Department of Finance: The detailed, repeated estimates, reconciliations, retroactive calculations, and schedule management increase workload and require new or enhanced systems to track capital gains and Section 8 impacts.
- Programs reliant on near‑term General Fund availability: Agencies expecting one‑time or ongoing increases in the General Fund might find those resources reduced because windfalls are redirected to the BSA or specified legacy obligations.
- Taxpayers and voters (indirectly): If the state uses transfers to prefund pensions or pay mandated claims, funding for other services could be delayed or reduced, shifting the visible allocation of state spending.
Key Issues
The Core Tension
ACA1 tries to reconcile two legitimate goals—locking away volatile revenue to build a meaningful rainy‑day reserve and using windfalls to address pressing, pre‑existing fiscal liabilities—but those goals pull in opposite directions: saving strengthens long‑term solvency while redirecting funds to pensions, mandated claims, and loan paydowns addresses immediate liabilities and politically salient obligations. The amendment’s split approach and post‑2030 exception attempt compromise, but leave open hard choices about timing, volatility management, and whether windfalls should primarily reduce long‑term risk or close legacy gaps now.
Two drafting ambiguities stand out and have substantive consequences. First, the text includes unresolved numeric placeholders—"1.5 ____ percent" for the baseline transfer rate and a cap phrase rendered as "10 20 percent." Those gaps matter: the transfer rate determines annual outflows from the General Fund, and the cap determines the maximum size of the reserve; either error could produce legally contestable ambiguity or force implementing agencies to guess legislative intent.
Second, the formula ties transfers to the capital‑gains component of income tax receipts and requires an 8 percent threshold calculation. Capital gains are notoriously volatile and concentrated among a small number of taxpayers, so basing transfers on that component can produce large year‑to‑year swings.
Although the statute builds in retroactive reconciliations and the ability to return excess funds, the timing (single transfers by October 1 tied to Budget Act estimates) means the state may commit funds on expectations that later change, creating either forced returns or pressure to suspend transfers under Section 22.
Operationally, the amendment mixes reserve accumulation with directed spending in a way that invites tension. The 50/50 split through 2029–30 attempts a compromise—half saved, half spent on legacy liabilities—but creates political pressure each year about which side of the ledger should prevail.
The post‑2030 default toward accumulation does not eliminate that pressure because the Legislature can still appropriate up to half. The provision allowing the Controller to use BSA funds for daily cashflow (so long as it "does not interfere with the purposes of the Budget Stabilization Account") is sensible as a cash management tool, but it blurs the bright line between liquid working balances and true rainy‑day reserves.
Finally, the definitions and eligibility rules for pension/OPEB prefunding (the requirement that such appropriations "supplement and not supplant" base contributions) and for what counts as infrastructure under the referenced Government Code will likely be the first fields of contention in implementation and potential litigation.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.