Cross-border payments in Denmark

Cross-border payments in Denmark The supplier payment format (DBF) Version 1.2.0 Publishing date 16 January 2018

Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3 1.2 History... 3 2 INFORMATION ABOUT THE SERVICE... 4 2.1 Restrictions to the service... 4 2.2 Parties... 4 2.3 Agreement... 4 3 EXAMPLE SCENARIO: CROSS-BORDER PAYMENT... 5 4 FORMAT OVERVIEW... 6 4.1 Business rules... 6 4.2 Format structure... 6 4.3 Payment types... 6 4.3.1 CROSS-BORDER PAYMENT... 6 5 IMPLEMENTATION GUIDELINE... 7 5.1 Data format rules... 7 5.1.1 STATUS... 7 5.2 Content... 7 5.3 Field description... 8 5.4 Beneficiary bank... 11 5.5 Business example... 11 5.5.1 BUSINESS EXAMPLE: CROSS-BORDER PAYMENT... 11 5.6 File example... 12 5.6.1 FILE EXAMPLE: CROSS-BORDER PAYMENT... 12 The DBF format - cross-border payments Page 2 (12)

1 Introduction Handelsbanken s implementation guide for the Danish format for cross-border payments, describes in detail the information to be included and how it is to be specified when initiating a cross border payment from an account with Handelsbanken Denmark. In this guide the format is abbreviated to DBF (Danske Banks Format). The description is specific to Handelsbanken s services and routines and may be used only when communicating with Handelsbanken. 1.1 Related documents This message implementation guide is based on the Danish format Business Online foreign transfers as defined and published by Danske Bank. Foreign Transfers from Denmark Business Online format, English 1.2 History At Handelsbanken, changes to version numbers are made according to the following guidelines. The original version is 1.0.0. The last digit is changed when the format descriptions are changed, for example text clarifications and examples. The second digit is changed if minor changes are made to the format such as new countries or changes in the payment type. The first digit is changed (thus becoming a completely new version) if the format changes mean that the customer will have to make adaptations in order to continue using the service. In this case, all customers affected are informed of the new version and what the changes involve Version Date Description 1.2.0 2017-12-01 Review of the file format. 1.1.1 2016-12-16 Minor updates 1.1.0 publlished 2012-11-22 Update due to changes in country specific information regarding China. 1.0.0 published 2009-01-15 The DBF format - cross-border payments Page 3 (12)

2 Information about the service This guide contains a description for cross-border payments. When communicating with a DBF message you are able to request a cross-border payment from an account held at Handelsbanken Denmark to an account held at a foreign bank or to a local bank in a foreign currency. In communication with Handelsbanken it is possible to request normal and express payments. 2.1 Restrictions to the service It is not possible to request cross-border cheque payments or financial payments. 2.2 Parties Name of party Customer Bank Description Customer or its software provider Handelsbanken 2.3 Agreement A customer must be connected to Handelsbanken s Electronic Banking service GlobalOn-Line and must have the authority to send files to the bank. Please see separate agreement/power of Attorney for further details. Furthermore, a test file must be submitted by the customer. When the test file has been approved by the bank, the customer can send files to the bank containing payment orders to be executed. For further information, please contact your local branch at Handelsbanken. The DBF format - cross-border payments Page 4 (12)

3 Example scenario: Cross-border payment Implementation guide Description: This scenario illustrates an example of the process when a customer requests a cross-border payment from Handelsbanken Denmark through Handelsbanken s Electronic Banking service GlobalOn-Line. 1) The Customer uploads the file with payment orders via GlobalOn-Line 2) The Bank receives the payment file and validates the file format and the content of the file. 3) The Bank accepts or rejects the file and the payment orders. A payment status report can be sent with information about rejected payment orders, if applicable. 4) The file is authorised by the authorised user/(s) according to the mandate 5) The Bank debits the account/(s) and executes the payment orders on the execution date 6) The status of the payment (for example Rejected, Pending, Processed) is always shown under Search payment in GlobalOn-Line. Cross-border payment Customer Customer Bank Bank Customer compiles information for the payment Customer sends the payment to the bank Cross-border payment Bank receives the payment Information about rejected and pending payments are presented via GlobalOn-Line Bank accepts or rejects the payment Bank executes the payment The DBF format - cross-border payments Page 5 (12)

