Payments Training Hub
Double-entry ledger postings PAYMENT OPERATIONS STARTED LIVE 01 Double-entry ledger postings - payment creates at least two ledger entries ACTIVE 02 General ledger - highest level of the accounting structure QUEUED 03 Suspense accounts - safety net that catches postings which QUEUED 04 Intraday and end-of-day reconciliation - prove that the ledger agrees with the QUEUED 05 Automated matching - items, and the remainder go to analysts QUEUED 06 Confusing them - common source of errors QUEUED A payment creates at least two ledger entries, because double-entry accounting requires a debit and a credit for every movement of value. Step 1 of 6 Double-entry ledger postings STARTED Double-entry ledger postings payment creates at least two ledger entries ACTIVE General ledger highest level of the accounting structure QUEUED Suspense accounts safety net that catches postings which QUEUED Intraday and end-of-day reconciliation prove that the ledger agrees with the real QUEUED Automated matching items, and the remainder go to analysts QUEUED Confusing them common source of errors QUEUED A payment creates at least two ledger entries, because double-entry accounting requires a debit and a credit for every movement of value.
General ledger PAYMENT OPERATIONS IN PROGRESS LIVE 01 Double-entry ledger postings - payment creates at least two ledger entries DONE 02 General ledger - highest level of the accounting structure ACTIVE 03 Suspense accounts - safety net that catches postings which QUEUED 04 Intraday and end-of-day reconciliation - prove that the ledger agrees with the QUEUED 05 Automated matching - items, and the remainder go to analysts QUEUED 06 Confusing them - common source of errors QUEUED The general ledger is the highest level of the accounting structure, and it receives summarised postings rather than every individual payment. Step 2 of 6 General ledger IN PROGRESS Double-entry ledger postings payment creates at least two ledger entries DONE General ledger highest level of the accounting structure ACTIVE Suspense accounts safety net that catches postings which QUEUED Intraday and end-of-day reconciliation prove that the ledger agrees with the real QUEUED Automated matching items, and the remainder go to analysts QUEUED Confusing them common source of errors QUEUED The general ledger is the highest level of the accounting structure, and it receives summarised postings rather than every individual payment.
Suspense accounts PAYMENT OPERATIONS IN PROGRESS LIVE 01 Double-entry ledger postings - payment creates at least two ledger entries DONE 02 General ledger - highest level of the accounting structure DONE 03 Suspense accounts - safety net that catches postings which ACTIVE 04 Intraday and end-of-day reconciliation - prove that the ledger agrees with the QUEUED 05 Automated matching - items, and the remainder go to analysts QUEUED 06 Confusing them - common source of errors QUEUED Suspense accounts are the safety net that catches postings which cannot be matched immediately. Step 3 of 6 Suspense accounts IN PROGRESS Double-entry ledger postings payment creates at least two ledger entries DONE General ledger highest level of the accounting structure DONE Suspense accounts safety net that catches postings which ACTIVE Intraday and end-of-day reconciliation prove that the ledger agrees with the real QUEUED Automated matching items, and the remainder go to analysts QUEUED Confusing them common source of errors QUEUED Suspense accounts are the safety net that catches postings which cannot be matched immediately.
Intraday and end-of-day reconciliation PAYMENT OPERATIONS IN PROGRESS LIVE 01 Double-entry ledger postings - payment creates at least two ledger entries DONE 02 General ledger - highest level of the accounting structure DONE 03 Suspense accounts - safety net that catches postings which DONE 04 Intraday and end-of-day reconciliation - prove that the ledger agrees with the ACTIVE 05 Automated matching - items, and the remainder go to analysts QUEUED 06 Confusing them - common source of errors QUEUED Intraday and end-of-day reconciliation prove that the ledger agrees with the real world. Step 4 of 6 Intraday and end-of-day reconciliation IN PROGRESS Double-entry ledger postings payment creates at least two ledger entries DONE General ledger highest level of the accounting structure DONE Suspense accounts safety net that catches postings which DONE Intraday and end-of-day reconciliation prove that the ledger agrees with the real ACTIVE Automated matching items, and the remainder go to analysts QUEUED Confusing them common source of errors QUEUED Intraday and end-of-day reconciliation prove that the ledger agrees with the real world.
Automated matching handles more than ninety-five percent PAYMENT OPERATIONS IN PROGRESS LIVE 01 Double-entry ledger postings - payment creates at least two ledger entries DONE 02 General ledger - highest level of the accounting structure DONE 03 Suspense accounts - safety net that catches postings which DONE 04 Intraday and end-of-day reconciliation - prove that the ledger agrees with the DONE 05 Automated matching - items, and the remainder go to analysts ACTIVE 06 Confusing them - common source of errors QUEUED Automated matching handles more than ninety-five percent of items, and the remainder go to analysts with the full message trail. Step 5 of 6 Automated matching handles more than ninety-five percent IN PROGRESS Double-entry ledger postings payment creates at least two ledger entries DONE General ledger highest level of the accounting structure DONE Suspense accounts safety net that catches postings which DONE Intraday and end-of-day reconciliation prove that the ledger agrees with the real DONE Automated matching items, and the remainder go to analysts ACTIVE Confusing them common source of errors QUEUED Automated matching handles more than ninety-five percent of items, and the remainder go to analysts with the full message trail.
Confusing them PAYMENT OPERATIONS COMPLETE LIVE 01 Double-entry ledger postings - payment creates at least two ledger entries DONE 02 General ledger - highest level of the accounting structure DONE 03 Suspense accounts - safety net that catches postings which DONE 04 Intraday and end-of-day reconciliation - prove that the ledger agrees with the DONE 05 Automated matching - items, and the remainder go to analysts DONE 06 Confusing them - common source of errors ACTIVE Confusing them is a common source of errors, and a good integration design names each date explicitly in its contract. Step 6 of 6 Confusing them COMPLETE Double-entry ledger postings payment creates at least two ledger entries DONE General ledger highest level of the accounting structure DONE Suspense accounts safety net that catches postings which DONE Intraday and end-of-day reconciliation prove that the ledger agrees with the real DONE Automated matching items, and the remainder go to analysts DONE Confusing them common source of errors ACTIVE Confusing them is a common source of errors, and a good integration design names each date explicitly in its contract.

