Rules

R007

The IE consists of top level Data Groups. Each top level Data Group has its own Data Group ACTION which attributes apply to the top level Data Group and its subsequent sub Data Groups.
The sender of the IE will always (in case of Create, Update, Invalidate and Delete) send all values of the occurrence.

The <Operation> attribute is used to indicate what action is applied to the occurrence in the IE. Its value is: “C” (create), “U” (update), “I”(Invalidate), “D” (Delete).

The <Activation date> indicates when the operation will become applicable for the specific occurrence.

For the D (Delete) operation the <Activation date> shall be the current date of the request.

R026

The possible values of <Operator Role Code> are:

1 = Allowed to practise direct delivery
2 = Allowed to leave empty the destination fields according to Article 22 of Directive 2020/262

The couplings <Operator Type / Operator Role Code> are as follows:

A / B	C	D	E
Allowed to practise direct delivery	X	X
Allowed to leave empty the destination fields according to Article 22 of Directive 2020/262	X		X

Where: A: OPERATOR TYPE
B: OPERATOR ROLE
C: AUTHORISED WAREHOUSE KEEPER
D: REGISTERED CONSIGNEE
E: REGISTERED CONSIGNOR

R027

An existing identifier (Excise Number) <Trader Excise Number> in the set of <TRADER AUTHORISATION>.

R028

The format of <Time To …> or <Maximum Duration of …> is expressed in days, months or years, with the format P999, where:

“P” is a letter in (“D” = Day, “M” = Month or “Y” = Year)
“999” is a three digits number

R030

The format of <ARC> is defined as per the below structure:

Field / Content / Field type / Examples
1 / Year / Numeric 2 / “05”
2 / Identifier of the MS where the e-AD/e-SAD was initially submitted / Alphabetic 2 / “ES”
3 / Nationally assigned, unique code / Alphanumeric 15 (digits and capital letters) / “7R19YTE17UIC8J4”
4 / Type of Movement / Alphanumeric 1 / “P”
5 / Check Digit / Numeric 1 / “9”

Field 1 is last two digits of year of formal acceptance of movement.
Field 2 is taken from the list of <NATIONAL ADMINISTRATIONS>.
Field 3 must be filled with a unique identifier per EMCS movement. The way this field is used is under MSAs" responsibility, but each EMCS movement must have a unique number.
Field 4 gives an identifier for the type of the movement. If <Submission Message Type> is “3”, then value “P” must be used
Field 5 gives the Check Digit for the whole ARC (see section “Design Principles” of the DDNEA main document), that will help detect an error when keying the ARC.

