Payments Academy
Value date versus booking date PAYMENT OPERATIONS STARTED LIVE 01 Value date versus booking date - two different dates for the same payment ACTIVE 02 Rules setting each date - Under the EU Payment Services Directive QUEUED 03 EUR 1 million value date - pacs. QUEUED 04 Dates carried in ISO 20022 messages - effect on the bank QUEUED 05 Value date failure and correction - ISO 20022 camt.087 message exists QUEUED 06 State both dates - value date is set by the scheme and the law QUEUED The value date and the booking date are two different dates for the same payment, and confusing them causes interest errors, reconciliation breaks and customer complaints. Step 1 of 6 Value date versus booking date STARTED Value date versus booking date two different dates for the same payment ACTIVE Rules setting each date Under the EU Payment Services Directive QUEUED EUR 1 million value date pacs. QUEUED Dates carried in ISO 20022 messages effect on the bank QUEUED Value date failure and correction ISO 20022 camt.087 message exists QUEUED State both dates value date is set by the scheme and the law QUEUED The value date and the booking date are two different dates for the same payment, and confusing them causes interest errors, reconciliation breaks and customer complaints.
Rules setting each date PAYMENT OPERATIONS IN PROGRESS LIVE 01 Value date versus booking date - two different dates for the same payment DONE 02 Rules setting each date - Under the EU Payment Services Directive ACTIVE 03 EUR 1 million value date - pacs. QUEUED 04 Dates carried in ISO 20022 messages - effect on the bank QUEUED 05 Value date failure and correction - ISO 20022 camt.087 message exists QUEUED 06 State both dates - value date is set by the scheme and the law QUEUED Under the EU Payment Services Directive, Directive (EU) 2015/2366, the value date for a credit to a payment account must be no later than the business day on which the amount is credited to Step 2 of 6 Rules setting each date IN PROGRESS Value date versus booking date two different dates for the same payment DONE Rules setting each date Under the EU Payment Services Directive ACTIVE EUR 1 million value date pacs. QUEUED Dates carried in ISO 20022 messages effect on the bank QUEUED Value date failure and correction ISO 20022 camt.087 message exists QUEUED State both dates value date is set by the scheme and the law QUEUED Under the EU Payment Services Directive, Directive (EU) 2015/2366, the value date for a credit to a payment account must be no later than the business day on which the amount is credited to
EUR 1 million value date example PAYMENT OPERATIONS IN PROGRESS LIVE 01 Value date versus booking date - two different dates for the same payment DONE 02 Rules setting each date - Under the EU Payment Services Directive DONE 03 EUR 1 million value date - pacs. ACTIVE 04 Dates carried in ISO 20022 messages - effect on the bank QUEUED 05 Value date failure and correction - ISO 20022 camt.087 message exists QUEUED 06 State both dates - value date is set by the scheme and the law QUEUED In a pacs. Step 3 of 6 EUR 1 million value date example IN PROGRESS Value date versus booking date two different dates for the same payment DONE Rules setting each date Under the EU Payment Services Directive DONE EUR 1 million value date pacs. ACTIVE Dates carried in ISO 20022 messages effect on the bank QUEUED Value date failure and correction ISO 20022 camt.087 message exists QUEUED State both dates value date is set by the scheme and the law QUEUED In a pacs.
Dates carried in ISO 20022 messages PAYMENT OPERATIONS IN PROGRESS LIVE 01 Value date versus booking date - two different dates for the same payment DONE 02 Rules setting each date - Under the EU Payment Services Directive DONE 03 EUR 1 million value date - pacs. DONE 04 Dates carried in ISO 20022 messages - effect on the bank ACTIVE 05 Value date failure and correction - ISO 20022 camt.087 message exists QUEUED 06 State both dates - value date is set by the scheme and the law QUEUED The effect on the bank, the customer and operations is that dates are money. Step 4 of 6 Dates carried in ISO 20022 messages IN PROGRESS Value date versus booking date two different dates for the same payment DONE Rules setting each date Under the EU Payment Services Directive DONE EUR 1 million value date pacs. DONE Dates carried in ISO 20022 messages effect on the bank ACTIVE Value date failure and correction ISO 20022 camt.087 message exists QUEUED State both dates value date is set by the scheme and the law QUEUED The effect on the bank, the customer and operations is that dates are money.
Value date failure and correction PAYMENT OPERATIONS IN PROGRESS LIVE 01 Value date versus booking date - two different dates for the same payment DONE 02 Rules setting each date - Under the EU Payment Services Directive DONE 03 EUR 1 million value date - pacs. DONE 04 Dates carried in ISO 20022 messages - effect on the bank DONE 05 Value date failure and correction - ISO 20022 camt.087 message exists ACTIVE 06 State both dates - value date is set by the scheme and the law QUEUED The ISO 20022 camt.087 message exists for exactly this correction Step 5 of 6 Value date failure and correction IN PROGRESS Value date versus booking date two different dates for the same payment DONE Rules setting each date Under the EU Payment Services Directive DONE EUR 1 million value date pacs. DONE Dates carried in ISO 20022 messages effect on the bank DONE Value date failure and correction ISO 20022 camt.087 message exists ACTIVE State both dates value date is set by the scheme and the law QUEUED The ISO 20022 camt.087 message exists for exactly this correction
State both dates for every payment PAYMENT OPERATIONS COMPLETE LIVE 01 Value date versus booking date - two different dates for the same payment DONE 02 Rules setting each date - Under the EU Payment Services Directive DONE 03 EUR 1 million value date - pacs. DONE 04 Dates carried in ISO 20022 messages - effect on the bank DONE 05 Value date failure and correction - ISO 20022 camt.087 message exists DONE 06 State both dates - value date is set by the scheme and the law ACTIVE The value date is set by the scheme and the law, and a wrong value date is corrected with a camt.087 and a compensating interest adjustment. Step 6 of 6 State both dates for every payment COMPLETE Value date versus booking date two different dates for the same payment DONE Rules setting each date Under the EU Payment Services Directive DONE EUR 1 million value date pacs. DONE Dates carried in ISO 20022 messages effect on the bank DONE Value date failure and correction ISO 20022 camt.087 message exists DONE State both dates value date is set by the scheme and the law ACTIVE The value date is set by the scheme and the law, and a wrong value date is corrected with a camt.087 and a compensating interest adjustment.