Key points of this lesson, in order.

0:00 / 3:07 Step 1 of 6

Ledger, General Ledger and Accounting Integration

Banking Integration Patterns, Lesson 3 of 9, Narration 3:07, D10 APIs and integration

Suspense accountReconciliationPayment hub

What you will learn

Your objective. By the end of this lesson, you will be able to explain ledger, general ledger and accounting integration. A payment creates at least two ledger entries, because double-entry accounting requires a debit and a credit for every movement of value.

Why it matters. Automated matching handles more than ninety-five percent of items, and the remainder go to analysts with the full message trail.

Chapter objective: Learner explains banking integration patterns, including file transfer, messaging, APIs, and event streaming, and selects the right pattern for a given payment integration need. Learner demonstrates this skill using realistic banking examples, explaining each step clearly and using correct terminology throughout.

Key learning points

  • Double-entry ledger postings
  • General ledger
  • Suspense accounts
  • Intraday and end-of-day reconciliation
  • Automated matching handles more than ninety-five percent
  • Confusing them

Key terms

Suspense account: A temporary account used to hold funds or entries that cannot yet be posted to their final account. Banks use suspense accounts for unidentified receipts, pending investigations and items awaiting...

Reconciliation: The process of comparing records from two sources, such as a bank statement and an internal ledger, to confirm they agree.

Payment hub: A central system in a bank that receives payment instructions from all channels, validates them, applies screening and routing rules, and sends them to the correct clearing system or correspondent.

Banking architecture diagram showing Ledger, General Ledger and Accounting Integration.

Practise this lesson

Exercise

Trace the payment in this lesson through its lifecycle stages.

Use the lifecycle stages in this lesson: acceptance, processing, clearing, settlement, beneficiary credit, ledger posting and reconciliation.

  1. What to do. Name each stage, state what happens, and say when the payment is truly final.

Correct result. Acceptance validates the instruction. Processing prepares it. Clearing sorts and nets it. Settlement moves the funds. Beneficiary credit puts the money in the creditor account. Ledger posting records it. Reconciliation proves it. Finality is only at settlement, not at acceptance or at status update.

Why. The lifecycle is the map of a payment. If you cannot say which stage a payment is in, you cannot answer where the money is.

Check your understanding

Practice question

Two systems must agree on what a payment status means. System A marks a payment as complete when the message is sent; System B marks it complete only when the beneficiary is credited. What is the integration risk?

Takeaway and next step

What to remember

Confusing them is a common source of errors, and a good integration design names each date explicitly in its contract.

Follow USD 5,000 through every stage, from instruction to beneficiary credit, and note where it can stop.

Open the Payment Lifecycle Simulator →

Builds on "Core Banking Integration Patterns".

Transcript and full text

Show transcript

