Den här sidan finns inte på ditt språk, därför visas den engelska sidan.
Cash management egateway

Supports a centralised payment and collection factory

Corporate eGateway is Nordea’s file-based, mass payment service with one point of entry for bulk payments and collections in the Nordic and Baltic countries, Germany, Russia, UK, Canada and the US.

The service provides a uniform file interface that covers all relevant types of domestic and cross-border payments, including direct debits in the Nordic area. In Sweden, the service makes it possible to handle both PlusGiro and Bankgiro payments in one file.

Centralised and flexible payment processing

Centralisation of the payment infrastructure limits the maintenance of system interface to one-point-of entry and one format. The need to adapt to local changes is reduced, and external and internal changes of the IT infrastructure can be made without interfering with one another.

It is possible to mix payment instructions to all countries in the same file. Both outgoing and incoming payments are handled in a way that facilitates straight-through-processing and automatic reconciliation for both the payer and the payee.                  


How eGateway can benefit your organisation

• One system interface, one banking partner, one agreement and one support function

• Possibility to build a Shared Service Centre for payments

• Automated reconciliation processes

• Reduced operating and transactional costs

• The same syntax for all countries and reduced need to adapt to local changes

• Limited maintenance of system interface

• External and internal IT changes can be made independently 

eGateway technical details

eGateway services Documents Format Descriptions Security Cut-off times eGateway services

eGateway services

For information on eGateway services for account statements, authorisation, credit advice, debit advice, direct debit, payments, status reports, click here >> (pdf, 462 KB)



Corporate eGateway makes it possible for company groups to use one banking interface for the Nordic and Baltic countries as well as Germany, Poland, the UK and USA and Canada. Through Nordea's partner banks a large number of other countries worldwide will be included as well. By setting-up a centralised EDI server on group level, a company can have a single technical interface with Nordea in terms of file format, communication and security.

To find relevant business and technical information on all services offered by Corporate eGateway, select from below.

Account structures

This document provides information about the possibilities for sending and receiving BBAN and IBAN account numbers.

The structures of IBAN and BBAN accounts are also described in details on country level.

Nordea Account Structure (pdf, 459 KB)

Functional specifications

Each country has different clearing and settlement infrastructures. Therefore each service has been described in detail, including for instance how Nordea processes disbursements, collections and statements through Corporate eGateway.

To find a specific description, covering the essential business information needed when using the Corporate eGateway service, see documents below.

Functional specification for Credit Advices (pdf, 1 MB)

Functional specification for Nordea Direct Debits (NDD) (pdf, 752 KB)

Functional specification for Nordea Payments (pdf, 715 KB)

Functional specification for XML Direct Debit (pdf, 1 MB)


Corporate eGateway exchanges EDIFACT files via either VPN, Connect Direct, SFTP (all through FTP) or a VANS operator. For XML ISO20022 Corporate eGateway offers WebServices for exchanging files.

Corporate eGateway and the local payment systems exchange files in country-specific or SWIFT formats via Nordea's internal network.

In addition, Corporate eGateway offers communication via SWIFTNet, for both EDIFACT and XML ISO20022, using SWIFTNet FileAct.

For detailed information about communication solutions offered by Corporate eGateway, select from below.

For access details please contact your local Cash Management adviser.

Security and Communication description for SWIFTNet FileAct (pdf, 154 KB)


To ensure successful implementation, we have multilingual and highly qualified banking professionals with local knowledge and regional expertise to help you meet your strategic business goals. Implementation of Corporate eGateway requires a good organisation, a good understanding of the product and good communication between all parties involved.

The implementation guide is aimed at integration suppliers and customers who are about to integrate a financial system with Corporate eGateway. This guide describes the project organisation tasks and the planning of the implementation. Each chapter contains a checklist.

Implementation guide (pdf, 363 KB)


Definition of business and technical vocabulary concerning Corporate eGateway.

eGateway Glossary (pdf, 632 KB)

Format Descriptions

Format Descriptions

