AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Account Maintenance

skill-joellewis-finance-skills-account-maintenance · by JoelLewis

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, se…

No reviews yet
0 installs
3 views
0.0% view→install

Install

$ agentstack add skill-joellewis-finance-skills-account-maintenance

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-joellewis-finance-skills-account-maintenance)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Account Maintenance? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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.
  • Death of a beneficiary: If a primary beneficiary dies, the firm should notify the account holder and recommend updating the designation; the per stirpes/per capita election on file determines where the predeceased beneficiary's share goes.

Retirement account beneficiary rules (SECURE Act): The SECURE Act of 2019 (and SECURE 2.0 Act of 2022) fundamentally changed inherited retirement account distribution rules:

  • Spouse beneficiaries may roll the inherited account into their own IRA, treat it as their own, or take distributions over their life expectancy — the most flexible options.
  • Eligible designated beneficiaries (minor children of the account holder, disabled or chronically ill individuals, individuals not more than 10 years younger than the deceased) may use the life expectancy method.
  • All other designated beneficiaries (including adult children and non-spouse partners) must distribute the entire inherited account within 10 years of the account holder's death. There is no annual RMD requirement during the 10-year period if the account holder died before their required beginning date; if the account holder died after their required beginning date, annual distributions may be required within the 10-year window.
  • Non-designated beneficiaries (estates, certain trusts, charities) follow either the 5-year rule or the deceased's remaining life expectancy, depending on whether the account holder died before or after the required beginning date.

These rules make beneficiary designation a critical planning decision. The choice between naming individuals, trusts, or other entities as beneficiaries has significant tax implications that should be coordinated with the tax-efficiency and financial-planning-integration skills.

TOD/POD designations: TOD (brokerage) and POD (bank) designations pass assets to named beneficiaries outside probate and override the will — the operational requirements are to document the designation on the custodian's designated form, retain a copy, and flag the account for estate-planning coordination since a stale TOD silently defeats the client's will.

Beneficiary review cadence: Best practice is to review beneficiary designations at every major life event and at minimum during the annual or biennial client review meeting. The firm should maintain a process to flag accounts with outdated or missing beneficiary designations — for example, accounts with no beneficiary on file, accounts where the designated beneficiary has a flagged death record, or accounts that have not had a beneficiary review in more than 3 years.

Account Re-Registration and Re-Titling

Re-registration changes the legal ownership or titling of an account. This is operationally more complex than a simple data update because it affects the legal rights to the account assets, may trigger tax consequences, and typically requires custodian processing with supporting documentation.

Common re-registration events:

  • Individual to revocable trust: The most frequent re-registration. Assets move from the individual's name into the trust's name. Because a revocable trust is a grantor trust (the individual retains control), this is generally not a taxable event. The trust uses the grantor's SSN as its TIN. Required documentation typically includes a trust certification, the account holder's written instruction, and (depending on the custodian) a medallion signature guarantee.
  • Name change (marriage or divorce): The account title changes to reflect the new legal name. Required documentation: legal name change document (marriage certificate, court order), government-issued ID in the new name (or a combination of old ID plus name change document), updated W-9.
  • Joint to individual (death of co-owner): For JTWROS accounts, the surviving owner becomes the sole owner. Required documentation: death certificate and letter of instruction from the surviving owner. The custodian removes the deceased owner's name from the account. For TIC accounts, the deceased owner's share passes to their estate, requiring a different process.
  • Individual to estate: Upon death, the individual account may need to be re-titled to the estate while probate is underway. Required documentation: death certificate, letters testamentary or letters of administration, EIN for the estate.
  • Trust to beneficiaries (trust termination): When a trust terminates per its terms, assets are distributed to trust beneficiaries. Required documentation: trustee certification of termination, distribution instructions, beneficiary identification and account setup.
  • Entity restructuring: LLC converting to corporation, partnership changes, mergers. Required documentation: entity formation/conversion documents, corporate resolutions, updated operating agreements.

