[{"data":1,"prerenderedAt":277},["ShallowReactive",2],{"blog-\u002Fblog\u002Fvirtual-account-management-structures":3,"blog-related-\u002Fblog\u002Fvirtual-account-management-structures":252,"blog-surround-\u002Fblog\u002Fvirtual-account-management-structures":276},{"id":4,"title":5,"audience":6,"body":10,"cluster":212,"conversionGoal":213,"cornerstone":214,"date":215,"description":216,"draft":214,"extension":217,"factCheckedAt":218,"faq":219,"featured":214,"language":218,"meta":232,"minRead":233,"navigation":234,"order":235,"originalAsset":218,"path":236,"pillar":237,"primaryKeyword":238,"publicationOrder":239,"relatedProject":218,"releaseScope":218,"reviewCycle":240,"reviewMethod":241,"reviewStatus":242,"reviewedAt":215,"reviewedBy":243,"searchIntent":244,"seo":245,"sources":218,"stem":246,"tags":247,"type":250,"updated":215,"__hash__":251},"blog\u002Fblog\u002Fvirtual-account-management-structures.md","Virtual Account Management (VAM): Structures and Design",[7,8,9],"treasurer","treasury-system-lead","shared-services-lead",{"type":11,"value":12,"toc":201},"minimark",[13,32,37,44,48,80,83,87,99,103,109,112,116,129,133,153,157,183,186,189],[14,15,16,25,26,31],"p",{},[17,18,19,20,24],"strong",{},"Virtual account management (VAM) is the part that comes after the concept: not ",[21,22,23],"em",{},"what"," virtual accounts are, but how you design the structure, run it and get its data back out of the bank."," ",[27,28,30],"a",{"href":29},"\u002Fblog\u002Fwhat-are-virtual-accounts","What virtual accounts are"," is the easy half — sub-account identifiers over one real account, many numbers over one pot of cash. The hard half is structural: which real accounts carry the virtual ones, how deep the hierarchy goes, how virtual balances behave as a subledger, and how the whole thing lands in your statements and reconciliation. That design work is what banks and vendors sell as \"VAM\" — and what this post walks through.",[33,34,36],"h2",{"id":35},"vam-the-product-vs-vam-the-design","VAM the product vs VAM the design",[14,38,39,40,43],{},"Banks offer VAM as a product: the ability to issue virtual account numbers or virtual IBANs over a real account, track per-virtual-account positions, and report activity by virtual account. What the product does ",[21,41,42],{},"not"," include is the structure — which entities, purposes and customers get virtual accounts, and how they're arranged. That is treasury's design decision, and it's where implementations succeed or quietly bloat. The bank provides the mechanism; you provide the model.",[33,45,47],{"id":46},"the-three-structures-that-cover-most-cases","The three structures that cover most cases",[49,50,51,58,69],"ul",{},[52,53,54,57],"li",{},[17,55,56],{},"Per-payer collection structures."," A unique virtual IBAN per customer, so every incoming payment self-identifies by the account it hits. This is the receivables-reconciliation pattern, and for many companies it is the entire business case on its own.",[52,59,60,63,64,68],{},[17,61,62],{},"Segregation structures."," A virtual account per entity, business line, currency-purpose or project over one real account — the identification benefits of many accounts without opening them. This is ",[27,65,67],{"href":66},"\u002Fblog\u002Fbank-account-rationalization","account rationalization"," done structurally: you don't close the sprawl, you stop creating it.",[52,70,71,74,75,79],{},[17,72,73],{},"In-house-bank structures."," Virtual accounts representing internal participants over a central real account, so group entities hold positions with the ",[27,76,78],{"href":77},"\u002Fblog\u002Fwhat-is-an-in-house-bank","in-house bank"," rather than at external banks — the plumbing beneath payments- and collections-on-behalf-of.",[14,81,82],{},"Most real designs combine two of these — for example, entity-level segregation with per-customer collection accounts nested beneath one entity.",[33,84,86],{"id":85},"the-subledger-model","The subledger model",[14,88,89,90,93,94,98],{},"The mental shift that makes VAM design clear: ",[17,91,92],{},"virtual balances are a subledger, not balances."," The real account has the only actual balance; each virtual account's \"balance\" is the running sum of transactions tagged to it — informational, maintained by the bank, always reconcilable back to the one real number. Design questions become subledger questions: can a virtual position go negative, how are balances rolled up the hierarchy, and does the arrangement between your entities constitute intercompany lending? That last one is the same position-tracking discipline as ",[27,95,97],{"href":96},"\u002Fblog\u002Fcash-concentration-sweeping-and-zba","cash concentration"," — sweeping creates intercompany loans physically, virtual structures create the equivalent positions informationally, and both need owners, limits and documentation.",[33,100,102],{"id":101},"designing-the-hierarchy","Designing the hierarchy",[104,105,106],"pull-quote",{},[14,107,108],{},"Every level in a virtual account hierarchy has to earn its place in a report someone actually reads. If a level exists only because the bank supports it, it's mapping work with no customer.",[14,110,111],{},"Multi-level hierarchies — real account at the top, entities beneath, purposes or customers beneath entities — are where VAM designs go to over-engineer. Banks differ in how many levels they support and how balances roll up, so a portable design stays shallow: two levels cover the overwhelming majority of genuine requirements. Deep trees multiply statement volume, mapping tables and month-end explanations, and the unwind is painful because account numbers, once given to payers, are sticky.",[33,113,115],{"id":114},"getting-the-data-back-out","Getting the data back out",[14,117,118,119,123,124,128],{},"The structure is only as good as its reporting. Cash moves on the real account; the virtual account rides along as the identifying reference. How that reference reaches you differs by bank — per-virtual-account statements, or one real-account statement with per-transaction virtual references, commonly in ",[27,120,122],{"href":121},"\u002Fblog\u002Fcamt-053-structure-and-fields","camt.053 statements"," and ",[27,125,127],{"href":126},"\u002Fblog\u002Fcamt-054-notification-explained","camt.054 notifications",". Two design-phase checks save the project: confirm exactly how each bank reports virtual activity (this varies more than the sales deck admits), and test reconciliation with real files before go-live — a virtual structure that reconciles badly is worse than the physical accounts it replaced, because now the mismatch is invisible.",[33,130,132],{"id":131},"when-not-to-use-vam","When not to use VAM",[49,134,135,141,147],{},[52,136,137,140],{},[17,138,139],{},"Where regulation wants a real account."," Some jurisdictions and some purposes (tax, payroll, local statutory requirements) expect a resident physical account; a virtual IBAN is not always an accepted substitute. Verify per country before designing it away.",[52,142,143,146],{},[17,144,145],{},"Where the bank's VAM is thin."," Capability varies significantly by bank and country; a structure designed around one bank's rich VAM offering may not port to the next bank.",[52,148,149,152],{},[17,150,151],{},"Where the problem is small."," A company with a dozen accounts and clean references doesn't need a virtual hierarchy — it needs its references enforced.",[33,154,156],{"id":155},"what-usually-goes-wrong","What usually goes wrong",[49,158,159,165,171,177],{},[52,160,161,164],{},[17,162,163],{},"Hierarchy sprawl"," — levels nobody reports on (see the pull-quote; it's the classic).",[52,166,167,170],{},[17,168,169],{},"Reconciliation designed last"," — the structure is agreed with the bank before anyone checks how it lands in statement files.",[52,172,173,176],{},[17,174,175],{},"Intercompany positions untracked"," — entity-level virtual accounts silently accumulate internal balances no one documents until audit or repatriation forces the question.",[52,178,179,182],{},[17,180,181],{},"One-bank thinking"," — a design that only one bank can operate, discovered during the next banking RFP.",[14,184,185],{},"Design the structure from the reports you need, keep it as shallow as those reports allow, and treat virtual balances with the same intercompany discipline as physical sweeps — then VAM delivers what it promises: the identification of many accounts, the administration of few.",[187,188],"hr",{},[14,190,191],{},[21,192,193,194,123,197,200],{},"See also ",[27,195,196],{"href":29},"what are virtual accounts",[27,198,199],{"href":66},"bank account rationalization",".",{"title":202,"searchDepth":203,"depth":203,"links":204},"",2,[205,206,207,208,209,210,211],{"id":35,"depth":203,"text":36},{"id":46,"depth":203,"text":47},{"id":85,"depth":203,"text":86},{"id":101,"depth":203,"text":102},{"id":114,"depth":203,"text":115},{"id":131,"depth":203,"text":132},{"id":155,"depth":203,"text":156},"structures","topic-hub",false,"2026-09-01","Virtual account management (VAM) is how you design and run virtual account structures — hierarchies, subledgers, virtual IBANs — and when each type fits.","md",null,[220,223,226,229],{"question":221,"answer":222},"What is virtual account management (VAM)?","Virtual account management is the discipline — and the bank product category — of designing and operating virtual account structures: deciding which real accounts carry which virtual accounts, how the hierarchy is levelled, how virtual balances are tracked as a subledger over the real balance, and how the structure flows into statements and reconciliation. Banks sell VAM as a product; treasury still owns the design, because the bank provides the mechanism, not the structure.",{"question":224,"answer":225},"What are the main types of virtual account structures?","Three patterns cover most real implementations: per-payer collection structures (a unique virtual IBAN per customer, for automatic receivables identification), segregation structures (a virtual account per entity, business line or purpose over one real account, replacing physical accounts), and in-house-bank structures (virtual accounts representing internal participants over a central real account, supporting on-behalf-of payments and collections). Most real designs combine two of the three.",{"question":227,"answer":228},"What is a multi-level virtual account hierarchy?","A structure where virtual accounts are nested: a real account at the top, a virtual account per entity beneath it, and further virtual accounts per purpose or customer beneath each entity. Banks differ in how many levels they support and how balances roll up. The working rule is to keep the hierarchy as shallow as the reporting actually requires — every extra level adds mapping, statement volume and explanation, and deep trees are the most common form of VAM over-engineering.",{"question":230,"answer":231},"How do virtual accounts appear in bank statements and reconciliation?","The cash movement happens on the real account, and the bank reports activity with the virtual account as the identifying reference — depending on the bank, as statements or notifications per virtual account, or as one statement on the real account carrying virtual account references per transaction. That reference is what your reconciliation keys on, so confirming exactly how each bank reports virtual account activity (and testing it with real files) belongs in the design phase, not after go-live.",{},6,true,8.4,"\u002Fblog\u002Fvirtual-account-management-structures","cash-and-liquidity-management","virtual account management",228,"annual","editorial","reviewed","Tan Gravam","informational",{"title":5,"description":216},"blog\u002Fvirtual-account-management-structures",[248,249],"treasury","cash-management","text","3qbmW3pT1takODCS0yptDe8gKpX1Obl3k8iacoso4sk",{"related":253,"prev":266,"next":268,"hasOrder":234,"place":271},[254,258,262],{"path":255,"title":256,"description":257},"\u002Fblog\u002Fbank-relationship-management","Bank Relationship Management","How a company deliberately manages which banks it uses, for what, and the value exchanged both ways — because the bank relationship is two-way, not one-sided.",{"path":259,"title":260,"description":261},"\u002Fblog\u002Fwhat-is-a-payment-factory","What Is a Payment Factory?","A payment factory centralizes payments for many entities through one channel, often with payments-on-behalf-of (POBO). Why, how, and the intercompany catch.",{"path":263,"title":264,"description":265},"\u002Fblog\u002Fintercompany-netting","Intercompany Netting: How It Works","Intercompany netting offsets what group entities owe each other so only net positions settle, cutting payments, FX and fees. Bilateral vs multilateral netting.",{"path":29,"title":267,"type":250,"language":218},"What Are Virtual Accounts?",{"path":269,"title":270,"type":250,"language":218},"\u002Fblog\u002Felectronic-bank-account-management-ebam","Electronic Bank Account Management (eBAM)",{"label":272,"position":273,"total":274,"hub":275},"Structures",9,13,"\u002Ftopics\u002Fcash-and-liquidity-management",[],1788294625813]