Harsh Thakkar
The Product Proposition

The VRN is the account number your customer pays.

A Virtual Reference Number is a bank-issued account number for receiving a payment. The client places that VRN in the invoice payment instructions as the account number to credit. When the customer pays that number, the bank uses it to identify the receivable and route the credit to the client’s designated collection structure.

The Receivables Challenge

Why receivables reconciliation gets complicated

Receivables teams connect payment activity across bank statements, remittance details, customer records and ERP or accounting systems. When payer-entered references are missing or inconsistent, the right cash can be difficult to match to the right customer, invoice or entity.

A challenging environment for receivables teams
  • Transaction Reference Numbers (TRNs)

    Track individual transactions but may not identify the customer or invoice associated with an incoming payment.

  • Remittance Information

    Customers may omit references, enter incorrect details or provide inconsistent information when making payments.

  • Centralized Collections

    Multiple customers or entities pay into one physical account, requiring additional information to identify the source.

  • ERP Reconciliation

    Missing or inaccurate payment information can prevent automatic matching and require manual investigation of exceptions.

Simplifying Receivables

From payment request to reconciliation

The client places the VRN account number on the invoice as the account to credit. The customer pays that number through their bank. The receiving bank recognizes the VRN and routes the credit into the client’s collection structure with the account number available for receivables matching.

How VRN collections workThree customers each pay their own virtual reference number. All payments land in one bank collection account, and the bank reports each credit with its VRN so receivables match automatically.Customer AInvoice INV-001PAYS TO ACCOUNT1001 2345 6789Customer BInvoice INV-002PAYS TO ACCOUNT1001 2345 6790Customer CInvoice INV-003PAYS TO ACCOUNT1001 2345 6791Bank collectionaccount1001 2345 6700+ VRNAutomatic reconciliationEach credit arrives with its VRNVRNCUSTOMERINVOICESTATUS1001 2345 6789Customer AINV-001Matched1001 2345 6790Customer BINV-002Matched1001 2345 6791Customer CINV-003Matched
Customer AINV-001PAYS TO1001 2345 6789Customer BINV-002PAYS TO1001 2345 6790Customer CINV-003PAYS TO1001 2345 6791Bank collection account1001 2345 6700+ VRNAutomatic reconciliationEach credit arrives with its VRNVRNCUSTOMERINVOICESTATUS…6789Customer AINV-001Matched…6790Customer BINV-002Matched…6791Customer CINV-003Matched
Invoice
  1. 01Generate VRN
  2. 02Issue invoice with VRN
Payment
  1. 03Customer pays the VRN
  2. 04Bank receives and identifies
Reconciliation
  1. 05Auto-reconcile
  2. 06Manage exceptions
Collection Models

VRNs support different collection models.

Use the same core capability across customer, invoice, dealer, subsidiary and platform collections. The reference structure follows the way the business receives and reconciles funds.

Virtual reference numbers
Single entityOne business, one physical account
  • VRN → customer

    B2B customer collections

    Persistent VRNs per customer identify the payer and support automated cash application.
  • VRN → invoice

    Invoice-level collections

    Invoice-specific VRNs link each payment to a single receivable.
  • VRN → dealer

    Dealer and regional collections

    VRNs per dealer, branch or location consolidate funds into one physical account.
Multi-entitySeveral entities or parties, attributed centrally
  • VRN → subsidiary

    Collections on behalf of (COBO)

    Treasury receives funds for subsidiaries; entity VRNs support identification and intercompany accounting.
  • VRN → entity AR

    Receivables on behalf of (ROBO)

    A central receivables team uses entity-linked VRNs to attribute funds and match receivables.
  • VRN → merchant

    Marketplace and platform collections

    VRNs per merchant or participant attribute collections centrally, subject to banking and regulatory requirements.
Product Design Considerations

Choose a VRN structure that fits the collection need

The right structure depends on how often a reference is used, what the business needs to identify and what its bank and receivables systems can support.

Customer-level VRN

Static
One VRN per customer, reused on every invoice.
Identifies
The paying customer
Best for
Recurring collections from the same payer

Invoice-level VRN

Dynamic
A new VRN for each invoice, closed once paid.
Identifies
A single receivable
Best for
Exact matching of individual invoices

Entity-level VRN

Static
One VRN per subsidiary, shared by its customers.
Identifies
A subsidiary or business unit
Best for
Centralized collections across entities (COBO, ROBO)