Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian AR and treasury teams cannot identify which customer paid a given bank credit when the underlying NEFT, RTGS, IMPS, or UPI rail carries a UTR but no invoice reference in the narration, leading to high unapplied cash balances.
Issue each customer a unique virtual account number mapped to a single physical master collection account, so every incoming credit carries the payer's virtual identifier and customer identification is deterministic at the bank-file level.
A customer master enriched with virtual account assignments, a daily bank file ingestion that reads the virtual ID field, and a reconciliation rule that matches virtual ID to customer code as the primary key before any narration-based fallback.
A bank reconciliation in which every master-account credit is tagged to a customer at the point of receipt, unapplied cash collapses to near zero, and AR cash application becomes a one-pass invoice allocation rather than a payer-identification puzzle.
Definition
A virtual account is a unique sub-account number — typically 16 to 20 digits — issued by an Indian commercial bank as an identifier mapped to a single physical master collection account. It carries no balance of its own; all funds sent to it settle into the master account, but the bank tags every incoming credit with the virtual identifier so that the receiver can identify the payer with certainty.
In one sentence: a virtual account is a fingerprint a bank gives each payer so the receiver can tell incoming credits apart at the moment they land.
Regulatory Reference
Virtual accounts are a commercial product of Indian banks rather than a Reserve Bank of India statutory construct. They sit inside the broader Payment and Settlement Systems Act, 2007 framework and operate on top of the NEFT, RTGS, IMPS, and UPI rails the RBI regulates.
Each major commercial bank publishes its own product specification — the character set permitted in the virtual identifier, the maximum length, the file format used to deliver tagged credits, and the API endpoints for creating and decommissioning virtual numbers. While there is no single RBI master circular on virtual accounts, the product operates within the broader KYC and customer due diligence framework — the master account holder is the regulated customer, and virtual account allocation does not create new KYC relationships.
Why It Matters
Three industries where virtual accounts have become standard infrastructure:
B2B receivables and distribution. FMCG, pharmaceutical, and industrial distributors collect from hundreds or thousands of stockists. Virtual accounts collapse a complex narration-based identification problem into a deterministic lookup.
Real estate and home loans. Builders issuing flats to thousands of buyers and NBFCs collecting EMIs from large retail books use one virtual account per booking or per loan, eliminating misallocation between accounts.
Education and fee collection. Schools, universities, and coaching institutes issue one virtual number per student-fee combination, so the receipt is identified at the point of bank credit without any reliance on parents typing the right reference.
How to Spot It in Practice
Four signals in the bank’s data:
- The bank statement carries a column labelled “Virtual Account”, “VA Identifier”, or “Sub Account” alongside the master account number.
- The MT940 or BAI2 file delivered by the bank carries a structured tag (often field :86: subfield) with the virtual identifier.
- The ERP customer master has a per-customer virtual account number field populated by an integration with the bank’s VA management API.
- A reconciliation dashboard shows near-zero unidentified credits in the master account because the virtual identifier resolves the payer at ingestion.
Common Misconceptions
- “Virtual accounts replace customer KYC.” They do not. The master account is the KYC-regulated relationship; virtual numbers are bookkeeping tags.
- “Every customer needs a virtual account.” Not necessarily. The cost-benefit favours virtual accounts where payer identification is the bottleneck, typically B2B with a long tail.
- “Virtual accounts eliminate cash application.” They eliminate the payer-identification step only. Allocation of the receipt across multiple open invoices still requires invoice-level logic.
- “All banks issue the same virtual account format.” Length and permitted characters vary materially between banks. Treasury teams managing multiple banking relationships normalise the formats inside the reconciliation engine.