Most customers use an EDI server or similar application for file conversion, security and communication since those routines are poorly supported by the ledger system itself. The EDI server communicates with the ledgers in the ledger system's internal file format and with Nordea's Message centre in either EDIFACT or XML ISO20022 format.

An EDI server has a number of built-in functionalities, but mainly it provides a company with a stand-alone EDI infrastructure. We strongly recommend customers to use an EDI server instead of implementing EDI solutions directly in the ledger system.

To find detailed information about the technical set-up, including Message Implementation Guides (MIG) used by Corporate eGateway, select from below.

Acknowledgement receipt

Corporate eGateway validates file security and checks file content on a syntax level, when receiving a file. A syntax and service report message (CONTRL) is returned from Corporate eGateway. The message used is either CONTRL for EDIFACT or pain.002 for XML ISO20022. The message indicates either that Nordea rejects the instructions because the received file has an invalid syntax or that Nordea assumes responsibility for further processing of the instructions.

For a full understanding of the use of this message see the documents on the right.

Message flow and use of EDIFACT (pdf, 520 KB)

Format description - CONTRL (pdf, 312 KB)

EDIFACT messages

Below you will find the latest version of all EDIFACT format descriptions for Corporate eGateway (all links open in a new window):

Please note that EDIFACT format is only in use for existing Corporate eGateway customers. For new customers we offer XML ver. 3 (CGI) as the only format.


DocumentVersion Comments
MIG PAYMUL6.4 (pdf, 906 KB)Changes since 6.3 (pdf, 79 KB)
Payments outside of the Nordic area (RfT)2.1 (pdf, 679 KB)Changes since 2.0 (pdf, 31 KB)
PAYMUL North America1.7 (pdf, 781 KB)Changes since 1.6 (pdf, 71 KB)
MIG CONTRL 1.2 (pdf, 401 KB)Changes since 1.1 (pdf, 82 KB)
MIG BANSTA3.0 (pdf, 404 KB)Changes since 2.9 (pdf, 18 KB)
MIG DEBMUL2.1 (pdf, 776 KB)Changes since 2.0 (pdf, 80 KB)
MIG CREMUL3.13 (pdf, 742 KB)Changes since 3.12 (pdf, 18 KB)

Direct Debit

DocumentVersion Comments
MIG DIRDEB1.4 (pdf, 692 KB)Changes since 1.3 (pdf, 30 KB)
MIG AUTHOR11.5 (pdf, 498 KB)Changes since 1.4 (pdf, 30 KB)
MIG AUTHOR21.6 (pdf, 517 KB)Changes since 1.5 (pdf, 30 KB)

Account Statements

DocumentVersion Comments
MIG FINSTA2.53 (pdf, 428 KB)Changes since 2.52 (pdf, 27 KB)
MIG FINSTA, App12.53 (pdf, 101 KB)Changes since 2.52 (pdf, 27 KB)

Examples per payment types

DocumentVersion Comments
PAYMUL (Europe)1.3 (pdf, 256 KB)
PAYMUL (Nordic and Baltic countries)
1.8 (pdf, 832 KB)
PAYMUL (North America)
1.1 (pdf, 165 KB)

Supporting material

Payment types3.6 (pdf, 360 KB)

XML ISO20022 messages

Transactions in XML ISO20022 - Common Global Implementation (CGI) compliant

DocumentVersion Comments
MIG XML ISO20022 pain. (pdf, 781 KB)Changes since 2.0 (pdf, 249 KB)
MIG XML ISO20022 pain. (pdf, 454 KB)Changes since 1.2 (pdf, 220 KB)
MIG XML ISO20022 camt. (pdf, 515 KB)Changes since 1.2 (pdf, 205 KB)
Bank Transaction Code List for camt. (pdf, 440 KB)Changes since 1.3 (pdf, 214 KB)
MIG XML ISO20022 camt.054.001.02 Credit Advices1.2 (pdf, 667 KB)Changes since 1.1 (pdf, 228 KB)
MIG XML ISO20022 camt.054.001.02 Debit Advices1.7 (pdf, 681 KB)Changes since 1.6 (pdf, 223 KB)
Bank Transaction Code List for camt. (pdf, 148 KB)Changes since 1.1 (pdf, 69 KB)

