Sub-Account

A sub-account is a subdivision of a larger account. It has its own identifier and its own balance and transaction history, but it exists within, and is legally or operationally tied to, a master account. Banks, payment institutions and fintech platforms use sub-accounts to keep track of which part of a pooled sum belongs to which customer, project, currency or department.

The term covers two different arrangements. In one, the sub-account is a real bank account opened in the books of a bank and linked to a parent account. In the other, it is only a record on a ledger maintained by a bank or by a fintech company, with all the actual money sitting in a single account. The second kind is often marketed as a virtual account, and the difference matters for ownership of funds, insolvency protection and regulation.

• Bank sub-accounts. A company opens several accounts under one relationship, for example one per subsidiary or per currency, which the bank reports individually and may sweep into a header account each day.
• Ledger sub-accounts in a pooled account. A payment firm holds client money in one omnibus account and records each client's share on its own books.
• Addressable sub-accounts. Each ledger balance is given its own account number, or virtual IBAN, so that incoming payments are routed to the right balance automatically.
• Wallet and card sub-accounts. A user divides their own balance into pots, budgets or currency pockets, or a business gives each employee card its own allocation.
• Platform sub-accounts. A payment provider creates a balance for each seller or user of a marketplace, from which payouts are made.

In banking-as-a-service and payments, the common pattern is the FBO account, a single account held at a bank in the name of a fintech company or the bank itself, for the benefit of the end customers. The bank's core system may see only one balance. The breakdown by customer is kept on a virtual ledger, run either by the bank, by a middleware provider or by the fintech company.

When a customer receives a payment, money arrives in the pooled account and the ledger credits that customer's sub-account. When the customer pays out, the ledger debits the sub-account and a payment leaves the pooled account. Transfers between two customers of the same program are simply book entries, with no movement of money at the bank. The sum of all sub-account balances should always equal the balance of the pooled account, and proving that it does is the purpose of daily ledger reconciliation.

Sub-accounts solve an identification problem. A business that collects from thousands of customers into one account must work out who paid each credit from the reference text. If each customer is given a unique account number that maps to a sub-account, the payer is identified by the number paid into, and cash application becomes automatic.

Corporate treasurers use the same idea internally. A group can replace many physical bank accounts with one account and a set of virtual sub-accounts for its subsidiaries, which cuts bank fees and gives a single view of cash. This underlies structures such as the in-house bank and paying or collecting on behalf of group companies.

For marketplaces and platforms, sub-accounts hold each seller's proceeds until payout. For consumer apps, they provide savings pots and multi-currency balances. In card issuing, a sub-account can back an individual card so that its spending is limited to the funds allocated to it.

A ledger sub-account is not, in itself, a bank account belonging to the end customer. The customer's rights depend on the legal structure around it.

In the United States, deposits held in a pooled custodial account can qualify for pass-through deposit insurance, under which each underlying owner is insured as if they held the deposit directly. This requires that the custodial relationship is disclosed and that records identifying each owner and their balance are properly maintained. In the European Union and the United Kingdom, payment and electronic money institutions do not offer deposit insurance. They must instead keep client money apart from their own under safeguarding rules, so that it is available to customers if the firm fails.

Banks also remain responsible for knowing who is using their accounts. Where a fintech company gives its own customers sub-accounts with individual account numbers, the bank must be satisfied that those customers have been identified and are monitored, or the arrangement can resemble a nested account that hides the real users from the bank.

The main risk is that the records are wrong. If the ledger and the bank balance drift apart, nobody can say with certainty how much each customer owns. This was shown in 2024 when the collapse of a United States middleware provider left many thousands of fintech customers unable to reach their money for months while partner banks and a court-appointed trustee tried to reconcile incomplete records. Regulators have since pressed banks to keep, or have direct access to, the sub-ledger for any pooled customer account.

Other risks include commingling of client and company money, errors in routing payments to the wrong sub-account, and customers misunderstanding what protection they have. Clear disclosure, independent reconciliation and segregation of funds are the standard safeguards.