4 Format overview This chapter contains a business oriented description of the DBF format for cross-border payments that is approved for communication with Handelsbanken. Exceptions at field level for Handelsbanken s implementation of the Supplier payment are explicitly specified in the Comment column in chapter 5. In communication with Handelsbanken, please pay attention to the following rules: 4.1 Business rules [1] For payments with due dates on Saturday, Sunday or other banking holidays, the payment day will be moved to the closest following banking day. [2] The payment date can be stated for a maximum of 12 months ahead. [3] The payment date can be exceeded by a maximum of 20 days. In that case the payment will be executed the following banking day. If the payment date is exceeded by more than 20 days the payment will be rejected. [4] Cheque payments are not available in this file format. [5] The Beneficiary s name and address and the Beneficiary s Country Code, are mandatory for all crossborder payments [6] The Beneficiary account is to be identified using the IBAN format where available. Please note that IBAN is mandatory for payments in EUR within the EU, EEA and Switzerland. In some countries IBAN cannot be used, so in these circumstances, the Beneficiary account must instead be identified using the BBAN format. When the Beneficiary account is identified using the IBAN format, the NationalBankID/Clearing number is not to be used. [7] The Beneficiary bank should preferably be identified using the BIC and, when requested, the NationalBankID (see note 6 above). [8] Allocation of fees (Cost account transfer) is mandatory for all cross-border payments. As a result of Denmark s national implementation of the PSD2 regulation (Payment Service Directive), from the beginning of January 2018, it is no longer be possible for us to use OUR/BEN for cost sharing in crossborder payments within the EU/EEA, regardless of currency with or without exchange. The cost account transfer code in field 17 should be set to 1 = SHA. Handelsbanken will automatically convert the cost sharing to SHA if OUR/BEN has been used, in accordance with the regulation 4.2 Format structure The DBF format consists of one record with information necessary to create a cross-border payment from Handelsbanken Denmark. Cross-border Payment 1..n Payment 4.3 Payment types In the DBF format cross-border payments can only be initiated from an account held at Handelsbanken Denmark. Cross-border cheque payment are not approved for communication with Handelsbanken, neither are intra-company payments. 4.3.1 CROSS-BORDER PAYMENT A cross-border payment is a payment from Handelsbanken Denmark to an account held at a foreign bank or a payment to a Danish bank in a foreign currency. A payment can be executed as a normal or an express payment. See Business rules above. The DBF format - cross-border payments Page 6 (12)

