account-opening-workflow
Design and operate back-office account opening processes from application intake through activation. Use when building account opening automation or improving STP rates, reducing NIGO rejection rates from custodians or clearing firms, defining document requirements for trusts entities IRAs or estate accounts, implementing approval workflows and regulatory holds for complex account types, setting up multi-custodian account opening across Schwab Fidelity or Pershing, designing account numbering titling or classification schemes, troubleshooting account opening failures or processing delays, integrating with custodian or clearing firm submission systems, or benchmarking account opening cycle times and operational efficiency.
What this skill does
# Account Opening Workflow ## Purpose Guide the design and operation of account opening workflows in brokerage and advisory back offices. Covers account type determination, required documentation assembly, approval workflows, NIGO (Not In Good Order) management, regulatory holds, account numbering and registration, and process automation. Focuses on the operational and systems perspective of account opening — the back-office processing that complements the front-office onboarding covered in the client-onboarding skill. ## Layer 12 — Client Operations (Account Lifecycle & Servicing) ## Direction prospective ## When to Use - Designing or improving back-office account opening processes - Building account opening automation and straight-through processing - Reducing NIGO rejection rates from custodians or clearing firms - Implementing regulatory hold and approval workflows for complex account types - Defining document requirements by account type - Integrating account opening with custodian or clearing firm systems - Managing account registration and titling rules - Designing account numbering schemes and classification systems - Troubleshooting account opening failures and processing delays - Building multi-custodian account opening operations - Implementing exception-based processing for high-volume operations - Establishing post-opening activation and verification procedures - Measuring and benchmarking account opening STP rates and operational efficiency ## Core Concepts ### Account Type Determination and Registration Account type determination is the foundational decision in the account opening workflow. The registration type dictates the document requirements, approval gates, tax treatment, titling rules, and custodian submission path. Operations teams must maintain a comprehensive account type matrix that maps each registration type to its downstream processing requirements. **Individual and joint registration types:** - **Individual** — single natural person as owner; titled in the individual's legal name; SSN as TIN; simplest registration and the baseline for all account opening processes - **Joint Tenants with Right of Survivorship (JTWROS)** — two or more co-owners with equal, undivided interest; on death of one owner, the surviving owner(s) automatically inherit the deceased owner's share without probate; all owners must sign account opening documents; titled as "John Smith and Jane Smith JTWROS" - **Tenants in Common (TIC)** — two or more co-owners with specified ownership percentages (need not be equal); on death, the deceased owner's share passes to their estate, not to the surviving co-owner(s); ownership percentages must be recorded and may affect tax reporting; titled as "John Smith and Jane Smith TIC" - **Community Property** — available only in community property states (Arizona, California, Idaho, Louisiana, Nevada, New Mexico, Texas, Washington, Wisconsin); assets acquired during marriage are jointly owned; specific titling and tax implications vary by state; some custodians treat community property accounts differently from other joint account types - **Community Property with Right of Survivorship** — a hybrid available in some community property states that combines community property tax treatment with automatic survivorship; not all custodians support this registration type **Trust registration types:** - **Revocable (living) trust** — grantor retains control and can modify or revoke the trust; typically titled as "John Smith, Trustee of the Smith Family Trust dated 01/15/2020"; grantor's SSN is often used as TIN; account opening requires trust certification or relevant pages of the trust agreement showing trust name, date, trustees, and investment powers - **Irrevocable trust** — grantor has permanently relinquished control; separate tax entity requiring its own EIN; beneficial ownership certification required under FinCEN CDD Rule; titled in the trust's legal name with trustee designation; requires more extensive documentation including the full trust agreement or comprehensive trust certification - **Testamentary trust** — created by a will and comes into existence upon the grantor's death; requires letters testamentary, death certificate, and court-certified copy of the will provisions creating the trust; account opening is typically manual due to the complexity and variation in court documentation **Entity registration types:** - **LLC (Limited Liability Company)** — requires articles of organization, operating agreement (or certificate of formation in some states), EIN, beneficial ownership certification; titled in the LLC's legal name; operating agreement must authorize the opening of investment accounts and identify authorized signers - **Corporation (C-Corp and S-Corp)** — requires articles of incorporation, bylaws, corporate resolution authorizing the account and designating authorized signers, EIN, beneficial ownership certification; S-Corp election (IRS Form 2553) may be relevant for tax reporting but does not change account opening requirements - **Partnership (General Partnership, Limited Partnership, LLP)** — requires partnership agreement, EIN, identification of general partner(s) who have authority to act on behalf of the partnership; limited partners typically do not have signing authority unless specified in the partnership agreement - **Sole Proprietorship** — may use the individual's SSN or a separate EIN; requires DBA documentation if operating under a trade name; some custodians treat sole proprietorship accounts as individual accounts with a DBA designation **Retirement account types:** - **Traditional IRA** — tax-deductible contributions (subject to income limits if the owner participates in an employer plan), tax-deferred growth, required minimum distributions beginning at age 73 (SECURE 2.0 Act); requires IRA adoption agreement, beneficiary designation, and IRA disclosure statement - **Roth IRA** — after-tax contributions, tax-free qualified distributions, no RMDs during the owner's lifetime; same documentation requirements as Traditional IRA plus verification of Roth eligibility (income limits) - **SEP IRA** — employer-funded; contributions up to 25% of compensation or the annual dollar limit; requires SEP plan document (IRS Form 5305-SEP or prototype plan) and IRA adoption agreement; employer must execute the plan document before the account can be opened - **SIMPLE IRA** — salary deferral plus employer match or non-elective contribution; requires SIMPLE plan document (IRS Form 5304-SIMPLE or 5305-SIMPLE) and SIMPLE IRA adoption agreement; must be established between January 1 and October 1 of the plan year - **Inherited IRA** — beneficiary account established upon the death of the original IRA owner; subject to the 10-year distribution rule for most non-spouse beneficiaries under the SECURE Act; requires death certificate, beneficiary verification, and custodian-specific inherited IRA application; titled as "Jane Smith, Beneficiary of John Smith, Deceased" - **Rollover IRA** — receives funds from an employer-sponsored plan (401(k), 403(b), 457); may be direct rollover (trustee-to-trustee) or indirect rollover (60-day); requires rollover paperwork and often a letter of acceptance from the receiving custodian **Custodial and estate accounts:** - **UTMA/UGMA** — custodian (typically a parent or grandparent) manages assets for a minor until the age of majority (18 or 21 depending on state and UTMA vs UGMA); the minor is the beneficial owner and the account is titled in the minor's SSN; titled as "John Smith, Custodian for Jane Smith under the [State] UTMA" - **Estate** — opened to manage assets of a deceased person during probate; requires letters testamentary (if there is a will) or letters of administration (if intestate), death certificate, and EIN for the estate; titled as "Estate of John Smith, Deceased"; personal representative or executor is the authorized signer **Account numberi
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.