SEPA Direct Debit Creditor's interface specification - Nets

SEPA Direct DebitCreditor’s interface specification

Document HistoryVersion Date Systemeffective dateChanges1.0 06.12.2010 01.11.2010 Version for rulebook 4.01.1 10.06.2011 19.11.2011 Version for rulebook 5.0Mandate Id has new rules for case insensitive contentNew reason code BE05 for Rejects and Returns1.2 08.03.2012 19.11.2012 Version for rulebook 6.0SDD B2B only: new reason code AC13 is introduced forRejects/Returns. AC13 – Debtor is a ConsumerSDD CORE and B2B: Extended time line for the reversalsfrom 2 to 5 business daysCreditor ID is Space and Case insensitive1.3 15-01-2014 01-02-2014 Version for rulebook 7.0SDD CORE only: new reason code FF05 is introduced forRejects/Returns. FF05-Direct Debit type incorrect (COREonly)Added new reason codes CNOR and DNORi

ReferencesThis section lists relevant documents of interest.Ref.DocumentNumberTitleIssued by1 Payment_ExternalCodeLists_09June09_v5.xls ISO2 SEPA Creditor user and information guide.docx Netsii

Contents1 Introduction .......................................................................................................................... 41.1 Pre notes .......................................................................................................................................... 41.2 Purpose ............................................................................................................................................ 41.3 Creditor’s User Guide ...................................................................................................................... 41.4 Abbreviations and definitions ......................................................................................................... 42 Description of the tables in Appendix A ..................................................................................... 52.1 Meaning of the colors in the tables ................................................................................................. 52.2 Nets specific rules ............................................................................................................................ 52.3 For R-transactions specifically ......................................................................................................... 52.4 Detailed description of data elements ............................................................................................ 63 Appendix A - Nets message description .................................................................................... 73.1 PAIN.008.001.02PBS Customer payment collection file ................................................................. 73.2 PAIN.007.001.02PBS Customer payment reversal file .................................................................. 613.3 CAMT.055.001.01PBS Customer payment cancellation file .......................................................... 873.4 PAIN.002.001.03 Customer counterparty reject file (Status file) ................................................ 1253.5 PAIN.002.001.03 Customer bookkeeping file ............................................................................. 1543.6 PAIN.002.001.03 Customer input acknowledgement file ........................................................... 1814 Appendix B – Message item types ........................................................................................ 2114.1 Organisation identification codes used in Creditor Debit collection (pain.008), cancellation(camt.055) and reversal (pain.007) request. ........................................................................................ 2114.2 Private identification codes used in Creditor Debit collection (pain.008), cancellation (camt.055)and reversal (pain.007) request. .......................................................................................................... 2114.3 Sequence type ............................................................................................................................. 2124.4 Creditor Reference Type used in Structure Remittance Information ......................................... 2124.5 Reversal reason codes ................................................................................................................. 2134.6 Cancellation reason code (used in Camt.055.001.01PBS) ........................................................... 2134.7 Status reason code used in customer counter party reject file .................................................. 2134.8 Detailed status code used in input acknowledgement file ......................................................... 2154.9 Purpose codes used in the Creditor sending payment collections. ............................................ 2165 Appendix C - Error code reference list................................................................................... 2325.1 Bulk level error codes .................................................................................................................. 2325.2 Transaction level error codes ...................................................................................................... 2325.3 Transaction level status codes for bookkeeping file ................................................................... 2355.4 File level codes ............................................................................................................................ 2366 Appendix D – Schema XML files ........................................................................................... 2377 Appendix E – Sample XML files ............................................................................................ 238iii

1 Introduction1.1 Pre notesThis document is the final version for SEPA Direct Debit CORE rulebook version 7.0 and SEPA Direct DebitB2B rulebook version 5.0.Please be aware, that updates and changes to the rulebooks are released annually by the EPC (EuropeanPayments Council). Updates to this Interface Specification can be found on www.nets.eu.1.2 PurposeThe purpose of this document is to describe the file formats used between Nets and SEPA creditors.1.3 Creditor’s User GuideThis interface description document does not provide the reader with detailed information regarding theSEPA schemes, scheme rules, timelines etc. It’s recommended that the reader is familiar with thecreditor’s user and information guide before studying this document.This document only brings an overview to introduce the messages in the SEPA system.1.4 Abbreviations and definitionsLikewise, please refer to Creditor’s User Guide for a list of abbreviations and definitions.Page 4 of 232

2 Description of the tables in Appendix AThe data elements that are used in Nets’ messages are described in the appendixes. They are based onthe ISO20022 standards, but they do not allow all fields and options available within the ISO20022standard.The general rules of describing data elements are listed in the “Detailed description of data elements”section below.2.1 Meaning of the colors in the tablesEach PAIN and CAMT is described in record layout tables. The fields of these tables are defined on thebasis of the ISO 20022 schema, which acts as the superset, and the SEPA Direct Debit rulebook(including implementation guidelines), which acts as the subset.Fields in this colour (yellow) are supported by Nets, and can be either mandatory or optional.This colour (light yellow) represents light parent tag fields used by Nets; they can be either mandatory oroptional. They do not contain any values, but they contain one or more yellow sub-tags that are used byNets.This colour (orange) represents R-transaction fields or amendment fields used by Nets; they can beeither mandatory or optional. The fields contain matching fields which have the same value as theoriginal transaction. These fields consist of tags and sub-tags as appropriate with regards to the originaltransaction. They refer to different groups of pain.008 fields. Data about the debtor (name, address, IDetc.) is e.g. only described in one field, as the whole group of debtor fields contains the same data aspain.008.Only these coloured fields can be used in Nets’ SDD system.Fields without colour (white fields) are not used, and they are not forwarded to the debtor by Nets’ SDDservice even though they adhere to ISO20022 standards.2.2 Nets specific rulesPlease note that some fields are mandatory even though these fields are not mandatory in the ISO andEPC implementation guidelines and even if they are not stated as mandatory in the XSD.2.3 For R-transactions specificallyThe R-transaction (camt.055 and pain.007) will contain fields that hold data from the original Direct Debit(orange fields). These fields will refer to different groups of data from pain.008. The mandatory fields arelisted in these fields and the optional fields can be found by looking at the referred section.Page 5 of 232

2.4 Detailed description of data elementsTable headingXML elementFormatDescriptionThe ISO20022 XML tag name used to identify the field. If the field is nestedunder other tags, the nesting is shown as a new line under the outer tag name.The expected format of the field:4a - four alpha characters (capital)4n - four digits4x – four characters4c – four alphanumerical characters (capital letters)4!a – must be four alpha characters (and no less than four) in capital letters[3x] – three optional charactersISODate – YYYY-MM-DDISODateTime - YYYY-MM-DDThh:mm:ssSee Schema – the format has to be seen in the linked schema.StatusField status can be1-1 – mandatory for Nets, only one occurrence allowed.1-n – mandatory for Nets, no specified limit to the number of occurrences.0-1 – optional, only one occurrence allowed.0-n – optional, no specified limit to the number of occurrences.{Or, Or} - either field 1 or field 2 must be present, but not both.Rule book referenceDescription / validationrulesIn case the data element exists in the SEPA Direct Debit Rulebook, a crossreferencehas been given. Nets have added this reference, in order to clarify theconnection between the Rulebook fields in Direct Debit and R-transactions.This column gives a description of the field or details about the validation thatwill be performed in the field.First, a schema validation is carried out, and then subsequent checks areperformed as per the content of the fields.Description / validation rules are present in formats which are sent from thecreditor to NetsPage 6 of 232

3 Appendix A - Nets message description3.1 PAIN.008.001.02PBS Customer payment collection file3.1.1 Payment collection (Direct Debit initiation) – group headerXML element Format Status Rulebookref.Description / validation rules3.1.1.1GrpHdr See Schema 1-1 NA Group HeaderContains common information about the payment.3.1.1.2GrpHdrMsgId35x 1-1 NA Message IdentificationThe creditor’s unique file reference is created by creditor as defined in Section“Description of specific XML tags” in the document Creditor’s user and informationguide to SEPA Direct DebitThe uniqueness of the message ID, which is created by creditor, is checked in Nets’SDD system.The identification cannot include leading, trailing or internal spacesLength: 1-35.Content: "([A-Za-z0-9]|[\?|/|\-|:|\(|\)|\.|,|'])"E.g.: M12345678PAIN008COR2009111200000001Page 7 of 232

XML element Format Status Rulebookref.Description / validation rules3.1.1.3GrpHdrCreDtTmISODate&Time1-1 NA Creation Date TimeThe date and time when the file was created by the creditor.E.g.: 2009-11-19T08:30:473.1.1.43.1.1.5GrpHdrAuthstnGrpHdrNbOfTxs128x 0-2 NA AuthorisationNot used by Nets.15n 1-1 NA Number of TransactionsThe number of transactions included in the file.Schema validationMust be the total number of transactions included in the file.3.1.1.6GrpHdrCtrlSumLength: 1-15. Content: "[0-9]{1,15} ".E.g.: 2Decimal 0-1 NA Control SumThe sum of all transactions listed in this file.Maximum length: 18 digitsMaximum number of fractional digits: 17 digitsE.g.: 1.50Page 8 of 232

XML element Format Status Rulebookref.Description / validation rules3.1.1.73.1.1.83.1.1.93.1.1.10GrpHdrInitgPtyGrpHdrInitgPtyNmGrpHdrInitgPtyPstlAdrGrpHdrInitgPtyIdSee Schema 1-1 NA Initiating Party70x 0-1 NA NameSee Schema 0-1 NA Postal addressSee Schema 0-1 NA IdentificationIndicates the information about the creditor who initiated the payment i.e. his/heraddress and identification details.Name by which creditor is known as well as the name that is used to identify the creditor whoinitiated the payment.E.g.: Peter Soerensen Eftf. A/SThis field and its underlying fields are not used by Nets.Contains one of the subfields which are used to indicate the organisation identificationor private identification of the creditor.3.1.1.11GrpHdrInitgPtyIdOrgIdSee Schema {Or NA Organisation IdentificationUnique and unambiguous way to identify the creditor’s organisation.It cannot be used at the same time as Id/PrvtId (below)If schmeNm/Cd is used, one of the values in table 4.1 Organisation identificationmust be filled out.Note:- This element not to be used to specify creditor scheme identification.Page 9 of 232

XML element Format Status Rulebookref.Description / validation rules3.1.1.123.1.1.133.1.1.14GrpHdrInitgPtyIdPrvtIdGrpHdrInitgPtyCtryOfResGrpHdrFwdgAgtSee Schema Or} NA Private Identification2!a 0-1 NA Country of ResidenceUnique and unambiguous identification of a creditor, e.g. passport.It cannot be used at the same time as Id/OrgId (above)If schmeNm/Cd is used, one of the values in table 4.2 Private identification must befilled out.Note: This element not to be used to specify creditor scheme identification.Not used by Nets.See Schema 0-1 NA Forwarding AgentNot used by Nets.Page 10 of 232

3.1.2 Payment collection (debit initiation) – payment informationXML Element Format Status Rulebookref.Description / validation rules3.1.2.1PmtInfSeeSchema1-n NA Payment InformationContains the set of fields that applies to the creditor’s side of the paymenttransaction that is included in the direct debit transaction initiation.3.1.2.2PmtInfPmtInfId35x 1-1 NA Payment information identificationNets Unique identification assigned by the creditor to unambiguously identifythe Instruction.Length: 1-35.Content: "([A-Za-z0-9]|[\?|/|\-|:|\(|\)|\.|,|'])"E.g.: P12345678PAIN008COR20091112000000013.1.2.3PmtInfPmtMtdString 1-1 NA Payment MethodSpecifies the means of payment that must be used to move the amount ofmoney.It must contain the value “DD” – schema validation.‘DD’ – Direct DebitE.g.: DDPage 11 of 232

XML Element Format Status Rulebookref.Description / validation rules3.1.2.43.1.2.53.1.2.6PmtInfBtchBookgPmtInfNbOfTxsPmtInfCtrlSumBoolean 0-1 NA Batch Booking15n 0-1 NA Number of TransactionsIdentifies whether a single entry per individual transaction or a batch entryfor the sum of the amounts of all transactions within the group of a messageis requested.Usage: Batch booking is used to request and not order a possible batchbooking.Number of individual transactions contained in the message.Schema validation Must be the total number of transactions included in the file.Length: 1-15. Content: "[0-9]{1,15} ".E.g.: 2Decimal 0-1 NA Control SumThe sum of all transactions listed in this file.Maximum length: 18 digitsMaximum number of fractional digits: 17 digitsE.g.: 1.503.1.2.7PmtInfPmtTpInfSeeSchema1-1 NA Payment Type InformationContains the fields that further specify the transaction type.Page 12 of 232

XML Element Format Status Rulebookref.Description / validation rules3.1.2.8PmtInfPmtTpInfInstrPrtyString 0-1 NA Instruction PriorityNot used by Nets.3.1.2.9PmtInfPmtTpInfSeeSchema1-1 NA Service LevelAgreement/rules under which the transaction should be processed.SvcLvl3.1.2.10PmtInfPmtTpInfSeeSchema1-1 AT-20 CodeSpecifies the pre-agreed service or level of service between the parties.SvcLvlThe identification code of the schemecdUsage rule: Only ‘SEPA’ is allowed.E.g.: SEPA3.1.2.11PmtInfPmtTpInfSeeSchema1-1 NA Local InstrumentContains the information that specifies the service level of the payment.LclInstrmPage 13 of 232

XML Element Format Status Rulebookref.Description / validation rules3.1.2.12PmtInfPmtTpInfSeeSchema1-1 AT-20 CodeIndicates the transaction type.LclInstrmcdAllowed values are:B2B – if the transaction is a Business to Business DD.CORE – if the transaction is a Core DD.Usage rule: The mixing of Core Direct Debits and Business-to-Business DirectDebits is not allowed in the same message file.E.g.: B2B3.1.2.13PmtInfPmtTpInfSeqTpSeeSchema1-1 AT-21 Sequence TypeIdentifies the Direct Debit sequence. See a complete list of sequence types insection 4.3E.g.: FRST.Note: The valid sequence type must be filled out at the transaction level. Thepayment information sequence type is insignificant.This means that a file may contain transactions and each of them may have adifferent sequence type.3.1.2.14PmtInfPmtTpInfSeeSchema0-1 AT-59 Category Purpose of all TransactionsNot used by Nets.CtgyPurpPage 14 of 232

XML Element Format Status Rulebookref.Description / validation rules3.1.2.15PmtInfReqdColltnDtISO Date 1-1 AT-11 Requested Collection DateDate at which the creditor requests the amount of money, to be collectedfrom the debtor.Due date of the collection:Must be a target dayA B2B collection must be received no later than one target day beforedue date and not earlier than 14 calendar days before due date.A CORE collection must be received no later than five target days beforedue date for first payment, two target days before due date for recursiveand final payments and not earlier than 14 calendar days before duedate.Length: 10.Content: ISO Date (YYYY-MM-DD) e.g. 2008-05-133.1.2.16PmtInfCdtrSeeSchema1-1 AT-03 CreditorParty to which the amount of money is due.3.1.2.17PmtInfCdtrNm70x 1-1 AT-03 Name of the CreditorName by which a creditor is known as well as the name that is usually usedto identify the creditor that initiated the payment.Length: 1-70.Content: TextE.g.: Nets Holding A/S.Page 15 of 232

XML Element Format Status Rulebookref.Description / validation rules3.1.2.18PmtInfCdtrPstlAdrSeeSchema0-1 AT-05 Postal Address of the creditorInformation that locates and identifies the address of the creditor whoinitiated the payment, as defined by postal services.3.1.2.19PmtInfCdtrSeeSchema0-1 AT-05 Address Type of the creditorNot used by Nets.PstlAdrAdrTp3.1.2.203.1.2.213.1.2.22PmtInfCdtrPstlAdrStrtNmPmtInfCdtrPstlAdrBldgNbPmtInfCdtrPstlAdrPstCd70x 0-1 AT-05 Street Name of the creditorNot used by Nets.16x 0-1 AT-05 Building Number of the creditorNot used by Nets.16x 0-1 AT-05 Postal Code of the creditorNot used by Nets.Page 16 of 232

XML Element Format Status Rulebookref.Description / validation rules3.1.2.233.1.2.243.1.2.25PmtInfCdtrPstlAdrTwnNmPmtInfCdtrPstlAdrCtrySubDvsnPmtInfCdtrPstlAdrCtry35x 0-1 AT-05 Town Name of the creditorNot used by Nets.35x 0-1 AT-05 Country Sub Division of the creditorNot used by Nets.2!a 0-1 AT-05 Country of the CreditorMust be a valid country code according to ISO3166.Mandatory if address line is used, otherwise not used.Length: 2.Content: Valid country codeE.g.: DKPage 17 of 232

XML Element Format Status Rulebookref.Description / validation rules3.1.2.26PmtInfCdtrPstlAdrAdrLine70x 0-2 AT-05 Address Line of the creditorAddress line can have a maximum of two occurrences:Length: 1-70Content: Text.For allowed content refer to section “Addresses” in the document Creditor’suser and information guide to SEPA Direct DebitE.g.: Lautrupbjerg 10, 2750 Ballerup.3.1.2.27PmtInfCdtrSeeSchema0-1 NA Identification of the creditorNot used by Nets.Id3.1.2.28PmtInfCdtrCtryOfRes2!a 0-1 NA Country of ResidenceNot used by Nets.3.1.2.29PmtInfCdtrAcctSeeSchema1-1 AT-04 Creditor AccountUnambiguous identification of the creditor’s account to which a credit entryhas been posted as a result of the payment transaction.Page 18 of 232

XML Element Format Status Rulebookref.Description / validation rules3.1.2.30PmtInfCdtrAcctIdSeeSchema1-1 AT-04 Identification of Creditor AccountUnique and unambiguous identification of creditor’s account and the financialinstitution that services creditor.3.1.2.31PmtInfCdtrAcctIdIBANString 1-1 AT-04 IBAN of Creditor AccountMaximum length: 34Format rule: [a-zA-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}E.g.: DK10520100096712083.1.2.32PmtInfCdtrAcctSeeSchema0-1 NA Type of Creditor AccountNot used by Nets.Tp3.1.2.333.1.2.34PmtInfCdtrAcctCcyPmtInfCdtrAcctNm3x 0-1 NA Currency of Creditor AccountNot used by Nets.70x 0-1 NA Name of the creditor AccountNot used by Nets.3.1.2.35PmtInfCdtrAgtSeeSchema1-1 AT-12 Creditor AgentFinancial institution servicing an account for the creditor (creditor bank).Page 19 of 232

XML Element Format Status Rulebookref.Description / validation rules3.1.2.36PmtInfCdtrAgtFinInstnIdSeeSchema1-1 NA Financial Institution Identification of Creditor AgentUnique and unambiguous identification of a financial institution assignedunder an internationally recognised or proprietary identification scheme.3.1.2.37PmtInfCdtrAgtFinInstnIdBICString 1-1 NA BIC of Creditor AgentMaximum length: 11Format rule: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}E.g.: AMBKDKKKXXX3.1.2.38PmtInfCdtrAgtSeeSchema0-1 NA Branch Identification of Creditor AgentNot used by Nets.BrnchId3.1.2.39PmtInfCdtrAgtAcctSeeSchema0-1 NA Creditor Agent AccountNot used by Nets.3.1.2.40PmtInfUltmtCdtrSeeSchema0-1 NA Ultimate CreditorNot used by Nets.3.1.2.41PmtInfChrgBr4!a 0-1 NA Charge BearerNot used by Nets.3.1.2.42PmtInfChrgsAcctSeeSchema0-1 NA Charges AccountNot used by Nets.Page 20 of 232

