Adviserflow DirectEnterprise Wealth Tech
Lending & Payments

Does Your Treasury Team Need Virtual Account Management? How VAM Works and What It Costs

Virtual accounts can cut bank-account sprawl and fix reconciliation, but POBO and COBO raise tax and regulatory questions. Here's how virtual account management works, what it costs and when it pays off.

By the Adviserflow Direct editorial team · November 2026 · 9 min read

The question treasury teams are really asking

If your group runs dozens or hundreds of bank accounts across several banks and countries, someone has probably proposed virtual account management as the fix. The pitch: fewer physical accounts, automatic matching of incoming payments, and one place to pay suppliers for every subsidiary. The real question is narrower. Do your problems come from the account structure, or from processes and data that virtual accounts won't touch?

Virtual account management (VAM) earns its keep in three situations: high-volume collections that your team reconciles by hand, an account footprint that grows with every new entity or market, and bank fees and idle balances scattered across too many places. If none of those describe you, a VAM project will cost more than it saves. If two or three do, it's usually among the better-return treasury projects a mid-size or large group can run.

Advertisement

How a virtual account actually works

A virtual account is a reference number, often formatted as a full account number or IBAN, that sits on top of a real physical account at a bank. It holds no money of its own. When a customer pays into virtual account 4471, the cash lands in the physical master account and the bank records that it arrived via 4471. The ledger behind the virtual layer tracks a balance per virtual account, but legally there's one account and one balance.

That gives you two levers. First, identification: issue each customer, contract or subsidiary its own virtual number and incoming payments match themselves, with no reliance on remittance text the payer typed badly. Second, segregation without physical accounts: each business unit sees "its" balance and statement while the cash is already concentrated, so you don't need daily sweeps from 40 accounts into one header account.

Most banks let you open virtual accounts in minutes through a portal or API, often in nested hierarchies (region, entity, customer). That's the operational win. Opening a physical account can take weeks of KYC per entity; a virtual account typically needs little beyond the master account's onboarding, though bank policies differ.

POBO, COBO and the in-house bank

Virtual accounts are the plumbing. Payments on behalf of (POBO) and collections on behalf of (COBO) are the operating models built on them, usually run through an in-house bank, a group treasury entity that acts as banker to the subsidiaries.

  • POBO: the in-house bank pays a subsidiary's supplier from a central account. The supplier is paid, the subsidiary's debt is settled, and an intercompany payable now exists between the subsidiary and the in-house bank.
  • COBO: a customer of a subsidiary pays into a central account, often to a virtual account carrying the subsidiary's name. The in-house bank receives the cash and owes it to the subsidiary, creating an intercompany receivable.

Both models shrink the number of external accounts sharply. A group can run regional payment and collection centers from a handful of physical accounts instead of one per entity per currency. The cost is a web of intercompany balances that must be booked daily, settled or interest-bearing, and defensible to tax authorities. That accounting and tax layer, not the bank technology, is where most POBO and COBO projects slip.

What VAM fixes, and what it doesn't

Reconciliation. This is the strongest use case. A lender collecting loan repayments, a payments company receiving merchant settlements, or a wealth manager taking client subscriptions can assign a unique virtual number per payer and lift auto-match rates substantially for bank transfers. It does little for card receipts or cash, and nothing if your ERP can't consume the virtual account reference in bank statements. The camt.053 or MT940 fields need to carry it through.

Account sprawl. Virtual accounts let you close physical accounts, but only where the subsidiary doesn't legally need its own. Payroll, tax payments and certain regulated activities often still require a local account in the entity's own name.

Fees and trapped cash. Fewer physical accounts means lower maintenance fees, fewer sweeps and fewer signatory lists to maintain. Concentrated balances can also earn more or cost less. What VAM won't do is move cash out of a market with capital controls. A virtual account in a restricted currency is still trapped cash.

Bank-provided VAM versus TMS-side options

You can run the virtual layer at a bank, in your treasury management system (TMS), or both. Global transaction banks such as J.P. Morgan, Citi, HSBC, Deutsche Bank, BNP Paribas, Standard Chartered and DBS offer bank-side VAM, and regional banks in the Gulf, India and Southeast Asia increasingly do too. TMS and ERP vendors, including Kyriba, SAP, FIS and ION, provide in-house bank functionality that keeps the virtual ledger on your side. Confirm current product scope with each vendor.

FactorBank-provided VAMTMS-side in-house bank
Who holds the virtual ledgerThe bankYour treasury team
Speed to launchFast for one bank and regionSlower; needs configuration and accounting design
Multi-bank coverageWeak; each bank's VAM is separateStrong; one ledger across all banks
Incoming payment identificationStrong; payer sees a real account numberDepends on bank references or matching rules
Intercompany accountingReports only; you still book itAutomated postings and interest calculation
Lock-in riskHigh; customers pay to that bank's numbersLower; bank changes are invisible to entities

For most groups with one dominant cash-management bank per region, the better fit is bank VAM for collections and a TMS in-house bank for POBO and intercompany accounting. Collections need numbers the payer can send money to, which only a bank can issue. Intercompany bookkeeping should live in a system you control.

