IE529 vs IE599 — Key Differences in EU Export Messages

EU export procedures generate a series of electronic messages as goods move from the customs office of export to the customs office of exit and out of EU territory. Two of the most important — and most frequently confused — are IE529 (Advance Notification of Exit) and IE599 (Confirmation of Exit). Only one of them constitutes proof of export for VAT purposes. Understanding the difference is critical for every exporter.

The Export Message Flow

Before examining each message individually, it helps to understand where they fit in the overall export procedure under the EU's AES (Automated Export System), as defined by Regulation (EU) No 952/2013 (Union Customs Code) and its implementing provisions.

1. Export declaration filed — the exporter (or customs agent) files the electronic export declaration. The system assigns an MRN and sends IE528 (MRN Allocated) to the declarant.
2. Goods arrive at exit point — when goods reach the customs office of exit (typically the sea port), the office generates IE529 — an advance notification that goods are present and expected to leave.
3. Physical departure confirmed — after the vessel sails and the port system confirms loading, the customs office of exit sends IE518 (Results of Exit Control) to the customs office of export.
4. Export procedure closed — the customs office of export generates IE599 (or CC599C in the new AES PLUS system) and sends it to the declarant. This completes the export procedure.

IE529 — Advance Notification of Exit

IE529 (formally: “Release for Exit”) is generated by the customs office of exit when export goods are presented and accepted for exit from the EU. It signals that:

• The goods covered by the MRN have arrived at the customs office of exit.
• The export declaration data has been checked against the physical consignment.
• The goods are cleared for exit — they may leave EU territory.

Crucially, IE529 does not confirm that the goods have actually left. It is a forward-looking notification: “these goods are expected to depart.” The container may still be sitting at the terminal when IE529 is issued.

In practice, many exporters receive IE529 through their customs system and mistakenly believe the export procedure is complete. It is not. IE529 is a necessary intermediate step, but it is not the finish line.

IE599 / CC599C — Confirmation of Exit

IE599 (or CC599C in the new AES PLUS system) is generated by the customs office of export after it receives confirmation (via IE518) from the customs office of exit that the goods have physically departed EU territory. This message confirms:

• The goods have actually left the EU.
• The export procedure is formally completed.
• The exporter has fulfilled their customs obligations for this shipment.

IE599/CC599C is the primary and definitive proof of export recognized by tax authorities across all EU member states. Without it, the exporter cannot apply the 0% VAT rate on the export transaction.

IE529 vs IE599 — Side-by-Side Comparison

VAT Implications — Why the Distinction Matters

The distinction between IE529 and IE599 is not merely technical — it has direct financial consequences. Under EU VAT rules (Directive 2006/112/EC, Art. 146) and national implementing legislation (e.g., Art. 41 of the Polish VAT Act), the 0% VAT rate on exports requires proof that goods have left EU territory.

IE599/CC599C provides this proof. IE529 does not. An exporter who relies on IE529 alone and applies 0% VAT is at serious risk during a tax audit. The tax authority will demand IE599/CC599C, and if it cannot be produced, the transaction will be reassessed at the domestic rate — 23% in Poland, 19% in Germany, 21% in the Netherlands.

Received IE529 but Not IE599 — What to Do

If you received IE529 but IE599/CC599C has not followed within 5–7 business days after vessel departure, something has gone wrong in the closure chain. The export procedure was initiated (goods were presented at the exit point) but not completed (departure was not confirmed). Common causes include:

• Missing port system registration — the export was not registered in the port community system, preventing automatic matching with the vessel manifest.
• Data mismatch — container number, weight, or goods description does not match between the declaration and the manifest.
• Vessel change — the container was loaded onto a different vessel than declared.
• Carrier manifest delay — the shipping line has not yet transmitted the vessel manifest to the port system.

In all these cases, specialist intervention is needed to identify the specific cause and resolve it within the port system. The longer you wait, the more complex the resolution becomes — and after 150 days, the MRN is subject to invalidation.

For more details on each cause and resolution, see our article on 7 common reasons for open MRN.

FAQ — IE529 vs IE599

Legal basis: Art. 269-274 of Regulation (EU) No 952/2013 (Union Customs Code); Art. 329-336 of Commission Implementing Regulation (EU) 2015/2447; Art. 146(1)(a) of Directive 2006/112/EC (VAT Directive). This article is for informational purposes and does not constitute legal or tax advice. Updated: March 2026.