If your bank holds FBO accounts for fintech programs, the omnibus balance on your core tells you almost nothing about who owns the money inside it. That detail lives in a subledger, often maintained by the fintech or a middleware provider, and the gap between your records and theirs is now one of the most examined control points in banking. After the Synapse collapse left end users unable to access funds for months, reconciliation stopped being a back-office topic and became a supervisory priority.
Key Takeaways:
- An FBO account is one omnibus custodial account at the bank with a third-party subledger tracking individual end-user balances; the structure breaks when the bank cannot independently verify that subledger
- Pass-through FDIC insurance depends on the recordkeeping requirements of 12 CFR § 330.5 and § 330.7, which means bad records put end users' insurance coverage at risk
- The FDIC's 2024 proposed custodial account rule would require direct, daily reconciliation and bank access to beneficial ownership records even when a third party maintains them
- Examiners already expect daily reconciliation, break aging and escalation, independent ledger access, periodic subledger validation, and wind-down data custody terms
What Is an FBO Account in a BaaS Program?
An FBO ("for benefit of") account is an omnibus custodial deposit account a fintech or program manager holds at a sponsor bank on behalf of its end users. The bank's core system shows one account with one balance. The record of which end user owns which portion of that balance, the subledger, is maintained outside the core, usually by the fintech itself or by a middleware provider operating the program's ledger infrastructure.
The structure exists for good reasons. It lets a fintech open accounts for thousands of users without the bank booking each one on its core, and it supports fast product iteration. Most deposit-taking BaaS programs run on some version of it, which is why the control questions around it apply to nearly every sponsor bank. If you are newer to the model, start with our explainer on what a sponsor bank is and how BaaS works.
Why FBO Structures Break: The Bank Doesn't Hold the Golden Record
The vulnerability is simple to state: the bank holds the money, but a third party holds the authoritative record of who owns it. If the subledger is wrong, or becomes unavailable, the bank has an omnibus balance it cannot allocate. End users cannot be paid what they are owed because nobody can prove what they are owed.
Small discrepancies are the early warning. Timing differences, failed transactions, fee postings, and returns create daily variances between the bank's omnibus balance and the sum of subledger balances. In a controlled program, those breaks are identified, aged, and cleared on a defined schedule. In an uncontrolled one, they accumulate silently until a partner dispute, an outage, or a failure forces a reconstruction that can take months.
The Synapse collapse in 2024 made this failure mode concrete and public. When the middleware firm that maintained ledgers for multiple fintech programs entered bankruptcy, end users at partner banks lost access to funds, and the parties spent months disputing whose records were correct and where shortfalls sat. The event is the reference case examiners now carry into every FBO conversation.
Pass-Through Deposit Insurance Requirements for Custodial Accounts
FDIC insurance can "pass through" an FBO account to each end user, insuring each beneficial owner up to the standard maximum rather than insuring the omnibus account once. But pass-through coverage is conditional. Under 12 CFR § 330.5, the account records must disclose the fiduciary or custodial relationship, and the details of each beneficial owner's interest must be ascertainable from records maintained by the bank or by the custodian in good faith and in the regular course of business. 12 CFR § 330.7 applies these recordkeeping requirements to accounts held by agents, nominees, and custodians.
The implication for BaaS programs is direct: the quality of the subledger determines whether end users actually have the insurance coverage the fintech's marketing implies. Records that cannot establish each owner's interest at the moment of a bank failure jeopardize pass-through treatment and delay any insurance determination. Reconciliation is not just an operations hygiene practice; it is the mechanism that keeps the insurance promise true.
The FDIC's Proposed Custodial Deposit Account Recordkeeping Rule
In September 2024, the FDIC proposed a recordkeeping rule for custodial deposit accounts with transactional features, a proposed new 12 CFR Part 375 aimed squarely at the FBO structures used in bank-fintech arrangements. The proposal responds to the exact failure the Synapse event exposed: an insured bank holding custodial deposits it cannot attribute to beneficial owners.
Under the proposal, covered banks would be required to:
- Maintain records identifying the beneficial owners of each custodial account, the balance attributable to each owner, and the ownership category, in a specified electronic file format
- Reconcile those records against the custodial account balance no less frequently than daily, as of close of business
- Maintain direct, unrestricted access to the records even when a third party maintains them, with defined requirements and contingency arrangements governing third-party recordkeeping
- Implement internal controls, validation, and annual certification around the recordkeeping
The rule is a proposal, and its final form may change. But supervisory expectations rarely wait for final rules. The proposal describes what the FDIC considers sound practice today, and examiners are already asking FBO questions in its vocabulary. Our review of FDIC guidance on bank-fintech partnerships traces how these expectations have hardened since 2023.
The FBO Reconciliation Control Set Examiners Expect Now
Whatever the rulemaking timeline, the control set below reflects what examination teams currently probe in deposit-taking BaaS programs:
| Control | What good looks like |
|---|---|
| Reconciliation frequency | Daily reconciliation of the bank's omnibus balance to the subledger total, per program, as of close of business, not monthly summaries |
| Break management | Every variance logged with amount, cause category, and age; escalation thresholds by dollar size and days outstanding; clearance evidenced |
| Independent ledger access | The bank can query end-user-level balances and transactions directly, without requesting extracts from the partner |
| Subledger validation | Periodic independent testing or audit of the subledger's accuracy and controls, not just reliance on the partner's SOC report |
| Wind-down data custody | Contract terms guaranteeing the bank receives complete ledger records, in usable format, during partner distress or offboarding |
The last row is the one programs most often miss. Data custody terms only matter when a partner is failing, which is exactly when cooperation is least likely. Negotiating ledger escrow or continuous data mirroring at signing is far easier than during a wind-down, a topic we cover in depth in our guide to fintech partner offboarding and wind-down.
Who Owns Reconciliation at the Bank, and What Each Cycle Should Produce
Ownership belongs inside the bank, in operations or finance, with compliance oversight, and explicitly not with the partner whose ledger is being verified. A reconciliation performed by the entity being reconciled is an attestation, not a control. Banks running multiple programs typically designate a deposit operations owner per program with a single portfolio-level owner reporting into the CFO or COO.
Each daily cycle should leave evidence: the reconciliation output with matched totals or identified breaks, the break log with aging, sign-off by the responsible owner, and escalation records for anything beyond threshold. Monthly, the portfolio view, programs reconciled, break trends, aged items, should reach management, and quarterly it should reach the board. When an examiner asks whether reconciliation operated all year, the answer should be a complete evidence trail, not a process description.
How Modern Sponsor Banks Keep Reconciliation Evidence Exam-Ready
The hard part of FBO oversight is not running one day's reconciliation; it is proving that the control operated every day, across every program, with breaks worked to closure, for the two years an examiner will sample. That proof falls apart when evidence lives in spreadsheets and inboxes owned by whoever ran that day's cycle.
Canarie lets a sponsor bank define its reconciliation standard once, frequency, break thresholds, escalation rules, evidence requirements, and continuously evaluates every fintech program against it. Each cycle's output lands in a per-partner evidence trail with a portfolio view on top, so the bank can show a regulator exactly which programs reconciled, when, and what happened to every break.
See how sponsor banks evidence daily reconciliation across every program →
Frequently Asked Questions
What is an FBO account in banking?
An FBO ("for benefit of") account is an omnibus custodial deposit account that a fintech or program manager holds at a bank on behalf of its end users. The bank sees a single account balance, while a subledger, typically maintained by the fintech or a middleware provider, tracks each end user's individual balance. The structure lets fintech programs scale without booking each user on the bank's core, but it makes reconciliation between the bank's records and the subledger a critical control.
How often should FBO accounts be reconciled?
Daily, as of close of business. The FDIC's 2024 proposed custodial account recordkeeping rule would formalize daily reconciliation for custodial deposit accounts with transactional features, and examiners already treat monthly reconciliation as inadequate for transactional BaaS programs. Daily frequency keeps breaks small and attributable; monthly cycles let variances compound into reconstructions.
Does FDIC insurance cover end users in an FBO account?
It can, through pass-through insurance, but coverage depends on recordkeeping. Under 12 CFR § 330.5 and § 330.7, the custodial relationship must be disclosed in the account records and each beneficial owner's interest must be ascertainable from records maintained in good faith and in the regular course of business. If the subledger cannot establish who owns what, pass-through treatment and timely insurance payouts are both at risk.
What happened with Synapse and FBO accounts?
Synapse was a middleware provider that maintained ledgers for fintech programs holding FBO accounts at several partner banks. When it entered bankruptcy in 2024, end users lost access to funds and the banks, fintechs, and trustee spent months disputing whose records were accurate and where shortfalls existed. The episode demonstrated that when the ledger keeper fails and the bank lacks independent records, end users bear the consequences, and it directly motivated the FDIC's custodial account recordkeeping proposal.