FBO Accounts: What They Are & How They Work (July 2026)
An FBO account, short for "for benefit of," is commonly used to refer to a custodial or fiduciary deposit account at an FDIC-insured bank that is maintained by one party for the benefit of one or more beneficial owners. In a common pooled-account model, a single bank account may support records for many individual balances or beneficial interests. The account structure, titling, recordkeeping, and information available to the bank vary by program. This article describes one common FBO account model, how customer balances are tracked, when FDIC pass-through insurance may apply, and what it can take to operate the program. FBO structures vary by bank, program, product design, agreements, applicable law, and regulatory treatment.
TLDR:
- In one common FBO structure, pooled funds are held in a custodial account at a bank, while customer balances are tracked through a sub-ledger
- Beneficial owners may be eligible for FDIC pass-through deposit insurance, subject to applicable FDIC requirements, coverage limits, ownership categories, and aggregation rules
- If pass-through requirements are not satisfied, coverage may be determined based on the named account holder rather than each beneficial owner, which could leave some funds uninsured
- Depending on the program, building on an FBO structure may require compliance, ledgering, reconciliation, and operational controls
- Unit provides financial infrastructure that can support programs using FBO structures, including ledgering, reconciliation, and operational workflows through partner bank programs.
What Is an FBO Account
FBO stands for “for benefit of.” In one common arrangement, a custodial account is established at a bank in the name of a platform or provider for the benefit of one or more customers or beneficiaries. The bank may see one account holder on paper, but that account can hold funds for multiple individual people or businesses, each with a claim to a specific slice of the balance.
An FBO relationship may be reflected in an account title such as “Fintech Inc. FBO Its Customers” or “Jane Smith FBO John Smith,” although naming conventions vary. In a common pooled structure, an account is opened at a bank while a fintech or other provider maintains records and workflows for customer balances, transactions, and identity information, making embedded finance possible at scale.
For example, a bill-payment program may use a pooled custodial account at a bank to facilitate payments from businesses to vendors. A payroll program may use a similar structure to facilitate wage or benefit payments. Depending on the program, end users may not have separate accounts on the bank’s core system. The provider maintains the related records and workflows, while the funds remain at the bank.
This common structure functions as one-to-many: one pooled account at the bank, serving many customers underneath it. The end customer often does not open their own account at the bank. Funds move through the pooled account, while the provider’s records track the balance associated with each customer. The precise account structure, roles, and responsibilities can vary based on the bank, program agreements, product design, applicable law, and regulatory treatment.
How FBO Accounts Work
In one common model, pooled funds are held in a custodial account at the sponsor bank under one aggregate balance and account number. The bank may see aggregate settlement activity and, depending on the program, may also receive customer, transaction, balance, and reconciliation data.
The fintech or another provider may maintain a sub-ledger tracking each user’s balance, transaction history, and identity. Depending on the program, those records may not correspond to separate accounts on the bank’s core system. Incoming and outgoing transactions are reflected in both the bank account and the customer records. Regular reconciliation helps identify and resolve any differences between them. Understanding banking infrastructure helps clarify how these layers interact.
Modern financial infrastructure makes this sub-ledger far easier to manage than it used to be. Instead of building a ledger from scratch, you can create a balance for each customer, often called a wallet account, and use that record to support payments and card activity. The funds remain in the custodial account at the bank, while the platform manages the customer-facing workflows. Depending on the platform and program design, a company may initiate transactions and manage customer-facing workflows without interacting directly with the pooled bank account.
How Ownership Works in an FBO Account
The party named on an FBO account may be different from the customers or beneficiaries associated with the funds. In many structures, the funds are held in a custodial account at the bank, while the fintech or other provider maintains the ledger that tracks each customer’s balance or beneficial interest. Depending on the structure, the end customer may be the beneficial owner of the funds reflected in the related records. In some cases, such as when a fintech holds a money transmitter license, it may also have custody responsibilities.
FDIC pass-through treatment depends in part on the actual ownership relationship and supporting records. An FBO label alone does not establish coverage.
When FDIC Pass-Through Insurance May Apply
Beneficial owners may be eligible for FDIC pass-through deposit insurance when applicable requirements are met. Coverage is not automatic and depends on factors including ownership, account records, identifiable customer balances, coverage limits, ownership categories, and aggregation rules. If the requirements are not met, the deposits may receive different insurance treatment than expected, including treatment based on named account holder rather than each beneficial owner. Accurate records are therefore essential.
Common FBO Account Use Cases
FBO and other custodial structures may be used when funds are held at a bank for the benefit of customers, businesses, or other beneficiaries.
Personal finance common examples:
- Custodial accounts for minors, titled FBO the child until they reach a set age
- Special needs trusts, where a trustee manages funds without disqualifying the beneficiary from public benefits
- 529 plans, where the plan holds funds FBO the student
- Estate administration, where an executor manages assets FBO heirs during probate
Business and embedded finance common examples:
- Neobanks pooling end user deposits at a sponsor bank
- Marketplaces holding seller payouts before disbursement
- Payroll providers holding wages or benefits FBO employees, requiring reliable money movement capabilities
- Escrow services holding funds FBO the intended recipient
In a pooled model, one account title may support many customer balances, each tracked through a sub-ledger or similar records.
What Building on an FBO Account May Require
Building an FBO account program in-house may require building or operating significant technical, operational, and compliance infrastructure between the bank's master account and each end user's balance. The information available to the bank about individual end users varies by program, and the bank may rely in part on records maintained by the fintech or another provider. Depending on the program, those capabilities may include:
- A ledger for tracking customer balances and transactions
- Reconciliation with bank and payment records
- KYC and KYB processes
- AML, sanctions, fraud, and transaction monitoring
- Dispute, return, and customer-support workflows
- Statements, transaction histories, and tax documents
- Policies and procedures required by the partner bank
Depending on the program, banks may rely in part on records maintained by a fintech or service provider. Reconciliation errors can create differences between the provider’s records and the bank’s records, making clear data access, reconciliation, escalation, and responsibility allocation important.
Regulatory Considerations and the FDIC’s Proposed Custodial Account Rule
The 2024 Synapse bankruptcy highlighted the importance of accurate beneficial-owner records, regular reconciliation, bank access to relevant data, and clear responsibility allocation among program participants. Building on enterprise-grade financial infrastructure can help companies support stronger controls for these systemic risks. Against this broader regulatory backdrop, the FDIC proposed new recordkeeping requirements for certain custodial deposit accounts.
On September 17, 2024, the FDIC proposed a rule covering recordkeeping for certain custodial deposit accounts. If finalized as proposed, it would add beneficial-owner recordkeeping, reconciliation, reporting, and certification requirements for covered banks.
Key Criteria When Choosing an FBO Infrastructure Provider
Choosing infrastructure for FBO accounts means weighing many of the same risks a bank examiner would flag first.
- Reconciliation: understand how often program records are compared with bank and payment records, how discrepancies are resolved, and who is responsible for the process.
- Bank partner relationships: check whether the connection to the bank is direct or routed through an intermediary. A single bank dependency creates continuity risk if that lack a continuity plan may face customer-access reconciliation, and operational disruption if a critical provider or bank relationship fails.
- Compliance ownership: identify who handles KYC, KYB, AML monitoring, fraud, disputes, statements, reconciliation, reporting, and issue escalation.
How Unit Supports Programs Using FBO Structures
Unit is a financial infrastructure platform that enables technology companies to store, move, spend, and lend money inside their product. For programs that use an FBO structure, Unit can support the ledgering, reconciliation, and operational workflows used to manage customer balances associated with funds held in custodial accounts at partner banks. The Unit platform provides bare-metal APIs, a single native ledger, and operational tools that can support onboarding, payments, reconciliation, returns, settlement, statements, compliance, security, and risk workflows, subject to program configuration and partner bank requirements.¹ Available capabilities and responsibilities depend on the program and its agreements.
Final Thoughts on FBO Account Structure and Compliance
Building on an FBO account means you own the sub-ledger, the reconciliation, and the compliance stack that sits between the bank and your end users. The Synapse fallout made it clear that weak recordkeeping doesn't stay a back-office problem for long. Reach out to our team if you want to see what well-built FBO infrastructure actually looks like under the hood.
The content in this article is provided for general informational and educational purposes only and should not be construed as legal, tax, accounting, or regulatory advice. Unit does not warrant or guarantee the accuracy, completeness, adequacy, or currency of the information provided, and the content may not reflect all considerations relevant to a particular business, product, or use case.
Unit is a financial technology company and not a bank. Banking services are provided by Unit’s bank partner(s), Members FDIC. Unit provides technology infrastructure and platform services to support financial products offered through partner bank programs, subject to applicable program terms, eligibility, approval, and responsibility allocations.
FDIC pass-through insurance is subject to applicable FDIC rules and requirements. Coverage is not provided by Unit and is not guaranteed in all circumstances.
1. Unit supports compliance, risk, and operational workflows, subject to applicable program responsibilities and partner requirements. Responsibility for compliance, risk management, fraud prevention, operational control is allocated among Unit, Unit's bank partner(s) and clients in accordance with applicable program agreements.
FAQ
How is ownership of funds in an FBO account determined?
Ownership depends on the account structure, agreements, records, applicable law, and relevant facts. In some arrangements, customers have beneficial interests in funds held in an account under the name of a custodian, agent, or other provider. Duties relating to those funds, and their treatment in bankruptcy, depend on the specific arrangement.
What affects FDIC pass-through insurance for an FBO account?
FDIC pass-through coverage applies when three conditions are met: funds must belong to the principal, records must document the agency relationship, and each beneficial owner's share must be identifiable in the sub-ledger. Coverage is also subject to applicable limits, ownership categories, and aggregation rules.
Can I build an FBO account program without owning the full compliance and ledger stack myself?
Unit provides technology infrastructure and platform services that can support partner bank programs, including ledgering, onboarding, payments, reporting, reconciliation, disputes, statements, tax documents, and compliance-related workflows.1 Available capabilities and responsibilities depend on the product, partner bank, and program agreements.
What should FBO infrastructure buyers learn from the Synapse bankruptcy?
The 2024 Synapse bankruptcy highlighted the importance of accurate records, regular reconciliation, bank access to beneficial-owner data, continuity planning, and clear responsibility allocation. Buyers should understand how balances are recorded, how discrepancies are resolved, who can access the data, and how records can be transferred if a provider relationship ends.
