Sub Accounts
Structural guidance for layering sub accounts safely without dumping allocation math publicly.
Individual (mock)
Individual · buckets & budgeting (mock)
Sub accounts (sample)
Operations fund
Contractor escrow (demo)
Travel buffer
Illustrative mock • not signed-in data • not a real screenshot
- Sub-account stacks are placeholders — sequencing matches product patterns only.
- Assign real buckets and allocations inside authenticated settings.
Overview
Sub accounts add structure when you budget for households, freelancers, or side projects—without juggling multiple legal logins. They still obey global Individual limits and risk controls; Community helps you compare patterns, not live allocation math.
Operational realities
- Transfers between sub accounts can still consume velocity limits depending on corridor rules.
- Automation (sweeps, rules) ships from authenticated configuration screens—not from chat workflows.
- Closing or merging compartments may be irreversible; confirm playbooks privately with Support when unsure.
Design thoughtfully
Starter framework
- Begin with fewer than four buckets—depth should match how often you reconcile.
- Map recurring pulls to the wallet that owns that obligation to avoid accidental overdraft sensations.
- If plastics map to sub accounts, skim the Cards topic for freezes and merchant categories.
- Export summaries for tax—not by uploading spreadsheets to Community threads.
Household narratives
Shared budgeting
Discuss allowance philosophies generically—skip posting exact allowances or dependents’ identifiable data.
Nest deeper?
Weigh UX overhead vs clarity; peers can debate trade-offs, not audit your spreadsheets.