Content updated: · About the tool
Read the stage together with its context
This guide groups procedural stages; it is not a translation table for every label in every national system. Preserve the result’s original wording, source and event time. If a message code is available, include it when asking the declarant for clarification.
Check whether a displayed date describes an event, a source update or your latest lookup. A check performed just now does not establish that every recent customs action is already visible. Keeping those dates separate makes later comparisons much more useful.
Export: acceptance, release and exit information
AES handles declaration acceptance, goods release and exit certification as distinct stages. Release for export does not by itself confirm that the goods have exited.
If the cargo is awaiting onward transport, establish the stage reached and who is handling the next action. If the cargo should already have left the EU, compare the declarant’s information with the transport history. Ask for the relevant confirmation document instead of treating a screenshot of a public status as that document.
Sources: European Commission — Automated Export System (AES)
Transit: arrival is different from discharge
Transit distinguishes ending through presentation at destination from discharge establishing correct completion after comparison of the relevant data. An arrival label therefore needs a different interpretation from confirmation of discharge.
If your question is whether T1 has been discharged, ask the handling team exactly that. Ask whether information from destination is missing or a particular discrepancy is being investigated. Keep the enquiry tied to transit instead of turning it into a request for export confirmation.
Sources: European Commission — Transit Manual 2026, VII.1.2.2.1 (page 411)
Document codes need a country and system
PUESC identifies CC599C as an export-completion message in Poland’s AES/ECS2 PLUS. Read a national document code in its own system’s context. A Polish message name is not a universal name for every export result across the EU.
Where the paperwork covers both export and transit, record the two MRNs on separate lines. Add the procedure, latest information and responsible contact for each. This prevents a reply about one declaration from being inadvertently used to close the question about the other.
Sources: PUESC — Złóż wywozowe zgłoszenie celne i wykonaj inne obowiązki związane z wywozem towarów
Unknown results and unavailable sources
MRN Follow-up help describes differences between public information and national systems. An absent stage in the public view does not establish its absence from the declaration records. Historical details in that help should not be generalised to every current procedure.
Keep missing data, rejected input and source failure as separate categories. If the request did not retrieve a response, do not assign “open” or “closed”. Restore the ability to check, or establish the state with the team that has access to the declaration.
Sources: European Commission — MRN Follow-up help (includes historical guidance)
Keep a useful record for the next person
In your internal case record, retain enough context for somebody else to understand the question without repeating your investigation.
- Procedure and MRN taken from the original document.
- Exact status wording and the visible event date.
- Source and lookup time, separately from the event date.
- Carrier or terminal information, clearly labelled with what it concerns.
- The specific missing stage or document and the contact responsible for checking it.