This translation has been prepared with the greatest possible care; however, in case of doubt, the German text is the authoritative version.

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "This translation has been prepared with the greatest possible care; however, in case of doubt, the German text is the authoritative version."

Transcription

1 The Deutsche Bundesbank s technical specifications for the clearing and settlement of interbank SEPA credit transfers via the RPS ( SCT/BCT/SCL technical specifications ) Version 2.4 valid from 30 September 2013 Notes on the English translation This translation has been prepared with the greatest possible care; however, in case of doubt, the German text is the authoritative version. SCT/BCT/SCL technical specifications, version 2.4 Page 1 of 42

2 Contents Inhaltsverzeichnis Introduction Duplication check Daily reconciliation report for credit transfers (DRC) DRC header DRC (pacs.008) credit transfer bulks sent body DRC (pacs.004) return bulks sent body DRC (camt.056) payment cancellation requests sent body DRC (camt.056) resolutions of investigation (ROIs) sent body DRC (pacs.008) credit transfer bulks received body DRC (pacs.004) return bulks received body DRC (camt.056) payment cancellation requests received body DRC (camt.056) resolutions of investigation (ROIs) received body DRC trailer XML file header Input credit file (ICF) header Credit validation file (CVF) header Settled credit file (SCF) header Bilateral credit file (BCF) header XML interbank messages SEPA credit transfer interbank payment SEPA credit transfer interbank credit transfer reject SCL SEPA credit transfer interbank return credit transfer SEPA credit transfer interbank payment cancellation request SEPA Credit Transfer interbank resolution of investigation Use of the instructing agent and instructed agent Error codes/reject reason codes Error codes/reject reason codes used in the SCT service Error codes/reject reason codes used in the BCT service Character set Notes on format/status, special features of XML Explanatory notes on the format of XML file headers and daily reconciliation reports Completing amount fields in line with the schema Use of filling characters in the amount fields Use of spaces in XML fields, in this case the collapsing procedure Compression procedure FileAct: EBICS environment: TARGET2 referencing Annexes (schema files and corresponding sample files) SCT/BCT/SCL technical specifications, version 2.4 Page 2 of 42

3 Changes/additions to the Technical specifications compared with version 2.3 (effective from 30 September 2013) Section Location Entire document Changes/additions Editorial changes 3 DRC Inclusion of new submission window when specifying the processing cycle number in the relevant sent body Inclusion of the two new delivery windows when specifying the processing cycle number in the relevant received body XML file header Note: The processing windows generated by the newly added submission window and the two new delivery windows are included accordingly when specifying the file cycle number (<FileCycleNo>). 11 TARGET2 referencing Inclusion of the processing windows generated by the newly added submission window and the two new delivery windows when specifying the processing cycle in the relevant references. 5.1 pacs Inclusion of the new submission window when entering data in the element <GrpHdr> <IntrBkSttlmDt>. 5.2 pacs scl Editorial revision of descriptions contained in column information and checks for elements located below the entry <TxInfAndSts> regarding the should contain the transaction-related reasons for the rejection of a bulk using error code B09 (bulk was completely rejected as all transactions contained in it were rejected. The specific reasons for rejecting each transaction are stated in the CVF). 5.3 pacs sct Inclusion of the new submission window when entering data in the element <GrpHdr> <IntrBkSttlmDt>. 5.4 camt sct Note added to descriptions in column information and checks for element <Undrlyg><TxInf><OrgnlIntrBkSttlmDt> explaining that failure to meet the deadline for submitting a request to another CSM to return a SEPA credit transfer may result in a rejection using error code XT Error/rejection codes Failure to meet the deadline for submitting a request to return a SEPA credit transfer may result in the issuance of a rejection using error code XT86 by other CSMs SCT/BCT/SCL technical specifications, version 2.4 Page 3 of 42

4 Section Location Changes/additions 12 Sample files One further sample file added to depict a bulk rejection (return) using error code B09. With effect from 1 February 2014 Sec tion Location Changes/additions 3.5 and 3.9 DRC Inclusion of the new amount field in the camt-029 schema file when specifying the ROI processed and ROI rejected values in the DRC (camt.029) resolution of investigation sent body. Inclusion of the new amount field in the camt-029 schema file when specifying the ROI received value in the DRC (camt.029) resolution of investigation received body. 5.3 pacs sct Adaption of description in column EPC references of the element <TxInf><RtrRsnInf><AddtlInf> to accommodate a clarification added by the EPC to version 7.0 of their Inter-Bank Implementation Guidelines. This did not lead to any changes to the technical tests performed by the. 5.4 camt sct Enhancement of description in column EPC references of the element <Undrlyg><TxInf><CxlRsnInf><AddtlInf> to accommodate a clarification added by the EPC to version 7.0 of their Inter-Bank Implementation Guidelines. This did not lead to any changes to the technical tests performed by the. 5.5 camt Incorporation of element <CxlDtls><TxInfAndSts> <OrgnlTxRef><IntrBkSttlmAmt> as a new mandatory field in the camt schema file. SCT/BCT/SCL technical specifications, version 2.4 Page 4 of 42

5 1 Introduction All items to be processed between the and participants are exchanged in the form of physical files. The formats of the individual files and bulks (logical files contained in files) are specified in the corresponding sections of this document. If the XML format and syntax rules defined in the XSD schema files are not observed, a file reject is generated by the. With regard to outgoing files, the data formats provided meet the specifications of this document. The format applied for the specific payment instructions in the individual files depends on the service in question. In the case of both its SCT service and its BCT service, the SEPA- Clearer supports SEPA credit transfers in XML format in accordance with ISO and the EPC specifications. Checking rules going beyond schema validations are described in the following sections. The message type pacs scl used in the CVF does not form part of the EPC specifications. It is a notice of rejection which the sends to participants in the event of an error to inform them about rejected bulks or individual transactions (at the validation or settlement stage). 2 Duplication check Participants in the Bundesbank's RPS are advised to unambiguously reference each individual transaction every business day. Ensuring that payments are unambiguous helps to avoid duplicate payments and makes it easier to classify and search for specific payments. The carries out duplication checks in the SCT service at file, bulk and individual transaction level and in the BCT service at file level. These cover the following criteria, from which an unambiguous key can be derived. Service Reference number Identification of the party that allocated the reference Interbank settlement date (determined by the processing window used in the SEPA- Clearer) or processing day in the The table below shows the duplication criteria applying at file, bulk and individual transaction levels. SCT/BCT/SCL technical specifications, version 2.4 Page 5 of 42

