S1320 is a code-cleanup bill that removes obsolete statutory language connected to the state's Business Information Infrastructure project and revises the State Controller's statutory project authority. The bill frames the changes as routine housekeeping under the Idaho Code Cleanup Act and declares an emergency effective July 1, 2026.
The changes are narrowly targeted, but they touch funding and governance language for a major enterprise IT effort. For compliance officers and state finance staff, the bill matters because it alters the statute-based funding mechanics and leaves open questions about how remaining project costs and any existing balances should be handled administratively.
At a Glance
What It Does
The bill repeals the statute that established the Business Information Infrastructure Fund (Section 67-1021C) and amends Section 67-1021A to retain the State Controller's authority to modernize and consolidate financial, payroll, human capital, budget and procurement systems into a centralized ERP. The amendment also keeps a now-expired transfer timetable tying indirect cost recovery moneys to the repealed fund.
Who It Affects
State Controller's Office, state agencies that use financial/payroll/HCM systems, the agencies that administer the indirect cost recovery fund under Section 67-3531, and vendors/consultants involved in ERP work. Budget and accounting officers will be the practical points of impact.
Why It Matters
Removing an earmarked fund statute can change how ERP modernization is financed and accounted for; leaving an amendment that references a repealed section and a past transfer deadline creates legal and fiscal ambiguity that agencies and auditors will need to resolve.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
S1320 approaches the Business Information Infrastructure project as a housekeeping matter. It instructs that the State Controller continue — in statute — to pursue a modernization project focused on consolidating the state's financial, payroll, human capital management, budget and procurement systems into a single enterprise resource planning (ERP) environment.
That project description remains in the amended Section 67-1021A and thus continues to express legislative authorization for the Controller's role in the effort.
Concurrently, the bill repeals the separate statutory provision that had created a dedicated Business Information Infrastructure Fund. The amended Section 67-1021A keeps language about distributing modernization costs equitably across state and public entities and preserves a mechanism that had required transfers from the indirect cost recovery fund.
Critically, the transfer language in the amendment refers to annual transfers that were to occur only through June 30, 2023, and directs that transfers be made as requested by the State Controller.Because the repeal and the amendment take effect under an emergency clause on July 1, 2026, the practical effect is immediate statutory change. That immediacy raises operational questions: with the fund repealed, where — legally and administratively — should amounts that were previously directed to the fund be held or spent, and how will agencies document cost-sharing?
The bill leaves those operational details to administrative practice and existing accounting rules rather than creating replacement statutory mechanics.
The Five Things You Need to Know
The bill repeals Section 67-1021C, the statute that established the Business Information Infrastructure Fund.
It keeps an updated Section 67-1021A that authorizes the State Controller to modernize and consolidate financial, payroll, human capital management, budget and procurement systems into an enterprise resource planning system.
Section 67-1021A, as amended, requires that modernization costs be equitably distributed among all state and public entities using the affected services and functions.
The amendment preserves a transfer mechanism directing annual transfers from moneys deposited to the indirect cost recovery fund (pursuant to Section 67-3531) to the business infrastructure fund, but the timetable in the text limits those transfers only through June 30, 2023.
The act declares an emergency and becomes effective July 1, 2026, making the repeal and amendment immediately operative for the next fiscal year.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Legislative intent and cleanup framing
This section states the Legislature's intent to streamline Idaho Code under the Idaho Code Cleanup Act. Practically, it grounds the bill as a codified housekeeping measure and signals that the changes are intended to remove provisions identified as obsolete rather than to create new policy. That framing matters because courts and agencies sometimes use legislative intent language when interpreting ambiguous edits.
Repeal of the Business Information Infrastructure Fund (67-1021C)
This provision removes the statute that created and governed the dedicated fund for the ERP modernization. Repeal removes the legal basis for an earmarked cash account in statute; absent other authority, any continuing balances and future earmarking must be handled under general fiscal law, appropriation acts, or administrative rules. The repeal is clean in title, but it creates an immediate legal gap where a previously statutory funding vehicle existed.
Controller's project authority and transfer language
Section 67-1021A is rewritten to retain the Controller's authority to lead and consolidate state business systems into an ERP and to require equitable cost distribution among state and public entities. It also preserves language directing transfers from the indirect cost recovery fund (per Section 67-3531) to the now-repealed fund, but those transfers are limited by a date range that runs through June 30, 2023. The result is a statutory mismatch: the operational-project description remains active while the fund named as the transfer destination no longer exists in code.
Emergency clause and effective date
The bill includes an emergency declaration making the act effective July 1, 2026. That timing is immediate enough to matter for fiscal-year planning and accounting: agencies must treat the statutory repeal and amendment as operative for the coming fiscal year, which pressures finance offices to resolve how to treat any residual balances or future cost allocations in the absence of the statutory fund.
This bill is one of many.
Codify tracks hundreds of bills on Government across all five countries.
Explore Government in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- State Controller's Office — gains a streamlined statutory authorization to continue ERP modernization work without maintaining a duplicate or outdated fund statute, reducing legal clutter.
- State agencies using finance/payroll/HCM systems — may see simplified statute governing the Controller's project authority, which can reduce procedural friction for participation in a centralized ERP.
- State auditors and legal staff — benefit from removal of obsolete statutory language that previously required them to track a fund that is no longer actively used.
Who Bears the Cost
- State agency budget and accounting offices — must resolve where to hold and track funds that were previously directed to the repealed fund and may need to revise internal chargeback or cost-allocation procedures.
- Legislative fiscal staff and the Controller's finance team — will need to reconcile statutes with actual cash balances and may face increased workload to document transitions or to draft follow-up provisions.
- Vendors and contractors — face uncertainty in contracting and invoicing if procurement or payment paths that were previously routed through the statutory fund are no longer available, potentially delaying payments or contract starts.
Key Issues
The Core Tension
The central dilemma is between tidy statutory housekeeping and fiscal/legal continuity: cleaning up obsolete code eliminates clutter and potential confusion over long-unused provisions, but removing a statutory funding vehicle (and leaving behind dated transfer language) risks creating funding gaps, audit exposures, and administrative uncertainty that the statute does not resolve.
The most immediate implementation challenge is the statutory mismatch the bill creates. Repealing the dedicated fund statute while leaving transfer directions that name that fund — and limiting transfers to a period that expired in 2023 — produces an ambiguity about whether any statutory authority remains to move indirect cost recovery money for ERP purposes.
Agencies and auditors will need to interpret whether the transfer language survives as a historical relic, or whether the repeal extinguishes the destination for those transfers.
A second tension concerns fiscal continuity. The bill removes an earmarked vehicle that may have been used to segregate ERP modernization funds.
Removing that vehicle without creating a replacement mechanism shifts the burden onto administrative accounting rules, appropriations language, or informal interagency agreements to preserve equitable cost-sharing. That puts negotiating power and practical discretion in the hands of executive branch administrators rather than embedding distribution mechanics in statute, which could create uneven treatment across agencies or create audit findings.
Finally, the emergency effective date compresses the timeline for resolving these questions. If balances remain in accounts or if agencies planned budgets around the statutory fund, the Controller and state finance officers will need to coordinate quickly to avoid payment interruptions, contested cost allocations, or breaches of procurement commitments.
The bill leaves these operational fixes to administrative actors rather than providing statutory directives, so follow-up guidance or corrective legislation is likely necessary.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.