Direct Debit

DocumentVersion Comments
Direct Debit Reversal pain. (pdf, 500 KB)Changes since 1.0 (pdf, 183 KB)
Direct Debit Initiation pain. (pdf, 615 KB)Changes since 1.0 (pdf, 214 KB)
Mandate Initiation pain. (pdf, 622 KB)Changes since 1.1 (pdf, 207 KB)
Mandate Cancellation pain. (pdf, 596 KB)Changes since 1.1 (pdf, 206 KB)
Mandate Acceptance Report pain. (pdf, 598 KB)Changes since 1.0 (pdf, 185 KB)

Direct Debit cancellation request

DocumentVersion Comments
Resolution of Investigation camt. (pdf, 468 KB)
Payment Cancellation Request
1.1 (pdf, 536 KB)Changes since 1.0 (pdf, 182 KB)

Supporting material

DocumentVersion Comments
Payment Types - pain. (pdf, 735 KB)
Pain.001 v3 examples, the Nordics
1.6 (pdf, 807 KB)
Pain.001 v3 examples, non-Nordics
1.7 (pdf, 595 KB)
Direct Debit examples, the Nordics 0.8 (pdf, 1 MB)

External material

DocumentVersion Comments
Payments - Maintenance 2009 Message Definition ReportSeptember 2009 (pdf, 9 MB)ISO 20022

Other formats

Below you will find other format descriptions provided by Nordea which may be used in relation to Corporate eGateway (all links open in a new window):


DocumentVersion Comments
1.0 (pdf, 22 KB)
BAI CAD1.0 (pdf, 27 KB)

Account statements

DocumentVersion Comments
MT9401.4 (pdf, 87 KB)

Message flow

It is important to have full understanding of what and how Nordea's Message Centre performs validation of all messages.

For detailed information about the message flow process in Corporate eGateway, select from below.

Message flow and use of EDIFACT (pdf, 310 KB)

Message flow and use of XML ISO20022 Messages (pdf, 492 KB)



Participants must make sure that payment orders are valid instructions to Nordea in order to prevent fraud. It must be ensured that an authorised party gives instructions in such a way that it cannot subsequently be denied that the instructions were sent. Moreover, it must be ensured that the instructions cannot be changed or manipulated by anybody during transmission. To ensure that, transactions should be subject to integrity, origin authentication and non-repudiation of origin techniques.

AUTACK (Authentication and Acknowledgement message)

The AUTACK message is used to authenticate and secure the complete interchange. One AUTACK message is included per interchange conveying one or more digital signatures computed on the complete data of the entire interchange. The digital signature in the AUTACK message is verified using an RSA algorithm and a public key that Corporate eGateway has received from the customer. The digital signature in the AUTACK message ensures that the information comes from a valid party and that the information has not been changed or manipulated by any other party during the transfer.

Use of Security

Corporate eGateway uses security solutions based on either RSA (AUTACK) or PKI (PGP Pretty Good Privacy).

Corporate eGateway makes it possible for you to send or receive files which are fully encrypted, eg securing confidentiality of all transmitted interchanges. For this Corporate eGateway uses worldwide EDIFACT standards as CIPHER and CONFID. In addition, we offer the use of the PGP (Pretty Good Privacy) security method.

We also offer transmission via SWIFTNet FileAct applying the security provided by SWIFTNet.

Related documentation

Public Key Document (pdf, 70 KB)

PGP AUTACK Key Exchange (pdf, 130 KB)

PGP Factsheet (pdf, 97 KB)

Cut-off times

Corporate eGateway's list of cut-off times provides the cut-off times used by the Message Centre and the local cut-off times for each service and country that are part of Corporate eGateway. It describes the date of entry for each booking applied within the Nordea banks and the expected availability at the beneficiary's bank.

Cut-off times (pdf, 827 KB)