6 Origin Service Reference number BIC Date Files ICF/BCF SCT/ File reference Sending - file header BCT If a file is rejected, it must in any case be given a new file reference prior to being resubmitted. institution ICF bulks ICF SCT Message ID Instructing Interbank Group header or assignment or identification It is necessary to ensure that the <Msgld> remains unambiguous throughout both pacs message types (pacs.008 and pacs.004) and the <Id> of the two camt types (camt.056 and camt (see explanatory note on <MsgId> and <Id>). agent settlement date Credit transfer pacs.008 SCT Transaction ID Debtor agent Interbank settlement date Return pacs.004 SCT Return ID Original creditor agent Interbank settlement date Payment cancellation request camt.056 SCT Cancellation ID Original debtor agent SCL processing day Resolution camt.029 SCT Cancellation Original SCL processing of status ID creditor day investigation agent Explanatory note on references at bulk and individual transaction level (1) Avoiding rejects by other CSMs owing to duplicate submission The Deutsch Bundesbank routes SEPA credit transfers which cannot be processed in the SEPA-Cleareer via other CSMs. To avoid rejections by other CSMs on account of other duplication checks, the references contained in the following message elements should be kept unambiguous for an extended period of time (at least three months) by, for example, applying a time stamp. Message identification (bulk level; pacs.008 and pacs.004) Identification (bulk level; camt.056 and camt.029) Transaction ID (individual transaction level; pacs.008) Return ID (individual transaction level; pacs.004) Cancellation ID (individual transaction level; camt.056) Cancellation status ID (individual transaction level; camt.029) SCT/BCT/SCL technical specifications, version 2.4 Page 6 of 42

7 The individual participant is responsible for any rejects by other CSMs on account of duplicate submissions arising from a participant's non-compliance with the aforementioned rules for completing fields. Furthermore, each participant is liable for any resulting damages and failure to meet the return deadlines etc defined in the rulebook. (2) Cross-referencing by other CSMs Among other activities, the routes R-transactions to other CSMs. Where applicable, other CSMs may have subjected these R-transactions to cross-referencing checks on the basis of references entered in the individual message elements and entries contained in other message elements of the original transaction as listed under the previous sub-item (eg the original interbank settlement date or the original interbank settlement amount), the aim being to establish whether the original transaction was also processed using this other CSM. If the details contained in the R-transaction regarding the original transaction do not exactly match the data relating to the original transaction, this may result in the R-transaction being rejected by the other CSM. SCT/BCT/SCL technical specifications, version 2.4 Page 7 of 42

8 3 Daily reconciliation report for credit transfers (DRC) Summary of the bulks submitted to and delivered from the s SCT service, a copy of which is made available to each participant in EBCDIC format every business day at the end of that day s SEPA processing schedule. The DRC is not in XML format. The DRC files delivered by the in ASCII format using the EBICS communication structure do not incorporate any special characters for the line feed at the end of the data record. 3.1 DRC header Status Field name Format Content Item M Record type 4x HDRC 0 M Service identifier 3x SCT 4 M File type 3x DRC 7 M Sending institution 4!a2!a2!c s BIC (Production: MARKDEFF; test: MARKDEF0) 10 M Sender s file reference 16!x s reference 18 M Date and time 6!n6!n YYMMDDHHMMSS 34 M Test code 1x Either T (test) or P (production), depending on the processing environment M Receiving institution 4!a2!a2!c3!c Originator s BIC/clearing institution s BIC (not communication partner) M Business date 6!n business day 58 SCT/BCT/SCL technical specifications, version 2.4 Page 8 of 42

9 3.2 DRC (pacs.008) credit transfer bulks sent body Submissions of original SEPA direct debits to the s STC service by participants Status Field name Format Content Item M Record type 4x DTSB 0 M Bulk reference 35x <MsgId> in group header 4 M Number credit transfers processed 8n Number of processed transactions in a bulk 39 M Number credit transfers rejected 8n Number of records rejected in a bulk 47 M Value credit transfers processed 18d Total value of processed transactions in a bulk. If an entire bulk is rejected: 0.00 M Value credit transfers rejected 18d Total value of records rejected in a bulk. If an entire bulk is rejected, total value of all transactions contained in the bulk M Processing cycle number 1n Processing cycle A 3 denotes processing after the first submission window A 4 denotes processing after the second submission window A 5 denotes processing after the third submission window A 6 denotes processing after the fourth submission window A 9 denotes processing after the fifth submission window SCT/BCT/SCL technical specifications, version 2.4 Page 9 of 42

10 3.3 DRC (pacs.004) return bulks sent body Submissions of returns to the s STC service by participants Status Field name Format Content Item M Record type 4x DRSB 0 M Bulk reference 35x <MsgId> in group header 4 M Number returns processed 8n Number of processed transactions in a bulk 39 M Number returns rejected 8n Number of records rejected in a bulk 47 M Value returns processed 18d Total value of processed transactions in a bulk. If an entire bulk is rejected: M Value returns rejected 18d Total value of records rejected in a bulk. 73 If an entire bulk is rejected, total value of all transactions contained in the bulk M Processing cycle number 1n Processing cycle A 3 denotes processing after the first submission window A 4 denotes processing after the second submission window A 5 denotes processing after the third submission window A 6 denotes processing after the fourth submission window A 9 denotes processing after the fifth submission window 91 SCT/BCT/SCL technical specifications, version 2.4 Page 10 of 42

11 3.4 DRC (camt.056) payment cancellation requests sent body Submissions of payment cancellation requests (PCRs) to the s STC service by participants Status Field name Format Content Item M Record type 4x DCSB 0 M Bulk reference 35x <Id> belonging to assignment 4 M Number PCRs processed 8n Number of processed transactions in a bulk 39 M Number PCRs rejected 8n Number of records rejected in a bulk 47 M Value PCRs processed 18d Total value of processed transactions in a bulk. If an entire bulk is rejected: M Value PCRs rejected 18d Total value of records rejected in a bulk. 73 If an entire bulk is rejected, total value of all transactions contained in the bulk M Processing cycle number 1n Processing cycle A 3 denotes processing after the first submission window A 4 denotes processing after the second submission window A 5 denotes processing after the third submission window A 6 denotes processing after the fourth submission window A 9 denotes processing after the fifth submission window 91 SCT/BCT/SCL technical specifications, version 2.4 Page 11 of 42

12 3.5 DRC (camt.056) resolutions of investigation (ROIs) sent body Submissions of resolutions of investigation (ROIs) to the s STC service by participants Status Field name Format Content Item M Record type 4x DRIB 0 M Bulk reference 35x <Id> belonging to assignment 4 M Number ROIs processed 8n Number of processed transactions in a bulk 39 M Number ROIs rejected 8n Number of records rejected in a bulk 47 M Value ROIs processed 18d Total value of processed transactions in a bulk. If an entire bulk is rejected: M Value ROIs rejected 18d Total value of records rejected in a bulk. 73 If an entire bulk is rejected, total value of all transactions contained in the bulk M Processing cycle number 1n Processing cycle A 3 denotes processing after the first submission window A 4 denotes processing after the second submission window A 5 denotes processing after the third submission window A 6 denotes processing after the fourth submission window A 9 denotes processing after the fifth submission window 91 SCT/BCT/SCL technical specifications, version 2.4 Page 12 of 42

13 3.6 DRC (pacs.008) credit transfer bulks received body Deliveries of original SEPA credit transfers from the s STC service to participants Status Field name Format Content Item M Record type 4x DTRB 0 M Bulk reference 35x <MsgId> in group header 4 M Number credit transfers received 8n Number of delivered transactions in a bulk 39 M Value credit transfers received 18d Total value of delivered transactions in a bulk 47 M Processing cycle number 1n Processing cycle A 3 denotes deliveries from the first delivery window A 4 denotes deliveries from the second delivery window A 5 denotes deliveries from the third delivery window A 6 denotes deliveries from the fourth delivery window A 7 denotes deliveries from the fifth delivery window An 8 denotes deliveries from the sixth delivery window A 9 denotes deliveries from the seventh delivery window DRC (pacs.004) return bulks received body Deliveries of returns from the s STC service to participants Status Field name Format Content Item M Record type 4x DRCB 0 M Bulk reference 35x <MsgId> in group header 4 M Number returns received 8n Number of delivered transactions in a bulk 39 M Value returns received 18d Total value of delivered transactions in a bulk 47 SCT/BCT/SCL technical specifications, version 2.4 Page 13 of 42

14 M Processing cycle number 1n Processing cycle A 3 denotes deliveries from the first delivery window A 4 denotes deliveries from the second delivery window A 5 denotes deliveries from the third delivery window A 6 denotes deliveries from the fourth delivery window A 7 denotes deliveries from the fifth delivery window An 8 denotes deliveries from the sixth delivery window A 9 denotes deliveries from the seventh delivery window DRC (camt.056) payment cancellation requests received body Deliveries of payment cancellation requests (PCRs) from the s STC service to participants Status Field name Format Content Item M Record type 4x DRRB 0 M Bulk reference 35x <Id> belonging to assignment 4 M Number PCRs received 8n Number of delivered transactions in a bulk 39 M Value PCRs received 18d Total value of delivered transactions in a bulk 47 M Processing cycle number 1n Processing cycle A 3 denotes deliveries from the first delivery window A 4 denotes deliveries from the second delivery window A 5 denotes deliveries from the third delivery window A 6 denotes deliveries from the fourth delivery window A 7 denotes deliveries from the fifth delivery window An 8 denotes deliveries from the sixth delivery window 65 SCT/BCT/SCL technical specifications, version 2.4 Page 14 of 42

15 Status Field name Format Content Item A 9 denotes deliveries from the seventh delivery window SCT/BCT/SCL technical specifications, version 2.4 Page 15 of 42

16 3.9 DRC (camt.029) resolutions of investigation (ROIs) received body Deliveries of resolutions of investigation (ROIs) from the s STC service to participants Status Field name Format Content Item M Record type 4x DROB 0 M Bulk reference 35x <Id> belonging to assignment 4 M Number ROIs received 8n Number of delivered transactions in a bulk 39 M Value ROIs received 18d Total value of delivered transactions in a bulk 47 M Processing cycle number 1n Processing cycle A 3 denotes deliveries from the first delivery window A 4 denotes deliveries from the second delivery window A 5 denotes deliveries from the third delivery window A 6 denotes deliveries from the fourth delivery window A 7 denotes deliveries from the fifth delivery window An 8 denotes deliveries from the sixth delivery window DRC trailer A 9 denotes deliveries from the seventh delivery window Status Field name Format Content Item M Record type 4x TDRC 0 M Total number records 6n Number of DRC bodies 4 SCT/BCT/SCL technical specifications, version 2.4 Page 16 of 42

17 4 XML file header 4.1 Input credit file (ICF) header (BBkICFBlkCdtTrf) see annex Credit validation file (CVF) header (BBkCVFBlkCdtTrf) see annex Settled credit file (SCF) header (BBkSCFBlkCdtTrf) see annex Bilateral credit file (BCF) header (BBkBCFBlkCdtTrf) see annex 4 SCT/BCT/SCL technical specifications, version 2.4 Page 17 of 42

18 5 XML interbank messages 5.1 SEPA credit transfer interbank payment (pacs ) see annex SEPA credit transfer interbank credit transfer reject SCL (pacs sclsct) see annex SEPA credit transfer interbank return credit transfer (pacs sct) see annex SEPA credit transfer interbank payment cancellation request (interbank recall of a credit transfer) (camt sct) see annex SEPA credit transfer interbank resolution of investigation (interbank negative response to a request to recall a credit transfer) (camt ) see annex 9 SCT/BCT/SCL technical specifications, version 2.4 Page 18 of 42

19 6 Use of the instructing agent and instructed agent The following charts provide an overview of how and in which messages the instructing agent, the instructed agent and the receiving and sending institutions are to be specified at the different message levels (file, bulk or individual transaction level) in connection with the SCT service. The InstructedAgentRule and the InstructingAgentRule" must be observed in accordance with the ISO standard. The latter rule includes an exclusion principle which clearly states that the instructing agent may be specified only in the group header or at individual transaction level. This principle also applies to the instructed agent. The following information is not intended to depict all the data elements that can or must contain a BIC in a SEPA credit transfer message but rather to identify the key agents involved in payment processing using the. Brief overview of key individual agents File header for the sending institution <SndgInst>: should contain the BIC belonging to the sender (communication partner) transferring files to the that contain the bulks of one or more instructing agents. This BIC can deviate from that of the (respective) instructing agent and need not be listed in the SCL-Directory. File header for the receiving institution <RcvgInst>: should contain the BIC belonging to the recipient (communication partner) who receives files from the on behalf of an instructed agent. This BIC can deviate from that of the (respective) instructed agent and need not be listed in the SCL-Directory. Group header for the instructing agent <InstgAgt>: should contain the BIC belonging to the submitter (originator) of a bulk transferred to the by the sender. This BIC must be listed in the SCL-Directory. The countervalue of the submitted bulk is settled using the technical sub-account on the TARGET2 SSP specified by the submitter for the purpose of effecting financial settlement via the during the corresponding SCT settlement cycle. Group header for the instructed agent <InstdAgt>: should contain the BIC belonging to the participant whose bulk was delivered to the recipient (known as the settlement institution). This BIC can, but need not necessarily, be contained in the SCL- Directory. The countervalue of the delivered bulk is settled using the technical sub-account on the TARGET2 SSP specified by the agent for the purpose of effecting financial settlement via the during the corresponding SCT settlement cycle. Individual transaction level for the instructing agent <InstgAgt>: should contain the BIC belonging to the original submitter of the bulk in which the transaction was contained upon its submission to the. Upon delivery of the transaction at individual transaction level, this BIC is entered by the and can, but need not necessarily, be listed in the SCL-Directory. SCT/BCT/SCL technical specifications, version 2.4 Page 19 of 42

20 Individual transaction level for the instructed agent <InstdAgt>: this field is not supported at individual transaction level, nor is it a component of the schema files. Individual transaction level for the creditor agent BIC <CdtrAgt>: should contain the BIC belonging to the payee s payment service provider (creditor bank). It is essential that this is contained in the SCL-Directory as it is the key criterion for effecting a routing system in the SCT service. Note: R-transactions name the creditor agent of the original message (pacs.008). See annex 4 for details of how the sending institution, receiving institution, instructing agent and instructed agent are to specified in the BCF file header. SCT/BCT/SCL technical specifications, version 2.4 Page 20 of 42

21 Image 1 (in German only) SCT/BCT/SCL technical specifications version 2.4 Page 21 of 42

22 BIC-Belegung FileHdr, GrpHdr, Indiv. Tx: Überweisung inländisches KI an inländisches KI SEPA Clearer pacs.008 (Original Credit Transfer) FileHdr SendInst MARKDEFF RecvInst SSSSSSSSSSS GrpHdr InstructingAgt./. InstructedAgt TTTTTTTTTTT IndivTx InstructingAgt BBBBBBBBBBB InstructedAgt./. IndivTx Creditor Agt CCCCCCCCCCC pacs.008 (Original Credit Transfer) FileHdr SendInst AAAAAAAAAAA RecvInst MARKDEFF GrpHdr InstructingAgt BBBBBBBBBBB InstructedAgt./. IndivTx InstructingAgt./. InstructedAgt./. IndivTx CreditorAgt CCCCCCCCCCC Inländisches KI Inländisches KI Image 2 (in German only) SCT/BCT/SCL technical specifications version 2.4 Page 22 of 42

23 Image 3 (in German only) SCT/BCT/SCL technical specifications version 2.4 Page 23 of 42

24 Image 4 (in German only) SCT/BCT/SCL technical specifications version 2.4 Page 24 of 42

25 Image 5 (in German only) SCT/BCT/SCL technical specifications version 2.4 Page 25 of 42

26 7 Error codes/reject reason codes 7.1 Error codes/reject reason codes used in the SCT service Error codes used in connection with the structural check of an input credit file (ICF) by the The errors described below result in the entire file being rejected by means of CVF (exception: A01) Error code A01 R02 R04 R07 R09 R10 R11 R12 R13 R14 R18 R19 R20 R21 R98 R99 S01 ICF was partially rejected. Nature of error The file name designation does not conform with the rules (code not currently in use). The sender s BIC in the file name does not conform with the rules (code not currently in use). SWIFTNet FileAct request type does not conform with the rules. ICF was completely rejected as it does not conform with the rules for other reasons (eg character set data deviate from UTF-8). File does not correspond to the schema and therefore cannot be processed. Sender s BIC (<SndgInst>) is incorrect. Recipient s BIC (<RcvgInst>) is incorrect. ICF is a duplicate. Error in test code (<TstCode>). Number of credit transfer bulks contained in the ICF is not consistent with the figure given in the file header. Number of PCR bulks contained in the ICF is not consistent with the figure given in the file header. Number of return bulks contained in the ICF is not consistent with the figure given in the file header. Number of resolution of investigation bulks contained in the ICF is not consistent with the figure given in the file header. File rejected as prefixes are used at group header or individual transaction level (code not currently in use). File rejected for other reasons (code not currently in use). File rejected as maximum permissible number of bulks in file was exceeded. SCT/BCT/SCL technical specifications, version 2.4 Page 26 of 42

27 Error codes used in connection with the structural check of a bulk by the The errors described below result in the entire bulk being rejected by means of CVF (exception: B01) Error code Nature of error e pacs.002scl AM04 Bulk was rejected due to insufficient funds. ISO X B01 Bulk was partially rejected. PRTRY X B02 Maximum permissible number of transactions contained in a bulk was exceeded. PRTRY X B03 B05 B09 B10 Number of transactions contained in a bulk is not consistent with the figure given in the group header. Total value in the field <TtlIntrBkSttlnAmt> or <TtlRtrdIntrBkSttlmAmt> does not correspond to the sum of the transactions in the bulk. Bulk was completely rejected as all transactions contained in it were rejected. The specific reasons for rejecting each transaction are stated in the CVF. Bulk was completely rejected either because the instructing agent has to be included in the ICF group header or the specified instructing agent is not authorised to make submissions for the submitted payment type. PRTRY PRTRY PRTRY PRTRY B11 Bulk was completely rejected as the instructed agent must not be included in the ICF group header. PRTRY X B12 Bulk was completely rejected as the assigner was not authorised to make submissions or the assignee data was incorrect. PRTRY B14 Bulk was completely rejected as the <MsgId> or <Id> appears in duplicate. PRTRY X B15 B98 Bulk was completely rejected as the date in the field <IntrBkSttlmDt> or <OrgnlIntrBkSttlmDt> falls outside the permitted time period. Bulk has been completely rejected as the <MsgId> (GrpHdr) or <Id> (Assgnmt) does not comply with the format rules. PRTRY PRTRY B99 Bulk rejected for other reasons. PRTRY X X X X X X X X SCT/BCT/SCL technical specifications, version 2.4 Page 27 of 42

28 Individual transaction-related error codes ( and other CSMs) or rejection codes (banks) specific to the individual transaction: Code ISO designation SEPA Core reason (pursuant to the EPC s SCT Implementation Guidelines, version 6.0) Nature of error Initiator e pacs.002scl pacs.004 camt.056 camt.029 AC01 IncorrectAccountNumber Account identifier invalid (ie invalid IBAN or account number does not exist) See description on left Banks / SEPA- Clearer ISO X X AC04 ClosedAccountNumber Account closed See description on left Banks ISO X X AC06 BlockedAccount Account blocked, reason not specified See description on left Banks ISO X AG01 TransactionForbidden Credit transfer forbidden on this type of account (eg savings account) AG02 InvalidBankOperation- Code Operation/transaction code incorrect, invalid file format Usage rule: To be used for incorrect operation/ transaction code See description on left Banks ISO X Banks ISO X AM02 Not Allowed Amount --- Incorrect amount Other ISO X CSMs/ SEPA- Clearer AM04 InsufficientFunds Insufficient funds on the account See description on left Banks ISO X X AM05 Duplication Duplicate payment See description on left Banks/ other CSMs/ SEPA- ISO X X SCT/BCT/SCL technical specifications, version 2.4 Page 28 of 42

29 Code ISO designation SEPA Core reason (pursuant to the EPC s SCT Implementation Guidelines, version 6.0) Nature of error Initiator e pacs.002scl pacs.004 camt.056 camt.029 ARDT --- The transaction has already been returned Clearer See description on left Banks PRTRY X BE04 MissingCreditorAddress Account address invalid Payee s address missing or incorrect Banks ISO X CUST RequestedByCustomer Beneficiary refusal Refused by payee Banks ISO X DUPL DuplicatePayment Duplicate sending See description on left Banks ISO X DT01 InvalidDateRange --- Date falls outside the time period permitted by other CSMs or the s time corridor ED05 SettlementFailed --- Unsuccessful settlement in the STEP2 SCT service Other CSMs/ SEPA- Clearer Other CSMs/ SEPA- Clearer ISO X X ISO X FOCR FollowingCancellation Request Positive answer to the recall Designation for a return on the basis of a recall request Banks ISO X FRAD --- Fraudulently originated credit transfer See description on left Banks PRTRY X LEGL LegalDecision Legal reason Rejection on legal grounds Banks ISO X MD07 EndCustomerDeceased Beneficiary deceased Account holder no longer alive Banks ISO X MS02 NotSpecifiedReason By order of the beneficiary Reason for return not specified by Banks ISO X CustomerGenerated customer MS03 NotSpecifiedReason Reason not specified Reason for return not specified by Banks ISO X SCT/BCT/SCL technical specifications, version 2.4 Page 29 of 42

30 Code ISO designation SEPA Core reason (pursuant to the EPC s SCT Implementation Guidelines, version 6.0) Nature of error Initiator e pacs.002scl pacs.004 camt.056 camt.029 NOAS NOOR AgentGenerated NoAnswerFromCustomer No response from beneficiary NoOriginalTransaction Received Original credit transfer never received payment service provider PY Transaction cannot be processed as the payer s and/or the payee s payment service provider(s) is/are not registered as direct or indirect participant(s) in the STEP2 SCT service RC01 BankIdentifierIncorrect Bank identifier incorrect, eg invalid BIC RR01 MissingDebtorAccountOr Identification RR02 RR03 MissingDebtorOr Address MissingCreditorOr Address Payee fails to respond Banks PRTRY X See description on left Banks PRTRY X X Other CSMs/ SEPA- Clearer PRTRY See description on left Banks ISO X Regulatory reason Rejected for regulatory reasons Banks ISO X Regulatory reason As above Banks ISO X Regulatory reason As above Banks ISO X RR04 Regulatory Reason Regulatory reason As above Banks ISO X TECH --- Technical problems resulting in erroneous credit transfer XD Issued if the country code is a valid ISO or SEPA country code but the (country-specific) structure of the See description on left Banks PRTRY X SEPA- Clearer PRTRY X SCT/BCT/SCL technical specifications, version 2.4 Page 30 of 42

31 Code ISO designation SEPA Core reason (pursuant to the EPC s SCT Implementation Guidelines, version 6.0) Nature of error Initiator e pacs.002scl pacs.004 camt.056 camt.029 IBAN or the check digits is incorrect XT The transaction contains at least one unsupported field. At least one mandatory field is missing from the transaction. The error code (if it exists) is specified in the invalid XML field XT The transaction contains at least one element with a BIC that is not SEPAreachable XT The content of at least one XML element is not in the format required. The invalid XML field is indicated by the error code. XT The two characters forming the country code do not constitute a valid ISO or SEPA country code XT Invalid underlying original transaction. Further check required XT Invalid status of underlying original transaction. No further action required XT The originally instructed amount <OrgnlIntrBkSttlmAmt> was not found or SEPA- Clearer SEPA- Clearer SEPA- Clearer SEPA- Clearer PRTRY X PRTRY X PRTRY X PRTRY X Other CSMs PRTRY X Other CSMs PRTRY X Other CSMs PRTRY X SCT/BCT/SCL technical specifications, version 2.4 Page 31 of 42

32 Code ISO designation SEPA Core reason (pursuant to the EPC s SCT Implementation Guidelines, version 6.0) Nature of error Initiator e pacs.002scl pacs.004 camt.056 camt.029 is not consistent with the original transaction amount XT Deadline expired for requesting the recall of a SEPA credit transfer XT Credit transfer rejected for other reasons (code not currently in use) Other CSMs PRTRY X SEPA- Clearer PRTRY SCT/BCT/SCL technical specifications, version 2.4 Page 32 of 42

33 7.2 Error codes/reject reason codes used in the BCT service Error codes used in connection with the structural check of a bilateral credit file (BCF) by the. The errors described below result in the entire file being rejected by means of CVF. Error code R07 R09 R10 R11 R12 R13 R14 R97 RIF RIA RID RFR Nature of error SWIFTNet FileAct request type does not conform with the rules. BCF was completely rejected as it does not conform with the rules for other reasons (eg character set data deviate from UTF8). File does not correspond to the schema and therefore cannot be processed. Sender s BIC (<SndgInst>) is incorrect. Recipient s BIC (<RcvgInst>) is incorrect. BCF is duplicated. Error in test code (<TstCode>). File rejected due to the absence of a bilateral agreement. File rejected due to insufficient funds. File was completely rejected either because the instructing agent has to be included in the BCF file header or the specified instructing agent is not authorised to make submissions for the submitted payment type. File was completely rejected as the date in the field <IntrBkSttlmDt> falls outside the permitted time period. File was completely rejected as the <FileRef> (file header) does not conform with the format rules. SCT/BCT/SCL technical specifications, version 2.4 Page 33 of 42

34 8 Character set The supports the full UTF-8 character set. Banks must be able to support the following Latin character set commonly used in international communication. a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z / -? : ( )., ' + Space However, it can be agreed on a bilateral or multilateral basis to support one or more UTF-8 character sets in addition to the Latin character set (eg the Greek character set). This applies above all to message elements containing the purpose of payment, name and address of the payer (creditor) and payee (debtor). Such data sets are delivered by the to the recipient in unchanged format. Checks by the (1) When files are submitted (ICFs), the checks whether their prologue contains the following information in line with the usage rules applying to the UTF-8 character set. <?xml version="1.0" encoding="utf-8"> If any other character set is entered, the entire file is rejected using the error code R09. (2) No character set checks beyond those covering compliance with the UTF-8 character set are carried out by the. SCT/BCT/SCL technical specifications, version 2.4 Page 34 of 42

35 9 Notes on format/status, special features of XML 9.1 Explanatory notes on the format of XML file headers and daily reconciliation reports Format Description A C Alpha, capital letters Alphanumeric, letters: capital letters D Decimal including decimal point and two decimal places N X Numeric Characters in accordance with Latin character set, in some cases restricted by XSD schema file (see also section entitled Character set ) 3!a Precisely three alpha characters ISO date ISODateTime YYYY-MM-DD YYYY-MM-DDThh:mm:ss Status M O Mandatory field Optional field SCT/BCT/SCL technical specifications, version 2.4 Page 35 of 42

36 9.2 Completing amount fields in line with the schema Sample entry Processing in the SEPA- Clearer One decimal place No decimal places No decimal point and no decimal places Submitted files containing amounts with a decimal point and/or more than two decimal places do not conform to the schema and are therefore rejected using error code R Use of filling characters in the amount fields The XML parser accepts characters that function as "fillers" in an XML context. These may be entered in the amount fields in an XML environment, however their use may result in processing problems for the receiving/processing institution. We therefore advise against using such filling characters. The fillers listed below are recognised by the XML parser and routed/processed as follows by the SCL. 1. Leading zeros before the decimal point and trailing zeros after the decimal point The ignores the extra zeros and delivers the amount with the first and the last significant characters to the SCL participant. Example: Submission to the SCL: <IntrBkSttlmAmt Ccy="EUR"> </IntrBkSttlmAmt> Delivery by the SCL: <IntrBkSttlmAmt Ccy="EUR">1.01<IntrBkSttlmAmt> 2. Spaces in the amount field The ignores the extra spaces and delivers the amount with the first and the last significant characters to the SCL participant. Example: Submission to the SCL: <IntrBkSttlmAmt Ccy="EUR"> 2.02 </IntrBkSttlmAmt> Delivery by the SCL: <IntrBkSttlmAmt Ccy="EUR">2.02</IntrBkSttlmAmt> SCT/BCT/SCL technical specifications, version 2.4 Page 36 of 42

37 3. + symbol before the amount The accepts the plus symbol and replaces it with a zero, provided that the maximum number of characters is not exceeded. Only when the maximum number of characters is exceeded does the SCL adjust the amount (see example 2 under 3 below). Example 1 Submission to the SCL: <IntrBkSttlmAmt Ccy="EUR">+3.03</IntrBkSttlmAmt> Delivery by the SCL: <IntrBkSttlmAmt Ccy="EUR">03.03</IntrBkSttlmAmt> Example 2 Submission to the SCL: <IntrBkSttlmAmt Ccy="EUR"> </IntrBkSttlmAmt> Delivery by the SCL: <IntrBkSttlmAmt Ccy="EUR">04.04</IntrBkSttlmAmt> 9.4 Use of spaces in XML fields, in this case the collapsing procedure "White spaces" form part of the standard XML environment. They are also permitted for the decimal data type, which is assigned to the amount field. Neither the ISO standard nor the EPC s Implementation Guidelines make provisions for any restrictions to this arrangement. As a rule, white spaces can be processed by XML parsers. However, problems can occur, eg when customised solutions have been programmed or the XML data records have been converted to different formats for further processing. We therefore advise against using spaces in the tags, as this may result in processing problems for the receiving/processing institution. CSMs have stipulated the following format rules for a variety of string -derived fields in their schema files. In the description, the white spaces facet was set to collapse in the schema files. Detailed information on the procedure used in XML parsing can be found in the document W3C Recommendation 28 October 2004, XML Schema Part 2: Datatypes Second Edition, the content of which can be called up using the internet link provided below. For reasons of interoperability, this collapsing procedure was integrated into the SEPA- Clearer s schema files with the same level of effect, meaning that, overall, and wherever necessary both submissions to and deliveries from the undergo the above procedure as part of the XML parsing process. SCT/BCT/SCL technical specifications, version 2.4 Page 37 of 42

38 10 Compression procedure 10.1 FileAct 1 Files may be transmitted in either direction in compressed or uncompressed format as desired by the customer. To this end, the following compression programmes may be used. FLAM 2 (which uses the ADC compression procedure as it has the largest compression factor) ZIP GZIP 10.2 EBICS environment 3 In EBICS, the ZIP compression procedure must be supported when transmitting files in either direction. 11 TARGET2 referencing TARGET2 issues settlement information (MT 900/MT 910) and electronic account statements (MT 940/MT 950) for all accounts held under its auspices. The aforementioned message types contain settlement references which serve to facilitate reconciliation with the SEPA credit transfers that are exchanged with the. 1) Automatically generated current order (ie liquidity transfer) by the from the PM account to the relevant sub-account in the amount of the sum total of the settlementrelated SEPA credit transfer messages arising from all ICFs and BCFs submitted in a specific submission window. Structure of the reference in field 21 (MT 900/MT 910) and field 61, sub-field 7 in MT 940/MT 950: SCL Format Content System 1-digit, alphabetical S () AS action 1-digit, alphabetical C (current order) Date 2-digit, numeric TT (processing day) Processing cycle 1-digit, numeric 3 (first processing window) 4 (second processing window) 5 (third processing window) 6 (fourth processing window) 7 (fifth processing window) 8 (sixth processing window) 9 (seventh processing window) 1 See Procedural rules on communication via SWIFTNet FileAct for the Deutsche Bundesbank's Retail Payment System (RPS) and the RPS (SCL). 2 FLAM (Frankenstein Limes Access Method) is a registered trademark of limes datentechnik gmbh, Friedrichsdorf, Germany. 3 See Procedural rules on communication with payment service providers with a bank sort code via EBICS. SCT/BCT/SCL technical specifications, version 2.4 Page 38 of 42

