Legislative intelligence / 90R
SESSION 2027View project ↗

Transportation Code § 372.0535: FINANCIAL REPORTING REQUIREMENTS

1 bill in the 90th Legislature would change this section

Part of Transportation Code Chapter 372, 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. 372.0535. FINANCIAL REPORTING REQUIREMENTS. (a) In this section, "system" includes a system established under Section 228.010, 366.034, or 370.034.

(b) Not later than the 180th day after the last day of a toll project entity's fiscal year, the entity shall publish on the entity's Internet website a report on the entity's financial data, including:

(1) the final maturity of all bonds issued by the entity for a toll project or system;

(2) toll revenue for each toll project for the previous fiscal year;

(3) an accounting of total revenue collected and expenses incurred by the entity for the previous fiscal year, such as debt service, maintenance and operation costs, any other miscellaneous expenses, and any surplus revenue; and

(4) a capital improvement plan with proposed or expected capital expenditures over a period determined by the entity.

(c) In addition to the reporting requirements under Subsection (b), a toll project entity may report any money deposited by the entity in a debt service reserve fund as required by a bondholder agreement.

(d) A toll project entity may publish on the entity's Internet website graphs or tables from the entity's certified audited financial report or annual continuing disclosure report to comply with the reporting requirements under Subsection (b).

(e) A toll project entity shall prominently display on the entity's Internet website a link to the report under Subsection (b). The report must be posted separately from the entity's certified audited financial report.

(f) Notwithstanding Subsection (b), for a toll project that is the subject of a comprehensive development agreement entered into by a toll project entity, the entity is only required to publish on the entity's Internet website the name and cost of the toll project and the termination date of the agreement.

Added by Acts 2019, 86th Leg., R.S., Ch. 744 (H.B. 803), Sec. 1, eff. September 1, 2019.

Redesignated from Transportation Code, Section 372.054 by Acts 2021, 87th Leg., R.S., Ch. 915 (H.B. 3607), Sec. 21.001(105), 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.