Key points of this lesson, in order.

0:00 / 7:42 Step 1 of 6

Value dates and booking dates

Accounts and balances, Lesson 3 of 4, Narration 7:42, D02 Accounts, ledger and accounting

ReconciliationExecution datePayment hub

What you will learn

Your objective. By the end of this lesson, you will be able to explain value dates and booking dates. The value date and the booking date are two different dates for the same payment, and confusing them causes interest errors, reconciliation breaks and customer complaints.

Why it matters. Takeaway: the booking date is when the entry is posted, the value date is when interest starts and funds are considered available, and the two can differ by days.

Chapter objective: Every account a bank holds, and what a balance really means

Key learning points

  • Value date versus booking date
  • Rules setting each date
  • EUR 1 million value date example
  • Dates carried in ISO 20022 messages
  • Value date failure and correction
  • State both dates for every payment

Key terms

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

Execution date: The date on which the bank executes a payment instruction, debiting the debtor account and sending the message onward.

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.

ISO 20022 XML explorer showing Value dates and booking dates.

Practise this lesson

Exercise

A corporate instructs a EUR 1 million payment on Friday 6 November 2026 with a value date of Monday 9 November 2026, and separately deposits a GBP 50,000 cheque on Monday. State the booking date and the value date for each.

Use the lesson: booking date is when the entry is posted, value date is when interest starts and funds are considered available.

  1. What to do. State both dates for the EUR 1 million payment and for the cheque, and explain the interest effect of the cheque.

Correct result. EUR 1 million payment: booking date Monday 9 November and value date Monday 9 November, so no interest difference. Cheque: booked Monday, value date Wednesday when it clears, so the customer earns no interest on GBP 50,000 for Monday and Tuesday and cannot withdraw it until Wednesday.

Why. Dates are money: the value date decides interest and availability.

Check your understanding

Practice question

What is the difference between the booking date and the value date?

Takeaway and next step

What to remember

Takeaway: the booking date is when the entry is posted, the value date is when interest starts and funds are considered available, and the two can differ by days.

Follow EUR 1 through every stage, from instruction to beneficiary credit, and note where it can stop.

Open the Payment Lifecycle Simulator →

Builds on "Ledger versus available balance".

Transcript and full text

Show transcript

