Sub-ledger to general ledger

The sub-ledger and the general ledger are two levels of the same accounting, and the payment sub-ledger is where every payment is recorded in detail, while the general ledger is where the totals are recorded by account. The sub-ledger holds one entry per payment, with the message identifier, the amount, the currency, the value date, the debtor and the creditor, and the posting reference. The two must agree, and the agreement is proved by a summarisation and a reconciliation, every day. Source: Bank for International Settlements, Committee on Payments and Market Infrastructures; International Financial Reporting Standards, conceptual framework. The summarisation rules decide how the sub-ledger totals are posted to the general ledger, and they must be specified, not assumed. A common rule is to summarise by account, by currency and by value date, so that all EUR payments to the T2 settlement account on one value date are posted as a single general ledger entry for the total, with the sub-ledger holding the detail. A third rule is to summarise returns separately from payments, so that the return volume is visible to operations and to risk. A fourth rule is to post foreign exchange differences to a separate account, so that a payment in USD that settles in EUR does not hide the exchange gain or loss inside the payment total. Each rule must be approved by finance, because it decides what the financial statements show. A worked example shows the summarisation in numbers. On Monday Bank A processes 1,000 SEPA Credit Transfers totalling EUR 10 million, 50 returns totalling EUR 500,000, and fees of EUR 2,000. The payment sub-ledger holds 1,000 entries for the payments, 50 entries for the returns, and 1,000 entries for the fees. The summarisation posts to the general ledger as debit customer deposits EUR 10 million and credit T2 settlement EUR 10 million, debit T2 settlement EUR 500,000 and credit customer deposits EUR 500,000, and debit customer deposits EUR 2,000 and credit fee income EUR 2,000. If the general ledger shows EUR 10 million and the sub-ledger sums to EUR 9. 9 million, the difference of EUR 100,000 is a break, and the missing payment must be found. The parties and the systems are the payment hub, which creates the sub-ledger entries, the ledger system, which holds the general ledger, and finance, which owns the chart of accounts and the summarisation rules. The hub raises a posting event for each payment, with the message identifier as the reference, and the ledger consumes the event, validates that the debit equals the credit, and posts to the sub-ledger. The interface must be idempotent, so that a retried posting event does not post twice, and it must be auditable, so that any general ledger total can be drilled down to the sub-ledger entries that made it, and any sub-ledger entry can be traced to the message that caused it. Failure is a sub-ledger to general ledger break, and the break has a standard handling. A payment that is in the general ledger but not in the sub-ledger means a manual journal was posted directly to the general ledger, bypassing the sub-ledger, and the fix is to reverse the manual journal and to post through the sub-ledger, because a general ledger entry without sub-ledger detail cannot be reconciled to a payment. A difference in amount, where the sub-ledger sums to a different total from the general ledger, means a posting was duplicated or a fee was included in the wrong total, and the fix is a correcting entry, approved by finance, with the original entries left visible. The effect on the bank, the customer and operations is that the sub-ledger is the operational record and the general ledger is the financial record, and both must be right. For the customer, the sub-ledger is the source for the statement, because it holds the payment detail, the reference and the value date. For operations, the reconciliation between the two is the daily proof that every payment was accounted for, and a break that is not cleared before the close means the books cannot be closed, and the finance team must stay until it is found. A business analyst must specify the summarisation, the reconciliation and the break handling for every payment type. For a business analyst, product owner or subject matter expert, the test is to trace a payment from the message to the sub-ledger to the general ledger and back, and to prove that the totals agree. Ask how the sub-ledger is summarised, by which dimensions, how often, and who approves the rules. Ask what happens when a posting event is retried, when a manual journal is posted, and when the summarisation fails. Ask how a general ledger total is drilled down to its sub-ledger entries, and how a sub-ledger entry is traced to its message. The ISO 20022 messages provide the reference, the sub-ledger provides the detail, and the general ledger provides the totals, and the three must be linked by the message identifier and the posting reference, or the audit will fail. Two mistakes are common and must be avoided. The first is to post directly to the general ledger, bypassing the sub-ledger, which creates a total that cannot be explained payment by payment, and the auditor will treat it as a control failure. The second is to summarise by day only, without separating payments, returns, fees and foreign exchange differences, which hides the return volume, the fee income and the exchange result inside a single total, and management cannot see what is happening. The correct design is to summarise by account, currency, value date and event type, to reconcile the sub-ledger to the general ledger every day, and to clear breaks before the close, with any break older than one day escalated to finance. Takeaway: the payment sub-ledger holds one entry per payment with full detail, the general ledger holds the totals by account, and the summarisation rules decide how the detail becomes the totals. Reconcile the two every day, drill down from any total to its payments, and never post directly to the general ledger. Further reading: International Financial Reporting Standards, Conceptual Framework for Financial Reporting; Bank for International Settlements, Committee on Payments and Market Infrastructures, A glossary of terms used in payments and settlement systems. Last reviewed 7 November 2026.