HB26-1387 · Bill · 2026 Regular Session · Colorado

Severance Tax Fund Expenditures

Concerning the expenditure of money from the severance tax trust fund, and, in connection therewith, allowing the state treasurer to transfer money from the severance tax perpetual base fund to the species conservation trust fund, establishing an annual transfer from the severance tax operational fund to the general fund, and reducing an appropriation.

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.

The act directs the state treasurer to annually transfer no more than $3 million from the severance tax perpetual base fund to the species conservation trust fund. The act also directs the state treasurer to, beginning on June 30, 2027, annually transfer from the severance tax operational fund to the general fund the lesser of $14.2 million or the difference between the amount of severance tax revenue projected to be deposited in the operational fund in the current fiscal year and the amount appropriated from the operational fund for certain programs in the same fiscal year. The cash funds appropriation from the severance tax operational fund for the 2026-27 state fiscal year to the department of natural resources for use by the executive director's office for the species conservation trust fund is decreased by $3,000,000. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on HB26-1387, oldest first
DateLocationAction
04/02/2026HouseIntroduced In House - Assigned to Appropriations
04/07/2026HouseHouse Committee on Appropriations Refer Amended to House Committee of the Whole
04/08/2026HouseHouse Second Reading Special Order - Laid Over Daily - No Amendments
04/09/2026HouseHouse Second Reading Special Order - Passed with Amendments - Committee
04/10/2026HouseHouse Third Reading Laid Over Daily - No Amendments
04/11/2026HouseHouse Third Reading Passed - No Amendments
04/13/2026SenateIntroduced In Senate - Assigned to Appropriations
04/14/2026SenateSenate Committee on Appropriations Refer Unamended - Consent Calendar to Senate Committee of the Whole
04/15/2026SenateSenate Second Reading Special Order - Passed - No Amendments
04/16/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-1387, oldest first
AmendmentCommittee / floor hearingOfferedDispositionOfficial document
J.001Committee amendment — Appropriations (House)04/07/2026PassedView official document

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

Full text

Official record

View HB26-1387 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

c4c401c857e40c57aaca469984691abae3e4836a869c298d00d964e124ed118a

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.