The value date and the booking date are two different dates for the same payment, and confusing them causes interest errors, reconciliation breaks and customer complaints. The booking date is the date the entry is posted to the account, the date the ledger balance changes. The value date is the date from which interest is calculated, the date the funds are considered to have been available to the holder. For a same day payment the two dates are the same, but for a future dated payment, a back valued payment, a cheque, or a cross-border payment, they can differ by days, and the difference is money. Source: Bank for International Settlements, Committee on Payments and Market Infrastructures; ISO 20022 pacs.008 and camt.053 date fields. The rules for each date are set by the payment system, the bank and the law, and they must be stated in the product terms. The booking date is set by the bank posting process, and it is usually the date the payment is processed. The value date is set by the scheme or the settlement system, and it is the date the beneficiary bank must make the funds available, subject to cut-offs and non-working days. Under the EU Payment Services Directive, Directive (EU) 2015/2366, the value date for a credit to a payment account must be no later than the business day on which the amount is credited to the payee payment service provider account. These are legal duties, not service aspirations. A worked example shows the money at stake. A corporate customer instructs a EUR 1 million payment on Friday 6 November 2026, with a value date of Monday 9 November 2026, because the payment is future dated to Monday. A second example is different: a cheque for GBP 50,000 is deposited on Monday, booked on Monday, but the value date is Wednesday, when the cheque clears, so the customer cannot earn interest on the GBP 50,000 for Monday and Tuesday, and cannot withdraw it until Wednesday. A third example is a cross-border payment received on Friday with a value date of Monday, because the nostro account is credited on Monday, and the beneficiary who expected Friday value will complain, and the complaint is about the value date, not the booking date. The parties and the messages that carry the dates are the debtor agent, the creditor agent and the clearing system, and the ISO 20022 messages carry both dates as separate fields. In a pacs.008 the two dates are separate fields. In a camt.053 statement the booking date and the value date are reported as separate date fields for each entry, so the customer can reconcile interest. In a pain.001 the requested execution date is set by the customer, and the bank must honour it subject to cut-offs, or reject the instruction with a reason. A requirement that maps only one date, or that maps the value date into the booking date field, will produce a statement that cannot be reconciled, and the error will be found by the customer finance team, not by the bank test team. Failure is a date error, and the remedy is a value-date correction, which is taught in full in ch71s7. A payment booked with the wrong value date causes the wrong interest to be calculated, and the correction is a camt.087 value-date correction message, with a compensating interest adjustment. A payment booked on the wrong date, for example a payment dated for a bank holiday, will be rejected by the clearing system or held until the next working day, and the customer must be told the new value date. A payment with a value date in the future that is never executed, because the instruction was cancelled, must release the hold on the available balance on the cancellation date, not on the value date. The effect on the bank, the customer and operations is that dates are money. For the bank, the value date decides the interest it pays and receives, the liquidity it must hold, and the reporting it must make, because interest is calculated on value dated balances, not on booked balances. For operations, the booking date and the value date must be reconciled separately: the booking date reconciles against the processing file, and the value date reconciles against the settlement and interest calculations. A product that shows only one date to the customer will generate complaints that operations cannot answer without looking at the underlying message. For a business analyst, product owner or subject matter expert, the test is to state both dates for every payment type, and to state the rule that sets each one. Ask what the value date is for a same day payment, a future dated payment, a cheque, a direct debit, a card clearing, and a cross-border payment, and ask what happens when the value date falls on a non-working day. Ask how the customer is told the value date, how it appears on the statement, and how a value-date error is corrected, with the message, the timeline and the interest adjustment. The ISO 20022 camt.087 message exists for exactly this correction, and the requirement must name it, or the correction will be done as a manual journal, which is slower, less auditable and more error prone. Two mistakes are common and must be avoided. The first is to promise same day value for a payment that settles next day, which is a mis-selling of the value date, and the customer who relies on it for a contract deadline will suffer a loss. The second is to book a payment on the instruction date when the value date is later, which overstates the ledger balance and understates the available balance, and the error will appear as a reconciliation break. The correct design is to carry both dates through the payment hub, the core banking system and the statement, to show both to the customer where they differ, and to correct a wrong value date with a camt.087 and a compensating interest entry, not with a silent rebooking. Takeaway: the booking date is when the entry is posted, the value date is when interest starts and funds are considered available, and the two can differ by days. The value date is set by the scheme and the law, and a wrong value date is corrected with a camt.087 and a compensating interest adjustment. State both dates for every payment type and show both where they differ. Further reading: Directive (EU) 2015/2366, PSD2, value date provisions; European Payments Council, SEPA Credit Transfer Rulebook 2025, version 1.1, effective 5 October 2025; ISO 20022, pacs.008 and camt.053 date fields. Last reviewed 7 November 2026.