XML Element Format Status Rulebookref.Description / validation rules3.1.2.43PmtInfChrgsAcctAgtString 0-1 NA Charges Account AgentNot used by Nets.3.1.2.44PmtInfCdrtSchmeIdSeeSchema0-1 NA Creditor Sheme IdNot used by Nets3.1.3 Payment collection (debit initiation) – payment transaction informationThe following sets of fields are used to specify the transaction information that is present in the payment collection – direct debit paymentcollection file.These sets of fields have to be repeated 1 to N times according to the number of transactions present in the field GrpHdr/NbOfTxs.Page 21 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.13.1.3.23.1.3.33.1.3.4PmtInfDrctDbtTxInfPmtInfDrctDbtTxInfPmtIdPmtInfDrctDbtTxInfPmtIdInstrIdPmtInfDrctDbtTxInfPmtIdEndToEndIdSee Schema 1-n NA Direct Debit Transaction InformationSee Schema 1-1 NA Payment Identification35x 0-1 NA Instruction IdentificationContains fields that are used to provide information on the individualtransaction(s) included in the message.Set of elements used to reference a payment instruction.Unique identification assigned by the creditor to unambiguously identify thetransaction.Length: 1-35.Content: "([A-Za-z0-9]|[\?|/|\-|:|\(|\)|\.|,|'])"E.g.: I12345678PAIN008COR200911120000000135x 1-1 AT-10 End To End IdentificationUnique identification assigned by the creditor to unambiguously identify thetransaction. This identification is passed on, unchanged, throughout the entireend-to-end chain.The end-to-end identification can be used for reconciliation or to link tasks thatrelate to the transaction. It can be included in several messages related to thetransaction.Length: 1-35.Content: "([A-Za-z0-9]|[\?|/|\-|:|\(|\)|\.|,|'])"E.g.: E12345678PAIN008COR2009111200000001E12345678PAIN008B2B2009111200000001Page 22 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.53.1.3.63.1.3.73.1.3.8PmtInfDrctDbtTxInfPmtTpInfPmtInfDrctDbtTxInfPmtTpInfInstrPrtyPmtInfDrctDbtTxInfPmtTpInfSvcLvlPmtInfDrctDbtTxInfPmtTpInfLclInstrmSee Schema 0-1 NA Payment Type InformationThe set of fields further identifies the transaction.String 0-1 NA Transaction PriorityNot used by Nets.See Schema 0-1 AT-20 Transaction service LevelNot used by Nets.See Schema 0-1 NA Transaction typeNot used by Nets.Page 23 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.93.1.3.103.1.3.11PmtInfDrctDbtTxInfPmtTpInfLclInstrmCdPmtInfDrctDbtTxInfPmtTpInfSeqTpPmtInfDrctDbtTxInfPmtTpInfCtgyPurpSee Schema 0-1 NA Transaction type codeNot used by Nets.See Schema 1-1 AT-21 Transaction Sequence TypeIdentifies the direct debit sequence, se a complete list of sequence types insection 4.3.Usage rule: If ‘Amendment Indicator’ is ‘TRUE’, and ‘Original Debtor Agent’ is setto ‘SMNDA’, this message element must indicate ‘FRST’. For available values,check the table Sequence type in section 4.3.E.g.: FRSTSee Schema 0-1 AT-59 Transaction Category PurposeNot used by Nets.Page 24 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.12PmtInfDrctDbtTxInfInstdAmtCcy(Attribute)18d 3!a 1-1 AT-06 Transaction Instructed AmountMoney to be moved between the debtor and creditor.Usage rule: Only ‘EUR’ is allowed in the attribute.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.Length: 1-18. Content: "([0-9])"Attribute: “Ccy”="EUR"NB. Decimal separator is ".", not ",".3.1.3.13PmtInfDrctDbtTxInfChrgBrString 1-1 NA Charge BearerE.g. if the amount is 14.97 euro: 14.97Specifies the party/parties that will bear the charges associated with theprocessing of the payment transaction.Usage rule: It must be filled with ‘SLEV’.E.g.: SLEVPage 25 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.143.1.3.153.1.3.16PmtInfDrctDbtTxInfDrctDbtTxPmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfPmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfMndtIdSee Schema 1-1 NA Direct Debit TransactionContains the fields which provide information specific to the Direct Debitmandate.Only one occurrence per DrctDbtTxInf.See Schema 1-1 NA Mandate Related Information35x 1-1 AT-01 Mandate IdentificationContains the fields that provide further details about the direct debit mandatesigned between the creditor and the debtor.Unique identification, as assigned by the creditor, to unambiguously identify themandate.The unique MandateIDLeading and trailing spaces inside the MndtId field are not significant andare removed before the mandate identifier content is stored.This data element is case insensitive. For example: Mandate Identification123AAa45678, 123aaA45678, 123aaa45678 and 123AAA45678 shall beconsidered identical also in comparing the Direct Debit and its R-transactions.Length: 1-35.Content: ([A-Za-z0-9]|[+|\?|/|\-|:|\(|\)|\.|,|'|\s]){1,35}E.g.: MANDATE12345678COR00001000000000025Page 26 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.17PmtInfDrctDbtTxInfISO Date 1-1 AT-25 Date Of SignatureDate on which the direct debit mandate was signed by the debtor.DrctDbtTxMndtRltdInfThe date of signature of the mandateDtOfSgntrLength: 10.Content: ISO Date (YYYY-MM-DD)E.g. 2008-02-233.1.3.18PmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfAmdmntIndBoolean 1-1 Amendment IndicatorIndicator notifying whether the underlying mandate is amended or not.By default it must contain “false”. If the mandate is amended, it must contain“true”.NB. This field is optional in the XSD, but for Nets it is mandatory.E.g.: FalsePage 27 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.193.1.3.203.1.3.21PmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfAmdmntInfDtlsPmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfAmdmntInfDtlsOrgnlMndtIdPmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfAmdmntInfDtlsOrgnlCdtrSchmeIdSee Schema 0-1 AT-24 Amendment Information DetailsThe list of fields contains the mandate elements that have been modified.AT-24: Reason for amending the mandateUsage rule: Mandatory if ‘Amendment indicator’ is ‘true’.35x 0-1 AT-19 Original Mandate IdentificationUnique identification, as assigned by the creditor, to unambiguously identify theoriginal mandate.Usage rule: Mandatory if changes occur in ‘Mandate identification’, otherwise itmust not be used.For content and format rules, please refer to:PmtInf/DrctDbtTxInf/DrctDbtTx/MndtRltdInf/MndtId. This data element is case insensitiveSee Schema 0-1 NA Original Creditor Scheme IdentificationOriginal creditor scheme identification that has been modified.It contains the field values of the creditor scheme identification listed in the oldversion of the mandate.Usage rule: Mandatory if changes occur in ‘Creditor scheme identification’,otherwise it must not be used.Page 28 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.22PmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfAmdmntInfDtlsOrgnlCdtrSchmeIdNm70x 0-1 AT-03 Name of Original CreditorThe name by which the original creditor is known as well as the name that isusually used to identify that particular creditor.Usage rule: If present the new creditor name must be specified under creditor(PmtInf/Cdtr/Nm) and creditors old name should be specified in this field.Format: Refer to the creditor’s name PmtInf/Cdtr/Nm.Page 29 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.23PmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfAmdmntInfDtlsOrgnlCdtrSchmeIdIdPrvtIdSee Schema 0-1 AT-18 Private Identification of original creditor schemeThe creditor’s identification specified by the value of tags and sub-tags in theoriginal version of the mandate (AT-02).Usage rule:Mandatory if changes occur in creditor scheme identification.Usage Rule: Private Identification is used to identify either an organisation or aprivate person.Usage Rule: ‘Scheme Name’ under ‘Other’ must’ specify ‘SEPA’ under ‘Code’.Usage Rule: ‘Identification’ under ‘Other ‘must be used with an identifierdescribed in the Creditor Scheme Identification format specified insection “Creditor scheme identification format” in in the documentCreditor’s user and information guide to SEPA Direct DebitUsage Rule: Only one occurrence of ‘Other’ is allowed.For content and format rules, please refer to the field:PmtInf/DrctDbtTxInf/DrctDbtTx/CdtrSchmeId/Id/PrvtId.OrgnlCdtrSchmeId/Id/PrvtId/Othr/Id - This data element is space andcase insensitivePage 30 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.24PmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfAmdmntInfDtlsOrgnlCdtrSchmeIdIdPrvtIdOthrSchmeNm35x 0-1 AT-18 Scheme Name of Original Creditor SchemePage 31 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.25PmtInfDrctDbtTxInf35x 0-1 AT-18DrctDbtTxMndtRltdInfAmdmntInfDtls• Conditional on Amendment Indicator (see above).• Used only if OrgnlCdtrSchmeId is used; and• Must be SEPA: (schema validation)3.1.3.26OrgnlCdtrSchmeIdIdPrvtIdOthrSchmeNmPrtryPmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfAmdmntInfDtlsOrgnlCdtrSchmeIdPstlAdrSee Schema 0-1 NA Postal AddressNot used by Nets.Page 32 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.273.1.3.28PmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfAmdmntInfDtlsOrgnlCdtrSchmeIdCtryOfResPmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfAmdmntInfDtlsOrgnlCdtrAgt2!a 0-1 NA Country of Residence of Original CreditorNot used by Nets.See Schema 0-1 NA Original Creditor AgentNot used by Nets.Page 33 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.293.1.3.30PmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfAmdmntInfDtlsOrgnlCdtrAgtAcctPmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfAmdmntInfDtlsOrgnlDbtrSee Schema 0-1 NA Original Creditor Agent AccountNot used by Nets.See Schema 0-1 NA Original DebtorNot used by Nets.Page 34 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.31PmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfAmdmntInfDtlsSee Schema 0-1 NA Original Debtor AccountOriginal debtor account that has been changed.Usage rule: It must contain the IBAN field.OrgnlDbtrAcctFormat:Refer to the format of the debtor account sectionPmtInf/DrctDbtTxInf/DbtrAcct/Id toPmtInf/DrctDbtTxInf/DbtrAcct/Id/IBAN.3.1.3.32PmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfAmdmntInfDtlsOrgnlDbtrAgtSee Schema 0-1 NA Original Debtor AgentUsed only if the debtor has changed debtor agent (bank). Note that the newdebtor agent’s BIC should be specified in PmtInf/DrctDbtTxInf/DbtrAgtUsage rule: Use ‘Other identification (OrgnlDbtrAgt /FinInstnId/ Othr/Id)’ withcode ‘SMNDA’ to indicate that the same mandate is used with thenew debtor agent.Usage rule: To be used with the ‘FRST’ indicator in the ‘Sequence type’.Page 35 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.333.1.3.343.1.3.35PmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfAmdmntInfDtlsOrgnlDbtrAgtAcctPmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfAmdmntInfDtlsOrgnlFnlColltnDtPmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfAmdmntInfDtlsOrgnlFrqcySee Schema 0-1 NA Original Debtor Agent AccountNot used by Nets.ISO Date 0-1 Original Final Collection DateNot used by Nets.4x 0-1 NA Original FrequencyNot used by Nets.Page 36 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.36PmtInfDrctDbtTxInfDrctDbtTx1025x 0-1 AT-16AT-17AT-60Electronic SignatureAdditional security provisions, such as a digital signature, as provided by thedebtor.MndtRltdInfElctrncSgntrUsage rule: If the direct debit is based on an EPC electronic mandate, this dataelement must contain AT-60, which is the reference to the mandateacceptance report made by the debtor bank.Usage Rule: This element is not to be used if the mandate is a paper mandate.Nets does currently not use this field.AT-16:AT-17:AT-60:Placeholder for the electronic signature data, if applicableType of mandate (paper, e-Mandate)Reference to the validation made by the debtor bank (if present inDS-03).3.1.3.37PmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfFrstColltnDtISO Date 0-1 First Collection DateNot used by Nets.Page 37 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.383.1.3.393.1.3.40PmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfFnlColltnDtPmtInfDrctDbtTxInfDrctDbtTxMndtRltdInfFrqcyPmtInfDrctDbtTxInfDrctDbtTxCdtrSchmeIdISO Date 0-1 Final Collection DateNot used by Nets.4x 0-1 NA FrequencyNot used by Nets.See Schema 1-1 NA Creditor Scheme IdentificationCredit party that signs the mandate.Usage rule: It is recommended that all transactions within the same ‘Paymentinformation’ block have the same ‘Creditor scheme identification’. Check section“Creditor scheme identification format” in in the document Creditor’s user andinformation guide to SEPA Direct DebitPage 38 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.413.1.3.423.1.3.43PmtInfDrctDbtTxInfDrctDbtTxCdtrSchmeIdNmPmtInfDrctDbtTxInfDrctDbtTxCdtrSchmeIdPstlAdrPmtInfDrctDbtTxInfDrctDbtTxCdtrSchmeIdId70x 0-1 NA Name of the CreditorNot used by Nets.See Schema 0-1 NA Postal Address of the CreditorNot used by Nets.See Schema 1-1 NA Identification of the CreditorUnique identification of the creditor.Page 39 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.443.1.3.45PmtInfDrctDbtTxInfDrctDbtTxCdtrSchmeIdIdOrgIdPmtInfDrctDbtTxInfDrctDbtTxSee Schema 0-1 NA Organisation Identification of the CreditorNot used by Nets and is not included in the schema either.See Schema 1-1 AT-02 Private Identification of the CreditorUnique and unambiguous identification of a person, e.g. passport.CdtrSchmeIdIdAT-02:Identifier of the creditor.PrvtIdUsage Rule: Private Identification is used to identify either an organisation or aprivate person..Page 40 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.463.1.3.47PmtInfDrctDbtTxInfDrctDbtTxCdtrSchmeIdIdPrvtIdOthrIdDrctDbtTxInfDrctDbtTxCdtrSchmeIdIdPvrtIdOthrSchmeNm35x 1-1 AT-02 The Creditor Scheme IdentifierUsage Rule: ‘Identification’ under ‘Othr ‘must be used with an identifier describedin the Creditor Scheme Identification format specified in section“Creditor scheme identification format” in in the document Creditor’suser and information guide to SEPA Direct DebitUsage Rule: Only one occurrence of ‘Othr’ is allowed.This data element is space and case insensitiveSee Schema 1-1 AT-02, Scheme Name of the CreditorPage 41 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.48DrctDbtTxInfDrctDbtTx35x 1-1 AT-02,Usage Rule: Must be “SEPA”: (schema validation)CdtrSchmeIdIdPvrtIdOthrSchmeNmPrtry3.1.3.493.1.3.50PmtInfDrctDbtTxInfDrctDbtTxCdtrSchmeIdCtryOfResPmtInfDrctDbtTxInfDrctDbtTxPreNtfctnId2!a 0-1 NA Country of Residence of the CreditorNot used by Nets.X35 0-1 NA Pre Notification IdentificationNot used by Nets.Page 42 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.513.1.3.523.1.3.533.1.3.54PmtInfDrctDbtTxInfDrctDbtTxPreNtfctnDtPmtInfDrctDbtTxInfUltmtCdtrPmtInfDrctDbtTxInfUltmtCdtrNmPmtInfDrctDbtTxInfUltmtCdtrPstlAdrISO Date 0-1 NA Pre Notification DateNot used by Nets.See Schema 0-1 NA Ultimate Creditor70x 0-1 AT-38 Name of the Ultimate CreditorContains all the sub fields which specify the details of the ultimate creditor.The data in the field and subfields about the ultimate creditor is only used, if dataare part of the mandate data that this collection is representing. Please refer toDS-01 formular.Name by which the ultimate creditor is known as well as the name that is used toidentify that particular creditor.Length: 1-70Content: StringE.g.: COMPANY BEHIND CREDITOR A/SSee Schema 0-1 NA Postal Address of ultimate creditorNot used by Nets.Page 43 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.553.1.3.563.1.3.573.1.3.58PmtInfDrctDbtTxInfUltmtCdtrIdPmtInfDrctDbtTxInfUltmtCdtrIdOrgIdPmtInfDrctDbtTxInfUltmtCdtrIdPrvtIdPmtInfDrctDbtTxInfUltmtCdtrCtryOfResSee Schema 0-1 NA Identification of the Ultimate CreditorContains the fields which are used to uniquely identify the ultimate creditor.See Schema {Or AT-39 Organisation Identification of the Ultimate CreditorUnique and unambiguous way to identify the creditor’s organisation.Usage Rule: Either ‘BIC or BEI’ or one occurrence of ‘Other’ is allowed.For allowed values in SchmeNm/Cd, check the table 4.1 Organisationidentification.See Schema Or} AT-39 Private Identification of the Ultimate CreditorUnique and unambiguous way to identify the person who is the creditor.Usage Rule: Either ‘Date and Place of Birth’ or one occurrence of ‘Other’ isallowed.For allowed values in SchmeNm/Cd, check the table 8.2 Private identification.2!a 0-1 NA Country of Residence of the Ultimate CreditorNot used by Nets.Page 44 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.593.1.3.603.1.3.613.1.3.623.1.3.63PmtInfDrctDbtTxInfDbtrAgtPmtInfDrctDbtTxInfDbtrAgtFinInstnIdPmtInfDrctDbtTxInfDbtrAgtFinInstnIdBICPmtInfDrctDbtTxInfDbtrAgtAcctPmtInfDrctDbtTxInfDbtrSee Schema 1-1 AT-13 Debtor AgentFinancial institution servicing an account for the debtor.Usage rule: It must contain the BIC field.See Schema 1-1 AT-13 Financial Instituion Identification of Debtor AgentString 1-1 AT-13 BIC of Debtor AgentUnique and unambiguous identification of the debtor agent’s financial institution,as assigned under an internationally recognised or proprietary identificationscheme.Maximum Length: 11Format rule: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}E.g.: AMBKDKKKXXXSee Schema 0-1 NA Debtor Agent AccountSee Schema 1-1 NA DebtorNot used by Nets.Party that owes an amount of money to the creditor.Page 45 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.643.1.3.653.1.3.66PmtInfDrctDbtTxInfDbtrNmPmtInfDrctDbtTxInfDbtrPstlAdrPmtInfDrctDbtTxInfDbtrPstlAdrAdrTp70x 1-1 AT-14 Name of DebtorName by which debtor is known as well as the name that is used to identify thatparticular debtor.Length: 1-70.Content: TextE.g.: JAMES MORRISONSee Schema 0-1 AT-09 Postal Address of DebtorSee Schema 0-1 NA Address Type of DebtorInformation that locates and identifies a specific address of the debtor, as definedby postal services.Not used by Nets.Page 46 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.673.1.3.683.1.3.69PmtInfDrctDbtTxInfDbtrPstlAdrStrtNmPmtInfDrctDbtTxInfDbtrPstlAdrBldgNbPmtInfDrctDbtTxInfDbtrPstlAdrPstCd70x 0-1 AT-09 Street Name of DebtorNot used by Nets.16x 0-1 AT-09 Building Number of DebtorNot used by Nets.16x 0-1 AT-09 Postal Code of DebtorNot used by Nets.Page 47 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.703.1.3.713.1.3.72PmtInfDrctDbtTxInfDbtrPstlAdrTwnNmPmtInfDrctDbtTxInfDbtrPstlAdrCtrySubDvsnPmtInfDrctDbtTxInfDbtrPstlAdrCtry35x 0-1 AT-09 Town Name of DebtorNot used by Nets.35x 0-1 AT-09 Country Sub Division of DebtorNot used by Nets.2!a 0-1 AT-09 Country of DebtorThe country of the debtor address.Must be a valid country code according to ISO3166.Mandatory if address line is used, otherwise it is not used.Length: 2.Content: Valid country codeE.g.: SEPage 48 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.73PmtInfDrctDbtTxInfDbtrPstlAdrAdrLine70x 0-2 AT-09 Address Line of DebtorThe address line can have a maximum of two occurrences.Length: 1-70Content: Text3.1.3.743.1.3.75PmtInfDrctDbtTxInfDbtrIdPmtInfDrctDbtTxInfDbtrIdOrgIdE.g. 27 Main Street, Little Town, 234BD7 Greater TownSee Schema 0-1 NA Identification of DebtorUnique and unambiguous identification of the debtor.This field and subfields are used, if it is included in the mandate.See Schema {Or AT-27 Organisation Identification of DebtorUsage Rule: Either ‘BIC or BEI’ or one occurrence of ‘Other’ is allowed.For allowed values, check the table Organisation identification.Page 49 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.763.1.3.773.1.3.783.1.3.79PmtInfDrctDbtTxInfDbtrIdPrvtIdPmtInfDrctDbtTxInfDbtrCtryOfResPmtInfDrctDbtTxInfDbtrAcctPmtInfDrctDbtTxInfDbtrAcctIdSee Schema Or} AT-27 Private Identification of DebtorUsage Rule: Either ‘Date and Place of Birth’ or one occurrence of ‘Other’ isallowed.For allowed values, check the table Private identification.2!a 0-1 NA Country of Residence of DebtorNot used by Nets.See Schema 1-1 AT-07 Debtor AccountUnambiguous identification of the debtor’s account.Usage rule: It must contain the IBAN field.See Schema 1-1 AT-07 Identification of Debtor AccountUnambiguous identification of the debtor account.Page 50 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.803.1.3.81PmtInfDrctDbtTxInfDbtrAcctIdIBANPmtInfDrctDbtTxInfUltmtDbtrString 1-1 AT-07 IBAN of Debtor AccountMaximum Length: 34Format rule: [a-zA-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}E.g. DK1052010009671208See Schema 0-1 NA Ultimate DebtorUltimate party that owes an amount of money to the (ultimate) creditor.Usagerule: Mandatory, if provided by the debtor in the mandate.3.1.3.82PmtInfDrctDbtTxInfUltmtDbtrNm70x 0-1 AT-15 Name of Ultimate DebtorThe data about the ultimate debtor in this field and its subfields is only used if thedata is part of the mandate that this transaction is representing. Please refer tothe DS-01 form in the rulebook.Name by which ultimate debtor is known as well as the name that is used toidentify that particular debtor.Length: 1-70Content: TextE.g.: Christian SoerensenPage 51 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.833.1.3.843.1.3.853.1.3.86PmtInfDrctDbtTxInfUltmtDbtrPstlAdrPmtInfDrctDbtTxInfUltmtDbtrIdPmtInfDrctDbtTxInfUltmtDbtrIdOrgIdPmtInfDrctDbtTxInfUltmtDbtrIdPrvtIdSee Schema 0-1 NA Postal Address of Ultimate DebtorNot used by Nets.See Schema 0-1 NA Identification of Ultimate DebtorUnique identification of the ultimate debtor.See Schema {Or AT-37 Organisation Identification of ultimate debtorUsage Rule: Either ‘BIC or BEI’ or one occurrence of ‘Other’ is allowed.For allowed values, check the table Organisation identification.See Schema Or} AT-37 Private Identification of ultimate debtorUsage Rule: Either ‘Date and Place of Birth’ or one occurrence of ‘Other’ isallowed.For allowed values, check the table Private identification.Page 52 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.873.1.3.883.1.3.893.1.3.903.1.3.91PmtInfDrctDbtTxInfUltmtDbtrCtryOfResPmtInfDrctDbtTxInfInstrForCdtrAgtPmtInfDrctDbtTxInfPurpPmtInfDrctDbtTxInfPurpCdPmtInfDrctDbtTxInfPurpPrtry2!a 0-1 NA Country of Residence of Ultimate DebtorNot used by Nets.140x 0-1 NA Instruction for Creditor AgentNot used by Nets.See Schema 0-1 AT-58 PurposeSee Schema 0-1 NA CodeSee Schema 0-1 NA ProprietaryPurpose is used by the end-customers, i.e. creditors, (ultimate) debtors, and(ultimate) creditors to provide information concerning the nature of the payment.Underlying reason for the payment transaction. See a complete list of purposecodes in section 4.9Not used by Nets.Page 53 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.923.1.3.933.1.3.943.1.3.95PmtInfDrctDbtTxInfRgltryRptgPmtInfDrctDbtTxInfTaxPmtInfDrctDbtTxInfRltdRmtInfPmtInfDrctDbtTxInfRmtInf4!a 0-10 NA Regulatory ReportingSee Schema 0-1 NA TaxNot used by Nets.Not used by Nets.See Schema 0-10 NA Related Remittance InformationNot used by Nets.See Schema 0-1 AT-22 Remittance InformationInformation supplied to enable the matching of an entry with the items that thetransfer is intended to settle, such as commercial invoices in an accountsreceivable system.Usage rule: Either ‘Structured’ or ‘Unstructured’ may be present.Page 54 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.96PmtInfDrctDbtTxInfRmtInfUstrd140x 0-1 NA Unstructured Remittance InformationUsage rule:Length: 1-140.It cannot be used at the same time as Structured RemittanceInformation (see below). This is schema validated, Format rule:Only one occurrence of ‘Unstructured’ is allowed.Content:TextE.g.: Rent for apartment May 20143.1.3.97PmtInfDrctDbtTxInfRmtInfStrd140xSee Schema0-1 NA Structured Remittance InformationUsage rule:Usage rule:‘Structured’ can be used, provided that the tags and the data withinthe ‘Structured’ element do not exceed 140 characters.It cannot be used at the same time as unstructured remittance (seeabove).Format rule: Only one occurrence of ‘Structured’ is allowed.Length: 1-140Content:Text structured in tags.3.1.3.98PmtInfDrctDbtTxInfRmtInfStrdRfrdDocInfSee Schema 0-1 NA Referred Document InformationSet of tags used to identify the documents referred to in the remittanceinformation.Page 55 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.993.1.3.100PmtInfDrctDbtTxInfRmtInfStrdRfrdDocAmtPmtInfDrctDbtTxInfRmtInfSee Schema 0-n NA Referred Document AmountSee Schema 0-1 NA Creditor Reference InformationSet of tags used to provide details about the amounts of the referred document.Reference information provided by the creditor to allow the identification of theunderlying documents.StrdCdtrRefInfUsage rule:Usage rule:When present, the creditor bank is not obliged to validate thereference information.When used, both ‘Creditor reference type’ and ‘Creditor reference’must be present.3.1.3.101PmtInfDrctDbtTxInfRmtInfStrdCdtrRefInfTpSee Schema 0-1 NA Creditor Reference TypeSpecifies the type of creditor reference.Page 56 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.1023.1.3.103PmtInfDrctDbtTxInfRmtInfStrdCdtrRefInfTpCdOrPrtryPmtInfDrctDbtTxInfRmtInfSee Schema 0-1 NA4x 0-1 NA CodeCreditor reference type in code format.StrdCdtrRefInfTpCdOrPrtryCdUsage rule:E.g.:It must be filled with ‘SCOR’.Mandatory if the creditor reference type is filled out..SCORPage 57 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.1043.1.3.105PmtInfDrctDbtTxInfRmtInfStrdCdtrRefInfTpCdOrPrtryPrtryPmtInfDrctDbtTxInfRmtInfStrdCdtrRefInfTpIssr35x 0-1 NA ProprietaryNot used by Nets.35x 0-1 NA IssuerEntity that assigns the credit reference type.Page 58 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.106PmtInfDrctDbtTxInfRmtInf35x 0-1 NA Creditor ReferenceUnique reference, as assigned by the creditor, to unambiguously refer to thepayment transaction.StrdCdtrRefInfRefUsage rule:Usage rule:If a creditor reference contains a check digit, the receiving bank isnot required to validate it.If the receiving bank validates the check digit and if the validationfails, the bank may continue its processing and send the transactionto the next party in the chain.3.1.3.1073.1.3.108PmtInfDrctDbtTxInfRmtInfStrdInvcrPmtInfDrctDbtTxInfRmtInfStrdInvceeSee Schema 0-1 NA InvoicerSee Schema 0-1 NA InvoiceeIdentification of the organisation that issued the invoice. Is used when theinvoicer is different from the creditor or ultimate creditor.Identification of the party to whom an invoice is issued. Is used when the invoiceeis different from the debtor or ultimate debtor.Page 59 of 232

XML Element Format Status RuleBookref.Validation RulesDescription / validation rules3.1.3.109PmtInfDrctDbtTxInfRmtInfStrdAddtlRmtInf140x 0-1 NA Additional Remittance InformationAdditional information, in free text form, is added to complement the structuredremittance information.Page 60 of 232

3.2 PAIN.007.001.02PBS Customer payment reversal file3.2.1 Payment reversal (reversal initiation) – group headerXML Element Format Status Rulebookref.Description / validation rules3.2.1.1GrpHdr See Schema 1-1 NA Group HeaderContains common information about the payment reversal.3.2.1.2GrpHdrMsgId35x 1-1 NA Message IdentificationCreditor's unique file reference created by creditor as defined in Section“Description of specific XML tags” in the document Creditor’s user andinformation guide to SEPA Direct Debit.The uniqueness of the message ID created by creditor is checked in Nets’ SDDsystem.The identification cannot include leading, trailing or internal spaces.Format: Refer to Pain 008 section GrpHdr/MsgId.E.g.: M12345678PAIN007COR200911120000000013.2.1.3GrpHdrCreDtTmISODate&Time1-1 NA Creation date timeThe date and time when the file was created by the creditor.Format: Refer to the Pain 008 section GrpHdr/CreDtTm.Page 61 of 232

XML Element Format Status Rulebookref.Description / validation rules3.2.1.4GrpHdrAuthstn128x0-2 NA AuthorisationNot used by Nets.3.2.1.53.2.1.6GrpHdrBtchBookgGrpHdrNbOfTxsBoolean 0-1 NA Batch BookingNot used by Nets.15n 1-1 NA Number Of TransactionsThe number of transactions included in this file.Schema validationMust be the total number of transactions included in this file.3.2.1.73.2.1.8GrpHdrCtrlSumGrpHdrGrpRvslFormat: Refer to Pain 008 section GrpHdr/NbOfTxs.Decimal 0-1 NA Control SumThe sum of all transaction amounts in this file.Maximum length: 18 digits.Maximum number of fractional digits: 17 digitsE.g.: 1.504x 1-1 NA Group ReversalUsage rule: It must be filled with ‘false’.E.g.: falsePage 62 of 232

XML Element Format Status Rulebookref.Description / validation rules3.2.1.93.2.1.103.2.1.113.2.1.123.2.1.13GrpHdrInitgPtyGrpHdrInitgPtyNmGrpHdrInitgPtyPstlAdrGrpHdrInitgPtyIdGrpHdrInitgPtyIdOrgIdSee Schema 0-1 NA Initiating Party70x 0-1 NA NameSee Schema 0-1 NA Postal AddressSee Schema 0-1 NA IdentificationInformation (address and identification details) about the creditor who initiatesthe payment reversal.Name by which the creditor is known as well as the name that is used toidentify the creditor who initiates the payment.E.g.: Peter Soerensen Eftf. A/S.This field and its underlying fields are not used by Nets.See Schema {Or NA Organisation IdentificationContains one of the subfields that are used to indicate the organisational orprivate identification of the creditor.Unique and unambiguous way to identify the creditor’s organisation.It cannot be used at the same time as Id/PrvtId (below)If SchmeNm/Cd is used, one of the values in the table 4.1 Organisationidentification must be used.Usage Rule: Either ‘BIC or BEI’ or one occurrence of ‘Other’ is allowed.Page 63 of 232

XML Element Format Status Rulebookref.Description / validation rules3.2.1.143.2.1.15GrpHdrInitgPtyIdPrvtIdGrpHdrInitgPtyCtryOfResSee Schema Or} NA Private Identification2!a 0-1 NA Country of ResidenceUnique and unambiguous identification of a creditor, e.g. passport.It cannot be used at the same time as Id/OrgId (above)If SchmeNm/Cd is used, one of the values in the table 8.2 Privateidentification must be used.Usage Rule: Either ‘Date and Place of Birth’ or one occurrence of ‘Other’ isallowed.The country of residence of the creditor or the party who initiates the paymentreversal on behalf of creditor.3.2.1.163.2.1.173.2.1.18GrpHdrFwdgAgtGrpHdrDbtrAgtGrpHdrCdtrAgtFormat: Refer to Pain 008 section PmtInf/Cdtr/PstlAdr/Ctry.See Schema 0-1 NA Forwarding AgentNot used by Nets.See Schema 0-1 NA Debtor AgentNot used by Nets.See Schema 0-1 AT-12 Creditor AgentFinancial institution servicing an account of the creditor.Page 64 of 232

XML Element Format Status Rulebookref.Description / validation rules3.2.1.193.2.1.20GrpHdrCdtrAgtFinInstnIdGrpHdrCdtrAgtFinInstnIdBICSee Schema 0-1 NA Financial Institution Identification of Creditor AgentString 0-1 AT-12 BIC of Creditor AgentUnique and unambiguous identification of a financial institution, as assignedunder an internationally recognised or proprietary identification scheme.Creditors agent equals creditors bankMaximum length:11Format rule: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}E.g.: AMBKDKKKXXXPage 65 of 232

3.2.2 Payment reversal (reversal initiation) – original group informationXML ElementFormatStatusRulebookref.Description / validation rules3.2.2.1OrgnlGrpInf See Schema 1-1 NA Original Group InformationInformation related to the original group of transactions to which the messagerefers.3.2.2.23.2.2.3OrgnlGrpInfOrgnlMsgIdOrgnlGrpInfOrgnlMsgNmId35x 1-1 NA Original Message IdentificationUnique and unambiguous identification of the original message as assigned bythe original instructing party.Format: Refer to Pain 008 section GrpHdr/MsgId.35x 1-1 NA Original Message Name IdentificationSpecifies the original message name identifier to which the message refers.SDD Service must always be equal to pain.008*.Length: 1-35. Content: "pain\.008[A-Za-z0-9\.]{0, 27}" or "PAIN\.008 [A-Zaz0-\.]{0,27}"E.g.: pain.008.001.023.2.2.4OrgnlGrpInfOrgnlCreDtTmISO DateTime0-1 NA Original Creation Date TimeNot used by Nets.3.2.2.5OrgnlGrpInfRvslRsnInfSee Schema 0-1 NA Reversal Reason InformationNot used by Nets.Page 66 of 232

3.2.2.63.2.2.73.2.2.83.2.2.93.2.2.10OrgnlGrpInfRvslRsnInfRvslOrgtrOrgnlGrpInfRvslRsnInfRvslRsnOrgnlGrpInfRvslRsnInfRvslRsnCdOrgnlGrpInfRvslRsnInfRvslRsnPrtryOrgnlGrpInfRvslRsnInfAddtlInfSee Schema 0-1 NA Reversal OriginatorNot used by Nets.See Schema 0-1 NA Reversal ReasonNot used by Nets.String {Or AT-31 Reversal Reason CodeNot used by Nets.String Or} NA Reversal Reason ProprietaryNot used by Nets.105x 0-1 NA Additional InformationNot used by Nets.Page 67 of 232

3.2.3 Payment reversal (reversal initiation) – transaction informationXML Element Format StatusRulebookRef.Description / validation rules3.2.3.1OrgnlPmtInfAndRvslSeeSchema0-n NA Original Payment Information and ReversalInformation concerning the original payment information, to which thereversal message refers.3.2.3.23.2.3.33.2.3.43.2.3.53.2.3.6OrgnlPmtInfAndRvslRvslPmtInfIdOrgnlPmtInfAndRvslOrgnlPmtInfIdOrgnlPmtInfAndRvslOrgnlNbOfTxsOrgnlPmtInfAndRvslOrgnlCtrlSumOrgnlPmtInfAndRvslBtchBookg35x 0-1 NA Reversal Payment Information IdentificationUnique identification for the reversal instruction.35x 0-1 NA Original Payment Information IdentificationUnique identification, as assigned by the original sending party, tounambiguously identify the original payment information group.15n 0-1 NA Original Number of TransactionsNumber of individual transactions contained in the original paymentinformation group.Format:- [0-9]{1,15}Decimal 0-1 NA Original Control SumTotal of all individual amounts included in the original payment informationgroup, irrespective of currencies.Format:- fractionDigits: 17Boolean 0-1 NA Batch BookingtotalDigits: 18Not used by Nets.Page 68 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.2.3.7OrgnlPmtInfAndRvslPmtInfRvslBoolean 0-1 NA Payment Information ReversalIndicates whether or not the reversal applies to the complete originalpayment information group or to individual transactions within that group.3.2.3.8OrgnlPmtInfAndRvslRvslRsnInfSeeSchema0-1 NA Reversal Reason InformationSet of elements used to provide detailed information on the reversalreason.3.2.3.9OrgnlPmtInfAndRvslRvslRsnInfSeeSchema0-1 NA OriginatorParty that issues the reversal.Orgtr3.2.3.10OrgnlPmtInfAndRvslRvslRsnInfRsnSeeSchema0-1 NA ReasonSpecifies the reason for the reversal.Usage Rule: ‘Reversal Reason’ must be present either in ‘Original GroupInformation’ or ‘Transaction Information’3.2.3.11OrgnlPmtInfAndRvslRvslRsnInfRsnCd4x 0-1 AT-31 CodeReason for the reversal, as published in an external reason code list.Page 69 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.2.3.123.2.3.13OrgnlPmtInfAndRvslRvslRsnInfPrtryOrgnlPmtInfAndRvslRvslRsnInfAddtlInf35x 0-1 NA ProprietaryReason for the reversal, in a proprietary form.105x 0-n NA Additional InformationFurther details on the reversal reason.3.2.3.14TxInfSeeSchema1-n NA Transaction InformationSet of fields used to provide information about the original transactions towhich the reversal message refers.3.2.3.15TxInfRvslId35x 1-1 NA Reversal IdentificationUnique identification for the reversal transaction.Length: 1-35.Content: "([A-Za-z0-9]|[\?|/|\-|:|\(|\)|\.|,|'])"E.g.: R12345678PAIN007COR2009111200000001Page 70 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.2.3.163.2.3.173.2.3.18TxInfOrgnlInstrIdTxInfOrgnlEndToEndIdTxInfOrgnlInstdAmt35x 0-1 NA Original Instruction IdentificationUnique identification assigned by the creditor, to unambiguously identifythe original instruction.This identification cannot include leading, trailing or internal spaces.Length: 1-35.Content: "([A-Za-z0-9]|[\?|/|\-|:|\(|\)|\.|,|'])"E.g.: INSID00000000000000000000000000000735x 1-1 AT-10 Original End to End IdentificationUnique identification assigned by the creditor, to unambiguously identifythe original transaction.Format: Refer to Pain 008 sectionPmtInf/DrctDbtTxInf/PmtId/EndToEndId.18d 3!a 0-1 AT-06 Original Instructed AmountThe amount of money that is to be moved between debtor and creditor asspecified in the original transaction. The stated amount is excl. thededuction of charges and it is expressed in the currency ordered by theoriginal initiating party.Must be the same amount as the original amount of the Direct Debit.Format: Refer to Pain 008 sectionPmtInf/DrctDbtTxInf/InstdAmt/Ccy.Page 71 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.2.3.193.2.3.20TxInfRvsdInstdAmtTxInfChrgBr18d 3!a 0-1 AT-06 Reversed Instructed Amount4!a 0-1 NA Charge BearerAmount of money to be moved between debtor and creditor in thereversed transaction. The amount is excl. the deduction of charges.The amount of the reversal must be the same as the amount of thecollection in euro (AT-06).Must be the same amount as the original amount of the Direct Debit.Format: Refer to Pain 008 sectionPmtInf/DrctDbtTxInf/InstdAmt/Ccy.Specifies if the creditor and/or debtor will bear the charges associated withthe processing of the transaction.It must be filled with “SLEV”.Format: Refer to Pain 008 section PmtInf/DrctDbtTxInf/ChrgBr.3.2.3.21TxInfRvslRsnInfSeeSchema1-1 NA Reversal Reason InformationSet of tags used to provide detailed information about the reversal reason.3.2.3.22TxInfRvslRsnInfSeeSchema1-1 NA Reversal OriginatorParty that initiates the reversal.OrgtrPage 72 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.2.3.23TxInfRvslRsnInfOrgtrNm70x 0-1 NA Reversal Originator NameThe name of the party that initiates the reversal (customer).If the single transaction is reversed, this parent (RvslRsnInf) must beused.Cannot be used at the same time asTxnInf/RvslRsnInf/RvslOrgtr/Id/OrgId/BICOrBEI (see below)E.g.: Peter Soerensen3.2.3.24TxnInfRvslRsnInfSeeSchema0-1 NA Identification of Reversal originatorUnique identification of the reversal originator.OrgtrId3.2.3.25TxnInfRvslRsnInfSeeSchema0-1 NA Organisation Identification of Reversal originatorUnique identification of the reversal originator organisation.OrgtrIdFor allowed values, check the table Organisation identification.OrgIdPage 73 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.2.3.26TxnInfRvslRsnInf4!a2!a2!c[3!c]0-1 NA BIC of Reversal OriginatorThe party from whom the reversal originated (bank).OrgtrIdIf the single transaction is reversed, then this parent (RvslRsnInf) must beused.OrgIdBICOrBEICannot be used at the same time as TxnInf/RvslRsnInf/RvslOrgtr/Nm (seeabove).BIC content: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}E.g.: DIRPFRAC3.2.3.27TxnInfRvslRsnInfSeeSchema0-1 NA Reversal Originator Postal AddressNot used by Nets.OrgtrPstlAdr3.2.3.28TxnInfRvslRsnInfOrgtrCtryOfRes2!a 0-1 NA Reversal Originator Country of ResidenceNot used by Nets.Page 74 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.2.3.29TxInfRvslRsnInfSeeSchema1-1 NA Reversal ReasonSpecifies the reason for the reversal.RsnUsage rule: ‘Reversal reason’ must be present in either ‘Original groupinformation’ or ‘Transaction information’.3.2.3.30TxInfRvslRsnInfRsnCdString 1-1 AT-31 Reversal Reason CodeThe code specifies the reason for the reversal.Reason for the reversal, as published in an external reason code list (4.7).It must be filled with “AM05” - duplication entry. Or MS02- reason notspecified3.2.3.313.2.3.32TxInfRvslRsnInfRsnPrtryTxInfRvslRsnInfAddtlRvslRsnInfString 0-1 NA Reversal Reason ProprietaryThe code specifies the reason for the reversal.Reason for the reversal in a proprietary form.Not used by Nets.105x 0-1 NA Additional Reversal Reason informationNot used by Nets.Page 75 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.2.3.33TxInfOrgnlTxRefSeeSchema1-1 NA Original Transaction ReferenceContains the fields used to identify the original transaction that is beingreferred to.Usage rule: The message elements under ‘Original transaction reference’must be populated with the same value as the message elements of theoriginal instruction, as defined within the following elements.3.2.3.34TxInfOrgnlTxRefIntrBkSttlmAmt18d 3!a 0-1 NA InterBank Settlement AmountNot used by Nets.3.2.3.35TxInfOrgnlTxRefSeeSchema0-1 NA AmountNot used by Nets.Amt3.2.3.363.2.3.37TxInfOrgnlTxRefIntrBkSttlmDtTxInfOrgnlTxRefReqdExctnDtISODate 0-1 NA InterBank Settlement DateNot used by Nets.ISODate 0-1 NA Requested Execution DateNot used by Nets.Page 76 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.2.3.38TxInfOrgnlTxRefReqdColltnDtISODate 0-1 AT-11 Requested Collection DateDate and time at which the creditor requests that the amount of money isto be collected from the debtor.Format: Refer to Pain 008 Section PmtInf/ReqdColltnDt.3.2.3.39TxInfOrgnlTxRefSeeSchema1-1 AT-02 Creditor Scheme IdentificationCredit party that signs the mandate.CdtrSchmeIdThis field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 sectionPmtInf/DrctDbtTxInf/DrctDbtTx/CdtrSchmeId toPmtInf/DrctDbtTxInf/DrctDbtTx/CdtrSchmeId/CtryOfRes.CdtrSchmeId/Id/PrvtId/Othr/Id - This data element is space andcase insensitive3.2.3.40TxInfOrgnlTxRefSeeSchema0-1 Settlement InformationNot used by Nets.SttlmInfPage 77 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.2.3.41TxInfOrgnlTxRefSeeSchema1-1 AT-20AT-21Payment Type InformationContains the fields used to further specify the type of transaction.PmtTpInfAT-59This field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/PmtTpInf toPmtInf/PmtTpInf/CtgyPurp.Among these are:AT-20 Identification code of the scheme:The original service level code - must be “SEPA”.AT-21 Transaction typeValues allowed are CORE or B2B, depending on the relevanttransaction.Also, for sequence type the accepted values are: FRST, OOFF,RCUR, and FNAL.AT-59 Category purpose of the collection3.2.3.42TxInfOrgnlTxRefSeeSchema0-1 NA Payment MethodNot used by Nets.PmtMtdPage 78 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.2.3.43TxInfOrgnlTxRefMndtRltdInfSeeSchema1-1 AT-01AT-16AT-17AT-18Mandate Related InformationContains the fields used to provide further details of the mandate signedbetween the creditor and the debtor.This field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.AT-19AT-24Refer to PAIN.008 sectionPmtInf/DrctDbtTxInf/DrctDbtTx/MndtRltdInf toPmtInf/DrctDbtTxInf/DrctDbtTx/MndtRltdInf/Frqcy.AT-25Among these are:AT-60AT-01: Unique mandate reference:The unique MandateIDThis data element is case insensitiveAT-16: Placeholder for electronic signature data, if applicable.Page 79 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.2.3.44TxInfOrgnlTxRefSeeSchema1-1 Continuing from previous page.AT-17: Type of mandate (paper, e-Mandate).MndtRltdInfAT-18: Identifier of the original creditor who issued the mandateAT-19: Unique mandate reference as given by the original creditor whoissued the mandate.AT-24: Reason for amending the mandate.AT-25Signing date of the mandate:AT-60: Reference of the validation made by the debtor bank.Mandatory fields:TxInf/OrgnlTxRef/MndtRltdInfTxInf/OrgnlTxRef/MndtRltdInf/MndtId (AT-01)TxInf/OrgnlTxRef/MndtRltdInf/DtOfSgntr (AT-25)TxInf/OrgnlTxRef/MndtRltdInf/AmdmntIndPage 80 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.2.3.45TxInfOrgnlTxRefRmtInfSeeSchema0-1 AT-22 Remittance InformationInformation supplied to enable the matching of an entry with the itemsthat the transfer is intended to settle, such as commercial invoices in anaccounts receivable system.This field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/DrctDbtTxInf/RmtInf toPmtInf/DrctDbtTxInf/RmtInf/Strd/AddtlRmtInf.3.2.3.46TxInfOrgnlTxRefSeeSchema0-1 AT-15AT-37Ultimate DebtorUltimate party that owes an amount of money to the (ultimate) creditor.UltmtDbtrThis field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/DrctDbtTxInf/UltmtDbtr toPmtInf/DrctDbtTxInf/UltmtDbtr/CtryOfRes.Among these are:AT-15: Name of the debtor reference party.AT-37: Identification code of the debtor reference party.Page 81 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.2.3.47TxInfOrgnlTxRefSeeSchema1-1 AT-14AT-09DebtorParty that owes an amount of money to the (ultimate) creditor.DbtrAT-27This field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/DrctDbtTxInf/Dbtr toPmtInf/DrctDbtTxInf/Dbtr/CtryOfRes.AT-14: The name of the debtorAT-09: The address of the debtorAT-27: Debtor identification codePage 82 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.2.3.48TxInfOrgnlTxRefDbtrAcct2!a2!n30x 1-1 AT-07 Debtor AccountUnambiguous identification of the debtor’s account.This field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/ DrctDbtTxInf/DbtrAcct/Id toPmtInf/DrctDbtTxInf/DbtrAcct/Id/IBAN.AT-07: Account Number (IBAN) of the debtor.3.2.3.49TxInfOrgnlTxRef4!a2!a2!c[3!c]1-1 AT-13 Debtor AgentFinancial institution that services an account for the debtor.DbtrAgtThis field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/DrctDbtTxInf/ DbtrAgt/FinInstnIdto PmtInf/DrctDbtTxInf/DbtrAgt/FinInstnId/BIC.AT-13: BIC code of the debtor bankPage 83 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.2.3.50TxInfOrgnlTxRefSeeSchema0-1 NA Debtor Agent AccountNot used by Nets.DbtrAgtAcct3.2.3.51TxInfOrgnlTxRef4!a2!a2!c[3!c]0-1 AT-12 Creditor AgentCreditor agent equals creditors bankCdtrAgtFinancial institution that services an account for the creditor.This field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/CdtrAgt toPmtInf/CdtrAgt/BrnchId.AT-12: BIC code of the creditor bank.3.2.3.52TxInfOrgnlTxRefSeeSchema0-1 NA Creditor Agent AccountNot used by Nets.CdtrAgtAcctPage 84 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.2.3.53TxInfOrgnlTxRefSeeSchema1-1 AT-03AT-05CreditorParty to which an amount of money is due.CdtrThis field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/Cdtr/Nm toPmtInf/Cdtr/CtryOfRes.AT-03: The name of the creditorAT-05: The address of the creditor.3.2.3.54TxInfOrgnlTxRefCdtrAcct2!a2!n30x 1-1 AT-04 Creditor AccountUnambiguous identification of the account of the creditor.This field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/CdtrAcct to PmtInf/CdtrAcct/Nm.AT-04: Account number (IBAN) of the creditor.Page 85 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.2.3.55TxInfOrgnlTxRefSeeSchema0-1 AT-15AT-37Ultimate CreditorUltimate party to which an amount of money is due.UltmtCdtrThis field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/DrctDbtTxInf/UltmtCdtr toPmtInf/DrctDbtTxInf/UltmtCdtr/CtryOfRes.AT-15: Name of the debtor reference party.AT-37: Identification code of the debtor reference party.Page 86 of 232