39 Settlement cycle 2-digit, alphabetical EG (denoting the submission of credits) applies to both the SCT and the BCT service Sub-account 2-digit, numeric Sequence number (positions 23 and 24 of the account number) of the relevant sub-account Serial number 7-digit, numeric Serial numbering of all current orders generated by the SCL each processing day In addition, in field 72 of MT 900/MT 910, the code-word "ASINF" followed by the information given below is supported. SCL Format Content Current order 3-digit, alphabetical CUO (current order) Processing cycle 1-digit, numeric 3 (first processing window) 4 (second processing window) 5 (third processing window) 6 (fourth processing window) 7 (fifth processing window) 8 (sixth processing window) 9 (seventh processing window) Settlement cycle 2-digit, alphabetical EG (denoting the submission of credits) applies to both the SCT and the BCT service In MT 940/MT 950, the information <MARKDEFFEDE>HHMMSS is additionally incorporated into field 61, sub-field 9. 2) Settlement of the submitted and delivered SCT bulks and BCFs using the sub-account during the relevant SCT/BCT settlement cycles of a settlement procedure. Structure of the settlement reference in field 21 (MT 900/MT 910) and field 61, sub-field 7 in MT 940/MT 950: SCL Format Content System 1-digit, alphanumeric S () AS action 1-digit, alphabetical I (input; settlement of submitted SCT bulks/bcfs) O (output; settlement of delivered SCT bulks/bcfs) X (error; settlement of rejected individual transactions; only applies to SCT service) Settlement date 2-digit, numeric TT (processing day) Processing cycle 1-digit, numeric 3 (first processing window) 4 (second processing window) 5 (third processing window) 6 (fourth processing window) SCT/BCT/SCL technical specifications, version 2.4 Page 39 of 42

