Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the State Budget Retiree Health topic
No spam. Unsubscribe anytime.
Senate finance panel debates making retiree health accounts non‑lapsing, timing for ERP funds
Summary
Senate Finance members debated language to make retiree health funds non‑lapsing and how to handle unspent ERP (enterprise resource planning) appropriations so the state can cover late claims and the ERP go‑live schedule without hurting the rainy‑day drawdown.
The Senate Finance Committee discussed whether retiree health funds should be designated non‑lapsing and how to treat unspent ERP (enterprise resource planning) appropriations as the committee considered the governor’s budget adjustments.
The debate focused on timing and budget mechanics: lawmakers asked whether lapsing certain appropriations on June 30 would increase the committee chair’s draw on the rainy‑day fund and whether those dollars could instead be reappropriated July 1 to cover planned ERP expenses. Committee members agreed the ERP go‑live date is likely in spring 2026 and that extending the appropriation could keep funds available until the system is operational.
The committee also discussed retiree health funding mechanics and the desire for a modest reserve to handle trailing claims. A staff member explained the existing structure: "The retiree health funds don't lapse in the first year and they lapse after the second year." The chair said he would prefer "for retiree health to never lapse and that money to always be available," while noting fiscal staff can recommend statutory reserve targets and that fiscal already reports balances regularly.
Committee members and staff described three layers of reserves used to manage retiree health: (1) the statutory reserve required by law, (2) an operating or cash‑flow reserve maintained for month‑to‑month fluctuations, and (3) an IBNR (incurred but not reported) amount intended to cover late‑reported claims. Committee discussion emphasized past experience: committee members noted the state has routinely lapsed funds in the second year and managed without crisis, but some members pressed for a contingency in case of unusually large claims tied to new therapies or other healthcare cost volatility.
On timing, members suggested the effective date for any change could be shifted to July 1 (or Jan. 1 of a subsequent year in discussion) so that lapses and reappropriations line up with fiscal operations and reduce the chair’s rainy‑day draw concerns. The committee agreed to hold final language to allow time to draft statutory text and set a lapse amount that could be reappropriated in the next fiscal year.
No formal vote on making retiree health non‑lapsing occurred during the session; several related items (9, 10 and 11 in the packet) were placed on hold for additional drafting and fiscal review.
