Scam messages have been sent out in the Tax Administration’s name. Read more about scams.

EMCS interfaces available in the Vero API service

EMCS, or the Excise Movement and Control System is an electronic system for exchanging information between EU countries. EMCS is used for reporting and controlling movement of products subject to harmonised excise duty (alcohol, alcoholic beverages, tobacco and liquid energy products). Customers have to report movements of products either in MyTax or via the API. It is still not required to use EMCS when moving products within Finland.

Overview of changes and updates in EMCS interfaces

Please note: Due to legislative changes in the Netherlands, between 1 January and 13 February 2024 a DegreePlato entry cannot be made for a beer product (B0000) if the Member State of destination is the Netherlands (NL).


The following changes to EMCS APIs are implemented as of 13 February 2024:

  • IE801 Get e-AD/e-SAD and
  • IE815 Submit draft e-AD/e-SAD
    • Consignee’s name and address details (ConsigneeTrader) are required if the Member State of entry for the export procedure is Finland (DestinationType = 6).
    • DegreePlato can be given as optional information for a beer product (B000), even if the Member State of destination does not require it.
    • New field for entering small-scale producer information (IndependentSmallProducersDeclaration). This affects the requirements of the existing DesignationOfOrigin and SizeOfProducer fields. See parameter descriptions.
  • IE813 Submit Change of Destination
    • Consignee’s name and address details (ConsigneeTrader) are required if the Member State of entry for the export procedure is Finland (DestinationType = 6).
  • IE801 Get e-AD/e-SAD
    • New field for entering small-scale producer information (IndependentSmallProducersDeclaration).

New messages on exports:

  • IE829–v2 Get Notification of Accepted Export:
    • IE829 API’s new version (version 2) is released 13 February 2024.
    • IE829 API’s version 1 cannot be used from 13 February 2024 onwards.
    • When information on an e-AD has been retrieved via the IE829–v2 API, the status of the e-AD should be changed to Accepted Export Declaration (when ExportDeclarationAcceptanceOrGoodsReleasedForExport = 0).
    • When information on the same e-AD has been retrieved via the IE829–v2 API for the second time, the status of the e-AD should be changed to Exporting (when ExportDeclarationAcceptanceOrGoodsReleasedForExport = 1).
  • IE836 Get Export Declaration Invalidation Notification to MSA of Dispatch
    • New message type added. This message contains information on the invalidation of the export declaration. After retrieving information on an e-AD via the IE836 API, the status of the e-AD should be changed to Accepted and either a new Export Declaration (in the Customs system), Cancellation (IE810) or ChangeOfDestination (IE813) should be submitted.
  • IE839 Get Rejection of e-AD for Export
    • New message type added. This message contains information on export non-release. After retrieving information on an e-AD via the IE839 API, the status of the e-AD should be changed to Accepted and either a new Export Declaration (in the Customs system), Cancellation (IE810) or ChangeOfDestination (IE813) should be submitted.
  • Note: When you get a notification about an IE829–v2, IE836 or IE839 type of message, it is recommended to call each of the IE829–v2, IE836 and IE839 Get APIs with the URI value that is included in the notification. Then sort all the received messages from these APIs by date and time, and update the e-AD statuses according to the instructions above to determine the history and the current status of the e-AD. Use the following parameters for sorting the messages:
    • IE829–v2: DateAndTimeOfIssuance
    • IE836: ReturnReceivedDate
    • IE839: DateAndTimeOfIssuance

Message descriptions in the sandbox: APIs: Details - Vero API Sandbox - developer portal

The new APIs for the EMCS and updates to existing APIs are released in the Vero API portal and sandbox. There you can check the updated fields and schemas as well as any other changes.

Direct message exchange in JSON format

The customer interface of EMCS is in the Tax Administration’s API service.

The APIs are real-time Rest APIs where the message format is JSON.

EMCS messages and information content requirements are based on the EU Commission’s EMCS specifications. Vero APIs are in the JSON format.

See the EU Commission’s website for more information about the EMCS and its specifications.

Go live notes

Users must get certificates for the production environment before API interfaces can be used. They also need to register their software product that uses EMCS interfaces, and build the API key processing into the software. If any new EMCS interfaces are introduced, you should select them in the API portal and run the necessary tests there before you can start using them.

See more details about going live with Vero API services.

Description of APIs

Message descriptions are in the Vero API sandbox and Vero API Portal. The test versions of the APIs in the sandbox do not contain validation of check rules related to message content. Test versions containing validations are available through test endpoints published in the Vero API Portal.

Notification service

Also available is a Notification Service API where the interface user is notified of any EMCS messages received. Notifications come from a request interface, and each notification contains a key. Using the key, the user can retrieve the actual information content associated with EMCS.

Requests for notifications through the request interface

Users need to request notifications from the Tax Administration’s interface because in the first phase, the service sends notifications only in response to requests.  Automated functionality will be available in February 2024 in the form of a ”push notification” solution. After that, users will receive the notifications automatically.

The descriptions of the Notification Service API are released in the Vero API sandbox.

API code sets

You can retrieve the code sets used in EMCS APIs through the API code set interface. You can explore the code set interface in the Vero API sandbox environment. The API codes are found in the category: General > Codes.

The codes are available in the sandbox and in the Vero API portal: Code sets – API-portal (vero.fi)

API key

Software houses and developers must register their API software in the Tax Administration's API portal. The API key, which is specific for every software product, is required in the EMCS in addition to the user’s certificate. In interface calls, the API kay needs to be places in the vero-softwarekey header.

Further information:

Page last updated 2/2/2024