Map virtual collection accounts to customers and the actual bank balance

Obtain the bank's account-structure document and confirm which physical account receives funds. J.P. Morgan describes its virtual accounts as subledger records linked to a physical demand-deposit account. Its model illustrates why a virtual balance should not automatically become an additional bank balance in the general ledger.

Products called virtual accounts can differ, so document the actual arrangement with your provider. Identify the legal holder, physical account, currency and purpose of each virtual identifier. Ask the accountant to approve the ledger design before importing separate virtual reports alongside the physical bank statement.

Record the customer or collection purpose assigned to each identifier, its activation date and current status. Keep the bank's identifier distinct from your internal customer number. A customer name change should not silently create a new mapping or cause historical receipts to move to a different account.

Define who can request, approve and retire identifiers. Before reusing one, confirm with the bank whether reuse is supported and assess the risk that a former customer will continue paying it. Preserve mapping history so a receipt can be interpreted using the assignment that existed when the payment arrived. Include the effective date of each reassignment in the exported mapping.

Verify new payment instructions through the company's established approval process before sending them to customers. Keep the approved version with the mapping. If an incorrect identifier was distributed, track the affected customers and replacement instructions rather than assuming a master-data edit reached everyone.

Compare the virtual transaction report with physical-account activity for the same period and status. Explain unallocated receipts, bank charges, transfers and other movements that may not belong to a customer identifier. The sum of customer allocations may need a bridge to the total physical balance rather than a forced direct match.

Use transaction references to connect individual receipts across reports. Check whether the accounting integration imports both records as cash or treats one as allocation detail. A correctly mapped customer payment can still duplicate the ledger if both feeds create an independent receipt.

Review timing differences explicitly. A virtual report and a bank statement may use different cutoffs or update times. Keep the extraction times and balance definitions with the reconciliation, then follow unresolved items to the next report. Do not change customer allocations merely to make reports captured at different moments agree.

When several legal entities use the structure, obtain professional advice on the actual arrangement. J.P. Morgan notes additional legal and intercompany considerations for multi-entity designs. An identifier assigned to a subsidiary does not by itself establish a separate legal bank account or eliminate the need to account for transactions between entities.

Give unmatched payments a defined owner and a route to customer clarification. Keep the physical cash receipt intact while the allocation is researched. If an identifier is closed, monitor subsequent attempts and follow the bank's process for redirected or returned funds.

At each close, retain the mapping version, virtual activity, physical statement and reconciliation bridge. Review access and recently changed assignments with the account owner. A workable structure should let the accountant explain where the cash is held, which customer paid and which entity owns the resulting balance without adding the same funds twice.