AES errors. Find the cause. Resolve the issue.
Export declaration rejected? MRN not found? Customs response missing? Goods released but exit still unconfirmed? Identify the failure point before taking corrective action.
A practical diagnostic guide to the EU Automated Export System, covering declaration validation, electronic messages, customs decisions, export tracking and exit enquiries.
Start with the actual customs status. A technical transmission failure, a customs rejection and a missing exit confirmation are not interchangeable problems.
Check the last confirmed event. Do not assume the next event occurred.
UCC Regulation (EU) No 952/2013; Implementing Regulation (EU) 2015/2447, including Articles 334–335 on exit certification and enquiry procedures.
Declaration rejected? Identify the failure layer first.
A declaration that cannot be processed is not always a customs rejection. The problem may arise before delivery, during technical validation, during customs acceptance checks or after the declaration has already been accepted. Each situation requires a different response.
Where did the declaration stop?
Message identifiers are drawn from the European Commission’s AES Business Guidance. Actual acknowledgements, technical error formats and connectivity depend on the national interface and its specifications.
Similar symptoms. Different remedies.
Transmission failure
The operator’s system cannot confirm that the declaration reached the intended customs endpoint. A timeout does not prove that customs received nothing.
First verification- Inspect transport logs and message identifiers.
- Check gateway and customs service status.
- Reconcile the submission before attempting a retry.
Schema or format error
The message does not meet an applicable technical specification. The problem may concern a field format, message structure, code or data dependency.
First verification- Read the exact technical error returned.
- Check the current national message specification.
- Correct the payload and follow the prescribed process.
Declaration not accepted
Customs returns a rejection, typically IE556 in the relevant AES export-declaration flow. The response must be examined to establish why acceptance was refused.
First verification- Identify the rejection reason and affected data.
- Check EORI, procedure, codes and applicable rules.
- Prepare a corrected submission where appropriate.
Accepted declaration needs correction
An accepted declaration is not treated like a rejected draft. Amendments and invalidation are subject to legal conditions and the applicable customs procedure.
First verification- Confirm the MRN and current customs status.
- Assess UCC Articles 173 and 174.
- Use the permitted amendment or invalidation route.
Read the error before changing the declaration.
Error messages should be analysed in context. A field identifier may indicate where validation failed, but it does not always explain the underlying business-rule dependency.
Preserve the submitted payload, the exact response, the timestamp and the correlation identifier before making a correction.
What should be checked in the declaration data?
These categories are diagnostic examples, not an exhaustive list of AES rejection codes.
Operator identification
EORI, declarant, representative and applicable authorisation references.
Procedure and codes
Requested procedure, previous procedure and relevant code-list values.
Goods information
Commodity classification, descriptions, quantities and required units.
Supporting references
Documents, certificates and references required for the declared scenario.
Transport and routing
Applicable transport details, offices, locations and conditional fields.
Cross-field consistency
Relationships between data elements, conditions and business rules.
Choose the action that matches the confirmed status.
| Confirmed situation | Recommended next step | Avoid |
|---|---|---|
| Transport status unknown | Reconcile gateway, response and submission records. | Immediate duplicate transmission. |
| Technical validation failed | Correct the payload against the applicable specification. | Changing unrelated customs data. |
| IE556 rejection received | Review rejection reasons and submit corrected data as appropriate. | Treating the rejected declaration as accepted. |
| IE528 acceptance received | Check MRN, customs status and permitted amendment procedures. | Replacing the declaration with an uncontrolled new one. |
| Release not confirmed | Verify pending controls and customs decisions. | Equating acceptance with release. |
Correction is not the same as amendment.
Under UCC Article 173, amendment of an accepted declaration is subject to conditions. In particular, the ordinary amendment route is restricted after customs announces an examination, establishes incorrect particulars or releases the goods. Article 173(3) separately provides for certain post-release amendments on application within three years of acceptance.
Invalidation under Article 174 is a separate legal mechanism and is not a general-purpose substitute for correcting an export declaration.
Regulation (EU) No 952/2013, Articles 172–174; Commission AES Business Guidance, export declaration processing and messages IE515, IE528 and IE556. National technical documentation must be consulted for specific validation codes and message formats.
Missing AES messages. Trace the exchange, not the assumption.
An expected customs response may be delayed, rejected by a technical interface, delivered to another software component or received without being displayed to the operator. The first task is to establish which event can actually be confirmed.
Four points where visibility can be lost.
Five symptoms. Five different investigations.
Identify the symptom first. Do not infer the customs outcome solely from the message displayed by the local application.
No response after submission
The connection times out before the operator receives a conclusive result. The customs system may or may not have processed the original request.
Message rejected by the interface
A syntax, envelope, authentication or transport-related issue prevents the intended message from being processed as expected.
Response cannot be matched
The response reaches the integration layer, but the software cannot reliably associate it with the originating declaration or request.
Same request submitted twice
A retry, user action or integration failure may produce repeated submissions. The effect depends on the receiving system and its validation rules.
Customs status and software status disagree
The national customs environment shows an updated movement status, while the trader’s application still displays an earlier stage. This may be caused by failed import, mapping, queue processing or local status-update logic.
One declaration. Three different records.
A useful investigation compares what the operator submitted, what the interface recorded and what the customs administration actually confirmed.
If an IE528 acceptance response is not visible, do not assume either acceptance or rejection. Reconcile the official record before deciding what to do next.
IE515 created and handed to the integration component.
Delivery status requires verification against the national interface.
No acceptance or rejection response is visible in the local application.
Reconcile the submission through available official channels before retrying.
Six checks before you retry a message.
Identify the original submission
Record local reference, message identifier, sender and timestamp.
Inspect the outbound transport record
Check whether the request left the application and reached the interface.
Check inbound technical responses
Look for transport acknowledgements, technical errors and queued responses.
Reconcile the customs record
Use available national status services, portal records or customs support channels.
Determine the permitted corrective action
Retry, correct, request support or await processing according to the confirmed status.
Close the incident with evidence
Retain logs, responses, decisions and the final reconciliation outcome.
A technical outage does not automatically authorise an offline export procedure.
The European Commission’s AES Business Continuity Plan addresses common-domain fallback and provides recommendations concerning external-domain communication. Procedures between traders and customs authorities are determined by the relevant national administration. Follow the official national contingency instructions and any applicable conditions before proceeding.
European Commission AES Business Guidance; European Commission AES system overview and Business Continuity Plan; national customs message specifications and trader integration guides. The six-step reconciliation procedure is an operational recommendation, not a mandatory EU-prescribed sequence.
MRN not found? Release still pending?
A valid movement reference does not automatically establish that goods have been released, presented at exit or certified as having left the customs territory of the Union. Troubleshooting begins by identifying the last confirmed customs event and the system responsible for it.
One MRN. Several legally distinct events.
Submission initiated; delivery and validation still require confirmation.
IE515
Customs acceptance confirmed. The declaration has a movement reference.
IE528
The relevant customs release decision has been communicated.
IE529
Goods are handled under the applicable office-of-exit formalities.
EXIT EVENTS
Customs confirms the exit outcome in accordance with the applicable rules.
EXIT RESULT
This diagram is a simplified diagnostic sequence, not a complete AES state machine. Controls, amendments, alternative procedures and other events may affect the actual processing. A message must be interpreted together with its contents and the relevant customs status.
The MRN exists. Why can’t you find it?
An unsuccessful search may indicate a reference error, an incorrect national environment, limited portal visibility or an unresolved integration problem. It does not, by itself, invalidate the declaration.
Do you have a confirmed customs acceptance response containing the MRN, or only a reference generated by your own software?
Locate the customs acceptance response and its assigned MRN.
Review transcription, characters and possible reference confusion.
Distinguish an export MRN from a transit MRN and other references.
Check the national portal, trader role and available visibility.
Use official national enquiry or support channels when necessary.
Not every shipment reference is an export MRN.
Internal declaration number
A reference generated by an ERP, customs application or service provider. It may exist before customs accepts the declaration.
NOT PROOF OF CUSTOMS ACCEPTANCECustoms movement reference
The reference assigned following acceptance of the export declaration. It identifies the relevant customs movement.
ACCEPTANCE — NOT EXIT CERTIFICATIONTransit or another procedure
Other customs procedures can also use an MRN. The identifier must be checked against the relevant procedure and customs system.
VERIFY THE PROCEDURE AND SYSTEMAccepted does not mean released.
When acceptance is confirmed but release is not, the investigation must focus on the customs decision, possible controls, unresolved requirements and communication of the outcome.
A missing IE529 in the local application requires status reconciliation. It does not automatically establish that customs refused release.
Was a control decision communicated?
Review the relevant AES control notification and the national customs record. A control decision is not itself a release decision.
Is the declaration awaiting customs action?
Determine whether documentary checks, examination or other requirements remain outstanding. Do not infer a reason from an unexplained pending status.
Was a release or no-release message issued?
Reconcile the relevant response, including IE529 for release or IE551 for no release where applicable to the scenario.
Has the local application updated?
If the official status and software display disagree, inspect message reception, mapping and processing logs.
Three systems. Three different answers.
Operational records often describe different events. Compare the evidence and its source before deciding whether there is a genuine customs discrepancy.
The application shows the last status it has successfully processed.
CHECK: INBOUND MESSAGE HISTORYThe relevant national system may show a later customs decision.
CHECK: OFFICIAL STATUS AND TIMESTAMPA commercial transport event does not automatically establish customs exit certification.
CHECK: TRANSPORT EVIDENCE AND CUSTOMS EXITDifferent information is not necessarily contradictory. A customs release decision, a transport departure and customs certification of exit concern different events. Their timestamps and supporting records must be evaluated separately.
Match the symptom to the next verification.
| Observed symptom | What it may mean | First action | Do not assume |
|---|---|---|---|
| MRN not visible | Wrong reference, portal or permissions; possible missing acceptance | Verify IE528 and national records | Declaration is invalid |
| MRN received, no release | Pending customs decision or missing response | Check control, release and no-release messages | Goods may leave under export release |
| Portal shows release, ERP does not | Inbound message or local synchronisation issue | Reconcile official status and logs | Customs has not released the goods |
| Carrier confirms departure | Commercial movement event | Verify customs exit information separately | Exit has been certified |
| Release confirmed, exit missing | Exit processing, notification or enquiry issue | Investigate office-of-exit records and follow-up | Release equals exit certification |
Release and exit certification are separate legal events.
Under the Union Customs Code, acceptance of a declaration and release of goods have distinct legal consequences. Certification of exit is governed by Article 334 of Commission Implementing Regulation (EU) 2015/2447. Where exit information remains unresolved, Article 335 provides an enquiry procedure, including provisions concerning information and evidence of exit.
The 90-day period in Article 335(1) concerns a possible enquiry by the customs office of export after release. It is not a general requirement for operators to wait 90 days before investigating an unresolved movement.
Regulation (EU) No 952/2013, including Articles 172, 188 and 194; Commission Implementing Regulation (EU) 2015/2447, Articles 334–335; European Commission AES Business Guidance. National customs systems determine the available status-query mechanisms and trader-facing interfaces.
Goods exported. Exit not certified.
The goods may have physically left the European Union, yet the export declaration remains open or the trader has not received the expected exit notification. Resolving the discrepancy requires a clear distinction between physical movement, electronic exit results and certification by the customs office of export.
Physical exit is not the same as certified exit.
Export goods have been released under the relevant customs decision.
IE529
Exit formalities and physical departure must be established.
EXIT EVENT
The customs office of export confirms the exit outcome.
IE599 / RESULT
Critical distinction: IE599 can communicate a positive or negative exit outcome. A received IE599 must therefore be checked for its actual control-result information. Its mere existence does not establish successful exit.
Find out which part of the exit chain is incomplete.
Start with the office-of-export record and the actual exit movement. A missing notification may reflect a customs-processing issue or a local communication problem.
Goods have not reached the expected exit stage
Verify the route, actual office of exit, presentation requirements and transport information. The declared office and actual exit route may differ.
CHECK THE PHYSICAL AND CUSTOMS ROUTEExit information has not reached the office of export
The customs office of export may still be waiting for the relevant exit results from the office of exit. The AES business flow uses IE518 for this exchange.
VERIFY EXIT RESULTS WITH CUSTOMSExit outcome exists but is not visible to the trader
A response may have been issued but not imported, displayed or correlated correctly by the trader’s software or service provider.
RECONCILE OFFICIAL STATUS AND MESSAGE LOGSTwo customs offices. Different responsibilities.
Understanding the division of responsibilities helps direct an enquiry to the appropriate authority and avoid treating a carrier’s transport confirmation as a customs decision.
Confirms exit-related results
The office of exit handles the applicable exit formalities and communicates exit results to the office of export through the relevant customs system.
Certifies the export exit
The office of export certifies exit to the declarant or exporter in the circumstances set out in Article 334 of Implementing Regulation 2015/2447.
How an unresolved export can be investigated.
The legal enquiry procedure provides a route for obtaining exit information and, in the circumstances laid down by law, supporting certification through alternative evidence.
Confirm release and missing exit information
Establish the MRN, release date, intended exit route and the last confirmed customs event. Preserve the existing transport records.
Provide exit details and request certification
Under Article 335(2), the declarant may proactively inform the office of export of the exit date and office of exit. Article 335(3) permits a request for exit certification in this context.
The office of export requests exit information
The office of export seeks information from the office of exit, which must respond within 10 days under Article 335(3).
Submit supporting evidence when the legal condition is met
If the office of exit does not respond within the prescribed period and the office of export informs the declarant, Article 335(4) permits the declarant to provide evidence of exit.
Obtain and retain the official outcome
The office of export assesses the information and, where the legal conditions are fulfilled, certifies exit. Retain the resulting customs communication with the export file.
What evidence can support certification of exit?
The regulation identifies several types of evidence that may be presented individually or in combination. The office of export determines whether the material is sufficient to establish that the goods left the customs territory of the Union.
Authenticated delivery evidence
A delivery note signed or authenticated by the consignee outside the EU customs territory.
Commercial documents
Invoices, delivery notes and proof of payment relevant to the exported goods.
Transport operator confirmation
A document signed or authenticated by the economic operator that took the goods outside the EU customs territory.
Customs-processed documents
Documentation processed by an EU Member State or third-country customs authority in accordance with applicable procedures.
Special supply records
Economic operators’ records for supplies to ships, aircraft or offshore installations, where relevant.
Evidence must support the actual exit.
A CMR, tracking record, invoice or payment confirmation should be assessed for its evidential value. No single document automatically guarantees certification.
Truck delivered outside the EU. Export still open.
A shipment has been released for export. The carrier confirms delivery to a consignee in a third country, but the trader has not received a positive exit notification.
MRN and release response available.
Delivery documents may support investigation.
No positive certification confirmed in the export record.
Correct approach: reconcile the office-of-export status, identify the actual office of exit and follow the Article 335 enquiry route where applicable. Preserve the transport evidence for any subsequent request. Do not close the customs issue merely because the consignee received the goods.
Unresolved exit can create problems beyond AES.
Customs certification and VAT exemption are related but legally distinct questions. An unresolved exit record can complicate the exporter’s ability to substantiate a VAT-exempt export and can expose weaknesses in document retention and reconciliation.
The applicable VAT treatment must be assessed under Directive 2006/112/EC, particularly Article 146, relevant case law and national implementing rules. A missing IE599 does not, by itself, establish that VAT is automatically due or that an exemption is necessarily unavailable.
Commission Implementing Regulation (EU) 2015/2447, Articles 334–335; Regulation (EU) No 952/2013, Article 267; European Commission AES Business Guidance, exit results and export notification; Council Directive 2006/112/EC, Article 146. National customs and VAT guidance should be consulted for the specific operation.
Resolve the incident. Prevent the next one.
Effective AES troubleshooting does not end when a message is recovered. Every incident should leave a verified customs status, a documented resolution and a clearer understanding of how to prevent the same failure.
Answers to recurring AES operational problems.
These answers explain general EU customs principles. National system specifications and the actual customs record remain essential when resolving a live movement.
01 What should I do if an AES declaration is rejected?
Identify whether the rejection occurred at the technical interface or during customs business validation. Read the complete error response, identify the affected data element and correct the underlying issue before resubmission.
A rejection does not have the same meaning as a customs decision not to release goods. Verify whether the original declaration was accepted and whether an MRN exists.
02 Can I resend a declaration after a timeout?
Not without checking the original submission. A timeout may occur after the customs system has received or processed the request. Review transport logs, acknowledgements and available official status information.
Follow the national retry and duplicate-handling rules. An uncontrolled resubmission can create additional reconciliation problems.
03 Does receiving an MRN mean the goods are released?
No. The export MRN is assigned following acceptance of the declaration. Release for export is a separate customs decision. In the standard AES message flow, IE528 communicates acceptance and IE529 communicates release for export.
Neither acceptance nor release proves that the goods have exited the EU.
04 Why is my export MRN not found?
Check the exact reference, customs procedure, national system and search permissions. Confirm that the reference was actually assigned by customs rather than generated locally by an ERP or service provider.
An unsuccessful search alone does not prove that the export declaration is invalid.
05 What if IE529 is missing but customs shows release?
Reconcile the official customs status with the trader’s inbound message history. The response may have been delivered but not correctly imported, correlated or displayed by the software.
Preserve the official release evidence and investigate the integration failure separately. Do not fabricate a missing electronic response.
06 Does an IE599 always confirm successful exit?
No. The AES Export Notification IE599 can communicate a positive or negative outcome. Inspect the exit control result and relevant data rather than relying on the message identifier alone.
A negative exit outcome must not be treated as proof that goods successfully left the customs territory of the Union.
07 Can I investigate missing exit confirmation before 90 days?
Yes. Article 335(2) of Implementing Regulation (EU) 2015/2447 allows the declarant to provide exit details to the customs office of export on their own initiative.
The 90-day period in Article 335(1) relates to a possible enquiry initiated by the office of export. It is not a mandatory waiting period for the declarant.
08 Is a signed CMR enough to close an export?
Not automatically. Transport documents may contribute to evidence of exit, but their relevance and sufficiency must be assessed in the applicable legal procedure.
Article 335(4) provides for alternative evidence under specific conditions. The customs office of export determines whether the evidence is sufficient to certify exit under Article 334.
09 Can a carrier’s delivery confirmation replace customs exit certification?
No. Delivery and customs certification are different events. A carrier’s confirmation may help establish the route and movement of the goods, but the customs exit outcome must be reconciled through the applicable official procedure.
10 Does missing IE599 automatically invalidate the VAT exemption?
No automatic conclusion follows from the absence of that message alone. VAT treatment depends on the applicable substantive conditions, evidence and national rules.
However, unresolved customs exit records create documentary risk and should be investigated promptly. Customs certification and VAT evidence must be assessed distinctly.
Build a reliable export monitoring routine.
A practical control system should identify exceptions before they become unresolved movements, duplicate submissions or incomplete export files.
Match each outbound declaration with its actual customs response.
Store the customs-assigned MRN against the correct local shipment record.
Distinguish accepted, released and not-released movements.
Identify released exports without a confirmed positive exit outcome.
Assign a responsible operator, next action and follow-up date.
Preserve messages, logs, customs decisions and supporting evidence.
These are recommended internal controls, not a six-step procedure prescribed by EU customs law. Monitoring frequency and escalation thresholds should reflect transaction volume and operational risk.
Route each issue to the right owner.
Transport or integration failure
Timeout, authentication issue, failed message import or software synchronisation error.
Business validation or data error
Rejected data, inconsistent references, incorrect particulars or unsupported declaration scenario.
Control, release or no-release issue
The declaration is accepted but a customs decision is pending, unavailable or disputed.
Unresolved export completion
Missing positive exit result, route discrepancy, incomplete transport evidence or enquiry.
Escalate with evidence, not just a screenshot.
A complete incident record helps the software provider, customs representative or competent customs office understand what happened without reconstructing the entire operation from the beginning.
Include sensitive commercial information only through authorised support channels, and follow applicable data-protection and security procedures.
Official sources and further reading.
This guide provides operational explanations of AES troubleshooting. Legal requirements are determined by the applicable EU provisions and national implementing procedures. The Commission’s AES business documentation explains the message flows.