A payment creates at least two ledger entries, because double-entry accounting requires a debit and a credit for every movement of value. When a customer sends USD 5,000 to another bank, the payment system debits the customer account and credits a settlement or clearing account. When the payment settles, the clearing account is debited and the nostro account is credited. Each entry carries the same transaction reference, the same value date, and the same amount, so that the chain can be followed from the customer instruction to the final settlement. If any entry is missing, the books do not balance, and the break must be found before the day closes. The general ledger is the highest level of the accounting structure, and it receives summarised postings rather than every individual payment. The payment system might send one summary entry per product per day, such as the total value of all Faster Payments sent, rather than a million separate entries. The finance team uses the general ledger to produce the balance sheet, the profit and loss account, and the regulatory returns. A mistake in the summarisation, such as posting a GBP 3 million total to the wrong cost centre, can distort the financial statements, so the interface between the payment system and the general ledger is tested as carefully as the payment flow itself. Suspense accounts are the safety net that catches postings which cannot be matched immediately. If a payment of EUR 750 arrives without a clear beneficiary account, the funds are parked in a suspense account while operations investigate. If a foreign exchange rate is missing for a USD payment, the accounting entry waits in suspense until the rate is supplied. Suspense balances must be reviewed daily, because a growing suspense balance means that breaks are not being resolved. A healthy bank clears most suspense items within one business day, and any item older than five days is escalated to a senior manager with a named owner and a deadline. Intraday and end-of-day reconciliation prove that the ledger agrees with the real world. The reconciliation system compares the payment hub records with the core banking records, the scheme settlement file, and the nostro bank statement, matching each item by reference, amount, and value date. A payment of INR 25,000 that appears in the hub but not in the core system is a break that must be investigated. A settlement amount that differs by one cent from the nostro statement is also a break, because a small difference can hide a larger systematic error. Automated matching handles more than ninety-five percent of items, and the remainder go to analysts with the full message trail. Value dates and cutoffs add a timing dimension that the ledger must respect. A payment instructed on Friday but settling on Monday must be recorded with the correct value date, because interest and regulatory reporting depend on it. A payment that misses the cutoff for a same-day scheme must be posted with the next business day as its value date, and the customer must be told. The accounting integration therefore carries the value date, the booking date, and the settlement date as separate fields, and each one is used for a different purpose. Confusing them is a common source of errors, and a good integration design names each date explicitly in its contract.

A payment creates at least two ledger entries, because double-entry accounting requires a debit and a credit for every movement of value. When a customer sends USD 5,000 to another bank, the payment system debits the customer account and credits a settlement or clearing account. When the payment settles, the clearing account is debited and the nostro account is credited. Each entry carries the same transaction reference, the same value date, and the same amount, so that the chain can be followed from the customer instruction to the final settlement. If any entry is missing, the books do not balance, and the break must be found before the day closes.

The general ledger is the highest level of the accounting structure, and it receives summarised postings rather than every individual payment. The payment system might send one summary entry per product per day, such as the total value of all Faster Payments sent, rather than a million separate entries. The finance team uses the general ledger to produce the balance sheet, the profit and loss account, and the regulatory returns. A mistake in the summarisation, such as posting a GBP 3 million total to the wrong cost centre, can distort the financial statements, so the interface between the payment system and the general ledger is tested as carefully as the payment flow itself.

Suspense accounts are the safety net that catches postings which cannot be matched immediately. If a payment of EUR 750 arrives without a clear beneficiary account, the funds are parked in a suspense account while operations investigate. If a foreign exchange rate is missing for a USD payment, the accounting entry waits in suspense until the rate is supplied. Suspense balances must be reviewed daily, because a growing suspense balance means that breaks are not being resolved. A healthy bank clears most suspense items within one business day, and any item older than five days is escalated to a senior manager with a named owner and a deadline.

Intraday and end-of-day reconciliation prove that the ledger agrees with the real world. The reconciliation system compares the payment hub records with the core banking records, the scheme settlement file, and the nostro bank statement, matching each item by reference, amount, and value date. A payment of INR 25,000 that appears in the hub but not in the core system is a break that must be investigated. A settlement amount that differs by one cent from the nostro statement is also a break, because a small difference can hide a larger systematic error. Automated matching handles more than ninety-five percent of items, and the remainder go to analysts with the full message trail.

Value dates and cutoffs add a timing dimension that the ledger must respect. A payment instructed on Friday but settling on Monday must be recorded with the correct value date, because interest and regulatory reporting depend on it. A payment that misses the cutoff for a same-day scheme must be posted with the next business day as its value date, and the customer must be told. The accounting integration therefore carries the value date, the booking date, and the settlement date as separate fields, and each one is used for a different purpose. Confusing them is a common source of errors, and a good integration design names each date explicitly in its contract.

Full lesson text (all scenes)

Completing a lesson updates your progress dashboard on the homepage.

Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.