Skip to content
Finance
Skill

/account-maintenance

Process account maintenance requests across the account lifecycle. Use when changing a client address or contact info with identity verification, updating beneficiary designations after marriage, divorce, birth, or death, re-registering or re-titling an account to a trust or new

From plugin
finance-skills
16491 skills
Install
$ npx -y skills add JoelLewis/finance_skills --skill account-maintenance --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/account-maintenance

Context preview

The summary Claude sees to decide when to auto-load this skill.

Process account maintenance requests across the account lifecycle. Use when changing a client address or contact info with identity verification, updating beneficiary designations after marriage, divorce, birth, or death, re-registering or re-titling an account to a trust or new

SKILL.md

account-maintenance.SKILL.md
name: account-maintenance
description: "Process account maintenance requests across the account lifecycle. Use when changing a client address or contact info with identity verification, updating beneficiary designations after marriage, divorce, birth, or death, re-registering or re-titling an account to a trust or new entity, selecting tax lot methods or fixing cost basis records, applying legal or compliance holds or Reg T freezes, setting up systematic withdrawals or standing instructions, processing a death notification and estate account setup, handling a QDRO, power of attorney, or guardianship, closing accounts and managing escheatment, or designing data quality review programs."

Account Maintenance

Core Concepts

Contact Information Changes

Address and contact updates are among the most frequent account maintenance requests, but they carry meaningful fraud and elder abuse risk. Firms must balance client convenience with protective controls.

**Address change procedures:**

  • **Client-initiated changes** may be submitted through the advisor, client portal, phone, or written request. Regardless of channel, the firm must verify the identity of the requesting party before processing the change. Common verification methods include knowledge-based authentication, callback to the phone number on file, or confirmation sent to the prior address or email.
  • **Advisor-initiated changes** on behalf of a client should require documented client authorization. Verbal authorization must be noted with date, time, and the identity of the person providing authorization. Written or electronic authorization is preferred and creates a stronger audit trail.
  • **Multi-system propagation** is a persistent operational challenge. When an address changes, the update must flow to all systems that store client contact data: CRM, custodian account master, correspondence system, billing system, and any third-party platforms. Failure to propagate consistently results in mail going to old addresses (privacy risk), incorrect tax form delivery (1099s, K-1s), and compliance exposure. Best practice is to designate a single system of record (typically CRM or custodian) and propagate changes outward via integration, rather than requiring manual updates in each system.
  • **Temporary vs permanent changes** should be distinguished in the workflow. A client who is traveling or has a seasonal residence may need mail temporarily redirected without changing the legal address of record. The system should support a temporary address with an expiration date that reverts to the permanent address automatically.

**Third-party address change red flags:** FINRA Regulatory Notice 07-43 and SEC guidance on senior investor protection highlight address changes as a key indicator of potential financial exploitation. Red flags that should trigger enhanced scrutiny include:

  • Address change request from someone other than the account holder (especially if followed by a distribution request)
  • Change to a P.O. Box when the prior address was a residential address
  • Change to an address associated with a known bad actor or previously flagged account
  • Multiple address changes in a short period
  • Address change for a senior investor (age 65+) followed within 30 days by a large withdrawal or wire transfer
  • Address change to a different state or country for a client with no known connection to that location

When a red flag is detected, the firm should place a temporary hold on the address change, contact the client at the prior contact information to confirm the request, and escalate to compliance or a designated senior investor protection contact if confirmation cannot be obtained.

**Notification requirements:** Many custodians and regulatory expectations require that a confirmation of the address change be sent to both the old and new addresses. This dual notification provides the client an opportunity to detect an unauthorized change. The confirmation should include the date of the change, the new address, and instructions for contacting the firm if the change was not authorized.

Beneficiary Management

Beneficiary designations determine the disposition of assets upon the account holder's death. Errors or omissions in beneficiary management are among the most consequential account maintenance failures because they are typically discovered only at death, when correction is impossible.

**Designation structure:**

  • **Primary beneficiaries** receive assets first (percentages must total 100%); **contingent beneficiaries** receive assets only if all primaries predecease or disclaim.
  • **Per stirpes vs per capita** — the election determines whether a predeceased beneficiary's share passes to their descendants (per stirpes) or redistributes to surviving beneficiaries (per capita). The operational requirement is to record the election explicitly on the custodian's form; an ambiguous or missing election is unresolvable at death.

**Beneficiary updates for life events:**

  • **Marriage:** The client may want to add a spouse as primary beneficiary. For ERISA-governed retirement plans, the spouse is the default beneficiary unless the spouse provides written consent to a different designation. For IRAs and non-ERISA accounts, there is no automatic spousal beneficiary right, but advisors should prompt a review.
  • **Divorce:** Beneficiary designations naming a former spouse are not automatically revoked by divorce in most states for non-ERISA accounts (the law varies by state and account type). The client must affirmatively update the designation. Failure to update after divorce is one of the most common and costly beneficiary errors. For ERISA plans, a QDRO may assign benefits to a former spouse regardless of the current designation.
  • **Birth or adoption:** Clients should add new children as beneficiaries or adjust percentages. Per stirpes designations may automatically include new descendants, but per capita designations do not.
  • *
Read more
Ships withfinance-skills

A collection of Claude Code skill plugins for financial services. 91 skills across 7 domain plugins teach Claude investment management, regulatory compliance, advisory workflows, trading operations, and more — so it can assist with finance questions, build

Get the whole plugin
Stats
170
Stars
34
Forks
Maintained
Maintenance
Python
Language
MIT
License
1mo ago
Last commit
6mo ago
Created

Repo: JoelLewis/finance_skills

Other skills on finance-skills.