Pain.008.001.01 - SDD Core C2B IG 2009 V3.4

The Pain.008.001.01 as described in the SDD Core implementation guidelines – EPC130-08-C2B-Core-DDIG-V3.4-Approved (Published in 2009). Use the search box above the table to find specific information. Back to the payment messages page.

Index	Mult	Message Element	SEPA Core Requirements
1.0	[1..1]	+Group Header
1.1	[1..1]	++Message Identification
1.2	[1..1]	++Creation Date Time
1.3	[0..2]	++Authorisation
1.4	[0..1]	++Batch Booking	Usage Rule: If present and contains ‘TRUE’, batch booking is requested. If present and contains ‘FALSE’, booking per transaction is requested. Usage Rule: If element is not present, pre-agreed customer-to-bank conditions apply.
1.5	[1..1]	++Number Of Transactions
1.6	[0..1]	++Control Sum
1.7	[1..1]	++Grouping	Usage Rule: Only ‘MIXD’ is allowed.
1.8	[1..1]	++Initiating Party
1.8	[0..1]	+++Name
1.8	[0..1]	+++Postal Address
1.8	[0..1]	+++Identification
1.8	{Or	++++Organisation Identification	Format Rule: Only one sub-element of ‘Organisation Identification’ may be present. Usage Rule: This element is not to be used to specify Creditor Scheme Identification.
1.8	Or}	++++Private Identification	Format Rule: Only one occurrence of ‘Private Identification’ may be present. Usage Rule: This element is not to be used to specify Creditor Scheme Identification.
1.8	[0..1]	+++Country of Residence
1.9	[0..1]	++Forwarding Agent
2.0	[1..n]	+Payment Information
2.1	[0..1]	++Payment Information Identification	Usage rule: It is recommended to provide ‘Payment Information Identification’.
2.2	[1..1]	++Payment Method
2.3	[0..1]	++Payment Type Information	Mandatory
2.4	[0..1]	+++Instruction Priority
2.5	{Or	+++Service Level	Mandatory
2.6	{Or	++++Code	(AT-20 The identification code of the Scheme) Usage Rule: Only ‘SEPA’ is allowed.
2.7	Or}	++++Proprietary
2.8	Or}	+++Clearing Channel
2.9	[0..1]	+++Local Instrument	Mandatory
2.10	{Or	++++Code	(AT-20 The identification code of the Scheme) Usage Rule: Only ‘CORE’ is allowed. ‘CORE’ is used to indicate a Core direct debit. Usage Rule: The mixing of Core Direct Debits and Business-to-Business Direct Debits is not allowed in the same message.
2.11	Or}	++++Proprietary
2.12	[0..1]	+++Sequence Type	Mandatory (AT-21 Transaction Type) Usage Rule: If ‘Amendment Indicator’ is ‘TRUE’, and ‘Original Debtor Agent’ is set to ‘SMNDA’, this message element must indicate ‘FRST’.
2.13	[0..1]	+++Category Purpose	(AT-59 Category purpose of the Collection) Usage Rule: Depending on the agreement between the Creditor and the Creditor Bank, ‘Category Purpose’ may be forwarded to the Debtor Bank.
2.14	[1..1]	++Requested Collection Date	(AT-11 Due Date of the Collection)
2.15	[1..1]	++Creditor
2.15	[0..1]	+++Name	Mandatory (AT-03 Name of the Creditor)
2.15	[0..1]	+++Postal Address	(AT-05 Address of the Creditor)
2.15	[0..1]	++++Address Type
2.15	[0..5]	++++Address Line	Usage Rule: Only two occurrences of are allowed.
2.15	[0..1]	++++Street Name
2.15	[0..1]	++++Building Number
2.15	[0..1]	++++Post Code
2.15	[0..1]	++++Town Name
2.15	[0..1]	++++Country Subdivision
2.15	[1..1]	++++Country
2.15	[0..1]	+++Identification
2.15	[0..1]	+++Country of Residence
2.16	[1..1]	++Creditor Account	(AT-04 Account Number of the Creditor).
2.16	[1..1]	+++Identification	Usage Rule: Only IBAN is allowed.
2.16	[0..1]	+++Type
2.16	[0..1]	+++Currency
2.16	[0..1]	+++Name
2.17	[1..1]	++Creditor Agent	Usage Rule: Only BIC is allowed Usage Rule: BIC must be specified as a stand alone element and not part of ‘Combined Identification’.
2.18	[0..1]	++Creditor Agent Account
2.19	[0..1]	++Ultimate Creditor	Usage Rule: This data element may be present either at ‘Payment Information’ or at ‘Direct Debit Transaction Information’ level.
2.19	[0..1]	+++Name	(AT-38 Name of the Creditor Reference Party)
2.19	[0..1]	+++Postal Address
2.19	[0..1]	+++Identification	(AT-39 Identification code of the Creditor Reference Party)
2.19	{Or	++++Organisation Identification	Format Rule: Only one sub-element of ‘Organisation Identification’ may be present.
2.19	Or}	++++Private Identification	Format Rule: Only one occurrence of ‘Private Identification’ may be present.
2.19	[0..1]	+++Country of Residence
2.20	[0..1]	++Charge Bearer	Usage Rule: Only ‘SLEV’ is allowed. Usage Rule: It is recommended that this element be specified at ‘Payment Information’ level.
2.21	[0..1]	++Charges Account
2.22	[0..1]	++Charges Account Agent
2.23	[1..n]	++Direct Debit Transaction Information
2.24	[1..1]	+++Payment Identification
2.25	[0..1]	++++Instruction Identification
2.26	[1..1]	++++End To End Identification	(AT-10 Creditor’s reference of the direct debit Collection)
2.27	[0..1]	+++Payment Type Information
2.38	[1..1]	+++Instructed Amount	(AT-06 Amount of the Collection in Euro) Usage Rule: Only ‘EUR’ is allowed. Usage Rule: Amount must be 0.01 or more and 999999999.99 or less. Format Rule: The fractional part has a maximum of two digits.
2.39	[0..1]	+++Charge Bearer	Usage Rule: Only ‘SLEV’ is allowed.
2.40	[0..1]	+++Direct Debit Transaction	Mandatory
2.41	[0..1]	++++Mandate Related Information	Mandatory
2.42	[0..1]	+++++Mandate Identification	Mandatory (AT-01 Unique Mandate Reference)
2.43	[0..1]	+++++Date Of Signature	Mandatory (AT-25 Date of Signing of the Mandate)
2.44	[0..1]	+++++Amendment Indicator
2.45	[0..1]	+++++Amendment Information Details	(AT-24 Reason for Amendment of the Mandate) Usage Rule: Mandatory if ‘Amendment Indicator’ is ‘TRUE’. The reason code from the Rulebook is indicated using one of the following message sub-elements.
2.46	[0..1]	++++++Original Mandate Identification	(AT-19 Unique Mandate Reference as given by the Original Creditor who issued the Mandate) Usage Rule: Mandatory if changes occur in ‘Mandate Identification’, otherwise not to be used.
2.47	[0..1]	++++++Original Creditor Scheme Identification	Usage Rule: Mandatory if changes occur in ‘Creditor Scheme Identification’ and or ‘Creditor Scheme Name’, otherwise not to be used.
2.47	[0..1]	+++++++Name	(Original AT-03 Name of the Creditor) Usage Rule: If present the new’ Name’ must be specified under ‘Creditor’.
2.47	[0..1]	+++++++Postal Address
2.47	[0..1]	+++++++Identification	(AT-18 Identifier of the original Creditor who issued the Mandate)
2.47	{Or	++++++++Organisation Identification
2.47	Or}	++++++++Private Identification	Usage Rule: Private Identification is used to identify either an organisation or a private person. Usage Rule: ‘Identification Type’ under ‘Other Identification must’ specify ‘SEPA’. Usage Rule: ‘Identification’ under ‘Other Identification’ must be used with an identifier described in General Message Element Specifications, Chapter 1.5.2. Usage Rule: Only one occurrence of ‘Private Identification’ is allowed.
2.47	[0..1]	+++++++Country of Residence
2.48	[0..1]	++++++Original Creditor Agent
2.49	[0..1]	++++++Original Creditor Agent Account
2.50	[0..1]	++++++Original Debtor
2.51	[0..1]	++++++Original Debtor Account	Usage Rule: Only IBAN allowed. Usage Rule: To be used only for changes of accounts within the same bank.
2.52	[0..1]	++++++Original Debtor Agent	Usage Rule: To use ‘Proprietary Identification’ with code ‘SMNDA’ to indicate same mandate with new Debtor Agent. Usage Rule: To be used with the ‘FRST’ indicator in the ‘Sequence Type’.
2.53	[0..1]	++++++Original Debtor Agent Account
2.54	[0..1]	++++++Original Final Collection Date
2.55	[0..1]	++++++Original Frequency
2.56	[0..1]	+++++Electronic Signature	(AT-16 Placeholder for the electronic signature data, if applicable) (AT-17 Type of Mandate (paper, e-Mandate)) (AT-60 Reference of the validation made by the Debtor Bank (if present in DS-03)) Usage Rule: If the direct debit is based on an EPC electronic mandate, this data element must contain AT-60 which is the reference to the Mandate Acceptance Report made by the Debtor Bank. Usage Rule: This element is not to be used if the mandate is a paper mandate.
2.57	[0..1]	+++++First Collection Date
2.58	[0..1]	+++++Final Collection Date
2.59	[0..1]	+++++Frequency
2.60	[0..1]	++++Creditor Scheme Identification	Mandatory Usage Rule: It is recommended that all transactions within the same ‘Payment Information’ block have the same ‘Creditor Scheme Identification’.
2.60	[0..1]	+++++Name
2.60	[0..1]	+++++Postal Address
2.60	[0..1]	+++++Identification	Mandatory (AT-02 Identifier of the Creditor)
2.60	{Or	++++++Organisation Identification
2.60	Or}	++++++Private Identification	Usage Rule: Private Identification is used to identify either an organisation or a private person. Usage Rule: ‘Identification Type’ under ‘Other Identification’ must specify ‘SEPA’. Usage Rule: ‘Identification’ under ‘Other Identification’ is allowed using an identifier described in General Message Element Specifications, Chapter 1.5.2. Usage Rule: Only one occurrence of ‘Private Identification’ is allowed.
2.60	[0..1]	+++++Country of Residence
2.61	[0..1]	++++Pre Notification Identification
2.62	[0..1]	++++Pre Notification Date
2.63	[0..1]	+++Ultimate Creditor	Usage Rule: This data element may be present either at ‘Payment Information’ or at ‘Direct Debit Transaction Information’ level.
2.63	[0..1]	++++Name	(AT-38 Name of the Creditor Reference Party)
2.63	[0..1]	++++Postal Address
2.63	[0..1]	++++Identification	(AT-39 Identification code of the Creditor Reference Party)
2.63	{Or	+++++Organisation Identification	Format Rule: Only one sub-element of ‘Organisation Identification’ may be present.
2.63	Or}	+++++Private Identification	Format Rule: Only one occurrence of ‘Private Identification’ may be present.
2.63	[0..1]	++++Country of Residence
2.64	[1..1]	+++Debtor Agent	(AT-13 BIC of the Debtor Bank) Usage Rule: Only BIC is allowed. Usage Rule: BIC must be specified as a stand alone element and not as part of ‘Combined Identification’.
2.65	[0..1]	+++Debtor Agent Account
2.66	[1..1]	+++Debtor
2.66	[0..1]	++++Name	Mandatory (AT-14 Name of the Debtor)
2.66	[0..1]	++++Postal Address	(AT-09 Address of the Debtor)
2.66	[0..1]	+++++Address Type
2.66	[0..5]	+++++Address Line	Usage Rule: Only two occurrences are allowed.
2.66	[0..1]	+++++Street Name
2.66	[0..1]	+++++Building Numb
2.66	[0..1]	+++++Post Code
2.66	[0..1]	+++++Town Name
2.66	[0..1]	+++++Country Subdivision
2.66	[1..1]	+++++Country
2.66	[0..1]	++++Identification	(AT-27 Debtor identification code)
2.66	{Or	+++++Organisation Identification	Format Rule: Only one sub-element of ‘Organisation Identification’ may be present.
2.66	Or}	+++++Private Identification	Format Rule: Only one occurrence of ‘Private Identification’ may be present.
2.66	[0..1]	++++Country of Residence
2.67	[1..1]	+++Debtor Account	(AT-07 Account Number of the Debtor) Usage Rule: Only IBAN is allowed.
2.68	[0..1]	+++Ultimate Debtor	Usage Rule: Mandatory, if provided by the Debtor in the Mandate.
2.68	[0..1]	++++Name	(AT-15 Name of the Debtor Reference Party)
2.68	[0..1]	++++Postal Address
2.68	[0..1]	++++Identification	(AT-37 Identification code of the Debtor Reference Party)
2.68	{Or	+++++Organisation Identification	Format Rule: Only one sub-element of ‘Organisation Identification’ may be present.
2.68	Or}	+++++Private Identification	Format Rule: Only one occurrence of ‘Private Identification’ may be present.
2.68	[0..1]	++++Country of Residence
2.69	[0..1]	+++Instruction for Creditor Agent
2.70	[0..1]	+++Purpose	(AT-58 Purpose of the Collection)
2.71	{Or	++++Code	Usage Rule: Only codes from the ISO 20022 ExternalPurposeCode list are allowed. See http://www.iso20022.org/Payments_External_Code_Lists.page
2.72	Or}	++++Proprietary
2.73	[0..10]	+++Regulatory Reporting
2.82	[0..1]	+++Tax
2.83	[0..10]	+++Related Remittance Information
2.90	[0..1]	+++Remittance Information	(AT-22 Remittance information from the Creditor) Usage Rule: Either ‘Structured’ or ‘Unstructured’, may be present.
2.91	[0..n]	++++Unstructured	Usage Rule: ‘Unstructured’ may carry structured remittance information, as agreed between the Creditor and the Debtor. Format Rule: Only one occurrence of ‘Unstructured’ is allowed.
2.92	[0..n]	++++Structured	Usage Rule: ‘Structured’ can be used, provided the tags and the data within the ‘Structured’ element do not exceed 140 characters in length. Format Rule: Only one occurrence of ‘Structured’ is allowed.
2.93	[0..1]	+++++Referred Document Information
2.99	[0..1]	+++++Referred Document Related Date
2.100	[0..n]	+++++Referred Document Amount
2.106	[0..1]	+++++Creditor Reference Information	Usage Rule: When present, the Creditor Bank is not obliged to validate the reference information. Usage Rule: When used, both ‘Creditor Reference Type’ and ‘Creditor Reference’ must be present.
2.107	[0..1]	++++++Creditor Reference Type
2.108	{Or	+++++++Code	Usage Rule :Only ‘SCOR’ is allowed.
2.109	Or}	+++++++Proprietary
2.110	[0..1]	+++++++Issuer
2.111	[0..1]	++++++Creditor Reference	Usage Rule: If a Creditor Reference contains a check digit, the receiving bank is not required to validate this. Usage Rule: If the receiving bank validates the check digit and if this validation fails, the bank may continue its processing and send the transaction to the next party in the chain.
2.112	[0..1]	+++++Invoicer
2.113	[0..1]	+++++Invoicee
2.114	[0..1]	+++++Additional Remittance Information

Back to the payment messages page.

PSD2 and The New Generation of Third-Party Providers

June 9, 2020

Differences between SEPA, SWIFT and UK Faster payments

August 26, 2019

SEPA Payments Schemes, Instruments, Initiatives and Messages standards

December 4, 2018

How Corporations use the SWIFT MT101 Request for transfer

October 5, 2018

SWIFT Serial and Cover payments

August 26, 2018

Cookie	Duration	Description
cookielawinfo-checkbox-analytics	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional	11 months	The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
viewed_cookie_policy	11 months	The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.

MOST POPULAR

PSD2 and The New Generation of Third-Party Providers

Differences between SEPA, SWIFT and UK Faster payments

SEPA Payments Schemes, Instruments, Initiatives and Messages standards

How Corporations use the SWIFT MT101 Request for transfer

SWIFT Serial and Cover payments

Contact Us

Useful Links