Settlement Ledger

A settlement ledger is a record that tracks the money a business owes to, or is owed by, its counterparties as a result of payments, and shows when those amounts are actually settled. A card acquirer uses one to record what it owes each merchant and what it is owed by card networks; a payment platform uses one to track funds due to sellers, partners and banks; a settlement system uses one to record each participant's position and the transfers that discharge it. The settlement ledger answers the question "who owes whom how much, and has it been paid?"

A settlement ledger is a specialised form of ledger, usually a subledger that feeds summary entries into the firm's general ledger. It sits alongside other operational ledgers, such as a wallet ledger recording customer balances, and is the main source for settlement reconciliation, in which internal records are compared with bank statements and settlement files.

A typical payments settlement ledger holds entries for:

• Obligations. Amounts that become due when transactions are captured, such as a merchant's sale, a payout to a seller or a fee due to a partner, with the expected settlement date and currency.
• Adjustments. Refunds, chargebacks, reversals, fees and reserves that change what is owed.
• Settlements. The actual movements of money that discharge obligations, linked to bank transactions or system confirmations.
• Status. Whether each item is pending, in a batch, settled, failed or under investigation.

By linking obligations to settlements, the ledger shows open positions at any time, such as the total owed to merchants but not yet paid out, or the amount expected from a card network that has not yet arrived.

Many firms also use the settlement ledger to calculate payouts. Instead of computing a merchant's or seller's payment separately, the payout engine reads the ledger balance due on the payout date, so that the amount paid and the amount recorded always come from the same source.

Modern payment companies usually build settlement ledgers on double-entry accounting principles, so that every movement debits one account and credits another and the books always balance. Common design features include:

• Immutability. Entries are never edited or deleted; corrections are made by posting new reversing entries, preserving a full audit trail.
• Idempotency. Each event carries a unique key, such as an idempotency key, so that retries and duplicate messages do not create duplicate entries.
• Multi-currency support. Balances are tracked per currency, with conversions recorded as explicit entries rather than silent recalculations.
• Time awareness. Entries carry both the time an event occurred and its effective or settlement date, so balances can be reported as of any point.

The general ledger records the firm's financial position for accounting and reporting, usually in summary. The settlement ledger holds the transaction-level detail behind certain general ledger accounts, such as amounts due to merchants, receivables from card schemes or funds in transit. At the end of each day or period, totals from the settlement ledger are posted to the general ledger, and the two are reconciled. Discrepancies may be parked temporarily in a suspense account until investigated.

Payment and settlement systems keep their own ledgers of participants' balances. In a real-time gross settlement system, the central bank's ledger records each participant's settlement account and moves balances as each payment settles. In net settlement systems, the ledger accumulates positions during a cycle and records the net transfers that settle them. In blockchain networks, the shared distributed ledger plays the role of both transaction record and settlement ledger, since recording a transfer on the chain is itself the settlement.

Because the settlement ledger determines how much money is paid out, weaknesses can cause direct losses. Common problems include duplicate payouts after system retries, missing entries for fees or chargebacks, timing mismatches across cut-offs and incomplete handling of currency conversions. Controls include automated reconciliation against external sources several times a day, alerts when balances do not tie out, segregation between the teams who can post adjustments and those who approve payouts, and regular review of aged open items. Regulators and auditors also rely on settlement ledger data to check that customer funds are safeguarded and correctly attributed, which makes ledger accuracy a compliance as well as an operational concern.