powerpoint presentation vendor webinar … · title: powerpoint presentation author: nordkvist,...

Welcome Making it possible

Welcome to Nordea’s webinar for vendors

• SEPA end date is approaching with

increasing pace (October 2016)

• Follow up from the webinar in December

• Corporate customers are depending on

both their banks and their ERP vendors/IT

consultants to become SEPA compliant

• Nordea is committed to support vendors

in your development of bank integration

towards Nordea

• www.nordea.com/vendors

• Newsletters

• Webinars

Webinar organizer:

Mikael Kepp, Vendor relationship management

[email protected]

• 31/05/2016

2 • Nordea's XML MIGs

http://www.nordea.com/vendors

mailto:[email protected]

Nordea’s XML MIGs

Speaker:

Per Nordkvist

Global Business Developer

• 31/05/2016


• In theory there is only one standard to

comply with…however there might be

bank specific flavors/categorization

• “formats are easy to manage - just inform

us where the differences are”

• The complete MIGs are available at

www.nordea.com/vendors

• Purpose of today’s webinar is to

proactively support you in developing

bank integration to Nordea’s Corporate

Access

• Per Nordkvist has many years of

experience and knowledge working with

and developing payments and file-based

solutions


Practicalities

• Webinar is being recorded

• Questions are welcome

• Send questions during the presentation

• Use the Question feature on the Dashboard

to the right on your screens

• Per will answer the questions verbally at the

end of the session

• Material will be uploaded to


• Including questions/answers

• Enjoy the webinar

• 31/05/2016


Microphones are

muted


Nordea's XML MIGs

Webinar 31 May 09.00-10.00 CET

Per Nordkvist

30/05/2016

SEPA Compliance

This is a standard

“Chapter Divider“ to

support the agenda

slide

• General information and background to Nordea’s

XML MIGs

• What to pay special attention to in relation to

Nordea’s XML MIGs

• Frequently asked questions about Nordea’s XML

MIGs

Background - launching Nordea Corporate Access

1. Regulatory compliance

• SEPA End Date for non-euro countries 31st of October 2016

2. Technology & architecture

• Simplification need within Nordea’s many file transfer solutions

3. Commercial

• Customer demand for an updated and harmonized Nordea channel offering

• 31/05/2016


Nordea’s Corporate Access XML MIGs

Nordea’s MIGs are constructed as recommended by local Nordic/Baltic Bankers Associations.

Note: Current “SEPA” MIG as used by “in-Euro”

countries do not cover domestic payment types

within the Nordic area, i.e. ERP’s & customer’s

must adhere to Nordea’s guidelines (MIGs).

Mandatory impact

High impact

Medium impact

Impact on

Nordea’s

MIGs

• 31/05/2016


http://www.swedishbankers.se/web/bf.nsf

• All payment types for Denmark, Norway & Sweden *

• Domestic and International, supplier, salaries, pensions, taxes and

intercompany payments

• All currencies

• Supports all currencies and payments from currency accounts

• One format

• ISO20022 XML * *

• pain.001.001.03

• pain.002.001.03

• camt.054.001.02D

• Communication methods

• H2H (AS2, FTP/VPN, SFTP, SWIFTNet FileAct & Webservices * * *)

• Corporate Netbank File Transfer

* = Finland & Baltics planned for 2017

* * = camt.055.001.01 (Cancellation) & camt.029.001.03 (Resolution Of Investigation) to be offered Q4 2016

* * * = Webservices to be launched Q3 2016

1

Corporate Access

• 31/05/2016


This is a standard


support the agenda

slide


XML MIGs


Nordea’s XML MIGs


MIGs

Nordea MIGs – related to local Nordic/Baltic Bankers

Associations MIGs

• Nordea is, to a large extent, following the recommendations in the MIGs

made by each Local Nordic/Baltic Bankers Association. Some of the fields

included is however categorized as Bilaterally Determined (BD) fields.

• This document contains high level information/summary on use of the

Bilaterally Determined (BD) fields in the pain.001.001.03 as defined by the

local Nordic/Baltic Bankers Associations MIGs when integrating towards

Nordea.

• The document is just meant to give vendors an indication of fields to be

especially aware of. For the detailed information, please see the MIG on

nordea.com

• www.nordea.com/vendors

• BD fields available by local Nordic/Baltic Bankers Association MIGs, but

not used by Nordea will just be ignored.

• 31/05/2016



Use of BD fields on Group Header level

• Not used

• Group Header/Authorisation/Proprietary

• Optional/conditional to use

• Control Sum (Note: If used it will be validated by Nordea)

• Initiating Party/Name

• Initiating Party/Identification/Organisation Identification/BICOrBEI

• Required

• Initiating Party/Identification/Organisation Identification

• Other/Identification: Customer Id as assigned by Nordea, also referred to as

“Signer ID”. Can be connected to digital certificate used to secure the file using

Secure Envelope. Note: Must be used when H2H file communication used, except

for SWIFTNet FileAct.

• Scheme Name/Code: CUST

1.0 GroupHeader <GrpHdr> [1..1] GroupHeader32

• 31/05/2016


Use of BD fields in Payment Information level

• Optional/conditional

• BatchBooking: Optional to use for domestic payments from Denmark & Norway. Optional

