Testing

Before starting to lodge declarations via message exchange, the company must test the functionality of its software with Customs and that the messages the software produces conform to Customs’ specifications. At the same time, the data communication links are also tested.

During the testing, the company submits declaration messages with varying data content (for example complete or amended declarations or additional information), to which Customs then responds with messages (acceptance, error, request for additional information, etc.). The company must respond to the reply messages as required, for example by correcting errors or sending additional information.

The testing consists of two or three parts, depending on the procedure.

System Parts of the test
Safety and Security data system AREX
Import system ITU
Transit system NCTS

Technical testing
Parallel testing

Export system ELEX

Independent testing
Technical testing

Parallel testing or
Testing using the company’s own material

Statistics system Intrastat

Technical testing using the company’s own material

Guidance for testing

Testing instructions for summary declaration system AREX

For the company to be accepted as an EDI sender, it must pass the testing of message exchange and customs competence. When the company’s application has been processed, Customs will contact the company to arrange a consultation and to set the dates for the testing. The company will build its own AREX summary declaration system independently based on Customs’ message implementing guidelines.

The testing for EDI senders consists of two phases: technical and parallel testing. In the technical testing, the company uses test material provided by Customs. The aim of the technical testing is to ensure the functioning of the message exchange between Customs and the company and to test the correctness of the message structure. In parallel testing, the company’s own material will be used.  The aim of the parallel testing is to ensure that the company has sufficient competence for providing summary declarations. Therefore, all the persons who will be completing summary declarations for the company should participate in the parallel testing.   

The company is to reserve an uninterrupted work period of three to five weeks for the technical and parallel testing. The duration of the testing depends on the number of messages to be submitted and the modes of transport used by the company. After successfully completing the testing phases, the company will be granted an EDI sender authorisation and can enter the production phase of message exchange. If the time reserved for testing is exceeded, the testing will be stopped and the company must schedule a new time for the testing. This may mean postponing the final testing by several months.

Testing instructions for export system ELEX

For the company to be accepted as an EDI sender, it must pass the testing of message exchange and customs competence. When the company’s application has been processed, Customs will contact the company to arrange a consultation, if needed, and to set the dates for the testing. The company is to build its own export declaration system independently based on Customs’ message implementing guidelines. 

The testing for EDI senders consists of three phases: independent testing, technical testing and parallel testing. In the independent testing, the company uses test material provided by Customs and tests the functioning of the message exchange. The aim of the technical testing is to ensure the functioning of the message exchange between Customs and the company and to test the correctness of the message structure using the test material provided by Customs. In the parallel testing, the company’s own export material will be used, that is, old export declarations submitted by the applicant in paper format as well as other related documents.  The aim of the parallel testing is to ensure that the company has sufficient competence for providing export declarations. Therefore, all employees of the company who complete export declarations (export secretaries, traffic coordinators, etc.) should participate in the parallel testing.   

The company is to reserve an uninterrupted work period of three weeks for the technical and parallel testing. The independent testing is undertaken on a voluntary basis and takes a maximum of two weeks.  After successfully completing the testing phases, the company will be granted an EDI sender authorisation and can enter the production phase of message exchange. If the time reserved for testing is exceeded, the testing will be stopped and the company must schedule a new time for the testing. This may mean that the final completion of the testing will be postponed by several months.

Independent testing

Companies can familiarise themselves with the content of export declaration messages in XML format with the help of the first four test cases. Companies can enquire about opportunities for independent testing where they can test the message exchange and sending messages over a set period with the help of the first test cases provided. More specific details on the testing are provided in the EDI export customer guide.  

The table below first lists the test case on a SAD form (e.g. Testi1.pdf), followed by the same case converted into XML format (e.g. Testi1-XML.xml). In the actual testing, the Customs testing official will provide the test cases on a SAD form to the company, who will then create the necessary XML messages based on the forms.

Testing instructions for EMCS

Testing instructions for the transit system

Testing instructions for the statistics system Intrastat

Testing instructions for the import system ITU

                            

Contact us
Customs Information Service, Business customers
Monday to Friday 8 am–4 pm

Contact Customs Information

The cost of a call from a landline or mobile phone subscription is 0 cents/min + local network charge/ standard mobile rate.


Keywords

Help us improve our site content

We want to improve our service, which is why your feedback is valuable to us. If you have ideas on how our web services could be developed further or if you wish to give us feedback, please let us know.

Send feedback