Tax implications of re-registration:

  • Cost basis transfer: When assets are re-registered without a change in beneficial ownership (e.g., individual to revocable trust, name change), the cost basis carries over unchanged. The original acquisition dates and cost lots transfer to the new registration.
  • Step-up in basis: When assets transfer due to death, the beneficiary generally receives a stepped-up cost basis equal to the fair market value of the assets on the date of death (or alternate valuation date if elected by the estate). This step-up eliminates unrealized capital gains that existed during the decedent's lifetime. Community property assets may receive a full step-up on both halves at the first spouse's death in community property states.
  • Taxable transfers: Re-registration that constitutes a gift (e.g., transferring assets from parent to child) or a sale (e.g., transferring assets to an unrelated party) may trigger gift tax or capital gains tax. The firm should not provide tax advice but should flag these situations and recommend the client consult a tax advisor.

Medallion signature guarantee requirements: A medallion signature guarantee is a certification by a financial institution that a signature is genuine and that the signer has the authority to execute the transaction. Medallion guarantees are commonly required for: transfers of securities to a different name or entity, requests to change account registration, physical stock certificate transfers, and certain large-value transactions. The three medallion guarantee programs are STAMP (Securities Transfer Agents Medallion Program), SEMP (Stock Exchanges Medallion Program), and MSP (NYSE Medallion Signature Program). Not all financial institutions participate in all programs; the firm must verify that the guarantee is from an institution participating in an accepted program.

Custodian processing: Re-registration timelines vary significantly by custodian and complexity. Simple name changes may process in 1-3 business days. Trust re-registrations typically take 3-7 business days. Estate re-registrations and complex entity changes may take 1-4 weeks, particularly if the custodian's legal department must review trust or entity documents. During processing, the account may be in a restricted state where trading is limited. The firm should set client expectations regarding processing times and any trading restrictions during the re-registration period.

Cost Basis Management

Accurate cost basis tracking is essential for tax reporting (1099-B), client tax planning, and regulatory compliance. The firm's obligations depend on whether shares are "covered" (acquired after the applicable effective date under the Emergency Economic Stabilization Act of 2008) or "uncovered."

Tax lot accounting methods:

  • Specific identification (Spec ID): The client or advisor selects which specific tax lots to sell. This provides maximum tax control — the ability to choose lots with the highest cost basis (minimizing gains) or lowest basis (harvesting losses). Requires lot-level identification at the time of the trade, either proactively or within the settlement period.
  • First In, First Out (FIFO): The oldest shares are deemed sold first. This is the IRS default method if no other method is elected. FIFO tends to produce long-term capital gains (favorable tax rates) but may not minimize total tax liability.
  • Last In, First Out (LIFO): The most recently acquired shares are deemed sold first. This tends to produce short-term capital gains but may result in lower gain amounts if recent purchases were at higher prices.
  • Highest In, First Out (HIFO): The shares with the highest cost basis are deemed sold first. This minimizes realized gains and is often the preferred method for taxable accounts focused on tax efficiency.
  • Average cost: Available only for mutual fund shares and shares acquired through dividend reinvestment plans. The average cost of all shares is used as the basis for each share sold. Once elected for a specific fund, average cost applies to all shares of that fund in the account.

Cost basis transfer rules:

  • ACATS transfers: Cost basis transfer mechanics between firms (covered vs uncovered shares, the CBRS 15-day window, IRC Section 6045A) are covered in account-transfers; the maintenance-side obligation is to verify the received basis against client records and resolve discrepancies promptly.
  • Re-registration transfers: Cost basis carries over in non-taxable re-registrations (e.g., individual to revocable trust). For transfers due to death, the receiving account should reflect the stepped-up basis as of the date of death.
  • Gift transfers: The recipient generally takes the donor's cost basis (carryover basis) for gains. If the fair market value at the time of gift is less than the donor's basis, special rules apply for determining basis for loss purposes (the basis is the FMV at the date of the gift).

Corporate action adjustments: Corporate actions frequently alter cost basis, and errors in corporate action processing are a leading source of cost basis inaccuracies:

  • Stock splits and reverse splits: The total cost basis remains the same; per-share basis adjusts proportionally. A 2-for-1 split halves the per-share basis; a 1-for-10 reverse split multiplies per-share basis by 10.
  • Mergers and acquisitions: If the merger is a tax-free reorganization (stock-for-stock exchange), the cost basis of the old shares carries over to the new shares, allocated proportionally. If the merger involves cash consideration (cash-and-stock deal), the cash portion is taxable and reduces the basis allocated to the new shares.
  • Spin-offs: The cost basis of the parent company shares is allocated between the parent and the spun-of

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.