© FOD FIN Belgium and IBM Corporation 2008
MASP.be
Author: Jan Augustijnen
Customer: FOD FIN Belgium
Document:
106748961
Date: 05/06/09
Version: 0.13
Owner:
Subject:
FOD FIN D&A
Status: Draft
Message Implementation Guide Exit Summary Declaration IE615 - IE613 - IE628 - IE604 - IE605 - IE616Page 1 of 36
© FOD FIN Belgium and IBM Corporation 2008
MASP.be
Document History
Revision History
Date of this revision: 05/06/09
Revision
Number
00.01
0.02
0.03
0.04
0.05
0.06
0.07
0.08
0.09
0.10
Revision Date
0.11
0.12
0.13
24/04/09
19/05/09
05/06/09
30/07/2008
12/08/2008
25/8/08
1/9/08
8/9/08
10/9/08
15/9/08
05/02/09
25/02/09
2/03/09
Date of next revision
(date)
Summary of Changes
Changes
marked
Initial version created
(N)
Added description of individual messages
(N)
Added CUSCAR
(N)
Added CARGOIMP
(N)
Added annex 30bis + EXS for CARGOIMP to XML
(N)
Correction of CUSCAR section
(N)
Correction of response messages
(N)
Updated XML section
(N)
Revision after remarks Michaël Vico
(N)
Transport charges = SG8->CPI instead of SG7->TOD + various (N)
fixes and clarifications.
Alignment with latest DG Taxud specifications
(N)
Add “number of pieces” to EDIFACT mapping
(N)
Correct box 30 EDIFACT / XML mapping
Y
Approvals
This document requires following approvals. Signed approval forms are filed in the Quality section of the
PCB.
Name
Paul Raes
Title
Program Manager D&A
Distribution
This document has been distributed to
Name
Paul Raes
Title
Program Manager D&A
Michael Vico
Project Manager D&A ECS
Bart Cieters
Analyst PLDA
Sven Rosiers
Architect IBM ECS
Ioana Aldea
Business Analyst IBM ECS
Stefan Van Assche
Lead Architect IBM
Carla Martens
QA IBM
Frieda Bollaert
Program Manager IBM
Document:
106748961
Date: 05/06/09
Version: 0.13
Owner:
Subject:
FOD FIN D&A
Status: Draft
Message Implementation Guide Exit Summary Declaration IE615 - IE613 - IE628 - IE604 - IE605 - IE616Page 2 of 36
© FOD FIN Belgium and IBM Corporation 2008
MASP.be
Contents
Document History ........................................................................................................... 2
Document History ........................................................................................................... 2
Revision History ........................................................................................................................................... 2
Revision History ........................................................................................................................................... 2
Approvals ..................................................................................................................................................... 2
Approvals ..................................................................................................................................................... 2
Distribution ................................................................................................................................................... 2
Distribution ................................................................................................................................................... 2
Contents ......................................................................................................................... 3
Contents ......................................................................................................................... 3
1. Introduction .................................................................................................................. 5
1.1 Purpose ................................................................................................................................................... 5
1.2 References .............................................................................................................................................. 5
1.3 Notation ................................................................................................................................................... 6
1.1 Functional description ........................................................................................................................... 10
1.1.1 Purpose .............................................................................................................................................. 10
1.1.2 Process Description ........................................................................................................................... 10
1.1.3 Sequence Diagram ............................................................................................................................ 11
1.1.3.1.1 Core flow ...................................................................................................................................... 11
1.1.3.1.2 Declaration Rejected .................................................................................................................... 12
1.1.3.1.3 EXS Amendment Accepted ......................................................................................................... 12
1.1.3.1.4 Amendment Rejected .................................................................................................................. 13
1.1.4 Timing constrains .............................................................................................................................. 14
1.1.5 Messages ........................................................................................................................................... 14
1.1.6 Exceptions & comments ..................................................................................................................... 15
1.2 Functional message structure ............................................................................................................... 16
1.3.1 Design principle .................................................................................................................................. 16
1.2.1 Primary message ............................................................................................................................... 16
1.2.1.1 Message structure .......................................................................................................................... 16
1.2.1.2 Field explanations ........................................................................................................................... 19
1.3.1.1.1 1875 annex 30 bis requirements ................................................................................................. 21
1.2.1.3 Mapping to XML ............................................................................................................................. 24
IE615 EXS .................................................................................................................................................. 24
IE613 EXS Amendment request ................................................................................................................ 25
1.2.1.4 Mapping to EDIFACT ..................................................................................................................... 27
1.2.1.5 Mapping to CARGOIMP ................................................................................................................. 29
Document:
106748961
Date: 05/06/09
Version: 0.13
Owner:
Subject:
FOD FIN D&A
Status: Draft
Message Implementation Guide Exit Summary Declaration IE615 - IE613 - IE628 - IE604 - IE605 - IE616Page 3 of 36
1.2.2 Response messages .......................................................................................................................... 30
1.2.2.1.1 Message Structure ....................................................................................................................... 30
IE628 EXS accepted .................................................................................................................................. 30
IE616 EXS rejected .................................................................................................................................... 30
IE604 EXS Amendment accepted .............................................................................................................. 30
IE605 EXS Amendment rejected................................................................................................................ 31
1.2.2.1.2 Mapping to XML ........................................................................................................................... 32
IE628 EXS accepted .................................................................................................................................. 32
IE616 EXS rejected .................................................................................................................................... 32
IE604 EXS Amendment accepted .............................................................................................................. 33
IE605 EXS Amendment rejected................................................................................................................ 33
1.2.2.1.3 Mapping to EDIFACT ................................................................................................................... 34
1.2.2.2 Mapping to CARGOIMP ................................................................................................................. 36
1.4 Technical message handling ................................................................................................................ 36
1. Introduction
This chapter identifies the document, describes the contents of the document, and states its purpose.
1.1
Purpose
The primary purpose of the Message Implementation Guide for IE615 - IE613 - IE628 - IE604 - IE605 IE616 is to describe the way that the messages and their related response message need to be
implemented.
1.2
References
This document refers to the following external documents and/or Web sites
Ref.
A1
Reference
Process definition ECS
Title
Doc1040-FSS_ECS Addendum_1-2006-final_
IIA_main doc.doc
Release
Final
A2
Messages ECS
Doc1040-FSS_ECS Addendum_1-2006final_B1_messages.doc
Final
A3
Codelists ECS
Doc1040-FSS_ECS ADDENDUM 1-2006-FINALA3_CODE LIST.DOC
Final
A4
Design Document ECS
CUD-SC01-DDNXA-v2.00-EN.doc
2.00
A5
XML Mapping
CUD-SC01-DDNXA_ECS_P2_APP_R_200-EN.pdf
2.00
CUSRES D04A
http://plda.fgov.be/files/u1/PLDA_MIG_CUS 1.1
RES-D04A_RB_v1_1.zip
CUSDEC D04A
http://plda.fgov.be/files/u1/NL_PLDA_05_MI 1.0
G_CUSDEC_EXP-D04A_revisie_V1_2.doc
A8
SAD XML
http://masp.belgium.be/en/content/ecs-fase-2-0
Functional
A9
PLDA
B2B
Documentation
A10
PLDA
B2B
Documentation
Synthese
A6
A7
A13
or 1.1
http://plda.fgov.be/fr/documentation#12
http://plda.fgov.be/nl/documentatie#11
or 1.1
http://plda.fgov.be/fr/documentation#11
CUSDEC Release
http://plda.fgov.be/files/u1/NL_PLDA_05_MI 1.0
G_CUSDEC_EXP_releaseD04A_V_1_0.doc
CUSCAR D04A
http://plda.fgov.be/files/u1/PLDA_MIG_CUS
CAR-D04A_RB_v1_7.zip
A11
A12
http://plda.fgov.be/nl/documentatie#12
1875 regulation including http://eurannex 30bis
lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2
006:360:0064:0125:EN:PDF
1.3
Notation
Acronym
Description
AAR
Anticipated Arrival Record
AER
Anticipated Export Record
ECS
Automated Export System
AIS
Automated Import System
API
Application Programming Interface
ATR
Anticipated Transit Record
BANSTA
BANking STAtus message
BGM
Beginning of Message. This is the name of a segment of an EDIFACT-message.
CAoDep
Competent Authority of Country of Departure
CASO
Central Application Security Officer
CCN
Common Communication Network
CD
Common Domain
CDCA
Centrally Developed Customs Application
CDIA
CCN/TC Directory Administrator
CDTA
Centrally Developed Transit Application
CoA
Confirm on Arrival
CoD
Confirm on Delivery
COL
Customs Office List
CONTRL
Syntax and service report message (CONTRL) EDIFACT message
CPT
Central Project Team
CS/MIS
Central Services Management Information System
CS/RD
Central Services Reference Data
CSE
Consolidated Specifications Environment
CSI
Common Systems Interface
CSIDD
CCN/CSI Data Descriptor
CSO
CCN-TC Central Security Officer
CSS
Central Services Specification
CUSCAR
CUStoms CArgo Report EDIFACT message (UNSM)
CUSDEC
CUStoms DEClaration EDIFACT message (UNSM)
CUSRES
CUStoms RESponse EDIFACT message (UNSM)
DDNA
Design Document for National Applications
DDNIA
Design Document for National Import Applications
DDNTA
Design Document for National Transit Applications
DDNXA
Design Document for National Export Applications
DMR
Data Maintenance Request (UN/EDIFACT)
Acronym
Description
DTD
Document Type Definition
DTI
Direct Trader Input
EBP
Elementary Business Process
EC
European Community
ECN
EDI/CSI Node
ECN+
EDI/CSI Node Plus
ECS
Export Control System
ECTA
Export Control Test Application
EDI
Electronic Data Interchange
EDIFACT
Electronic Data Interchange for Administration, Commerce and Transport
EFTA
European Free Trade Association
EXC
Exception Report
EXP
Expiration Report
EXS
Exit Summary Declaration
FMS
Functional Message Structure
FTSS
Functional Transit System Specification
FTX
Free TeXt. This is the name of a segment of an EDIFACT-message.
GENRAL
GENeRAL purpose message
GESMES
GEneric Statistical MESsage EDIFACT (UNSM)
GMT
Greenwich Mean Time
GSS
Generic Security Services
GUI
Graphical User Interface
HAoDes
Higher Authority of the Office of Destination
HS6
Harmonised System 6
HTML
HyperText Markup Language
HTTP
HyperText Transfer Protocol
HTTPS
HTTP over SSL
ICR
Issue Control Report
ICS
Import Control System
IDL
Interface Definition Language
IE
Information Exchange
IETF
Internet Engineering Task Force
IFL
Implementation of Functional Languages
ISO
International Standards Organisation
IT
Information Technology
KEL
Known Error List
LAA
Local Application Administrator
LAD
Local Application Designer
Acronym
Description
LRN
Local Reference Number
LSO
Local Security Officer
LSYA
Local System Administrator
MCC
Minimal Common Core
MD5
Message Digest 5
MIME
Multipurpose Internet Mail Extensions
MRN
Movement Reference Number
NA
National Administration
NCA
National Customs Application
NCF
Notification of Crossing Frontier
NCTA
National Customs Test Application
NCTS
New Computerised Transit System
NCTS-CO
New Computerised Transit System – Central Operations
NDCA
Nationally Developed Customs Application
NECA
National Export Control Application
NECTA
National Export Control Test Application
NTA
National Transit Application
NTSR
National Transit System Requirements
NTTA
National Transit Test Application
OLAF
Office Europeen de Lutte Anti-fraude / European Anti-fraud Office
OoDep
(Customs) Office of Departure
OoDes
(Customs) Office of Destination
OoExp
(Customs) Office of Export
OoExt
(Customs) Office of Exit
OoGua
(Customs) Office of Guarantee
OoLdg
(Customs) Office of Lodgement
OoTra
(Customs) Office of Transit
OTS
Old Transit System
PARTIN
Party Information EDIFACT message (UNSM)
PARTTC
Party Transit Computerisation EDIFACT message (PARTIN + DMRs)
QoS
Quality of Service
RD
Reference Data
RFC
Request For Comment
SAD
Single Administrative Document
SAM
Single Administrative Message
SECTA
Standard Export Control Test Application
SGML
Standard Generalised Markup Language
SMTP
Simple Message Transfer Protocol
Acronym
Description
SRO
System Requirements Overview
SSL
Secure Socket Layer
STD
State Transition Diagram
STTA
Standard Transit Test Application
SUG
Start-up Guide
TAXUD
TAXation and Customs Union DG
TBD
To Be Determined
TC
Technical Centre
TCC
Transit Community / Common customs
TCP
Transit Computerisation Project
TETA
Trader EDI Test Application
TLS
Transport Layer Security
TMS
Technical Message Structure
TraDep
Trader at Departure
TraDes
Trader at Destination
TraExp
Trader at Export
TraExt
Trader at Exit
TraLdg
Person Lodging Summary Declaration
TSD
Time Sequence Diagram
TTA
Transit Test Application
TTSS
Technical Transit System Specification
UDP
Upload/Download Parsing
UML
Unified Modelling Language
UN
United Nations
UN/EDIFACT
See ‘UN’ and ‘EDIFACT’
UNB, UNH, UNT,
UNZ, UCD, UCI,
UCM, UCS
These are not abbreviations but names of (service) segments of an EDIFACT-message.
UNSf
User Needs Specification
UNSM
United Nations Standard Message (e.g. CUSDEC)
URI
Universal Resource Identifier
UTF
UCS Transformation Format
WWW
World Wide Web
XML
eXtensible Markup Language
1.1
Functional description
1.1.1 Purpose
The Exit summary declaration is used in case goods leaving the customs territory of the Community are
not assigned to a customs approved treatment or use for which a customs declaration is required. In
other words, the EXS needs to be used for goods for which no export declaration (IE515) was issued (
see also 1.1.6)
1.1.2 Process Description
Where goods to be brought out of the customs territory of the Community are not covered by a customs
declaration, an “Exit Summary Declaration”, shall be lodged at the customs office of exit, as defined in
Article 793(2) of Commission Regulation (EC) No 1875/2006, in accordance with Article 182c of the
Code. The Exit summary declaration is used in case goods leaving the customs territory of the
Community are not assigned to a customs approved treatment or use for which a customs declaration is
required.
The most important change between the EXS processes and the export declaration processes is that we
must take into account that the EXS is sent by the Exporter/Lodger/Trader to the Office of Exit directly
before arrival of the goods in the Office of Exit. Since the Office of Exit does not have declaration
information in his system. Any MRN and item numbers references must be checked using the EXS data,
not the declaration data.
The EXS is handled by PLDA in the same way as the manifest, more specifically using the CUSCAR04
message using the following attribute BGM/C002/1001. The attribute takes the following codes:

