Export data retrieval

Retrieve export data by MRN and transfer every item into NCTS

From 1 September 2026, Germany's ATLAS system will automatically compare export and transit declarations. Declarium uses the export MRN, transfers the available item data from ATLAS, and turns it into a complete, reviewable NCTS dataset without retyping every item.

Solution approach

Turn an export MRN into a complete NCTS dataset

For export followed by transit, Declarium receives the export MRN and retrieves the export data made available through the intended ATLAS workflow. House consignments and goods items are transferred in a structured way into the preparation of the transit declaration. This creates a reliable NCTS dataset without operations teams having to enter every export item again.

  • Retrieve export data using the MRN
  • Transfer available export data at item level
  • Prepare a complete NCTS transit declaration

ATLAS checks export and transit automatically from 1 September 2026

The interface between ATLAS Export and ATLAS Transit turns a comparison that was often performed manually into a system check. ATLAS compares the commodity code, goods quantity or net mass, and country of destination. It also checks the transit declaration type, customs status, procedure code, export status, and correct export references.

  • Compare commodity code, net mass, and destination country
  • Check transit type, customs status, and procedure code
  • Confirm that the export status permits onward movement under transit

Why consolidated items become a risk

Some workflows compress several export items into one transit item, for example by using the first item's commodity code and the total weight or value of the entire shipment. That model does not reproduce the referenced export declaration one to one. Under the automated comparison, missing items, different commodity codes, or an inconsistent net mass can therefore prevent acceptance or release.

  • Do not compress several export items into one aggregate item
  • Map every NCTS item to the correct export item
  • Handle item order and references in a controlled way

How MRN-based export data retrieval works

The workflow starts with the export MRN. Through the intended process, the export consignment is presented for onward movement under transit and ATLAS provides the exit data. Declarium processes the response, creates the matching house consignments and goods items, adds the required previous-document references, and makes the resulting dataset reviewable before further processing.

  • Receive the export MRN and workflow context digitally
  • Process export data from the ATLAS response
  • Prepare house consignments, goods items, and previous-document references

Item-level transfer instead of duplicate data entry

The export declaration already contains core goods data needed again for the subsequent transit procedure. Declarium uses this existing data source and transfers the relevant items into the NCTS workflow in a controlled way. Operations teams no longer need to copy commodity codes, weights, destination countries, and item numbers from documents or emails.

  • Less manual copying from export documents, PDFs, or customs software
  • Lower risk of typing errors and swapped items
  • One consistent data basis for export and transit

Correct N830 references and the NCTS Phase 5 structure

For export followed by transit, the export declaration is referenced as previous document N830. In NCTS Phase 5, one house consignment generally corresponds to one previous export declaration and must contain its goods items completely. If the item order differs, the original export item number needs to be mapped explicitly. Declarium prepares this structure transparently in the data workflow.

  • Reference the export MRN on the correct house consignment
  • Map goods items one to one to the export declaration
  • Represent different item orders unambiguously

For forwarders, authorised consignors, shippers, and 3PLs

The solution is particularly relevant when an exporter or customs agent prepares the export declaration, while the subsequent transit procedure is handled by a freight forwarder, authorised consignor, warehouse, or 3PL. This handover is exactly where broken data flows, missing item details, and time-critical questions often occur.

  • Freight forwarders and carriers handling export followed by transit
  • Authorised consignors and warehouses with NCTS workflows
  • Exporters, shippers, and 3PLs with shared responsibilities

Start without a large integration project

Companies can begin with a controlled MRN handover and managed workflow. For recurring volumes, export data retrieval can later be integrated into TMS, WMS, ERP, or other operating systems. Status, questions, MRNs, and documents remain visible in a structured process.

  • Controlled start with existing MRN and shipment data
  • Later REST API integration for recurring volumes
  • Return status, errors, and documents to operational systems

Find errors before the truck stops

Even with automated data transfer, professional exceptions can occur, such as an export status that does not permit transit, an incompatible transit type, or an actual shipment that changed after export acceptance. Declarium makes questions and errors visible so they can be resolved before departure or release instead of stopping the movement at customs.

  • Plausibility checks before further processing
  • Clear questions for status and procedure conflicts
  • Traceable exception handling instead of unresolved email threads

Common Questions

What is export data retrieval by MRN?

Export data retrieval uses the MRN of an existing export movement to obtain the export data made available for the subsequent transit movement through the intended ATLAS workflow. The data can then be prepared at item level for the NCTS transit declaration.

Can Declarium retrieve export data using only the MRN?

The export MRN is the central starting point. The professional and technical conditions for export followed by transit must also be met, including the appropriate export status, customs office, and role in the process. Declarium maps these requirements during onboarding and operation.

Which export data is transferred into the transit declaration?

Relevant data includes house consignments, goods items, commodity codes, net masses, destination countries, and references to the export MRN and export item. Additional requirements depend on the specific transit procedure and goods flow.

What changes on 1 September 2026?

Germany will activate the interface between ATLAS Export and ATLAS Transit. Selected data and professional conditions will then be checked automatically. A negative result can prevent receipt, acceptance, or release of the transit declaration.

Do export and transit data have to match 100 percent?

ATLAS does not compare every field in both declarations. The automated check particularly covers commodity code, net mass, destination country, procedure and status compatibility, and correct references. The referenced goods items need to match clearly at item level.

Can several export items be consolidated into one NCTS item?

When a transit declaration references an export declaration, the goods items generally need to be mapped one to one. Combining several different export items into one NCTS item does not reproduce that structure correctly and may cause rejection during the automated data check.

What happens when the ATLAS data check is negative?

Depending on the time of the check, the transit declaration is not received, accepted, or released. According to the ATLAS participant notice, a new corrected transit declaration must then be created.

Is export data retrieval a public MRN lookup?

No. An MRN alone does not provide public access to complete export data. The data transfer takes place within the intended customs and ATLAS workflow with the required roles, messages, and professional conditions.

Does the automated check also apply to air freight?

For air transport and Road Feeder Services, additional-information code T0002 may be used under the conditions described in ATLAS-Info 0981/2026. In that case, the comparison remains manual. Eligibility needs to be checked for the specific workflow.

Does Declarium require a direct TMS or ERP integration?

No. Companies can start with a controlled workflow without a large integration project. For recurring volumes, the process can later connect to TMS, WMS, ERP, or other operating systems through the Declarium REST API.

Hendrik Schote & Chris Aufenanger

Co-Founders

Ready for the next step? Simply reach out to us. We look forward to the conversation.

Hundreds of users already trust Declarium.