Legislative intelligence / 90R
SESSION 2027View project ↗

Transportation Code § 228.012: PROJECT SUBACCOUNTS

1 bill in the 90th Legislature would change this section

Part of Transportation Code Chapter 228, with every bill that changes it.

Bills are matched to sections automatically from their text and can be missed, for example when a bill changes a whole chapter at once or renumbers sections. No bill listed here does not mean no bill changes this section.

Current law

Sec. 228.012. PROJECT SUBACCOUNTS. (a) The department shall create a separate account in the state highway fund to hold payments received by the department under a comprehensive development agreement and the surplus revenue of a toll project or system. The department shall create subaccounts in the account for each project, system, or region. Interest earned on money in a subaccount shall be deposited to the credit of that subaccount.

(b) The department shall hold money in a subaccount in trust for the benefit of the region in which a project or system is located and may assign the responsibility for allocating money in a subaccount to a metropolitan planning organization in which the region is located for projects approved by the department. At the time the project is approved by the department money shall be allocated and distributed to projects authorized by Section 228.0055 or Section 228.006, as applicable.

(c) Repealed by Acts 2021, 87th Leg., R.S., Ch. 856 (S.B. 800), Sec. 25(18), eff. September 1, 2021.

(d) The commission or the department may not:

(1) revise the formula as provided in the department's unified transportation program or a successor document in a manner that results in a decrease of a department district's allocation because of the deposit of a payment into a project subaccount; or

(2) take any other action that would reduce funding allocated to a department district because of the deposit of a payment into a project subaccount.

Added by Acts 2007, 80th Leg., R.S., Ch. 264 (S.B. 792), Sec. 7.01, eff. June 11, 2007.

Amended by:

Acts 2011, 82nd Leg., R.S., Ch. 1196 (S.B. 19), Sec. 4, eff. June 17, 2011.

Acts 2011, 82nd Leg., R.S., Ch. 1345 (S.B. 1420), Sec. 35, eff. September 1, 2011.

Acts 2013, 83rd Leg., R.S., Ch. 1312 (S.B. 59), Sec. 92, eff. September 1, 2013.

Acts 2021, 87th Leg., R.S., Ch. 856 (S.B. 800), Sec. 25(18), eff. September 1, 2021.

Links

Texas Bill Atlas is an independent research tool, not an official state website.

PLEASE READ

Before you use Texas Bill Atlas

An independent, open-source project. This site is not affiliated with, endorsed by, or operated by the Texas Legislature, the Texas Legislative Council, the Secretary of State, or any state agency.

Data may be incomplete, delayed, or wrong. Bill records are copied automatically from the legislature’s public files. Topic, agency, party, influence and last-action tags, and the full-text summaries written by Luna (an AI model), are automated interpretations and can be mistaken.

Not advice. Nothing here is legal, political, or professional advice. The project and its contributors make no warranty of accuracy or completeness and accept no liability for errors, omissions, or decisions made using this site.

Check the official record. Confirm anything that matters on Texas Legislature Online. Spotted a mistake? Report it on GitHub.

TEXAS BILL ATLAS

Privacy Policy

Last updated: November 11, 2026

Texas Bill Atlas is a free, independent, open-source project. We believe you should be able to research legislation without creating an account or providing personal information.

Information we collect

We do not require registration, names, email addresses, or other personal information to use the service.

We do not sell personal information, serve targeted advertising, or intentionally track individual browsing activity.

Analytics and security

We use Cloudflare for website delivery, security, and traffic analytics.

Cloudflare may process technical information such as IP addresses, browser details, request information, and website usage statistics. Cloudflare may also use cookies necessary for security and abuse prevention.

For more information, see Cloudflare's Privacy Policy.

Watchlists and saved preferences

Watchlists and preferences are stored locally in your browser by default.

If you choose to enable watchlist synchronization, we store the selected bill numbers, the member codes of legislators you follow, your saved searches (their names, search words and filters), filters, and hashed access keys on our server. View-only links show the bill numbers only.

No account or personal information is required. Anyone possessing a valid private access link may access the associated watchlist according to that link's permissions.

You can delete a synced watchlist using its edit access key. Inactive synced watchlists are automatically removed after approximately one year.

Technical data

Our servers may temporarily process IP addresses and request information for security, rate limiting, and reliable operation.

We do not use this information to build individual user profiles.

The site also loads certain external resources, including Google Fonts. Those providers may receive ordinary technical request information.

Third-party services

Links to government websites, GitHub, and other external services are governed by their respective privacy policies.

Changes

We may update this policy as the project develops. The current version will be available on this website with its updated date.

Questions

For questions about the project or its privacy practices, visit our GitHub repository.