Corporate Access

Corporate Access File Transfer gives you a wide choice of communication methods to support your needs for automated file transmission, offering integration with the following channels: 

• AS2
• SFTP
• SWIFTNet for Corporates
• Corporate Access Web Service
• Enhanced PEPPOL.

Use of Secure Envelope is mandatory for the protocols AS2, SFTP, Corporate Access Web Service and Enhanced PEPPOL, and optional for SWIFTNet for Corporates and manual upload. 

Secure Envelope is our solution for protecting the content of files sent via our file transfer service, Corporate Access File Transfer. The files and their content are enveloped and digitally signed according to an open standard. 

Schema for Secure Envelope

Here, you can find the schema for Secure Envelope.

• Secure Envelope specification
• Application request  
• Application response   

Example certificate

If you want to create a Secure Envelope before you receive a production certificate, you can use the values and certificate below. 

SignerID: 5780860238

PIN = WSNDEA1234

• Demo certificate 

Web services protocol

• WSDL file (zip, 1 KB) 

Test files – Secure Envelope

• Encoded – Corporate Access payment test file (encoded) (txt, 3 KB)
• Enveloped – encoded – Corporate Access payment test file (enveloped) (zip, 1 KB)
• Signed – enveloped – encoded – Corporate Access payment test file (signed and enveloped) (zip, 3 KB) 

You can retrieve your digital certificate from us using either your bank connection software or the Nordea Security Client (NSC). For more information, see the documents below. 

1. Download of Nordea Security Client 
2. Step-by-step guide – download certificate using Nordea Security Client
3. Nordea Security Client – user guide
4. How to export a certificate to a PSKC #12 file (pdf, 660 KB) 

Do you need to renew a certificate? If you need further guidance, you can find a video with instructions here.

The documents below provide insights regarding each local payment market and its infrastructure. They also contain detailed information on how local markets are integrated into the service, for example information on payment types and cut-off times.

• Corporate Access Payables appendix Denmark
• Corporate Access Payables appendix Finland
• Corporate Access Payables appendix Norway
• Corporate Access Payables appendix Sweden 

The message implementation guides below define how information in messages should be structured for exchanges between the message sender and Nordea. 

See the information below if you are implementing the service.

New Corporate Access test tool
We have partnered with the Finnish vendor XMLdation to offer a new and improved test tool for validating different ISO 20022 messages/scenarios for Corporate Access. 

With the new tool, you can test your payment files, receive simulated feedback files and test Secure Envelope. 

The tool will be continually updated with the introduction of new standards such as ISO20022 Version 2019 and Pretty Good Privacy (PGP).

Register as a user:
To get full access to the test tool, sign up via XMLdation’s registration page below and use the registration code to request an email with your personal login credentials.

• XMLdation registration page
• Registration code: 27032617
• XMLdation login page 

Once logged in, you can access the tool’s user guide for instructions. For additional support, see Corporate Access above.

Previous Corporate Access test tool 
The previous test tool for Corporate Access was discontinued in 2025.

Standard ISO 20022 XML schemas
Our Corporate Access service follows the standard ISO 20022 XML schemas for all files. The standard XML schemas can be found at www.iso20022.org.

• Message archive for pain.001 and pain.002  
• Message archive for camt.052, camt.053 and camt.054  
• Message archive for camt.055 and camt.029   

Example document
The document below provides examples per available payment type in Corporate Access (pain001.001.03 – Denmark, Finland, Norway, Sweden and international).

• Pain.001 v3 examples Denmark, Finland, Norway, Sweden (pdf, 521 KB)

Corporate Access Payables test files

Payment Instruction pain001.001.03

• Corporate Access payment test file, pain.001 (PG1) (zip, 0 KB)

Note: a Secure Envelope is a prerequisite for files sent via host-to-host communication, except for SWIFTnet FileAct.
 

Pain002 File Status file
On receipt of a pain.001, our system responds with a file status report message.

• File reception status file, pain.002 (zip, 0 KB) 

Pain002 Status Report file
As an optional service, we can provide a secondary file, reporting on the payment status.

•  Pain.002 v3 status report examples (pdf, 512 KB) 

Camt054 Debit Notification file
To enable you to automatically reconcile your payments, we offer a debit notification report file.

• Camt.054 v2 debit notification report examples Sweden (pdf, 486 KB)

For more detailed information on file types and processes, see Corporate Access Payables appendix user guide & message flow.

The documents below define how information should be structured for file exchanges.

See the information below if you are implementing the service. 

Standard ISO 20022 XML schemas
Our Corporate Access service follows the standard ISO 20022 XML schemas for all files. The standard XML schemas can be found at www.iso20022.org.

• Message Archive for camt.052, camt.053 and camt.054 

Example file Corporate Access Account Reporting
The Corporate Access Account Reporting service currently offers you the following XML messages:

• Bank to Customer Statement (camt.053.001.02) (standard)
• Bank to Customer Credit Notification (camt.054.001.02)
• Bank to Customer Statement (camt.053.001.02) (extended).

Below, you will find Corporate Access Account Reporting example files for each country.

The information above is based on input from the vendors themselves. We have not verified the information and therefore cannot take any responsibility for its accuracy. In any case, we recommend that you approach your ERP/TMS vendor or IT consultancy firm to discuss what is required for integration with Corporate Access. 

All vendors who have tested and implemented a solution for integrating with Corporate Access and wish to be listed above can use this web form. 

Everyone you intend to use as an approver in the payment files must be registered in Nordea Corporate. You can do this by upgrading an existing Corporate Netbank / Nordea Business user or registering a new person as an approver. 

• Information on the administrative process (English)
• Information on the administrative process (Norwegian)

All pre-confirmed payment files must be updated according to the new message implementation guide. They must contain information on who, at your request, has approved the payments.

• Information on the technical process (English)
• Information on the technical process (Norwegian)

If you use a third-party vendor to create your payment files, there is a high probability that the vendor already has a solution for this in place. We recommend that you involve your ERP vendor early in the process.

It is important that the approvers registered in Nordea Corporate match the approvers registered in the payment files.

• Guide for registration of approvers in Nordea Corporate (English)
• Guide for registration of approvers in Nordea Corporate (Norwegian)

Important information: we have made it mandatory for customers to include approvers in payment files. Payment files for Norwegian accounts received without the correct information will be rejected.