Legislative intelligence / 90R
SESSION 2027View project ↗

Business and Commerce Code § 271.004: DETERMINATION OF REASONABLE RELATION OF TRANSACTION TO PARTICULAR JURISDICTION

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 271, 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. 271.004. DETERMINATION OF REASONABLE RELATION OF TRANSACTION TO PARTICULAR JURISDICTION. (a) For purposes of this chapter, a transaction bears a reasonable relation to a particular jurisdiction if the transaction, the subject matter of the transaction, or a party to the transaction is reasonably related to that jurisdiction.

(b) A transaction bearing a reasonable relation to a particular jurisdiction includes:

(1) a transaction in which:

(A) a party to the transaction is a resident of that jurisdiction;

(B) a party to the transaction has the party's place of business or, if that party has more than one place of business, the party's chief executive office or an office from which the party conducts a substantial part of the negotiations relating to the transaction, in that jurisdiction;

(C) all or part of the subject matter of the transaction is located in that jurisdiction;

(D) a party to the transaction is required to perform in that jurisdiction a substantial part of the party's obligations relating to the transaction, such as delivering payments;

(E) a substantial part of the negotiations relating to the transaction occurred in or from that jurisdiction and an agreement relating to the transaction was signed in that jurisdiction by a party to the transaction; or

(F) all or part of the subject matter of the transaction is related to the governing documents or internal affairs of an entity formed under the laws of that jurisdiction, such as:

(i) an agreement among members or owners of the entity, an agreement or option to acquire a membership or ownership interest in the entity, and the conversion of debt or other securities into an ownership interest in the entity; and

(ii) any other matter relating to rights or obligations with respect to the entity's membership or ownership interests; and

(2) a transaction in which:

(A) all or part of the subject matter of the transaction is a loan or other extension of credit in which a party lends, advances, borrows, or receives, or is obligated to lend or advance or entitled to borrow or receive, money or credit with an aggregate value of at least $25 million;

(B) at least three financial institutions or other lenders or providers of credit are parties to the transaction;

(C) the particular jurisdiction is in the United States; and

(D) a party to the transaction has more than one place of business and has an office in that particular jurisdiction.

(c) If a transaction bears a reasonable relation to a particular jurisdiction at the time the parties enter into the transaction, the transaction shall continue to bear a reasonable relation to that jurisdiction regardless of:

(1) any subsequent change in facts or circumstances with respect to the transaction, the subject matter of the transaction, or any party to the transaction; or

(2) any modification, amendment, renewal, extension, or restatement of any agreement relating to the transaction.

Added by Acts 2007, 80th Leg., R.S., Ch. 885

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.