Legislative intelligence / 90R
SESSION 2027View project ↗

Business and Commerce Code § 9.406: DISCHARGE OF ACCOUNT DEBTOR; NOTIFICATION OF ASSIGNMENT; IDENTIFICATION AND PROOF OF ASSIGNMENT; RESTRICTIONS ON ASSIGNMENT OF ACCOUNTS, CHATTEL PAPER, PAYMENT INTANGIBLES, AND PROMISSORY NOTES INEFFECTIVE

1 bill in the 90th Legislature would change this section

Part of Business and Commerce Code Chapter 9, 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. 9.406. DISCHARGE OF ACCOUNT DEBTOR; NOTIFICATION OF ASSIGNMENT; IDENTIFICATION AND PROOF OF ASSIGNMENT; RESTRICTIONS ON ASSIGNMENT OF ACCOUNTS, CHATTEL PAPER, PAYMENT INTANGIBLES, AND PROMISSORY NOTES INEFFECTIVE. (a) Subject to Subsections (b)-(i), an account debtor on an account, chattel paper, or a payment intangible may discharge its obligation by paying the assignor until, but not after, the account debtor receives a notification, authenticated by the assignor or the assignee, that the amount due or to become due has been assigned and that payment is to be made to the assignee. After receipt of the notification, the account debtor may discharge its obligation by paying the assignee and may not discharge the obligation by paying the assignor.

(b) Subject to Subsection (h), notification is ineffective under Subsection (a):

(1) if it does not reasonably identify the rights assigned;

(2) to the extent that an agreement between an account debtor and a seller of a payment intangible limits the account debtor's duty to pay a person other than the seller and the limitation is effective under law other than this chapter; or

(3) at the option of an account debtor, if the notification notifies the account debtor to make less than the full amount of any installment or other periodic payment to the assignee, even if:

(A) only a portion of the account, chattel paper, or payment intangible has been assigned to that assignee;

(B) a portion has been assigned to another assignee; or

(C) the account debtor knows that the assignment to that assignee is limited.

(c) Subject to Subsection (h), if requested by the account debtor, an assignee shall seasonably furnish reasonable proof that the assignment has been made. Unless the assignee complies, the account debtor may discharge its obligation by paying the assignor, even if the account debtor has received a notification under Subsection (a).

(d) Except as otherwise provided in Subsection (e) and Sections 2A.303 and 9.407, and subject to Subsection (h), a term in an agreement between an account debtor and an assignor or in a promissory note is ineffective to the extent that it:

(1) prohibits, restricts, or requires the consent of the account debtor or person obligated on the promissory note to the assignment or transfer of, or the creation, attachment, perfection, or enforcement of a security interest in, the account, chattel paper, payment intangible, or promissory note; or

(2) provides that the assignment or transfer or the creation, attachment, perfection, or enforcement of the security interest may give rise to a default, breach, right of recoupment, claim, defense, termination, right of termination, or remedy under the account, chattel paper, payment intangible, or promissory note.

(e) Subsection (d) does not apply to the sale of a payment intangible or promissory note, other than a sale pursuant to a disposition under Section 9.610 or an acceptance of collateral under Section 9.620.

(f) Exc

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.