FOD FIN Belgium and IBM Confidential - © FOD FIN Belgium and
IBM Corporation 2008
MASP.be
Message Implementation Guide
Report of Receipt
IE818
Author: Maarten Moens
Owner: FOD FIN D&A
Customer: FOD FIN Belgium
FOD FIN Belgium and IBM Confidential
Document:
Path:
533582039
D:\533582039.doc
Owner:
Subject:
FOD FIN D&A
Message Implementation Guide Report of Receipt IE818
Date: 05/06/2008
Version: 0.02
Status: Draft
Page 1 of 15
FOD FIN Belgium and IBM Confidential - © FOD FIN Belgium and
IBM Corporation 2008
MASP.be
Document History
Revision History
Date of this revision: 05/06/2008
Revision
Number
00.01
0.02
Date of next revision
Revision Summary of Changes
Date
20/05/08 Initial version created
5/6/08
Internal IBM review
(date)
Changes
marked
(N)
(N)
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
Johan Leemans
Project Manager D&A EMCS
Jean-francois Leys
Business Analyst IBM EMCS
Stefan Van Assche
Lead Architect IBM EMCS
Carla Martens
QA IBM
Frieda Bollaert
Program Manager IBM
Document:
Path:
533582039
D:\533582039.doc
Owner:
Subject:
FOD FIN D&A
Message Implementation Guide Report of Receipt IE818
Date: 05/06/2008
Version: 0.02
Status: Draft
Page 2 of 15
FOD FIN Belgium and IBM Confidential - © FOD FIN Belgium and
IBM Corporation 2008
MASP.be
Contents
1.
Introduction ............................................................................................................. 4
1.1
Purpose ........................................................................................................................................... 4
1.2
References ...................................................................................................................................... 4
1.3
Notation ........................................................................................................................................... 5
1.4
Functional description ..................................................................................................................... 8
1.4.1
Purpose .................................................................................................................................... 8
1.4.2
Process Description ................................................................................................................. 9
1.4.3
Sequence Diagram ................................................................................................................ 10
1.5
Message overview ........................................................................................................................ 11
1.5.1
Primary message ................................................................................................................... 11
1.5.1.1
Message structure .......................................................................................................... 11
1.5.1.2
Field explanations ........................................................................................................... 12
1.5.1.3
Mapping to XML ............................................................................................................. 15
1.5.2
Response messages ............................................................................................................. 15
1.5.2.1
1.6
Refusal Message for Report of Receipt (IE704)............................................................. 15
Technical message structure ........................................................................................................ 15
Document:
Path:
533582039
D:\533582039.doc
Owner:
Subject:
FOD FIN D&A
Message Implementation Guide Report of Receipt IE818
Date: 05/06/2008
Version: 0.02
Status: Draft
Page 3 of 15
FOD FIN Belgium and IBM Confidential - © FOD FIN Belgium and
IBM Corporation 2008
MASP.be
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 IE818 is to describe the way that the
message and its related response message need to be implemented.
1.2 References
This document refers to the following external documents and/or Web sites
Ref.
Reference
Title
Core Business EMCS
ECP1-ESS-FESS-2-SECTION
BUSINESS.doc
Messages EMCS
ECP1-ESS-FESS-Appendix
MESSAGES.doc
A3
Codelists EMCS
ECP1-ESS-FESS-Appendix B-LIST OF CODES.doc
2.13
A4
Design Document EMCS
ECP2-EMCSDEV-DDNEA-v2.15-EN.doc
2.15
A5
XML Mapping
ECP2-EMCSDEV-DDNEA_P2_APP_E_215-EN.pdf
2.15
A6
XML Schemas
EMCS - XML SCHEMAS.zip
??
A1
A2
Document:
Path:
533582039
D:\533582039.doc
Owner:
Subject:
FOD FIN D&A
Message Implementation Guide Report of Receipt IE818
Release
II
CORE 2.13
D-FUNCTIONAL 2.13
Date: 05/06/2008
Version: 0.02
Status: Draft
Page 4 of 15
FOD FIN Belgium and IBM Confidential - © FOD FIN Belgium and
IBM Corporation 2008
MASP.be
1.3 Notation
Acronyms
Description
AAD
Administrative Accompanying Document
API
Application Programming Interface
ARC
AAD Reference Code
BCC
Business Communication Channels
CCN
Common Communication Network
CD
Common Domain
CDEA
Centrally Developed Excise Application
CDIA
CCN/TC Directory Administrator
CLD
Collaboration Diagram
CoA
Confirm on Arrival
CoD
Confirm on Delivery
CONTRL
Syntax and service report XML message
COS
Central Operation Specification
CPT
Central Project Team
CS/MIS
Central Services - Management Information System
CS/RD
Central Services Reference Data
CSI
Common Systems Interface
CSIDD
CCN/CSI Data Descriptor
DDNEA
Design Document for National Excise Applications
DG TAXUD
TAXation and Customs Union DG
DTD
Document Type Definition
EC
European Community
ECP
Excise Computerisation Project
ECS
Export Control System
ELO
Excise Liaison Office
EMCS
Excise Movement and Control System
EMCS-CO
Excise Movement and Control System - Central Operations
ETA
Excise Test Application
EXC
Exception Report
EXP
Expiration Report
FESS
Functional Excise System Specification
FMS
Functional Message Structure
FRS
Fallback and Recovery Specification
FS
Functional Stage
GLT
Glossary of Terms
GMT
Greenwich Mean Time
GSS
Generic Security Services
GUI
Graphical User Interface
HTML
HyperText Markup Language
HTTP
HyperText Transfer Protocol
Document:
Path:
533582039
D:\533582039.doc
Owner:
Subject:
FOD FIN D&A
Message Implementation Guide Report of Receipt IE818
Date: 05/06/2008
Version: 0.02
Status: Draft
Page 5 of 15
FOD FIN Belgium and IBM Confidential - © FOD FIN Belgium and
IBM Corporation 2008
MASP.be
Acronyms
Description
HTTPS
HTTP over SSL
IE
Information Exchange
ISO
International Standards Organisation
IT
Information Technology
KEL
Known Error List
LRN
Local Reference Number
LSO
Local Security Officer
MD5
Message Digest 5
MIME
Multipurpose Internet Mail Extensions
MS
Member State
MSA
Member State Administration
NACK
Non-ACKnowledgement service message
NCTS
New Computerised Transit System
NDEA
Nationally Developed Excise Application
NEA
National Excise Application
ORO
Occasionally Registered Operator
PRO
Permanent Registered Operator
PSS
Phasing and Scope Specification
QoS
Quality of Service
RD
Reference Data
RoR
Report of Receipt
SD
Scope Document
SEED
System for Exchange of Excise Data
SEP
Security Policy
SESS
Security Excise System Specification
SETA
Standard Excise Test Application
SGML
Standard Generalised Markup Language
SMTP
Simple Mail Transfer Protocol
SRO
System Requirements Overview
SSL
Secure Socket Layer
STD
State Transition Diagram
TC
Technical Centre
TCP/IP
Transmission Control Protocol / Internet Protocol
TESS
Technical Excise System Specification
TMS
Technical Message Structure
TSD
Time Sequence Diagram
UC
Use Case
UML
Unified Modelling Language
URI
Universal Resource Identifier
UTF
UCS Transformation Format
VAT
Value Added Tax
VIES
VAT Information Exchange System
WS
Web Service
Document:
Path:
533582039
D:\533582039.doc
Owner:
Subject:
FOD FIN D&A
Message Implementation Guide Report of Receipt IE818
Date: 05/06/2008
Version: 0.02
Status: Draft
Page 6 of 15
FOD FIN Belgium and IBM Confidential - © FOD FIN Belgium and
IBM Corporation 2008
MASP.be
Acronyms
Description
WWW
World Wide Web
XML
Extensible Markup Language
XSD
XML Schema Definition
Document:
Path:
533582039
D:\533582039.doc
Owner:
Subject:
FOD FIN D&A
Message Implementation Guide Report of Receipt IE818
Date: 05/06/2008
Version: 0.02
Status: Draft
Page 7 of 15
FOD FIN Belgium and IBM Confidential - © FOD FIN Belgium and
IBM Corporation 2008
MASP.be
1.4 Functional description
1.4.1 Purpose
Receipt of goods is acknowledged by the consignee submitting a report of receipt stating that the goods
have arrived at destination.
This use case covers all variants of delivery except the exportation of goods, more precisely:
 receipt in a tax warehouse or by a registered consignee;
 receipt by a temporary registered consignee or by an exempted organisation;
 direct delivery.
