Legislative intelligence / 90R
SESSION 2027View project ↗

Business Organizations Code § 402.003: EARLY ADOPTION OF CODE BY EXISTING DOMESTIC ENTITY

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 Organizations Code Chapter 402, 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. 402.003. EARLY ADOPTION OF CODE BY EXISTING DOMESTIC ENTITY. (a) A domestic entity formed before the effective date of this code may voluntarily elect to adopt and become subject to this code by:

(1) adopting the code by complying with the procedures for approval, under prior law and its governing documents, of an amendment to:

(A) its articles of incorporation, with respect to a corporation or cooperative association;

(B) its regulations, with respect to a limited liability company;

(C) its articles of association, with respect to a professional association;

(D) its declaration of trust, with respect to a real estate investment trust;

(E) its partnership agreement, with respect to a partnership; or

(F) its primary governing document, with respect to another type of domestic entity;

(2) if any of its governing documents, including its certificate of formation, do not comply with this code, complying with the procedures, under prior law and its governing documents, to amend the noncomplying governing documents to comply with this code, including filing with the filing officer in accordance with Chapter 4 a certificate of amendment to cause its certificate of formation to comply with this code; and

(3) if the domestic entity is a filing entity, filing with the filing officer in accordance with Chapter 4 a statement that the filing entity is electing to adopt this code.

(b) A domestic entity that elected to adopt and become subject to this code as provided by Subsection (a) is not considered to have failed to comply with Subsection (a)(2) because:

(1) the entity's governing documents do not state the type of entity formed; or

(2) a circumstance described by Section 402.0051 applies.

Acts 2003, 78th Leg., ch. 182, Sec. 1, eff. Jan. 1, 2006.

Amended by:

Acts 2007, 80th Leg., R.S., Ch. 688 (H.B. 1737), Sec. 139, eff. September 1, 2007.

Acts 2011, 82nd Leg., R.S., Ch. 139 (S.B. 748), Sec. 59, eff. September 1, 2011.

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.