What is an FBO account?
An FBO account, short for For Benefit Of account, is a bank account held by one party on behalf of another, where the account holder manages the funds but does not own them. The beneficiaries retain legal ownership of the money. The account holder acts as a custodian, managing deposits, disbursements, and record-keeping according to the terms of the arrangement.
FBO accounts are used across banking, fintech, trust management, payroll, and escrow. In a payments context they are most commonly associated with platforms and neobanks that hold customer funds in a pooled structure at a partner bank.
How FBO accounts work
In a typical fintech FBO structure, a platform opens a single bank account in its own name, titled to reflect the FBO relationship, such as "Platform Inc. FBO its customers." All customer funds are deposited into this one pooled account at the bank.
The bank sees one account with one aggregate balance. The platform is responsible for maintaining a detailed internal ledger that tracks exactly how much of that pooled balance belongs to each individual customer. Every deposit, withdrawal, and transfer needs to be recorded at the sub-account level so that the total of all individual balances always equals the aggregate bank balance.
The customers themselves do not have a direct relationship with the bank. Their interaction is with the platform, which allocates and disburses funds on their behalf according to their individual activity. Virtual accounts are commonly used to give each customer a unique account number and routing number while the underlying funds remain in the single FBO pool.
FBO accounts and money transmission licensing
One of the primary reasons platforms use FBO structures is to manage their exposure to money transmission licensing requirements. A business that holds customer funds in its own name and transmits them to third parties is typically classified as a money transmitter, which triggers state-by-state licensing obligations across 49 US states.
Under an FBO structure, the bank holds the funds. The bank is the licensed entity. The platform operates under the bank's regulatory umbrella rather than obtaining its own money transmitter licenses. This is sometimes called the authorized delegate model: the platform acts as an agent of the bank for the purpose of the banking activity.
This is not a blanket exemption from all regulation. The platform still has compliance obligations, including KYC, transaction monitoring, and AML program requirements. The bank will require the platform to demonstrate that its compliance controls meet the bank's standards before opening an FBO account. The arrangement shifts which entity holds the license, not whether compliance obligations exist.
FDIC insurance in FBO structures
FDIC insurance in an FBO structure works differently from a standard deposit account. In a direct account, the depositor is insured up to $250,000 (USD) per insured bank per depositor category. In an FBO structure, the standard coverage is at the account level, meaning the entire pooled account is covered up to $250,000 unless pass-through insurance applies.
Pass-through FDIC insurance, also called deposit pass-through insurance, extends coverage to each individual beneficial owner rather than treating the pooled account as a single depositor. For pass-through insurance to apply, the account must be properly titled to reflect the FBO relationship, and the platform must maintain accurate records identifying each beneficial owner and their individual balance. If these conditions are met, each customer can be eligible for up to $250,000 in FDIC coverage on their portion of the pooled balance.
Maintaining the records required for pass-through insurance is part of the payment ledger and bank reconciliation obligations that come with running an FBO structure.
FBO accounts vs. direct deposit accounts
A direct deposit account, or demand deposit account (DDA), gives the account holder a direct relationship with the bank. They are the named depositor. They have direct access to their funds, direct FDIC insurance coverage, and a direct contractual relationship with the institution.
An FBO account puts an intermediary between the customer and the bank. The customer's relationship is with the platform, not the bank. This has practical implications:
- The customer cannot directly instruct the bank to move their funds. All instructions go through the platform
- FDIC insurance coverage depends on how the FBO is structured and whether pass-through conditions are met
- If the platform fails, access to funds depends on whether the bank can identify individual customer balances from the platform's records
The FBO model is operationally efficient for platforms managing large numbers of customers. The tradeoff is that the platform takes on significant record-keeping responsibility and the customers have less direct protection than they would in a DDA structure.
The platform's ledger obligation
Running an FBO structure correctly depends entirely on the accuracy of the platform's internal ledger. The bank tracks one account. The platform tracks thousands or millions of sub-balances. If those two records do not reconcile, customers may not be able to access their funds, pass-through FDIC insurance may be jeopardized, and the platform may face regulatory action.
This makes payment reconciliation a critical operational function for any platform running an FBO. Every transaction that hits the pooled bank account needs to be matched to an individual customer record. Discrepancies need to be investigated and resolved. The ledger needs to be reconciled against the bank statement regularly, typically daily for high-volume platforms.
The flow of funds design for an FBO structure should clearly map how money enters the pool, how it is allocated to individual sub-accounts, and how it exits through disbursements, so that every leg of the movement is traceable and reconcilable.