In each of these cases, it is possible for the consignee to accept the delivery of a part of the goods and to
refuse the other part.
Upon arrival of the goods, the consignee makes an inventory, in particular on excesses and shortages.
He records the results into a report of receipt submitted for validation to the MSA of destination.
When validated, the report of receipt is disseminated to all concerned partners. In the case where the
consignor would not have an access to EMCS (which should be very rare), either the MSA of dispatch
and/or the consignee informs him.
Legally, the receipt of the report of receipt by the consignor has the same value as the return of copy 3 of
the current paper AAD. It is a discharge of the movement or of the accepted part of the goods, subject to:
 payment of duties on non-exempted shortages;
 results of possible further procedures that would ascertain irregularities on which the financial
responsibility of the guarantor would be engaged.
Technically, in EMCS, this discharge will be achieved through the validation of the report of receipt by the
MSA of destination application, which is automatically forwarded to all MSA involved, as well as to the
consignor and the consignee.
Where goods are released for consumption at arrival, payment of duties is subject to national provisions
of the Member State of destination.
It is possible for the consignee to completely refuse the delivery. This does not exempt the consignee
from making a complete report of receipt including, where relevant, assessment of shortages and
excesses. The movement is not discharged and the consignor is expected to change the destination to
allow goods moving to another destination (possibly return to the tax warehouse of dispatch).
Partial refusal is supported by the consignee indicating the refused quantity of each concerned goods
item. The part of the goods that has not been refused nor declared as a shortage is considered accepted
by the consignee. The consignor is expected to change the destination for the part of the consignment
that has been refused. In that case, the movement is only partially discharged.
If the delivery is totally or partially refused, at least one, possibly several reasons must be given. Some
reasons are then a convenient input for Risk Assessment to draw attention of the MSAs on some
particular cases of refusal. The reason may be given either at the most general level (consignment) or at
the sub-record level (goods item).
Document:
Path:
533582039
D:\533582039.doc
Owner:
Subject:
FOD FIN D&A
Message Implementation Guide Report of Receipt IE818
Date: 05/06/2008
Version: 0.02
Status: Draft
Page 8 of 15
FOD FIN Belgium and IBM Confidential - © FOD FIN Belgium and
IBM Corporation 2008
MASP.be
1.4.2 Process Description
The consignee records the results of his inventory into the report of receipt.
Submitting the report of receipt electronically is an obligation.
If the consignee is a temporary registered consignee or an exempted organisation, he submits the
data to be entered in the report of receipt in the way determined by the authorities of his MS.
The submitted information contains in particular the following references:
 ARC of the received consignment;
 if the consignee is an authorised warehouse keeper or a registered consignee, Excise number, name and