to use for cross-border payments from Sweden. Default if not sent or used:

• Domestic payments = Batch booking

• Cross-border payments = Single booking

• ControlSum (Note: If used it will be validated by Nordea)

• Instruction Priority

• Not used

• Payment Information

• Debtor/dentification/Organisation Identification/BICOr BEI

• Required

• Debtor/Identification/Organisation Identification/Other

• Identification: Customer agreement identification number as assigned by Nordea

• SchemeName/Code: BANK

• Debtor Account

• Identification/Other/Scheme Name/Code (If not IBAN used)

• Currency (always)

2.0 PaymentInformation <PmtInf> [1..n] PaymentInstructionInformation3

• 31/05/2016


Use of BD fields in Credit Transfer Transaction

Information level

• Required

• Creditor Account (if used)

• Identification/Other/Scheme Name/Code (If not IBAN used)

• Optional/conditional

• Instruction Identification

• Exchange Rate Information (rate, type, contract id)

• Charge Bearer

• Cheque Instruction

• Cheque Type must be used if Payment method “CHK”

• Note: Delivery Method/Code can be omitted

• Intermediary Agent 1

• BIC

• Not used

• Instruction Priority

• Instruction For Creditor Agent

2.27 CreditTransferTransactionInformation <CdtTrfTxInf> [1..n] CreditTransferTransactionInformation10

• 31/05/2016


This is a standard


support the agenda

slide


XML MIGs


Nordea’s XML MIGs


MIGs

Nordea’s XML MIGs – Frequently asked questions…1/2

• No, the payment will not be rejected. There are other values in the payment that will determine if a payment is a SEPA transaction, or not, such as currency, country code, etc. Nordea will always equalize the handling of code “SEPA” as “NURG”

If I use code “SEPA” in <PmtTpInf>, but the payment is aimed for Denmark (or USA), will Nordea reject this payment, because I have not used code “NURG”?

• SEPA End-data regulation requires only IBAN and no bank details for beneficiary account for EURO payments within the EU/EES area. Nordea has chosen, in order to simplify for customers, to apply the same rule for all currencies for payments within EU/EES area.

Why can’t I use bank clearing code (Sort code) for beneficiary bank when making payments to UK?

• Yes, it is possible to mix different payment currencies towards beneficiaries through Corporate Access.

Will I be able to send all payments in the same message, i.e. <PmtInf>, for example both EUR and US currency.

• Generally No, but there is always a limit when it comes to communication protocols. Nordea recommends that the file doesn’t contain more than 3.000 “batches” (<PmtInf>), with a maximum of 10.000 transactions per “batch”. i.e. not more than 30 million transactions.

Is there a maximum file size/transaction size of the XML when sending the file to Nordea?

• 31/05/2016


Nordea’s XML MIGs – Frequently asked questions…2/2

• These ID’s are set by the customer, they have to be unique, and will be duplicate controlled by Nordea for a min. period of 90 calendar days.

For <MsgID>, <PmtInfId> and <EndToEndId> do I choose these ID’s or are these ID’s provided by Nordea?

• Payments received by Nordea after cut-off time, will normally be executed the following banking day.

• Note: Some exceptions exist, example: Salary/Pension payments Sweden, which will be rejected after cut-off time.

What happens if a payment is sent after cut-off time? Will it be rejected?

• This is a SEPA payment (i.e. cross-border payment). If payment currency is EUR and beneficiary within EU/EES area – then it is a SEPA payment.

We have the following scenario: Debtor account = NOK; Beneficiary is in Norway and holds an IBAN account; Payment currency = EUR. What payment type is this?

• Yes – credit notes can be specified under <Strd> by using code “CREN” + reference/number and amount.

• Note: Min. one “CINV” (debet invoice) must be present when using credit notes and total amount may not result in a credit.

Can we handle credit notes via your service in XML format?

• 31/05/2016


• A “tip” and “reminder” before the end of this

Webinar

This is a standard


support the agenda

slide

Nordea’s Corporate Access XML Test Tool – your support

Nordea are providing a web-based Test Tool, which will enable customers and

ERP vendors to:

Check correct syntax

New: Enable to see the message structure via the UI, including the

possibility to download the syntax /compliance result, pain.002, as a file

Validate general ISO/CGI business rules

Validate Nordea specific business rules

New: Enable to see the message structure via the UI, including the

possibility to download the status report result, pain.002, as a file

New: Receive information about how the camt.054 report will look like

including possibility to download the debit advice result as a file (Will be launched

10 June, 2016)

May be downloaded

as files (pain.002 &

camt.054)

• 31/05/2016


Corporate Access

Note: Nordea’s new file-based payment services will for the future replace all

current file-based payment offerings (incl. formats)

XML

XML

XML XML

XML

XML

XML

File based payments in EUR

only available in ISO20022 XML

after 31 October 2016

• 31/05/2016


Closing remarks

• Recap of today’s information:

• Recorded session &

questions/answers will uploaded to


• Contact [email protected] for

support, e.g. regarding:

• Documentation

• Testing tool

• 31/05/2016



mailto:[email protected]

Making it possible nordea.com/vendors

powerpoint presentation vendor webinar … · title: powerpoint presentation author: nordkvist,...

Documents