3.3 CAMT.055.001.01PBS Customer payment cancellation file3.3.1 Payment cancellation (cancellation request) – Assignment, Case & Control DataXML Element Format Status RulebookRef.Description / validation rules3.3.1.1Assgnmt See Schema 1-1 NA AssignmentIdentifies the assignment of an investigation case from an assigner to anassignee.3.3.1.2AssgnmtId35x 1-1 NA Assignment identificationUniquely identifies the case assignment.Creditor's unique file reference created by creditor as defined in Section“Description of specific XML tags” in the document Creditor’s user andinformation guide to SEPA Direct Debit.Format: Refer to Pain 008 section GrpHdr/MsgId.E.g.: M12345678CAMT055COR20091211000000013.3.1.33.3.1.4AssgnmtAssgnrAssgnmtAssgnrPtySee Schema 1-1 NA AssignerParty who assigns the case.Usage: - This is also the sender of the message.See Schema 1-1 NA PartyIdentification of a person or organisation.Page 87 of 232

XML Element Format Status RulebookRef.Description / validation rules3.3.1.53.3.1.63.3.1.73.3.1.8AssgnmtAssgnrPtyNmAssgnmtAssgnrPtyPstlAdrAssgnmtAssgnrPtyIdAssgnmtAssgnrPtyIdOrgId70x 0-1 NA Party NameSee Schema 0-1 NA Party Postal AddressName of the party who initiates the cancellation.Not used by Nets.See Schema 0-1 NA Identification of Initiating PartyUnique Identification of an initiating party.See Schema 0-1 NA Organisation Identification of Initiating PartyUnique identification of an initiating party organisation.It cannot be used at the same time as Assgnmt/Assgnr/Pty/Id/PrvtId(below).Usage Rule: Either ‘BIC or BEI’ or one occurrence of ‘Other’ is allowed.Page 88 of 232