address;
 if the consignee is a temporary registered consignee, reference of the temporary authorisation (in the place of
the Excise number), name and address;
 if the consignee is an exempted organisation: name and address;
 code of the competent Excise office at destination;
 if the place of delivery is a separate tax warehouse: Excise number, name and address;
 if the place of delivery is any other place: identifier, name and address;
 date of arrival of goods;
 global indicator: receipt satisfactory or unsatisfactory or receipt refused or receipt partially refused;
 if the global indicator is anything else than "receipt satisfactory", a list of global reasons for unsatisfactory
receipt;
 For each body record (line) for which an anomaly, partial refusal, shortage or excess has been ascertained:





sequential number of the body record;
Excise product code;
observed shortage (negative value) or excess (positive value) of quantity (expressed in the unit associated with the product code);
optionally, and if the global indicator is "partially refused", refused quantity concerning the body record (expressed in the unit
associated with the product code);
if the global indicator is anything else than "receipt satisfactory", an optional (list of) specific reason(s) for unsatisfactory receipt.
The draft report of receipt is sent to the MSA destination application.
Final situation:
The report of receipt is under validation by the MSA destination application; the consignee is waiting for a
positive or negative answer.
If the draft of report of receipt is found invalid, a refusal message is sent back to the consignee or, according to
national provisions, to the Excise officer
Should I combine 2 usecases into one? E.G. the validation of the ROR is a separate usecase, but
requires no interaction from the Consignee…
Document:
Path:
533582039
D:\533582039.doc
Owner:
Subject:
FOD FIN D&A
Message Implementation Guide Report of Receipt IE818
Date: 05/06/2008
Version: 0.02
Status: Draft
Page 9 of 15
FOD FIN Belgium and IBM Confidential - © FOD FIN Belgium and
IBM Corporation 2008
MASP.be
1.4.3 Sequence Diagram
The following sequence gives an overview of the submitting the report of receipt process.
Figure 1: Sequence diagram IE818
The sequential steps are explained in chronological order as follows:
1. When the goods arrive at their destination, the Consignee (trader) acknowledges the receipt of
goods by submitting the draft Report of Receipt (RoR) (IE818) to the MSA destination application
for validation. This RoR will indicate the acceptance of delivery (with or without shortages) or the
(partial) refusal of delivery.
2. Assuming that, the validation process passes successfully, the MSA destination forwards the
validated Report of Receipt (IE818) to the Belgium EMCS application.
3. Finally, the MSA destination application sends back the validated RoR to the Consignee as a
confirmation.
4. As a last step the Belgium EMCS application forwards the delivery notification (IE818) to the
Consignor (trader) to inform him/her for the acceptance/refusal of delivery.
Document:
Path:
533582039
D:\533582039.doc
Owner:
Subject:
FOD FIN D&A
Message Implementation Guide Report of Receipt IE818
Date: 05/06/2008
Version: 0.02
Status: Draft
Page 10 of 15
FOD FIN Belgium and IBM Confidential - © FOD FIN Belgium and
IBM Corporation 2008
MASP.be
1.5 Message overview
1.5.1 Primary message
1.5.1.1 Message structure
The primary message is the IE818 “Report of Receipt” described below:
ATTRIBUTES
EXCISE MOVEMENT e-AAD
TRADER Consignee
TRADER Place of Delivery
OFFICE Place of Delivery - Customs
OFFICE of Destination
REPORT OF RECEIPT
UNSATISFACTORY REASON
REPORT OF RECEIPT Body
UNSATISFACTORY REASON
ATTRIBUTES
Message Type
Date of Validation of Report of Receipt
EXCISE MOVEMENT e-AAD
ARC
TRADER Consignee
Trader Identification
Trader Name
Street And Number
Postcode
City
NAD_LNG
TRADER Place of Delivery
Trader Identification
Trader Name
Street And Number
Postcode
City
NAD_LNG
OFFICE Place of Delivery - Customs
Office Reference Number
OFFICE of Destination
Office Reference Number
REPORT OF RECEIPT
Date of Arrival of Excise Products
Global Conclusion of Receipt
UNSATISFACTORY REASON
Unsatisfactory Reason Code
Complementary Information
Complementary Information_LNG
REPORT OF RECEIPT Body
Body Record Unique Reference
Indicator of Shortage or Excess
Observed Shortage or Excess
Excise Product Code
Refused Quantity
UNSATISFACTORY REASON
Unsatisfactory Reason Code
Document:
Path:
533582039
D:\533582039.doc
Owner:
Subject:
FOD FIN D&A
Message Implementation Guide Report of Receipt IE818
1x
1x
1x
1x
1x
1x
1x
9x
999x
9x
R
R
R
C
C
C
R
C
O
C
R
C
n1
n14
Rule122
Rule003 Cond109
R
an21
Rule030
C
R
R
R
R
R
an..16
an..35
an..65
an..9
an..35
a2
Rule045 Cond010
C
C
C
C
C
C
an..16
an..35
an..65
an..9
an..35
a2
Rule045 Cond074
Cond079
Cond078
Cond078
Cond078
Rule031 Cond002
R
an8
Rule032
R
an8
Rule032
C
R
n8
n..2
Rule001 Cond015
Rule046 Cond119
R
O
C
n1
an..350
a2
Rule154
R
O
C
R
C
n..3
a1
n..15,2
an..4
n..15,2
Rule058
Rule036
R
n1
Rule154
Cond118
Cond118
Cond105
Cond014
Cond014
Rule031
Rule018 Cond002
Cond094
Rule049
Cond095
Date: 05/06/2008
Version: 0.02
Status: Draft
Page 11 of 15
FOD FIN Belgium and IBM Confidential - © FOD FIN Belgium and
IBM Corporation 2008
MASP.be
Complementary Information
Complementary Information_LNG
O
C
an..350
a2
Rule018 Cond002
Conditions and rules are described in detail in [A2]. Applicable codes for certain fields can be found in
[A3].
1.5.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
Segment/field
Description
ATTRIBUTES
Message Type
The possible values of <Message Type> are:
- 1 = Submission
- 2 = Dissemination
Date of Validation of Report of Receipt The format of DateAndTime is 14 digits
:YYYYMMDDHHMMSS (e.g. 20040510103215)
The addressed time is local time.
EXCISE MOVEMENT eAAD
ARC
The format of <ARC> is defined in [A3]
TRADER Consignee
Trader Identification
The possible values of <Trader Identification> are described in
the following table:
Destination Type
Code
1 - Destination Tax warehouse
2 - Destination Registered
consignee
3 - Destination Temporary
registered
consignee
4 - Destination Direct delivery
5 - Destination Exempted
organisation
6 - Destination –
Export
Document:
Path:
533582039
D:\533582039.doc
Owner:
Subject:
FOD FIN D&A
Message Implementation Guide Report of Receipt IE818
TRADER
CONSIGNEE.
Trader
Identification
Excise number (1)
Excise number (2)
TRADER Place of
Delivery.Trader
Identification
Tax Warehouse
Reference (Excise
Number)
Any identification
(*)
Temporary
authorisation
reference
Any identification
(*)
Excise number (3)
(Does not apply)
(Does not apply)
Any identification
(*)
VAT number
(optional)
(The data group
<TRADER Place
of Delivery> does
not exist)
Date: 05/06/2008
Version: 0.02
Status: Draft
Page 12 of 15
FOD FIN Belgium and IBM Confidential - © FOD FIN Belgium and
IBM Corporation 2008
MASP.be
8 - Unknown
destination
(consignee
unknown)
(The data group
<TRADER
CONSIGNEE>
does not exist)
(The data group
<TRADER Place
of Delivery> does
not exist)
(1) The operator type of the consignee is "Authorised warehouse
keeper"
(2) The operator type of the consignee is "Registered
consignee".
(3) The operator type of the consignee is either "Authorised
warehouse keeper" or "Registered consignee"
(*) For the place of delivery, "Any identification" means: a VAT
number or any other identifier; it is optional
Trader Name
Street And Number
Postcode
City
TRADER Place of Delivery
Trader Identification
The possible values of <Trader Identification> are described in
the following table:
Destination Type
Code
1 - Destination Tax warehouse
TRADER
CONSIGNEE.
Trader
Identification
Excise number (1)
2 - Destination Registered
consignee
3 - Destination Temporary
registered
consignee
4 - Destination Direct delivery
5 - Destination Exempted
organisation
6 - Destination –
Export
Excise number (2)
8 - Unknown
destination
(The data group
<TRADER
Document:
Path:
533582039
D:\533582039.doc
Owner:
Subject:
FOD FIN D&A
Message Implementation Guide Report of Receipt IE818
TRADER Place of
Delivery.Trader
Identification
Tax Warehouse
Reference (Excise
Number)
Any identification
(*)
Temporary
authorisation
reference
Any identification
(*)
Excise number (3)
(Does not apply)
(Does not apply)
Any identification
(*)
VAT number
(optional)
(The data group
<TRADER Place
of Delivery> does
not exist)
(The data group
<TRADER Place
Date: 05/06/2008
Version: 0.02
Status: Draft
Page 13 of 15
FOD FIN Belgium and IBM Confidential - © FOD FIN Belgium and
IBM Corporation 2008
MASP.be
(consignee
unknown)
CONSIGNEE>
does not exist)
of Delivery> does
not exist)
(1) The operator type of the consignee is "Authorised warehouse
keeper"
(2) The operator type of the consignee is "Registered
consignee".
(3) The operator type of the consignee is either "Authorised
warehouse keeper" or "Registered consignee"
(*) For the place of delivery, "Any identification" means: a VAT
number or any other identifier; it is optional
Trader Name
Street And Number
Postcode
City
OFFICE Place of Delivery - Customs
Office Reference Number
An existing identifier <Office Reference Number> in the set of
<OFFICE>
OFFICE of Destination
Office Reference Number
An existing identifier <Office Reference Number> in the set of
<OFFICE>
REPORT OF RECEIPT
Date of Arrival of Excise Products
The format of Date is 8 digits : YYYYMMDD (e.g. 20040510)
Global Conclusion of Receipt
The possible values of <Global Conclusion of Receipt> are:
- 1 = Receipt accepted and satisfactory
- 2 = Receipt accepted although unsatisfactory
- 3 = Receipt refused
- 4 = Receipt partially refused
- 11 = Export refused
- 21 = Exit accepted and satisfactory
- 22 = Exit accepted although unsatisfactory
- 23 = Exit refused
UNSATISFACTORY REASON
Unsatisfactory Reason Code
An existing <Unsatisfactory Reason Code> in the list of
<UNSATISFACTORY REASON>
Complementary Information
REPORT OF RECEIPT Body
Body Record Unique Reference
Refers to <Body Record Unique Reference> of an e-AAD Body
AND must be unique within the message.
Indicator of Shortage or Excess
The possible values of <Indicator of Shortage or Excess> are:
- S = Shortage
- E = Excess
Observed Shortage or Excess
Excise Product Code
An existing <Excise Product Code> in the list of <EXCISE
Document:
Path:
533582039
D:\533582039.doc
Owner:
Subject:
FOD FIN D&A
Message Implementation Guide Report of Receipt IE818
Date: 05/06/2008
Version: 0.02
Status: Draft
Page 14 of 15
FOD FIN Belgium and IBM Confidential - © FOD FIN Belgium and
IBM Corporation 2008
MASP.be
PRODUCT> defined in [A3]
Refused Quantity
UNSATISFACTORY REASON
Unsatisfactory Reason Code
An existing <Unsatisfactory Reason Code> in the list of
<UNSATISFACTORY REASON>
Complementary Information
1.5.1.3 Mapping to XML
The functional mapping of IE818 message fields to XML Tags is defined in [A5]. The technical XML
message formatting is defined [A6] in the file ie818.xsd.
1.5.2 Response messages
1.5.2.1 Refusal Message for Report of Receipt (IE704)
Please refer to the MIG describing message IE704
1.6 Technical message structure
Please refer to SECTION VI TECHNICAL MESSAGE STRUCTURE in [A4]
Document:
Path:
533582039
D:\533582039.doc
Owner:
Subject:
FOD FIN D&A
Message Implementation Guide Report of Receipt IE818
Date: 05/06/2008
Version: 0.02
Status: Draft
Page 15 of 15