How Payment Systems Ensure Accurate Fund Reconciliation: A Deep Dive into Clearing and Settlement Processes

1. Clearing Reconciliation System

Payment companies rely on bank funds to back all financial services; each account's funds in the accounting system correspond one‑to‑one with bank deposits. To ensure correct conversion between real and virtual accounts, the company must promptly reconcile all fund movements with the bank.

1.1 Fund Inflow Reconciliation

Bank‑initiated fund inflows are notified to the payment company in real time. Each evening the bank credits the company's collection account and provides a clearing file, which the company matches against its business data.

(1) Bank recharge details exceed company records – temporary over‑accounting is applied pending investigation. (2) Bank recharge details are fewer than company records – potential loss, also handled with temporary over‑accounting.

1.2 Fund Outflow Reconciliation

When users request withdrawals, the company batches requests to the bank, which deducts from the company's deposit account. The bank returns success or failure files; successful withdrawals are recorded, while failures trigger a reverse credit without passing through the reconciliation center.

2. What Is Reconciliation?

2.1 Definition of Fund Reconciliation

In accounting, reconciliation ensures that ledger entries match supporting documents, achieving correctness, authenticity, and consistency. In payment institutions, it means comparing system‑saved transaction logs with bank‑provided clearing logs and files to verify that daily expected and actual balances of reserve accounts are identical.

2.2 Role of the Reconciliation Center

The reconciliation center is a system module dedicated to clearing reconciliation. It receives data from accounting and clearing systems, matches bank clearing flows with internal entry flows, and stores verified records in historical flow tables.

3. Reconciliation Content and Data Sources

Step 1: Match entry flows with clearing flows to ensure each order’s bank result aligns with the system result. Step 2: Compare summary confirmation sheets with bank statements to verify that all business‑level amounts are consistent.

3.1 Reconciliation Business Process

The process is illustrated by a flow diagram (image omitted).

3.2 Main Functions of the Reconciliation Center

The center handles various fund movements such as recharge, withdrawal, refund, purchase foreign exchange, loan disbursement, and repayment. It ensures that pending and cleared flows balance at daily cut‑off points, supports automatic posting, and provides reporting, balance entry, and internal account registration features.

4. Reconciliation Center Function Module Analysis

4.1 Acquiring Reconciliation Data

(1) Data is usually imported manually via a page, though some flows are auto‑matched or scheduled. (2) All clearing flow imports share a unified entry point with channel‑mapping logic. (3) Parsing rules differ per business type.

4.2 Clearing Flow Reconciliation

Images illustrate the matching logic.

4.3 Reconciliation Logic

One‑to‑One Reconciliation

Each entry flow matches a single bank flow based on channel, order number, and amount. Examples include various recharge and withdrawal codes.

Tips: Successful match → flag as “reconciled”; amount mismatch → flag as “amount unequal”; missing entry → flag as “bank over‑account”.

Many‑to‑Many Reconciliation

When multiple bank flows correspond to a single order (e.g., refunds), the system aggregates amounts before matching.

One‑to‑Many Reconciliation

Multiple entry flows may match a single bank flow, such as overseas settlement cases.

4.4 Reconciliation Functions

Internal Flow Matching

Internal flows (e.g., withdrawal and its reversal) are matched directly without bank involvement.

Reconciliation Summary Confirmation

Confirmed successful flows are moved to historical tables; mismatched or over‑account flows are classified, edited, or deleted as needed.

Flow Classification and Aggregated Posting

Over‑account flows are classified and posted in bulk, with specific business codes allowed for posting.

Clearing/Entry/Historical Flow Management

Modules provide query, edit, delete, and import capabilities for clearing and entry flows, while historical flows are read‑only.

Bank Balance Entry

Operators record actual bank balances, which are later verified against temporary balances and reconciled.

Internal Account Registration

Registers non‑bank internal accounts (e.g., clearing fees) with strict one‑debit‑one‑credit rules.

Pending Income/Expense Posting and Confirmation

Handles registration, posting, and confirmation of pending income and expense items, ensuring proper account sides and validation.

5. Unexpected Data Recovery Logic

5.1 Types of Anomalies

(1) Duplicate payments; (2) Payment failure with amount mismatch; (3) Successful payment with amount mismatch.

5.2 Recovery Process

Use Merchant Success Orders as Reference

Align backend order status with merchant‑reported success, without altering orders that lack corresponding merchant records.

Avoid Duplicate Recovery

Recover T‑day orders on T+1 day only once.

Time‑zone Differences

Bank cut‑off times differ, causing mismatches between merchant and backend data; these are treated as timing differences.