5 Implementation guideline This section consists of a technical descriptions of the message types as defined in the DBF format that are approved for use in communication with Handelsbanken. 5.1 Data format rules [1] The file must contain one line for each payment. A field must start and finish with quotation marks (") and the fields must be separated by a comma (,). You must not use quotation marks in the individual fields. [2] The fields have no fixed lengths, which means that you do not have to add spaces or zeros in front or behind the content in a field. In the field description, the maximum length is described for the information to be stated in each field. [3] Mandatory fields must always be filled in. An empty field is to be indicated with two quotation marks (""). When there are no more required fields in a payment, you can omit the remainder of the fields. [4] Decimal character for amount fields is always decimal comma (,) and two decimals are stated. [5] Date is entered in the format DDMMYYYY. 5.1.1 STATUS M= Mandatory O= Optional N= Not used A= Accepted but not acted upon If fields are marked with Accepted but not acted upon values in these fields will be ignored by Handelsbanken. If values are filled in fields marked with Not used the payment file and/or the payment may be rejected. Please note that some fields are mandatory in the Handelsbanken application but are optional in the original format description, Business Online as defined by Danske Bank. 5.2 Content This section contains the format description with the exceptions and additions required by Handelsbanken to ensure proper processing of the payments. The DBF format - cross-border payments Page 7 (12)

5.3 Field description Description: The DBF format contains one record containing necessary information to create a cross-border payment from Handelsbanken Denmark. Field No. Field Name No. of char. Format 1 Command 8 Alphanum 2 From account 11,14 or 18 Alphanum 3 To account 35 Alphanum Field Status M M M Description Command for create payment: CMUO Example BBAN: 08901234567 or 08900001234567 Example IBAN: DK3608900001234567 Beneficiary account number. Use IBAN for cross-border payments to countries where IBAN is mandatory. Comment Must be an account held at Handelsbanken Denmark IBAN 18 characters or BBAN 11 or 14 digits (clearing number 4 digits + account number 7 or 10 digits) If beneficiary account is stated as IBAN, BIC of beneficiary bank is optional. 4 Currency 3 Alphanum M ISO currency code 5 Amount 15 Num M Max. 2 decimals. (length of field is incl. decimal comma) 6 Not used N Field is not used. Specify as blank ( ). Separate with comma. 7 Date 8 Num M Payment date (day of payment/debit) in format: DDMMYYYY 8 Transfer type 1 Num M 1 = Normal payment 9-12 Beneficiary name and address 4*35 Alphanum M 3 = Express payment Name and full address of the beneficiary is mandatory. At least line 1 (name) and 4 (city) must be filled in. 13-16 Not used N Fields are not used. Specify as blank ( ). Separate with comma 17 Cost account transfer 1 Num M Allocation of fees: 1 = To be shared (SHA) 2 = Sender pays (OUR) 3 = Beneficiary pays (BEN) Transfer type is mandatory. Not used Please see Business rules 4.1 The DBF format - cross-border payments Page 8 (12)

Field No. Field Name 18-21 Message to beneficiary No. of char. Format 4*35 Alphanum Field Status Description Comment O Message to the beneficiary For payments in CNY to beneficiaries in Mainland China the first line in the message to the beneficiary must contain one of the following codes: 22-29 Not used N Fields are not used. Specify as blank ( ). Separate with comma 30 Beneficiary s country code 2 Alphanum M ISO country code of beneficiary 31-38 Not used Fields are not used. Specify as blank ( ). Separate with comma. 39 Sender s Reference 20 Alphanum A Text on sender s account statement. 40-50 Not used N Fields are not used. Specify as blank ( ). Separate with comma. 51 BIC of beneficiary bank 11 Alphanum M/O BIC of beneficiary bank, 8 or 11 characters. * /TRADE/ indicating the payment regards purchase of physical goods * /TRADE/SRV/ indicating the payment regards purchase of service Not used Accepted but not acted upon Not used If beneficiary account is stated as IBAN, BIC of beneficiary bank is optional. The DBF format - cross-border payments Page 9 (12)

Field No. Field Name No. of char. Format Field Status Description Comment 52 Bank Code 2 Alphanum M/O Bank code for beneficiary s bank, should be stated for: Mandatory for some countries 'AU' = Australian Bank State Branch Code, BSB (Australia) 'CC' = Canadian payments Association Payment Routing (Canada) 'HK' = Hong Kong National Clearing Code, CHATS (Hong Kong) 'RU' = Russian Central Bank Identification Code (Russia) 'FW' = ABA/FedWire Routing Number (USA)/ 'SC' = Sort Code (South Africa) 'CN' = CNAPS code (China) 53 Bank Number beneficiary bank 12 Num M/O National bank ID for beneficiary s bank 6 digits Australian Bank State Branch Code, BSB (Australia): 9 digits Canadian payment association (Canada): 6 digits Hong Kong National Clearing Code (CHATS) 9 digits Russian Central Bank Identification Code 9 digits ABA/Fed Wire Routing Number (USA) 6 digits Sort Code (South Africa) 12 digits CNAPS Code (China) Mandatory for some countries 54-56 Not used Fields are not used. Specify as blank (""). Separate with comma. The DBF format - cross-border payments Page 10 (12)

5.4 Beneficiary bank The Beneficiary bank should preferably be identified using the BIC and, when requested, the Bank number/national Bank ID. The Beneficiary account is to be identified using the IBAN format where available. Please note that IBAN is mandatory for payments in EUR within the EU, EEA and Switzerland. In some countries IBAN cannot be used, so in these circumstances, the Beneficiary account must instead be identified using the BBAN format. When the Beneficary account is identified using the IBAN format, the Bank number/national Bank ID is not to be used. 5.5 Business example In this section a business example of a DBF cross-border payment is presented. The example states the fields necessary expressed from a functional point of view. A corresponding file example is presented below. 5.5.1 BUSINESS EXAMPLE: CROSS-BORDER PAYMENT This is an example of a normal cross-border payment. Field name Value Comment Command CMUO Command for creating a cross border payment From account 08901234567 To account Currency GB29NWBK60161331926819 GBP Amount 9933,74 Date 18052017 Transfer type 1 Normal payment Name and address John Smith Gamle vejen 21 11256 Copenhagen Cost account transfer 1 Shared costs (SHA) Message to beneficiary Invoice 23 Beneficiary s country DK Sender s Reference 12345 BIC LOYDGB22 The DBF format - cross-border payments Page 11 (12)

5.6 File example This file example corresponds to the business example presented above. 5.6.1 FILE EXAMPLE: CROSS-BORDER PAYMENT In this section one basic file example of a cross-border payment is presented. "CMUO","08901234567","GB29NWBK60161331926819","GBP","9933,74","","18052017","1","John Smith","Gamle vejen 21","11256","Copenhagen","","","","","1","Invoice 23","","","","","","","","","","","","DK","","","","","","","","","12345","","","","","","","","","","","","LOYDGB22","","","","","", The DBF format - cross-border payments Page 12 (12)