LRO outlines how local-option property tax exemptions work, highlights thresholds and code-area complexity

The Legislative Revenue Office on March 18 told the House Committee on Revenue that local-option property tax exemptions are a small but complex subset of Oregon’s property tax expenditures and that operational details such as tax‑rate thresholds and the creation of new tax “code areas” affect how readily those exemptions can be adopted.

Bo Olen of the Legislative Revenue Office summarized the office’s review and told the committee, “I prepared some information on local option property tax exemptions, and the presentation will touch on 3 main areas, starting with a summary of local option property tax exemptions, and then, zoom in a little bit on 2 of the types of local option policies.”

The nut graf: Oregon’s tax‑expenditure report lists 140 property tax expenditures; Olen said about 27 (roughly 19%) are local‑option exemptions. Those local options skew toward partial exemptions (about two‑thirds partial, one‑third full), and many include operational features — opt‑in/opt‑out rules for individual districts, vote thresholds that extend exemptions to all districts in a code area, payment‑in‑lieu provisions, and sunset requirements — that affect revenue impacts and implementation.

Key facts Olen highlighted include: there are about 140 property tax expenditures in the tax‑expenditure report and about 27 local‑option exemptions; roughly 94 of the 140 are full exemptions overall. Ten of the local‑option exemptions use a 51% tax‑rate threshold (districts representing 51% of the tax rate must approve for the exemption to apply to all districts). Three exemptions use a 75% threshold (including brownfield development under review, seismic upgrades, and new industrial property in rural areas). Eleven local options allow a city, county, port or tribe to opt in so the exemption applies to all districts; four allow an individual district to opt in or opt out; 15 allow local governments to amend the policy; nine can be repealed by local governments; six have payment‑in‑lieu arrangements; and 19 include a statutory sunset.

Olen also explained the operational challenge of “code areas” — the distinct combinations of taxing districts that apply to a property. “When property is subject to taxes from the same set of taxing districts, they’re in the same code area,” Olen said, adding that code areas often have “6 to 9 taxing districts on average” and that Oregon has about 930 unique code areas. That matters because some local‑option mechanisms require reassignment or creation of new code areas when a single district elects to opt in or opt out.

The presentation showed how vote‑threshold rules interact with districts. Olen walked the committee through scenarios showing the percent of code areas able to satisfy various thresholds depending on which district types support the exemption. For example, if schools do not support an exemption, only about 69% of code areas could satisfy a 51% threshold and only about 1% could satisfy a 75% threshold, illustrating that thresholds requiring broad cross‑district approval are harder to meet.

Committee members asked technical questions about how often code areas change and whether an area that opts out could later opt back in; Olen said he would “have to look into the specific policies to know that” and would verify whether restrictions exist.

Ending: The committee closed the informational portion after members asked follow‑up questions about opt‑in/out mechanics and the technical steps assessors must take when code areas change. Olen provided the presentation materials and offered to answer follow‑up questions if the committee wanted additional analyses.