Legislative intelligence / 90R
SESSION 2027View project ↗

Business and Commerce Code § 8.105: NOTICE OF ADVERSE CLAIM

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 Business and Commerce Code Chapter 8, 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. 8.105. NOTICE OF ADVERSE CLAIM. (a) A person has notice of an adverse claim if:

(1) the person knows of the adverse claim;

(2) the person is aware of facts sufficient to indicate that there is a significant probability that the adverse claim exists and deliberately avoids information that would establish the existence of the adverse claim; or

(3) the person has a duty, imposed by statute or regulation, to investigate whether an adverse claim exists, and the investigation so required would establish the existence of the adverse claim.

(b) Having knowledge that a financial asset or interest therein is or has been transferred by a representative imposes no duty of inquiry into the rightfulness of a transaction and is not notice of an adverse claim. However, a person who knows that a representative has transferred a financial asset or interest therein in a transaction that is, or whose proceeds are being used, for the individual benefit of the representative or otherwise in breach of duty has notice of an adverse claim.

(c) An act or event that creates a right to immediate performance of the principal obligation represented by a security certificate or sets a date on or after which the certificate is to be presented or surrendered for redemption or exchange does not itself constitute notice of an adverse claim except in the case of a transfer more than:

(1) one year after a date set for presentment or surrender for redemption or exchange; or

(2) six months after a date set for payment of money against presentation or surrender of the certificate, if money was available for payment on that date.

(d) A purchaser of a certificated security has notice of an adverse claim if the security certificate:

(1) whether in bearer or registered form, has been indorsed "for collection" or "for surrender" or for some other purpose not involving transfer; or

(2) is in bearer form and has on it an unambiguous statement that it is the property of a person other than the transferor, but the mere writing of a name on the certificate is not such a statement.

(e) Filing of a financing statement under Chapter 9 is not notice of an adverse claim to a financial asset.

Amended by Acts 1995, 74th Leg., ch. 962, Sec. 1, eff. Sept. 1, 1995.

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.