XML Element Format Status RulebookRef.Description / validation rules3.3.1.9AssgnmtAssgnr4!a2!a2!c[3!c]0-1 NA BIC or BEI of Initiating PartyBIC or BEI of an initiating party. Used if the initiating party is a bankPtyIdMaximum length: 11OrgIdFormat rule: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}BICOrBEIE.g.: AMBKDKKKXXX3.3.1.10AssgnmtAssgnrPtyIdOrgIdOthrSee Schema 0-1 NA Other Identification of Initiating Party.If SchmeNm/Cd is used, one of the values in the table 8.1. Organisationidentification must be used.Page 89 of 232

XML Element Format Status RulebookRef.Description / validation rules3.3.1.11AssgnmtAssgnrPtyIdPrvtIdSee Schema 0-1 NA Private Identification of the Initiating PartyUnique and unambiguous identification of an initiating party e.g. passport.It cannot be used at the same time as Assgnmt/Assgnr/Pty/Id/OrgId(above).Usage Rule: Either ‘Date and Place of Birth’ or one occurrence of ‘Other’ isallowed.Used if the initiating party is a private person.If SchmeNm/Cd is used, one of the values in the table Privateidentification must used.3.3.1.123.3.1.13AssgnmtAssgnrPtyCtryOfResAssgnmtAssgnrPtyCtctDtls2!a 0-1 NA Country of ResidenceNot used by Nets.See Schema 0-1 NA Contact DetailsNot used by NetsPage 90 of 232

XML Element Format Status RulebookRef.Description / validation rules3.3.1.143.3.1.153.3.1.163.3.1.173.3.1.18AssgnmtAssgnrAgtAssgnmtAssgneAssgnmtAssgnePtyAssgnmtAssgnePtyNmAssgnmtAssgneAgtSee Schema 0-1 NA AgentNot used by Nets.See Schema 1-1 NA AssigneeParty to which the case is assigned.Always NetsSee Schema 0-1 NA PartyIdentification of a person or an organisation.70x 0-1 NA Party NameName of the assignee party.Must always be “Nets” (not validated)See Schema 0-1 NA AgentIdentification of a financial institution.Page 91 of 232

XML Element Format Status RulebookRef.Description / validation rules3.3.1.193.3.1.20AssgnmtAssgneAgtFinInstnIdAssgnmtAssgneAgtFinInstnIdBICSee Schema 0-1 NA Financial Institution of AgentUnique identification of a financial institution.11x 0-1 NA BICBIC of a financial institution.Format:- [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}Must be : PBSEDK213.3.1.21AssgnmtCreDtTmISO DateTime1-1 NA Created Date TimeCreated date time of the Cancellation.3.3.1.223.3.1.23Case See Schema 0-1 NA CaseNot used by Nets.CtrlData See Schema 1-1 NA Control DataProvides details on the number of transactions and the control sum of themessage.3.3.1.24CtrlDataNbOfTxs15n 1-1 NA Number Of TransactionsNumber of individual transactions contained in the message.Format: [0-9]{1,15}Page 92 of 232

XML Element Format Status RulebookRef.Description / validation rules3.3.1.25CtrlDataCtrlSumDecimal 0-1 NA Control SumTotal of all individual amounts included in the message, irrespective ofcurrencies.Format: fractionDigits: 17totalDigits: 183.3.2 Payment cancellation (cancellation request) – original group information and cancelXML Element Format StatusRulebookRef.Description / validation rulesPage 93 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.3.2.13.3.2.2UndrlygOrgnlGrpInfAndCxlUndrlygOrgnlGrpInfAndCxlSee Schema 1-1 NA Original Group InformationInformation related to the original group of transactions, to which themessage refers.35x 0-1 NA Group Cancellation IdentificationNot used by Nets.3.3.2.3GrpCxlIdUndrlygOrgnlGrpInfAndCxlSee Schema 0-1 NA CaseNot used by Nets.3.3.2.4CaseUndrlygOrgnlGrpInfAndCxlOrgnlMsgId35x 1-1 NA Original Message IdentificationThe MessageId of the original file.Format: Refer to Pain 008 section GrpHdr/MsgId.Page 94 of 232

XML Element Format StatusRulebookRef.Description / validation rules3.3.2.5UndrlygOrgnlGrpInfAndCxlOrgnlMsgNmId35x 1-1 NA Original Message Name IdentificationThe type of XML message to be cancelled. SDD Service must always be equal to pain.008* (use of wildcard invalidation).Length: 1-35Content: "pain\.008[A-Za-z0-9\.]{0,27}" or "PAIN\.008[A-Za-z0-9\.]{0,27}"E.g.: pain.008.001.023.3.2.6UndrlygOrgnlGrpInfAndCxlISO DateTime0-1 NA Original Created Date TimeNot used by Nets.OrgnlCreDtTm3.3.2.7UndrlygOrgnlGrpInfAndCxlSee Schema 0-n NA Cancellation Reason InformationNot used by Nets.CxlRsnInfPage 95 of 232

3.3.3 Payment cancellation (cancellation request) –original payment information and cancelXML Element Format StatusRulebookref.Description / validation rulesPage 96 of 232

XML Element Format StatusRulebookref.Description / validation rules3.3.3.13.3.3.23.3.3.33.3.3.43.3.3.5UndrlygOrgnlPmtInfAndCxlUndrlygOrgnlPmtInfAndCxlPmtCxlIdUndrlygOrgnlPmtInfAndCxlCaseUndrlygOrgnlPmtInfAndCxlOrgnlPmtInfIdUndrlygOrgnlPmtInfAndCxlOrgnlGrpInfSee Schema 0-n NA Original Payment Information and CancelSet of elements used to provide information about the original paymentinformation and cancellation information.35x 1-1 NA Payment Cancellation IdentificationSee Schema 0-1 NA CaseUnique identification to identify the cancellation request.Format: Refer to Pain 008 section GrpHdr/MsgId.Not used by Nets.35x 1-1 NA Original Payment Information IdentificationSee Schema 0-1 NA Original Group InformationUnique identifier of the original payment information block, as assigned bythe original sending party.Information concerning the original group of transactions, to which themessage refers.Page 97 of 232

XML Element Format StatusRulebookref.Description / validation rules3.3.3.63.3.3.73.3.3.8UndrlygOrgnlPmtInfAndCxlOrgnlGrpInfOrgnlMsgNmIdUndrlygOrgnlPmtInfAndCxlNbOfTxsUndrlygOrgnlPmtInfAndCxlCtrlSum35x 0-1 NA Original Message Name IdentificationThe type of XML message to be cancelled.SDD Service must always be equal to pain.008* (use of wildcard invalidation).Length: 1-35Content: "pain\.008[A-Za-z0-9\.]{0,27}" or "PAIN\.008[A-Za-z0-9\.]{0,27}"E.g.: pain.008.001.0215n 0-1 NA Number Of TransactionsDecimal 0-1 NA Control SumNumber of individual transactions contained in the message.Format: [0-9]{1,15}Total of all individual amounts included in the message, irrespective ofcurrencies.Format: fractionDigits: 17totalDigits: 18Page 98 of 232

XML Element Format StatusRulebookref.Description / validation rules3.3.3.93.3.3.103.3.3.11UndrlygOrgnlPmtInfAndCxlPmtInfCxlUndrlygOrgnlPmtInfAndCxlCxlRsnInfUndrlygOrgnlPmtInfAndCxlCxlRsnInfBoolean 0-1 NA Payment Information CancellationIndicates whether or not the cancellation applies to a whole group oftransactions or to individual transactions within the original group.If True: Indicates that the cancellation applies to the complete group.If False: Indicates that the cancellation applies to individual items withinthe group.See Schema 0-n NA Cancellation Reason InformationDetailed information on the cancellation reason.See Schema 0-1 NA Cancellation OriginatorParty who isuues the Cancellation request.OrgtrPage 99 of 232

XML Element Format StatusRulebookref.Description / validation rules3.3.3.12UndrlygOrgnlPmtInfAndCxlCxlRsnInf70x 0-1 NA Name of Cancellation OriginatorName of the Party who initiates the cancellation request.Orgtr3.3.3.13NmUndrlygOrgnlPmtInfAndCxlCxlRsnInfSee Schema 0-1 NA Identification of Cancellation OriginatorUnique identification of Cancellation originator.OrgtrId232Page 100 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.14UndrlygOrgnlPmtInfAndCxlCxlRsnInfSee Schema 0-1 NA Organisation Identification of Cancellation OriginatorUnique identification of the organisation who initiates the cancellation.OrgtrId3.3.3.15OrgIdUndrlygOrgnlPmtInfAndCxlCxlRsnInfOrgtr11x 0-1 NA BIC of Cancellation OriginatorBIC of the organisation who initiates the cancellation.Format: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}E.g.: DIRPFRACIdOrgIdBICOrBEI232Page 101 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.19UndrlygOrgnlPmtInfAndCxlTxInfSee Schema 1-n NA Transaction InformationSet of elements used to provide information about the originaltransactions to which the cancelled message refers.3.3.3.203.3.3.21UndrlygOrgnlPmtInfAndCxlTxInfCxlIdUndrlygOrgnlPmtInfAndCxlTxInfOrgnlInstrId35x 1-1 NA Cancellation IdentificationThe cancellation ID of the transaction which is created by the creditor.Length: 1-35.Content: "([A-Za-z0-9]|[\?|/|\-|:|\(|\)|\.|,|'])"E.g. CXL12345678PAIN6COR2009111200000001NB. This field is optional in the XSD, but for Nets it is mandatory.35x 0-1 NA Original Instruction IdentificationNot used by Nets.232Page 103 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.223.3.3.23UndrlygOrgnlPmtInfAndCxlTxInfOrgnlEndToEndIdUndrlygOrgnlPmtInfAndCxlTxInfOrgnlInstdAmt35x 1-1 AT-10 Original End to End IdentificationUnique identification, as assigned by the original initiating party, tounambiguously identify the original transaction.Format: Refer to Pain 008 sectionPmtInf/DrctDbtTxInf/PmtId/EndToEndId.18d 3!a 1-1 AT-06 Original Instructed AmountThe amount money that is moved between debtor and creditor asspecified in the original transaction. The stated amount is excl. thededuction of charges and it is expressed in the currency ordered by theoriginal initiating party.Format: Refer to the Pain 008 sectionPmtInf/DrctDbtTxInf/InstdAmt/Ccy.NB. This field is optional in the XSD, but for Nets it is mandatory.3.3.3.24UndrlygOrgnlPmtInfAndCxlISO DateTime0-1 NA Original Requested Execution DateRequested execution date of the original message.TxInfOrgnlReqdExctnDt232Page 104 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.25UndrlygOrgnlPmtInfAndCxlISO DateTime0-1 NA Original Requested Collection DateRequested collection date of the original message.TxInfOrgnlReqdColltnDt3.3.3.263.3.3.27UndrlygOrgnlPmtInfAndCxlTxInfCxlRsnInfUndrlygOrgnlPmtInfAndCxlTxnInfCxlRsnInfSee Schema 1-1 NA Cancellation Reason InformationContains information about the reason for cancelling the payment.NB. This field is optional in the XSD, but for Nets it is mandatory.See Schema 0-1 NA Cancellation OriginatorParty who isuues the Cancellation request.Orgtr232Page 105 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.28UndrlygOrgnlPmtInfAndCxlTxnInf70x 0-1 NA Name of Cancellation OriginatorName of the Party who initiates the cancellation request.Can not be used at the same time as Originator/Id(see below)CxlRsnInfOrgtr3.3.3.29NmUndrlygOrgnlPmtInfAndCxlTxnInfSee Schema 0-1 NA Identification of Cancellation OriginatorUnique identification of Cancellation originator.Can not be used at the same time as Originator/Nm(see above)CxlRsnInfOrgtrId232Page 106 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.30UndrlygOrgnlPmtInfAndCxlTxnInfSee Schema 0-1 NA Organisation Identification of Cancellation OriginatorUnique identification of the organisation who initiates the cancellation.CxlRsnInfOrgtrIdOrgId3.3.3.31UndrlygOrgnlPmtInfAndCxl4!a2!a2!c[3!c]0-1 NA BIC of Cancellation OriginatorBIC of the organisation who initiates the cancellation.Format: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}TxnInfE.g.: DIRPFRACCxlRsnInfOrgtrIdOrgIdBICOrBEI232Page 107 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.32UndrlygOrgnlPmtInfAndCxlTxnInfSee Schema 1-1 NA Reason For CancellationSpecifies the reason for cancellation.CxlRsnInf3.3.3.33RsnUndrlygOrgnlPmtInfAndCxlTxnInfCxlRsnInf4x {Or NA Cancellation Reason codeReason for the cancellation request in a coded form.Can not be used at the same time as Rsn/Prtry(see below)Ex:- DUPLRsnCd232Page 108 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.34UndrlygOrgnlPmtInfAndCxlTxnInf35x Or} NA Cancellation Reason ProprietaryReason for the cancellation request in a proprietary form.Can not be used at the same time as Rsn/Cd(see above)CxlRsnInfRsn3.3.3.35PrtryUndrlygOrgnlPmtInfAndCxlTxInfOrgnlTxRefSee Schema 1-1 NA Original Transaction ReferenceContains the fields used to identify the original transaction that is beingreferred to.Usage rule: The message elements under ‘Original transaction reference’must be populated by the same value as the message elements of theoriginal instruction, as defined within the following elementsNB. This field and its subfields are optional in the XSD, but for Nets it ismandatory.232Page 109 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.363.3.3.373.3.3.38UndrlygOrgnlPmtInfAndCxlTxInfOrgnlTxRefIntrBkSttlmAmtUndrlygOrgnlPmtInfAndCxlTxInfOrgnlTxRefAmtUndrlygOrgnlPmtInfAndCxlTxInfOrgnlTxRefIntrBkSttlmDt18d 3!a 0-1 NA InterBank Settlement AmountNot used by Nets.See Schema 0-1 NA Amount of Original DDNot used by Nets.ISODate 0-1 NA InterBank Settlement Date of Original DDNot used by Nets.232Page 110 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.393.3.3.40UndrlygOrgnlPmtInfAndCxlTxInfOrgnlTxRefReqdExctnDtUndrlygOrgnlPmtInfAndCxlTxInfOrgnlTxRefReqdColltnDtISODate 0-1 NA Requested Execution Date of Original DDNot used by Nets.ISODate 0-1 AT-11 Requested Collection Date of Original DDDate and time at which creditor requests the amount of money to becollected from debtor.Format: Refer to Pain 008 Section PmtInf/ReqdColltnDt.232Page 111 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.41UndrlygOrgnlPmtInfAndCxlTxInfOrgnlTxRefCdtrSchmeIdSee Schema 1-1 AT-02 Creditor Scheme IdentificationCredit party that signs the mandate.Usage rule: It is recommended that all transactions within the same‘Payment information’ block have the same ‘Creditor schemeidentification’. Check section “Creditor scheme identification format” in inthe document Creditor’s user and information guide to SEPA Direct DebitThis field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.3.3.3.42UndrlygOrgnlPmtInfAndCxlTxInfOrgnlTxRefSttlmInfSee Schema 0-1 NA Settlement informationRefer to PAIN.008 sectionPmtInf/DrctDbtTxInf/DrctDbtTx/CdtrSchmeId toPmtInf/DrctDbtTxInf/DrctDbtTx/CdtrSchmeId/CtryOfRes.CdtrSchmeId/Id/PrvtId/Othr/Id - This data element is space andcase insensitiveNot used by Nets.232Page 112 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.43UndrlygOrgnlPmtInfAndCxlSee Schema 1-1 AT-20AT-21AT-59Payment Type InformationSet of tags used to further specify the original transaction type.TxInfOrgnlTxRefThis field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.PmtTpInfRefer to PAIN.008 section PmtInf/PmtTpInf toPmtInf/PmtTpInf/CtgyPurp.Mandatory fields:TxInfAndSts/OrgnlTxRef/PmtTpInfTxInfAndSts/OrgnlTxRef/PmtTpInf/SvcLvlTxInfAndSts/OrgnlTxRef/PmtTpInf/SvcLvl/cd (AT-20 – will be ”SEPA”)TxInfAndSts/OrgnlTxRef/PmtTpInf/LclInstrmTxInfAndSts/OrgnlTxRef/PmtTpInf/LclInstrm/cd (AT-20 – will be CORE orB2B)TxInfAndSts/OrgnlTxRef/PmtTpInf/ SeqTp (AT-21)Among these are:AT-20: Identification code of the scheme:The original service level code - must be “SEPA”.Values allowed are CORE or B2B, depending on the relevanttransaction.AT-21: Transaction type232.Also, for sequence type the accepted values are: FRST, OOFF,RCUR, and FNAL.Page 113 ofAT-59: Category purpose of the collection.

XML Element Format StatusRulebookref.Description / validation rules3.3.3.44UndrlygOrgnlPmtInfAndCxlTxInfOrgnlTxRefPmtMtdSee Schema 0-1 NA Payment MethodNot used by Nets.232Page 114 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.45UndrlygOrgnlPmtInfAndCxlTxInfSee Schema 1-1 AT-01AT-16AT-17AT-18Mandate related informationSet of tags used to provide further details of the mandate signed bycreditor and debtor.This field must contain the matching fields which contain exactly the samevalues as the fields contained in the original transaction.OrgnlTxRefMndtRltdInfAT-19AT-24Refer to PAIN.008 sectionPmtInf/DrctDbtTxInf/DrctDbtTx/MndtRltdInf toPmtInf/DrctDbtTxInf/DrctDbtTx/MndtRltdInf/Frqcy.AT-25Among these are:AT-60AT-01: Unique mandate reference:The unique MandateIDThis data element is case insensitiveAT-16: Placeholder for electronic signature data, if applicable.AT-17: Type of mandate (paper, e-Mandate).AT-18: Identifier of the original creditor who issued the mandateAT-19: Unique mandate reference as given by the original creditor whoissued the mandate.AT-24: Reason for amending the mandate.232Page 115 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.46UndrlygOrgnlPmtInfAndCxlTxInfOrgnlTxRefMndtRltdInfSee Schema 1-1 Continuing from previous page.AT-25Signing date of the mandate.AT-60: Reference of the validation made by the debtor bank.Mandatory fields:Undrlyg/OrgnlPmtInfAndCxl/TxInf/OrgnlTxRef/MndtRltdInfUndrlyg/OrgnlPmtInfAndCxl/TxInf/OrgnlTxRef/MndtRltdInf/MndtId (AT-01)Undrlyg/OrgnlPmtInfAndCxl/TxInf/OrgnlTxRef/MndtRltdInf/DtOfSgntr (AT-25)Undrlyg/OrgnlPmtInfAndCxl/TxInf/OrgnlTxRef/MndtRltdInf/AmdmntInd3.3.3.47UndrlygOrgnlPmtInfAndCxlTxInfOrgnlTxRefRmtInfSee Schema 0-1 AT-22 Remittance InformationInformation supplied to enable the matching of an entry with the itemsthat the transfer is intended to settle, such as commercial invoices in anaccounts receivable system.This field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/DrctDbtTxInf/RmtInf toPmtInf/DrctDbtTxInf/RmtInf/Strd/AddtlRmtInf.232Page 116 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.48UndrlygOrgnlPmtInfAndCxlSee Schema 0-1 AT-15AT-37Ultimate DebtorUltimate party that owes an amount of money to the (ultimate) creditor.TxInfOrgnlTxRefThis field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.UltmtDbtrRefer to PAIN.008 section PmtInf/DrctDbtTxInf/UltmtDbtr toPmtInf/DrctDbtTxInf/UltmtDbtr/CtryOfRes.Among these are:AT-15:AT-37:Name of the debtor reference party.Identification code of the debtor reference party.232Page 117 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.49UndrlygOrgnlPmtInfAndCxlSee Schema 1-1 AT-14AT-09AT-27DebtorParty that owes an amount of money to the (ultimate) creditor.TxInfOrgnlTxRefThis field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.DbtrRefer to PAIN.008 section PmtInf/DrctDbtTxInf/Dbtr toPmtInf/DrctDbtTxInf/Dbtr/CtryOfRes.AT-14:AT-09:The name of the debtorThe address of the debtorAddress line can have a maximum of two occurrences:ooCountry of the debtor’s address.Must be a valid country code.AT-27:Debtor identification code.232Page 118 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.50UndrlygOrgnlPmtInfAndCxlTxInfOrgnlTxRefDbtrAcct2!a2!n30x 1-1 AT-07 Debtor AccountUnambiguous identification of the debtor’s account.This field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/ DrctDbtTxInf/DbtrAcct/Id toPmtInf/DrctDbtTxInf/DbtrAcct/Id/IBAN.AT-07:Account number (IBAN) of the debtor. First two characters must be a valid country code.232Page 119 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.51UndrlygOrgnlPmtInfAndCxl4!a2!a2!c[3!c]1-1 AT-13 Debtor AgentFinancial institution servicing an account for the debtor.TxInfOrgnlTxRefThis field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.DbtrAgtRefer to PAIN.008 section PmtInf/ DrctDbtTxInf/ DbtrAgt/FinInstnIdto PmtInf/DrctDbtTxInf/DbtrAgt/FinInstnId/BIC.AT-13:BIC code of the debtor bank.3.3.3.52UndrlygOrgnlPmtInfAndCxlTxInfOrgnlTxRefDbtrAgtAcctSee Schema 0-1 NA Debtor Agent AccountNot used by Nets.232Page 120 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.53UndrlygOrgnlPmtInfAndCxl4!a2!a2!c[3!c]0-1 AT-12 Creditor AgentFinancial institution servicing an account for the creditor.TxInfOrgnlTxRefThis field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.CdtrAgtRefer to PAIN.008 section PmtInf/CdtrAgt toPmtInf/CdtrAgt/BrnchId.AT-12:BIC code of the creditor bank.3.3.3.54UndrlygOrgnlPmtInfAndCxlTxInfOrgnlTxRefCdtrAgtAcctSee Schema 0-1 NA Creditor Agent AccountNot used by Nets.232Page 121 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.55UndrlygOrgnlPmtInfAndCxlSee Schema 1-1 AT-03AT-05CreditorParty to which an amount of money is due.TxInfOrgnlTxRefThis field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.CdtrRefer to PAIN.008 section PmtInf/Cdtr/Nm toPmtInf/Cdtr/CtryOfRes.AT-03:AT-05:The name of the creditor.The address of the creditor:The address line can have a maximum of two occurrences.232Page 122 of

