A tuition centre receives dozens of bank transfers each week. Three families send exactly the same amount; some leave an invoice number blank, and one parent pays from a relative’s account. The centre sees real money in its bank account but cannot reliably identify which invoices have been settled. A virtual account collection service helps turn incoming transfers into identifiable, reconcilable customer receipts without requiring a separate operating bank account for every family.
A virtual account number (VAN) is typically a payer or purpose-specific identifier linked to the business’s designated bank account. In the arrangement described by UOB Singapore, a payer uses the assigned VAN, the bank credits the linked business account, and the VAN appears in transaction reporting to simplify receivables matching. The gold standard is genuine credit, correctly identified payer reference, accurate invoice allocation and a clear correction route for ambiguous or returned money.
This service differs from payment acceptance in Merchant Acquiring, automated deductions in Direct Debit Collection, or virtual money balances in Digital Wallets. It extends the eduKate Gold Standard into the day-to-day receipt that makes a customer ledger trustworthy.
Three family fees: how a virtual account prevents a false ‘paid’ status
| Assigned payer reference | Invoice due | Confirmed bank credit | Open balance |
|---|---|---|---|
| Family A VAN | S$280 | S$280 | S$0 |
| Family B VAN | S$320 | S$120 | S$200 |
| Family C VAN | S$360 | S$360 | S$0 |
| All three | S$960 | S$760 | S$200 |
This is an original fictional illustration. The bank credits the business’s linked account, and the business’s receivables system applies S$760 to these three invoices. A later confirmed S$200 credit on Family B’s VAN would clear the remaining balance, subject to actual allocation and bank evidence.
The 16 virtual account collection chapters
1. A virtual account identifier is not automatically a separate deposit account
A customer may see a bank-like number and conclude they have opened their own deposit account. That is generally not what a company’s receivables collection VAN does. In the Singapore bank arrangements described by UOB, the VAN identifies a payer or outlet, while incoming money reaches the merchant’s linked deposit account. The payer does not receive an independent banking relationship with the merchant’s bank merely through that number.
The UOB explanation is explicit about the linked account and the identifying VAN in statements. A trustworthy provider should state which legal entity owns the underlying account, what the customer is asked to pay, and who can trace an unexpected transfer. The service must not market reference numbers as segregated trust accounts without actual legal evidence.
2. Select the assignment scheme before accepting transfers
A VAN can be assigned per customer, branch, invoice or another permitted business purpose, depending on the bank’s product. Each design supports a different form of matching. Per-customer assignment helps identify ongoing receipts; per-invoice assignment may narrow a transfer to one billed amount, but it also creates lifecycle and expiry questions.
Decide whether identifiers are static or dynamic, who approves creation, how long each remains valid and whether a number can ever be reused. The bank must receive the correct mapping data. UOB describes bank-assigned or appropriately customised ranges, including customer identifiers as part of VANs. A finance team should not invent arbitrary numbers and assume the bank will accept them.
3. Understand what the bank credits and what the business allocates
A payer sends funds using a VAN as the destination reference. The receiving bank applies its supported validation and credits the registered business account. A receivables system then associates the reported VAN and transaction reference with a customer or invoice. Those last two steps are separate: a bank credit can be real even when the internal receivables allocation is wrong.
Preserve linked account, VAN, amount, currency, value date, bank reference and source channel. Verify the bank statement before treating money as collected, then post the approved allocation to accounts receivable. A collection dashboard should distinguish funds credited, identified, applied and still awaiting exception review.
4. A VAN can identify a payment purpose without proving who sent the money
A customer can sometimes instruct a relative or another company to pay an invoice using the assigned identifier. The bank’s report may accurately show the VAN but the actual sending account could belong to somebody else. Likewise, an accidental payment into a familiar VAN can land in the same merchant master account.
Match the reference with invoices and permitted payer arrangements, but do not assert that the VAN alone proves the sender’s identity or the legitimacy of a disputed debt. Investigate unusual payer and refund instructions through appropriate channels. Automatic matching is a bookkeeping convenience that still requires controls against mistaken identification.
5. Reconcile three customers with a partial payment
Imagine three fictional families owe S$280, S$320 and S$360, a combined S$960. Their assigned VANs appear on a business bank statement with completed credits of S$280, S$120 and S$360. The business has received S$760, but S$200 remains unpaid on the second invoice.
A good service matches all three correct VANs and leaves the S$200 balance open. It does not mark the S$320 invoice paid because the parent’s VAN appeared or because the combined bank balance increased. If the parent later sends a separate S$200 transfer with the same VAN, the centre can reconcile that payment to the remaining receivable without duplicating the earlier S$120.
6. Keep payments, invoices and customer credit distinct
A customer may have multiple invoices, an advance payment or a valid credit note. A correct incoming VAN does not determine which open item the customer intended to settle when more than one exists. Blindly assigning every payment to the oldest invoice can violate an actual remittance instruction or hide an unresolved dispute.
Define application rules based on invoice references, due amounts, source communications and contractual policy. Support unapplied cash and partial settlement as real accounting statuses. Notify the customer when a material ambiguity remains. A ledger that balances overall can still be wrong if one household’s money was allocated against another household’s tuition fees.
7. Never confuse a bank notification with final funds
An API may report a new inward-credit event, while the bank statement, settlement channel or original reference is still being updated. There can be duplicated webhook deliveries or delayed reports. Repeating an application whenever the same notification is received can falsely mark two invoices paid for one bank receipt.
DBS lists inward credit notifications, intraday credit confirmation and status enquiries among its business banking APIs. Preserve a durable bank transaction identifier and use idempotent posting in the receivables ledger. Financial completion comes from the actual confirmed credit, not the number of technical alerts processed.
8. A payer error should enter an exception queue, not disappear
Customers can mistype a VAN, use an inactive identifier, provide incomplete references or pay the wrong amount. The bank’s treatment depends on its validation rules and arrangement. Some invalid instructions may be rejected; other cases may reach a designated account but fail the business’s allocation controls.
Keep records of rejections, unidentified credits and any pending investigation. Identify who is authorised to determine that a payment belongs to a real invoice. Do not “fix” the issue by fabricating a matching VAN or silently crediting whichever customer has the closest amount. When funds are returned or reassigned, preserve the actual bank and accounting evidence.
9. VAN changes and reuse create long-lived mapping risk
A company might close an account, rename an outlet or move a customer to a new billing system. Old invoices and standing instructions can continue to reference a previously active VAN. Reassigning that number immediately to a different customer may cause a late transfer to be allocated to the wrong person.
Maintain effective dates, closure states and suitable non-reuse periods under the bank and business arrangements. Explain updated instructions through trusted customer channels. Reconcile legacy transactions and pending refunds before retiring a mapping. The objective is to preserve financial identity across business changes rather than maximise the recycling of convenient account numbers.
10. Link payment identifiers to the customer’s privacy expectations
A VAN can encode or reveal a customer number, outlet identity or other information. A business may want easy reference in statements but should avoid exposing unnecessary personal or sensitive details through public account instructions or reports. Bank statements and remittance data may also show names and additional identifiers.
Use proportionate identifier design, restricted exports and legitimate access to payer records. Staff should be able to reconcile a specific invoice without seeing every family’s personal details or unrelated bank transactions. Avoid treating a virtual account number as an authentication secret: it is principally a collection reference and should be protected accordingly.
11. Distinguish VAN collections from PayNow UEN and card acquiring
A Singapore business can receive payment through PayNow Corporate UEN, via FAST or GIRO transfers, or through card acquiring. These mechanisms need not provide the same customer-specific identification or reporting features. A UEN can identify the business as payee, while VAN arrangements can provide distinct assigned payer references.
The DBS PayNow Corporate guide explains UEN-based receiving and bank-statement notifications. The VAN service’s value is payer-to-receivable matching, not a claim that every transaction moves through an independent payment rail. Compare speed and fees using the actual underlying transfer methods rather than one generic promise of instant collections.
12. Protect refunds and outbound payment destinations independently
A customer may overpay S$100 or cancel a class and qualify for a refund. The receiving VAN does not automatically tell the business which bank account is legally authorised for refunding money. A transfer might have come from a third party, a shared account or a source the customer can no longer access.
Verify refund rights from the commercial contract and authenticate any destination using appropriate controls. Reference the original bank receipt, credited invoice, refund approval and actual outgoing payment. Do not send money to a newly provided account solely because the requester knows the VAN number. A refund is financially complete only when the rightful recipient is credited.
13. Reporting must agree with the general ledger and merchant bank
The bank can accurately credit S$50,000 during a day while the accounts-receivable system allocates only S$48,000 to customers. The remaining S$2,000 might be unapplied cash, disputed transfers, posting delays or an actual system error. A line in a suspense account does not itself resolve the difference.
Reconcile opening bank balance, all confirmed inflows, fees, reversals and closing statement; separately reconcile the customer subledger and outstanding receivables. Provide an exception report with reasons, ageing and named owners. A green dashboard should not be created by forcing unapplied cash into an arbitrary customer account.
14. Audit the bank and ERP integration during changes or outages
A company may integrate VAN reports with an accounting platform or build API-based notifications. A change in message fields, date format or leading-zero handling can break payer matching without affecting the underlying bank’s ability to receive funds. Customers keep paying, but the accounts team stops recognising them.
Test unique identifier formats, source versioning, duplicate reports, unusual currencies and failure replay. DBS describes virtual accounts and receivables reconciliation among its corporate digital cash solutions. Verify end-to-end account posting after a software upgrade and preserve a manual exception process rather than telling every payer to send again.
15. A fictional learning centre receives the right money in the wrong ledger
A tuition centre assigns a unique VAN to each family. One parent’s payment of S$320 is credited to the business bank, but a software update strips leading zeros from its VAN before matching. The finance team sends an overdue notice despite receiving the correct amount. The parent understandably shows a genuine bank transfer receipt.
A responsible service traces the bank statement, original full VAN, ERP mapping and invoice record. It reverses the incorrect receivables status, confirms the corrected allocation to the family and fixes the import format before the next batch. The hypothetical case illustrates how a virtual identifier solves little unless its full technical and financial meaning is preserved.
16. The gold standard is every receipt identifiable and properly applied
Virtual accounts can reduce manual reconciliation and shorten the delay between customer payment and release of their credit line or service. But the technology cannot prevent every wrong amount, disputed invoice or fraudulent request. Good operations measure unapplied cash, duplicate postings, incorrect payer matches, missing notifications and actual time until an invoice is settled.
A gold-standard service can reconstruct the customer, assigned VAN, banking event, internal allocation and final balance without guessing. It is especially valuable when many payers send similar amounts. Correct finance records and usable customer support define success, not how many virtual identifiers a bank can issue.
Virtual account and payer-matching FAQs
Is a virtual account number always its own bank deposit account?
No. In the UOB-style collection model, the VAN identifies the payer but funds reach the merchant’s linked bank account.
Does a VAN automatically prove the identity of the sending account owner?
No. A third party could make the payment using the customer’s assigned reference.
What if I pay only part of an invoice?
The actual receipt should reduce the receivable by the amount received and leave the genuine balance open.
Is a virtual account the same as a digital wallet?
No. A VAN can be a bank receivables identifier without creating a separate stored-money wallet.
Can a company issue refunds to the VAN?
Refund destinations and procedures depend on the actual bank arrangement; verify the rightful payee and supported outbound route.
A receivables and account-matching control audit
- Explain legal ownership of the master bank account and the reference-only role of VANs.
- Approve unique payer references, validity dates, retirement and authorised reuse.
- Reconcile confirmed bank credits to immutable transactions and customer allocations.
- Keep part-payments, excess credits, unidentified receipts and disputes visible.
- Authenticate refund destinations and account instruction changes separately.
- Preserve full identifiers, leading zeros and bank references through ERP/API changes.
- Measure aged exceptions and verify invoice correction and customer communication.
Bank-originated source material and relevant eduKate guides
- UOB Singapore: Virtual Account Services—Assigned Numbers and Linked Bank Accounts.
- DBS Singapore: Virtual Accounts and Receivables Reconciliation.
- DBS Singapore: Inward Credit Notification and Bank Status APIs.
- OCBC Singapore: Virtual Account and Business Collections.
- DBS Singapore: PayNow Corporate UEN versus Bank Account Collections.
- eduKate: Direct Debit Collection Services.
- eduKate: Payment Gateway Services.
- eduKate: Digital Wallet Services.
Educational financial-service operations, not a representation of a specific bank account product’s legal ownership, credit finality or fees. Check the provider’s actual virtual-account and receiving-bank agreement.