RogataEvery bill, laid before the people.

HB26-1403 · Bill · 2026 Regular Session · Colorado

Information Technology Depreciation Lease Payments

Concerning the prevention of the transfer of unexpended information technology annual depreciation-lease equivalent payments to the general fund.

Official status: Became Law

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 requires an amount equivalent to the recorded depreciation or amortization of an information technology asset acquired, repaired, improved, replaced, renovated, or constructed with an appropriation from the information technology capital account in the capital construction fund based on the depreciation period (information technology annual depreciation-lease equivalent payment) to be credited and transferred to the information technology capital account within the capital construction fund. Current law also requires the state treasurer to transfer any unappropriated balances in the information technology capital account or any otherwise unexpended and unencumbered money remaining in the information technology capital account at the end of a fiscal year to the general fund. The act prohibits the state treasurer from transferring any money that was transferred, credited, or paid into the information technology capital account as an information technology annual depreciation-lease equivalent payment back to the general fund at the end of a fiscal year, for state fiscal years commencing on or after July 1, 2026. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on HB26-1403, oldest first
DateLocationAction
04/02/2026HouseIntroduced In House - Assigned to Appropriations
04/06/2026HouseHouse Committee on Appropriations Refer Unamended 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 - No Amendments
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

Full text

Official record

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

a28d5af469c2177b507513b2b14b4b688dbd3e9bed8e300d4ac36586935f3c60

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.