HB26-1059 · Bill · 2026 Regular Session · Colorado

Cost Recovery Cash Fund Consolidation

Concerning the cash funds created in connection with money retained by the department of revenue to mitigate the administrative costs incurred by the department in collecting certain charges.

Official status: Became Law

1 proposed amendment

Prime sponsors

Progress (from the official record)

Official summary

Official text — shown in English exactly as published by the official source. The official text controls.

Current law allows the department of revenue (department) to retain an amount equal to its administrative costs in collecting, administering, and enforcing the production fees for clean transit and wildlife and land remediation, the enterprise per ride fees, the retail delivery fees, and the enterprise retail delivery fees. Current law also allows the department to retain 3% of the prepaid wireless trust cash fund to mitigate administrative costs. The money retained by the department is currently transmitted into multiple individual cost recovery cash funds that are used to mitigate the department's administrative costs of collecting those fees and charges. These cash funds include the oil and gas production fees collection fund, the enterprise per ride fees fund, and the retail delivery fees fund (cost recovery funds). The act repeals each of these cost recovery funds and directs the state treasurer to transmit the money retained by the department to mitigate the department's administrative costs for all the programs into a single cost recovery cash fund, which is created in the act. The act also requires the department to submit an annual report starting November 1, 2027, to the joint budget committee with information about the costs associated with collecting, administering, and enforcing the fees and, where applicable, the specific tasks that contribute significantly to the fee collection workload. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on HB26-1059, oldest first
DateLocationAction
01/14/2026HouseIntroduced In House - Assigned to Finance
01/29/2026HouseHouse Committee on Finance Refer Unamended to Appropriations
05/01/2026HouseHouse Committee on Appropriations Refer Amended to House Committee of the Whole
05/01/2026HouseHouse Second Reading Special Order - Passed with Amendments - Committee
05/04/2026HouseHouse Third Reading Passed - No Amendments
05/05/2026SenateIntroduced In Senate - Assigned to Finance
05/07/2026SenateSenate Committee on Finance Refer Unamended to Appropriations
05/08/2026SenateSenate Committee on Appropriations Refer Unamended - Consent Calendar to Senate Committee of the Whole
05/08/2026SenateSenate Second Reading Special Order - Passed - No Amendments
05/11/2026SenateSenate Third Reading Passed - No Amendments
05/28/2026HouseSigned by the Speaker of the House
05/28/2026SenateSigned by the President of the Senate
05/28/2026GovernorSent to the Governor
05/29/2026GovernorGovernor Signed

Recorded votes

Proposed amendments (1 proposed amendment)

Amendments proposed to HB26-1059, oldest first
AmendmentCommittee / floor hearingOfferedDispositionOfficial document
L.001Committee amendment — Appropriations (House)05/01/2026PassedView official document

Source: Colorado General Assembly (leg.colorado.gov) · Data as of

Full text

Official record

View HB26-1059 on leg.colorado.gov

Source: Colorado General Assembly (leg.colorado.gov) · Data as of

Verify this record

This record carries a fingerprint of its official content, computed by our data pipeline with the SHA-256 algorithm — a real computation over the record itself, not a badge we award ourselves. Anyone can recompute it from the official source and compare.

SHA-256 fingerprint

2601510ba202205a59696e01da860da70f5db3cb5e36975b6ed29ac1bdcdfd14

What it covers: the record exactly as the official source publishes it — its identifiers (bill number, session, jurisdiction), its official title and long title, its official summary, its status, its sponsors in published order, every recorded action, every recorded vote, and the link to each official text version — assembled in a fixed canonical form described on the How this data works page.

Computed 2026-11-06 · Algorithm: SHA-256 · Canonical form: rogata-canonical-v1

Source: Colorado General Assembly (leg.colorado.gov) · Data as of

The fingerprint does not cover our retrieval date (the “Data as of” stamp in the source line): re-fetching unchanged official content produces the same fingerprint, while any change to the official content changes it.

If you recompute the fingerprint from the official source and get a different value, one of us is out of date — please report it through the corrections log.