XML Element Format StatusRulebookref.Description / validation rules3.3.3.56UndrlygOrgnlPmtInfAndCxlTxInfOrgnlTxRefCdtrAcct2!a2!n30x 1-1 AT-04 Creditor accountUnambiguous identification of the creditor’s account.This field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/CdtrAcct to PmtInf/CdtrAcct/Nm.AT-04:Account number (IBAN) of the creditor.3.3.3.57UndrlygOrgnlPmtInfAndCxlSee Schema 0-1 AT-15AT-37Ultimate CreditorUltimate party to which an amount of money is due.TxInfOrgnlTxRefThis field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.UltmtCdtrRefer to PAIN.008 section PmtInf/DrctDbtTxInf/UltmtCdtr toPmtInf/DrctDbtTxInf/UltmtCdtr/CtryOfRes.AT-15:AT-37:Name of the debtor reference party.Identification code of the debtor reference party.232Page 123 of

232Page 124 of

3.4 PAIN.002.001.03 Customer counterparty reject file (Status file)3.4.1 Reject payment (rejection request) – group headerXML Element Format Status Rule BookRef.Description / validation rules3.4.1.1GrpHdr See Schema 1-1 NA Group HeaderContains common information about the rejected payment.3.4.1.2GrpHdrMsgId35x 1-1 NA Message IdentificationUnique file reference created by the Sending party (debtor bank).The identification cannot include leading, trailing or internal spaces.Length: 1-35.Content: "([A-Za-z0-9]|[\?|/|\-|:|\(|\)|\.|,|'])3.4.1.3GrpHdrCreDtTmISO Datetime1-1 NA Created Date TimeThe date and time when this file was created by Nets.Format: Refer to Pain 008 section GrpHdr/CreDtTm.3.4.1.43.4.1.53.4.1.6GrpHdrInitgPtyGrpHdrFwdgAgtGrpHdrDbtrAgtSee Schema 0-1 NA Initiating PartyNot used by Nets.See Schema 0-1 NA Forwarding AgentNot used by Nets.See Schema 0-1 NA Debtor AgentNot used by Nets.232Page 125 of

XML Element Format Status Rule BookRef.Description / validation rules3.4.1.7GrpHdrCdtrAgtSee Schema 0-1 NA Creditor AgentNot used by Nets.232Page 126 of

3.4.2 Reject payment (rejection request) – original group informationXML Element Format Status Rulebookref.Description / validation rules3.4.2.1OrgnlGrpInfAndSts See Schema 1-1 NA Original Group Information and StatusOriginal group information concerning the group of transactions, to whichthe status report message refers to.3.4.2.23.4.2.3OrgnlGrpInfAndStsOrgnlMsgIdOrgnlGrpInfAndStsOrgnlMsgNmId35x 1-1 NA Original Message IdentificationUnique identification assigned by Nets to identify the message.E.g.: 000000000000000135x 1-1 NA Original Message Name IdentificationSpecifies the original message name identifier to which the message refers.E.g.:pain.008.001.023.4.2.4OrgnlGrpInfAndStsOrgnlCreDtTmISO DateTime0-1 NA Original Created Date TimeNot used by Nets.3.4.2.53.4.2.6OrgnlGrpInfAndStsOrgnlNbOfTxsOrgnlGrpInfAndStsOrgnlCtrlSum15!n 0-1 NA Original Number of TransactionsNot used by Nets.Decimal 0-1 NA Original Control SumNot used by Nets.232Page 127 of

XML Element Format Status Rulebookref.Description / validation rules3.4.2.73.4.2.83.4.2.93.4.2.10OrgnlGrpInfAndStsGrpStsOrgnlGrpInfAndStsStsRsnInfOrgnlGrpInfAndStsStsRsnInfOrgtrOrgnlGrpInfAndStsStsRsnInfRsnSee Schema 0-1 NA Group StatusSpecifies the status of a group of transactions.Usage rule: It will always be filled with the code ‘PART’.E.g.: PARTSee Schema 0-n NA Status Reason InformationSee Schema 0-1 R2 Status OriginatorSet of elements used to provide detailed information on the status reason.Usage Rule: ‘Status Reason Information’ may be present either in ‘OriginalGroup Information And Status’ or in ‘Transaction Information and Status’.Party that issues the status.See Schema 0-1 R3 Status ReasonR2: Identification of the type of party that initiated the rejectUsage Rule: Limited to BIC to identify the bank or CSM originating thestatus or ‘Name’ to indicate a CSM when it has no BIC.Specifies the reason for the status report.R3: Reason code for non-acceptance of the Collection232Page 128 of

XML Element Format Status Rulebookref.Description / validation rules3.4.2.113.4.2.123.4.2.133.4.2.14OrgnlGrpInfAndStsStsRsnInfRsnCdOrgnlGrpInfAndStsStsRsnInfRsnPrtryOrgnlGrpInfAndStsStsRsnInfAddtlInfOrgnlGrpInfAndStsNbOfTxsPerSts4x {Or NA Status Reason CodeReason for the status, as published in an external reason code list.35x Or} NA Status Reason ProprietaryReason for the status reason as a proprietary code.105x 0-n NA Additional InformationNot used by Nets.See Schema 0-n NA Number of Transactions Per StatusNot used by Nets.232Page 129 of

3.4.3 Reject payment (rejection request) – transaction informationXML Element Format Status Rulebookref.Description / validation rules3.4.3.1OrgnlPmtInfAndStsSeeSchema0-n NA Original Payment Information and StatusInformation concerning the original payment information, to which thestatus report message refers.3.4.3.23.4.3.33.4.3.43.4.3.5OrgnlPmtInfAndStsOrgnlPmtInfIdOrgnlPmtInfAndStsOrgnlNbOfTxsOrgnlPmtInfAndStsOrgnlCtrlSumOrgnlPmtInfAndStsPmtInfSts35x 1-1 NA Original Payment Information IdentificationUnique identification, as assigned by the original sending party, tounambiguously identify the original payment information group.15n 0-1 NA Original Number of TransactionsNumber of individual transactions contained in the original paymentinformation group.Format:- [0-9]{1,15}Decimal 0-1 NA Original Control SumTotal of all individual amounts included in the original paymentinformation group, irrespective of currencies.4x 0-1 NA Payment Information StatusWill always be “PART”232Page 130 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.6OrgnlPmtInfAndStsStsRsnInfSeeSchema0-n NA Status Reason InformationSet of elements used to provide detailed information on the statusreason.Usage Rule: ‘Status Reason Information’ may be present either in‘Original Group Information And Status’ or in ‘Transaction Informationand Status’.Not Used by Nets3.4.3.7OrgnlPmtInfAndStsStsRsnInfOrgtrSeeSchema0-1 R2 Status OriginatorParty that issues the status.R2: Identification of the type of party that initiated the rejectUsage Rule: Limited to BIC to identify the bank or CSM originating thestatus or ‘Name’ to indicate a CSM when it has no BIC.Not used by Nest3.4.3.8OrgnlPmtInfAndStsStsRsnInfRsnSeeSchema0-1 R3 Status ReasonSpecifies the reason for the status report.R3: Reason code for non-acceptance of the CollectionNot used by Nets232Page 131 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.9OrgnlPmtInfAndStsStsRsnInfRsnCd4x {Or NA Status Reason CodeReason for the status, as published in an external reason code list.Not used by Nets3.4.3.103.4.3.11OrgnlPmtInfAndStsStsRsnInfRsnPrtryOrgnlPmtInfAndStsAddtlInf35x Or} NA Status Reason ProprietaryReason for the status, as a proprietary code.Not Used by Nets105x 0-n NA Additional InformationNot used by Nets3.4.3.12OrgnlPmtInfAndStsNbOfTxsPerStsSeeSchema0-n NA Number of Transaction Per StatusNot used by Nets.3.4.3.13OrgnlPmtInfAndStsTxInfAndStsSeeSchema1-n NA Transaction Information and StatusInformation concerning the original transactions to which the counterparty reject message refers.232Page 132 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.143.4.3.153.4.3.16OrgnlPmtInfAndStsTxInfAndStsStsIdOrgnlPmtInfAndStsTxInfAndStsOrgnlInstrIdOrgnlPmtInfAndStsTxInfAndStsOrgnlEndToEndId35x 1-1 R5 Status Identification of the rejectUnique identification, as assigned by an instructing party for an instructedparty, to unambiguously identify the counterparty reject message.R5: Specific reference of the bank that initiated the reject.E.g.: 1196.135x 0-1 NA Original Instruction IdentificationNot used by Nets.35x 1-1 AT-10 Original End to End IdentificationUnique identification, as assigned by the creditor as the original initiatingparty, to unambiguously identify the original transaction.Format: Refer to Pain 008 sectionPmtInf/DrctDbtTxInf/PmtId/EndToEndId.3.4.3.17OrgnlPmtInfAndStsTxInfAndStsTxStsSeeSchema1-1 NA Transaction StatusSpecifies the status of the transaction.Usage rule: ‘Transaction status’ will always be filled with the code ‘RJCT’.E.g.: RJCT232Page 133 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.18OrgnlPmtInfAndStsTxInfAndStsSeeSchema1-1 NA Status Reason Information of the RejectSet of fields used to provide detailed information about the status reasonof the reject.StsRsnInf3.4.3.19OrgnlPmtInfAndStsTxInfAndStsStsRsnInfSeeSchema1-1 R2 Status Originator of the RejectParty that issued the reject.R2: Identification of the type of party that initiated the rejectOrgtrEither the Nm tag or the OrgId tag is filled, depending on whether thedebtor or the debtor’s bank is the originator of the reject.3.4.3.20OrgnlPmtInfAndStsTxInfAndStsStsRsnInfOrgtrNm70x 0-1 R2 Status Originator Name of the RejectName of the party that issued the reject, if this is the debtor.It cannot be used at the same time ifTxInfAndSts/StsRsnInf/Orgtr/Id/OrgId is used.E.g.: Peter Soerensen232Page 134 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.21OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-1 R2 Status Originator Identification of the RejectUnique identification of the party that issued the reject, if this is thedebtor’s bank.StsRsnInfOrgtrId3.4.3.22OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-1 R2 Status Originator Organisation Identification of the RejectUnique identification of the organisation of the party that issued thereject, if this is the debtor’s bank.StsRsnInfOrgtrIdOrgId232Page 135 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.23OrgnlPmtInfAndStsTxInfAndStsStsRsnInfOrgtrIdOrgIdBICOrBEI11x 0-1 R2 BIC of the Status Originator of the RejectMaximum length: 11Format rule: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}Bic of the Debtor bankIt cannot be used at the same time as TxInfAndSts/StsRsnInf/Orgtr/NmE.g.: AMBKDKKKXXX3.4.3.24OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-1 R2 Private Identification of Status Originator of the RejectNot used by Nets.StsRsnInfOrgtrIdPrvtId3.4.3.25OrgnlPmtInfAndStsTxInfAndStsSeeSchema1-1 R3 Status Reason of the RejectSpecifies the reason for the status report.StsRsnInfRsnR3: Reason code for non-acceptance of the collection.232Page 136 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.26OrgnlPmtInfAndStsTxInfAndStsSeeSchema{Or NA Status Reason Code of the RejectSpecifies the reason for the rejection by the debtor bank or the refusal bythe debtor.StsRsnInfRsnIt cannot be used at the same time as StsRsn/PrtryCdFor allowed values, check the table Transaction level error codesE.g.: AC013.4.3.273.4.3.28OrgnlPmtInfAndStsTxInfAndStsStsRsnInfRsnPrtryOrgnlPmtInfAndStsTxInfAndStsStsRsnInfAddtlInf35x Or} NA Status Reason Proprietary of the RejectSpecifies the reason for the status in a proprietary form.It cannot be used at the same time as StsRsn/CdCurrently not used by Nets105x 0-1 NA Additional Information of the RejectNot used by Nets.232Page 137 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.29OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-1 NA Charges InformationNot used by Nets.ChrgsInf3.4.3.30OrgnlPmtInfAndStsTxInfAndStsISO DateTime0-1 NA Acceptance Date TimeNot used by Nets.AccptncDtTm3.4.3.313.4.3.32OrgnlPmtInfAndStsTxInfAndStsAcctSvcrRefOrgnlPmtInfAndStsTxInfAndStsClrSysRef35x 0-1 NA Account Servicer ReferenceNot used by Nets.35x 0-1 NA Clearing System ReferenceNot used by Nets.232Page 138 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.33OrgnlPmtInfAndStsTxInfAndStsSeeSchema1-1 NA Original Transaction ReferenceSet of key fields used to identify the original transaction that is beingreferred to.OrgnlTxRefUsage rule: The message elements under ‘Original transaction reference’will be populated with the same value as the message elements of theoriginal instruction, as defined within the following elements.3.4.3.34OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefSeeSchema1-1 AT-06 AmountThe amount of money that is to be transferred between debtor andcreditor as specified in the original transaction. The stated amount is excl.the deduction of charges and it is expressed in the currency ordered bythe original initiating party.AmtFormat: Refer to pain.008 section PmtInf/DrctDbtTxInf/InstdAmtMandatory fields:TxInfAndSts/OrgnlTxRef/AmtTxInfAndSts/OrgnlTxRef/Amt/InstdAmt/@Ccy3.4.3.35OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefReqdColltnDtISODate 1-1 AT-11 Requested Collection DateDate and time when the creditor requests that the amount of money is tobe collected from the debtor in the original transaction.Format: Refer to Pain 008 Section PmtInf/ReqdColltnDt.232Page 139 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.36OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefReqdExctnDtISODate 0-1 NA Requested Execution DateNot used by Nets.232Page 140 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.37OrgnlPmtInfAndStsTxInfAndStsSeeSchema1-1 AT-02 Creditor Scheme IdentificationThe credit party that signs the mandate.OrgnlTxRefCdtrSchmeIdUsage rule: It is recommended that all transactions within the same‘Payment information’ block have the same ‘Creditor schemeidentification’. Check section “Creditor scheme identification format” in inthe document Creditor’s user and information guide to SEPA Direct DebitThis field will contain the matching fields which contain exactly the samevalues as the fields contained in the original transaction.Refer to PAIN.008 sectionPmtInf/DrctDbtTxInf/DrctDbtTx/CdtrSchmeId toPmtInf/DrctDbtTxInf/DrctDbtTx/CdtrSchmeId/CtryOfResMandatory fields:TxInfAndSts/OrgnlTxRef/CdtrSchmeIdTxInfAndSts/OrgnlTxRef/CdtrSchmeId/IdTxInfAndSts/OrgnlTxRef/CdtrSchmeId/Id/PrvtId (AT-02)CdtrSchmeId/Id/PrvtId/Othr/Id - This data element is space andcase insensitiveAT-02:The identifier of the creditor.232Page 141 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.38OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefPmtTpInfSeeSchema0-1 AT-20AT-21AT-59Payment Type InformationSet of tags used to further specify the original transaction type.This field will contain the matching fields which contain exactly the samevalues as the fields contained in the original transaction.Refer to PAIN.008 section PmtInf/PmtTpInf toPmtInf/PmtTpInf/CtgyPurp.Mandatory fields:TxInfAndSts/OrgnlTxRef/PmtTpInfTxInfAndSts/OrgnlTxRef/PmtTpInf/SvcLvlTxInfAndSts/OrgnlTxRef/PmtTpInf/SvcLvl/cd (AT-20 – will be ”SEPA”)TxInfAndSts/OrgnlTxRef/PmtTpInf/LclInstrmTxInfAndSts/OrgnlTxRef/PmtTpInf/LclInstrm/cd (AT-20 – will be CORE orB2B)TxInfAndSts/OrgnlTxRef/PmtTpInf/ SeqTp (AT-21)AT-20: Identification code of the scheme:The original service level code - will be “SEPA”.232AT-21Values allowed are CORE or B2B, depending on the relevanttransaction.Transaction typePage 142 ofAlso, for sequence type the accepted values are: FRST, OOFF,RCUR, and FNAL.

XML Element Format Status Rulebookref.Description / validation rules3.4.3.39OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-1 NA Payment MethodNot used by Nets.OrgnlTxRefPmtMtd232Page 143 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.40OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefMndtRltdInfSeeSchema1-1 AT-01AT-16AT-17AT-18AT-19AT-24Mandate Related InformationSet of tags used to provide further details of the mandate signed bycreditor and debtor.This field will contain the matching fields which contain exactly the samevalues as the fields contained in the original transaction.Refer to PAIN.008 sectionPmtInf/DrctDbtTxInf/DrctDbtTx/MndtRltdInf toPmtInf/DrctDbtTxInf/DrctDbtTx/MndtRltdInf/Frqcy.AT-25AT-60AT-01: Unique mandate reference:The unique MandateIDThis data element is case insensitiveAT-16: Placeholder for the electronic signature data, if applicable.AT-17: Type of mandate (paper, e-Mandate).AT-18: Identifier of the original creditor who issued the mandateAT-19: Unique mandate reference as given by the original creditor whoissued the mandate.AT-24: Reason for amending the mandate.232Page 144 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.41OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefMndtRltdInfSeeSchema1-1 Continuing from previous page.AT-25Signing date of the mandate.AT-60: Reference of the validation made by the debtor bank.Mandatory fields:OrgnlPmtInfAndSts/TxInfAndSts/OrgnlTxRef/MndtRltdInfOrgnlPmtInfAndSts/TxInfAndSts/OrgnlTxRef/MndtRltdInf/MndtId (AT-01)OrgnlPmtInfAndSts/TxInfAndSts/OrgnlTxRef/MndtRltdInf/DtOfSgntr (AT-25)OrgnlPmtInfAndSts/TxInfAndSts/OrgnlTxRef/MndtRltdInf/AmdmntInd3.4.3.42OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefSeeSchema0-1 AT-22 Remittance InformationInformation supplied to enable the matching of an entry with the itemsthat the transfer is intended to settle, such as commercial invoices in anaccounts receivable system.RmtInfThis field will contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/DrctDbtTxInf/RmtInf toPmtInf/DrctDbtTxInf/RmtInf/Strd/AddtlRmtInf.232Page 145 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.43OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-1 AT-15AT-37Ultimate DebtorUltimate party that owes an amount of money to the (ultimate) creditor.OrgnlTxRefUltmtDbtrThis field will contain the matching fields which contain exactly the samevalues as the fields contained in the original transaction.Refer to PAIN.008 section PmtInf/DrctDbtTxInf/UltmtDbtr toPmtInf/DrctDbtTxInf/UltmtDbtr/CtryOfRes.AT-15: Name of the debtor reference party.AT-37: Identification code of the debtor reference party.232Page 146 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.44OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefDbtrSeeSchema1-1 AT-14AT-09AT-27DebtorParty that owes an amount of money to the (ultimate) creditor.This field will contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/DrctDbtTxInf/Dbtr toPmtInf/DrctDbtTxInf/Dbtr/CtryOfRes.Mandatory fields:TxInfAndSts/OrgnlTxRef/DbtrTxInfAndSts/OrgnlTxRef/Dbtr/Nm (AT-14)AT-14: The name of the debtorAT-09: The address of the debtorAT-27: Debtor identification code232Page 147 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.45OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefDbtrAcct2!a2!n30x 1-1 AT-07 Debtor AccountUnambiguous identification of the debtor’s account.This field will contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/ DrctDbtTxInf/DbtrAcct/Id toPmtInf/DrctDbtTxInf/DbtrAcct/Id/IBAN.Mandatory fields:TxInfAndSts/OrgnlTxRef/DbtrAcctTxInfAndSts/OrgnlTxRef/DbtrAcct/IdTxInfAndSts/OrgnlTxRef/DbtrAcct/Id/IBAN (AT-07)AT-07:Account number (IBAN) of the debtor.232Page 148 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.46OrgnlPmtInfAndStsTxInfAndSts4!a2!a2!c[3!c]1-1 AT-13 Debtor AgentFinancial institution servicing an account for the debtor.OrgnlTxRefDbtrAgtThis field will contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/ DrctDbtTxInf/DbtrAgt/FinInstnId toPmtInf/DrctDbtTxInf/DbtrAgt/FinInstnId/BIC.Mandatory fields:TxInfAndSts/OrgnlTxRef/DbtrAgtTxInfAndSts/OrgnlTxRef/DbtrAgtc/FinInstnIdTxInfAndSts/OrgnlTxRef/DbtrAgt/FinInstnId/BIC (AT-13)AT-13: BIC code of the debtor bank232Page 149 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.47OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-1 NA Debtor Agent AccountNot used by Nets.OrgnlTxRefDbtrAgtAcct3.4.3.48OrgnlPmtInfAndStsTxInfAndSts4!a2!a2!c[3!c]1-1 AT-12 Creditor AgentFinancial institution servicing an account for the creditor.OrgnlTxRefCdtrAgtThis field will contain the matching fields which contain exactly the samevalues as the fields contained in the original transaction.Refer to PAIN.008 section PmtInf/CdtrAgt toPmtInf/CdtrAgt/BrnchId.Mandatory fields:TxInfAndSts/OrgnlTxRef/CdtrAgtTxInfAndSts/OrgnlTxRef/CdtrAgt/FinInstnIdTxInfAndSts/OrgnlTxRef/CdtrAgt/FinInstnId/BIC (AT-12)AT-12: BIC code of the creditor bank.232Page 150 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.49OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-1 NA Creditor Agent AccountNot used by Nets.OrgnlTxRefCdtrAgtAcct3.4.3.50OrgnlPmtInfAndStsTxInfAndStsSeeSchema1-1 AT-03AT-05CreditorParty to which an amount of money is due.OrgnlTxRefCdtrThis field will contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/Cdtr/Nm toPmtInf/Cdtr/CtryOfRes.Mandatory fields:TxInfAndSts/OrgnlTxRef/CdtrTxInfAndSts/OrgnlTxRef/Cdtr/Nm (AT-03)AT-03: The name of the creditor.AT-05: The address of the creditor.232Page 151 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.51OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefCdtrAcct2!a2!n30x 1-1 AT-04 Creditor AccountUnambiguous identification of the account of the creditor.This field will contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/CdtrAcct to PmtInf/CdtrAcct/Nm.Mandatory fields:TxInfAndSts/OrgnlTxRef/CdtrAcctTxInfAndSts/OrgnlTxRef/CdtrAcct/IdTxInfAndSts/OrgnlTxRef/CdtrAcct/Id/IBAN (AT-04)AT-04: Account number (IBAN) of the creditor.232Page 152 of