The value date and the booking date are two different dates for the same payment, and confusing them causes interest errors, reconciliation breaks and customer complaints. The booking date is the date the entry is posted to the account, the date the ledger balance changes. The value date is the date from which interest is calculated, the date the funds are considered to have been available to the holder. For a same day payment the two dates are the same, but for a future dated payment, a back valued payment, a cheque, or a cross-border payment, they can differ by days, and the difference is money. Source: Bank for International Settlements, Committee on Payments and Market Infrastructures; ISO 20022 pacs.008 and camt.053 date fields.

The rules for each date are set by the payment system, the bank and the law, and they must be stated in the product terms. The booking date is set by the bank posting process, and it is usually the date the payment is processed. The value date is set by the scheme or the settlement system, and it is the date the beneficiary bank must make the funds available, subject to cut-offs and non-working days. Under the EU Payment Services Directive, Directive (EU) 2015/2366, the value date for a credit to a payment account must be no later than the business day on which the amount is credited to the payee payment service provider account. These are legal duties, not service aspirations.

A worked example shows the money at stake. A corporate customer instructs a EUR 1 million payment on Friday 6 November 2026, with a value date of Monday 9 November 2026, because the payment is future dated to Monday. A second example is different: a cheque for GBP 50,000 is deposited on Monday, booked on Monday, but the value date is Wednesday, when the cheque clears, so the customer cannot earn interest on the GBP 50,000 for Monday and Tuesday, and cannot withdraw it until Wednesday. A third example is a cross-border payment received on Friday with a value date of Monday, because the nostro account is credited on Monday, and the beneficiary who expected Friday value will complain, and the complaint is about the value date, not the booking date.

The parties and the messages that carry the dates are the debtor agent, the creditor agent and the clearing system, and the ISO 20022 messages carry both dates as separate fields. In a pacs.008 the two dates are separate fields. In a camt.053 statement the booking date and the value date are reported as separate date fields for each entry, so the customer can reconcile interest. In a pain.001 the requested execution date is set by the customer, and the bank must honour it subject to cut-offs, or reject the instruction with a reason. A requirement that maps only one date, or that maps the value date into the booking date field, will produce a statement that cannot be reconciled, and the error will be found by the customer finance team, not by the bank test team.

Failure is a date error, and the remedy is a value-date correction, which is taught in full in ch71s7. A payment booked with the wrong value date causes the wrong interest to be calculated, and the correction is a camt.087 value-date correction message, with a compensating interest adjustment. A payment booked on the wrong date, for example a payment dated for a bank holiday, will be rejected by the clearing system or held until the next working day, and the customer must be told the new value date. A payment with a value date in the future that is never executed, because the instruction was cancelled, must release the hold on the available balance on the cancellation date, not on the value date.

The effect on the bank, the customer and operations is that dates are money. For the bank, the value date decides the interest it pays and receives, the liquidity it must hold, and the reporting it must make, because interest is calculated on value dated balances, not on booked balances. For operations, the booking date and the value date must be reconciled separately: the booking date reconciles against the processing file, and the value date reconciles against the settlement and interest calculations. A product that shows only one date to the customer will generate complaints that operations cannot answer without looking at the underlying message.

For a business analyst, product owner or subject matter expert, the test is to state both dates for every payment type, and to state the rule that sets each one. Ask what the value date is for a same day payment, a future dated payment, a cheque, a direct debit, a card clearing, and a cross-border payment, and ask what happens when the value date falls on a non-working day. Ask how the customer is told the value date, how it appears on the statement, and how a value-date error is corrected, with the message, the timeline and the interest adjustment. The ISO 20022 camt.087 message exists for exactly this correction, and the requirement must name it, or the correction will be done as a manual journal, which is slower, less auditable and more error prone.

Two mistakes are common and must be avoided. The first is to promise same day value for a payment that settles next day, which is a mis-selling of the value date, and the customer who relies on it for a contract deadline will suffer a loss. The second is to book a payment on the instruction date when the value date is later, which overstates the ledger balance and understates the available balance, and the error will appear as a reconciliation break. The correct design is to carry both dates through the payment hub, the core banking system and the statement, to show both to the customer where they differ, and to correct a wrong value date with a camt.087 and a compensating interest entry, not with a silent rebooking.

Takeaway: the booking date is when the entry is posted, the value date is when interest starts and funds are considered available, and the two can differ by days. The value date is set by the scheme and the law, and a wrong value date is corrected with a camt.087 and a compensating interest adjustment. State both dates for every payment type and show both where they differ. Further reading: Directive (EU) 2015/2366, PSD2, value date provisions; European Payments Council, SEPA Credit Transfer Rulebook 2025, version 1.1, effective 5 October 2025; ISO 20022, pacs.008 and camt.053 date fields. Last reviewed 7 November 2026.

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.