account-maintenance
Process account maintenance requests across the full account lifecycle. Use when changing a client address or contact info and verifying identity, 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 accounting methods or fixing cost basis records, applying legal holds compliance holds or Reg T freezes, setting up systematic withdrawals automatic investments or dividend reinvestment, processing a death notification or estate account setup, handling a QDRO or divorce decree for retirement accounts, responding to power of attorney or guardianship situations, closing accounts and managing escheatment, or designing periodic account review and data quality programs.
What this skill does
# Account Maintenance ## Purpose Guide the operations of ongoing account maintenance in brokerage and advisory firms. Covers address and contact changes, beneficiary updates, account re-registration and re-titling, cost basis management, account restrictions and holds, standing instructions, and lifecycle events (marriage, divorce, death, incapacity). Enables designing and operating efficient account maintenance processes that satisfy regulatory requirements while minimizing operational risk. ## Layer 12 — Client Operations (Account Lifecycle & Servicing) ## Direction both ## When to Use - Processing a client address or contact information change and determining identity re-verification requirements - Updating primary or contingent beneficiary designations after a life event - Re-registering or re-titling an account (individual to trust, name change, entity restructuring) - Selecting or changing tax lot accounting methods and managing cost basis records - Applying or removing account restrictions (legal hold, compliance hold, Reg T freeze, death notification) - Setting up or modifying standing instructions (systematic withdrawals, automatic investments, dividend reinvestment, standing wire/ACH) - Processing a death notification, including account freeze, beneficiary claim, and estate account setup - Handling divorce decree processing, including QDRO for retirement accounts and account division - Responding to incapacity situations involving power of attorney or guardianship/conservatorship - Closing accounts voluntarily or involuntarily and managing asset disposition, final billing, and escheatment - Designing periodic account maintenance review processes and data quality programs - Evaluating operational risk in account servicing workflows ## 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. Multiple primary beneficiaries share the assets according to specified percentages (must total 100%). - **Contingent beneficiaries** receive assets only if all primary beneficiaries predecease the account holder or disclaim. - **Per stirpes** means that if a beneficiary predeceases the account holder, that beneficiary's share passes to their descendants in equal shares by representation. Per stirpes is the more common election for family designations. - **Per capita** means that if a beneficiary predeceases the account holder, that beneficiary's share is redistributed equally among the surviving beneficiaries. The predeceased beneficiary's descendants do not inherit. **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. If the deceased beneficiary's share is governed by per stirpes language, the share passes to their descendants; if per capita, the share redistributes to surviving beneficiaries. **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 acc
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.