| 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
Hands-On Exercise: pain.001 to Canonical Model to pacs.008
What you will learn
Your objective. By the end of this lesson, you will be able to explain hands-on exercise: pain.001 to canonical model to pacs.008. Emma Wilson logs in to Barclays online banking on the morning of 5 November 2026 and creates a new international payment.
Why it matters. This matters because the architecture decides what the bank can build, how fast it can change, and where a payment can fail. Most payment requirements live in the architecture.
Chapter objective: Learner designs a payment data model, including parties, accounts, instructions, transactions, and statuses, and maps fields between a core banking system and ISO 20022 messages. Learner demonstrates this skill using realistic banking examples, explaining each step clearly and using correct terminology throughout.
Key learning points
- Emma Wilson
- Bank creates a canonical record
- Field: validated against reference data
- Payment: then approved
- Debtor agent
- Check that every pacs.008 value
Key terms
Remittance information: Information that explains what a payment is for, such as invoice numbers, contract references or salary month.
Sanctions screening: Checking payment parties, countries and references against sanctions lists published by governments and international bodies.
Execution date: The date on which the bank executes a payment instruction, debiting the debtor account and sending the message onward.
ISO 20022 XML explorer showing Hands-On Exercise: pain.001 to Canonical Model to pacs.008.
Practise this lesson
Exercise
Read the pacs.008 message described in this lesson and identify its key parts.
Use the message structure, fields and example in this lesson.
- What to do. List the three levels of the message and name the field that carries the amount and the field that carries the end-to-end reference.
Correct result. The amount is carried in the instructed amount element and the reference in the end-to-end identification. The three levels are the group header, the payment information, and the credit transfer transaction information.
Why. A message is only useful if you can read it. The group header identifies the message, the payment information identifies the batch, and the transaction information carries the single payment.
Check your understanding
Practice question
Which of the following best describes hands-on exercise: pain.001 to canonical model to pacs.008?
Takeaway and next step
What to remember
If any value cannot be traced, your mapping has a gap.
Open the message type from this lesson and inspect its fields, then find the field that carries the amount.
Open the ISO 20022 Message Explorer →
Builds on "Data Lineage, Retention and Auditability".
Transcript and full text
Show transcript
Emma Wilson logs in to Barclays online banking on the morning of 5 November 2026 and creates a new international payment. She enters the creditor as Schneider GmbH, Musterstrasse 12, 10115 Berlin, Germany, with IBAN DE89 3704 0044 0532 0130 00 at Deutsche Bank, BIC DEUTDEFFXXX. She enters the amount as EUR 8,750.00, the execution date as 6 November 2026, the payment purpose as supplier payment for invoice INV-2026-1147, and the end to end reference as INV-2026-1147. Her debtor account is GB29 NWBK 6016 1331 9268 19, and she confirms the payment with her mobile app. The channel assigns the instruction identifier INSTR-884120 and the time 9 42 in the morning London time. The bank creates a canonical record from her instruction, and that record becomes the single source of truth for the payment. The payment identifier is PAY-2026-1105-004821, the type is customer credit transfer, and the status is received. The debtor is Emma Wilson, GB29 NWBK 6016 1331 9268 19, and the creditor is Schneider GmbH, DE89 3704 0044 0532 0130 00. The instructed amount is EUR 8,750.00, the debtor account currency is GBP, the exchange rate is 0.8482, and the equivalent debit is GBP 7,421.36. The execution date is 2026-11-06, the charge bearer is shared, the fee is GBP 15.00, and the end to end reference is INV-2026-1147. Every field is validated against reference data before the record moves forward. Before release, the canonical record passes through validation, enrichment, and screening. Validation confirms that the IBAN check digits are correct, the amount has two decimal places for EUR, the execution date is a working day, and the purpose code SUPP matches the description. Enrichment confirms the BIC DEUTDEFFXXX from the IBAN, adds the country code DE, and adds the cutoff time of 2 in the afternoon London time for same day value. Sanctions screening checks Emma Wilson, Schneider GmbH, Germany, and the reference INV-2026-1147, and returns no match. The payment is then approved, the status changes to released, and the audit trail records each step with a timestamp and a user or system identifier. The released canonical record is transformed into a pacs.008 message for the next bank in the chain. The message identifier is MSG-2026-1105-004821, the instruction identifier INSTR-884120 is carried in the payment identification, and the end to end reference INV-2026-1147 is carried unchanged so Schneider GmbH can match the payment to its invoice. The debtor is Emma Wilson with account GB29 NWBK 6016 1331 9268 19, the creditor is Schneider GmbH with account DE89 3704 0044 0532 0130 00, the instructed amount is EUR 8,750.00, and the charge bearer is shared. The debtor agent is Barclays, the creditor agent is Deutsche Bank, and the remittance information carries the invoice number. Nothing in the pacs.008 invents a value that was not in the canonical record. Your task is to repeat this walkthrough with your own example and check your work field by field. Choose a different customer, a different creditor country, and a different currency, for example a payment of USD 12,300.00 from a customer in London to a supplier in Singapore. Write down the instruction as the customer enters it, build the canonical record with the payment identifier, debtor account, creditor account, amount and currency, execution date, payment purpose, and end to end reference, and then list each pacs.008 field that your canonical record produces. Check that every pacs.008 value can be traced back to the canonical record, that the amount precision matches the currency, and that the end to end reference is unchanged. If any value cannot be traced, your mapping has a gap.
Emma Wilson logs in to Barclays online banking on the morning of 5 November 2026 and creates a new international payment. She enters the creditor as Schneider GmbH, Musterstrasse 12, 10115 Berlin, Germany, with IBAN DE89 3704 0044 0532 0130 00 at Deutsche Bank, BIC DEUTDEFFXXX. She enters the amount as EUR 8,750.00, the execution date as 6 November 2026, the payment purpose as supplier payment for invoice INV-2026-1147, and the end to end reference as INV-2026-1147. Her debtor account is GB29 NWBK 6016 1331 9268 19, and she confirms the payment with her mobile app. The channel assigns the instruction identifier INSTR-884120 and the time 9 42 in the morning London time.
The bank creates a canonical record from her instruction, and that record becomes the single source of truth for the payment. The payment identifier is PAY-2026-1105-004821, the type is customer credit transfer, and the status is received. The debtor is Emma Wilson, GB29 NWBK 6016 1331 9268 19, and the creditor is Schneider GmbH, DE89 3704 0044 0532 0130 00. The instructed amount is EUR 8,750.00, the debtor account currency is GBP, the exchange rate is 0.8482, and the equivalent debit is GBP 7,421.36. The execution date is 2026-11-06, the charge bearer is shared, the fee is GBP 15.00, and the end to end reference is INV-2026-1147. Every field is validated against reference data before the record moves forward.
Before release, the canonical record passes through validation, enrichment, and screening. Validation confirms that the IBAN check digits are correct, the amount has two decimal places for EUR, the execution date is a working day, and the purpose code SUPP matches the description. Enrichment confirms the BIC DEUTDEFFXXX from the IBAN, adds the country code DE, and adds the cutoff time of 2 in the afternoon London time for same day value. Sanctions screening checks Emma Wilson, Schneider GmbH, Germany, and the reference INV-2026-1147, and returns no match. The payment is then approved, the status changes to released, and the audit trail records each step with a timestamp and a user or system identifier.
The released canonical record is transformed into a pacs.008 message for the next bank in the chain. The message identifier is MSG-2026-1105-004821, the instruction identifier INSTR-884120 is carried in the payment identification, and the end to end reference INV-2026-1147 is carried unchanged so Schneider GmbH can match the payment to its invoice. The debtor is Emma Wilson with account GB29 NWBK 6016 1331 9268 19, the creditor is Schneider GmbH with account DE89 3704 0044 0532 0130 00, the instructed amount is EUR 8,750.00, and the charge bearer is shared. The debtor agent is Barclays, the creditor agent is Deutsche Bank, and the remittance information carries the invoice number. Nothing in the pacs.008 invents a value that was not in the canonical record.
Your task is to repeat this walkthrough with your own example and check your work field by field. Choose a different customer, a different creditor country, and a different currency, for example a payment of USD 12,300.00 from a customer in London to a supplier in Singapore. Write down the instruction as the customer enters it, build the canonical record with the payment identifier, debtor account, creditor account, amount and currency, execution date, payment purpose, and end to end reference, and then list each pacs.008 field that your canonical record produces. Check that every pacs.008 value can be traced back to the canonical record, that the amount precision matches the currency, and that the end to end reference is unchanged. If any value cannot be traced, your mapping has a gap.
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.