Testing

By introducing the e-invoice you can offer your customers a new invoicing method.

Ask your software supplier for help when you start using or update new software.

The following sample messages are available for testing the software.

• New invoicer notification (zip, 1 KB)Opens new window
• Modification of invoicer notification (zip, 1 KB)Opens new window
• Reception notification (zip, 1 KB)Opens new window

You can use the Finvoice testing tool, offered by Nordea, for checking the format and, to some extent, logical correctness of the structure of the messages formed by your software.

The tool is easy to use, and you get a reply right away. No data on the message is stored in Nordea's systems. 

You can use Nordea's XML testing tool for checking the formal and, to some extent, logical correctness of the structure of the messages formed by your software.

The tool is easy to use, and you get a reply right away. No data on the message is stored in Nordea's systems. The tool uses the Java Web Start application, so you will need at least version 1.5 of the Java Runtime module.

Logical checks

The logical checks of a message are made in accordance with the processing rules that are used in the reception of the message in file transfer and in forming payments for the payment-processing systems.

However, the checks in the testing tools do not always fully conform with production, so using the testing tool does not guarantee that the file suits production in all situations.

The correctness of customer agreements, such as the service ID or accounts, cannot be checked, and dates cannot be compared with the calendar used by the payment application.

Use of the testing tool

This tool is intended for verifying the formal and structural correctness of a message. Its use is free and it does not include user guidance or support.

Before you start using the new feature of your software, the files formed in your system must be sent to the testing services of Nordea's file transfer. See the instructions on the XML testing tab.

Check the message

• Select the type of the payment to be tested from the dropdown menu.
  
• Select the XML file to be checked from your own files with the Browse button.
  
• You will get the result of the check on your screen by pressing the Validate button.

The summary of the check results shows the number of XML errors under XML errors and the number of errors based on the processing rules under Business rule errors.

You can view the file either as a text file or as a tree structure. When you click the error, you will be taken to the faulty element.

The new payment messages in the XML format based on the ISO 20022 standard should be applied to payment of invoices and salaries, as the national payment practices have been waived in Finland. Ask your software supplier for help when you start using or update new software.

• Agree with your software supplier on updating your systems so that they can form pain.001 payment messages in accordance with the ISO20022 XML standard and forward them with the Web Services protocol.
  
• Ensure that the message format is correct either with the tools provided by your software supplier or by using the schema below and a suitable validation tool.
  
• The correctness of the content can be checked by comparing the files with the model message below. Further information is also available in the Corporate Payments Service description and its example appendix.
  
• When forming testing material, you must take the contents in the Environment field of the ApplicationRequest message into account depending on the testing methods, which are described below.

Once you have successfully performed the afore-mentioned phases, you can start sending files to production.

Technical documentation

Web Services Security and Communication Description (pdf, 878 KB)Opens new window

1. With the test certificate and Nordea’s general test IDs:

• Download the Web Services test certificate on the Instructions page.
  
• Type the word PRODUCTION in the Environment field of the ApplicationRequest message.
  
• The payment files are not checked.
  
• You do not get transmission feedback in the test but you can separately retrieve the general model feedback pain.002 complying with the XML standard.
  

OR

2. With your own certificate, service IDs and accounts:

• Type the word TEST in the Environment field of the ApplicationRequest message.
  
• At reception the software checks the following: the files are in the correct format and certain parts of their content are in order, the IDs are as agreed and the customer’s payment agreement is valid.
  
• The test produces authentic transmission feedback reporting the result of the test. Payments are not entered into accounts and no account statement is formed.
  
• NB. If the value in the Environment field is not TEST, the files will be paid.
  
• The customer and the bank have agreed that the Corporate Payments Service agreement is given a test status:
  
• The value in the Environment field must be PRODUCTION.
  
• At reception the software checks the following: the files are in the correct format and certain parts of their content are in order, the IDs are as agreed and the customer’s payment agreement is valid.
  
• The test produces authentic transmission feedback reporting the result of the test. Payments are not entered into accounts and no account statement is formed.