SB26-009 · Bill · 2026 Regular Session · Colorado

Charitable Organization State Sales & Use Tax

Concerning the determination of whether an entity is a charitable organization for purposes of state sales and use tax.

Official status: Became Law

6 proposed amendments

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.

Under existing law, charitable organizations are exempt from state sales and use tax. The definition of charitable organization for purposes of state sales and use tax includes criteria that mirror the federal definition of a 501(c)(3) organization. The act requires the department of revenue to presume that an organization that presents the department with a 501(c)(3) determination letter from the internal revenue service is a charitable organization for purposes of state sales and use tax. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on SB26-009, oldest first
DateLocationAction
01/14/2026SenateIntroduced In Senate - Assigned to Finance
02/03/2026SenateSenate Committee on Finance Refer Unamended to Senate Committee of the Whole
02/06/2026SenateSenate Second Reading Laid Over to 02/09/2026 - No Amendments
02/09/2026SenateSenate Second Reading Passed - No Amendments
02/10/2026SenateSenate Third Reading Passed - No Amendments
02/11/2026HouseIntroduced In House - Assigned to Finance
03/05/2026HouseHouse Committee on Finance Refer Amended to House Committee of the Whole
03/10/2026HouseHouse Second Reading Laid Over Daily - No Amendments
03/31/2026HouseHouse Second Reading Special Order - Passed with Amendments - Committee, Floor
04/01/2026HouseHouse Third Reading Laid Over Daily - No Amendments
04/02/2026HouseHouse Third Reading Passed - No Amendments
04/06/2026SenateSenate Considered House Amendments - Result was to Concur - Repass
04/07/2026SenateSigned by the President of the Senate
04/07/2026HouseSigned by the Speaker of the House
04/08/2026GovernorSent to the Governor
04/20/2026GovernorGovernor Signed

Recorded votes

Proposed amendments (6 proposed amendments)

Amendments proposed to SB26-009, oldest first
AmendmentCommittee / floor hearingOfferedDispositionOfficial document
L.001Committee amendment — Finance (House)03/05/2026PassedView official document
L.005
Sponsor: Representative DeGraaf
Floor amendment — Second Reading (House)03/31/2026LostView official document
L.007
Sponsor: Representative Richardson
Floor amendment — Second Reading (House)03/31/2026LostView official document
L.009
Sponsor: Representative Richardson
Floor amendment — Second Reading (House)03/31/2026LostView official document
L.008
Sponsor: Representative Richardson
Floor amendment — Second Reading (House)03/31/2026LostView official document
L.010
Sponsor: Representative Luck
Floor amendment — Second Reading (House)03/31/2026PassedView official document

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

Full text

Official record

View SB26-009 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

b40e674ace8ea3c12cb4cc618d6dc87104ae8bac0d93208b469a4e5ecd8186bb

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.