Legislative intelligence / 90R
SESSION 2027View project ↗

Estates Code § 123.151: DESIGNATION OF FORMER SPOUSE OR RELATIVE OF FORMER SPOUSE ON CERTAIN MULTIPLE-PARTY ACCOUNTS

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 Estates Code Chapter 123, 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. 123.151. DESIGNATION OF FORMER SPOUSE OR RELATIVE OF FORMER SPOUSE ON CERTAIN MULTIPLE-PARTY ACCOUNTS. (a) In this section:

(1) "Beneficiary," "multiple-party account," "party," "P.O.D. account," and "P.O.D. payee" have the meanings assigned by Chapter 113.

(2) "Public retirement system" has the meaning assigned by Section 802.001, Government Code.

(3) "Relative" has the meaning assigned by Section 123.051.

(4) "Survivorship agreement" means an agreement described by Section 113.151.

(b) If a decedent established a P.O.D. account or other multiple-party account and the decedent's marriage was later dissolved by divorce, annulment, or a declaration that the marriage is void, any payable on request after death designation provision or provision of a survivorship agreement with respect to that account in favor of the decedent's former spouse or a relative of the former spouse who is not a relative of the decedent is not effective as to that spouse or relative unless:

(1) the court decree dissolving the marriage:

(A) designates the former spouse or the former spouse's relative as the P.O.D. payee or beneficiary; or

(B) reaffirms the survivorship agreement or the relevant provision of the survivorship agreement in favor of the former spouse or the former spouse's relative;

(2) after the marriage was dissolved, the decedent:

(A) redesignated the former spouse or the former spouse's relative as the P.O.D payee or beneficiary; or

(B) reaffirmed the survivorship agreement in writing; or

(3) the former spouse or the former spouse's relative is designated to receive, or under the survivorship agreement would receive, the proceeds or benefits in trust for, on behalf of, or for the benefit of a child or dependent of either the decedent or the former spouse.

(c) If a designation is not effective under Subsection (b), a multiple-party account is payable to the named alternative P.O.D. payee or beneficiary or, if an alternative P.O.D. payee or beneficiary is not named, to the estate of the decedent.

(c-1) If the provision of a survivorship agreement is not effective under Subsection (b), for purposes of determining the disposition of the decedent's interest in the account, the former spouse or former spouse's relative who would have received the decedent's interest if the provision were effective is treated as if that spouse or relative predeceased the decedent.

(d) A financial institution or other person obligated to pay an account described by Subsection (b) that pays the account to the former spouse or the former spouse's relative as P.O.D. payee or beneficiary under a designation that is not effective under Subsection (b) is liable for payment of the account to the person provided by Subsection (c) only if:

(1) before payment of the account to the designated P.O.D. payee or beneficiary, the payor receives written notice at the home office or principal office of the payor from an interested person that the designation of the P.O.D. payee

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.