Design and Implementation of a Multi‑Entity, Multi‑Currency Fund Processing Platform

The payment center at QUNAR is a public support department responsible for all payment‑related business, including complex fund management across multiple entities and currencies. To meet these needs, a SaaS‑style fund processing platform was built to handle accounting, day‑end processing, fund monitoring, reserve management, billing, and reconciliation, forming a closed‑loop between virtual and real bank funds.

Business Scenario : A typical case involves a user purchasing an airline ticket using a combination of balance and a "take‑to‑spend" guarantee payment. The flow includes three companies (CQLOAN, QXJF, QUNAR) for user payment and two companies (QUNAR, Alipay) for the procurement side.

Payment Fund Flow : Consists of three nodes – user balance payment, "take‑to‑spend" payment, and agency guarantee payment. The agency guarantee payment uses frozen accounts to ensure fund safety, with various account types (cash, frozen, procurement, profit, refund, credit, pre‑payment) for dedicated use.

Procurement Fund Flow : Includes agency outflow and Alipay deduction of QUNAR's reserve funds.

Business Model : The platform links virtual funds recorded in the accounting system with real bank funds, ensuring consistency through dual‑certificate mechanisms. A simple diagram illustrates the relationship between virtual reserve accounts and actual bank accounts.

Sub‑systems of the Platform :

Core accounting system (accounting, bookkeeping, day‑end)

Reconciliation system (data collection, wide‑table, reconciliation, discrepancy handling)

Fund post‑processing (billing, settlement, monitoring, reserve management)

Query system (query, data export, download)

Ensuring System Accuracy : The article outlines three key consistency challenges – asynchronous internal system data, payment‑center‑to‑accounting consistency, and payment‑center‑to‑third‑party consistency – and describes daily audit procedures such as entry verification, ledger balance checks, transition account validation, and total‑detail reconciliation.

Reconciliation : Internal reconciliation resolves data differences between payment subsystems, while external reconciliation aligns the payment center with third‑party data using gateway records. A diagram shows the reconciliation workflow.

The article also discusses time‑lag issues in reconciliation and proposes solutions such as unified timestamp parameters and rolling reconciliation windows.

Finally, the piece ends with a brief announcement about an upcoming React Native conference, inviting readers to scan QR codes for more information and ticket purchase.