What virtual account management costs

Pricing varies widely by bank, region and how much other business you bring. The figures below are typical 2026 market ranges in USD, for orientation only. Local pricing differs, so confirm with vendors.

Cost itemTypical 2026 rangeWhat drives it
Bank VAM setup$0 to $25,000 per regionOften waived for large relationships
Per virtual accountUnder $1 to a few dollars per month, or tiered bundlesVolume; collection-heavy users negotiate bulk tiers
Physical account maintenance avoided$30 to $300 per account per monthCountry, currency, bank tier
TMS in-house bank module$40,000 to $250,000 per yearEntities, users, modules, deployment
Implementation$75,000 to $600,000+Countries, ERP integration, tax design work
Tax and legal advice$20,000 to $150,000+Number of jurisdictions in scope

A hypothetical worked example: say a group with 18 entities in 10 countries runs 140 physical accounts at an average of $120 per month each. Closing 90 of them saves about $130,000 a year in maintenance alone, before sweep fees, reduced reconciliation effort and better interest on concentrated cash. Against a $300,000 implementation and a $90,000 annual TMS module, fee savings alone don't pay back quickly; the case depends on reconciliation labor and interest benefits making up the gap. Start from 30 accounts and the math rarely works on fees at all.

Tax, transfer-pricing and regulatory checks by region

POBO and COBO change who legally pays and receives money, so every jurisdiction in scope needs review by qualified tax and legal advisers before go-live. The patterns below describe how things generally work, not advice for your structure.

Transfer pricing everywhere

Intercompany balances created by POBO and COBO are financial transactions. Under OECD transfer-pricing guidance, which most tax authorities follow in some form, they generally need arm's-length interest or a documented short-term settlement policy. Check withholding tax on intercompany interest, thin-capitalization limits and whether the in-house bank has enough substance to earn its margin.

Europe and the UK

Intragroup payment activity often sits outside payment-services licensing, but the boundary matters if any third-party flows creep in. Virtual IBANs have drawn regulator attention on anti-money-laundering grounds, and payee-name checks such as the EU's Verification of Payee and the UK's Confirmation of Payee mean the account name on a virtual IBAN must match what payers expect. Some countries also require invoices to show who receives payment, and VAT treatment can change when a different entity collects.

Asia-Pacific

Rules vary sharply. Singapore and Hong Kong are generally considered friendly to regional POBO and COBO centers. India's foreign-exchange rules restrict cross-border POBO and netting, though domestic virtual accounts for collections are common. China generally permits cross-border POBO and COBO only within approved regimes, with registration requirements. Several Southeast Asian markets often expect local-currency payments from local accounts.

Middle East, Africa and Latin America

Gulf banks offer virtual accounts for collections, and the UAE is a common regional treasury hub. Some GCC states apply withholding tax to certain cross-border payments and expect local entities to meet specific obligations themselves. In much of Africa and Latin America, exchange controls and central-bank reporting limit cross-border POBO, so many groups run in-country COBO only.

Red flags and a decision rule

Watch for these when reviewing proposals:

  • A bank quote that prices virtual accounts cheaply but raises transaction fees on the master account.
  • No clear answer on how virtual account references flow into your ERP statement import.
  • A project plan with no tax or transfer-pricing workstream before configuration starts.
  • An assumption that every subsidiary can close its local accounts, made before checking payroll, tax and licensing needs.
  • Exit terms that leave thousands of customer-facing virtual numbers tied to one bank with no migration support.

The decision rule: start with collections if your team reconciles a large volume of incoming transfers by hand, say several thousand a month. Start with POBO and an in-house bank if you run a large physical account estate, roughly 75 or more, and most of your entities sit in jurisdictions without exchange controls. If neither applies, fix statement data and matching rules first. Your next step is a two-column inventory: every physical account, and the legal or operational reason it has to exist. The accounts with no reason are your business case.

Quick answers

Is a virtual account a real bank account?

No. It's a reference number, often formatted as an account number or IBAN, linked to one physical account at a bank. Funds sit legally in the physical account, while the bank or your TMS tracks a sub-balance for each virtual number.

Can we use virtual accounts across several banks?

Bank-side virtual accounts only work within the bank that issues them, so a multi-bank group ends up with separate VAM setups. To get one view across banks, groups usually run an in-house bank ledger in a TMS or ERP and feed it statements from each bank.

Do POBO and COBO need a banking or payments license?

In many jurisdictions, purely intragroup payment and collection activity falls outside payment-services licensing, but details vary and third-party flows can change the answer. Have local legal counsel confirm the position in each country before go-live.

How long does a VAM implementation take?

It depends on scope. A single-bank collections setup in one region can often go live within a few months. A multi-country POBO and COBO program with an in-house bank, ERP integration and tax review typically takes a year or more and is often rolled out in waves by region.

What happens to virtual accounts if we change banks?

Virtual account numbers belong to the issuing bank, so customers paying into them must be given new details. That's the main source of lock-in. Negotiate migration support, a parallel-running period and payment redirection terms in the original contract.

Written by the Adviserflow Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.