Legislative intelligence / 90R
SESSION 2027View project ↗

Utilities Code § 64.152: RESPONSIBILITIES OF BILLING UTILITY

No bill in the 90th Legislature changes this section yet

Follow this section in Texas Bill Atlas: a bill filed later that changes it shows up as new.

Part of Utilities Code Chapter 64, 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. 64.152. RESPONSIBILITIES OF BILLING UTILITY. (a) If a customer's telephone bill is charged for any product or service without proper customer consent or verification, the billing utility, on its knowledge or notification of any unauthorized charge, shall promptly, not later than 45 days after the date of knowledge or notification of the charge:

(1) notify the service provider to cease charging the customer for the unauthorized product or service;

(2) remove any unauthorized charge from the customer's bill;

(3) refund or credit to the customer all money that has been paid by the customer for any unauthorized charge, and if the unauthorized charge is not adjusted within three billing cycles, shall pay interest on the amount of the unauthorized charge;

(4) on the customer's request, provide the customer with all billing records under its control related to any unauthorized charge within 15 business days after the date of the removal of the unauthorized charge from the customer's bill; and

(5) maintain for at least 24 months a record of every customer who has experienced any unauthorized charge for a product or service on the customer's telephone bill and who has notified the billing utility of the unauthorized charge.

(b) A record required by Subsection (a)(5) shall contain for each unauthorized charge:

(1) the name of the service provider that offered the product or service;

(2) any affected telephone numbers or addresses;

(3) the date the customer requested that the billing utility remove the unauthorized charge;

(4) the date the unauthorized charge was removed from the customer's telephone bill; and

(5) the date any money that the customer paid for the unauthorized charges was refunded or credited to the customer.

(c) A billing utility may not:

(1) disconnect or terminate telecommunications service to any customer for nonpayment of an unauthorized charge; or

(2) file an unfavorable credit report against a customer who has not paid charges the customer has alleged were unauthorized unless the dispute regarding the unauthorized charge is ultimately resolved against the customer, except that the customer shall remain obligated to pay any charges that are not in dispute, and this subsection does not apply to those undisputed charges.

Added by Acts 1999, 76th Leg., ch. 1212, Sec. 55, eff. Sept. 1, 1999.

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.