fee-billing
Build and manage advisory fee billing operations from fee schedule design through calculation, collection, revenue recognition, and compliance disclosure. Use when the user asks about tiered or breakpoint fee schedules, billing cycle configuration, AUM valuation for billing, direct-debit vs invoice collection, GAAP revenue recognition for fees, ADV Part 2A or Reg BI fee disclosure, diagnosing billing exceptions or refunds, migrating from spreadsheet billing to automated systems, or forecasting advisory revenue. Also trigger when users mention 'fee calculation', 'billing engine', 'effective fee rate', 'household billing aggregation', 'mid-period adjustment', 'billing in advance vs arrears', 'fee compression', or 'ERISA 408(b)(2)'.
What this skill does
# Fee Billing ## Purpose Provide comprehensive guidance on advisory fee billing operations, from fee schedule design and AUM valuation through calculation, collection, revenue recognition, and compliance disclosure. This skill supports the build-out of billing engines, the analysis of billing exceptions, and the day-to-day operations that convert advisory relationships into recognized revenue. ## Layer 10 — Advisory Practice (Front Office) ## Direction both ## When to Use - Designing or evaluating fee schedule structures (tiered, flat, breakpoint, hybrid) - Building or improving a fee calculation engine - Handling mid-period account events such as contributions, withdrawals, transfers, or terminations - Configuring billing cycles (advance vs. arrears, quarterly vs. monthly) - Setting up custodian direct-debit collection or invoice-based billing - Analyzing revenue recognition treatment under GAAP for fees billed in advance or arrears - Reviewing compliance requirements for fee disclosure (ADV Part 2A, Reg BI, ERISA 408(b)(2)) - Diagnosing billing exceptions, disputes, refunds, or retroactive adjustments - Migrating from manual or spreadsheet-based billing to an automated billing system - Forecasting advisory revenue or analyzing revenue concentration ## Core Concepts ### 1. Fee Schedule Structures Advisory firms employ a range of fee structures, often combining several within a single practice. **Flat Fee (Fixed Dollar).** A predetermined dollar amount charged per period regardless of account size. Common for financial planning engagements or retainer-based advice. Straightforward to bill but disconnected from asset growth. **AUM-Based (Percentage of Assets).** The most prevalent model for registered investment advisers. A single percentage (e.g., 1.00%) is applied to the market value of managed assets. Simple to communicate but can become expensive for large portfolios and cheap for small ones. **Tiered / Breakpoint (Declining Rate).** A graduated schedule where successive tiers of assets are billed at progressively lower rates. For example: | Tier | AUM Range | Annual Rate | |------|-----------|-------------| | 1 | First $500,000 | 1.00% | | 2 | Next $500,000 | 0.80% | | 3 | Next $1,000,000 | 0.60% | | 4 | Over $2,000,000 | 0.40% | Under a true tiered schedule each dollar is billed at the rate for the tier it falls within. Under a breakpoint schedule the entire balance is billed at the rate corresponding to the highest tier reached. The distinction matters significantly for large accounts and must be clearly defined in the advisory agreement. **Flat-Plus-AUM Hybrid.** Combines a fixed planning fee with a lower AUM percentage. Useful for firms that want to be compensated for planning work independently of portfolio size. **Hourly.** Charges based on advisor time. Rarely used as the sole billing method for ongoing relationships but common for project-based planning engagements. **Financial Planning Fees.** One-time or recurring fees for plan creation and updates, often billed separately from investment management fees. **Performance-Based Fees.** Permitted only for "qualified clients" under SEC Rule 205-3 (generally $1.1 million in AUM with the adviser or net worth exceeding $2.2 million). Requires a high-water mark or similar mechanism to prevent double-charging after drawdowns. Rarely used by typical RIAs due to complexity and regulatory constraints. **Family / Household Billing Aggregation.** Assets across related accounts (spouses, trusts, custodial accounts, IRAs) are combined for fee-tier determination, then the calculated fee is allocated back to individual accounts. This gives the household the benefit of breakpoint pricing. The aggregation definition (who qualifies as "household") must be documented in the advisory agreement. ### 2. AUM Valuation for Billing The accuracy and consistency of AUM valuation directly determines billing accuracy. **Valuation Date Selection.** The most common approaches are: - **Quarter-end value:** Assets valued as of the last business day of the billing quarter. Simple and widely used. - **Prior quarter-end value:** Assets valued as of the end of the preceding quarter. Avoids billing on unrealized gains or losses that occurred during the period just ended. Common for advance billing. - **Period average:** The average of daily or month-end values across the billing period. Smooths volatility but is operationally complex. **Market Value vs. Cost Basis.** Nearly all advisory agreements specify market value. Cost basis would understate the true value being managed and is almost never used. **Held-Away Assets.** Assets the adviser monitors but that are not custodied at the primary custodian (e.g., 401(k) plans, outside brokerage accounts, annuities). Whether these are included in the billable AUM depends on the advisory agreement. If included, obtaining timely and accurate valuations is a persistent operational challenge. **Accrued Income.** Bond accrued interest and declared but unpaid dividends may be included or excluded. Most custodian feeds include accrued interest in the total market value, so the default is typically inclusion unless the fee schedule specifies otherwise. **Margin Debit Treatment.** If a client uses margin, the question arises whether to bill on gross assets or net equity. The advisory agreement should specify. Most firms bill on net equity (gross market value minus margin balance). **Cash Inclusion / Exclusion.** Some agreements exclude cash or money market positions from billable AUM, particularly if the adviser is not actively managing those balances. This is uncommon but must be handled when present. **New Account Proration.** Accounts opened mid-period require proration. The standard method is to calculate the fee based on the number of days the account was open relative to the total days in the billing period. Some firms use a simpler approach and bill for the partial quarter only if the account was opened before the midpoint of the period. ### 3. Billing Cycle Mechanics **Quarterly Billing.** The dominant cycle for RIAs. Billing quarters typically align with calendar quarters (Jan-Mar, Apr-Jun, Jul-Sep, Oct-Dec), though some firms use fiscal quarters. **Monthly Billing.** Less common for investment management but used for financial planning retainers or firms that want to smooth revenue. Requires more operational overhead. **Annual Billing.** Occasionally used for flat-fee or financial-planning-only arrangements. May be billed as a single payment or split into installments. **Advance vs. Arrears Billing.** - **Advance (in advance):** Fees are billed at the start of the period for services to be rendered. Creates a deferred revenue liability on the firm's balance sheet. Requires refund calculation for accounts terminated mid-period. Most common for RIAs. - **Arrears (in arrears):** Fees are billed at the end of the period for services already rendered. Simpler from a revenue-recognition standpoint (revenue is earned when billed) but delays cash collection. Growing in popularity due to its alignment with the service delivery timeline. **Pro-Ration Rules.** Events requiring proration include: - Account openings mid-period - Account closings or terminations mid-period - Large contributions (some firms apply a materiality threshold, e.g., only prorate for contributions exceeding $10,000 or 10% of account value) - Large withdrawals (same materiality threshold logic) - Transfers between accounts within the same household (should be revenue-neutral) The standard proration formula is: ``` Prorated Fee = Full-Period Fee * (Days in Period Account Was Active / Total Days in Period) ``` **Billing Period Alignment.** When a firm converts billing cycles (e.g., from quarterly to monthly), a transition period is needed. Clients should not be double-billed or under-billed during the switch. A reconciliation calculation comparing what was billed under the old cycle
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.