Ledger is the accounting record that holds every financial transaction of a business, posted to named accounts so that any account's balance can be calculated at any time. The general ledger aggregates all accounts into the figures behind the balance sheet and profit and loss, while sub-ledgers hold transaction-level detail for one area, such as receivables, card settlements or customer e-money balances, and post summarised totals to it. Entries follow double-entry rules, are immutable and corrected by reversal. For payment and e-money institutions, the ledger must produce reliable daily customer balances for safeguarding reconciliation under rules such as CASS 15. Buyers test it through three-way reconciliation with bank and scheme reports, and persistent breaks lead to retentions or indemnities.
General ledger vs sub-ledger
A typical general ledger has a few hundred accounts. A payments company's customer sub-ledger can have millions, one per wallet or merchant. Keeping detail in sub-ledgers stops the general ledger becoming unmanageable and lets finance, operations and product teams each own their records.
Illustrative example: an EMI with 400,000 customer wallets keeps a running balance for each wallet in its e-money sub-ledger. At month end the sub-ledger shows €38.2 million owed to customers, and that single total is posted to the e-money liabilities account in the general ledger. If the two figures differ, a posting has been missed, duplicated or booked to the wrong period.
How does a double-entry ledger work in fintech
Every transaction is recorded as at least two entries that sum to zero: a €50 card top-up debits the safeguarding bank account and credits the customer's liability account. Ledgers built by fintech engineering teams apply the same rule in code. Entries are immutable, errors are corrected with reversing entries rather than edits, and writes are idempotent so that a retried API call does not post the same payment twice. Each entry also stores the external reference from the scheme, bank or acquirer, which is what later lets it be matched against statements.
Real-time balances are the other requirement. A card authorisation has to check available funds in milliseconds, so product ledgers usually hold a pending layer for authorised but unsettled amounts alongside the posted balance.
Why the ledger matters for safeguarding
Payment and e-money institutions must keep customer money separate from their own and prove it continuously. In the UK, CASS 15 of the FCA Handbook, in force since 7 May 2026, requires an internal safeguarding reconciliation at least once every reconciliation day, comparing the amount the firm's records say it owes customers with the funds it holds for them in its safeguarding account. A ledger that cannot produce a reliable customer balance by the end of each business day makes that check impossible.
What buyers check in a fintech ledger
In due diligence, the ledger is where a buyer tests whether reported revenue and customer balances are real. Typical requests are several months of three-way reconciliation between ledger, bank statements and scheme or acquirer reports, a list of unreconciled breaks with their age, and evidence of how manual adjustments are approved. Breaks that persist for weeks, or a ledger rebuilt in spreadsheets each month, point to safeguarding risk and usually lead to a price retention or a specific indemnity in the share purchase agreement.
See also: Sub-Ledger.