Designing Multi‑Currency Accounts for Global Payments: A Practical Methodology

01 Accounting Overall Architecture

The accounting system is divided into five layers. The top Business Layer initiates operations such as remittance, collection, FX, settlement, and refunds, generating business documents without directly touching accounts. The Accounting Acceptance Layer validates these documents, determines processing rules, and creates accounting vouchers. The Core Accounting Layer runs two parallel ledgers: the Customer Ledger, which updates each customer’s currency balances and transaction logs, and the Institution Financial Ledger, which updates reserve‑account balances, records income, fees, and FX differences. Both ledgers are driven by the same transaction ID and reconciled daily. The Storage Layer persists accounts, balances, and logs with physical isolation for customer and institution data.

02 Account Sub‑System

The sub‑system records who owns money, how much, and how it changes, handling multi‑country users, multi‑currency balances, and diverse regulatory demands. Subject management stores holder information, KYC status, and jurisdiction. An account can hold all currencies or be split per business type.

Balance dimensions include book balance, available balance, frozen balance, and in‑transit balance, with the relationship: book balance = available + frozen + in‑transit . In‑transit amounts are shown to merchants as expected arrivals to improve experience.

Institutional ledgers reflect legal entities (e.g., HK MSO, SG MAS, UK FCA) that open dedicated bank accounts for reserve funds, own funds, and fee income, each mapped to a currency.

2.3 Posting and Freezing Rules

Posting records a fund movement; freezing locks part of the funds. Exchange rates can be locked at quote time (e.g., a 15‑minute lock) and applied at posting. Example journal entries for receiving 100 EUR and converting at 1.08 USD:

Debit: Customer A – EUR Balance 100 EUR
Credit: FX Transitional – Customer A 100 EUR

Debit: FX Transitional – Customer A 100 EUR (at 1.08 = 108 USD)
Credit: Customer A – USD Balance 108 USD

A simplified approach records two linked transaction lines instead of full double‑entry.

Freezing strategy defines currency priority, converts frozen amounts at the freeze‑time rate, and may re‑evaluate amounts if rates change, with configurations for freezing whole accounts, sub‑accounts, or individual customers.

2.4 Transaction Log and Balance Design

Each transaction log entry must contain an accounting date (based on the entity’s legal location) and a timezone field, ensuring consistent daily cutoffs across regions. Balances are updated per currency in isolated rows to avoid performance bottlenecks.

03 Customer Reserve Fund Isolation

Reserve funds (customer pending payments) must be kept in dedicated bank deposit accounts separate from the institution’s own funds, never mixed, invested, or used for other purposes. Isolation occurs at three levels:

Account Isolation: Customer accounts and institution bank accounts reside in different database tables or databases.

Entry Isolation: Customer ledger entries record customer balance changes; institution ledger entries record real fund movements. Both are linked by the transaction ID.

Balance Isolation: Customer balances and reserve‑account balances are calculated independently and reconciled daily.

Reserve accounts can be managed per currency, and multiple reserve accounts may exist for the same currency (e.g., USD reserve in JPMorgan and Citi) requiring aggregation during reconciliation.

04 Sub‑Account Splitting

Virtual sub‑accounts under a main account are created per business dimension, each with its own balance and transaction log. This achieves physical concentration of funds (single reserve account) while maintaining logical isolation.

Example: a cross‑border e‑commerce platform with North America, Southeast Asia, and independent‑site channels opens settlement accounts in USD, EUR, and SGD. Without sub‑accounts, all USD receipts would be mixed, making month‑end reconciliation ambiguous. With sub‑accounts, each channel’s balances are distinct, and automatic aggregation rules can move excess EUR to USD when thresholds are met.

05 Global Daily‑Cut Sub‑System

Daily‑cut switches the accounting day at a fixed moment, essential for accounting periods, data archiving, and batch processing. Global payments span 24 time zones, so each jurisdiction runs its own daily‑cut schedule (e.g., APAC UTC+8 00:00, EU UTC+1 00:00, Americas UTC‑5 00:00). Transactions are tagged with entity and timezone; the cut process routes data to the appropriate accounting day.

The architecture has three layers:

Scheduling Layer: Manages regional cut timetables, holidays, and calendars.

Execution Layer: At cut time, switches the accounting day pointer, creates read‑only snapshots, and triggers batch jobs, ensuring reliability.

Compensation Layer: Handles exceptions, such as transactions spanning the cut, by re‑validating boundary transactions after the cut completes.

Daily‑end processing includes balance roll‑forward, interest calculation on in‑transit funds (if required by regulation), automatic aggregation of sub‑account balances, and automated reconciliation of customer balances with reserve accounts.

06 Reconciliation Mechanism

Reconciliation ensures that customer ledger totals match the institution’s real funds. It is performed per currency, per legal entity, and per day. Differences fall into three categories:

Timing Differences: Bank‑side entries not yet reflected in the platform or vice‑versa; these resolve automatically in the next cycle.

Operational Differences: Missing entries on either side; require manual investigation, tracing the offending transaction, and creating corrective entries.

System Differences: Bugs or configuration errors; require fixing the system and re‑running reconciliation.

After adjustments, all corrective entries are archived for audit purposes.

Conclusion

The core of any accounting design is to know whose money it is, how much, and how it changes. Global payment institutions must ensure that every cent is traceable and auditable across exchange‑rate volatility, overlapping time zones, and divergent regulations, keeping customer and institution ledgers perfectly aligned.