40 7 (fifth processing window) 8 (sixth processing window) 9 (seventh processing window) Settlement cycle 2-digit, numeric EG (denoting the submission of credits; debiting of submitted SCT bulks arising from ICFs) AG (denoting the delivery of credits; crediting of delivered SCT bulks arising from SCFs and CVFs) EB (denoting the submission of credits; debiting of submitted BCFs) AB (denoting the delivery of credits; crediting of delivered BCFs) File ID 6-digit, numeric 6 digits of an internal file reference of the Bulk ID 3-digit, numeric 3 digits of an internal bulk reference of the Consistent assignment of the value 001 for a BCF in the BCT service In addition, field 72 of MT 900/MT 910 supports the code-word "ASINF" followed by the information given below. SCL Format Content Bulk ID 35-digit, alphanumeric Message identification (<MsgID>) in group header of the settled SCT bulk File reference (<FileRef>) in file header of the settled BCF Settlement date 6-digit, numeric DDMMYY Instructing or instructed agent 11-digit, alphanumeric BIC in group header of settled SCT bulk or file header of settled BCF: Submitted bulks: instructing agent Delivered bulks: instructed agent In MT 940/MT 950, the information <MARKDEFFEDE>HHMMSS is additionally incorporated into field 61, sub-field 9. 3) Return transfer of entire funds from the sub-account to the corresponding PM account after completion of all settlements in a settlement procedure (SCT/BCT and SDD settlement cycles) automatically initiated by the When retransferring the (entire amount of) liquidity from the sub-account to the PM account, references are likewise assigned (note to such effect in field 21 of the MT 900/MT 910 as well as in field 61 sub-field 7 of the MT 940/MT 950). In this case, however, it merely takes the form of an internal reference to the TARGET2 platform deriving from the SCT/BCT/SCL technical specifications, version 2.4 Page 40 of 42

