If your software lodges export or transit declarations in the EU, it has to speak two message sets: AES for export and NCTS phase 5 messages for transit. Most public documentation treats them separately, in long specifications and national PDFs. This article puts them side by side, as a developer at a customs broker or forwarder sees them: which message your system sends, which answers come back, and where the two systems meet.

It describes the public EU specifications. National connections have their own rules for access, certificates, and software approval, so check the documentation of the customs administration you connect to.

Two systems, one integration

The Automated Export System (AES) is the EU-wide system for export and exit formalities required by the Union Customs Code. The European Commission describes it as an evolution of the earlier Export Control System (ECS). The New Computerised Transit System (NCTS) handles transit: goods that move under customs supervision from an office of departure to an office of destination.

For a broker, the two often belong to one shipment. Goods are declared for export, and then placed under transit to reach the point where they leave the EU. The Commission notes that AES connects to NCTS when export is followed by transit, so that export movements do not stay open. Your integration benefits from the same view: one shipment, two movements, each with its own reference number and its own life cycle.

Both systems use the same pattern. The trader sends a declaration with its own Local Reference Number (LRN). Customs validates it, then either rejects it or allocates a Movement Reference Number (MRN). After that come amendments, controls, release, and the end of the movement, each as a separate message. The messages are identified by codes such as IE515 or IE015.

Export under AES: from IE515 to the exit

Irish Revenue publishes a list of AES message types for traders that is a good public reference for the export side.

DirectionMessageMeaning
SentIE515Export declaration
SentIE513Export declaration amendment
ReceivedIE528Export MRN allocated
ReceivedIE556Rejection from office of export
ReceivedIE504Amendment acceptance
ReceivedIE560Export control decision notification
ReceivedIE529Release for export
ReceivedIE551Export no release
ReceivedIE509Export invalidation decision
ReceivedIE599Export notification

A typical happy path is short: your system sends IE515, receives IE528 with the MRN, and later receives IE529 when the goods are released for export. Every other message is a branch from that path. An IE556 means the declaration was rejected and needs to be corrected and sent again. An IE560 tells you customs has decided on a control. An IE551 means the goods are not released.

The point for software design is that these answers arrive asynchronously, sometimes hours apart. A declaration is not a request with one response. It is a movement with a state, and every incoming message moves that state forward.

NCTS phase 5 messages: from IE015 to release

The transit side follows the same shape with different codes. Again, Irish Revenue's list of NCTS P5 message types is a clear public source.

DirectionMessageMeaning
SentIE015Declaration data
SentIE013Declaration amendment
SentIE014Declaration invalidation request
SentIE007Arrival notification
ReceivedIE928Positive acknowledge
ReceivedIE028MRN allocated
ReceivedIE056Rejection from office of departure
ReceivedIE004Amendment acceptance
ReceivedIE060Control decision notification
ReceivedIE029Release for transit
ReceivedIE051No release for transit
ReceivedIE009Invalidation decision
ReceivedIE025Goods release notification
ReceivedIE045Write-off notification

At departure, your system sends IE015 and receives IE928 to confirm receipt, then IE028 with the MRN, and IE029 when the goods are released for transit. At destination, the arrival is notified with IE007. IE025 reports the release of the goods at destination, and IE045 the write-off of the movement.

The same list includes guarantee messages, unloading remarks, and technical acknowledgements such as IE906 (functional NACK) and IE917 (XML NACK). Not every integration needs all of them at first, but your message handling should recognise them and route an unknown message to a person rather than drop it.

What changed with NCTS phase 5

The European Commission set 2 December 2024 as the legal deadline for deploying NCTS phase 5, and reported 29 countries live by 20 December 2024. The transitional period from phase 4 ended on 21 January 2025.

According to a summary by the customs software vendor AEB, phase 5 came in two stages:

  • Transition. A new data hierarchy (declaration, consignment, house consignment, goods item), new data groups such as Authorisation and Location of goods, amendment of departure declarations, and up to 1,999 goods items per declaration.
  • Final state, from 22 January 2025. Multiple house consignments, mandatory 6-digit commodity codes, the MRN as the reference that identifies each movement (depending on national rules, the paper transit accompanying document (TAD) can be replaced or reduced), and a role for the office of incident.

For developers, the hierarchy is the biggest change. A declaration is no longer a flat list of items. Your data model needs consignments and house consignments as first-class objects, and your mapping from the broker's shipment data has to produce them.

The AES side has its own timeline. The Commission set deadlines for national administrations of 1 December 2023 for core functions, 13 February 2024 for the interface with EMCS, and 2 December 2024 for new functions, including centralised clearance, the NCTS interface, and pre-lodged declarations. By that last date, "all National Customs Administrations and EOs shall be ready to operate in AES".

National names: AES-RO, NCTS5-RO, ATLAS

The EU defines the messages. Each member state runs its own national system and decides how traders connect to it.

Romania. AES-RO replaced ECS-RO for export declarations from 16 March 2024, and export declarations are no longer printed (Euronews Romania). NCTS5-RO started on 17 May 2024 (SGS eCustoms). KPMG Romania notes that qualified digital certificates are required.

Germany. Export declarations are made in ATLAS (ATLAS-Ausfuhr), through customs software, the free IAA Plus, or an agent. The IHK Lahn-Dill notes that the transition to AES 3.0 ended on 30 November 2023, and that the LRN replaces the former Bezugsnummer. Anyone offering software for ATLAS or AES in Germany must have it certified by the customs administration. The process typically takes several months, and the official page states that pure XML message exchange alone does not lead to a certificate.

Warning

Access, certificates, and software approval are national matters and they change. Before you plan an integration, read the current documentation of the customs administration you will connect to.

What to build first in an integration

The message lists look long, but the order of work is predictable.

  1. A movement model with states. Store each export and each transit as a movement with its LRN, its MRN once allocated, and its current state. Every incoming message is an event that changes that state. Keep all messages, sent and received, linked to the movement.
  2. The happy path for one direction. For export: IE515, IE528, IE529. For transit: IE015, IE928, IE028, IE029. Get these right end to end, including XML validation against the published schemas, before adding branches.
  3. Rejections next. IE556 and IE056 are the messages users meet most often in early testing. Show the reason from the message to the person who has to fix the declaration, in their own screen.
  4. Amendments and invalidation. IE513 and IE013 with their acceptance messages, and invalidation. These touch an existing movement, so they test whether your state model holds.
  5. The link between export and transit. When a transit follows an export, keep the export MRN on the transit movement, so that the broker's team sees one shipment instead of two unrelated records.
  6. Controls and the end of the movement. IE560 and IE060, IE599, IE025, and IE045. These close the loop and are what the broker reports on.

A clear status per movement is the feature users notice. They want to know, without reading XML, whether a declaration is waiting, rejected, released, or closed.

How we can help

We build customs API integration for AES and NCTS: sending declarations from the broker's software, bringing customs responses back into it, and showing the status of each movement. The national connection and its certification stay with the party that holds them under the national rules.