Mastering the Four-Stage Reconciliation Model for Large Payment Institutions

Seven years ago I worked in the reserve‑fund management line of a leading payment institution, handling reconciliation, cost billing, merchant billing, clearing, settlement, accounting, finance processing, reserve‑fund reporting, and fund allocation.

Reconciliation is a critical step, ensuring the accuracy of tens of millions of transactions and hundreds of billions of funds each day.

1. Four Data Segments

The four core data segments are accounting data, payment data, clearing data, and settlement data. By assigning numeric codes to each segment and its sub‑categories (e.g., payment, refund, payout, payout reversal), the model can uniquely identify and match every piece of data.

To distinguish sub‑categories within a segment, a coding scheme is designed that can recognize each subclass.

2. Three Verification Groups

Based on the relationships among the four segments, three verification groups are generated:

Accounting verification : matches payment records with accounting records to ensure every payment request is recorded for correct merchant settlement.

Transaction verification : matches the platform's payment records with the channel's clearing records to ensure consistency.

Fund verification : matches channel clearing with channel settlement to confirm that the money received is correctly settled.

3. Three Types of Errors

The verification can reveal three error categories:

Accounting error – wrong entry : accounting data and payment data mismatch, causing over‑ or under‑payment to merchants.

Transaction error – one‑sided record : platform payment data differs from channel clearing data, leading to single‑sided or mismatched entries.

Fund error – amount discrepancy : differences between receivable/payable and actual receipt/payment, affecting real cash.

4. Adding New Data Segments for Errors

Each error and its handling generate new data segment types (e.g., segments 5, 6, 7, 8), extending the original four‑segment model.

5. Purpose of Data Segments

Assigning segment codes reveals the originating system and business type, enabling rule‑based accounting processing such as transaction‑based accounting rules.

Example: a user pays 10 CNY, the payment core generates a “2001” payment‑receivable record, resulting in the following journal entry:

Debit: Clearing receivable – 10 CNY

Credit: Merchant payable – 10 CNY