Virtual Accounts: Sub-Ledgering Without Opening Real Bank Accounts
By Formance Staff
Product
Ledger
Connectivity
Loading article content
Loading table of contents
Loading author
_FORMANCE LEDGER/
Post your first virtual account credit
Clone Formance Ledger on GitHub, run it locally, and post the virtual account credit from this article against your own omnibus and customer account paths.
Engineering teams at regulated entities often build a sub-ledger system for virtual accounts when they run a for-benefit-of (FBO) or omnibus account at a partner bank.
The bank offers one account, but the e-money wallet needs 40,000 customer balances. The bank has offered virtual account numbers or virtual International Bank Account Numbers (vIBANs). Your engineering lead must decide whether the bank's virtual account report can serve as the sub-ledger or whether your core ledger must own every per-customer balance.
Sub-ledgering virtual accounts without opening a real bank account relies on three things: one account tree, one reconciliation invariant, and one posting rule.
What is a virtual account?
A virtual account is a routing identifier: it tags an inbound credit so you can attribute it to one customer, while the balance that credit implies lives in a sub-ledger account inside your core ledger. The bank account holds funds, while the virtual identifier holds a reference.
The same pattern applies on payment rails without IBANs. Using a virtual account number or reference code, map the quoted identifier to a customer and attribute the resulting credit to the underlying payment account.
The European Banking Authority's 2024 report states a vIBAN is "an identifier causing payments to be redirected to a payment account identified by an IBAN different from that identifier." The identifier routes the payment, while the linked payment account holds the funds.
For an FBO or omnibus account, this routing-plus-sub-ledger pattern maps directly onto the account structure. The company holds the omnibus account, and customers are beneficiaries tracked in a per-customer sub-ledger.
Formance Ledger is an open-source, programmable core ledger that unifies fiat and digital assets with a regulatory-grade audit trail. It is built for engineering teams to model and track money movements across FBO and omnibus accounts in real time.
The three benefits of virtual accounts
Virtual accounts solve three recurring problems for engineering and finance teams running an omnibus or FBO account: automated reconciliation, reduced need for separate bank accounts, and centralized liquidity management.
1. Automated reconciliation
Automated reconciliation runs the invariant check against the omnibus account at a defined cadence, compares the sub-ledger postings against the bank's tagged entries, and surfaces drift in hours rather than at month-end.
Three regulatory bodies now treat that cadence as a baseline:
•The UK’s Financial Conduct Authority (FCA) updated PS25/12, which states that safeguarding institutions must perform an internal safeguarding reconciliation "no less than once each reconciliation day".
•The final compromise text of PSD3 directs the European Banking Authority (EBA) to draft regulatory technical standards on safeguarding, "including requirements on segregation, designation, reconciliation and calculation of safeguarded funds".
•The Federal Deposit Insurance Corporation (FDIC) is proposing requirements that, once finalized, IDIs holding custodial deposit accounts with transactional features would have to reconcile against beneficial-ownership records "no less frequently than at the close of business daily".
The virtual-account architecture remains the same in every case: reconciliation runs against the ledger’s immutable postings, so the invariant holds at the regulator’s cadence.
2. Reduced need for separate bank accounts
Where your bank supports this setup, one omnibus or FBO account can carry 40,000 customer balances through virtual identifiers rather than 40,000 real accounts at the partner bank.
Adding a customer means assigning an identifier against the omnibus account rather than opening a separate bank account.
The addition may reduce per-customer onboarding at the partner bank. Clarify your own onboarding obligations and the bank's account-opening process before treating either as resolved.
3. Centralized liquidity management
Centralized liquidity management means treasury manages one cash position at the partner bank while the ledger carries per-customer attribution for every unit inside it.
In one omnibus account, every balance stays attributed to a customer inside the core ledger. Treasury sees one cash position for forecasting, sweeping, and intraday funding decisions, and operations sees 40,000 customer balances from the same postings for support, reporting, and reconciliation.
Formance built Assets Coloring for exactly centralized liquidity management. It tags units of the omnibus account balance with distinct provenance (customer funds vs. operating float being the canonical case), so the distinction survives collection without a second account tree.
How virtual account sub-ledgering works
Virtual-account sub-ledgering runs on specific mechanics: tracking individual customer balances and an account tree with a reconciliation invariant.
The mechanics give you a per-customer record the bank can't overwrite and a daily check that proves the collected funds still tie out to every entitlement inside it.
Tracking individual customer balances
An FBO account sub-ledger gives you a per-customer record that exists independently of the bank's report.
Every balance recomputes from immutable postings. When a customer's available figure disagrees with the bank's tagged total, you walk back that customer's postings since the last clean cut-off and find the posting that diverged.
The bank's report becomes a reference you reconcile against, not the source of truth you depend on when it drifts.
The account tree and the reconciliation invariant
Virtual IBAN sub-ledgering uses an account tree: one omnibus boundary per bank account, one sub-ledger account per virtual identifier, and one suspense account for credits you can't attribute yet.
Every inbound credit posts from the boundary to a sub-ledger account or to suspense. The boundary is your ledger's sign-aware picture of the bank account. The sub-ledgers partition the cash it introduced.
The invariant that holds at each reconciliation day is:
sum(customer sub-ledger balances) + suspense = -omnibus boundary balance = bank statement balance at the same cut-off
Suspense sits inside the equation on purpose. An unattributed credit is still customer money in the omnibus account, and leaving it out is how a statement "reconciles" while a customer waits for funds.
Five steps to build virtual accounts without opening real bank accounts
Engineering and finance teams can build virtual accounts without opening real accounts in five steps.
These include setting up the master account, creating the virtual accounts and identifiers, building the ledger to track individual balances, keeping records accurate through reconciliation and audit trails, and automating payment attribution and reporting.
Step 1: Set up a master account
The master account is the single omnibus or FBO account at the partner bank that holds pooled customer funds. Every virtual identifier in Steps 2 through 5 routes credits into it, and every reconciliation check in Step 4 ties back to it.
That master account holds the customer funds, and your ledger represents its boundary at @platform:banks:partnerA:omnibus. The partner bank holds the cash, while the ledger records who it belongs to.
Your company is the account holder on the master account, and the customers are the beneficiaries. The bank records the holder relationship and relies on you to record the beneficiary relationships.
Everything the bank does to the master account (credits, debits, fees, and returns) has to appear as a posting touching the boundary. Otherwise, the invariant will fail for reasons unrelated to customers.
While Formance provides the ledger that records every balance and posting against the master account, it does not hold or move funds itself.
All money movement runs through the connected bank or PSP, and the ledger is the system of record that tracks beneficial ownership against the cash the bank holds as custodian.
Step 2: Create virtual accounts and unique identifiers
The partner bank issues vIBANs or reference codes that tag inbound credits routed to the omnibus account. The identifier carries no balance.
Store the identifier-to-customer mapping in your ledger as metadata on the customer's sub-ledger account, with the date the bank issued it. Then confirm with the bank which field in its payment notification carries the vIBAN.
In our experience, banks differ on whether the identifier arrives as the creditor account, a related-parties field, or a payment reference.
We once watched a team spend a week chasing "missing" credits that were landing in suspense. The partner bank had moved the vIBAN from CdtrAcct to a structured remittance field after a camt.054 schema update. The ingestion key still pointed at the old location, so every credit came through unattributed.
Log the raw payload from every bank notification. If the bank changes its format, you'll spot the change on the next notification instead of chasing a reconciliation failure.
Step 3: Build a ledger to track individual balances and transactions
The ledger owns every per-customer balance, so the account tree needs three named positions: one for the omnibus boundary, one per customer, and one for credits you haven't attributed yet.
The structure is core-ledger scope (the real-time, per-transaction source of truth). It feeds your general ledger (the periodic, aggregated book your finance team closes in) rather than replacing it with another type of ledger.
The three accounts you need are:
•@platform:banks:partnerA:omnibus, which represents the omnibus account boundary.
•@customers:<id>:available, which holds each customer's balance.
•@platform:suspense:unattributed, which holds credits whose reference you can't resolve yet.
Postings between these accounts are written in Numscript, Formance's purpose-built language for describing financial transactions.
Numscript states the posting as intent, including which asset, which amount, which source, and which destination. The posting commits atomically, which lets the no-negative-balance rule in Step 5 live in the ledger itself rather than in application code wrapped around it.
Here is a EUR 1,250,000.00 credit attributed to customer 48213, with the bank's notification identifier attached as metadata so the posting traces back to the camt.054 entry that produced it:
// VIRTUAL_ACCOUNT_CREDIT// Event: attribute an inbound bank credit to customer 48213send [EUR/2 125000000] ( source = @platform:banks:partnerA:omnibus allowing unbounded overdraft destination = @customers:48213:available)set_tx_meta("event_type", "virtual_account_credit")set_tx_meta("bank_notification_ref", "camt054-ntry-2026-09-28-00417")set_tx_meta("viban_ref", "partner_a-viban-48213")
The boundary is the counter-account for cash the bank holds on your behalf. Inbound credits make that boundary's running balance negative.
During the daily check, it compares its negated balance with the positive bank statement balance.
If your funding sources need to stay distinguishable inside the same boundary, Assets Coloring adds a provenance tag per unit without a second account tree. It can distinguish safeguarded receipts from operating float.
Step 4: Keep ledger records accurate through reconciliation and audit trails
As noted earlier in the article, virtual account reconciliation is one check run at least once per reconciliation day. It's the invariant that proves the funds still tie to every customer entitlement inside it, and it's the piece supervisors look at first when they ask whether safeguarded funds are intact:
sum(customer sub-ledger balances) + suspense = -omnibus boundary balance = bank statement balance at the same cut-off
Without a shared point in time, you can't compare the three figures. Record both the effective time (when the bank says the credit happened) and the system time (when your ledger wrote it), then run the check against a defined effective-time cut-off.
In practice, bi-temporality lets you reproduce yesterday's 17:00 balance after a late-arriving notification lands at 09:00.
When the check fails, compare each account's postings since the last clean cut-off against the bank's tagged entries. The account with an unmatched posting is your discrepancy, and the posting's metadata names the notification.
For each reconciliation, keep queryable records of the safeguarding check: what you ran, what you found, and what the outcome was against the safeguarding requirement.
Formance Reconciliation automates matching your ledger postings to the bank's statements at configurable intervals, raising drift alerts when balances diverge. Pair the scheduled run with your own event-driven check on each notification so the end-of-day pass confirms the result.
Step 5: Automate inbound and outbound posting rules
Inbound rules start with normalization, which includes credit and debit notifications from every bank, PSP, and custodian that need to land in a single data model.
Your attribution logic doesn't branch on which rail sent the notification.
On a camt.054 credit, a recognized reference posts boundary to the customer. An unknown reference posts boundary to suspense, then the suspense connects to the customer once operations attributes it. Both paths touch the boundary, so the invariant holds either way, and suspense aging becomes a queryable list.
Use the bank's notification reference as the idempotency key in your ingestion layer. A retried webhook with the same reference should produce zero new postings.
Don't key off the bank's internal sequence numbers. They can change between retries and will double-post the customer.
Two notifications for the same customer arriving in the same second are two distinct references and two distinct postings, each committed atomically.
Outbound rules work in reverse, and an outbound payout takes two postings:
1The first moves funds from the customer's sub-ledger to @platform:banks:partnerA:out:pending, keyed to your payment instruction.
2The second clears that pending account into the omnibus boundary when the bank's debit notification arrives, keyed to that notification's reference.
Prevent customer sub-ledgers from going below zero unless overdraft is part of the design. Returns after drawdown post to a named loss or receivable account under written policy.
Start building virtual accounts on a core ledger
A core ledger gives you the second reference the bank's report can't be. When the bank changes its vIBAN mapping, or when an auditor asks who owned a specific balance on a specific day, your own transactions are the record that answers.
Starting with a core ledger is the shortest path to a working invariant. The account tree, per-customer sub-ledgers, the suspense account, and the daily reconciliation check all live in one place, enforced by double-entry postings rather than application code.
Build the core ledger first, and every connector, workflow, and reconciliation rule you add later ties back to a record that already proves funds tie out to every customer entitlement.