XML Element Format Status Rulebookref.Description / validation rules3.4.3.52OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-1 AT-38AT-39Ultimate CreditorUltimate party to which an amount of money is due.OrgnlTxRefUltmtCdtrThis field will contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/DrctDbtTxInf/UltmtCdtr toPmtInf/DrctDbtTxInf/UltmtCdtr/CtryOfRes.AT-38: The name of the creditor reference party.AT-39: The identification code of the creditor reference party.232Page 153 of

3.5 PAIN.002.001.03 Customer bookkeeping file3.5.1 Bookkeeping file – group headerXML Element Format Status Rulebookref.Description / validation rules3.5.1.1GrpHdrSeeSchema1-1 NA Group HeaderContains common information about the bookkeeping file.3.5.1.2GrpHdrMsgId35x 1-1 NA Message IdentificationUnique file reference created by Nets.The identification cannot include leading, trailing or internal spaces.Length: 1-35.Content: "([A-Za-z0-9]|[\?|/|\-|:|\(|\)|\.|,|'])3.5.1.3GrpHdrCreDtTmISO Datetime1-1 NA Created Date TimeThe date and time when this file was created by Nets.Format: Refer to Pain 008 section GrpHdr/CreDtTm.3.5.1.4GrpHdrInitgPtySeeSchema0-1 NA Initiating PartyNot used by Nets.3.5.1.5GrpHdrFwdgAgtSeeSchema0-1 NA Forwarding AgentNot used by Nets.232Page 154 of

3.5.2 Bookkeeping file – original group information and statusXML Element Format Status Rule BookRef.Description / validation rules3.5.2.1OrgnlGrpInfAndSts See Schema 1-1 NA Original Group Information and StatusNB. The content of original group information and status are not relevantto the fields in the bookkeeping file, so the fields are filled with nonref.3.5.2.23.5.2.3OrgnlGrpInfAndStsOrgnlMsgIdOrgnlGrpInfAndStsOrgnlMsgNmId35x 1-1 NA Original Message IdentificationThere is no reference to the original bulk, as the book keeping bulks arenot related to any bulks received from and sent to Creditors earlier, sothe value “NONREF” will be presentWill always be NONREF35x 1-1 NA Original Message Name IdentificationThere is no reference to the original bulk, as the book keeping bulks arenot related to any bulks received from and sent to Creditors earlier, sothe value “NONREF” will be presentWill always be NONREF3.5.2.4OrgnlGrpInfAndStsOrgnlCreDtTmISO DateTime0-1 NA Original Created Date TimeNot used by Nets.3.5.2.53.5.2.6OrgnlGrpInfAndStsOrgnlNbOfTxsOrgnlGrpInfAndStsOrgnlCtrlSum15!n 0-1 NA Original Number of TransactionsNot used by Nets.Decimal 0-1 NA Original Control SumNot used by Nets.232Page 156 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.2.123.5.2.133.5.2.143.5.2.153.5.2.16OrgnlGrpInfAndStsStsRsnInfRsnOrgnlGrpInfAndStsStsRsnInfRsnCdOrgnlGrpInfAndStsStsRsnInfRsnPrtryOrgnlGrpInfAndStsStsRsnInfAddtlInfOrgnlGrpInfAndStsNbOfTxsPerStsSee Schema 0-1 R3 Status ReasonNot used by Nets.See Schema {Or NA Status Reason CodeNot used by Nets.35x Or} NA Status Reason ProprietaryNot used by Nets.105x 0-1 NA Additional InformationNot used by Nets.See Schema 0-1 NA Number of Transactions Per StatusNot used by Nets.232Page 158 of

3.5.3 Bookkeeping file – transaction information and statusXML Element Format Status Rule BookRef.Description / validation rules3.5.3.1OrgnlPmtInfAndSts See Schema 0-n NA Original Payment Information and StatusInformation concerning the original payment information, to which thebookkeeping message refers.3.5.3.23.5.3.33.5.3.4OrgnlPmtInfAndStsOrgnlPmtInfIdOrgnlPmtInfAndStsOrgnlNbOfTxsOrgnlPmtInfAndStsOrgnlCtrlSum35x 1-1 NA Original Payment Information IdentificationUnique identification, as assigned by the original sending party, tounambiguously identify the original payment information group.This field will contain one of the following options:Content of PmtInf/PmtInfId pain.008 for a settled Direct DebitContent of the OrgnlGrpInf/OrgnlMsgId from pain.007 if a SettledReversal originated from a creditor file.Contain “NONREF” if there is no information present to fill the field.15n 0-1 NA Original Number of TransactionsNumber of individual transactions contained in the “OrgnlPmtInfAndSts”tagFormat:- [0-9]{1,15}Decimal 0-1 NA Original Control SumTotal of all individual amounts included in the “OrgnlPmtInfAndSts” tag.232Page 159 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.53.5.3.63.5.3.73.5.3.83.5.3.9OrgnlPmtInfAndStsPmtInfStsOrgnlPmtInfAndStsStsRsnInfOrgnlPmtInfAndStsStsRsnInfOrgtrOrgnlPmtInfAndStsStsRsnInfRsnOrgnlPmtInfAndStsStsRsnInfRsnCd4x 0-1 NA Payment Information StatusSpecifies the status of the payment information group.Will always be: PARTSee Schema 0-n NA Status Reason InformationNot used by Nets.See Schema 0-1 R2 Status OriginatorNot used by Nets.See Schema 0-1 R3 Status ReasonNot used by Nets.4x {Or NA Status Reason CodeNot used by Nets.232Page 160 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.103.5.3.113.5.3.123.5.3.133.5.3.14OrgnlPmtInfAndStsStsRsnInfRsnPrtryOrgnlPmtInfAndStsAddtlInfOrgnlPmtInfAndStsNbOfTxsPerStsOrgnlPmtInfAndStsTxInfAndStsOrgnlPmtInfAndStsTxInfAndStsStsId35x Or} NA Status Reason ProprietaryNot used by Nets.105x 0-n NA Additional InformationNot used by Nets.See Schema 0-n NA Number of Transaction Per StatusNot used by Nets.See Schema 1-n NA Transaction Information and Status35x 1-1 NA Status IdentificationInformation concerning the original transactions, to which thebookkeeping file message refers.Unique identification assigned by Nets, to unambiguously identify eachtransaction in the bookkeeping file.3.5.3.15OrgnlPmtInfAndStsTxInfAndStsOrgnlInstrIdE.g.: BK001555G1KRVW6R.1.135x 1-1 NA Original Instruction IdentificationUnique identification assigned bycreditor, to unambiguously identify theoriginal instruction.May also contain “NONREF”.232Page 161 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.163.5.3.173.5.3.18OrgnlPmtInfAndStsTxInfAndStsOrgnlEndToEndIdOrgnlPmtInfAndStsTxInfAndStsTxStsOrgnlPmtInfAndStsTxInfAndStsStsRsnInf35x 1-1 AT-10 Original End to End IdentificationSee Schema 1-1 R1 Transaction StatusUnique identification assigned by the creditor, to unambiguously identifythe original transaction.Format: Refer to the Pain 008 sectionPmtInf/DrctDbtTxInf/PmtId/EndToEndId.Specifies the status of the transaction.Usage rule: ‘Transaction status’ will be present with the code ‘ACSC’ or‘RJCT’.If a transaction – direct debit or creditor’s own reversal – is not settled,the status will be RJCT.If a transaction – direct debit, reversal or refund - is settled, the statuswill be ACSC.E.g.: ACSCSee Schema 1-1 NA Status Reason InformationSet of fields used to provide detailed information on the status reason. Inthe bookkeeping file the information is only used to specify the originatorof the transaction (creditor) and the reason for any R-transactions.232Page 162 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.19OrgnlPmtInfAndStsTxInfAndStsStsRsnInfOrgtrSee Schema 1-1 NA Status OriginatorIf the transaction is a settlement transaction then the BICOrBEI will bePBSEDK21.If the transaction is a post-settlement R-transaction the BICOrBEI will bethe BIC of the originators bank, creditor bank or debtor bank.3.5.3.203.5.3.21OrgnlPmtInfAndStsTxInfAndStsStsRsnInfOrgtrIdOrgnlPmtInfAndStsTxInfAndStsStsRsnInfOrgtrIdOrgIdSee Schema 1-1 NA Status Originator IdentificationSee Schema 1-1 R2 Organisation Identification identification of status originator232Page 163 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.22OrgnlPmtInfAndStsTxInfAndStsStsRsnInfOrgtrIdOrgIdBICOrBEI4!a2!a2!c[3!c] 1-1 R2 BIC of the Status OriginatorIf the transaction is a settlement transaction then the BICOrBEI will bePBSEDK21.If the transaction is a post-settlement R-transaction the BICOrBEI will bethe BIC of the originators bank, creditor bank or debtor bank.Maximum length: 11Format rule: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}3.5.3.23OrgnlPmtInfAndStsTxInfAndStsStsRsnInfOrgtrIdPrvtIdE.g. PBSEDK21See Schema 0-1 R2 Private Identification of Status OriginatorNot used by Nets.232Page 164 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.263.5.3.27OrgnlPmtInfAndStsTxInfAndStsStsRsnInfRsnPrtryOrgnlPmtInfAndStsTxInfAndStsStsRsnInfAddtlInf35x Or} NA Status Reason ProprietarySpecifies the reason for the status in a proprietary form.It cannot be used at the same time as StsRsn/Cd.For allowed values, check the table Transaction level error codes,columns “Type” (PRTRY) and “Pain 002 (BKF)”.E.g.: RR01Currently not used by PBS105x 0-1 NA Additional InformationSpecifies the additional information on the status reason.This field states the type of transaction in the bookkeeping field.For allowed values, check the table Transaction level status codes forbookkeeping file.E.g.: 3001232Page 166 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.283.5.3.293.5.3.303.5.3.313.5.3.32OrgnlPmtInfAndStsTxInfAndStsChrgsInfOrgnlPmtInfAndStsTxInfAndStsAccptncDtTmOrgnlPmtInfAndStsTxInfAndStsAcctSvcrRefOrgnlPmtInfAndStsTxInfAndStsClrSysRefOrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefSee Schema 0-1 NA Charges InformationNot used by Nets.See Schema 0-1 NA Acceptance Date TimeNot used by Nets.35x 0-1 NA Account Servicer ReferenceNot used by Nets.35x 0-1 NA Clearing System ReferenceNot used by Nets.See Schema 1-1 NA Original Transaction ReferenceSet of key fields used to identify the original transaction that is beingreferred to.Usage rule: The message elements under ‘Original transaction reference’will be populated with the same value as the message elements of theoriginal instruction, as defined within the following elements.232Page 167 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.333.5.3.343.5.3.35OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefIntrBkSttlmAmtCcy(Attribute)OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefAmtOrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefAmtInstdAmtCcy(Attribute)18d 3!a 1-1 AT-06 Interbank Settlement AmountSee Schema 0-1 AT-06 AmountAmount of money moved between the instructing agent and theinstructed agent.Format: Refer to the Pain 008 sectionPmtInf/DrctDbtTxInf/InstdAmt/Ccy.18d 3!a 0-1 AT-06 Instructed AmountAmount of money to be moved between the debtor and creditor, beforededuction of charges, expressed in the currency ordered by the initiatingparty.Amount of money to be moved between the debtor and creditor, beforededuction of charges, expressed in the currency ordered by the initiatingparty.Format: Refer to Pain 008 sectionPmtInf/DrctDbtTxInf/InstdAmt/Ccy.232Page 168 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.36OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefISODate 1-1 NA InterBank Settlement DateDate on which the amount of money ceases to be available to the agentthat owes it and when the amount of money becomes available to theagent to which it is due.IntrBkSttlmDtMust be a target date and within the allowed range.3.5.3.373.5.3.38OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefReqdColltnDtOrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefReqdExctnDtE.g.: 2009-12-09 (YYYY-MM-DD).ISODate 1-1 AT-11 Requested Collection DateISODate 0-1 NA Requested Execution DateDate and time at which the creditor requests that the amount of money isto be collected from the debtor.Format: Refer to Pain 008 Section PmtInf/ReqdColltnDt.Not used by Nets.232Page 169 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.39OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefCdtrSchmeIdSee Schema 1-1 AT-02 Creditor Scheme IdentificationCredit party that signs the mandate.This field will contain some fields which contain exactly the same valuesas the fields contained in original transaction.Refer to PAIN.008 sectionPmtInf/DrctDbtTxInf/DrctDbtTx/CdtrSchmeId toPmtInf/DrctDbtTxInf/DrctDbtTx/CdtrSchmeId/CtryOfRes.Mandatory fields:TxInfAndSts/OrgnlTxRef/CdtrSchmeIdTxInfAndSts/OrgnlTxRef/CdtrSchmeId/Id/PrvtId/Othr (AT-02)TxInfAndSts/OrgnlTxRef/CdtrSchmeId/Id/PrvtId/Othr/Id – This dataelement is space and case insensitiveOriginal Creditor scheme idTxInfAndSts/OrgnlTxRef/CdtrSchmeId/Id/PrvtId/Othr/SchmeNm/ Prtrywill always be SEPAAT-02: The identifier of the creditor.232Page 170 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.40OrgnlPmtInfAndStsTxInfAndStsSee Schema 1-1 AT-20AT-21Payment Type InformationSet of tags used to further specify the original transaction type.OrgnlTxRefAT-59PmtTpInfThis field will contain matching fields which contain exactly the samevalues as the fields contained in the original transaction.Refer to PAIN.008 section PmtInf/PmtTpInf toPmtInf/PmtTpInf/CtgyPurp.Mandatory fields:TxInfAndSts/OrgnlTxRef/PmtTpInfTxInfAndSts/OrgnlTxRef/PmtTpInf/SvcLvl/cd (AT-20 – will be ”SEPA”)TxInfAndSts/OrgnlTxRef/PmtTpInf/LclInstrm/cd (AT-20 – will be CORE orB2B)TxInfAndSts/OrgnlTxRef/PmtTpInf/ SeqTp (AT-21)AT-20: Identification code of the scheme:The original service level code will be “SEPA”. Values allowedare CORE or B2B, depending on the relevant transaction.AT-21: Transaction type.Accepted sequence type values are: FRST, OOFF, RCUR, andFNAL.232AT-59: Category purpose of the collection.Page 171 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.41OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefPmtMtdSee Schema 0-1 NA Payment MethodNot used by Nets.232Page 172 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.42OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefMndtRltdInfSee Schema 1-1 AT-01AT-16AT-17AT-18Mandate Related InformationSet of tags used to provide further details about the mandate signed bythe creditor and the debtor.This field will contain matching fields, which contain exactly the samevalues as the fields contained in original transaction.AT-19AT-24Refer to PAIN.008 sectionPmtInf/DrctDbtTxInf/DrctDbtTx/MndtRltdInf toPmtInf/DrctDbtTxInf/DrctDbtTx/MndtRltdInf/Frqcy.AT-25AT-01: Unique mandate reference:AT-60• The unique MandateID• This data element is case insensitiveAT-16: Placeholder for the electronic signature data, if applicable.AT-17: Type of mandate (paper, e-Mandate)AT-18: Identifier of the original creditor who issued the mandateAT-19: Unique mandate reference as given by the original creditor whoissued the mandate.AT-24: Reason for amending the mandate.232Page 173 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.433.5.3.44OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefMndtRltdInfOrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefRmtInfSee Schema 1-1 Continuing from previous page.AT-25: Signing date of the mandate.AT-60: Reference of the validation made by the debtor bank.Mandatory fields:See Schema 0-1 AT-22 Remittance InformationOrgnlPmtInfAndSts/TxInfAndSts/OrgnlTxRef/MndtRltdInfOrgnlPmtInfAndSts/TxInfAndSts/OrgnlTxRef/MndtRltdInf/MndtId (AT-01)OrgnlPmtInfAndSts/TxInfAndSts/OrgnlTxRef/MndtRltdInf/DtOfSgntr (AT-25)OrgnlPmtInfAndSts/TxInfAndSts/OrgnlTxRef/MndtRltdInf/AmdmntIndInformation supplied to enable the matching of an entry with the itemsthat the transfer is intended to settle, such as commercial invoices in anaccounts receivable system.This field will contain some fields which contain exactly the same valuesas the fields contained in the original transaction.Refer to PAIN.008 section PmtInf/DrctDbtTxInf/RmtInf toPmtInf/DrctDbtTxInf/RmtInf/Strd/AddtlRmtInf.232Page 174 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.45OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefUltmtDbtrNmSee Schema 0-1 AT-15 Ultimate Debtor NameUltimate party that owes an amount of money to the (ultimate) creditor.AT-15: Name of the debtor reference partyThis field will contain exactly the same values as the fields contained inthe original transaction.Please note that all tags with information about Ultimate Debtor from thepain.008 will not be present in the bookkeeping file.Refer to PAIN.008 section PmtInf/DrctDbtTxInf/UltmtDbtr/Nm.232Page 175 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.46OrgnlPmtInfAndStsTxInfAndStsSee Schema 1-1 AT-14AT-09DebtorParty that owes an amount of money to the (ultimate) creditor.OrgnlTxRefDbtrAT-27Refer to PAIN.008 section PmtInf/DrctDbtTxInf/Dbtr toPmtInf/DrctDbtTxInf/Dbtr/CtryOfRes.Mandatory fields:TxInfAndSts/OrgnlTxRef/DbtrTxInfAndSts/OrgnlTxRef/Dbtr/Nm (AT-14)AT-14: The name of the debtorAT-09: The address of the debtorAT-27: Debtor identification codeThis field will contain some fields which contain exactly the samevalues as the fields contained in original transaction.3.5.3.47OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefDbtrAcctIdIBAN2!a2!n30x 1-1 AT-07 Debtor AccountUnambiguous identification of the account of the debtor.This field will contain exactly the same values as the fields contained inthe original transaction.Refer to PAIN.008 section PmtInf/ DrctDbtTxInf/DbtrAcct/Id/IBAN.AT-07:Account number (IBAN) of the debtor.232Page 176 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.483.5.3.49OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefDbtrAgtFinInstnIdBICOrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefDbtrAgtAcct4!a2!a2!c[3!c] 1-1 AT-13 Debtor AgentFinancial institution servicing an account for the debtor.This field will contain exactly the same values as the fields contained inthe original transaction.Refer to PAIN.008 sectionPmtInf/DrctDbtTxInf/DbtrAgt/FinInstnId/BIC.AT-13: BIC code of the debtor bankSee Schema 0-1 NA Debtor Agent AccountNot used by Nets.232Page 177 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.50OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefCdtrAgtFinInstnIdBIC4!a2!a2!c[3!c] 1-1 AT-12 Creditor AgentFinancial institution servicing an account for the creditor.This field will contain exactly the same values as the fields contained inthe original transaction.Refer to PAIN.008 section PmtInf/CdtrAgt/ FinInstnId/BIC.3.5.3.51OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefCdtrAgtAcctAT-12: BIC code of the creditor bank.See Schema 0-1 NA Creditor Agent AccountNot used by Nets.232Page 178 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.52OrgnlPmtInfAndStsTxInfAndStsSee Schema 1-1 AT-03AT-05CreditorParty to which an amount of money is due.OrgnlTxRefCdtrThis field will contain some fields which contain exactly the same valuesas the fields contained in the original transaction.Refer to PAIN.008 section PmtInf/Cdtr/Nm toPmtInf/Cdtr/CtryOfRes.Mandatory fields:TxInfAndSts/OrgnlTxRef/CdtrTxInfAndSts/OrgnlTxRef/Cdtr/Nm (AT-03)AT-03: The name of the creditor.AT-05: The address of the creditor.232Page 179 of

XML Element Format Status Rule BookRef.Description / validation rules3.5.3.53OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefCdtrAcctIdIBAN2!a2!n30x 1-1 AT-04 Creditor AccountUnambiguous identification of the creditor’s account.This field will contain some fields which contain exactly the same valuesas the fields contained in the original transaction.Refer to PAIN.008 section PmtInf/CdtrAcct/Id/IBAN.AT-04: Account number (IBAN) of the creditor.3.5.3.54OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefSee Schema 0-0 AT-38AT-39Ultimate CreditorNot used by Nets, even if the original transaction contains tags withinformation about Ultimate CreditorUltmtCdtr232Page 180 of

3.6 PAIN.002.001.03 Customer input acknowledgement file3.6.1 Customer input acknowledgement file – group headerXML Element Format Status Rule BookRef.Description / validation rules3.6.1.1GrpHdr See Schema 1-1 NA Group HeaderContains common information about the acknowledgement file.3.6.1.2GrpHdrMsgId35x 1-1 NA Message IdentificationUnique file reference created by Nets.The identification cannot include leading, trailing or internal spaces.Length: 1-35.Content: "([A-Za-z0-9]|[\?|/|\-|:|\(|\)|\.|,|'])E.g.: 35253.6.1.3GrpHdrCreDtTmISO Datetime1-1 NA Created Date TimeThe date and time when the file was created by the Nets.Format: Refer to Pain 008 section GrpHdr/CreDtTm.3.6.1.43.6.1.5GrpHdrInitgPtyGrpHdrFwdgAgtSee Schema 0-1 NA Initiating PartyNot used by Nets.See Schema 0-1 NA Forwarding AgentNot used by Nets.232Page 181 of

