FBO reconciliation that walks every difference to zero, each step with its records, before the 10 am attestation
Every end user's balance tied to the FBO account by 10 am, with the proof for examiners.
See one case, screen by screen ↓FBO reconciliation is a sponsor bank's daily proof that each FBO custodial account at the bank holds what the fintech partner's ledger says its end users own, down to each end user. FBO Reconciliation does it with seven agents that read the core, the payments hub, card settlement and each partner's ledger file, walk the difference to zero with each step cited, check every end user and recompute both totals independently, for two analysts to prepare and file the attestation.
AI use cases in banking: a buyer's guide to agentic AI for bank and credit union operations →
Updated
FBO reconciliation proves that a sponsor bank's FBO custodial account holds what the fintech partner's ledger says its end users own. Every night the core banking system posts the FBO account, the payments hub posts ACH batches, returns and wires, the card processor settles, and each partner sends its end-user ledger file — often around 5 am, sometimes late, sometimes in a changed format. An analyst downloads the core statement and the partner file into a spreadsheet and compares one total with another. Partner files can hold hundreds of thousands of rows, so many teams compare only totals.
The difference is then explained from memory — "probably returns after the cut-off", "card timing" — and items that should clear the next day are rarely checked to see that they did. Negative balances, two wallets for one owner, balances with no owner after a program change, missing names or tax IDs and wrong ownership codes hide inside a total that ties. Partner follow-up is by email, sign-off is a checkbox in a shared sheet, and an examiner asking for end-user balances on a past day starts a forensic rebuild from old files.
Estimated split for one business morning across six fintech partners, by hand and with the solution.
Seven agents read, pair, explain, check every end user and recompute; two analysts attest, and the Controller approves every money movement.
Thursday, October 22, 2026, at Tessaly Community Bank, a $3.4 billion community bank with six fintech partners. The attestation for Wednesday, October 21 is due at 10:00 am. The agents ran from 5:00 to 7:40 am; five of six partner files arrived. Here is what happens next, screen by screen, in the working solution.
Nadia opens Plover Pay for October 21. FBO account ••7781 holds $48,213,907.16 in the core; the 184,206 end-user balances in Plover Pay's ledger file add up to $48,212,441.09. Below the two totals, one waterfall walks the +$1,466.07 difference down to $0.00, and on the right the agents' run shows how they got there: the Matching agent paired 842,296 of 842,318 ledger entries.
“Every value and step carries a numbered citation.”
She clicks the citation on the first step. The ACH return file RTN-20261021-04 opens from the payments hub with the cited passage marked: posted to FBO account ••7781 at 4:10 pm Central, 14 entries, total credits $1,214.00. Plover Pay's ledger closed at 4:00 pm. Opening the source is recorded in the audit trail.
The highlighted passage is the exact text the citation points to.
The break page shows the Break agent's explanation at 0.98 confidence: fourteen payouts from October 19 and 20 came back — six with no account (R03), five closed (R02), three with an invalid account number (R04) — each with its trace number. The clock shows the ledger closed at 4:00 pm, the returns posted at 4:10 pm, and all 14 credited in the 6:00 am file. The other −$252.07 is 22 card purchases that settle at 11:00 am; if they do not, the Break agent turns them into an aged break at noon.
Break agent: “Never calls a difference explained without a record; below 0.90 it hands the item to a person.”
Unexplained is $0.00, within the $50.00 tolerance, and the Tie-out agent's independent recompute from the raw files agrees to the cent. Inside the total, three end users are negative, −$88.20 in all: an offline card purchase force-posted, an ACH deposit returned R01 after it was spent, and a card refund reversed. The FBO account still covers every positive balance, $48,212,529.29, with $1,377.87 to spare. Nadia asks the agents why the bank is higher, and gets the answer with its records.
“Section 7.3 asks Plover Pay to fund them within one business day.”
Not every day ties. Linnet Payroll's ledger shows $10,156.12 more than FBO account ••7792 holds. The Break agent explains $9,846.12 as payroll batch PB-7731 loaded twice in the partner's ledger, a partner error, and leaves −$310.00 above the $50.00 tolerance. A person decides what it is, in case CASE-LNT-0410, and the attestation shows it as an exception.
Ostra Remit's ledger file was due at 5:00 am; the transfer failed a certificate check at 4:48 am. The screen shows the core's FBO balance, $10,355,780.22, and the partner's provisional total, $10,355,140.22 — a total, not 35,957 balances. The Oversight watcher escalated case CASE-OST-0414 to Celeste Amari at 7:00 am and to Howard Lin, the Controller, at 9:00 am. Nadia can fetch the file again; an addendum follows when it arrives.
Back on Plover Pay, Nadia opens CASE-PLV-0412 with one button. The Oversight watcher drafted the notice to Tobias Reyes, Plover Pay's Head of Operations, citing section 7.3 of the program agreement: fund the three balances from reserve account ••4410 by the end of business on October 23. Nadia submits it; Celeste Amari, the Fintech Partner Oversight Manager, checks and sends it at 9:16 am. Tobias replies at 9:18 am that Plover Pay will fund all three from the reserve today.
“Sent by Celeste Amari at Oct 22 · 9:16 am · made by Nadia Ferreira.”
Celeste proposes the funding: Dr Plover Pay reserve ••4410 $88.20, Cr FBO Plover Pay customers ••7781 $88.20. Working as Howard Lin, the case shows the entry with Approve the funding and Return. The person who proposed it cannot approve it, and tomorrow's file is checked by the Ledger Integrity agent to confirm the three end users were credited.
The Attestation agent drafted the daily attestation at 7:40 am: all six partners, their FBO balances and end-user sums, and the statement, cited. Nadia gives each of the three exceptions a reason code — Ostra Remit's late file, Linnet Payroll's $310.00 and Harbor & Finch's $2,400.00 aged wire recall — and signs as preparer at 9:20 am. Owen Pritchard checks and files it at 9:21 am, 39 minutes before the deadline, with a fingerprint.
The preparer sees Check and file locked: nobody checks their own work.
Any day rebuilds a past business day from the attested snapshot, with no partner file and no forensic rebuild. Plover Pay on Tuesday, October 20: FBO balance $48,190,222.85, end-user sum $48,188,104.11, attested by Owen Pritchard and Nadia Ferreira, every record 30 of 30 fields. One button downloads the balances in the FDIC's proposed 30-field format; another builds an examiner pack.
The same partner's day, seen by the five people who carry it — what their morning looked like, and what it looks like now.
Seven agents read, pair, explain, check every end user and recompute; two analysts attest, and the Controller approves every money movement.
Reads the core's FBO balances, the payments hub's ACH and wire files, card settlement and each partner's ledger file, and checks arrival, control totals and format.
Pairs every ledger entry with the bank record behind it: ACH batches and returns, wires, card settlement, book transfers.
Explains each difference with the records behind it, says when a timing item should clear, and checks that it did.
Checks every end user: negative, duplicate and ownerless balances, the 30 record fields, ownership codes, and unusual patterns for the BSA Officer.
Recomputes both totals independently from the raw files: the end-user sum row by row, the FBO balance from the opening balance and every posting.
Drafts the daily attestation and the examiner pack, with every number cited.
Watches file deadlines and case SLAs, drafts partner notices, reminds and escalates.
Prepare and check · send notices · approve money. The agents propose; a named person decides.
Ask about any partner, day, break or end user, in plain words. Every answer cites its records.
Why is the bank $1,466.07 higher?
Two timing items. An ACH return batch of 14 payouts, $1,214.00, came back to the FBO account at 4:10 pm, ten minutes after Plover Pay's ledger closed; the ledger credited all 14 end users in its 6:00 am file. And $252.07 of card purchases left end users' balances at authorization but settle from the FBO account at 11:00 am. Nothing is left over.
Will the card timing clear today?
It should, at 11:00 am: the 22 purchases are in settlement file CPS-20261022-01. If they do not settle, the Break agent turns the $252.07 into an aged break at noon and tells you.
Who funds the negative balances?
Plover Pay does: section 7.3 asks it to fund any negative end-user balance from its reserve within one business day of the bank's notice. The three balances total $88.20. Even with them, the FBO account covers every positive balance with $1,377.87 to spare.
Which partners are not ready for the 10:00 attestation?
Two. Ostra Remit has not sent its October 21 ledger file; the transfer failed a certificate check at 4:48 am, and the case went to Howard Lin at 9:00 am. Linnet Payroll has $310.00 that no record explains, above its $50.00 tolerance. The other four are ready.
13 screens from the working solution, on its sample data. Pick one to see it large.
The tolerances, deadlines, escalations and privacy rules every partner's day is checked against are settings. One administrator proposes a change and the other approves it, on the audit trail.
| Setting | Default | Choose from |
|---|---|---|
| Unexplained tolerance | $50.00 ($100.00 for Harbor & Finch) | Set per partner |
| Ledger file due by | 5:00 am (5:30 am for Harbor & Finch) | Set per partner, with each partner's ledger cut-off |
| Negative balance funding | 1 business day after notice | Set per partner, from its program agreement |
| Partner ledger file late | Partner +1 hour · oversight manager +2 hours · Controller +4 hours | Deadlines and escalations |
| Timing item not cleared | Aged break at the expected clear time + 1 hour | Deadlines and escalations |
| Mask names and tax IDs on every screen (GLBA) | On · a reason is asked before showing names | On · Off |
| Keep end-user snapshots, workpapers and the trail | Five years (the BSA record rule) | On · Off |
| BSA referrals visible only to the BSA Officer | On | Cannot be turned off |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published figures (FDIC, “Recordkeeping for Custodial Accounts,” proposed rule, 89 FR, October 2, 2024, RIN 3064-AG07 — 600 to 1,100 banks affected, about 2,200 hours to set up and 1,100 hours a year per bank; the bankruptcy trustee's figures for the 2024 middleware failure, about $85 million short, as reported by Banking Dive). Tessaly Community Bank, its fintech partners, accounts and the people named on this page are fictional — characters and sample data in the working solution.
FBO reconciliation is a sponsor bank's daily proof that each FBO custodial account at the bank holds what the fintech partner's ledger says its end users own, down to each end user. FBO Reconciliation does it with seven agents that read the core, the payments hub, card settlement and each partner's ledger file, walk the difference to zero with each step cited, check every end user and recompute both totals independently, for two analysts to prepare and file the attestation.
An FBO ("for benefit of") account is one custodial deposit account at a sponsor bank that holds money for a fintech partner's end users. The bank holds one balance; each end user's share lives in the partner's ledger. If the two drift apart, nobody can say who owns what — which is why the account is reconciled to the ledger every business day.
The Matching agent pairs every ledger entry with the bank record behind it, and the Break agent names each remaining difference — an ACH return batch posted after the ledger cut-off, card settlement timing, a duplicate load — and cites the records. Each timing item gets an expected clear time and is checked; if it has not cleared, it becomes an aged break with an SLA. Below 0.90 confidence the Break agent hands the item to a person.
Every end user. The Ledger Integrity agent checks each balance for negative, duplicate and ownerless accounts, the 30 record fields of the FDIC's proposed format and the ownership codes, which affect how much of each balance is insured. It also checks that the FBO account covers every positive balance, which a matching total alone can hide.
In October 2024 the FDIC proposed recordkeeping for custodial deposit accounts with transactional features, including records of each beneficial owner and a reconciliation no less frequently than at the close of business daily; it is a proposal, not a final rule. FBO Reconciliation keeps a snapshot of every end user's balance for each attested day, rebuilds any day on request and exports it in the proposal's 30-field format.
The day does not stop. The Intake agent sees the missing file, the Oversight watcher reminds the partner and escalates to the oversight manager and then the Controller, and the screen shows the core's balance against the partner's provisional total. The partner is filed as an exception in the attestation, with an addendum when the file arrives.
Yes. The agents explain, check and draft; they never sign, file, send a notice or move money. One analyst prepares the attestation and a different one checks and files it, the oversight manager sends every partner notice, and only the Controller approves funding and adjusting entries. Overrides of an agent's classification need a reason code.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your program agreements, partner ledger file formats and a sample of past reconciliations — and it goes live once every quality gate has passed. We will walk you through it on your own FBO accounts first.
Every order decided in minutes, with protected benefits never frozen.
1-min demoDeceased Account ProcessingEstates settled in days, every account paid to the right person by its titling.
1-min demoDormant Account & Escheatment ManagementEvery dormant account dated from real owner contact, and every letter inside its window.
1-min demoWe'll run FBO Reconciliation on a sample of your own FBO accounts and partner ledger files.