41 application. Hence, reconciliation with the underlying transactions is not possible. 12 Annexes (schema files and corresponding sample files) Note: Message instances (ie messages exchanged between banks and the ) must contain the name space declaration at bulk level. This declaration thereafter applies to all tags contained in the message; individual tags therefore need not be identified with the prefix "sw. SCL participants must take care to adhere to the stipulated entries/declaration (see also sample files). Prefix data at bulk and individual transaction level result in the entire file being returned using the error code R98 (implementation at a later expansion stage only). SCL delivery messages to banks are likewise sent without a prefix at tag level. Sample message instance: <SCLSCT:pacs xmlns="urn:iso:std:iso:20022:tech:xsd:sct:pacs "> <GrpHdr> <MsgId>AAAAAAAAAAABCD123</MsgId> SCT/BCT/SCL technical specifications, version 2.4 Page 41 of 42

42 No Sample name Description of transaction type 1 BBkICFBlkCdtTrf_1.xml Example of the submission of an input credit file (pacs.008, camt.056, pacs.004 and camt.029) by an SCL participant to the 2 BBkSCFBlkCdtTrf_1.xml Example of the delivery of a settled credit file (pacs.008) from the SEPA clearer to an SCL participant 3 BBkSCFBlkCdtTrf_2.xml Example of the delivery of a settled credit file (pacs.004) from the to an SCL participant 4 BBkSCFBlkCdtTrf_3.xml Example of the delivery of a settled credit file (camt.056) from the to an SCL participant 5 BBkSCFBlkCdtTrf_4.xml Example of the delivery of a settled credit file (camt.029) from the to an SCL participant. 6 BBkCVFBlkCdtTrf_1.xml Example of the rejection of an SCL participant s entire file by the owing to the detection of a parsing XML error 7 BBkCVFBlkCdtrTrf_2.xml Example of a bulk submitted by an SCL participant being rejected by the owing to insufficient funds 8 BBkCVFBlkCdtrTrf_3.xml Example of the rejection of a bulk submitted by an SCL participant by the as all the transactions contained in it were rejected (bulk error code B09) 9 BBkCVFBlkCdtrTrf_4.xml Example of the rejection of an SCL participant s individually submitted credit transfer by the owing to an error in the transferor s IBAN 10 BBkCVFBlkCdtrTrf_5.xml Example of the rejection of a BCT participant s entire file by the owing to the detection of a parsing XML error 11 BBkBCFBlkCdtTrf_1.xml Example of the submission of a bilateral credit file (pacs.008, camt.056, pacs.004 and camt.029) by an SCL participant to the 12 BBkBCFBlkCdtTrf_2.xml Example of the delivery of a bilateral credit file (pacs.008, camt.056, pacs.004 and camt.029) from the to an SCL participant SCT/BCT/SCL technical specifications, version 2.4 Page 42 of 42

This translation has been prepared with the greatest possible care; however, in case of doubt, the German text is the authoritative version.

This translation has been prepared with the greatest possible care; however, in case of doubt, the German text is the authoritative version. The Deutsche Bundesbank s technical specifications for the clearing and settlement of interbank SEPA credit transfers via the RPS SEPA- Clearer ( SCT/BCT/SCL technical specifications ) Version 2.5 valid

More information

This translation has been prepared with the greatest possible care; however, in case of doubt, the German text is the authoritative version.

This translation has been prepared with the greatest possible care; however, in case of doubt, the German text is the authoritative version. The Deutsche Bundesbank s technical specifications for the clearing and settlement of interbank SEPA credit transfers via the RPS SEPA- Clearer ( SCT/BCT/SCL technical specifications ) Version 2.6 valid

More information

The Deutsche Bundesbank s procedural rules for the clearing and settlement of SEPA credit transfers via the RPS SEPA-Clearer

The Deutsche Bundesbank s procedural rules for the clearing and settlement of SEPA credit transfers via the RPS SEPA-Clearer The eutsche Bundesbank s procedural rules for the clearing and settlement of SEPA credit transfers via the RPS SEPA-Clearer (Procedural rules for SEPA credit transfers) Version 2.6 valid from 23 November

More information

SEPA Reason Codes. Direct Debit Customer to Bank Implementation Guidelines

SEPA Reason Codes. Direct Debit Customer to Bank Implementation Guidelines SEPA Reason s The SEPA reason codes in this document are sourced from the following European Payments Council Implementation Guideline documentation which detail the customer-to-bank and inter-bank formats

More information

This translation has been prepared with the greatest possible care; however, in case of doubt, the German text is the authoritative version.

This translation has been prepared with the greatest possible care; however, in case of doubt, the German text is the authoritative version. The Deutsche Bundesbank s procedural rules for the clearing and settlement of SEPA direct debits via the RPS SEPA-Clearer ( Procedural rules for SEPA direct debits ) Version 2.3 valid from 30 September

More information

SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Doc: EPC115-06 30 November 2012 (Version 7.0 Approved) EPC SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for implementing

More information

Version 2.3 valid from 30 September Notes on the English translation

Version 2.3 valid from 30 September Notes on the English translation The Deutsche Bundesbank s technical specifications for the clearing and settlement of interbank SEPA direct debits via the RPS (SCL) ( SDD/SCL technical specifications ) Version 2.3 valid from 30 September

