Configure and test a Treasury Prime FBO account with sub-ledger reconciliation ensuring physical balance equals sum of virtual customer balances

Steps

1. Open the FBO account through your bank partner via Treasury Prime's account creation API; confirm the FBO account is established on the bank's core and obtain the account number and routing number for the omnibus account
2. Create virtual customer accounts for each of your end-users via the Treasury Prime accounts API; each virtual account receives a unique identifier but routes to the shared FBO account's physical routing and account numbers — customer-facing account numbers are logical identifiers managed by Treasury Prime's ledger
3. Implement a daily reconciliation job: retrieve the FBO physical account balance from the bank (via BAI2 prior-day statement or Treasury Prime balance API); retrieve the sum of all active virtual customer account balances from the Treasury Prime ledger API; compare the two totals and alert if they differ by more than a configurable tolerance
4. Investigate reconciliation breaks by querying Treasury Prime transaction history for any transactions posted on the physical account that do not have a corresponding virtual account ledger entry — these represent funds that arrived at the physical FBO but were not attributed to a specific customer
5. Implement a suspense account process for unattributed credits: hold them in a designated suspense virtual account, investigate the payment source, and transfer to the correct customer virtual account once identified using the Treasury Prime account-to-account transfer API
6. Test the reconciliation process in Treasury Prime's sandbox environment by simulating various edge cases: multiple customers transacting simultaneously, fee postings, interest credits, and failed transfers that reverse — verify the FBO balance and virtual balance sum remain equal after each scenario