Ready‑to‑Use Settlement System Design Cases: 7 Real‑World Examples

10‑Step Settlement System Design Framework

Step 1: Identify data sources – order data, accounting data, or manually submitted settlement data serve as the basis for generating settlement documents.

Step 2: Define data acquisition paths – settlement parties’ basic and bank‑card information are usually stored in external systems; the settlement system must connect to these systems to retrieve required data.

Step 3: Design settlement documents – decide the types of settlement statements, their contents, and the workflow for each type.

Step 4: Abstract settlement modes – support settlement to bank cards or internal virtual accounts.

Bank‑card settlement: direct payment to the merchant’s signed settlement bank account.

Virtual‑account settlement: credit to a virtual account on the platform, from which merchants can withdraw.

Step 5: Define settlement cycles – support multiple cycle models such as T1 (next workday), D1 (next calendar day), D0 (same day), S0 (per‑order immediate), weekly, monthly, etc.

Step 6: Determine settlement initiator – automatic settlement according to contract rules or manual initiation by merchants.

Automatic: system triggers payment at the agreed time.

Self‑service: merchants submit settlement requests within the allowed cycle.

Step 7: Design settlement processing flow – each product may have a distinct flow; the article provides a D1 example diagram.

Step 8: Consider tax, invoice, and internal document linkage – decide whether settlement statements need tax handling, invoice matching, or reconciliation with internal inventory/receipt documents.

Step 9: Integrate payment module – map settlement statements to payment orders, define forward and reverse payment flows.

Step 10: Provide billing – generate clear bills showing amount, time, recipient, and debt/credit details; deliver via email, in‑system download, or API.

Case Study 1 – Enterprise Welfare Platform

The platform helps enterprises issue employee welfare vouchers or cards, leveraging tax‑exempt benefits (14% of employee salary for corporate welfare, etc.). The system aggregates purchase contracts, virtual‑account recharges, and distributes vouchers to employees. Core modules include settlement center, merchant settlement, and vendor settlement.

Business Flow

Enterprise purchases welfare products, recharges a virtual account, and distributes points or cards to employees. The platform earns service fees or product margins.

Case Study 2 – Government Service Platform

Terminal devices are procured by projects, stored after approval, and used for public services. Settlement covers procurement contracts, maintenance work orders, and exception handling.

Settlement Rules

Rules include ID, settlement type, object, cycle, method, and creation time. Individual settlements usually skip invoices and use a proxy‑payment channel; corporate settlements require invoice upload and bank transfer.

Case Study 3 – Promotion Platform

The platform aggregates multiple promotion projects (ETC, POS, credit cards, pension accounts). Three settlement types are defined: commission rewards, equipment deposit refunds, and task‑based bonuses.

Commission settlement varies by role (expansion specialist, seed agent, ordinary agent) and considers metrics such as team size, order volume, and effective agents.

Deposit refunds are processed based on actual equipment usage and wear.

Case Study 4 – Bank Acquiring Settlement

Settlement is the final step of the acquiring process, reconciling merchant transaction batches into a single settlement statement and transferring funds via core banking or national payment systems.

Supported settlement cycles include T+0, T+1, T+N, D+0, D+1, with holiday handling. Minimum/maximum settlement amounts trigger alerts or defer settlement.

Case Study 5 – Points E‑Commerce Platform

Merchants register, obtain settlement accounts, and after order payment the system freezes the amount. Upon order receipt, the clearing system splits cash, marketing subsidy, and platform commission, generating a bill.

Bill settlement occurs at T+1, with automatic push to the settlement system at 15:00 daily and final transfer to merchant bank accounts.

Case Study 6 – Highway ETC Platform

ETC settlement handles toll fees, with varying cycles (D0, D1, T1) and funding models (full‑amount settlement vs. net‑amount after refunds). The system fetches daily ETC bills from partner FTP, matches them to vehicles, and generates settlement bills for the payment center.

Compensation mechanisms handle delayed or missing bills, and a special "over‑payment receivable" type offsets excess payments.

Case Study 7 – Consumer Finance Platform

The platform provides short‑term consumer loans (1–12 months) via apps, public accounts, and partner channels. Settlement involves multiple parties: fund providers, guarantors, channel partners, and service agencies.

Core settlement flow: loan disbursement → repayment → split of funds to each participant, with automatic netting of receivable/payable amounts.

System Architecture

Key modules: account management, path management, receipt/payment rule management, project‑agreement management, and transaction management. The system supports real‑time, work‑day, daily, weekly, and monthly settlement cycles, various deduction and recharge modes, and both manual and automatic matching of receipts.

All images above are retained to illustrate the core concepts and flow diagrams described in the original article.