XML Element Format Status Rule BookRef.Description / validation rules3.6.1.63.6.1.7GrpHdrDbtrAgtGrpHdrCdtrAgtSee Schema 0-1 NA Debtor AgentNot used by Nets.See Schema 0-1 NA Creditor AgentNot used by Nets232Page 182 of

3.6.2 Customer input acknowledgement file – Group information and statusXML Element Format Status Rule Book Ref. Description / validation rules3.6.2.1OrgnlGrpInfAndStsSeeSchema1-1 NA Original Group Information and StatusOriginal group information concerning the group of transactions, to whichthe status report message refers.3.6.2.2OrgnlGrpInfAndStsOrgnlMsgId35x 1-1 NA Original Message IdentificationUnique identification assigned by the originating party to identify theoriginal message.Format: Refer to Pain 008 section GrpHdr/MsgId3.6.2.3OrgnlGrpInfAndStsOrgnlMsgNmIdNB. This tag is empty if the validated file did not pass the Nets XSDvalidation.35x 1-1 NA Original Message Name IdentificationSpecifies the original message name identifier to which the messagerefers. Contains the type of pain that was used in the original message.E.g.: pain.008.001.02NB. This tag is empty if the validated file did not pass the Nets XSDvalidation.3.6.2.4OrgnlGrpInfAndStsOrgnlCreDtTmISO DateTime0-1 NA Original Created Date TimeNot used by Nets.232Page 183 of

XML Element Format Status Rule Book Ref. Description / validation rules3.6.2.5OrgnlGrpInfAndStsOrgnlNbOfTxs15!n 0-1 NA Original Number of TransactionsNumber of individual transactions contained in the original message.Contains the number that the original message stated, not the actuallycounted number of transactions.Format: Refer to Pain 008 section GrpHdr/NbOfTxs.3.6.2.6OrgnlGrpInfAndStsOrgnlCtrlSum18!d 0-1 NA Original Control SumNB. This tag is empty if the validated file did not pass the Nets XSDvalidation.Total of all individual amounts included in the original message,irrespective of currencies.Contains the amount that the original message stated, not the actualcounted amount.If the validated file did no pass the Nets XSD validation, the amount willbe 0.00.Format: Refer to Pain 008 section GrpHdr/CtrlSum.232Page 184 of

XML Element Format Status Rule Book Ref. Description / validation rules3.6.2.7OrgnlGrpInfAndStsGrpStsSeeSchema0-1 R1 Group StatusSpecifies the status of the validated message.For allowed values, check the table Detailed status code used in inputacknowledgement fileE.g.: RJCT3.6.2.8OrgnlGrpInfAndStsStsRsnInfSeeSchema1-1 NA Status Reason InformationSet of fields used to provide the detailed information on the status reason.This field and the sub-tags contain information about the originator of theacknowledgement file, Nets, and the overall reason code for the originalmessage.3.6.2.9OrgnlGrpInfAndStsStsRsnInfSeeSchema1-1 NA Status OriginatorParty that issues the acknowledgement file. This is always Nets.OrgtrUsage rule: Limited to BIC to identify Nets3.6.2.10OrgnlGrpInfAndStsStsRsnInfSeeSchema0-1 NA Status ReasonThe acknowledgement file is stated in the original message.Rsn232Page 185 of

XML Element Format Status Rule Book Ref. Description / validation rules3.6.2.11OrgnlGrpInfAndStsStsRsnInfSeeSchema{Or NA Status Reason CodeSpecifies the status of the original message.RsnCdIt cannot be used at the same time as StsRsn/Prtry.Not used by Nets.3.6.2.12OrgnlGrpInfAndStsStsRsnInfRsnPrtry35x Or} NA Status Reason ProprietarySpecifies the reason for the status in a proprietary form.It cannot be used at the same time as StsRsn/Cd.3.6.2.13OrgnlGrpInfAndStsStsRsnInfAddtlInfFor allowed values, check the table File level codesE.g.: A01105x 0-1 NA Additional InformationNot used by Nets.232Page 186 of

XML Element Format Status Rule Book Ref. Description / validation rules3.6.2.14OrgnlGrpInfAndStsNbOfTxsPerStsSeeSchema0-2 NA Number of Transactions Per StatusDetailed information on the number of transactions for each identicaltransaction status.There will be two occurrences of this tag including sub-tags: One with thenumbers and summed amounts for the accepted transactions, and onewith the numbers and amounts of rejected transactions.It will be present if OrgnlGrpInfAndSts/GrpSts is “PART”3.6.2.15OrgnlGrpInfAndStsNbOfTxsPerStsDtldNbOfTxs15!n 0-1 NA Detailed Number of TransactionsNumber of individual transactions contained in the message, detailed perstatus.It will be present if OrgnlGrpInfAndSts/GrpSts is “PART”.Format: Refer to Pain 008 section GrpHdr/NbOfTxs.232Page 187 of

XML Element Format Status Rule Book Ref. Description / validation rules3.6.2.16OrgnlGrpInfAndStsNbOfTxsPerStsDtldStsString 0-1 NA Detailed StatusCommon transaction status for all individual transactions reported.It will be present if OrgnlGrpInfAndSts/GrpSts is “PART”.The allowed values are “ACCP” and “RJCT”.3.6.2.17OrgnlGrpInfAndStsNbOfTxsPerStsDtldCtrlSumE.g.: ACCP18!d 0-1 NA Detailed Control SumTotal of all individual amounts included in the message, irrespective ofcurrencies. The message will be detailed per status.It will be present if OrgnlGrpInfAndSts/GrpSts is “PART”.Format: Refer to Pain 008 section GrpHdr/CtrlSum.232Page 188 of

3.6.3 Customer input acknowledgement file – transaction information and statusIf “OrgnlGrpInfAndSts/GrpSts” is not equal to “ACCP” or “RJCT”, a status for each of the transactions in the original group information that wasrejected by the system is given.If the fields in the table are marked as mandatory, it means that they are mandatory under the TxInfAndSts tag, not under pain.002 as such.If the text in this section refers to “the original transaction”, it leads back to the transaction file (pain.008, pain.007 or camt.055) to which theacknowledgement file is the response. For example, if the file is a response to a camt.055 transaction file, the content of the fields may differfrom the content of the original direct debit, provided that the camt.055 transaction file sent by the creditor contained different data.232Page 189 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.1OrgnlPmtInfAndStsSeeSchema0-n NA Original Payment Information and StatusInformation concerning the original payment information, to which thestatus report message refers.3.6.3.23.6.3.33.6.3.43.6.3.5OrgnlPmtInfAndStsOrgnlPmtInfIdOrgnlPmtInfAndStsOrgnlNbOfTxsOrgnlPmtInfAndStsOrgnlCtrlSumOrgnlPmtInfAndStsPmtInfSts35x 1-1 NA Original Payment Information IdentificationUnique identification, as assigned by the original sending party, tounambiguously identify the original payment information group.15n 0-1 NA Original Number of TransactionsNumber of individual transactions contained in the original paymentinformation group.Format:- [0-9]{1,15}Decimal 0-1 NA Original Control Sum4x 0-1 NA Payment Information StatusTotal of all individual amounts included in the original payment informationgroup, irrespective of currencies.Specifies the status of the payment information group.3.6.3.6OrgnlPmtInfAndStsStsRsnInfSeeSchema0-n NA Status Reason InformationSet of elements used to provide detailed information on the status reason.Usage Rule: ‘Status Reason Information’ may be present either in ‘OriginalGroup Information And Status’ or in ‘Transaction Information and Status’.232Page 190 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.7OrgnlPmtInfAndStsStsRsnInfOrgtrSeeSchema0-1 R2 Status OriginatorParty that issues the status.(R2 Identification of the type of party that initiated the reject)Usage Rule: Limited to BIC to identify the bank or CSM originating the statusor ‘Name’ to indicate a CSM when it has no BIC.3.6.3.8OrgnlPmtInfAndStsStsRsnInfRsnSeeSchema0-1 R3 Status ReasonSpecifies the reason for the status report.(R3 Reason code for non-acceptance of the Collection)3.6.3.93.6.3.10OrgnlPmtInfAndStsStsRsnInfRsnCdOrgnlPmtInfAndStsStsRsnInfRsnPrtry4x 1-1 NA Status Reason CodeReason for the status, as published in an external reason code list.35x 1-1 NA Status Reason ProprietaryReason for the status, as a proprietary code.232Page 191 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.11OrgnlPmtInfAndStsAddtlInf105x 0-n NA Additional Information3.6.3.12OrgnlPmtInfAndStsNbOfTxsPerStsSeeSchema0-n NA Number of Transaction Per StatusNot used by Nets.3.6.3.13OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-N NA Transaction Information and StatusInformation concerning the original transactions, to which the status reportmessage refers.3.6.3.14OrgnlPmtInfAndStsTxInfAndStsStsId35x 1-1 NA Status IdentificationUnique identification, to unambiguously identify the reported status. Eachrejected transaction in the acknowledgement file has a unique Netsidentification.3.6.3.15OrgnlPmtInfAndStsTxInfAndStsOrgnlInstrIdE.g.: 3521.135x 0-1 NA Original Instruction IdentificationUnique identification, as assigned by the creditor party for the debtor party,to unambiguously identify the original instruction.This field is only present, if the OrgnlInstrId in camt.055 or pain.007 wasused.232Page 192 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.16OrgnlPmtInfAndStsTxInfAndStsOrgnlEndToEndId35x 1-1 AT-10 Original End to End IdentificationUnique identification, as assigned by the original initiating party, tounambiguously identify the original transaction.Format: Refer to Pain 008 sectionPmtInf/DrctDbtTxInf/PmtId/EndToEndId.3.6.3.17OrgnlPmtInfAndStsTxInfAndStsSeeSchema1-1 NA Transaction StatusSpecifies the status of the transaction.TxStsUsage rule: ‘Transaction status’ will be present with the code ‘RJCT’.E.g.: RJCT3.6.3.18OrgnlPmtInfAndStsTxInfAndStsSeeSchema1-1 NA Status Reason InformationSet of fields used to provide detailed information on the status reason.StsRsnInf3.6.3.19OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-1 R2 Status OriginatorParty that issues the status. As validator of the original message, Nets willissue the status.StsRsnInfOrgtrR2 identification of the type of party that initiated the reject.232Page 193 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.20OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-1 R2 Status Originator IdentificationUnique identification of the party that issues the status.StsRsnInfOrgtrId3.6.3.21OrgnlPmtInfAndStsTxInfAndStsSeeSchema1-1 R2 Organisation Identification of Status OriginatorUnique identification of the organisation of the party that issues the status.StsRsnInfOrgtrIdOrgId232Page 194 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.22OrgnlPmtInfAndStsTxInfAndSts4!a2!a2!c[3!c]1-1 R2 BIC of the Status OriginatorThis is the BIC of Nets.StsRsnInfOrgtrIdMaximum length: 11Format rule: [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}OrgIdBICOrBEIE.g.: PBSEDK213.6.3.23OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-1 R2 Private Identification of Status OriginatorNot used by Nets.StsRsnInfOrgtrIdPrvtId3.6.3.24OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-1 R3 Status ReasonSpecifies the reason for the rejection of the transaction.StsRsnInfRsnR3 reason code for non-acceptance of the collection.232Page 195 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.25OrgnlPmtInfAndStsTxInfAndStsSeeSchema{Or NA Status Reason CodeSpecifies the reason for the status.StsRsnInfRsnIt cannot be used at the same time as StsRsn/Prtry.CdFor allowed values, check the column for pain.002 receipts in the tableTransaction level error codes.E.g.: XT333.6.3.26OrgnlPmtInfAndStsTxInfAndStsStsRsnInfRsnPrtry35x Or} NA Status Reason ProprietarySpecifies the reason for the status in a proprietary form.It cannot be used at the same time as StsRsn/Cd.For allowed values for pain.002 receipts, check the table Transaction levelerror codes.232Page 196 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.27OrgnlPmtInfAndStsTxInfAndStsStsRsnInfAddtlInf105x 0-1 NA Additional InformationNot used by Nets.3.6.3.28OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-1 NA Charges InformationNot used by Nets.ChrgsInf3.6.3.29OrgnlPmtInfAndStsTxInfAndStsISO DateTime0-1 NA Acceptance date timeNot used by Nets.AccptncDtTm3.6.3.303.6.3.31OrgnlPmtInfAndStsTxInfAndStsAcctSvcrRefOrgnlPmtInfAndStsTxInfAndStsClrSysRef35x 0-1 NA Account Servicer ReferenceNot used by Nets.35x 0-1 NA Clearing System ReferenceNot used by Nets.232Page 197 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.32OrgnlPmtInfAndStsTxInfAndStsSeeSchema1-1 NA Original Transaction ReferenceSet of key fields used to identify the original transaction that is beingreferred to.OrgnlTxRefUsage rule: The message elements under ‘Original transaction reference’ willbe populated with the same value as the message elements of the originalinstruction, as defined within the following elements.3.6.3.33OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefIntrBkSttlmAmtCcy(Attribute)18d 3!a 0-1 AT-06 Interbank Settlement AmountNot used by Nets.3.6.3.34OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefSeeSchema0-1 AT-06 AmountAmount of money to be moved between debtor and creditor, before thededuction of charges, expressed in the currency ordered by the initiatingparty.Amt232Page 198 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.353.6.3.363.6.3.37OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefAmtInstdAmtCcy(Attribute)OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefIntrBkSttlmDtOrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefReqdColltnDt18d 3!a 0-1 AT-06 Instructed AmountISODate 0-1 NA InterBank Settlement DateAmount of money to be moved between debtor and creditor, before thededuction of charges, expressed in the currency ordered by the initiatingparty.Format: Refer to Pain 008 section PmtInf/DrctDbtTxInf/InstdAmt.Not used by Nets.ISODate 1-1 AT-11 Requested Collection DateDate and time at which the creditor requests that the amount of money iscollected from the debtor.Format: Refer to Pain 008 Section PmtInf/ReqdColltnDt.232Page 199 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.38OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefReqdExctnDtISODate 0-1 NA Requested Execution DateNot used by Nets.3.6.3.39OrgnlPmtInfAndStsTxInfAndStsSeeSchema1-1 AT-02 Creditor Scheme IdentificationCredit party that signs the mandate.OrgnlTxRefCdtrSchmeIdUsage rule: It is recommended that all transactions within the same‘Payment information’ block have the same ‘Creditor scheme identification’.Check section 0.This field will contain some fields which contain exactly the same values asthe fields contained in the original transaction.Refer to PAIN.008 sectionPmtInf/DrctDbtTxInf/DrctDbtTx/CdtrSchmeId toPmtInf/DrctDbtTxInf/DrctDbtTx/CdtrSchmeId/CtryOfRes.CdtrSchmeId/Id/PrvtId/Othr/Id - This data element is space and caseinsensitive232Page 200 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.40OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefPmtTpInfSeeSchema1-1 AT-20AT-21AT-59Payment Type InformationSet of fields used to further specify the type of the original transaction.AT-20:Identification code of the scheme:The original service level code: “SEPA”.AT-21: Transaction typeValues allowed are CORE or B2B, depending on the relevanttransaction.Also, for sequence type the accepted values are: FRST, OOFF,RCUR, and FNAL.AT-59: (White field) Category purpose of the collection:This field will contain some fields which contain exactly the samevalues as the fields contained in the original transaction.Refer to PAIN.008 section PmtInf/PmtTpInf toPmtInf/PmtTpInf/CtgyPurp.3.6.3.41OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-1 NA Payment MethodNot used by Nets.OrgnlTxRefPmtMtd232Page 201 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.42OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefMndtRltdInfSeeSchema1-1 AT-01AT-16AT-17AT-18AT-19AT-24Mandate Related InformationSet of tags used to provide further details of the mandate signed betweenthe creditor and the debtor.This field will contain some fields which contain exactly the same values asthe fields contained in the original transaction.Refer to PAIN.008 sectionPmtInf/DrctDbtTxInf/DrctDbtTx/MndtRltdInf toPmtInf/DrctDbtTxInf/DrctDbtTx/MndtRltdInf/Frqcy.AT-25AT-01: Unique mandate reference:AT-60The unique MandateIDThis data element is case insensitiveAT-16: Placeholder for the electronic signature data, if applicable.AT-17: Type of mandate (paper, e-Mandate).AT-18: Identifier of the original creditor who issued the mandateAT-19: Unique mandate reference as given by the original creditor whoissued the mandate.AT-24: Reason for amending the mandate232Page 202 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.43OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefMndtRltdInfSeeSchema1-1 AT-01AT-16AT-17AT-18AT-19Continuing from previous page.AT-25: Signing date of the mandateAT-60: Reference of the validation made by the debtor bank.Mandatory fields:OrgnlPmtInfAndSts/TxInfAndSts/OrgnlTxRef/MndtRltdInfAT-24OrgnlPmtInfAndSts/TxInfAndSts/OrgnlTxRef/MndtRltdInf/MndtId (AT-01)AT-25AT-60OrgnlPmtInf7AndSts/TxInfAndSts/OrgnlTxRef/MndtRltdInf/DtOfSgntr (AT-25)OrgnlPmtInfAndSts/TxInfAndSts/OrgnlTxRef/MndtRltdInf/AmdmntInd232Page 203 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.44OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefSeeSchema0-1 AT-22 Remittance InformationInformation supplied to enable the matching of an entry with the items thatthe transfer is intended to settle, such as commercial invoices in an accountsreceivable system.RmtInfThis field will contain some fields which contain exactly the same values asthe fields contained in the original transaction.Refer to PAIN.008 section PmtInf/DrctDbtTxInf/RmtInf toPmtInf/DrctDbtTxInf/RmtInf/Strd/AddtlRmtInf.232Page 204 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.45OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-1 AT-15AT-37Ultimate DebtorUltimate party that owes an amount of money to the (ultimate) creditor.OrgnlTxRefUltmtDbtrAT-15: Name of the debtor reference party.AT-37: Identification code of the debtor reference party.This field will contain some fields which contain exactly the same values asthe fields contained in the original transaction.Refer to PAIN.008 section PmtInf/DrctDbtTxInf/UltmtDbtr toPmtInf/DrctDbtTxInf/UltmtDbtr/CtryOfRes.Postal Address fields will not be send by Nets in the customer inputacknowledgement file232Page 205 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.46OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefDbtrSeeSchema1-1 AT-14AT-09AT-27DebtorParty that owes an amount of money to the (ultimate) creditor.AT-14: The name of the debtorAT-09: The address of the debtorAT-27: Debtor identification codeThis field will contain some fields which contain exactly the same values asthe fields contained in the original transaction.Refer to PAIN.008 section PmtInf/DrctDbtTxInf/Dbtr toPmtInf/DrctDbtTxInf/Dbtr/CtryOfRes.232Page 206 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.47OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefDbtrAcct2!a2!n30x 1-1 AT-07 Debtor AccountUnambiguous identification of the debtor’s account.AT-07: Account number (IBAN) of the debtor.This field will contain some fields which contain exactly the same values asthe fields contained in the original transaction.Refer to PAIN.008 section PmtInf/ DrctDbtTxInf/DbtrAcct/Id toPmtInf/DrctDbtTxInf/DbtrAcct/Id/IBAN.3.6.3.48OrgnlPmtInfAndStsTxInfAndSts4!a2!a2!c[3!c]1-1 AT-13 Debtor AgentFinancial institution servicing an account for the debtor.OrgnlTxRefDbtrAgtAT-13: BIC code of the debtor bankThis field will contain some fields which contain exactly the same values asthe fields contained in the original transaction.Refer to PAIN.008 section PmtInf/ DrctDbtTxInf/ DbtrAgt/FinInstnId toPmtInf/DrctDbtTxInf/DbtrAgt/FinInstnId/BIC.232Page 207 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.49OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-1 NA Debtor Agent AccountNot used by Nets.OrgnlTxRefDbtrAgtAcct3.6.3.50OrgnlPmtInfAndStsTxInfAndSts4!a2!a2!c[3!c]1-1 AT-12 Creditor AgentFinancial institution servicing an account for the creditor.OrgnlTxRefCdtrAgtAT-12: BIC code of the creditor bank.This field will contain some fields which contain exactly the same values asthe fields contained in the original transaction.Refer to PAIN.008 section PmtInf/CdtrAgt to PmtInf/CdtrAgt/BrnchId.3.6.3.51OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-1 NA Creditor Agent AccountNot used by Nets.OrgnlTxRefCdtrAgtAcct232Page 208 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.52OrgnlPmtInfAndStsTxInfAndStsSeeSchema1-1 AT-03AT-05CreditorParty to which an amount of money is due.OrgnlTxRefCdtrAT-03: The name of the creditor.AT-05: The address of the creditor.This field will contain some fields which contain exactly the same values asthe fields contained in the original transaction.Refer to PAIN.008 section PmtInf/Cdtr/Nm to PmtInf/Cdtr/CtryOfRes.3.6.3.53OrgnlPmtInfAndStsTxInfAndStsOrgnlTxRefCdtrAcct2!a2!n30x 1-1 AT-04 Creditor AccountUnambiguous identification of the account of the creditor.AT-04: Account number (IBAN) of the creditor.This field will contain some fields which contain exactly the same values asthe fields contained in the original transaction.Refer to PAIN.008 section PmtInf/CdtrAcct to PmtInf/CdtrAcct/Nm.232Page 209 of

XML Element Format Status Rulebookref.Description / validation rules3.6.3.54OrgnlPmtInfAndStsTxInfAndStsSeeSchema0-1 AT-15AT-37Ultimate CreditorUltimate party to which an amount of money is due.OrgnlTxRefUltmtCdtrThis field must contain the matching fields which contain exactly the samevalues as the fields contained in original transaction.Refer to PAIN.008 section PmtInf/DrctDbtTxInf/UltmtCdtr toPmtInf/DrctDbtTxInf/UltmtCdtr/CtryOfRes.AT-15: Name of the debtor reference party.AT-37:Identification code of the debtor reference party.Postal Address fields will not be send by Nets in the customer inputacknowledgement file232Page 210 of

4 Appendix B – Message item types4.1 Organisation identification codes used in Creditor Debit collection(pain.008), cancellation (camt.055) and reversal (pain.007) request.Eg: XML element in the pain.008: PmtInf/DrctDbtTxInf/UltmtCdtr/Id/OrgId/SchmeNm/CdCODE NAME DefinitionBANK Bank Party Identification Unique and unambiguous assignment made by aspecific bank to identify a relationship as definedbetween the bank and its client.CUST CustomerNumber Number assigned by an issuer to identify acustomer.DUNS Data Universal Numbering System. A unique identification number provided by Dun &Bradstreet to identify an organisation.EMPL EmployerIdentificationNumber Number assigned by a registration authority to anemployer.GS1G GS1GLNIdentifier Global Location Number. A non-significantreference number used to identify legal entities,functional entities, or physical entities accordingto GS1 numbering scheme rules.The number isused to retrieve detailed information that is linkedto it.TXID TaxIdentificationNumber Number assigned by a tax authority to identify anorganisation.4.2 Private identification codes used in Creditor Debit collection (pain.008), cancellation (camt.055)and reversal (pain.007) request.Eg: XML element in pain.008: PmtInf/DrctDbtTxInf/UltmtCdtr/Id/PrvtId/SchmeNm/CdCODE NAME DefinitionARNU AlienRegistrationNumbe Number assigned by a social security agency toidentify a non-resident person.CCPT PassportNumber 'Number assigned by an authority to identifythe passport number of a personCUST CustomerIdentificationNumber Number assigned by an issuer to identify acustomer.DRLC DriversLicenseNumber Number assigned by an authority to identify adriver's license.EMPL EmployeeIdentificationNumber Number assigned by a registration authority toan employee.NIDN NationalIdentityNumber Number assigned by an authority to identifythe national identity number of a person.Page 211 of 232

