Stabilizing SAP GTS for the AES Phase 5 Era
- Patrik Rajský

- Jan 15
- 3 min read
In our previous deep-dive, we explored the "Smart Border" requirements and the XML-based shift of France's DELTA-IE. However, as SAP Leads are quickly discovering, the challenges of 2026 extend far beyond the French border.
While France has completed its migration, other member states are at varying stages of the UCC Automated Export System (AES) Phase 5 roadmap. This follow-up examines the broader EU landscape, providing a strategic blueprint for maintaining compliance across all European territories within SAP GTS 11.0 and SAP GTS, edition for SAP HANA.

The EUCDM Revolution: Data Elements Over SAD Boxes
The move to AES Phase 5 is not a simple format update; it is a fundamental re-engineering of customs business semantics based on the EU Customs Data Model (EUCDM).
Hierarchical XML: The flat structure of the legacy Single Administrative Document (SAD) and its numbered "boxes" are replaced by nested XML Data Groups and Data Elements (D.E.).
Explicit Context: Systems no longer infer context; for example, D.E. 1/1 now requires granular codes like "EX A" for standard exports.
Commodity Precision: Export declarations in systems like DELTA-IE now strictly require 8-digit Combined Nomenclature codes, while imports retain 10-digit TARIC codes.
Actor Identification: There is a significant shift from location-based IDs (like the 14-digit SIRET in France) to legal entity-based IDs (the 9-digit SIREN) to align with the Union Customs Code (UCC).t
Technical Architecture: The Death of the IDoc
AES Phase 5 marks the definitive end of the "IDoc Era" for European customs communications. The asynchronous, batch-oriented nature of Intermediate Documents is incompatible with the real-time, synchronous requirements of modern UCC systems.
Shift to Enterprise Services: SAP GTS edition for SAP HANA (E4H) now generates XML payloads (like the IE515) directly within the Customs Management Communication Engine.
SOAP and APIs: Communication is now wrapped in SOAP envelopes or transmitted via RESTful-like API endpoints.
Real-Time Polling: In jurisdictions like Romania (AES-RO), the system utilizes a System-to-System (S2S) architecture requiring the middleware to "pull" messages from a queue rather than receiving a direct push.
Upstream Schema Validation: Validation has moved "upstream". E4H now performs local XSD schema checks before a message is even signed, reducing fatal errors from customs authorities but increasing the CPU load on the GTS server.
Managing the "Multi-Speed" European Landscape
The operational reality in early 2026 is characterized by a "multi-speed" Europe. IT teams must manage a hybrid ecosystem of stable core markets and strategic laggards.
Member State | System | Status (Jan 2026) | Key Technical Characteristic |
Germany | ATLAS 10.x | Stabilized | Strict enforcement; no legacy support. |
Spain | AES V5 | Stabilized | High maturity; legacy EXS V4 retired. |
France | DELTA-IE | Transitional | Hybrid operations; frequent "stabilization phase" anomalies. |
Netherlands | DMS 4.1 | Delayed | Centralized Clearance (CCE) delayed until July 2026. |
Strategic Recommendations for SAP Leads
To navigate the "messy reality" of the 2026 stabilization phase, we recommend three immediate technical focuses:
Automate the ELO Handshake: In France, the Enveloppe Logistique Obligatoire (ELO) is now strictly mandatory for UK-EU trade. Since GTS does not natively create these logistics "folders," IT must bridge the gap via APIs to push MRNs directly to carrier "Smart Border" tools.
Refine Classification Truncation: Ensure your GTS classification strategy automatically truncates commodity codes to 8 digits for French export (CUSFR) while retaining 10 digits for imports to avoid IE515 schema rejections.
Monitor the IE599 Loop: Persistent anomalies in receiving electronic proofs of exit (IE599) pose a major VAT risk. Implement an "Incomplete Declaration" report to alert teams 5 days before the new, rigid "Two-Step" regularization deadlines.
Is your SAP GTS landscape fully compliant with the 2026 AES mandates?
Our consultants specialize in stabilizing XML message flows and resolving complex EUCDM mapping rejections.



Comments