Note: Field 4 gives an identifier for the type of the movement. If <Submission Message Type> is “3”, then value “P” must be used (the introduced logic is applicable for ARCs generated after 01/01/2023. Any ARCs generated before 01/01/2023 are associated with a Duty Suspension movement, regardless of the alphanumeric character specified in ‘Field 4’ of the ARC.

R032

The format of <Office Reference Number> is defined as per below:

Field / Content / Field type / Examples
1 / Identifier of the MS to which the Office belongs / Alphabetic 2 / “IT”
2 / National number of the Customs Office/ Alphanumeric 6 (digits and capital letters) / “0830AB”

Field 1 is taken from the list of <NATIONAL ADMINISTRATIONS>.
Field 2 has to be freely filled with a 6 character alphanumeric code. The 6 characters allow MSAs, where necessary, to define a hierarchy of customs offices (COL).

R038

An existing identifier (Excise Number) <Trader Excise Number> in the set of <TRADER AUTHORISATION> or <Temporary Authorisation Reference> in the set of <TEMPORARY AUTHORISATION>.

R040

The format of <Temporary Authorisation Reference > is defined as per below:

Field / Content / Field type / Examples
1 / Identifier of the MS where the temporary authorisation reference is registered/ Alphabetic 2 / “PL”
2 / Nationally assigned, unique code / Alphanumeric 11 (digits and capital letters) / “0830AB ”

Field 1 is taken from the list of <NATIONAL ADMINISTRATIONS> of the Member States.
The format of the temporary authorisation reference is the same as the format of the trader excise number.

R044

For TRADER Consignor

An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>
The <Operator Type Code> of the referred <TRADER> must be:
For Duty Suspension movements:

“Authorised warehouse keeper”; OR
“Registered consignor”;

For Duty Paid movements
“Certified consignor;

An existing identifier <Temporary Authorisation Reference> in the set of <TEMPORARY AUTHORISATION>
The <Operator Type Code> of the referred <TRADER> must be:
For Duty Paid movements:
“Temporary Certified Consignor”.

For TRADER Place of dispatch

For Duty Suspension movements:
An existing identifier <Tax Warehouse Reference> (Excise Number in SEED).

Note: The distinction between Duty Paid B2B and Duty Suspension movements should be derived from the ARC structure or based on the <Submission Message Type> in case of IE815, where the ARC is not available.

R045

The possible values of <Trader Identification> are described in the following table:

IF Destination Type Code==1 - Destination - Tax warehouse
THEN
TRADER CONSIGNEE. Trader Identification -> Excise number (1)
TRADER Place of Delivery.Trader Identification -> Tax Warehouse Reference (Excise Number) (5)

IF Destination Type Code==2 - Destination - Registered consignee
THEN
TRADER CONSIGNEE. Trader Identification -> Excise number (2)
TRADER Place of Delivery.Trader Identification -> Any identification (*)

IF Destination Type Code==3 - Destination - Temporary registered consignee
THEN
TRADER CONSIGNEE. Trader Identification ->Temporary authorisation reference (4)
TRADER Place of Delivery.Trader Identification ->Any identification (*)

IF Destination Type Code==4 - Destination - Direct delivery
THEN
TRADER CONSIGNEE. Trader Identification -> Excise number (3)
TRADER Place of Delivery.Trader Identification -> (Does not apply)

IF Destination Type Code==5 - Destination - Exempted consignee
THEN
TRADER CONSIGNEE. Trader Identification -> (Does not apply)
TRADER Place of Delivery.Trader Identification -> Any identification (*)

IF Destination Type Code==6 - Destination - Export
THEN
TRADER CONSIGNEE. Trader Identification -> VAT number (optional)
TRADER Place of Delivery.Trader Identification -> (The data group <TRADER Place of Delivery> does not exist)

IF Destination Type Code==9 - Destination - Certified Consignee
THEN
TRADER CONSIGNEE. Trader Identification -> Excise Number (6)
TRADER Place of Delivery.Trader Identification -> Any identification (*)

IF Destination Type Code==10 - Destination - Temporary Certified Consignee
THEN
TRADER CONSIGNEE. Trader Identification -> Temporary Authorisation Reference (7)
TRADER Place of Delivery.Trader Identification -> Any identification (*)

IF Destination Type Code==11 - Destination-Return to the place of dispatch of the consignor, for a Duty Paid B2B movement
THEN
New TRADER CONSIGNEE. Trader Identification -> Excise Number (8) or Temporary Authorisation Reference (9)

(1) The operator type of the consignee is “Authorised warehouse keeper”. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>;
(2) The operator type of the consignee is “Registered consignee”. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>;

(3) The operator type of the consignee is either “Authorised warehouse keeper” or “Registered consignee” An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>;
(4) An existing <Temporary Authorisation Reference> in the set of <TEMPORARY AUTHORISATION> with Operator Type Code “Temporary Registered Consignee”;
(5) An existing identifier <Tax Warehouse Reference> in the set of <TAX WAREHOUSE>;
(6) The operator type of the consignee is “Certified consignee”. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>;
(7) An existing <Temporary Authorisation Reference> in the set of <TEMPORARY AUTHORISATION> with Operator Type Code “Temporary Certified Consignee”;
(8) The operator type of the consignee is “Certified consignor”. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>;
(9) An existing <Temporary Authorisation Reference> in the set of <TEMPORARY AUTHORISATION> with Operator Type Code “Temporary Certified Consignor”.

(*) For the place of delivery, “Any identification” means: a VAT number or any other identifier; it is optional.
When the value of the “TRADER CONSIGNEE.Trader Identification” and “TRADER Place of Delivery.Trader Identification” is any of the following: “Excise Number” or “Tax Warehouse Reference” or “Temporary Authorisation Reference”, then the structure of the value should comply with the structure of the “Trader Excise Number/Tax Warehouse Reference”’ as defined in rule R070.

R051

Valid value is an existing <Country Code> in the list of <COUNTRY>, with the exception of country codes that refer to the EU Member States. Thus, an existing <Country Code> in the list of <COUNTRY> (with the exception of <Country Code> “GR”), but not in the list of <NATIONAL ADMINISTRATIONS> apart from <National Administration Code> “GB”.

R054

The format of <Journey Time> is expressed in hours or in days, with the format P99, where:

“P” is a letter in (“H” = Hours or “D” = Day)
“99” is a two digits number
If P is “H” then the number is less or equal to 24
if P is “D” then the number is less or equal to the possible values of <Maximum Journey Time> per <Transport Mode Code>.

R058

Refers to <Body Record Unique Reference> of the e-AD/e-SAD Body of the associated e-AD/e-SAD and must be unique within the message.

R059

The <Sequence Number> is an automatically generated sequential number, set to 1 at initial submission of the e-AD/e-SAD, and then incremented of 1 upon each change of destination.

R060

The <Body Record Unique Reference> must be a unique sequential number starting from 1

R070

The <Trader Excise Number> must be unique in the list of <TRADER AUTHORISATION>.
The <Tax Warehouse Reference> must be unique in the list of <TAX WAREHOUSE>“.

The format of <Trader Excise Number> or <Tax Warehouse Reference> is defined as per the below structure:

Field / Content / Field type / Examples
1 / Identifier of the MS where the economic operator or tax warehouse is registered / Alphabetic 2 / "PL”
2 / Nationally assigned, unique code / Alphanumeric 11 / “2005764CL78”

Field 1 is taken from the list of <NATIONAL ADMINISTRATIONS>.
Field 2 must be filled with a unique identifier for the Excise registered operator (authorised warehouse keeper, registered consignee, registered consignor, certified consignor, and certified consignee) or for the tax warehouse. The way this value is assigned falls under the MSAs” responsibility, but each Excise registered operator (authorised warehouse keeper, registered consignee, registered consignor, certified consignor, and certified consignee) and each tax warehouse must have a unique number.

R071

The format of <Event Report Number> is defined as per the below structure:

Field 1 is taken from the list of <NATIONAL ADMINISTRATIONS>
Field 2 must be filled with a unique identifier per report. The way this field is used is under MSAs" responsibility, but each report must have a unique number. It is possible, but not mandatory, that it contains the year when the report was initially submitted (as suggested in the example).
Field 3 gives the Check Digit for the whole identifier, that will help detect an error when keying this identifier.

R072

The possible <Submitter Identification> contains:

value of <Trader Excise Number>

R083

The format of <Follow Up Correlation ID> is defined as per the below structure:

Field / Content / Field type / Examples
1 / Year / Numeric 2 / “05”
2 / Identifier of the MS where the message was initially submitted / Alphabetic 2 / “ES”
3 / Free nationally assigned, code / Alphanumeric 21 / ARC
4 / Complement / Alphanumeric 3 / “123”

Field 1 is last two digits of year.
Field 2 is taken from the list of <NATIONAL ADMINISTRATIONS>.
Field 3 must be filled with a nationally assigned identifier. In certain case, for the Follow Up Correlation ID it can be an ARC.
Field 4 gives a complement to field 3 to make together a unique identifier (for example, in the case of Follow Up Correlation ID where several follow-up messages deal with the same ARC).

R086

The <Operation> attribute is used to indicate what action is applied: “C” (create), “D” (delete).

In case of “updates”, the Data Group “SYSTEM UNAVAILABILITY” to be updated will be first deleted and then (re-)created.

R091

Must be less than or equal to the <Observed Shortage>

R093

The format of <MS of Submission Event Report Reference> is:

2 alphabetic characters: Identifier of the Member State of Submission of the event report
followed by a nationally assigned, unique code

R098

An Event Report IE840 exists in the system (including the case that it is encapsulated in a received IE934) having the same <Event Report Number> and <ARC> with that of the submitted message.

R100

A valid MRN or SAD Number confirmed against Customs data, according to the Customs case.

MRN = Movement Reference Number
SAD = Single Administrative Document

R103

A Control Report IE717 exists in the system (including the case that it is encapsulated in a received IE934) having the same <Control Report Reference> and <ARC> with that of the submitted message.

R109

The format of <Control Report Reference> is defined as per the below structure:

Field / Content / Field type / Examples
1 / Identifier of the MS where the report is validated / Alphabetic 2 / “ES”
2 / Nationally assigned, unique code / Alphanumeric 13 (digits and capital letters) / “2005YTE17UIC2”
3 / Check Digit / Numeric 1 / “9”
Field 1 is taken from the list of <NATIONAL ADMINISTRATIONS>.
Field 2 must be filled with a unique identifier per report. The way this field is used is under MSAs" responsibility, but each report must have a unique number. It is possible, but not mandatory, that it contains the year when the report was initially submitted (as suggested in the example).
Field 3 gives the Check Digit for the whole identifier, that will help detect an error when keying this identifier (see section “Design Principles” of the DDNEA main document).

R156

An existing <Request Reason Code> in the list of <REQUEST REASON>

R194

Refers to <Body Record Unique Reference> of an e-AD Body
AND
must be unique per “E-AD Split Details”

R196

In case of standard submission (i.e. <Message Type> is “Standard submission”), the possible values of <Destination Type Code> are:

1 = Destination - Tax warehouse;
2 = Destination - Registered consignee;
3 = Destination - Temporary registered consignee;
4 = Destination - Direct delivery;
5 = Destination - Exempted consignee;
6 = Destination - Export;
8 = Unknown destination (consignee unknown).
In case of ‘Duty Paid’ submission (i.e. <Message Type> is “Duty Paid B2B”), the possible values of <Destination Type Code> are:
9 = Destination - Certified consignee;
10 = Destination - Temporary certified consignee;

R204

The “Tax Warehouse Reference” shall be one of the <TAX WAREHOUSE.Reference of Tax Warehouse> such that there exists at least one Active version having its Validity Interval intersecting the Validity Interval of the <TRADER AUTHORISATION>, after the Activation Date of the latter, by at least one day.

R205

The “Tax Warehouse Reference” shall be the same as one of the <(USING) TAX WAREHOUSE.Reference of Tax Warehouse> within one or more <TRADER AUTHORISATION> data groups of “Authorised Warehouse Keeper” type satisfying also Rule 204.

R206

The value of the <Operator Type Code> Data Item cannot be changed after the creation of the TRADER AUTHORISATION.

R207

The <Excise Products Category Code> of the <Excise Product Code> must not exist inside the same <TRADER AUTHORISATION> or <TAX WAREHOUSE>.

R208

The <Excise Products Category Code> must be unique in the list of <EXCISE PRODUCTS CATEGORY> inside the same <TRADER AUTHORISATION> or <TAX WAREHOUSE>.

R209

The <Excise Product Code> must be unique in the list of <EXCISE PRODUCTS> inside the same <TRADER AUTHORISATION>, <TAX WAREHOUSE>, or <TEMPORARY AUTHORISATION>.

R211

If the excise product code is anything but S500
THEN
the CN code must be taken from the corresponding list of <CN CODE>.

R212

IF <TEMPORARY AUTHORISATION.Small Wine Producer> is present and is True
THEN the <Excise Product Code> must be either ‘W200’ or ‘W300’

R213

A Control Report IE717 exists in the system (including the case that it is encapsulated in a received IE934) having the same <Control Report Reference>with that of the submitted message. In addition if the ARC is provided in the submitted message then it coincides with the ARC of the referenced Control Report IE717.

R214

An existing identifier <Office Reference Number> in the set of <OFFICE>. The Office must belong to the same MSA to which the entity (economic operator, tax warehouse or temporary authorisation) is registered.

R215

IF <MOVEMENT GUARANTEE.Guarantor Type Code> is “No guarantee is provided according to Article 17.2 and 17.5(b) of Directive 2020/262”
THEN
<Excise Product Code> must be an energy product
(Note:

When the message under validation is the IE815 or the IE801, the excise product code used in the current validation is that contained in the IE815 or the IE801 respectively;
When the message under validation is the IE813, the excise product code used in the current validation is that contained in the last IE801 or in the last, if any, IE818 that indicated partial refusal.

R216

IF <MOVEMENT GUARANTEE.Guarantor Type Code> is “No guarantee is provided according to Article 17.2 and 17.5(b) of the Directive 2020/262”
THEN
<Transport Mode Code> must be “Sea Transport” or “Fixed transport installations”
(Note:

When the message under validation is the IE815 or the IE801, the Guarantor Type Code used in the current validation is that contained in the IE815 or the IE801 respectively
When the message under validation is the IE813, the Guarantor Type Code used in the current validation is that contained:
– in the IE813, in case the Guarantor Type Code is given in this message
Otherwise
– in the last IE801 or the last, if any, IE813 that indicated change of place of delivery.

R217

The format of <MV Correlation ID> is defined as per the below structure:
Field / Content / Field type / Examples
1 / Year / Numeric 2 / “05”
2 / Identifier of the MS where the message was initially submitted / Alphabetic 2 / “ES”
3 / Free nationally assigned, code / Alphanumeric 21
4 / Complement / Alphanumeric 3 / “123”

Field 1 is last two digits of year.
Field 2 is taken from the list of <NATIONAL ADMINISTRATIONS>.
Field 3 must be filled with a nationally assigned identifier.
Field 4 gives a complement to field 3 to make together a unique identifier.

R218

An existing <Country Code> in the list of <COUNTRY> and except <Country Code> “GR” for which the code “EL” is used.

R219

The <Gross Mass> must be equal or higher than <Net Mass>

R224

An existing identifier (Excise Number) <Trader Excise Number> in the set of <TRADER AUTHORISATION> or <TEMPORARY AUTHORISATION>

R225

A VAT number or any other National number

R229

For each occurrence of the Data Group <ACTIONS Requested> in the IE722 message, there exists a corresponding occurrence of the Data Group <ACTIONS Result> in the submitted message with the same <Movement Verification Action Code>, <ACO_Complementary Information> (when applicable), <ACO_Complementary Information_LNG> (when applicable), <Image of Document> (when applicable) and <Box Number> (when applicable)

R230

The Activation Date must be equal to or greater than the Modification Date.

R231

The <Body Record Unique Reference> must be unique within the message and must refer to a <Body Record Unique Reference> of the e-AD/e-SAD Body of the associated e-AD/e-SAD for which shortages or excesses have been declared.

R232

The value of the Data Item must be greater than zero.

R233

An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>
The <Operator Type Code> of the referred <TRADER> must be:

“Authorised warehouse keeper” OR “Registered consignor” for <Temporary Registered Consignee> authorisations OR;
“Certified Consignor” for <Temporary Certified Consignee> authorisations OR;
“Certified Consignee” for <Temporary Certified Consignor> authorisations.
In addition, the Member State of the <TRADER AUTHORISATION> must be different from the Member State the <TEMPORARY AUTHORISATION> is registered for.

An existing identifier <Trader Excise Number> in the set of <TEMPORARY AUTHORISATION>
The <Operator Type Code> of the referred <TRADER> must be:

“Temporary Certified Consignor” for <Temporary Certified Consignee> authorisations OR;
“Temporary Certified Consignee” for <Temporary Certified Consignor> authorisations.
In addition, the Member State of the linked <TEMPORARY AUTHORISATION> must be different from the Member State the <TEMPORARY AUTHORISATION> is registered for.

R235

The validation of the Check Digit field shall be performed at the time the <ARC> or the <Event Report Number> or the <Control Report Reference> is generated

R236

An existing identifier <Office Reference Number> in the Customs Office List (COL)

R237

The value of the Data Item must be greater than or equal to 0.5 and less than or equal to 100.

R238

The value must be the same as the corresponding value in the IE723 message(s) for the specific request.

R239

When more than one IE723 messages exist for a specific request, the value must be the same in all IE723 messages.

R240

IF <Follow Up Correlation ID> matches with <Follow Up Correlation ID> in a request message AND <National Case Reference Identifier> is present in the request message
THEN
<National Case Reference Identifier> must be equal to the value of <National Case Reference Identifier> in the request message.

R241

IF <MV Correlation ID> matches with <MV Correlation ID> in a request message AND <National Case Reference Identifier> is present in the request message

THEN
<National Case Reference Identifier> must be equal to the value of <National Case Reference Identifier> in the request message

R248

The format of <Maximum Journey Time> is expressed in hours or in days, with the format P99, where:

“P” is a letter in (“H” = Hours or “D” = Day)
“99” is a two digits number
If P is “H” then the number is less or equal to 24
if P is “D” then the number is less or equal to the possible values of <Maximum Journey Time> per <Transport Mode Code> as described in the following table:

Transport ModeCode	Maximum Journey Time
0 - Other	D45
1 - Sea Transport	D45
2 - Rail transport	D35
3 - Road transport	D35
4 - Air transport	D20
5 - Postal consignment	D30
7 - Fixed transport installations	D15
8 - Inland waterway transport	D35

Note 1: The value “Other” refers to multimode transport (where there is unload and reload of cargo) and covers the cases of Group Consigments, Export, Split and Change of destination.
Note 2: In case of export, the journey time is the estimated duration of the journey up to the exit of the customs territory of the Union.

R249

If the value of < Primary Criterion Type Code> Data Item is “46= Type of Transport”, then an existing <Transport Mode Code> in the list of BC67 -TRANSPORT MODES shall be used

R251

In case the “Number of Packages” is set to “0”, then there should exist at least one “PACKAGE” (i.e. either within the same <E-AD BODY> or within other <E-AD BODY> occurrences of the same message) with the same “Shipping Marks” and “Number of Packages” with value greater than “0”.

R255

Provide the latest sequence number of the related e-AD/e-SAD.

R258

The applicable ‘Destination Type Codes’ for Duty Suspension movements are:
‘1 - Destination-Tax Warehouse’
‘2 - Destination-Registered Consignee’
‘3 - Destination-Temporary Registered Consignee’
‘4 - Destination-Direct Delivery’
‘5 - Destination-Exempted Consignee’
‘6 - Destination-Export’
‘8 - Unknown destination (consignee unknown)’

The applicable ‘Destination Type Codes’ for Duty Paid B2B movements are:
‘9 - Destination-Certified Consignee’
‘10 - Destination-Temporary Certified Consignee’
‘11 - Destination-Return to the place of dispatch of the Consignor’

R259

The applicable ‘Destination Type Codes’ for Duty Paid B2B movements are:
‘9 - Destination-Certified Consignee’
‘10 - Destination-Temporary Certified Consignee’
‘11 - Destination - Return to the place of dispatch of the consignor for a Duty Paid B2B movement’

R260

The applicable ‘Origin Type Codes’ for Duty Suspension movements are:
‘1 - Origin-Tax Warehouse’
‘2 - Origin-Import’

The applicable ‘Origin Type Codes’ for Duty Paid B2B movements are:
‘3 - Origin-Duty Paid’

R261

The applicable ‘Submission Type Codes’ for Duty Suspension movements are:
‘1 - Standard Submission’

The applicable ‘Submission Type Codes’ for Duty Paid B2B movements are:
‘3 - Submission for Duty Paid B2B’

R262

The applicable ‘Reminder Message Type Codes’ for Duty Suspension movements are:
‘1 - Reminder message at expiry of time to change destination’
‘2 - Reminder message at expiry of time to send the report of receipt/export’
‘3 - Reminder message at expiry of time to give destination information (Article 22 of Directive 2020/262)’

The applicable ‘Reminder Message Type Codes’ for Duty Paid B2B movements are:
‘1 - Reminder message at expiry of time to change destination’
‘2 - Reminder message at expiry of time to send the report of receipt/export’

R263

The applicable ‘Excise Product Codes’ for Duty Suspension movements are:

all codes listed in the ‘CL - Excise Product’ codelist, except from ‘S600 - Completely denatured alcohol, falling within Article 20 of Directive 92/83/EEC, being alcohol which has been denatured and fulfils the conditions to benefit from the exemption provided for in Article 27(1)(a) of that Directive’.

The applicable ‘Excise Product Codes’ for Duty Paid B2B movements are:

all codes listed in the ‘Excise Product’ codelist

R264

The Excise Product Code ‘S600’ is only applicable to the ‘Certified Consignor’ and ‘Certified Consignee’ authorisation types.

R265

The possible values of <Operator Role Code> are:

1 = Allowed to practise direct delivery
2 = Allowed to leave empty the destination fields according to Article 22 of Directive 2020/262

The couplings <Operator Type / Operator Role Code> are as follows:

1 = Allowed to practise direct delivery–> Applicable for ‘Authorised Warehouse Keeper’ and ‘Registered Consignee’
2 = Allowed to leave empty the destination fields according to Article 22 of Directive 2020/262 –> Applicable for ‘Authorised Warehouse Keeper’ and ‘Registered Consignor’

R266

The format of <Global Excise Trader Identifier> is defined as per the below structure:
Field / Content / Field type / Examples
1 / Identifier of the MS where the economic operator or tax warehouse is registered / Alphabetic 2 / “PL”
2 / Nationally assigned, unique code / Alphanumeric 20 / “2005764CL78232ERW123”

Field 1 is taken from the list of <NATIONAL ADMINISTRATIONS>.
Field 2 must be filled with a unique identifier that will allow linking of the different authorisation types (authorised warehouse keeper, registered consignee, registered consignor, certified consignor, and certified consignee) of a single Excise economic operator.

R267

For “delete” operations of “Tax Warehouse” records, the deleted “tax warehouse” must not be linked to an “Authorised Warehouse Keeper”.

R268

For “delete” operations of “Authorised Warehouse Keeper” records, the deleted “Authorised Warehouse Keeper” must not be the sole keeper of a tax warehouse, i.e. the deletion of the “Authorised Warehouse Keeper” must not result to an “orphan” tax warehouse.

R269

For “delete” operations of ‘Registered Consignors’ or ‘Authorised Warehouse Keepers’, there should be no ‘Temporary Registered Consignees’ associated to the deleted economic operators.
Similarly, for “delete” operations of “Certified Consignors” or “Certified Consignees”, there should be no “Temporary Certified Consignees” or “Temporary Certified Consignors” respectively associated to the deleted economic operators.

R270

For authorisations of United Kingdom (Northern Ireland) (i.e. as derived from the structure of the “Trader Excise Number>, <Reference of Tax Warehouse> or <Temporary Authorisation reference>), the applicable postcode must start with “BT”.

R271

For information exchanges from United Kingdom (Northern Ireland), the Trader Excise Number of either consignor or consignee or direct delivery or Tax Warehouse Reference must be related to Northern Ireland (i.e. Member State to be “XI” as derived from its structure).

R272

For information exchanges from United Kingdom (Northern Ireland), the Temporary Authorisation Reference must be related to Northern Ireland (i.e. Member State to be “XI” as derived from its structure).

R273

For information exchanges from United Kingdom (Northern Ireland), the ARC must be related to Northern Ireland (i.e. Member State to be “XI” as derived from its structure).

R274

For information exchanges from United Kingdom (Northern Ireland), the Event Report Number / Control Report Reference must be related to Northern Ireland (i.e. Member State to be “XI” as derived from its structure).

R275

For information exchanges from United Kingdom (Northern Ireland), the Follow Up Correlation ID/MV Correlation ID must be related to Northern Ireland (i.e. Member State to be “XI” as derived from its structure).

R276

For information exchanges from United Kingdom (Northern Ireland) (i.e. Northern Ireland being the sending Member State), the <Status Request Message Type> = “2-Movement History Request” is not allowed.

TR0104

The HEADER Data Group is required for rejecting IE717, IE801, IE802, IE803, IE807, IE810, IE813, IE818, IE819, IE837, IE861, IE871, IE904, IE905 messages, except for the cases where the data item <Administrative Reference code> is syntactically invalid or missing in the afore-mentioned messages.
It must not be present for rejecting all other messages (refer to Section “Design Principles - Exception Handling - Syntactic layer” of DDNEA for EMCS Phase 4 Main Document).

TR9001

Action identification is identification for the occurrence within the Information Exchange Message.
Although the content of the Action identification can be chosen freely by the producer of the change,
it must be unique within the scope of the transaction.
This is a technical attribute added to identify the occurrence in the enclosing transaction (message)
and intended to enable unique definition of error cases.

TR9080

Within the “REFERENCE SYNCHRONISATION” Data Group, the “Period from date” must be prior or equal
to the “Period to date”.

TR9110

The value of this attribute shall be:

0: for retrieval (or missing in order to enable backward compatibility);
1: for extraction;
2: for non-invalidated records.

TR9115

In case that an extraction is requested, the “Period from date” and/or the “Period to date” fields will
be used to request occurrences valid in the specified period. On the contrary, in case retrieval is
requested, the “Period from date” and/or the “Period to date” fields will be used to request occurrences
modified and published in the specified period.

TR9120

The value of this field shall be “1” in case a Status Synchronisation Request is requested. The value of this attribute shall be “2” in case a Movement History Request is requested. If it is not used a Status Request/Response will be performed.

TR9121

The field is Required for:

response messages (IE821, IE905, IE881 and IE934);
refusal messages (IE702, IE704, IE714, IE906, and IE917); and
the resubmitted lost/delayed messages as a result of status synchronisation request (IE801, IE803, IE807, IE810, IE813, IE818, IE819, IE829, IE839, IE881, IE905).

It does not apply for requests and one way messages.