| 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 collections that share the same creditor, creditor account, collection date and charges bearer. One pain.008 file can hold many payment informa | 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 collection, normally DD for direct debit. It tells the bank which processing channel and clearing system to use. The method must match t | M |
ReqdColltnDt | The date on which the customer asks the bank to collect the direct debit from the debtor account. The bank checks it against cut off times and business days. It | M |
Cdtr | The creditor that will receive the collected funds, with name, postal address and identification. The bank matches the creditor to its customer records and chec | M |
CdtrAcct | The account of the creditor to be credited with the collected funds, identified by IBAN. The bank checks that the account exists and is authorised for direct de | M |
CdtrAgt | The bank holding the creditor account, identified by BIC. It is the bank receiving the pain.008 file. The creditor agent validates the file, checks the mandates | M |
Dbtr | The debtor whose account will be debited, with name, postal address and identification. The bank screens the debtor before collection. Complete debtor data redu | M |
DbtrAcct | The account of the debtor to be debited, identified by IBAN. The bank validates the IBAN format and check digits before accepting the file. A valid IBAN does no | M |
DbtrAgt | The bank holding the debtor account, identified by BIC when known. The customer may leave it blank and let the creditor agent derive it from the debtor IBAN. Ac | O |
MndtRltdInf | The mandate that authorises the creditor to collect direct debits from the debtor account. It carries the mandate identification, date of signature, and the sch | M |
A utility company sends a pain.008 to Harbour Bank with 400 collections for EUR 1,250.00 each, due 6 November 2026, under mandate references starting UTL884120. The control sum matches, every mandate is valid, Harbour accepts the file, and it creates pacs.003 messages to collect each debit from the debtor banks.
Valid example from the message catalogue. Scheme rules: pain.008 is the base ISO 20022 customer direct debit initiation message, and each scheme adds its own rules on top. SEPA Core requires the creditor identifier and gives the debtor an eight week refund
Collections: pain.008 and pacs.003 Step by Step
What you will learn
Your objective. By the end of this lesson, you will be able to explain collections: pain.008 and pacs.003. The collection begins when Stadtwerke Linden creates a pain.008.001.02 Customer Direct Debit Initiation file and sends it to its bank, Harbour Bank Frankfurt.
Why it matters. A creditor that collects without pre-notification gives the debtor grounds to claim a refund, and a business analyst should make the pre-notification step visible in every collection design.
Chapter objective: Mandates, collections, returns and refunds
Key learning points
- Collection begins when Stadtwerke Linden
- Group header
- Pre-notification: available
- Pacs.003 carries the creditor
- Mandate SWL-JW-2026-0417 valid
- Banks record
Key terms
Remittance information: Information that explains what a payment is for, such as invoice numbers, contract references or salary month.
Settlement: The final movement of funds between banks to discharge obligations created by cleared payments. Settlement is usually made in central bank money or through correspondent accounts.
Creditor: The party that is owed money and receives a payment, such as a supplier, a seller or a service provider.
ISO 20022 XML explorer showing Collections: pain.008 and pacs.003 Step by Step.
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
Read the pain.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 main blocks of the message, name the field that carries the amount, and name the field that identifies the payment.
Correct result. The message is made of blocks, each carrying a part of the payment instruction. The amount field and the identification field are the two a receiving bank checks first, because without them it cannot process or reconcile the payment.
Why. A message is only useful if you can read it. The blocks tell the receiving bank what to do, and the amount and identification fields are what it checks first.
Check your understanding
Practice question
Which of the following best describes collections: pain.008 and pacs.003?
Takeaway and next step
What to remember
Both banks record the debit and the credit with the mandate reference and the end to end identification.
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 "e-Mandate Service and Its ISO 20022 Messages".
Transcript and full text
Show transcript
The collection begins when Stadtwerke Linden creates a pain.008.001.02 Customer Direct Debit Initiation file and sends it to its bank, Harbour Bank Frankfurt. The file carries one collection instruction for EUR 89.99, naming Stadtwerke Linden as creditor, Jonas Weber as debtor, the debtor IBAN, the mandate reference SWL-JW-2026-0417, the creditor identifier DE98ZZZ00001234567, the due date of Monday 2 November 2026, and the remittance information naming the October electricity bill. The group header carries the message identification, the creation date and time, one transaction, and a control sum of EUR 89.99. The file must reach Harbour Bank Frankfurt before the SDD cut-off for the due date. Before the collection, the creditor must pre-notify the debtor, and that notice is a scheme rule, not a courtesy. Stadtwerke Linden sends Jonas Weber a pre-notification at least fourteen calendar days before the due date, unless a shorter period was agreed in the mandate, telling him that EUR 89.99 will be collected on Monday 2 November 2026. The pre-notification gives the debtor time to check the amount, to make sure funds are available, and to raise a query if the amount is wrong. A creditor that collects without pre-notification gives the debtor grounds to claim a refund, and a business analyst should make the pre-notification step visible in every collection design. Harbour Bank Frankfurt validates the pain.008 file, checks the creditor identifier and the mandate data, and creates a pacs.003.001.02 FI to FI Customer Direct Debit message for the interbank leg. The pacs.003 carries the creditor and debtor details, the mandate reference, the amount of EUR 89.99, the due date, and the interbank settlement date. It travels through the clearing system to Meridian Bank Munich, the debtor bank. The pacs.003 is the interbank version of the collection, just as the pacs.008 is the interbank version of a credit transfer, and it is the message the debtor bank acts on when the due date arrives. On the due date, Meridian Bank Munich checks the collection against the mandate and the account. It confirms that mandate SWL-JW-2026-0417 is valid, that it has not been cancelled, and that the amount of EUR 89.99 matches the mandate terms. It then checks that the Jonas Weber account holds at least EUR 89.99, and it debits the account on Monday 2 November 2026. The bank sends a pacs.002 status report back through clearing, confirming that the collection was accepted, and it credits the funds through settlement to Harbour Bank Frankfurt, which credits the Stadtwerke Linden account. Both banks record the debit and the credit with the mandate reference and the end to end identification. Worked example with numbers: on 19 October Stadtwerke Linden sends Jonas Weber a pre-notification for the EUR 89.99 collection due on 2 November, at least fourteen calendar days before the due date, as the scheme requires. On 2 November Harbour Bank Frankfurt creates a pacs.003.001.02 for EUR 89.99 and sends it through clearing to Meridian Bank Munich, which checks mandate SWL-JW-2026-0417, confirms it is valid and not cancelled, checks that the account holds at least EUR 89.99, and debits the account. The creditor is credited EUR 89.99, and the collection is complete, with the mandate reference and the end to end identification travelling on every message so that the collection can be traced. Failure and recovery: the collection fails when the pre-notification is missing, when the mandate is invalid, or when the account holds too little. If Stadtwerke Linden forgets the pre-notification, Jonas Weber can claim the collection was not properly notified, and the debtor bank may return it. If the account holds only EUR 40.00 on 2 November, Meridian Bank returns the collection with a pacs.004 and a reason code for insufficient funds, and Stadtwerke Linden must try again next month or ask the customer to pay by another method. The recovery for a missing pre-notification is a new collection with a proper notice, and the recovery for insufficient funds is a retry in the next cycle, but both cost a month. For a business analyst, product owner or subject matter expert, the collection requirement must state the pre-notification rule, fourteen calendar days unless a shorter period was agreed, and must state the messages, pain.008 from the creditor to its bank and pacs.003 between banks. The requirement must also state the checks the debtor bank runs on the due date, mandate valid, mandate not cancelled, amount matches the mandate terms, and account holds enough funds. The test pack must include a collection on the due date, a collection with a missing pre-notification, and a collection with insufficient funds, because each case exercises a different rule. Source: EPC SDD Core Rulebook 2025; last reviewed 7 November 2026.
The collection begins when Stadtwerke Linden creates a pain.008.001.02 Customer Direct Debit Initiation file and sends it to its bank, Harbour Bank Frankfurt. The file carries one collection instruction for EUR 89.99, naming Stadtwerke Linden as creditor, Jonas Weber as debtor, the debtor IBAN, the mandate reference SWL-JW-2026-0417, the creditor identifier DE98ZZZ00001234567, the due date of Monday 2 November 2026, and the remittance information naming the October electricity bill. The group header carries the message identification, the creation date and time, one transaction, and a control sum of EUR 89.99. The file must reach Harbour Bank Frankfurt before the SDD cut-off for the due date.
Before the collection, the creditor must pre-notify the debtor, and that notice is a scheme rule, not a courtesy. Stadtwerke Linden sends Jonas Weber a pre-notification at least fourteen calendar days before the due date, unless a shorter period was agreed in the mandate, telling him that EUR 89.99 will be collected on Monday 2 November 2026. The pre-notification gives the debtor time to check the amount, to make sure funds are available, and to raise a query if the amount is wrong. A creditor that collects without pre-notification gives the debtor grounds to claim a refund, and a business analyst should make the pre-notification step visible in every collection design.
Harbour Bank Frankfurt validates the pain.008 file, checks the creditor identifier and the mandate data, and creates a pacs.003.001.02 FI to FI Customer Direct Debit message for the interbank leg. The pacs.003 carries the creditor and debtor details, the mandate reference, the amount of EUR 89.99, the due date, and the interbank settlement date. It travels through the clearing system to Meridian Bank Munich, the debtor bank. The pacs.003 is the interbank version of the collection, just as the pacs.008 is the interbank version of a credit transfer, and it is the message the debtor bank acts on when the due date arrives.
On the due date, Meridian Bank Munich checks the collection against the mandate and the account. It confirms that mandate SWL-JW-2026-0417 is valid, that it has not been cancelled, and that the amount of EUR 89.99 matches the mandate terms. It then checks that the Jonas Weber account holds at least EUR 89.99, and it debits the account on Monday 2 November 2026. The bank sends a pacs.002 status report back through clearing, confirming that the collection was accepted, and it credits the funds through settlement to Harbour Bank Frankfurt, which credits the Stadtwerke Linden account. Both banks record the debit and the credit with the mandate reference and the end to end identification.
Worked example with numbers: on 19 October Stadtwerke Linden sends Jonas Weber a pre-notification for the EUR 89.99 collection due on 2 November, at least fourteen calendar days before the due date, as the scheme requires. On 2 November Harbour Bank Frankfurt creates a pacs.003.001.02 for EUR 89.99 and sends it through clearing to Meridian Bank Munich, which checks mandate SWL-JW-2026-0417, confirms it is valid and not cancelled, checks that the account holds at least EUR 89.99, and debits the account. The creditor is credited EUR 89.99, and the collection is complete, with the mandate reference and the end to end identification travelling on every message so that the collection can be traced.
Failure and recovery: the collection fails when the pre-notification is missing, when the mandate is invalid, or when the account holds too little. If Stadtwerke Linden forgets the pre-notification, Jonas Weber can claim the collection was not properly notified, and the debtor bank may return it. If the account holds only EUR 40.00 on 2 November, Meridian Bank returns the collection with a pacs.004 and a reason code for insufficient funds, and Stadtwerke Linden must try again next month or ask the customer to pay by another method. The recovery for a missing pre-notification is a new collection with a proper notice, and the recovery for insufficient funds is a retry in the next cycle, but both cost a month.
For a business analyst, product owner or subject matter expert, the collection requirement must state the pre-notification rule, fourteen calendar days unless a shorter period was agreed, and must state the messages, pain.008 from the creditor to its bank and pacs.003 between banks. The requirement must also state the checks the debtor bank runs on the due date, mandate valid, mandate not cancelled, amount matches the mandate terms, and account holds enough funds. The test pack must include a collection on the due date, a collection with a missing pre-notification, and a collection with insufficient funds, because each case exercises a different rule. Source: EPC SDD Core Rulebook 2025; 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.