On February 12, 2026, Customs (in all member states) will roll out EMCS Phase 4.2, in line with the European Commission's schedule. This upgrade applies to all member states that use the Excise Movement and Control System (EMCS).
Although EMCS Phase 4.2 does not introduce any new business functionalities, the release does entail mandatory technical and validation adjustments that economic operators must comply with from the go-live date.
EMCS (Excise Movement and Control System) is the European electronic system for monitoring and tracking the movement of excise goods under excise duty suspension within the European Union.
EMCS is used to exchange electronic administrative documents (e-AD and e-VAD) between economic operators and the customs authorities of the Member States. The system provides:
EMCS is mandatory for operators who dispatch, receive, or transport excise goods under excise duty suspension.
From February 12, 2026, all EMCS messages exchanged with customs must comply with the specifications of Phase 4.2. Message formats from previous phases (such as Phase 4.1) will no longer be accepted. This is particularly relevant for operators working with B2B or system-to-system integrations.
The most important changes are:
Custom message specifications
The EMCS message structures are harmonized at European level in order to eliminate inconsistencies and incompleteness in data exchange, including in the interface between EMCS and AES (Automated Export System).
Stricter validation rules
Additional checks will be introduced, particularly for temporary registered, certified, or authorized operators:
Validation in case of delayed submission
When the date and time of transmission are in the past, the indication for deferred submission must be explicitly marked, which ensures more consistent data exchange.
For customers working with Stream Software, the changes under EMCS Phase 4.2 will be incorporated into the application. The necessary technical adjustments and validations will be implemented to ensure:
EMCS is provided as standard within our application as a basic functionality.