Booking versus non-booking entries

A booking entry changes the ledger balance, and a non-booking entry does not. A debit to a customer account is a booking entry, because the ledger balance falls. A credit to a customer account is a booking entry, because the ledger balance rises. A hold on a customer account is a non-booking entry, because the ledger balance does not change, only the available balance falls. A memo, a reservation, a future dated instruction and a queued payment are all non-booking entries until the moment they are released and posted. Source: Bank for International Settlements, Committee on Payments and Market Infrastructures; core banking and payment hub practice. The lifecycle of a payment moves between non-booking and booking entries, and the transition points must be specified. When a customer instructs a future dated payment, the hub records a non-booking entry and reduces the available balance, but the ledger balance is unchanged. On the execution date the hub releases the instruction, the core system posts a booking entry, the ledger balance falls, and the non-booking entry is removed. When a card payment is authorised, the card system records a non-booking hold, and the available balance falls. When a payment is queued for a cut-off, it is a non-booking entry until it is released, and if the cut-off passes without release, it stays non-booking and is carried to the next cycle. A worked example shows the two entry types side by side. A customer holds EUR 10,000 in a current account. On Monday the customer authorises a EUR 2,000 hotel payment by card, and the available balance falls to EUR 8,000, while the ledger balance stays at EUR 10,000, because the authorisation is a non-booking hold. On Tuesday the customer instructs a EUR 5,000 supplier payment for Friday, and the available balance falls to EUR 3,000, while the ledger balance stays at EUR 10,000, because the future dated instruction is a non-booking entry. On Friday the supplier payment is released, a booking debit of EUR 5,000 is posted, and the ledger balance falls to EUR 3,100. Each step is a different entry type, and the statement must show which is which. The parties and the systems that hold each entry type are different. The payment hub holds the non-booking entries: the future dated instructions, the queued payments and the pending authorisations. The core banking system holds the booking entries: the debits and credits that change the ledger balance. The card system holds the authorisation holds, and it sends the clearing file that converts a hold into a booking entry. A non-booking entry that has no matching booking entry after its expiry is a break, and a booking entry that has no matching non-booking entry is also a break, because every booking should have been a non-booking first. Failure happens when the transition from non-booking to booking goes wrong. A hold that is never released, because the clearing file was lost, leaves the customer unable to spend money that is theirs, and the fix is a hold expiry rule, typically 7 to 30 days, and a manual release process. A hold that is released too early, before the clearing file arrives, lets the customer spend the same money twice, and the bank bears the loss. A queued payment that is released after the cut-off will be booked on the wrong value date, and the correction needs a camt.087 value-date correction. Each failure is a lifecycle failure, and the fix is in the lifecycle design, not in the ledger. The effect on the bank, the customer and operations is that the two entry types decide what the customer sees and what the bank reports. For the customer, the available balance is the money that can be spent, and it is reduced by non-booking entries, while the ledger balance is the record of what has been posted, and it is changed only by booking entries. For the bank, the booking entries decide the balance sheet, while the non-booking entries decide the liquidity and the operational risk, because a large queue of future dated payments is a future outflow that treasury must fund. For operations, the two reconciliations must both be done every day, and a product that reconciles only the ledger will miss a queue that is growing out of control. For a business analyst, product owner or subject matter expert, the test is to name, for every payment event, whether it is booking or non-booking, and when it converts from one to the other. Ask what happens when a card authorisation is never cleared, when a future dated payment is cancelled, when a queued payment misses its cut-off, and when a hold expires. Ask how the customer is told about a non-booking entry, how it appears on the statement, and how long it may live before it is escalated. The ISO 20022 camt.052 intraday report can carry both booked and pending entries, and the camt.053 end of day statement carries only booked entries, so the mapping from the hub to the message must be specified, or the customer will receive a statement that does not match the channel. Two mistakes are common and must be avoided. The first is to call a hold a debit in a requirement, which causes the core system to post a booking entry for an authorisation, and the ledger will be wrong until the clearing file arrives and the duplicate is found. The second is to call a future dated instruction a payment in the customer communication, which tells the customer the money has moved when it has only been reserved, and the complaint will be about the missing credit at the beneficiary. The correct design is to use the words hold, reserved, scheduled and posted precisely, to show the non-booking entries as pending in the channel, and to convert them to booking entries only on the trigger event, with the conversion audited and reversible only by a correcting entry. Takeaway: a booking entry changes the ledger balance, a non-booking entry changes only the available balance, and every payment moves from non-booking to booking on a defined trigger. Holds, reservations, future dated instructions and queued payments are non-booking until they are released, cleared or executed. Name the entry type and the conversion trigger for every event. Further reading: Bank for International Settlements, Committee on Payments and Market Infrastructures, A glossary of terms used in payments and settlement systems; ISO 20022, camt.052 and camt.053 reporting. Last reviewed 7 November 2026.