SOSE SocialSecurityNumber Number assigned by an authority to identifythe social security number of a person.TXID TaxIdentificationNumber Number assigned by a tax authority to identifya person.4.3 Sequence typeCode Name DescriptionFNAL Final Final collection of a series of direct debit instructions.FRST First First collection of a series of direct debit instructions.OOFF One Off Direct debit instruction where the debtor's authorisation is used to initiate a single direct debittransaction.RCUR Recurring Direct debit instruction where the debtor's authorisation is used for regular direct debittransactions initiated by the creditor.4.4 Creditor Reference Type used in Structure Remittance InformationCode Name Description TypeRADMRemittanceadvice messageDocument is a remittance advice sent separately from thecurrent transaction.ISORPINRelatedpaymentinstructionDocument is a linked payment instruction to which thecurrent payment instruction is related, e.g. in a coverscenario.ISOFXDRForeignexchange dealreferenceDocument is a pre-agreed or pre-arranged foreign exchangetransaction to which the payment transaction refers.ISODISP Dispatch advice Document is a dispatch advice. ISOPUOR Purchase order Document is a purchase order. ISOSCORStructuredcommunicationreferenceDocument is a structured communication reference providedby the creditor to identify the referred transaction.ISOIn the SEPA Direct Debit context only SCOR is allowed.Page 212 of 232

4.5 Reversal reason codesCode Name Description TypeAM05 Duplication Duplication ISOMS02Not specified reasoncustomer generatedReason has not been specified by creditorISO4.6 Cancellation reason code (used in Camt.055.001.01PBS)Code Name Description TypeAGNT Incorrect agent Agent in the payment workflow is incorrect. ISOCURR Incorrect currency Currency of the payment is incorrect. ISOCUST Requested by customer Cancellation requested by the debtor. ISODUPL Duplicate payment Payment is a duplicate of another payment. ISOSUSP Suspicious payment Payment is a suspicious payment. ISOUPAY Undue payment Payment is not justified. ISOTECH Technical problems in SDD Techinal problems resulting in erroneous SDDs PRTRYFRAD Fradulent Direct Debit Fradulent Originated Direct Debit PRTRY4.7 Status reason code used in customer counter party reject fileCode Name Description TypeAC01Incorrect accountnumberFormat of the account number specified is incorrect.ISOAC04Closed accountnumberAccount number specified has been closed on the receiver'sbooks.ISOAC06 Blocked account Account specified is blocked, prohibiting posting oftransactions against it.AG01 Transaction forbidden Transaction forbidden on this type of account (formerlyNoAgreement)ISOISOAG02Invalid bank operationcodeBank operation code specified in the message is not validfor receiverISOAM04 Insufficient funds Amount of funds available to cover specified messageamount is insufficient.ISOAM05 Duplication Duplication ISOMD01 No mandate No mandate ISOPage 213 of 232

MD02Missing mandatoryinformation inmandateMandate related information data required by the schemeis missing.ISOMD03Invalid file format forother reason thangrouping indicatorFile format incomplete or invalid.ISOMD07End customerdeceasedEnd customer is deceased.ISOMS02Not specified reasoncustomer generatedReason has not been specified by end customerISOMS03Not specified reasonagent generatedReason has not been specified by agent.ISORC01Bank identifierincorrectBank identifier code specified in the message has anincorrect format (formerlyIncorrectFormatForRoutingCode).ISORR01Missing DebtorAccount orIdentificationMissing Debtor Account or Identification – code used byDebtor banks to indicate a reject for the Regulatory reasonPRTRYRR02Missing Debtor Nameor AddressMissing Debtor Name or Address - Code used by banks toindicate a Return for Regulatory ReasonPRTRYRR03Missing Creditor Nameor AddressMissing Creditor Name or Address - Code used by banks toindicate a Return for Regulatory ReasonPRTRYRR04 Regulatory Reason PRTRYSL01Specific service offered by the debtor bank, for example,the debtor bank may check the details of the direct debitagainst its database of recurrent direct debits and find aninconsistency.ISOBE05UnrecognizedInitiating PartyUnrecognized Initiating Party – Identifier of the CreditorIncorrectISOAC13Invalid DebtorAccount TypeInvalid Debtor Account Type – Debtor account is aconsumer account (B2B only)ISOFF05Direct Debit typeincorrect (CORE only)Direct Debit type incorrect (CORE only)ISOCNORCreditor bank is notregisteredCreditor bank is not registered under this BIC in the CSMISODNORDebtor bank is notregisteredDebtor bank is not registered under this BIC in the CSMISOPage 214 of 232

4.8 Detailed status code used in input acknowledgement fileCode Name DescriptionACCPAccepted customerprofilePreceding check of technical validation was successful. Customer profile check wasalso successful. This includes the assessment of the static risks.RJCT Rejected Payment collection file or individual transaction included in the payment collectionfile has been rejected.PART Partially accepted A number of transactions have been accepted, whereas other transactions have notyet achieved 'accepted' status.Page 215 of 232

4.9 Purpose codes used in the Creditor sending payment collections.e.g: XML element in the pain.008: PmtInf/DrctDbtTxInf/Purp/CdClassification Code Name DefinitionCard Settlement CDCD Cash disbursement ATM Cash Withdrawal in an unattended or Cash Advance in anattended environment (POI or bank counter)Card Settlement CDCB CardPayment with Cashback Purchase of Goods and Services with additional Cashdisbursement at the POI (Cashback)Card Settlement CDQC Quasi Cash: Purchase of Goods which are equivalent to cash like coupons incasinos.Card Settlement CDOC Original Credit A service which allows the card acceptor to effect a credit to acardholder' account. Unlike a Merchant Refund, an Original Creditis not preceded by a card payment. This service is used forexample for crediting winnings from gaming.Cash Mgmt ACCT AccountManagement Transaction moves funds between 2 accounts of same accountholder at the same bank.Cash Mgmt CASH CashManagementTransfer Transaction is a general cash management instruction.Cash Mgmt COLL CollectionPayment Transaction is a collection of funds initiated via a credit transfer ordirect debit.Page 216 of 232

Cash Mgmt CSDB CashDisbursement Transaction is related to cash disbursement.Cash Mgmt DEPT Deposit Transaction is releted to a payment of deposit.Cash Mgmt INTC IntraCompanyPayment Transaction is an intra-company payment, ie, a payment betweentwo companies belonging to the same group.Cash Mgmt LIMA LiquidityManagement Bank initiated account transfer to support zero target balancemanagement, pooling or sweeping.Cash Mgmt NETT Netting Transaction is related to a netting operation.Commercial AGRT AgriculturalTransfer Transaction is related to the agricultural domain.Commercial AREN Accounts Receivables Entry Transaction is related to a payment associated with an AccountReceivable EntryCommercial BEXP BusinessExpenses Transaction is related to a payment of business expenses.Commercial BOCE Back Office Conversion Entry Transaction is related to a payment associated with a Back OfficeConversion EntryCommercial COMC CommercialPayment Transaction is related to a payment of commercial credit or debit.(formerly CommercialCredit)Commercial CPYR Copyright Transaction is payment of copyright.Page 217 of 232

Commercial GDDS PurchaseSaleOfGoods Transaction is related to purchase and sale of goods.Commercial GDSV PurchaseSaleOfGoodsAndServices Transaction is related to purchase and sale of goods and services.Commercial GSCB PurchaseSaleOfGoodsAndServicesWithCashBack Transaction is related to purchase and sale of goods and serviceswith cash back.Commercial LICF LicenseFee Transaction is payment of a license fee.Commercial POPE Point of Purchase Entry Transaction is related to a payment associated with a Point ofPurchase Entry.Commercial ROYA Royalties Transaction is the payment of royalties.Commercial SCVE PurchaseSaleOfServices Transaction is related to purchase and sale of services.Commercial SUBS Subscription Transaction is related to a payment of information orentertainment services either in printed or electronic form.Commercial SUPP SupplierPayment Transaction is related to a payment to a supplier.Page 218 of 232

Commercial TRAD TradeServices Transaction is related to a trade services operation.Consumer CHAR CharityPayment Transaction is a payment for charity reasons.Consumer COMT ConsumerThirdPartyConsolidatedPayment Transaction is a payment used by a third party who can collectfunds to pay on behalf of consumers, ie credit counseling or billpayment companies.Finance CLPR CarLoanPrincipalRepayment Transaction is a payment of car loan principal payment.Finance DBTC DebitCollectionPayment Collection of funds initiated via a debit transfer.Finance GOVI GovernmentInsurance Transaction is related to a payment of government insurance.Finance HLRP HousingLoanRepayment Transaction is related to a payment of housing loan.Finance INPC InsurancePremiumCar Transaction is a payment of car insurance premium.Finance INSU InsurancePremium Transaction is payment of an insurance premium.Page 219 of 232

Finance INTE Interest Transaction is payment of interest.Finance LBRI LaborInsurance Transaction is a payment of labor insurance.Finance LIFI LifeInsurance Transaction is a payment of life insurance.Finance LOAN Loan Transaction is related to transfer of loan to borrower.Finance LOAR LoanRepayment Transaction is related to repayment of loan to lender.Finance PPTI PropertyInsurance Transaction is a payment of property insurance.Finance RINP RecurringInstallmentPayment Transaction is related to a payment of a recurring installmentmade at regular intervals.Finance TRFD TrustFund Transaction is related to a payment of a trust fund.Page 220 of 232

General ADVA AdvancePayment Transaction is an advance payment.General CBFF CapitalBuilding Transaction is related to capital building fringe fortune, ie capitalbuilding for retirement.General CCRD CreditCardPayment Transaction is related to a payment of credit card account.General CDBL CreditCardBill Transaction is related to a payment of credit card bill.General CFEE CancellationFee Transaction is related to a payment of cancellation fee.General COST Costs Transaction is related to payment of costs.General DCRD Debit Card Payment Transaction is related to a debit card payment.General GOVT GovernmentPayment Transaction is a payment to or from a government department.Page 221 of 232

General ICCP IrrevocableCreditCardPayment Transaction is reimbursement of credit card payment.General IDCP IrrevocableDebitCardPayment Transaction is reimbursement of debit card payment.General IHRP InstalmentHirePurchaseAgreement Transaction is payment for an installment/hire-purchaseagreement.General INSM Installment Transaction is related to a payment of an installment.General MSVC MultipleServiceTypes Transaction is related to a payment for multiple service types.General NOWS NotOtherwiseSpecified Transaction is related to a payment for type of services notspecified elsewhere.General OFEE OpeningFee Transaction is related to a payment of opening fee.General OTHR Other Other payment purpose.Page 222 of 232

General PADD Preauthorized debit Transaction is related to a pre-authorized debit originationGeneral PTSP PaymentTerms Transaction is related to payment terms specificationsGeneral RCKE Re-presented Check Entry Transaction is related to a payment associated with a representedcheck entryGeneral RCPT ReceiptPayment Transaction is related to a payment of receipt.General REFU Refund Transaction is the payment of a refund.General RENT Rent Transaction is the payment of rent.General STDY Study Transaction is related to a payment of study/tuition costs.General TELI Telephone-Initiated Transaction Transaction is related to a payment initiated via telephone.General WEBI Internet-Initiated Transaction Transaction is related to a payment initiated via internet.Page 223 of 232

Investment ANNI Annuity Transaction settles annuity related to credit, insurance,investments, other.nInvestment CMDT CommodityTransfer Transaction is payment of commodities.Investment DERI Derivatives Transaction is related to a derivatives transactionInvestment DIVD Dividend Transaction is payment of dividends.Investment FREX ForeignExchange Transaction is related to a foreign exchange operation.Investment HEDG Hedging Transaction is related to a hedging operation.Investment PRME PreciousMetal Transaction is related to a precious metal operation.Page 224 of 232

Investment SAVG Savings Transfer to savings/retirement account.Investment SECU Securities Transaction is the payment of securities.Investment TREA TreasuryPayment Transaction is related to treasury operations.Medical ANTS AnesthesiaServices Transaction is a payment for anesthesia services.Medical CVCF ConvalescentCareFacility Transaction is a payment for convalescence care facility services.Medical DMEQ DurableMedicaleEquipment Transaction is a payment is for use of durable medical equipment.Medical DNTS DentalServices Transaction is a payment for dental services.Page 225 of 232

Medical HLTC HomeHealthCare Transaction is a payment for home health care services.Medical HLTI HealthInsurance Transaction is a payment of health insurance.Medical HSPC HospitalCare Transaction is a payment for hospital care services.Medical ICRF IntermediateCareFacility Transaction is a payment for intermediate care facility services.Medical LTCF LongTermCareFacility Transaction is a payment for long-term care facility services.Medical MDCS MedicalServices Transaction is a payment for medical care services.Medical VIEW VisionCare Transaction is a payment for vision care services.Page 226 of 232

Salary & Benefits ALMY AlimonyPayment Transaction is the payment of alimony.Salary & Benefits BECH ChildBenefit Transaction is related to a payment made to assistparent/guardian to maintain child.Salary & Benefits BENE UnemploymentDisabilityBenefit Transaction is related to a payment to a person who isunemployed/disabled.Salary & Benefits BONU BonusPayment. Transaction is related to payment of a bonus.Salary & Benefits COMM Commission Transaction is payment of commission.Salary & Benefits CSLP CompanySocialLoanPaymentToBank Transaction is a payment by a company to a bank for financingsocial loans to employees.Salary & Benefits GVEA Austrian Government Employees Category A Transaction is payment to category A Austrian governmentemployees.Salary & Benefits GVEB Austrian Government Employees Category B Transaction is payment to category B Austrian governmentemployees.Salary & Benefits GVEC Austrian Government Employees Category C Transaction is payment to category C Austrian governmentemployees.Page 227 of 232

Salary & Benefits GVED Austrian Government Employees Category D Transaction is payment to category D Austrian governmentemployees.Salary & Benefits PAYR Payroll Transaction is related to the payment of payroll.Salary & Benefits PENS PensionPayment Transaction is the payment of pension.Salary & Benefits PRCP PricePayment Transaction is related to a payment of a price.Salary & Benefits SALA SalaryPayment Transaction is the payment of salaries.Salary & Benefits SSBE SocialSecurityBenefit Transaction is a social security benefit, ie payment made by agovernment to support individuals.Tax ESTX EstateTax Transaction is related to a payment of estate tax.Tax HSTX HousingTax Transaction is related to a payment of housing tax.Page 228 of 232

Tax INTX IncomeTax Transaction is related to a payment of income tax.Tax NITX NetIncomeTax Transaction is related to a payment of net income tax.Tax TAXS TaxPayment Transaction is the payment of taxes.Tax VATX ValueAddedTaxPayment Transaction is the payment of value added tax.Tax WHLD WithHolding Transaction is related to a payment of withholding tax.Transport AIRB Air Transaction is a payment for air transport related business.Transport BUSB Bus Transaction is a payment for bus transport related business.Page 229 of 232

Transport FERB Ferry Transaction is a payment for ferry related business.Transport RLWY Railway Transaction is a payment for railway transport related business.Utilities CBTV CableTVBill Transaction is related to a payment of cable TV bill.Utilities ELEC ElectricityBill Transaction is related to a payment of electricity bill.Utilities ENRG Energies Transaction is related to a utility operation.Utilities GASB GasBill Transaction is related to a payment of gas bill.Utilities NWCH NetworkCharge Transaction is related to a payment of network charges.Page 230 of 232

Utilities NWCM NetworkCommunication Transaction is related to a payment of network communication.Utilities OTLC OtherTelecomRelatedBill Transaction is related to a payment of other telecom related bill.Utilities PHON TelephoneBill Transaction is related to a payment of telephone bill.Utilities WTER WaterBill Transaction is related to a payment of water bill.Page 231 of 232

5 Appendix C - Error code reference list5.1 Bulk level error codesNo Code Description TypePain002( Receipt)1 ED05 Settlement Failed ISO X2 B00 Bulk totally accepted PRTRYX3 B01 Bulk partially accepted4 B02 Maximum number of transactions in a bulkexceeded.5 B03 Number of transactions mismatch.6 B05 Total amount mismatch.7 B07 Control sum mismatch.8 B08 Maximum number of bulks in a file exceeded.9 B09 All transactions rejected10 B10 Instructing agent mismatch.11 B11 Invalid use of Instructed agent.12 B13 Zero settlement amount.13 B14 Duplicate message Id.14 B15 Invalid settlement date.15 B16 Invalid settlement info details.16 B23 Too many consecutive rejected transactions.PRTRYPRTRYPRTRYPRTRYPRTRYPRTRYPRTRYPRTRYPRTRYPRTRYPRTRYPRTRYPRTRYPRTRYXXXXXXXXXXXXXX5.2 Transaction level error codesTransaction error codes are always used at the transaction level as part of either thecode/proprietary field.No Code Description TypePain002(BKF)Pain002( Receipt)1 AC01 IncorrectAccountNumber ISO X2 AC04 ClosedAccountNumber ISO X3 AC06 BlockedAccount ISO X

No Code Description TypePain002(BKF)Pain002( Receipt)4 AG01 TransactionForbidden ISO X5 AG02 InvalidBankOperationCode ISO X6 AM01 ZeroAmount ISO X7 AM02 NotAllowedAmount ISO X8 AM04 For BKF-pain.002: Insufficient FundsFor Receipt-pain.002: Transaction amountlimit exceeds the allowed range for theCredit Party accountISO X X9 AM05 Duplication ISO X X10 DT01 InvalidDate ISO X11 ED05 SettlementFailed ISO X12 MD01 NoMandate ISO X13 MD02 MissingMandatoryInformationMandate ISO X X14 MD03 InvalidFileFormatForOtherReasonThanGroupingIndicatorISOX15 MD06 RefundRequestByEndCustomer ISO X16 MD07 EndCustomerDeceased ISO X17 MS02 NotSpecifiedReasonCustomerGenerated ISO X18 MS03 NotSpecifiedReasonAgentGenerated ISO X19 RC01 BankIdentifierIncorrect ISO X20 RR01 Missing Debtor Account or Identification -Code used by banks to indicate a Return forRegulatory Reason21 RR02 Missing Debtor Name or Address - Code usedby banks to indicate a Return for RegulatoryReason22 RR03 Missing Creditor Name or Address - Codeused by banks to indicate a Return forRegulatory ReasonISOISOISOXXX23 RR04 Regulatory Reason ISO X24 SL01 Specific Service offered by debtor bank ISO X

No Code Description TypePain002(BKF)Pain002( Receipt)25 BE05 Unrecognized Initiating Party – Identifier ofthe Creditor Incorrect26 AC13 Invalid Debtor Account Type – Debtoraccount is a consumer account (B2B only)ISOISOXX27 FF05 Direct Debit type incorrect (CORE only) ISP X28 PY01 Unknown BIC in routing table PRTRY X29 XD19 Invalid IBAN format PRTRY X30 XD75 Sequence Type Mismatch PRTRY31 XT13 Unsupported XML field PRTRY X32 XT33 Invalid data format PRTRY X33 XT73 Invalid country code PRTRY X34 XT74 Invalid original transaction status, actionrequired35 XT75 Invalid original transaction status, action notrequired36 XT77 The Interbank settlement amount is not thesame as the original debitPRTRYPRTRYPRTRYXXX37 XT79 Debtor agent not allowed to receive DD PRTRY X38 XT80 Creditor agent not allowed to send DD PRTRY X39 XT81 Only SEPA core fields are allowed PRTRY X40 XT82 Not used PRTRY X41 TM01 Associated message was received afteragreed processing cut-off time.42 T001 Non-Latin characters are not allowed in theidentification fields of a transactionISOPRTRYXX43 XT78 Compensation Amount PRTRY X44 CNOR Creditor bank is not registered under thisBIC in the CSM45 DNOR Debtor bank is not registered under this BICin the CSMISOISOXX

5.3 Transaction level status codes for bookkeeping fileNo Code Description Type1 3001 Settled DD originated by the creditor. PRTRY2 3002 Non-settled DD originated by the creditor. PRTRY3 3003 Settled reversals originated by the creditor. PRTRY4 3004 Non-settled reversals originated by the creditor. PRTRY5 3005 Settled returns/refunds originated by the debtor. PRTRY

5.4 File level codesNo Code Description1 A00 IDF totally accepted2 A01 IDF partially accepted3 R01 IDF received on non-target day4 R02 Network file name not compliant5 R03 Unknown service identifier6 R04 Direct participant BIC mismatch (network address)7 R06 Invalid file name format8 R07 Invalid file extension9 R10 Schema validation failed10 R11 Invalid sending institution11 R12 Invalid receiving institution12 R13 Duplicate IDF13 R14 Invalid test code14 R15 Invalid sending institution BIC format15 R16 Invalid receiving institution BIC format.16 R17 Invalid service identifier in file header17 R18 Direct debit bulk number mismatch18 R19 Request for cancellation bulk number mismatch19 R20 Returns bulk number mismatch20 R21 Rejects bulk number mismatch21 R22 Reversals bulk number mismatch22 R23 All bulks rejected23 R24 Maximum number of IDF received

6 Appendix D – Schema XML filesPayment collection file (DD)Payment reversal requestPayment cancellation requestCounter party rejects file, bookkeeping file,input acknowledgement filePain.008.001.02PBSPain.007.001.02PBSCamt.055.001.01PBSPain.002.001.03

7 Appendix E – Sample XML filesPayment collection filePayment reversal requestPayment cancellation requestCounter party rejects fileBookkeeping file with example of onlymandatory tags filled (MIN) out and all tagsfilled out (MAX)Input acknowledgement file (File all ok)Input acknowledgement file (XSD errors in thefile)Input acknowledgement file (XSD ok, failed oninterchange level)Input acknowledgement file (XSD andinterchange ok, failed on instruction level)Input acknowledgement file (file is partlyaccepted)Input acknowledgement file (File failed due tonon-latin chars)Example of only mandatory tags filled (MIN) inthe payment collection fileSample Payment collection initiation requestSample Payment reversal requestSample Payment cancellation requestSample Counter Party Rejects FileSample Bookkeeping fileSample Input Acknowledgement FileSample Input Acknowledgement FileSample Input Acknowledgement FileSample Input Acknowledgement FileSample Input Acknowledgement FileSample Input Acknowledgement FileSample of Pain008 file