Master Payment Accounting: Design Principles, Hotspot Account Fixes & Day‑Cut

1. Accounting Principles

Accounting is the foundation of payment transactions. Core concepts include the account subsystem, hotspot accounts, account merging, day‑cut (date‑switch), marketing‑related accounting, and settlement models.

1.1 Abstract from Scenarios

Identify the account owner, the scenario requirements, and the financial attributes needed. Distinguish external customers (who need payment services) from internal customers (clearing, operations, finance).

2. Account Subsystem

Accounts represent accounting subjects and can be classified by financial perspective (assets, liabilities, equity, profit‑loss) or by usage (deposit, intermediate, virtual). Typical institutions maintain central‑bank clearing accounts, payment‑institution accounts, and virtual sub‑accounts.

2.1 Account Types and Hierarchy

Customer accounts (personal or corporate)

Intermediate accounts (clearing, settled, pending)

Virtual accounts for specific business lines

2.2 Core Functions

Account creation and configuration

Balance management

Transaction recording (account flow)

Service interfaces: open, close, debit, credit, adjust

Principle: payment succeeds → debit succeeds → settlement succeeds.

2.3 Account Creation Example

主体ID: 123
ID类型: userid
用户类型: 个人
用户姓名: 张三
账户类型: 佣金账户
特殊要求: 可付款

3. Accounting as a Problem‑Solving Tool

Product managers can abstract business requirements into accounting models by identifying the responsible entity, target account, fee type, and recording time. This reduces development effort and clarifies requirements.

4. Hotspot Accounts

A hotspot account receives high concurrent updates (e.g., >10 updates/sec with latency >1 s), causing contention.

4.1 Mitigation Strategies

Rate limiting – install a “hotspot valve” to cap traffic.

Batch aggregation – accumulate updates over a time window and apply a single balance change.

Queue‑based buffering – serialize requests before updating the balance.

Sub‑account sharding – split the logical account into multiple physical sub‑accounts.

Cache‑first accounting – record changes in a fast cache and sync to the database periodically.

5. Account Merging

Common for guarantee‑deposit accounts across business lines. The merge process consists of:

Transfer balances from legacy virtual accounts to a new unified account.

Consolidate corresponding ledger entries.

Reallocate underlying bank‑deposit balances.

After merging, all future transactions reference the unified account, simplifying reconciliation.

6. Reverse‑Deduction (“倒扣”) Model

Instead of requiring pre‑payment of a guarantee, the platform deducts the required amount from future earnings until the total is covered.

6.1 Implementation Patterns

Settlement‑order method – generate a settlement bill that records the remaining deductible amount; deduct during each payout.

Account‑method – maintain a dedicated “deduction” account per merchant; each payout transfers the deductible portion from the settlement account to the deduction account.

Risk controls include limiting overdraft exposure and disabling merchants that exceed a predefined negative balance.

7. Sub‑Account Architecture

Complex scenarios (e.g., airline ticketing, multi‑level distribution) split a logical account into multiple sub‑accounts that reflect distinct cash‑flow paths. Benefits include fine‑grained permission control, clearer audit trails, and flexible extensions such as credit lines or investment accounts.

8. Day‑Cut (Date‑Switch) Principles

Day‑cut separates continuous transaction time into discrete accounting days, essential for interest calculation, reporting, and reconciliation.

8.1 Dual‑Balance Method

Each account stores a real‑time balance and a static end‑of‑day balance. Updates affect the appropriate field based on the current cut‑off date.

8.2 Shadow‑Account Method

During the cut‑off window, a temporary shadow account records incoming transactions; after the cut, the shadow data are merged back into the primary account. Both methods require locking to avoid race conditions between real‑time transactions and batch processing.

9. Marketing‑Related Accounting

Coupons and subsidies are treated as marketing expenses. Accounting differs by issuer:

Platform‑issued coupon → debit “Platform Marketing Expense”.

Merchant‑issued coupon → credit “Merchant Marketing Liability”.

When a user purchases a coupon, revenue is recognized at purchase, while the subsidy is recognized at redemption. Net marketing cost is reconciled at period end.

10. Settlement Accounting Implementation

The settlement workflow includes four stages: payment transaction, channel clearing, merchant settlement, and channel settlement. Each stage produces a data segment that is mapped to voucher rules.

Data segmentation : 1‑payment, 2‑clearing, 3‑settlement, 4‑reconciliation.

In‑transit balances : payment in‑transit, fund in‑transit, customer in‑transit.

Voucher rules map each segment to debit/credit entries on specific accounts (e.g., debit “Channel Clearing Receivable”, credit “Merchant Pending Settlement”).

The system matches entries, handles errors, and periodically reconciles so that all balances converge to zero.

11. Balance Update Flow

When a transaction is processed:

Validate the transaction’s legality.

Insert a record into the account‑flow table.

Update balances: total = total + amount; if the entry is frozen, update the frozen balance; otherwise update the available balance.

Self‑check ensures total balance = frozen balance + available balance. Successful updates notify the requester.

12. Freeze Configuration

Freeze rules are linked to entry rules. A rule defines whether the amount is fully or partially frozen, the freeze mode (fixed duration or fixed time point), and the freeze time. A daily scan unlocks eligible entries, moving the amount from frozen to available balance.