More information

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Doc: EPC130-08 30 November 2012 (Version 7.0 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for

More information

Department Payments and Settlement Systems

Department Payments and Settlement Systems processing of retail payments: Services offered by the Deutsche Bundesbank Department Payments and Settlement Systems Processing of retail payments: Services offered by the Deutsche Bundesbank The Deutsche

More information

Processing of retail payments: Services of Deutsche Bundesbank. Department Payments and Settlement System

Processing of retail payments: Services of Deutsche Bundesbank. Department Payments and Settlement System : Services of Deutsche Bundesbank Department Payments and System Page 2 Processing of retail payments: Services offered by the Deutsche Bundesbank The Deutsche Bundesbank offers its bank and nonbank customers

More information

Guidance on reason codes for SDD R-transactions

Guidance on reason codes for SDD R-transactions EPC173-14 Version 2.0 Date issued:16 April 2015 Guidance on reason codes for SDD R-transs 1. SDD R-TRANSACTION DEFINITION The content of this document applies to the SEPA Direct Debit Core Scheme Rulebook

More information

Clarification Paper SEPA Credit Transfer and SEPA Direct Debit

Clarification Paper SEPA Credit Transfer and SEPA Direct Debit EPC348-12 Version 2.0 Date issued: 16 May 2013 EPC Clarification Paper SEPA Credit Transfer and SEPA Direct Debit Abstract This document addresses operational issues arising from implementation of the

More information

Clarification Paper SEPA Credit Transfer and SEPA Direct Debit

Clarification Paper SEPA Credit Transfer and SEPA Direct Debit EPC348-12 Version 2.1 Date issued: 06 November 2015 EPC Clarification Paper SEPA Credit Transfer and SEPA Direct Debit Abstract Document Reference This document addresses operational issues arising from

More information

SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Doc: EPC115-06 25 November 2014 (Version 8.0 Approved) EPC SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for implementing

More information

Format Description SWIFT MT940 Structured

Format Description SWIFT MT940 Structured Format Description SWIFT MT940 Structured Rabo Cash Management Colophon Title Format Description SWIFT MT940 Structured Version, date 3.331, November 2014 On behalf of Zakelijke Klantkanalen Contact address

More information

SEPA Direct Debit Unpaid Report File Format

SEPA Direct Debit Unpaid Report File Format SEPA Direct Debit Unpaid Report File Format PAIN.002.001.03 XML File Structure This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document

More information

SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES

SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES Doc: EPC114-06 19 June 2007 (Version 2.3 ) OITS SG SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the SEPA rules for implementing the direct

More information

The Deutsche Bundesbank's procedural rules on communication via SWIFTNet FileAct (SWIFTNet FileAct procedural rules)

The Deutsche Bundesbank's procedural rules on communication via SWIFTNet FileAct (SWIFTNet FileAct procedural rules) The Deutsche Bundesbank's procedural rules on communication via SWIFTNet FileAct (SWIFTNet FileAct procedural rules) Version 1.7 valid from 21 November 2016 Notes on the English translation This translation

More information

SEPA CREDIT TRANSFER SCHEME RULEBOOK

SEPA CREDIT TRANSFER SCHEME RULEBOOK EPC125-05 Version 7.2 Approved Date issued: 4 March 2015 Date effective: 3 April 2015 SEPA CREDIT TRANSFER SCHEME RULEBOOK Conseil Européen des Paiements AISBL Cours Saint-Michel 30 B 1040 Brussels Tel:

More information

SEPA CREDIT TRANSFER SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

SEPA CREDIT TRANSFER SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Doc: EPC132-08 17 November 2011 (Version 6.0 Approved) EPC SEPA CREDIT TRANSFER SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for

More information

SEPA Credit Transfers Originators Guide

SEPA Credit Transfers Originators Guide SEPA Credit Transfers Originators Guide This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document may not be reproduced or further

More information

SEPA INSTANT CREDIT TRANSFER SCHEME RULEBOOK. Version 0.1 for public consultation. from 12 April to 10 July 2016

SEPA INSTANT CREDIT TRANSFER SCHEME RULEBOOK. Version 0.1 for public consultation. from 12 April to 10 July 2016 EPC 004-16 Version 0.1 for public consultation 12 April 2016 SEPA INSTANT CREDIT TRANSFER SCHEME RULEBOOK Version 0.1 for public consultation from 12 April to 10 July 2016 Conseil Européen des Paiements

More information

Intra-day payment Frequently asked questions

Intra-day payment Frequently asked questions Intra-day payment Frequently asked questions Contents 1. THE MEANING, advantages and scope of intra-day payment... 3 1.1. What does the launch of intra-day payment mean?... 3 1.2. What advantages does

More information

PAIN.002. Format description Functional

PAIN.002. Format description Functional PAIN.002 Format description Functional Content 1. PAIN.002 STATUS EXPORT FORMAT 3 2. PAIN.002 SCENARIOS 5 APPENDIX 1: EXPORTING PAIN.002 FROM RABO CASH MANAGEMENT 12 APPENDIX 2: DOWNLOADING PAIN.002 FROM

More information

TERMS AND CONDITIONS OF REMOTE DATA TRANSMISSION

TERMS AND CONDITIONS OF REMOTE DATA TRANSMISSION TERMS AND CONDITIONS OF REMOTE DATA TRANSMISSION I. Scope of services 1. The bank offers to its customers (account holders) data transmission by electronic means hereinafter referred to as remote data

More information

SEPA CREDIT TRANSFER SCHEME RULEBOOK

SEPA CREDIT TRANSFER SCHEME RULEBOOK EPC125-05 Version 8.2 Date issued: 03 March 2016 Date effective: 01 April 2016 SEPA CREDIT TRANSFER SCHEME RULEBOOK Conseil Européen des Paiements AISBL Cours Saint-Michel 30 B 1040 Brussels Tel: +32 2

More information

Format Description MT940. Rabo Cash Management

Format Description MT940. Rabo Cash Management Format Description MT940 Rabo Cash Management COLOFON Title Format Description MT940 Version, date 2.4, January 2013 On behalf of Contact address FL-Services Rabobank Nederland, Croeselaan 18, Postbus

More information

SEPA Direct Debit Creditor Guide

SEPA Direct Debit Creditor Guide SEPA SEPA Direct Debit Creditor Guide Glossary of Terms Version Control Version Date Name Update V1.0 30/10/2013 Bank of Ireland Creditors Guide published on BOI website This document is published by Bank

More information

SEPA Direct Debit Initiation Customer-to-Bank Implementation Guidelines for the Netherlands

SEPA Direct Debit Initiation Customer-to-Bank Implementation Guidelines for the Netherlands SEPA Direct Debit Initiation Customer-to-Bank Implementation Guidelines for the Netherlands CORE and Business-to-Business Implementation Guidelines Disclaimer These guidelines may be subject to changes.

More information

Format Description. SWIFT MT103 Single Customer Credit Transfer

Format Description. SWIFT MT103 Single Customer Credit Transfer De Format Description SWIFT MT103 Single Customer Credit Transfer COLOPHON Title Format Description SWIFT MT103 Version, date 1.3, June 2015 On behalf of Contact address Corporate Client Channels Rabobank

More information

Terms and Conditions for Remote Data Transmission

Terms and Conditions for Remote Data Transmission Terms and Conditions for Remote Data Transmission (Status 31 October 2009) 1. Scope of services (1) The Bank is available to its Customers (account holders) for remote transmission of data by electronic

More information

SEPA CREDIT TRANSFER SCHEME RULEBOOK

SEPA CREDIT TRANSFER SCHEME RULEBOOK EPC125-05 Version 4.1 approved Date issued: 1 November 2010 Date effective: 1 November 2010 SEPA CREDIT TRANSFER SCHEME RULEBOOK Conseil Européen des Paiements AISBL Av. de Tervueren 12 B 1040 Brussels

More information

SEPA in Slovakia. Quick facts. International Bank Account Number (IBAN) IBAN structure. 75 SEPA Country Sheets - Slovakia

SEPA in Slovakia. Quick facts. International Bank Account Number (IBAN) IBAN structure. 75 SEPA Country Sheets - Slovakia SEPA in Slovakia Useful links Slovak Central Bank www.nbs.sk/en/payment-systems/sepa SEPA Implementation Plan Download the PDF Slovak Banking Association www.sbaonline.sk/en Quick facts International Bank

More information

480.84 en (pf.ch/dok.pf) 10.2015 PF. Manual PostFinance ISO messages for banks [pacs messages]

480.84 en (pf.ch/dok.pf) 10.2015 PF. Manual PostFinance ISO messages for banks [pacs messages] 480.84 en (pf.ch/dok.pf) 10.2015 PF Manual PostFinance ISO messages for banks [pacs messages] Customer service Enquiries concerning service ISO 20022 for banks PostFinance Ltd Customer Service Banks Mingerstrasse

More information

499.35 en (pf.ch/dok.pf) 11.2015 PF. EPO manual Electronic payment order via file transfer

499.35 en (pf.ch/dok.pf) 11.2015 PF. EPO manual Electronic payment order via file transfer 499.35 en (pf.ch/dok.pf) 11.2015 PF EPO manual Electronic payment order via file transfer Customer support Customer support for EPO Consulting & Sales Phone +41 848 888 900 (CHF 0.08/min. from a landline)

More information

SEPA CORE DIRECT DEBIT SCHEME RULEBOOK

SEPA CORE DIRECT DEBIT SCHEME RULEBOOK EPC016-06 Version 7.1 Approved Date issued: 27 January 2014 Date effective: 1 February 2014 SEPA CORE DIRECT DEBIT SCHEME RULEBOOK Conseil Européen des Paiements AISBL Cours Saint-Michel 30A B 1040 Brussels

More information

EPC Version June 2012 EPC

EPC Version June 2012 EPC EPC139-12 Version 1.1 22 June 2012 EPC SEPA DIRECT DEBIT CORE RULEBOOK CHANGE REQUEST CONSULTATION DOCUMENT The Single Euro Payments Area (SEPA) payment schemes, as set out in the SEPA Credit Transfer

More information

ING FTP. Unstructured MT940 and MT942 Format Description. The Netherlands. February 2014 (V2.0)

ING FTP. Unstructured MT940 and MT942 Format Description. The Netherlands. February 2014 (V2.0) ING FTP Unstructured MT940 and MT942 Format Description The Netherlands February 2014 (V2.0) ING FTP Unstructured MT940 and MT942 The MT940 and MT942 Customer Statement Message is a standard SWIFT (Society

More information

SEPA Credit Transfer Unpaid Report File Format

SEPA Credit Transfer Unpaid Report File Format SEPA Credit Transfer Unpaid Report File Format PAIN.002.001.03 XML File Structure This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This

More information

SEPA LOCAL PRACTICES AND IMPLEMENTATION GUIDELINES*

SEPA LOCAL PRACTICES AND IMPLEMENTATION GUIDELINES* BNP Paribas SEPA Newsletter Issue September 2013 SEPA LOCAL PRACTICES AND IMPLEMENTATION GUIDELINES* SEPA (Single Euro Payments Area) aims to harmonise formats and processes for euro payments across every

More information

SEPA Creditors Guide. SEPA Direct Debit Core Scheme. Version 1.3 Final Page 1 of 38

SEPA Creditors Guide. SEPA Direct Debit Core Scheme. Version 1.3 Final Page 1 of 38 SEPA Creditors Guide SEPA Direct Debit Core Scheme Version 1.3 Final Page 1 of 38 Log of Revisions to the SDD Creditors Guide Version number Version1.1 Brief description of revision Comprehensive guide

More information

Format description XML SEPA Credit Transfer. Format Description

Format description XML SEPA Credit Transfer. Format Description Format description XML SEPA Credit Transfer Format Description CONTENTS 1 SEPA CT Import format 3 1.1 SEPA CT import format description 3 1.1.1 Description 3 1.1.2 General characteristics 3 1.1.3 Difference

More information

Online Banking Record Descriptions

Online Banking Record Descriptions Record s hotline@sydbank.dk Page 1 of 65 Contents Introduction... 3 Sydbank format... 3 Format descriptions... 5 of fixed-length records... 5 of variable-length records... 6 Payment start... 7 IB000000000000...

More information

ABNAMRO addendum on the XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands

ABNAMRO addendum on the XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands on the XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands Version 1.0 December 2010 Contents 1. Introduction...8 Character Set...9 2. Message items description...10

More information

SEPA DATA MODEL. Reason for Issue Approved by the EPC Plenary on 13 December 2006

SEPA DATA MODEL. Reason for Issue Approved by the EPC Plenary on 13 December 2006 Doc: EPC029-06 (Version 2.2) 13 December2006 OITS SG SEPA DATA MODEL Abstract Document Reference Issue This document sets out the SEPA Data Model which is referred to in the SEPA Credit Transfer and Direct

More information

ERP SEPA readiness checklist

ERP SEPA readiness checklist ERP SEPA readiness checklist version July 2013 www.ingsepa.com Financial Supply Chain SEPA This list contains 11 questions to determine the level of SEPA-readiness of an ERP 1. The first 3 questions deal

More information

SIF Validation Tool. Wages Protection System Qatar Central Bank& Ministry of Labour And Social Affairs. End User Guide

SIF Validation Tool. Wages Protection System Qatar Central Bank& Ministry of Labour And Social Affairs. End User Guide SIF Validation Tool Wages Protection System Qatar Central Bank& Ministry of Labour And Social Affairs End User Guide [1] SIF Validation Tool at a Glance Content 1 SIF VALIDATION TOOL AT A GLANCE 3 2 GETTING

More information

SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Doc: EPC114-06 25 November 2014 (Version 8.0 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for implementing

More information

SEPA Direct Debit Initiation Customer-to-Bank Implementation Guidelines for The Netherlands

SEPA Direct Debit Initiation Customer-to-Bank Implementation Guidelines for The Netherlands SEPA Direct Debit Initiation Customer-to-Bank Implementation Guidelines for The Netherlands CORE and Business-to-Business Implementation Guidelines Disclaimer These guidelines may be subject to changes.

More information

Addendum on the XML message for SEPA Direct Debit Initiation (PAIN)

Addendum on the XML message for SEPA Direct Debit Initiation (PAIN) Deutsche Deutsche Bank Bank Addendum on the XML message for SEPA Direct Debit Initiation (PAIN) Addendum on the XML message for SEPA Direct Debit Initiation (PAIN) 01 Contents Introduction 03 1.1 Change

More information

STEP2 Pan-European Bulk Payment Processing System. Functional Overview

STEP2 Pan-European Bulk Payment Processing System. Functional Overview STEP2 Pan-European Bulk Payment Processing System Functional Overview Final 3v1 of 11 th September 2006 1 Contents 1 Introduction...4 1.1 References...4 1.2 Modification History...4 2 The Scope Of The

More information

SWIFT REQUEST FOR TRANSFER SERVICE. Description

SWIFT REQUEST FOR TRANSFER SERVICE. Description SWIFT REQUEST FOR TRANSFER SERVICE Description 15.11.2012 Contents 1 Message MT101 Scope...4 2 MT101 Message Structure...5 2.1 Basic Header Block (1)... 5 2.2 Application Header Block (2)... 6 2.3 Text

More information

Frequently Asked Questions

Frequently Asked Questions This document describes (FAQs) about IBAN Plus. This includes the IBAN Plus product, how to use the product, the quality of the data, and IBAN regulations and standards. This document is for anyone who

More information

PAYMENT CONDITIONS. Effective as of 10.06.2014 1

PAYMENT CONDITIONS. Effective as of 10.06.2014 1 1. Definitions In addition to the terms and conditions provided in the Current Account Contract Conditions and the General Conditions of the Bank, the following definitions are used in these Payment Conditions:

More information

SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands

SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands Disclaimer These guidelines may be subject to changes. Utmost care has been taken to ensure the information in this publication

More information

Functional specifications for Nordea XML Direct Debit (NDD) Corporate egateway

Functional specifications for Nordea XML Direct Debit (NDD) Corporate egateway Functional specifications for Nordea XML Direct Debit (NDD) Corporate egateway Table of contents 1 Introduction... 1 1.1 NDD documents 1 2 Basic description of the NDD service... 1 2.1 Basic architecture

More information

SEPA CORE DIRECT DEBIT SCHEME RULEBOOK

SEPA CORE DIRECT DEBIT SCHEME RULEBOOK EPC016-06 Version 9.2 Date issued: 03 March 2016 Date effective: 20 November 2016 SEPA CORE DIRECT DEBIT SCHEME RULEBOOK Conseil Européen des Paiements AISBL Cours Saint-Michel 30 B 1040 Brussels Tel:

More information

SEPA. Frequently Asked Questions

SEPA. Frequently Asked Questions SEPA Frequently Asked Questions Page 1 of 13 Contents General SEPA Questions... 4 What is SEPA?... 4 What is the aim of SEPA?... 4 What are the benefits of SEPA?... 4 What countries are included in SEPA?...

More information

TERMS AND CONDITIONS APPLICABLE TO CREDIT INSTITUTIONS

TERMS AND CONDITIONS APPLICABLE TO CREDIT INSTITUTIONS ERSTE BANK HUNGARY ZRT TERMS AND CONDITIONS APPLICABLE TO CREDIT INSTITUTIONS Effective from: 01 September 2014 1. General Provisions 1.1. These Terms and Conditions (hereinafter TC ) apply to all correspondent

More information

Intraday credit transfer: Frequently Asked Questions and Definitions. Bank customers enjoy significant advantages

Intraday credit transfer: Frequently Asked Questions and Definitions. Bank customers enjoy significant advantages Intraday credit transfer: Frequently Asked Questions and Definitions Bank customers enjoy significant advantages Following 1 July 2012 the execution time of domestic HUF credit transfers will be one business

More information

SEPA Direct Debit Implementation Guide. Version 1.7

SEPA Direct Debit Implementation Guide. Version 1.7 SEPA Direct Debit Implementation Guide Version 1.7 DANSKE BANK Table of contents 1 Change log... 3 2 Purpose of this document... 4 2.1 Target groups... 4 2.2 Help... 4 3 Introduction to SEPA Direct Debit...

More information

TECHNICAL SPECIFICATIONS GUIDE CANADA SAVINGS BONDS. csb.gc.ca PAYROLL SAVINGS PROGRAM 20$ 40$ 80$ 50 $ 30$ TECHGUIDE-14

TECHNICAL SPECIFICATIONS GUIDE CANADA SAVINGS BONDS. csb.gc.ca PAYROLL SAVINGS PROGRAM 20$ 40$ 80$ 50 $ 30$ TECHGUIDE-14 7 TECHNICAL SPECIFICATIONS GUIDE CANADA SAVINGS BONDS PAYROLL SAVINGS PROGRAM csb.gc.ca 40 5 30 0 20 80 70 0 What are you saving for? 50 40 20 0 80 4 20 7 7 TECHGUIDE-4 TECHNICAL SPECIFICATIONS GUIDE For

More information

SEPA BUSINESS TO BUSINESS DIRECT DEBIT SCHEME RULEBOOK

SEPA BUSINESS TO BUSINESS DIRECT DEBIT SCHEME RULEBOOK EPC222-07 Version 5.0 Approved Date issued: 30 November 2012 Date effective: 1 February 2014 SEPA BUSINESS TO BUSINESS DIRECT DEBIT SCHEME RULEBOOK Conseil Européen des Paiements AISBL Cours Saint-Michel

More information

SEPA BUSINESS TO BUSINESS DIRECT DEBIT SCHEME RULEBOOK

SEPA BUSINESS TO BUSINESS DIRECT DEBIT SCHEME RULEBOOK EPC222-07 Version 6.2 Date issued: 03 March 2016 Date effective: 01 April 2016 SEPA BUSINESS TO BUSINESS DIRECT DEBIT SCHEME RULEBOOK Conseil Européen des Paiements AISBL Cours Saint-Michel 30 B 1040 Brussels

More information

OPERATING RULES FOR INTERBANK CLEARING OF PAYMENTS IN FOREIGN EXCHANGE

OPERATING RULES FOR INTERBANK CLEARING OF PAYMENTS IN FOREIGN EXCHANGE Pursuant to Section 4, paragraph 1 of the Decision on Interbank Clearing of Payments in Foreign Exchange (''RS Official Gazette'', No. 31/2007 and 93/2007), the Governor of the National Bank of Serbia

More information

User's manual for OTPdirekt Internet Banking. v.1.0

User's manual for OTPdirekt Internet Banking. v.1.0 User's manual for OTPdirekt Internet Banking v.1.0 1 Contents General... 4 Log in... 4 Logging out... 4 Home page... 5 Accounts... 5 Accounts - Overview of movements... 6 Accounts - OTPdirekt transactions...

More information

March 2014. Euro Payment. Manual

March 2014. Euro Payment. Manual March 2014 Euro Payment Manual Contents 1 Introduction 2 Euro Payment: characteristic features 2.1 Introduction 2.2 Differences compared to the Dutch credit transfer 2.3 IBAN and BIC 2.4 Timelines and

More information

Entering payment order abroad and payment order in a foreign currency in the Czech Republic via electronic banking service ČSOB InternetBanking 24

Entering payment order abroad and payment order in a foreign currency in the Czech Republic via electronic banking service ČSOB InternetBanking 24 Entering payment order abroad and payment order in a foreign currency in the Czech Republic via electronic banking service ČSOB InternetBanking 24 Content 1. Payment order abroad... 2 1.1. Entering payment

More information

Terms and Conditions for Direct Debit Collection.

Terms and Conditions for Direct Debit Collection. Terms and Conditions for Direct Debit Collection. Version as of 3 February 2015 Landesbank Baden-Württemberg - 1 - As at 10/13 Contents Terms and Conditions for Direct Debit Collection Collection Authorization

More information

Our global technology. Your advantage. Telegraphic Transfers. Product Disclosure Statement Issued 2 June 2008

Our global technology. Your advantage. Telegraphic Transfers. Product Disclosure Statement Issued 2 June 2008 Our global technology. Your advantage. Telegraphic Transfers Product Disclosure Statement Issued 2 June 2008 ONLINE SECURE SIMPLE FX INTERNATIONAL PAYMENTS Contents Product Disclosure Statement Telegraphic

More information

SWIFT Certified Application Payments

SWIFT Certified Application Payments SWIFT Certified Application Payments Technical validation Guide 2014 Version 1.1 April 2014 Legal notices Copyright SWIFT 2014. All rights reserved. You may copy this publication within your organisation.

More information

Frequently Asked Questions

Frequently Asked Questions Reference Data SEPA Plus Frequently Asked Questions This document describes the most Frequently Asked Questions (FAQs) about the SEPA Plus product. This includes information about the SEPA Plus files and

More information

NZD 1.0000 GBP 0.3842. Telegraphic Transfers (New Zealand)

NZD 1.0000 GBP 0.3842. Telegraphic Transfers (New Zealand) NZD 1.0000 GBP 0.3842 Telegraphic Transfers (New Zealand) Product Disclosure Statement Issued 1 July 2009 1 VND 11107.55 USD 1.00 NZD 1.0000 EUR 0.4550 Contents. Product Disclosure Statement. Introduction

More information

Plastic Card Claims Automation Specifications Document

Plastic Card Claims Automation Specifications Document Plastic Card Claims Automation Specifications Document Version: 1.3 Last modified: April 28, 2009 The Plastic Card Policy is underwritten by CUMIS Insurance Society, Inc., a member of the CUNA Mutual Group.

More information

SNS Bank addendum on the XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands

SNS Bank addendum on the XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands SNS Bank addendum on the XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands Version 1.2 April 2015 1-14 Contents 1. Introduction... 8 Character Set... 9 2. Message

More information

Electronic foreign currency payments, LUM2

Electronic foreign currency payments, LUM2 Electronic foreign currency payments, LUM2 Contents 1 Electronic foreign currency payment service... 3 2 Service agreement and testing... 3 2.1 Agreement... 3 2.2 Testing... 4 2.2.1 File transfer and processing...

More information

SWIFTReady for Corporates Cash Management

SWIFTReady for Corporates Cash Management Service Partners SWIFTReady for Corporates Cash Management Label Criteria 2012 This document explains the business criteria needed to obtain the SWIFTReady for Corporates Cash Management label, aimed at

More information

SEPA Country-Specific Information Italy

SEPA Country-Specific Information Italy SEPA Country-Specific Information Italy Cash Management & ebanking January 2014 Contents INTRODUCTION 3 END-DATE INFORMATION 3 IBAN CONVERSION SERVICE 3 SEPA PRODUCTS 4 SEPA CREDITOR IDENTIFIER (CI) 6

More information

Bankline internet banking import file layout user guide

Bankline internet banking import file layout user guide Bankline internet banking import file layout user guide Bankline internet banking import file layout user guide 2 Contents 1. Introduction to Bankline import...3 1.1 What is Bankline import?...3 1.2 How

More information

Spanish legacy branch code 4 numbers. Spanish legacy bank code 4 numbers

Spanish legacy branch code 4 numbers. Spanish legacy bank code 4 numbers SEPA in Spain Useful links Spanish official SEPA website (in Spanish language) http://www.sepaesp.es/ National Central Bank of Spain www.bde.es/bde/en Official Migration Guide for the Spanish market Download

More information

Q&A Payment Transaction Standardization in Europe and Switzerland

Q&A Payment Transaction Standardization in Europe and Switzerland Payment Transaction Standardization in Europe and Switzerland Version: October 2015 Payment Transaction Standardization in Europe and Switzerland General Introduction Starting February 1, 2014, Europe

More information

Service description. Corporate Access Payables

Service description. Corporate Access Payables Service description Corporate Access Payables Table of contents Page 2 of 12 1 INTRODUCTION... 3 2 STRUCTURE OF DOCUMENTATION... 4 3 AGREEMENT SET-UP... 4 4 AVAILABLE MESSAGE TYPES... 5 5 OFFERED PAYMENT

More information

CONTRL. Syntax and service report message. Edition 2014

CONTRL. Syntax and service report message. Edition 2014 EANCOM 2002 S3 Edition 2014 1. Introduction... 2 2. Message Structure Chart... 5 3. Branching Diagram... 6 4. Segments Description... 7... 8 6. Example(s)... 17 EANCOM 2002 S3 Part II The Messages 1. Introduction

More information

SWIFT Certified Application - Exceptions and Investigations

SWIFT Certified Application - Exceptions and Investigations Service Partner Programme SWIFT Certified Application - Exceptions and Investigations Label Criteria 2016 This document explains the criteria required to obtain the SWIFT Certified Application - Exceptions

More information

Background. IBAN Overview

Background. IBAN Overview International Bank Account Number ( IBAN ) IBAN Overview The International Bank Account Number ( IBAN ) is an international standard for identifying bank accounts across national borders in a way that

More information

Bankline internet banking import file layout user guide

Bankline internet banking import file layout user guide Bankline internet banking import file layout user guide Bankline Internet Banking Import File Layout User Guide 2 Contents 1. Introduction to Bankline import...3 1.1 What is Bankline import?...3 1.2 How

More information

Hal E-Bank Foreign payments (Format of export/import files)

Hal E-Bank Foreign payments (Format of export/import files) Hal E-Bank Foreign payments (Format of export/import files) Hal E-Bank Foreign payments: format of export/import files Version: 17.x.x.20 Author: HALCOM d.d., Ljubljana Editor: HALCOM a.d., Beograd, July

More information

USER INFORMATION GUIDE TO THE TARGET2 PRICING

USER INFORMATION GUIDE TO THE TARGET2 PRICING ATTACHMENT 2 USER INFORMATION GUIDE TO THE TARGET2 PRICING October 2007 Page 1 of 23 USER INFORMATION GUIDE TO THE TARGET2 PRICING Table of contents Introduction 4 1. General Overview of TARGET2 and the

More information

Migration of mandates based on NBB file. version July

Migration of mandates based on NBB file. version July Financial Supply Chain SEPA Migration of mandates based on NBB file version July 2013 www.ingsepa.com Background 1 Acquisition 1 Formats 1 DOM80 migration 2 Processing of the NBB migration file 2 SDD Mandate

More information

Infor LN Financials User Guide for Cash Management

Infor LN Financials User Guide for Cash Management Infor LN Financials User Guide for Cash Management Copyright 2015 Infor Important Notices The material contained in this publication (including any supplementary information) constitutes and contains confidential

More information

BT 24 User Manual 1. Useful information... 4 2. Application access... 6 2.1 First log into BT24... 6 2.2 Subsequent logins into BT 24... 6 2.

BT 24 User Manual 1. Useful information... 4 2. Application access... 6 2.1 First log into BT24... 6 2.2 Subsequent logins into BT 24... 6 2. BT 24 User Manual 1. Useful information... 4 2. Application access... 6 2.1 First log into BT24... 6 2.2 Subsequent logins into BT 24... 6 2.3 Password changing... 7 2.4 How I reset the password... 8 2.5

More information

Customer Statement - MT940 with Structured Information To Account Owner

Customer Statement - MT940 with Structured Information To Account Owner General Information The MT940 customer statement message is an electronic message containing financial statement information for customers concerning their accounts. Danske Bank can send a MT940 either

More information

SEPA in Netherlands. Quick facts. International Bank Account Number (IBAN) IBAN structure. 66 SEPA Country Sheets - Netherlands

SEPA in Netherlands. Quick facts. International Bank Account Number (IBAN) IBAN structure. 66 SEPA Country Sheets - Netherlands SEPA in Netherlands Useful links Information campaign, by National Forum on SEPA migration www.overopiban.nl IBAN-Acceptgiro information www.acceptgiro.nl/ IBAN BIC conversion service www.ibanbicservice.nl

More information

On top of this Italy requested waivers that allow usage of some legacy formats and niche products until 1 st February 2016.

On top of this Italy requested waivers that allow usage of some legacy formats and niche products until 1 st February 2016. Since 1 st February 2014, SEPA became a reality and succeeded in harmonising the European payment landscape. However, in order to support strong local market practices, some local flavours remain applicable

More information

SWIFT MT940 MT942 formats for exporting data from OfficeNet Direct

SWIFT MT940 MT942 formats for exporting data from OfficeNet Direct SWIFT MT940 MT942 formats for exporting data from OfficeNet Direct January 2008 2008 All rights reserved. With the exception of the conditions specified in or based on the 1912 Copyright Act, no part of

More information

SEPA Creditors Guide. SEPA Direct Debit Core Scheme. Version 1.4 Final Page 1 of 38

SEPA Creditors Guide. SEPA Direct Debit Core Scheme. Version 1.4 Final Page 1 of 38 SEPA Creditors Guide SEPA Direct Debit Core Scheme Version 1.4 Final Page 1 of 38 Log of Revisions to the SDD Creditors Guide Version number Version1.1 Brief description of revision Comprehensive guide

More information

EUROPEAN DIRECT DEBIT. ING Luxembourg s SEPA Direct Debit. European Direct Debit 1

EUROPEAN DIRECT DEBIT. ING Luxembourg s SEPA Direct Debit. European Direct Debit 1 EUROPEAN DIRECT DEBIT ING Luxembourg s SEPA Direct Debit European Direct Debit 1 EUROPEAN DIRECT DEBIT OR SEPA DIRECT DEBIT 3 Introduction to the European direct debit 3 Which countries are part of SEPA?

More information

Payment Status Report

Payment Status Report Payment Status Report Implementation Guidelines Version 1.0 Beligian Finance Sector Federation rue d Arlon, 82 B-1040 Brussels http://www.febelfin.be T +32 2 507 68 11 F +32 2 888 68 11 2 Table of Contents

More information

Format Validation Tool ING Commercial Banking

Format Validation Tool ING Commercial Banking Format Validation Tool ING Commercial Banking Help instructions and additional information For Payment and collection formats Publication date: 11/09/2013 This document is meant for both ING internal employees

More information

CONDITIONS FOR MAKING PAYMENT TRANSACTIONS

CONDITIONS FOR MAKING PAYMENT TRANSACTIONS CONDITIONS FOR MAKING PAYMENT TRANSACTIONS 1. GENERAL PROVISIONS 1.1 In the Conditions for Making Payment Transactions (hereinafter referred to in this document as the Conditions) the bank issues the terms

More information