929 = pre-notification for arrival import (entry summary declaration)

933 = arrival notification import

830 = pre-notification for arrival export (exit summary declaration EXS)

833 = export arrival notification
In PLDA, the exit summary declaration is called a pre-notification. This system function handles the
registration of the EXS ( + modification). It corresponds with [A2] DGTaxud process CO1A (SUM) –
PROCESS EXIT SUMMARY DECLARATION AT OFFICE OF LODGEMENT. This includes the following
process step:

CO1A0501(SUM) Register Declaration
The following codes are used for handling different transactions on the EXS:

UCG2104 Register Maritime Summary Declaration and Prenotification when Function Code = 9

UCG2105 Modify Maritime Summary Declaration and Prenotification when Function Code = 5

UCG2106 Cancel Maritime Summary Declaration and Prenotification when Function Code = 3
1.1.3 Sequence Diagram
1.1.3.1.1
Core flow
Following figure displays the core flow process in which an Exit Summary Declaration is successfully
submitted and the export movement is presented at the declared Office of Exit for immediate leave from
the European Union customs Territory.
: Person Lodging SD
: Office of Lodgement
Actual : Office of Exit
: Trader (Carrier) at Exit
: Local Authority at Exit
1: E_EXS_DAT (IE615)
2: C_EXS_SND (IE601)
3: E_EXS_ACK (IE628)
4: E_ARR_EXT (IE507)
5: E_EXT_REL (IE525)
6: E_EXT_NOT (IE590)
Figure 1: Presentation and Immediate Leave
The process starts when the Person lodging the Summary Declaration submits from his/her premises an
Exit Summary Declaration (E_EXS_DAT) in the form of an IE615 message to the Office of Lodgement.
After a successful validation check where no inconsistencies are detected of the received message at the
Office of Lodgement, the Trader is notified for the acceptance of the Exit Summary Declaration via an
E_EXS_ACK message (IE628). Upon the confirmation that the Exit Summary Declaration was accepted,
the Trader may proceed with the actual movement of the consignment towards the declared Office of
Exit. If the Office of Lodgement is different than the declared Office of Exit, the provided Exit Summary
Declaration record including the risk analysis results is communicated to the declared Office of Exit via a
C_EXS_SND message (IE601) and the state at the Office of Lodgement is set to “Registered”. As a
consequence, the declared Office of Exit is informed about the upcoming arrival of the consignment.
Upon the arrival of the goods at the Office of Exit, the Trader at Exit submits an arrival notification via an
E_ARR_EXT (IE507) message requesting the goods to leave immediately the European Union customs
Territory. After the successful validation of the message by the Office of Exit, the Customs Officer taking
into account the Risk Indicator decides not to control the goods. An E_EXT_REL (IE525) message is sent
notifying the Trader at Exit that the goods are allowed to immediate leave. After the goods have exited the
Local Authority at Exit indicates the fact to the Office of Exit via an E_EXT_NOT (IE590) message so the
movement can be considered as exited.
1.1.3.1.2
Declaration Rejected
Figure 2 displays the process in which the Exit Summary Declaration (IE615) is rejected by the Office of
Lodgement.
: Person Lodging SD
: Office of Lodgement
Declared : Office of Exit
1: E_EXS_DAT (IE615)
2: E_EXS_REJ (IE616)
Figure 2: Exit Summary Declaration Rejected
The process starts when the Person lodging the Summary Declaration submits from his/her premises an
Exit Summary Declaration (E_EXS_DAT) in the form of an IE615 message to the Office of Lodgement.
The validation check at the Office of Lodgement is not successful as inconsistencies or functional errors
are detected and thus the incoming Exit Summary Declaration is rejected. The Trader is notified via the
return of an E_EXS_REJ message (IE616), including the reason of the rejection. No further process or
message exchange is taking place for this scenario.
1.1.3.1.3
EXS Amendment Accepted
Following figure displays the process of the presentation of the anticipated consignment at the declared
Office of Exit followed by an amendment to the Exit Summary Declaration.
Person or Representative at Exit :
Person Lodging SD
: Office of Lodgement
Actual : Office of Exit
: Trader (Carrier) at Exit
: Local Authority at Exit
1: E_EXS_DAT (IE615)
2: E_EXS_ACK (IE628)
3: C_EXS_SND (IE601)
4: E_EXS_AMD (IE613)
5: E_EXS_AAC (IE604)
6: E_ARR_EXT (IE507)
7: E_EXT_REL (IE525)
8: E_EXT_NOT (IE590)
Figure 3: EXS Amendment Accepted
The process starts identically to that of Core flow scenario. Prior the arrival of the goods at the Exit and
the submission by the Trader at Exit of the arrival notification via an E_ARR_EXT (IE507) message, the
Person lodging the Summary Declaration or his predefined (in the Exit Summary Declaration)
representative at Exit, submits an amendment of the Exit Summary Declaration via an E_EXS_AMD
(IE613) message. The Office of Exit after checking the validity of the amendment and if the movement is
in an appropriate state, accepts the amendment of the Exit Summary Declaration via an E_EXS_ACC
(IE604) message. As the Customs Officer after taking into account the Risk Indicator decides not to
control the goods, the Trader at Exit is informed via an E_EXT_REL (IE525) message that the goods are
either allowed to immediate leave or to be stored prior their exit.
1.1.3.1.4
Amendment Rejected
Following figure displays the process in which an amendment is rejected by the Office of Exit.
Person or Representative at Exit :
Person Lodging SD
: Office of Lodgement
: Trader (Carrier) at Exit
Actual : Office of Exit
: Local Authority at Exit
1: E_EXS_DAT (IE615)
2: C_EXS_SND (IE601)
3: E_EXS_ACK (IE628)
4: E_EXS_AMD (IE613)
5: E_EXS_ARJ (IE605)
6: E_EXS_AMD (IE613)
7: E_EXS_AAC (IE604)
8: E_ARR_EXT (IE507)
9: E_EXT_REL (IE525)
10: E_EXT_NOT (IE590)
Figure 4: Amendment Rejected
The process starts identically to that of EXS Amendment Accepted scenario (1.1.3.1.3). However, in this
scenario upon the submission of the amendment by the Person lodging the Summary Declaration or his
predefined (in the Exit Summary Declaration) representative at Exit via an E_EXS_AMD (IE613)
message, the Office of Exit rejects the amendment as invalid. The reason of the rejection is
communicated to the issuer of the amendment via an E_EXS_ARJ (IE605) message. If the reason of the
rejection is not related to the status of the movement, the state of the movement is set to “Under
Amendment” and the issuer can resubmit a corrected amendment via a new E_EXS_AMD (IE613)
message. When the Office of Exit accepts the amendment, an E_EXS_ACC (IE604) message is sent
notifying the issuer. As the Customs Officer after taking into account the Risk Indicator decides not to
control the goods. The scenario continues as per the Core flow.
1.1.4 Timing constrains
For aviation, the EXS must be submitted 30 min before wheels off.
1.1.5 Messages
The important messages in this MIG are described in the following table:
Id
Description
From
To
Type
IE604
Exit Summary Declaration amendment
accepted
PLDA+
EO
CUSRES D04A
IE605
Exit Summary declaration amendment
rejected
PLDA+
EO
CUSRES D04A
IE613
Exit Summary Declaration Amendment
request
EO
PLDA+
CUSCARD04A
IE615
Exit Summary declaration
EO
PLDA+
CUSCARD04A
IE616
Exit summary declaration rejected
PLDA+
EO
CUSRES D04A
IE628
Exit summary declaration accepted & MRN
PLDA+
EO
CUSRES D04A
1.1.6 Exceptions & comments
An EXS is not required in the following cases:

