Legislative intelligence / 90R
SESSION 2027View project ↗

Tax Code § 351.1066: ALLOCATION OF REVENUE: CERTAIN MUNICIPALITIES

1 bill in the 90th Legislature would change this section

Part of Tax Code Chapter 351, 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. 351.1066. ALLOCATION OF REVENUE: CERTAIN MUNICIPALITIES. (a) This section applies only to:

(1) a municipality with a population of at least 3,500 but less than 5,500 that is the county seat of a county with a population of less than 50,000 that borders a county with a population of more than 1.6 million;

(2) a municipality with a population of at least 2,800 but less than 3,500 that is the county seat of a county with a population of less than 22,000 that is bordered by the Trinity River and includes a state park and a portion of a wildlife management area;

(3) a municipality with a population of at least 8,000 that is located in a county that borders the Pecos River and that has a population of not more than 15,000;

(4) a municipality with a population of not more than 15,000 that is located in a county through which the Frio River flows and an interstate highway crosses, and that has a population of at least 15,000;

(5) a municipality with a population of not less than 7,500 that is located in a county with a population of not less than 40,000 but less than 250,000 that is adjacent to a county with a population of less than 750;

(6) a municipality that is the county seat of a county with a population of at least 8,500 and that county contains part of the Chaparral Wildlife Management Area; and

(7) a municipality that has a population of not more than 25,000, that contains a cultural heritage museum, and that is located in a county that borders the United Mexican States and the Gulf of Mexico.

(b) Notwithstanding any other provision of this chapter, a municipality to which this section applies may use all or any portion of the revenue derived from the municipal hotel occupancy tax for:

(1) the construction, enlarging, equipping, improvement, maintenance, repairing, and operation of a recreational facility to substantially enhance hotel activity and encourage tourism; and

(2) the construction, enlarging, equipping, improvement, maintenance, repairing, and operation of an arena used for rodeos, livestock shows, and agricultural expositions to substantially enhance hotel activity and encourage tourism.

(c) A municipality to which this section applies may not use municipal hotel tax revenue to construct or expand a facility described by Subsection (b) in an amount that would exceed the amount of hotel revenue in the area that is likely to be reasonably attributable to events held at that facility during the 15-year period beginning on the date the construction or expansion is completed.

(d) An independent analyst or consultant hired by the municipality must make the projection required by Subsection (c).

(e) A municipality that uses municipal hotel occupancy tax revenue under this section shall annually prepare a report that describes:

(1) the events held during the preceding year at each facility that received municipal hotel occupancy tax revenue from the municipality during that year; and

(2) the number of hotel room nights, h

The section continues: whole chapter.

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.