| Field | Meaning | Required |
|---|---|---|
GrpHdr | The header with message identification, creation date and time, number of transactions, control sum and initiating party. It identifies the file for the bank an | M |
PmtInf | A block grouping payments that share the same debtor, debtor account, execution date and charges bearer. One pain.001 file can hold many payment information blo | M |
PmtInfId | A unique identification for the payment information block, assigned by the customer. It lets the customer and the bank refer to the whole block in status report | M |
PmtMtd | The method used for the payment, normally TRF for a credit transfer, TRA for a transfer advice or CHK for a cheque. TRF is the standard value for a bank credit | M |
ReqdExctnDt | The date on which the customer asks the bank to execute the payment. The bank checks it against cut off times and business days and may move it to the next busi | M |
Dbtr | The customer ordering the payment, with name, postal address and identification. The bank matches the debtor to its customer records and checks signing authorit | M |
DbtrAcct | The account from which the payment is debited, identified by IBAN or other account identification. The bank checks that the account exists, has sufficient funds | M |
DbtrAgt | The bank holding the debtor account, identified by BIC. It is the bank receiving the pain.001 file. The debtor agent validates the file, screens the payments an | M |
CdtrAgt | The bank holding the creditor account, identified by BIC when known. The customer may leave it blank and let the debtor agent derive it from the creditor IBAN. | O |
Cdtr | The beneficiary of the payment, with name, postal address and identification. The bank screens the creditor against sanctions and fraud lists before execution. | M |
CdtrAcct | The account to be credited, identified by IBAN or other account identification. The bank validates the IBAN format and check digits before accepting the file. A | M |
Amt | The amount and currency of the individual credit transfer, for example EUR 10,000. It is the amount the creditor receives before any charges. The sum of the amo | M |
Northgate Trading sends a pain.001 file to Meridian Bank London with one payment information block for 48 supplier payments totalling EUR 120,000, requested execution date 6 November 2026, charge bearer SLEV. The bank validates the file, debits the Northgate account, and reports acceptance in a pain.002.
Valid example from the message catalogue. Scheme rules: pain.001 is a base ISO 20022 message: the structure and fields below are the base definition, and each scheme adds its own rules for its rail. Under SEPA SCT the IBAN is mandatory for debtor and credi
Cut-Off Management and Processing Calendars
What you will learn
Your objective. By the end of this lesson, you will be able to explain cut-off management and processing calendars. A cut-off time is the last moment a payment instruction can be accepted for processing on a given value date.
Why it matters. A customer who submits a payment of 500,000 pounds at 5 past 5 in the afternoon for CHAPS will therefore see a value date of the next working day, even though the money leaves the account immediately.
Chapter objective: Learner explains payment operations, including daily processing, cut-offs, monitoring, incident handling, and reporting, and builds a daily operations checklist for a payment team. Learner demonstrates this skill using realistic banking examples, explaining each step clearly and using correct terminology throughout.
Key learning points
- Cut-off time
- Operations must apply these times exactly
- Hub reads these calendars automatically when it
- Pain.001 file with 12,000 payments worth 18
- Operations team
Key terms
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.
Value date: The date on which funds become available to the beneficiary and on which interest starts to accrue. It is the date used for settlement and for nostro posting.
Exception: A payment that cannot be processed normally and needs manual handling, investigation or repair. Exceptions arise from missing data, failed screening, account errors or system faults.
ISO 20022 XML explorer showing Cut-Off Management and Processing Calendars.
Insights and practice scenarios
Worked insights and practice scenarios for this lesson. Each one is a reusable PaymentForge case, so the same case may appear in more than one lesson.
Practise this lesson
Exercise
Investigate the reconciliation break described in this lesson and find its root cause.
Use the three-way matching rule and the break categories in this lesson.
- What to do. Compare the instruction, the settlement record and the statement, name the break type, and state the corrective action.
Correct result. A break is found by matching amount, currency, date and reference across the three sources. The root cause is a timing difference, an amount difference, a missing entry, or a duplicate, and the corrective action follows the cause.
Why. Reconciliation is the last line of defence. A break that is not investigated is money that cannot be proved.
Check your understanding
Practice question
A payment operations team receives an email that looks like it is from the central bank, asking an operator to approve an urgent payment through a link. What should the operator do?
Takeaway and next step
What to remember
Fourth, the incident is logged so the bank can see whether one channel repeatedly sends payments after the cut-off and needs a reminder or a system fix.
Reconcile the payment in this lesson against its statement and find the break.
Open the Accounting and Reconciliation Lab →
Builds on "A Day in Payment Operations".
Transcript and full text
Show transcript
A cut-off time is the last moment a payment instruction can be accepted for processing on a given value date. After the cut-off, the instruction is either held for the next processing day or rejected back to the channel with a clear message. For CHAPS in the United Kingdom, the customer cut-off is often 5 in the afternoon and the bank to bank cut-off is 6 in the evening, while for Fedwire in the United States the closing time is half past 6 in the evening Eastern Time. A customer who submits a payment of 500,000 pounds at 5 past 5 in the afternoon for CHAPS has missed the bank customer cut-off, so the payment is held for the next working day and is not settled that day; whether the customer account is debited immediately is a bank practice, not settlement, and the value date is the next working day. Source: Bank of England CHAPS operating hours and cut-off practice. Operations must apply these times exactly, because one late release can breach a contract. Processing calendars are the reference tables that tell the payment hub which days are working days for each currency and each clearing system. A payment in euros follows the T2 calendar, which is closed on New Year Day, Good Friday, Easter Monday, 1 May, Christmas Day and 26 December. A payment in US dollars follows the United States federal holiday calendar, which closes Fedwire on Thanksgiving and Independence Day. A payment from London to Tokyo must respect both the United Kingdom calendar and the Japanese calendar, because the beneficiary bank in Tokyo cannot credit an account on a Japanese public holiday. The hub reads these calendars automatically when it sets the value date. Weekends create a regular pattern that operations teams plan around every week. On a Friday afternoon, the volume of payments rises sharply as companies pay suppliers before the weekend and customers send money home. A bank may process 2.4 million payments on a Friday compared with 1.9 million on a Tuesday, and the team adds extra staff to the exception queue to cope. On a Monday morning, the team faces the payments that arrived over the weekend through Faster Payments and the standing orders due on Monday, plus the files that corporate customers uploaded on Sunday evening. A pain.001 file with 12,000 payments worth 18 million pounds may be waiting at 6 in the morning on Monday. Public holidays in different countries cause the most confusion, because a payment can be a working day in one country and a holiday in another. A payment of 750,000 US dollars from a customer in London to a supplier in Hong Kong on the day of the Chinese New Year holiday will be held by the correspondent bank in Hong Kong until the next working day. The sending bank must warn the customer at the point of instruction, not after the payment is stuck. Good banks publish a holiday calendar for each currency on their website and in their corporate portal, and the payment hub uses the same calendar to calculate the value date automatically so the customer sees the correct date before confirming. When a cut-off is missed, the operations team follows a clear procedure instead of improvising. First, the analyst checks the value date on the instruction and confirms whether the customer asked for same day value or accepted next day value. Second, the team checks whether an alternative rail is still open, for example sending a euro payment through Faster Payments is never possible, because Faster Payments is a sterling-only system; a euro payment must use a euro rail such as SEPA Instant, whatever the amount. Source: Pay.UK, Faster Payments is a sterling system. Third, the team contacts the customer with the new value date and the reason for the delay. Fourth, the incident is logged so the bank can see whether one channel repeatedly sends payments after the cut-off and needs a reminder or a system fix.
A cut-off time is the last moment a payment instruction can be accepted for processing on a given value date. After the cut-off, the instruction is either held for the next processing day or rejected back to the channel with a clear message. For CHAPS in the United Kingdom, the customer cut-off is often 5 in the afternoon and the bank to bank cut-off is 6 in the evening, while for Fedwire in the United States the closing time is half past 6 in the evening Eastern Time. A customer who submits a payment of 500,000 pounds at 5 past 5 in the afternoon for CHAPS has missed the bank customer cut-off, so the payment is held for the next working day and is not settled that day; whether the customer account is debited immediately is a bank practice, not settlement, and the value date is the next working day. Source: Bank of England CHAPS operating hours and cut-off practice. Operations must apply these times exactly, because one late release can breach a contract.
Processing calendars are the reference tables that tell the payment hub which days are working days for each currency and each clearing system. A payment in euros follows the T2 calendar, which is closed on New Year Day, Good Friday, Easter Monday, 1 May, Christmas Day and 26 December. A payment in US dollars follows the United States federal holiday calendar, which closes Fedwire on Thanksgiving and Independence Day. A payment from London to Tokyo must respect both the United Kingdom calendar and the Japanese calendar, because the beneficiary bank in Tokyo cannot credit an account on a Japanese public holiday. The hub reads these calendars automatically when it sets the value date.
Weekends create a regular pattern that operations teams plan around every week. On a Friday afternoon, the volume of payments rises sharply as companies pay suppliers before the weekend and customers send money home. A bank may process 2.4 million payments on a Friday compared with 1.9 million on a Tuesday, and the team adds extra staff to the exception queue to cope. On a Monday morning, the team faces the payments that arrived over the weekend through Faster Payments and the standing orders due on Monday, plus the files that corporate customers uploaded on Sunday evening. A pain.001 file with 12,000 payments worth 18 million pounds may be waiting at 6 in the morning on Monday.
Public holidays in different countries cause the most confusion, because a payment can be a working day in one country and a holiday in another. A payment of 750,000 US dollars from a customer in London to a supplier in Hong Kong on the day of the Chinese New Year holiday will be held by the correspondent bank in Hong Kong until the next working day. The sending bank must warn the customer at the point of instruction, not after the payment is stuck. Good banks publish a holiday calendar for each currency on their website and in their corporate portal, and the payment hub uses the same calendar to calculate the value date automatically so the customer sees the correct date before confirming.
When a cut-off is missed, the operations team follows a clear procedure instead of improvising. First, the analyst checks the value date on the instruction and confirms whether the customer asked for same day value or accepted next day value. Second, the team checks whether an alternative rail is still open, for example sending a euro payment through Faster Payments is never possible, because Faster Payments is a sterling-only system; a euro payment must use a euro rail such as SEPA Instant, whatever the amount. Source: Pay.UK, Faster Payments is a sterling system. Third, the team contacts the customer with the new value date and the reason for the delay. Fourth, the incident is logged so the bank can see whether one channel repeatedly sends payments after the cut-off and needs a reminder or a system fix.
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.