Goods that are covered by export declarations in accordance with articles 231 & 233

Goods that are part of personal luggage of travelers

Goods for which an oral declaration is accepted in accordance with articles 226, 227 en 229, lid
2;
This means that the EXS will not have to be sent in almost 95% of all cases because:

A valid export declaration exists

The monetary value of the goods is below the threshold ( articles 226,227 and 229)
1.2
Functional message structure
1.3.1 Design principle
The following has to be taken into account to physically implement the new messages:

At the minimum, the mandatory fields of the IE specification [A2] have to be mapped to the
destination format ( XML, EDIFACT, CARGOIMP).

When sending, optional fields of the IE specification [A2] can be disregarded by the Trader, the
central system will not reject messages with missing optional fields.

When receiving, the Trader will not reject messages with missing optional fields of the IE
specification [A2]

Obviously, the mandatory fields of the XML, EDIFACT & CARGOIMP have to be implemented.
The official PLDA specifications have to be followed to interpret which values to assign to these
mandatory fields.
1.2.1 Primary message
1.2.1.1
Message structure
The primary message is the EXS aka IE615 which is the original pre-notification for export. Message
structure is described below:
EXPORT OPERATION 1 x R
TRADER Consignor (Box 2) 1 x O
Rule 804
Rule 10
Rule 11
1x
TRADER Consignee (Box 8) 1 x O
PERSON Lodging the summary declaration
TRADER Representative 1 x O Rule 857
ITINERARY
99 x C Cond 570
R
Rule 879
GOODS ITEM
999 x R
TRADER Consignor (ex Box 2) 1 x O
TRADER Consignee (ex Box 8) 1 x O
CONTAINERS (Box 31) 99 x O
PACKAGES (Box 31) 99 x C Cond 577
PREVIOUS ADMINISTRATIVE REFERENCES (Box 40)
PRODUCED DOCUMENTS/CERTIFICATES (Box 44)
CUSTOMS OFFICE of Lodgement
CUSTOMS OFFICE of Exit (Box 29)
SEALS ID (Box D)
99 x O
Rule 10
Rule 11
COMMODITY Code (box 33)
9x
99 x
1x
1x
EXPORT OPERATION
LRN
Total number of items (box 5)
Total number of packages (box 6)
Commercial Reference Number (box 7)
R
R
O
C
an..22
n..5
n..7
an..70
Location code (box 30)
Location of goods (box 30)
Location of goods_LNG
R
O
C
an..17
an..35
a2
Rule 105
Cond 567
Rule 876
Rule 880
Rule 880
Cond 99
1x
O
C
R
R
Customs sub place (box 30)
Total gross mass (box 35)
Specific Circumstance Indicator
Transport charges – Method of payment
Declaration date (box 54)
Declaration place (box 54)
Declaration_place_LNG
O
C
O
O
R
R
O
an..17
n..11,3
a1
a1
n8
an..35
a2
Rule 880
Cond581
TRADER Consignor
TIN (box 2)
Name (box 2)
Street and number (box 2)
Country (box 2)
Postcode (box 2)
City (box 2)
NAD_LNG
O
R
R
R
R
R
O
an..17
an..35
an..35
a2
an..9
an..35
a2
TRADER Consignee
TIN (box 8)
Name (box 8)
Street and number (box 8)
Country (box 8)
Postcode (box 8)
City (box 8)
NAD_LNG
O
R
R
R
R
R
O
an..17
an..35
an..35
a2
an..9
an..35
a2
PERSON Lodging the summary declaration
TIN (Box 14)
Name (box 14)
Street and number (box 14)
Country (box 14)
Postcode (box 14)
City (box 14)
NAD_LNG
R
O
O
O
O
O
C
an..17
an..35
an..35
a2
an..9
an..35
a2
TRADER Representative
TIN
Name
Street and number
Country
Postcode
City
NAD_LNG
R
O
O
O
O
O
C
an..17
an..35
an..35
a2
an..9
an..35
a2
ITINERARY
Country of routing code
R
a2
GOODS ITEM
Commercial Reference Number (ex box 7)
C
an..70
Textual Description (box 31)
Textual_Description_LNG
Item Number (Box 32)
O
C
R
Gross Mass (box 35)
UN dangerous goods code (ex box 44)
Transport charges – Method of payment
C
O
C
an..280
a2
Cond 99
n..5
Rule 5
Rule 7
n..11,3 Cond 580
n4
a1
Cond 576
TRADER Consignor
TIN (ex box 2)
O
an..17
Cond 99
Cond 567
Rule 876
Name (ex box 2)
Street and number (ex box 2)
Country (ex box 2)
Postcode (ex box 2)
City (ex box 2)
NAD_LNG
R
R
R
R
R
O
an..35
an..35
a2
an..9
an..35
a2
TRADER Consignee
TIN (ex box 8)
Name (ex box 8)
Street and number (ex box 8)
Country (ex box 8)
Postcode (ex box 8)
City (ex box 8)
NAD_LNG
O
R
R
R
R
R
O
an..17
an..35
an..35
a2
an..9
an..35
a2
CONTAINERS
Container numbers (Box 31)
R
an..17
COMMODITY Code
Combined Nomenclature (box 33.1)
R
an..8
PACKAGES
Marks & numbers of Packages (Box 31)
Marks_&_numbers_of_Packages_LNG
Kind of packages (Box 31)
Number of Packages (Box 31)
O
C
R
C
an..42
a2
a2
n..5
Number of Pieces (Box 31)
C
n..5
Cond 61
Rule 20
Cond 61
PREVIOUS ADMINISTRATIVE REFERENCES
Previous Document Category (Box 40)
Previous Document Type (Box 40)
Previous Document Reference (Box 40)
Previous_Document_Reference_LNG
Complement of information (Box 40)
Complement_of_information_LNG
R
R
R
R
O
C
a1
an..6
an..35
a2
an..26
a2
Cond 99
PRODUCED DOCUMENTS/CERTIFICATES
Document Type (Box 44)
Document Reference (Box 44)
Document_Reference_LNG
Complement of information (Box 44)
Complement_of_information_LNG
R
R
R
O
C
an..4
an..35
a2
an..26
a2
Rule 800
Cond 99
CUSTOMS OFFICE of Lodgement
Reference Number
R
an8
CUSTOMS OFFICE of Exit
Reference Number (Box 29)
R
an8
SEALS ID
Seals Identity (box D)
Seals_Identity_LNG
R
O
an..20
a2
Rule 881
Cond 585
Cond 99
Conditions and rules are described in detail in [A2]. Applicable codes for certain fields can be found in
[A3].
1.2.1.2
Field explanations
The explanation of the different fields in the message structure is given in the table below, but only for
non-trivial data fields:
EXPORT OPERATION
LRN
Total number of items (box 5)
Total number of packages (box 6)
Local Reference number provided by the declarant of the EXS unique
identifying the EXS
Obvious
Obvious
Commercial Reference Number (box 7)
Location code (box 30)
Location of goods (box 30)
Location of goods_LNG
Customs sub place (box 30)
Total gross mass (box 35)
Location code for the location of the goods.
not used
not used
not used
Obvious
Specific Circumstance Indicator
Regulation 1875/2006, Annex 30A.
Possible values for AES/ECS:
A = Postal and express consignments
B = Ship and aircraft supplies
E = Authorised economic operators
Transport charges – Method of payment
Declaration date (box 54)
Declaration place (box 54)
Declaration_place_LNG
TRADER Consignor
TIN (box 2)
Name (box 2)
Street and number (box 2)
Country (box 2)
Postcode (box 2)
City (box 2)
NAD_LNG
TRADER Consignee
TIN (box 8)
Name (box 8)
Street and number (box 8)
Country (box 8)
Postcode (box 8)
City (box 8)
NAD_LNG
PERSON Lodging the summary declaration
See also Annex 38 Implementing Provisions (Box 47, last column)
Common code values for AES/ECS:
A = Payment in cash
B = Payment by credit card
C = Payment by cheque
D = Other (e. g. direct debit to agent's cash account)
E = Deferred or postponed payment
F
Obvious
Obvious
Obvious
Obvious
EORI TIN
Obvious
Obvious
Obvious
Obvious
Obvious
Obvious
Obvious
EORI TIN
Obvious
Obvious
Obvious
Obvious
Obvious
Obvious
Trader responsible for declaring the EXS
TIN (Box 14)
Name (box 14)
Street and number (box 14)
Country (box 14)
Postcode (box 14)
City (box 14)
NAD_LNG
TRADER Representative
TIN
Name
Street and number
Country
Postcode
City
NAD_LNG
ITINERARY
Country of routing code
GOODS ITEM
Commercial Reference Number (ex box 7)
EORI TIN
Obvious
Obvious
Obvious
Obvious
Obvious
Obvious
Obvious
EORI TIN
Obvious
Obvious
Obvious
Obvious
Obvious
Obvious
Textual Description (box 31)
Textual_Description_LNG
Item Number (Box 32)
Text describing the goods
Gross Mass (box 35)
UN dangerous goods code (ex box 44)
Transport charges – Method of payment
TRADER Consignor
TIN (ex box 2)
Name (ex box 2)
Street and number (ex box 2)
Country (ex box 2)
Postcode (ex box 2)
City (ex box 2)
NAD_LNG
TRADER Consignee
TIN (ex box 8)
Name (ex box 8)
Street and number (ex box 8)
Country (ex box 8)
Postcode (ex box 8)
City (ex box 8)
NAD_LNG
CONTAINERS
Container numbers (Box 31)
COMMODITY Code
Combined Nomenclature (box 33.1)
Obvious
PACKAGES
Marks & numbers of Packages (Box 31)
Marks_&_numbers_of_Packages_LNG
Kind of packages (Box 31)
Number of Packages (Box 31)
Number of Pieces (Box 31)
PREVIOUS ADMINISTRATIVE REFERENCES
Previous Document Category (Box 40)
Previous Document Type (Box 40)
Obvious
Obvious
EORI TIN
Obvious
Obvious
Obvious
Obvious
Obvious
Obvious
Obvious
EORI TIN
Obvious
Obvious
Obvious
Obvious
Obvious
Obvious
Container number
Not to be used
Not to be used
Not to be used
Previous Document Reference (Box 40)
Previous_Document_Reference_LNG
Complement of information (Box 40)
Complement_of_information_LNG
PRODUCED DOCUMENTS/CERTIFICATES
Document Type (Box 44)
Document Reference (Box 44)
Document_Reference_LNG
Complement of information (Box 44)
Complement_of_information_LNG
CUSTOMS OFFICE of Lodgement
Reference Number
CUSTOMS OFFICE of Exit
Reference Number (Box 29)
SEALS ID
Seals Identity (box D)
Seals_Identity_LNG
1.3.1.1.1
Not to be used
Not to be used
Not to be used
Not to be used
Not to be used
Not to be used
1875 annex 30 bis requirements
The following table describes the requirements for data attributes from a legal point of view, namely from
reference [A14]. The table below is valid for the following mode of transport:
1 = Sea transport
2 = Rail transport
3 = Road transport
4 = Air transport
5 = Postal consignment
7 = Fixed transport installations
8 = Inland waterway transport
9 = Own propulsion
As a matter of fact, the Specific Circumstance Indicator, with following possible values, can be used by
the trader lodging the ENS to indicate specific transport like B:

A Postal and express consignments

B Ship and aircraft supplies

C Road mode of transport

D Rail mode of transport

E Authorised economic operators
The indication of the specific circumstance has impact on the set of attributes that are required or not (
refer to [A14]. Considering the mapping between transport mode and the circumstance indicator, it is
clear that only values B & E of the circumstance indicator cannot be derived from transport mode. When
AEO is in place, we also don’t need the value E of the circumstance indicator.
The following table is derived from [A14] annex 30 bis Table 1: data element requirements for ENS in the
case of air & sea transport:
Item
Nr
1
2
Data attribute
Number of items
Unique consignment reference number
Comments
Required without exception
Required without exception = LRN
3
Transport document number
Alternative to UCR [2]. So when element 2 is provided,
then the transport document number is not necessary
SAD Box
5
7
44
4
5
6
7
8
9
Consignor
Person lodging the summary declaration
Consignee
Country(ies) of routing codes
Office of Exit
Location of Goods
Required either on header or on item level
Required on header
Only when different from element 5
This information is to be provided to the extent known
Required without exception
Required without exception
Goods description
it is a plain language description that is precise enough for
Customs services to be able to
identify the goods. General terms (i.e. “consolidated”,
“general cargo” or “parts”) cannot be accepted. A list of
such
general terms will be published by the Commission. It is
not necessary to provide this information where the
Commodity code is provided.
31
Type of packages (code)
Number of packages
Code specifying the type of package as provided for in
Annex 38 for SAD Box 31 (UN/ECE Recommendation 21
Annex VI)
Required
31
31
Shipping marks
Equipment identification number, if containerised
Goods item number
Free form description of the marks and numbers on
transport units or packages.
This information shall only be provided for packaged
goods where applicable
Required if applicable
Required
31
31
32
16
17
18
Commodity code
Gross mass (kg)
UN Dangerous Goods code
first four digits of the CN code; It is not necessary to
provide this information where
the goods description is provided.
Required
This element shall only be provided where it is relevant
19
20
21
22
Seal number
Transport charges method of payment code
Declaration date
Signature/Authentication
The identification numbers of the seals affixed to the
transport equipment, where applicable
This information is to be provided only where available.
Required
Required
Other specific circumstance indicator
A Postal and express consignments
B Ship and aircraft supplies
C Road mode of transport
D Rail mode of transport
E Authorised economic operators
This element needs to be provided only where the benefit
of a special circumstance other than those referred to
under Table 1 is requested by the person lodging the
summary declaration.
This element does not need to be provided where it can
be deduced automatically and unambiguously from other
data elements provided by the trader.
10
11
12
13
14
15
23
The required data elements for other transport modes are described in [A14] annex 30 bis Table 2 , 3
and 4. Table 5 in [A14] annex 30bis described the required data elements for reduced data set for AEO’s.
2
14
8
33
35
54
54
1.2.1.3
Mapping to XML
The XML mapping is done according to the mapping rules in [A5]. Taking into account that the mapping is
performed in two stages, i.e. functional message structure -> technical message structure -> XML, the
mapping is as follows:

IE615 EXS
Data group / element
XML tag
EXPORT OPERATION
LRN
Total number of items (box 5)
Total number of packages (box 6)
Commercial Reference Number (box 7)
Location code (box 30)
Total gross mass (box 35)
Specific Circumstance Indicator
Transport charges – Method of payment
Declaration date (box 54)
Declaration place (box 54)
Declaration_place_LNG
TRADER Consignor
TIN (box 2)
Name (box 2)
Street and number (box 2)
Country (box 2)
Postcode (box 2)
City (box 2)
NAD_LNG
TRADER Consignee
TIN (box 8)
Name (box 8)
Street and number (box 8)
Country (box 8)
Postcode (box 8)
City (box 8)
NAD_LNG
PERSON Lodging the summary declaration
TIN (Box 14)
Name (box 14)
Street and number (box 14)
Country (box 14)
Postcode (box 14)
City (box 14)
NAD_LNG
TRADER Representative
TIN
Name
Street and number
Country
Postcode
City
NAD_LNG
ITINERARY
Country of routing code
GOODS ITEM
Commercial Reference Number (ex box 7)
Textual Description (box 31)
HEAHEA
RefNumHEA4
TotNumOfIteHEA305
TotNumOfPacHEA306
ComRefNumHEA
ArrAgrLocCodHEA62
TotGroMasHEA307
SpeCirIndHEA1
TraChaMetOfPayHEA1
DecDatHEA383
DecPlaHEA394
DecPlaHEA394LNG
TRACONCO1
TINTCO159
NamTCO17
StrAndNumTCO122
CouCO125
PosCodCO123
CitTCO124
NADLNGCO
TRACONCE1
TINCE159
NamCE17
StrAndNumCE122
CouCE125
PosCodCE123
CitCE124
NADLNGCE
PERLODSUMDEC
TINPLD1
NamPLD1
StrAndNumPLD1
CouCodPLD1
PosCodPLD1
CitPLD1
PERLODSUMDECLNG
TRAREP
TINTRE1
NamTRE1
StrAndNumTRE1
CouCodTRE1
PosCodTRE1
CitTRE1
TRAREPLNG
ITI
CouOfRouCodITI1
GOOITEGDS
ComRefNumGIM1
GooDesGDS23
Textual_Description_LNG
Item Number (Box 32)
Gross Mass (box 35)
UN dangerous goods code (ex box 44)
Transport charges – Method of payment
TRADER Consignor
TIN (ex box 2)
Name (ex box 2)
Street and number (ex box 2)
Country (ex box 2)
Postcode (ex box 2)
City (ex box 2)
NAD_LNG
TRADER Consignee
TIN (ex box 8)
Name (ex box 8)
Street and number (ex box 8)
Country (ex box 8)
Postcode (ex box 8)
City (ex box 8)
NAD_LNG
CONTAINERS
Container numbers (Box 31)
COMMODITY Code
Combined Nomenclature (box 33.1)
PACKAGES
Marks & numbers of Packages (Box 31)
Marks_&_numbers_of_Packages_LNG
Kind of packages (Box 31)
Number of Packages (Box 31)
Number of Pieces (Box 31)
PRODUCED DOCUMENTS/CERTIFICATES
Document Type (Box 44)
Document Reference (Box 44)
Document_Reference_LNG
CUSTOMS OFFICE of Lodgement
Reference Number
CUSTOMS OFFICE of Exit
Reference Number (Box 29)
SEALS ID
Seals Identity (box D)
Seals_Identity_LNG

GooDesGDS23LNG
IteNumGDS7
GroMasGDS46
UNDanGooCodGDI1
MetOfPayGDI12
TRACONCO2
TINCO259
NamCO27
StrAndNumCO222
CouCON225
PosCodCO223
CitCO224
NADLNGGTCO
TRACONCE2
TINCE259
NamCE27
StrAndNumCE222
CouCE225
PosCodCE223
CitCE224
NADLNGGICE
CONNR2
ConNumNR21
COMCODGODITM
ComNomCMD1
PACGS2
MarNumOfPacGS21
MarNumOfPacGS21LNG
KinOfPacGS23
NumOfPacGS24
NumOfPieGS25
PRODOCDC2
DocTypDC21
DocRefDC23
DocRefDCLNG
CUSOFFLON
RefNumCOL1
CUSOFFEXIEXT
RefNumEXT1
SEAID529
SeaIdSEAID530
SeaIdSEAID530LNG
IE613 EXS Amendment request
The IE613 message is mapped the same way as the IE615 message with the following rules:
R115
The IE structure used for the amendment is the same as E_DEC_DAT/E_EXP_DAT/E_EXS_DAT
/E_ENS_DAT/E_SUD_DAT with some changes:
replace LRN by MRN R an18,
replace ‘Declaration date’ by ‘Date of amendment’ R n8,
replace ‘Declaration place’ by ‘Amendment place’ R an..35
The IE transmits a complete amended declaration data, this means that all data groups and attributes are
transmitted and not only those that are amended.
R853
The amendment request must be sent to the Member State where the Office of Exit (declared in the initial
version of the Exit summary declaration) is located
R856
No amendment allowed for 'PERSON lodging the summary declaration'.
R870
If the amendment request is sent by a 'Trader Representative' the 'Trader Representative. TIN becomes =R.
If it is sent by the Person lodging the Exit/Entry summary declaration, it is = 'O'.
1.2.1.4
Mapping to EDIFACT
The EXS message can be implemented for Maritime transport by means of the CUSCAR D04A message
[A12]. In this section, we provide the description of how the different fields have to be filled in the
CUSCAR message (for fields that are not mentioned, [A12] has to be followed).
In the UNH header of the message we set the following:

If BGM/C002/1225=9 than UNH[1].S009.0057 = ‘615’

If BGM/C002/1225=5 or 3 than UNH[1].S009.0057 = ‘613’

BGM/C002/1001 = "830"

BGM/C002/1225 = {"3" , "5", "9"} // cancel=3, original =9, modif=5
Following specific fields in the CUSCAR D04A have to be set for the EXS:
EXPORT OPERATION
LRN
Total number of items (box 5)
Total number of packages (box 6)
Commercial Reference Number (box 7)
BGM->1004 (when UNH[1].S009.0057 = ‘613’, then this field must contain
the MRN received in response to the original IE615)
SG7->CNT->6069 = 8
SG7->CNT->6066
The total number of packages is equal to the sum of all ‘Number of packages’
+ all ‘Number of pieces’ + a value of ‘1’ for each declared ‘bulk’.
SG8->RFF->1153 = “BM”
SG8->RFF->1154
Total gross mass (box 35)
SG8->LOC->3227 (cfr. reference A12)
SG8->LOC->3225
SG7->CNT->6069 = 9
SG7->CNT->6066
Specific Circumstance Indicator
Knowing this is CUSCAR, we don’t need types A,C,D.
We can derive type E from :
SG7->CNI->1373 = “24”
Location code (box 30)
Transport charges – Method of payment
Declaration date (box 54)
Declaration place (box 54)
Declaration place_LNG
TRADER Consignor
TIN (box 2)
Name (box 2)
Street and number (box 2)
Country (box 2)
Postcode (box 2)
City (box 2)
TRADER Consignee
TIN (box 8)
Name (box 8)
Street and number (box 8)
Country (box 8)
SG8->CPI->4215
UNB->S004
Derive from Person lodging the summary declaration
not mapped
SG11->NAD->3035 = “CZ”
SG11->NAD->3039 (format: Country code + “005” + Company number)
SG11->NAD->3036
SG11->NAD->3042
SG11->NAD->3207
SG11->NAD->3251
SG11->NAD->3164
SG11->NAD->3035 = “CN”
SG11->NAD->3039 (format: Country code + “005” + Company number)
SG11->NAD->3036
SG11->NAD->3042
SG11->NAD->3207
Postcode (box 8)
City (box 8)
PERSON Lodging the summary declaration
TIN (Box 14)
Name (box 14)
Street and number (box 14)
Country (box 14)
Postcode (box 14)
City (box 14)
SG11->NAD->3251
SG11->NAD->3164
SG2-NAD->3035 = ‘AG’
SG2->NAD->3039 (format: Country code + “005” + Company number)
SG2->NAD->3036
SG2->NAD->3042
SG2->NAD->3207
SG2->NAD->3251
SG2->NAD->3164
SG2-NAD->3035 = ‘AE’
TRADER Representative
TIN
Name
Street and number
Country
Postcode
City
ITINERARY
Note: AE code to be added to [A13]
SG2->NAD->3039 (format: Country code + “005” + Company number)
SG2->NAD->3036
SG2->NAD->3042
SG2->NAD->3207
SG2->NAD->3251
SG2->NAD->3164
For segment group 9:
Country of routing code
GOODS ITEM
Textual Description (box 31)
Textual_Description_LNG
Item Number (Box 32)
Gross Mass (box 35)
UN dangerous goods code (ex box 44)
CONTAINERS
Container numbers (Box 31)
COMMODITY Code
Combined Nomenclature (box 33.1)
PACKAGES
Marks & numbers of Packages (Box 31)
Kind of packages (Box 31)
Number of Packages (Box 31)
Number of Pieces (Box 31)
PRODUCED DOCUMENTS
Document Type (box 44)
Document Reference (box 44)
Document Reference LNG
CUSTOMS OFFICE of Lodgement
Reference Number
CUSTOMS OFFICE of Exit
Reference Number (Box 29)
SEALS ID
Seals Identity (box D)
Seals_Identity_LNG
LOC
// provide full itinerary starting from first entry, all
subsequent ports and the final destination
“92” = routing (only Iso Alfa II country codes)
“9” = place/port of loading )
“11” = place/port of discharge
SG14->FTX->4451 = “AAA”
SG14->FTX->4440
SG14->FTX->3453
SG14->GID->1496
SG14->MEA->6311 = “WT”
SG14->MEA->6313 = “G”
SG14->MEA->6314
SG14->DGS->7124
SG14->SGP->8260
SG14->CST->7361
SG14->PCI->7102
SG14->GID->7065
SG14->GID->7224
SG14->FTX->4451 = “PKG” (packaging information)
SG14->FTX->4441 = “PCS”
SG14->FTX->4440 = number of pieces (format “n..5”)
SG8->RFF->1153
SG8->RFF->1154
not mapped
LOC->3227 = “88”
LOC->3225
SG9->LOC->3227 = ‘79’
SG9->LOC->3225
SG5->SEL->9308
1.2.1.5
Mapping to CARGOIMP
XML Taxud version will be used to support this.
1.2.2 Response messages
1.2.2.1.1


Message Structure
IE628 EXS accepted
EXPORT OPERATION 1 x R
CUSTOMS OFFICE of Export
TRADER Declarant
1 xR
1x
R
EXPORT OPERATION
LRN
MRN
Declaration Acceptance date
R
R
R
an..22
an18
n8
CUSTOMS OFFICE of Export
Reference Number
R
an8
TRADER Declarant
TIN (Box 14)
Name (Box 14)
Street and number (Box 14)
Country (Box 14)
Postcode (Box 14)
City (Box 14)
R
O
O
O
O
O
an17
an..35
an..35
a2
an..9
an..35
R
O
C
n8
an..350
a2
Cond 99
IE616 EXS rejected
E_EXS_DAT
1 x R Rule 123
EXPORT OPERATION 1 x R
E_EXS_DAT
EXPORT OPERATION
Declaration rejection date
Declaration rejection reason
Declaration_rejection_reason_LNG

IE604 EXS Amendment accepted
EXPORT OPERATION 1 x R
CUSTOMS OFFICE Actual Office of Exit
PERSON Lodging the summary declaration
TRADER Representative 1 x C Cond 552
EXPORT OPERATION
MRN
1x
1x
R
an18
R
C
Date of amendment
Amendment acceptance date
R
R
n8
n8
CUSTOMS OFFICE Actual Office of Exit
Reference Number
R
an8
PERSON Lodging the summary declaration
TIN (Box 14)
Name (Box 14)
Street and number (Box 14)
Country (Box 14)
Postcode (Box 14)
City (Box 14)
R
O
O
O
O
O
an17
an..35
an..35
a2
an..9
an..35
TRADER Representative
TIN
Name
Street and number
Country
Postcode
City
R
O
O
O
O
O
an17
an..35
an..35
a2
an..9
an..35
 IE605 EXS Amendment rejected
E_EXS_AMD
1 x O Rule 123
EXPORT OPERATION 1 x R
CUSTOMS OFFICE Actual Office of Exit
PERSON Lodging the summary declaration
TRADER Representative 1 x C Cond 553
1x
1x
E_EXS_AMD
EXPORT OPERATION
MRN
Date of amendment
Amendment rejection date
Amendment rejection motivation code
Amendment rejection motivation text
Amendment_rejection_motivation_text_LNG
C
C
R
C
C
C
an18
n8
n8
n1
an..350
a2
CUSTOMS OFFICE Actual Office of Exit
Reference Number
R
an8
PERSON Lodging the summary declaration
TIN (Box 14)
Name (Box 14)
Street and number (Box 14)
Country (Box 14)
Postcode (Box 14)
City (Box 14)
R
O
O
O
O
O
an17
an..35
an..35
a2
an..9
an..35
TRADER Representative
Cond 124
Cond 124
Cond 124
Cond 310
Cond 99
C
C
TIN
Name
Street and number
Country
Postcode
City
1.2.2.1.2
R
O
O
O
O
O
an17
an..35
an..35
a2
an..9
an..35
Mapping to XML
The XML mapping is done according to the mapping rules in [A5]. Taking into account that the mapping is
performed in two stages, i.e. functional message structure -> technical message structure -> XML, the
mapping is as follows:

IE628 EXS accepted
Data group / element
XML tag
EXPORT OPERATION
LRN
MRN
Declaration Acceptance date
HEAHEA
RefNumHEA4
DocNumHEA5
DecRegDatHEA1
CUSTOMS OFFICE of Export
Reference Number
CUSOFFLON
RefNumCOL1
TRADER Declarant
TIN (Box 14)
Name (Box 14)
Street and number (Box 14)
Country (Box 14)
Postcode (Box 14)
City (Box 14)
PERLODSUMDEC
TINPLD1
NamPLD1
StrAndNumPLD1
CouCodPLD1
PosCodPLD1
CitPLD1

IE616 EXS rejected
Data group / element
XML tag
EXPORT OPERATION
Declaration rejection date
Declaration rejection reason
Declaration_rejection_reason_LNG
FUNCTIONAL ERROR
Error type
Error pointer
Error reason
Original attribute value
HEAHEA
DecRejDatHEA159
DecRejReaHEA252
DecRejReaHEA252LNG
FUNERRER1
ErrTypER11
ErrPoiER12
ErrReaER13
OriAttValER14

IE604 EXS Amendment accepted
Data group / element
XML tag
EXPORT OPERATION
MRN
HEAHEA
DocNumHEA5
Date of amendment
Amendment acceptance date
AmdDatHEA599
AmeAccDatHEA602
CUSTOMS OFFICE Actual Office of Exit
Reference Number
ACEACE
RefNumACE1
PERSON Lodging the summary declaration
TIN (Box 14)
Name (Box 14)
Street and number (Box 14)
Country (Box 14)
Postcode (Box 14)
City (Box 14)
PERLODSUMDEC
TINPLD1
NamPLD1
StrAndNumPLD1
CouCodPLD1
PosCodPLD1
CitPLD1
TRADER Representative
TIN
Name
Street and number
Country
Postcode
City
TRAREP
TINTRE1
NamTRE1
StrAndNumTRE1
CouCodTRE1
PosCodTRE1
CitTRE1

IE605 EXS Amendment rejected
Data group / element
XML tag
EXPORT OPERATION
MRN
Date of amendment
Amendment rejection date
Amendment rejection motivation code
Amendment rejection motivation text
Amendment_rejection_motivation_text_LNG
HEAHEA
DocNumHEA5
AmdDatHEA599
AmeRejDatHEA603
AmeRejMotCodHEA604
AmeRejMotTexHEA605
AmeRejMotTexHEA605LNG
CUSTOMS OFFICE Actual Office of Exit
Reference Number
ACEACE
RefNumACE1
PERSON Lodging the summary declaration
TIN (Box 14)
Name (Box 14)
Street and number (Box 14)
Country (Box 14)
Postcode (Box 14)
City (Box 14)
PERLODSUMDEC
TINPLD1
NamPLD1
StrAndNumPLD1
CouCodPLD1
PosCodPLD1
CitPLD1
TRADER Representative
TIN
Name
Street and number
Country
Postcode
City
TRAREP
TINTRE1
NamTRE1
StrAndNumTRE1
CouCodTRE1
PosCodTRE1
CitTRE1
FUNCTIONAL ERROR
Error type
Error pointer
Error reason
Original attribute value
FUNERRER1
ErrTypER11
ErrPoiER12
ErrReaER13
OriAttValER14
1.2.2.1.3
Mapping to EDIFACT
The EXS response messages can be implemented for Maritime transport by means of the CUSRES
D04A message which is described in detail in [A6].
In this section, it is described how PLDA will reply to the CUSCAR message in case of EXS.
SRC represents the original message (CUSCAR) to which the CUSRES is a reply.
The following table describes the 604 Amendment accepted:
CUSRES 04A Field
Value
UNH/0065
“CUSRES”
UNH/0052
SRC.UNH/0052
UNH/0054
UNH/0051
UNH[1].S009.0057
SRC.UNH/0054
SRC.UNH/0051
= 604 ( Amendment accepted)
BGM/1001
830
BGM/1004
TransactionID
GR3/RFF/1153
“MR”
GR3/RFF/1154
SRC.BGM/1004
BGM/1225
44
Comment
Unique reference number generated by
PLDA
Message accepted and completely
processed
The following table describes the 605 Amendment rejected:
CUSRES 04A Field
Value
Comment
UNH/0065
“CUSRES”
UNH/0052
SRC.UNH/0052
UNH/0054
UNH/0051
UNH[1].S009.0057
SRC.UNH/0054
SRC.UNH/0051
= 605 (Amendment rejected)
BGM/1001
830
BGM/1004
TransactionID
GR3/RFF/1153
“MR”
GR3/RFF/1154
SRC.BGM/1004
BGM/1225
48
Message accepted but not processed
GR4/ERP/1049
1
Error on heading level
GR4/ERP/9166
GR4/ERP/1050
GR4/ERC/9321
Exception.segment
Exception.segment.seqnr
Exception.errorCode
Unique reference number generated by
PLDA.
GR4/ERC/1131
109
Customs indicator
GR4/ERC/3055
147
Belgian customs
GR12/ERP/1049
{12,14}
Code qualifying a reference.
12 = article level
14 = item level within the article
GR12/ERP/1052
Goods item number
Identifies a reference.
If 1049/14 -> sequence number of the
item
GR12/ERP/9166
Exception.segment
Segment name
GR12/ERP/1050
Exception.segment.seqnr
Sequence number of the segment
GR4/ERC/9321
Exception.errorCode
GR4/ERC/1131
109
Customs indicator
GR4/ERC/3055
147
Belgian customs
The following table describes the 628 EXS accepted:
CUSRES 04A Field
Value
Comment
UNH/0065
“CUSRES”
UNH/0052
SRC.UNH/0052
UNH/0054
UNH/0051
UNH[1].S009.0057
SRC.UNH/0054
SRC.UNH/0051
= 628 ( EXS accepted)
BGM/1001
830
BGM/1004
TransactionID
GR3/RFF/1153
“MR”
GR3/RFF/1154
SRC.BGM/1004
Original LRN
BGM/1225
44
Message accepted and completely processed
SG6/DOC/1001
“704”
Code identifying the doc as Bill of lading
SG6/DOC/1004
SRC.SG8->RFF->1154
Bill of lading numbers of the ENS
SG6/RFF/1153
“MRN”
Segment to be added to [A13]
SG6/RFF/1154
MRN number
Generated by PLDA for each B/L
MRN
The following table describes the 616 EXS rejected:
CUSRES 04A Field
Value
UNH/0065
“CUSRES”
UNH/0052
SRC.UNH/0052
UNH/0054
UNH/0051
UNH[1].S009.0057
SRC.UNH/0054
SRC.UNH/0051
= 616 (EXS rejected)
BGM/1001
830
BGM/1004
TransactionID
Comment
Unique reference number generated by
PLDA.
GR3/RFF/1153
“MR”
GR3/RFF/1154
SRC.BGM/1004
BGM/1225
48
Message accepted but not processed
GR4/ERP/1049
1
Heading
GR4/ERP/9166
GR4/ERP/1050
GR4/ERC/9321
Exception.segment
Exception.segment.seqnr
Exception.errorCode
GR4/ERC/1131
109
Customs indicator
GR4/ERC/3055
147
Belgian customs
GR12/ERP/1049
{12,14}
Code qualifying a reference.
12 = article level
14 = item level within the article
GR12/ERP/1052
Goods item number
Identifies a reference.
If 1049/14 -> sequence number of the
item
GR12/ERP/9166
Exception.segment
Segment name
GR12/ERP/1050
Exception.segment.seqnr
Sequence number of the segment
GR4/ERC/9321
Exception.errorCode
GR4/ERC/1131
109
Customs indicator
GR4/ERC/3055
147
Belgian customs
1.2.2.2
Mapping to CARGOIMP
Please refer to XML Taxud version.
1.4
Technical message handling
The technical handling of the messages ( headers, signature, connectivity) will not change in MASP.be.
Therefore, all documentation [A9] and [A10] are still relevant.