This document is an excerpt from the EUR-Lex website
Document d557750f-9e68-11ee-b164-01aa75ed71a1
Commission Implementing Regulation (EU) 2018/574 of 15 December 2017 on technical standards for the establishment and operation of a traceability system for tobacco products (Text with EEA relevance)
Consolidated text: Commission Implementing Regulation (EU) 2018/574 of 15 December 2017 on technical standards for the establishment and operation of a traceability system for tobacco products (Text with EEA relevance)
Commission Implementing Regulation (EU) 2018/574 of 15 December 2017 on technical standards for the establishment and operation of a traceability system for tobacco products (Text with EEA relevance)
02018R0574 — EN — 21.12.2023 — 001.001
This text is meant purely as a documentation tool and has no legal effect. The Union's institutions do not assume any liability for its contents. The authentic versions of the relevant acts, including their preambles, are those published in the Official Journal of the European Union and available in EUR-Lex. Those official texts are directly accessible through the links embedded in this document
|
COMMISSION IMPLEMENTING REGULATION (EU) 2018/574 of 15 December 2017 on technical standards for the establishment and operation of a traceability system for tobacco products (OJ L 096 16.4.2018, p. 7) |
Amended by:
|
|
|
Official Journal |
||
|
No |
page |
date |
||
|
COMMISSION IMPLEMENTING REGULATION (EU) 2023/448 of 1 March 2023 |
L 65 |
28 |
2.3.2023 |
|
Corrected by:
COMMISSION IMPLEMENTING REGULATION (EU) 2018/574
of 15 December 2017
on technical standards for the establishment and operation of a traceability system for tobacco products
(Text with EEA relevance)
CHAPTER I
SUBJECT MATTER AND DEFINITIONS
Article 1
Subject matter
This Regulation lays down the technical standards for the establishment and operation of the traceability system provided for in Article 15 of Directive 2014/40/EU.
Article 2
Definitions
For the purposes of this Regulation, in addition to the definitions laid down in Article 2 of Directive 2014/40/EU, the following definitions shall apply:
‘unique identifier’ means the alphanumeric code enabling the identification of a unit pack or an aggregated packaging of tobacco products;
‘economic operator’ means any natural or legal person who is involved in the trade of tobacco products, including for export, from the manufacturer to the last economic operator before the first retail outlet;
‘first retail outlet’ means the facility where tobacco products are placed on the market for the first time, including vending machines used for the sale of tobacco products;
‘export’ means shipment from the Union to a third country;
‘aggregated packaging’ means any packaging containing more than one unit packet of tobacco products;
‘disaggregation of aggregated packaging’ means any disassembly of aggregated packaging of tobacco products;
‘facility’ means any location, building, office or vending machine where tobacco products are manufactured, stored, logistically or financially handled or placed on the market;
‘anti-tampering device’ means the device allowing for the recording of the verification process following the application of each unit level unique identifier by means of a video or a log file, which once recorded cannot be further altered by an economic operator;
‘offline flat-files’ means the electronic files established and maintained by each ID issuer that contain data in a plain text format allowing for the extraction of information encoded in the unique identifiers (excluding the time stamp) used at the unit packet and aggregated packaging levels without accessing the repositories system;
‘registry’ means the record established and maintained by each ID issuer of all the identifier codes generated for economic operators, operators of first retail outlets, facilities and machines along with the corresponding information;
‘data carrier’ means a carrier representing data in a form readable with the aid of a device;
‘machine’ means assemblies of machinery that are used for the manufacture of tobacco products and are integral to the manufacturing process;
‘machine part’ means any identifiable fixed or mobile part of a machine provided that such a part constitutes a complete module. A mobile part may be used for one or more machines simultaneously or interchangeably;
‘time stamp’ means the date and time of occurrence of a particular event recorded in UTC (Coordinated Universal Time) time in a prescribed format;
‘primary repository’ means a repository storing traceability data relating exclusively to the products of a given manufacturer or importer;
‘secondary repository’ means a repository containing a copy of all traceability data stored in the primary repositories;
‘router’ means a device established within the secondary repository that transfers data between different components of the repositories system;
‘repositories system’ means the system consisting of the primary repositories, the secondary repository and the router;
‘common data dictionary’ means a set of information describing the contents, format, and structure of a database and the relationship between its elements, used to control access to and manipulation of the databases common for all primary and secondary repositories;
‘working day’ means every day of work in the Member State for which the ID issuer is competent;
‘trans-loading’ means any transfer of tobacco products from one vehicle to another during which tobacco products do not enter and exit a facility;
‘vending van’ means a vehicle used for the delivery of tobacco products to multiple retail outlets in quantities that have not been predetermined in advance of the delivery;
‘IT service provider’ means a service provider that is tasked by an economic operator with transmitting information on product movements and transactional information to the repositories system.
CHAPTER II
TECHNICAL SPECIFICATIONS RELATED TO THE UNIQUE IDENTIFIER
SECTION 1
Common provisions
Article 3
ID issuer
Each Member State shall put in place adequate measures to ensure:
that the ID issuer it has appointed continues to comply with the requirement of independence in accordance with Article 35; and
the continuous operation of the services provided by successive ID issuers, in case a new ID issuer is appointed to take over the services from the previous ID issuer. For this purpose Member States shall require the ID issuer to develop an exit plan laying down the procedure to be followed to guarantee the continuity of the operations until the new ID issuer is appointed.
Article 4
Competent ID issuers for generating and issuing unique identifiers
By derogation to the first subparagraph, the competent ID issuer shall be the entity appointed for the Member State on whose market the products are placed, where such a requirement is imposed by that Member State.
Article 5
Validity of unique identifiers and deactivation
SECTION 2
Unique identifiers at unit packet level
Article 6
Marking by means of unit level UIs
Article 7
Verification of unit level UIs
By way of derogation from paragraphs 2, 4 and 5, the obligation to install an anti-tampering device shall not apply:
until 20 May 2020 to production processes operated by economic operators, or where applicable, the group of undertakings to which they belong, that handled less than 120 million unit level UIs at Union level during the calendar year 2019;
until 20 May 2021 to production processes operated by economic operators falling under the definition of small and medium enterprises set out in Commission Recommendation 2003/361/EC ( 1 );
to fully manual production processes.
Article 8
Structure of unit level UIs
Each unit packet of tobacco products shall be marked with a unit level UI. It shall consist of as short a sequence of alphanumeric characters as possible, not exceeding 50 characters. The sequence shall be unique to a given unit packet and shall be composed of the following data elements:
in the first position, the alphanumeric characters that constitute the ID issuer identification code assigned pursuant to Article 3(4);
an alphanumeric sequence, whose probability to be guessed shall be negligible and in any case lower than one in ten thousand (‘serial number’);
a code (‘product code’) allowing for the determination of the following:
the place of manufacturing;
the manufacturing facility referred to in Article 16;
the machine used to manufacture the tobacco products referred to in Article 18;
the product description;
the intended market of retail sale;
the intended shipment route;
where applicable, the importer into the Union;
in the last position, the time stamp in the form of a numeric sequence of eight characters, in the format YYMMDDhh, indicating the date and time of manufacture.
ID issuers shall prepare and make publicly available instructions for encoding and decoding unit level UIs in accordance with Annex III.
Where ID issuers use encryption or compression for the generation of unit level UIs, they shall inform the competent authorities of the Member States and the Commission of algorithms used for such encryption and compression. Unit level UIs shall not be reused.
Article 9
Request and issuing of unit level UIs
The ID issuer shall, within two working days from the receipt of the request and in the order indicated:
generate the codes referred to in Article 8(2) and the corresponding human-readable codes referred to in Article 23;
transmit both sets of codes along with the information referred to in paragraph 2 via the router to the primary repository of the requesting manufacturer or importer, as established under Article 26; and
electronically transmit both sets of codes to the requesting manufacturer or importer.
However, a Member State may require ID issuers to offer physical delivery of unit level UIs as an alternative to electronic delivery. In cases where physical delivery of unit level UIs is offered, manufacturers and importers shall specify whether physical delivery is requested. In that case, the ID issuer shall within 10 working days from the receipt of the request, and in the following order:
generate the codes referred to in Article 8(2) and the corresponding human-readable codes referred to in Article 23;
transmit both sets of codes along with the information referred to in paragraph 2 via the router to the primary repository of the requesting manufacturer or importer, as established under Article 26;
electronically transmit both sets of codes to the requesting manufacturer or importer;
deliver both sets of codes to the requesting manufacturer or importer in the form of optical barcodes, compliant with Article 21, placed on physical carriers, such as adhesive labels.
SECTION 3
Unique identifiers at aggregated packaging level
Article 10
Marking by means of aggregated level UIs
Article 11
Structure of aggregated level UIs generated by ID issuers
For aggregated level UI generated on the basis of a request to the competent ID issuer, the structure of the aggregated level UI shall consist of a sequence of a maximum of 100 alphanumeric characters that is unique to a given aggregated package and shall be composed of the following data elements:
in the first position, the alphanumeric characters that constitute the ID issuer identification code assigned under Article 3(4);
an alphanumeric sequence, whose probability to be guessed shall be negligible and in any case lower than one in ten thousand (‘serial number’);
the identifier code of the facility (as set out in Article 16) in which the aggregation process took place;
in the last position, the time stamp in the form of a numeric sequence of eight characters, in the format YYMMDDhh, indicating the date and time of aggregation.
ID issuers shall prepare and make publicly available instructions for encoding and decoding aggregated level UIs.
Article 12
Link between UI levels
Article 13
Request and issuing of aggregated level UIs generated by ID issuers
For manufacturers and importers, the ID issuer shall, within two working days from the receipt of the request and in the order indicated:
generate the code referred to in Article 11(2);
transmit the codes along with the information referred to in paragraph 2 via the router to the primary repository of the requesting manufacturer or importer, as established under Article 26; and
transmit the codes electronically to the requesting manufacturer or importer.
For economic operators other than manufacturers and importers, the ID issuer shall, within two working days from the receipt of the request and in the order indicated:
generate the code referred to in Article 11(2);
transmit the codes along with the information referred to in paragraph 2 via the router to the secondary repository established under Article 27; and
transmit the codes electronically to the requesting economic operators.
CHAPTER III
IDENTIFIER CODES FOR ECONOMIC OPERATORS, FACILITIES AND MACHINES
Article 14
Request for an economic operator identifier code
Economic operators managing standalone warehouses that are not based in the Union and that handle products manufactured in the Union and destined for the Union markets in transit through third countries may apply for an economic operator identifier code from the ID issuer competent for the Member State on whose market most of the products handled by these economic operators are placed.
The de-registration of an economic operator identifier code shall lead to the automatic de-registration of related facility identifier codes and machine identifier codes by the ID issuer.
Article 15
Issuing and registration of economic operator identifier codes
Upon receipt of a request pursuant to Article 14, the ID issuer shall generate an economic operator identifier code, which consists of the following data elements, to be placed in the following order:
in the first position, the alphanumeric characters that constitute the ID issuer identification code assigned under Article 3(4); and
in the second position, an alphanumeric sequence which is unique within the code pool of the ID issuer.
If the requesting operator is a manufacturer or an importer, it shall, within two working days from receiving the code, further transmit the code along with the information on its primary repository established in accordance with Article 26 to the operator of the secondary repository.
Article 16
Request for a facility identifier code
By way of derogation from the first subparagraph, a first retail outlet that is integrated into a non-retail type of facility shall be identified with a separate facility identifier code that corresponds to its function.
Economic operators managing standalone warehouses that are not based in the Union and that handle products manufactured in the Union and destined for the Union markets in transit through third countries may apply for a facility identifier code for a standalone warehouse that is located in a third country from the ID issuer competent for the Member State on whose market most of the products handled by these economic operators are placed. To this end, they shall provide to the ID issuer the information listed in point 1.4 of Section 1 of Chapter II of Annex II, in the format indicated therein.
The de-registration of a facility identifier code shall lead to the automatic de-registration of related machine identifier codes by the ID issuer.
Article 17
Issuing and registration of facility identifier codes
Upon receipt of a request pursuant to Article 16, the ID issuer shall generate a facility identifier code, which consists of the following data elements, to be placed in the following order:
in the first position, the alphanumeric characters that constitute the ID issuer identification code assigned under Article 3(4); and
in the second position, an alphanumeric sequence which is unique within the code pool of the ID issuer.
Article 18
Request for a machine identifier code
Manufacturers and importers shall carry out all necessary modifications of the information submitted in the initial application forms in order to provide the necessary information on machine parts which require a machine identifier code by 20 May 2024. The modifications shall take place in the format indicated in point 1.8 of Section 1 of Chapter II of Annex II. This requirement shall also apply to the information on machines containing no separately identifiable machine parts.
Article 19
Issuing and registration of machine identifier codes
Upon receipt of a request pursuant to Article 18, the ID issuer shall generate a machine identifier code, which consists of the following data elements, to be placed in the indicated position:
in the first position, the alphanumeric characters that constitute the ID issuer identification code assigned under Article 3(4); and
in the second position, an alphanumeric sequence which is unique within the code pool of the ID issuer.
Article 20
Transfer of offline flat-files and registries
CHAPTER IV
DATA CARRIERS
Article 21
Data carriers for the Unique Identifiers
Unit level UIs shall be encoded using at least one of the following types of data carriers:
an optical device-readable Data Matrix with error detection and correction equivalent to or higher than those of the Data Matrix ECC200. Barcodes conforming to ISO/IEC 16022:2006 shall be presumed to fulfil the requirements set out in this point;
an optical device-readable QR Code with a recovery capacity of approximately 30 %. Barcodes conforming to ISO/IEC 18004:2015 with the error correction level H shall be presumed to fulfil the requirements set out in this point;
an optical device-readable DotCode with the error detection and correction equivalent to or higher than those provided with the Reed-Solomon error correction algorithm with the number of check characters (NC) equal to three plus the number of data characters (ND) divided by two (NC = 3 + ND/2). Barcodes conforming to the ISS DotCode Symbology Specification published by the Association for Automatic Identification and Mobility (‘AIM’) (revision 3.0, August 2014) shall be presumed to fulfil the requirements set out in this point.
Aggregated level UIs shall be encoded by economic operators using at least one of the following types of data carriers:
an optical device-readable Data Matrix with error detection and correction equivalent to or higher than those of the Data Matrix ECC200. Barcodes conforming to ISO/IEC 16022:2006 shall be presumed to fulfil the requirements set out in this point;
an optical device-readable QR Code with a recovery capacity of approximately 30 %. Barcodes conforming to ISO/IEC 18004:2015 with the error correction level H shall be presumed to fulfil the requirements set out in this point;
an optical device-readable Code 128 with the error detection equivalent to or higher than the one provided with the algorithm based on the even/odd — bar/space character parity and the check character. Barcodes conforming to ISO/IEC 15417:2007 shall be presumed to fulfil the requirements set out in this point.
In order to distinguish the data carriers referred to in paragraph 5 from any other data carrier placed on aggregated packaging, economic operators shall add the marking ‘EU TTT’ next to such data carriers.
Article 22
Quality of the optical data carriers
Article 23
Human-readable code
CHAPTER V
REPOSITORIES SYSTEM
Article 24
Components of the repositories system
The repositories system shall be composed of the following sub-systems:
repositories which are established for the purpose of storing data relating to tobacco products of individual manufacturers and importers (‘primary repositories’);
a repository which contains a copy of all data stored in the primary repositories system (‘secondary repository’);
a routing service (‘router’) set up and managed by the provider of the secondary repository system.
Article 25
General characteristics of the repositories system
The repositories system shall satisfy the following conditions:
it shall allow for functional integration of the repositories system into the traceability system, as well as uninterrupted electronic data exchange between the repositories system and other relevant components of the traceability system;
it shall allow for electronic identification and authentication of tobacco products, at unit packet and aggregation level, in accordance with the requirements set out in this Regulation;
it shall allow for automatic deactivation of unique identifiers in accordance with the rules set out in Article 5;
it shall ensure electronic receipt and storing of information recorded and sent to the repositories system by economic operators and ID issuers, in accordance with the requirements of this Regulation;
it shall ensure storage of data for a minimum period of five years as of the moment the data are uploaded into the repositories system;
it shall allow for automatic status messaging to economic operators, and to Member States and the Commission as requested, such as in the event of success, error or changes related to reporting activities, in accordance with the requirements of this Regulation;
it shall allow for automatic validation of messages received from economic operators at each entry point to the system, including refusal of incorrect or incomplete messages, in particular reporting activities related to non-registered or duplicated unique identifiers, whereby the repositories system shall store the information concerning any refused message. Messages transmitted by the ID issuers and the primary repositories to the router and the secondary repository shall be validated again by the recipient;
it shall ensure messaging between all of its components which shall take place instantaneously, in accordance with the requirements of this Regulation, in particular the overall response time of the repositories system in sending acknowledgment messages, not considering the speed of the internet connection of the end user, which shall be no more than 60 seconds;
it shall ensure continuous availability of all components and services with a monthly uptime of at least 99,5 % and sufficient back-up mechanisms in place;
it shall be guarded by security procedures and systems ensuring that access to the repositories and download of the data stored therein is only granted to persons authorised according to this Regulation;
it shall be accessible by the competent authorities of Member States and by the Commission. National administrators designated by the Member States and Commission services shall be granted access rights enabling them to create, manage, and withdraw user access rights for repositories, and related operations stipulated in this Chapter, via a graphical user management interface. ►C1 Modes of accessing the graphical user management interface shall be compatible with Regulation (EU) No 910/2014, in particular the relevant reusable solutions provided as building blocks under the telecommunication part of the Connecting Europe Facility. ◄ National administrators designated by the Member States shall be able to grant subsequent access rights to other users under their responsibility;
it shall enable Member States and the Commission to carry out downloads of full and selected sets of data stored in a repository;
it shall maintain a complete record (‘audit trail’) of all operations concerning the stored data of the users performing those operations and of the nature of these operations, including the history of users access. The audit trail shall be created when the data is uploaded for the first time and, notwithstanding any additional national requirements, be maintained until at least five years after.
Article 26
Primary repositories
Article 27
Secondary repository
The secondary repository shall provide for graphical and non-graphical interfaces, including an application programming interface, stationary and mobile user interfaces containing an inspection application for the leading mobile operating systems, that enable Member States and the Commission to access and query the data stored in the repositories system, using all commonly available database search functions, including Structured Query Language (SQL) or equivalent syntax for building custom queries, in particular by remotely carrying out the following operations:
retrieval of any information concerning one or multiple unique identifier(s), including the comparison and cross-checking of multiple unique identifiers and the related information, in particular their location in the supply chain;
creation of lists and statistics, such as product stocks and inflow/outflow numbers, associated with one or multiple elements of reporting information listed as Data Fields in Annex II;
identification of all tobacco products that have been reported by an economic operator to the system, including the products reported as recalled, withdrawn, stolen, missing or intended for destruction.
The user interfaces referred to in paragraph 2 shall enable each Member State and the Commission to configure their own rules for:
automatic alerting based on exceptions and specific reporting events, such as abrupt fluctuations or irregularities in trade, attempts to introduce duplicate unique identifiers into the system, deactivation of the identifiers referred to in Articles 15(4), 17(4) and 19(4), or where a product is indicated by economic operators as stolen or missing;
the receipt of periodic reports based on any combination of the elements of reporting information listed as Data Field in Annex II;
tailor-made dashboards, for stationary interfaces.
The user interfaces referred to in paragraph 2 shall enable Member States and the Commission to:
connect remotely to the data stored in the repositories system with the analytical software of their choice;
flag individual data points for analytical purposes, with flags and their values stored in the secondary repository and made visible to all or only selected users;
upload external data elements, such as brand normalisation patterns, that may be required for improvements in data analytical functionalities.
ID issuers and providers of primary repositories may have access to the register referred to in the first subparagraph in order to validate the messages sent to them by manufacturers and importers.
Article 28
Coordination tasks of the provider of the secondary repository
Any newly selected replacement provider operating the secondary repository shall rely on the latest version of the list of specifications communicated by its predecessor. Any updates to the list of specifications going beyond the change of the provider’s identity shall be made in accordance with the procedure laid down in paragraph 3.
The list referred to in the first subparagraph shall be communicated no later than 2 months following the date when the provider operating the secondary repository was selected.
Any newly selected replacement provider operating the secondary repository shall rely on the latest version of the data dictionary communicated by its predecessor. Any updates to the data dictionary going beyond the change of the provider’s identity shall be made in accordance with the procedure laid down in paragraph 3.
The common data dictionary shall be communicated to the providers operating primary repositories no later than 2 months following the date when the provider operating the secondary repository was selected.
The provider of the secondary repository shall set up a user-acceptance-testing environment allowing ID issuers, providers operating primary repositories and economic operators to perform quality assurance of their technical solutions and routines in anticipation of the next version of the repositories system. The user-acceptance-testing environment shall reflect any planned changes to the repositories system upon their communication in accordance with paragraph 3.
Article 29
Router
Article 30
Costs of the repositories system
All ordinary costs related to the repositories system referred to in Article 24(1), including those that arise from its establishment, operation and maintenance, shall be borne by manufacturers and importers of tobacco products. Those costs shall be fair, reasonable, and proportionate:
to the services rendered; and
to the amount of unit level UIs requested over a given period of time.
Article 31
Deadline for the establishment of the repositories system
The repositories system shall be established and functional for testing purposes by 20 March 2019.
CHAPTER VI
RECORDING AND TRANSMITTING
Article 32
Recording and transmission of information on product movements
To allow the determination of the actual shipment route of unit packets manufactured in, or imported into the Union, economic operators shall record the following events:
application of unit level UIs on unit packets;
application of aggregated level UIs on aggregated packaging;
dispatch of tobacco products from a facility;
arrival of tobacco products at a facility;
trans-loading.
For dispatch of tobacco products to laboratories, waste disposal centres, national authorities, international governmental organisations, embassies and military bases, manufacturers and importers shall transmit the information listed in point 3.8 of Section 3 of Chapter II of Annex II, in the format indicated therein, to the primary repository contracted by them. All other economic operators shall transmit the information listed in point 3.8 of Section 3 of Chapter II of Annex II, in the format indicated therein, via the router.
If tobacco products reported as stolen are recovered, economic operators may transmit a reactivation request in accordance with the scope and format specified in point 2.4 of Section 2 of Chapter II of Annex II.
Article 33
Recording and transmission of transactional information
To allow the determination of the transactional information referred to in Article 15(2), points (j) and (k) of Directive 2014/40/EU, economic operators shall record the following events:
issuing of the order number;
issuing of the invoice;
receipt of the payment.
Article 34
Time frame for transmission of required information
The information referred to in Article 32 shall be transmitted in the order of the occurrence of the events.
By way of derogation from paragraph 1, economic operators may transmit the information referred to in Article 32(1) points (a), (b) and (d), Articles 32(3) and (4), and Article 33(1), within 24 hours from the occurrence of the event, if they fulfil any of the following conditions:
they, or where applicable, the group of undertakings to which they belong, handled less than 120 million unit level UIs at Union level during the previous calendar year;
they are small and medium enterprises within the meaning of Commission Recommendation 2003/361/EC.
CHAPTER VII
FINAL PROVISIONS
Article 35
Independence
For the purposes of paragraph 1, the following criteria shall be used to assess independence:
independence from the tobacco industry in terms of legal form, organisation and decision making. In particular it shall be assessed whether the undertaking or the group of undertakings is not under the direct or indirect control of the tobacco industry, including a minority shareholding;
independence from the tobacco industry in financial terms, which will be presumed if, before assuming their functions the undertaking or the group of undertakings concerned generates less than 10 % of its annual worldwide turnover, excluding VAT and any other indirect taxes, from goods and services supplied to the tobacco sector over the past two calendar years, as may be determined on the basis of the most recent approved accounts. For each subsequent calendar year, the annual worldwide turnover, excluding VAT and any other indirect taxes, from goods and services supplied to the tobacco sector shall not exceed 20 %;
absence of conflicts of interests with the tobacco industry of the persons responsible for the management of the undertaking or the group of undertakings, including members of the board of directors or any other form of governing body. In particular, they:
shall not have participated in company structures of the tobacco industry for the last five years;
shall act independently from any pecuniary or non-pecuniary interest linked to the tobacco industry, including possession of stocks, participation in private pension programmes or interest held by their partners, spouses or direct relatives in the ascending or descending line.
Article 36
Security and interoperability of communications and data
All electronic communication provided for under this Regulation shall be carried out using secure means. Applicable security protocols and connectivity rules shall be based on non-proprietary open standards. They shall be established by:
the ID issuer for communications between the ID issuer, the operators of the first retail outlets and the economic operators registering with the ID issuer or requesting unique identifiers;
the providers of the primary repositories for communications between the primary repositories and manufactures or importers;
the provider of the secondary repository for communications between the secondary repository and the router and:
the ID issuers;
the primary repositories; and
economic operators using the router, i.e. economic operators other than manufacturers and importers.
Article 36a
Quality of data
Article 37
Transitional provision
Article 38
Entry into force
This Regulation shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union.
This Regulation shall be binding in its entirety and directly applicable in all Member States.
ANNEX I
SELECTION PROCEDURE FOR INDEPENDENT THIRD PARTY PROVIDERS OF REPOSITORY SYSTEMS
PART A
The following procedures shall apply to the selection of an independent third party provider operating a primary repository:
Each manufacturer and importer of cigarettes and roll-your-own tobacco shall notify to the Commission, no later than two months following the entry into force of Delegated Regulation (EU) 2018/573:
the identity of the third party that it proposes to appoint to operate a primary repository (the ‘proposed provider’), and
a draft data storage contract containing the key elements laid down in the Delegated Regulation for approval by the Commission.
Where several legal persons constitute the same manufacturer or importer, the notification shall be submitted jointly by all legal persons.
In cases where the importer concerned cooperates with only one non-EU manufacturer or belongs to the same group of companies as the latter, the data storage contract may be co-signed by both the importer and the non-EU manufacturer. In cases where the importer concerned cooperates with several non-EU manufacturers or is also a Union manufacturer itself, the data storage contract shall be signed solely by the importer.
The notification shall be accompanied by:
the written declaration of technical and operational expertise, referred to in Article 4 of Delegated Regulation (EU) 2018/573,
the written declaration of legal and financial independence, referred to in Article 8 of Delegated Regulation (EU) 2018/573, and
a table setting out the correspondence between the contractual clauses and the requirements laid down in Delegated Regulation (EU) 2018/573.
The Commission shall, within three months of the date of receiving the notification, and on the basis of an examination of the suitability of the proposed provider, in particular, as regards its independence and technical capacities as referred to in Article 15(8) of Directive 2014/40/EU, approve or reject the proposed provider and the draft contract. In the absence of a reply by the Commission within that timeframe, the provider and the draft contract shall be deemed to be approved.
Where the Commission does not approve the proposed provider or the draft contract, or where it considers that the contract does not incorporate the key elements laid down in Delegated Regulation (EU) 2018/573, the manufacturer or importer concerned shall, within one month of being informed by the Commission, propose an alternative provider and/or make necessary amendments to the draft contract for further consideration by the Commission.
Once the proposed provider and the draft contract have been approved, the manufacturers and importers shall, within two weeks of such approval, provide in electronic format:
a copy of the contract signed by both parties, and
the declarations required to be provided as part of the contract under Articles 4 and 8 of Delegated Regulation (EU) 2018/573.
Manufacturers and importers of tobacco products other than cigarettes and roll-your-own tobacco shall notify to the Commission, by 31 December 2022, the identity of the proposed provider, a draft data storage contract containing the key elements laid down in Delegated Regulation (EU) 2018/573 for approval by the Commission, and the additional documentation referred to in paragraph 2.
The provider appointed to operate the primary repository shall only integrate its repository into the traceability system following the conclusion of the approved contract.
A list of notified and approved third parties shall be made publicly available by the Commission on a website.
Any amendment to the key elements of the contract, as defined in Delegated Regulation (EU) 2018/573, shall be subject to approval by the Commission. In the absence of a reply by the Commission within three months of the date of notification of the amendment, the amendment shall be deemed to be approved. This deadline can be extended by the Commission once by a maximum of another three months, by means of a letter to the notifying operator. Any other amendment to the contract than to its key elements shall only require prior communication to the Commission.
PART B
The following procedure shall apply to the selection of an independent third party operating the secondary repository system:
The Commission shall appoint, from amongst the providers of the primary repositories who have been approved in accordance with Part A ►M1 within six months following the entry into force of Delegated Regulation (EU) 2018/573 ◄ , a provider tasked with operating the secondary repository (‘the operator of the secondary repository’) for the purpose of carrying out the services specified in Chapter V of this Regulation.
The appointment of the operator of the secondary repository shall be based on an assessment of objective criteria and take place by means of a concession contract concluded in writing between the Commission and each successive operator of the secondary repository.
The result of the appointment of the operator of the secondary repository shall be made publicly available by the Commission on a website.
Each primary repository provider appointed in accordance with Part A shall enter into an individual contract with the provider appointed to operate the secondary repository for the purpose of carrying out the services specified in Chapter V of this Regulation.
The contracts between each primary repository provider and the operator of the secondary repository shall be signed and submitted to the Commission within three monthsfrom the date of the appointment of each successive operator of the secondary repository.
PART C
The following requirements shall apply in addition to the selection procedures outlined in Parts A and B:
Where the contractual relationship between a manufacturer or importer and the provider of a primary repository is terminated, or expected to be terminated, by any of the parties to the contract, for any reason, including the failure to comply with the criteria for independence laid down in Article 35, the manufacturer or importer shall immediately inform the Commission of such termination, or expected termination, and of the date of the notification of such termination to the provider, as well as the date at which the termination is or is expected to take effect. The manufacturer or importer shall propose and notify to the Commission a replacement provider at the latest three months prior to the termination date of the existing contract. The appointment of the replacement provider shall take place in accordance with Part A.
In the event that the operator of the secondary repository gives notice of its intention to cease operating that repository in accordance with the concession contract referred to in paragraph 2 of Part B, it shall immediately inform the Commission thereof and of the date at which the termination is to take effect. The notice period shall not be shorter than nine months. The contract shall provide for the Commission to be able to unilaterally extend it by up to six months if required for establishing and operationalising a replacement operator of the secondary repository. The Commission shall inform the competent authorities of the Member States about the notice period and its potential extension.
Where paragraph 1 applies, the contract referred to in paragraph 4 of Part B shall, in turn, be terminated by the parties immediately after the closure of the affected primary repository.
ANNEX II
Key messages to be sent by the economic operators
The messages required for regulatory purposes shall contain at least the data fields listed in this Annex.
Member States and the Commission may require an extension of the address data to include exact geographic coordinates (latitude and longitude). Both ID issuers and providers of data repositories (including the router) may decide to extend the message content for strictly technical reasons to secure smooth functioning of the traceability system. ID issuers may also decide to extend the message content for non-technical reasons to secure smooth functioning of the tobacco products traceability system with other systems used for regulatory purposes. Before becoming effective, such extensions shall be reflected in the technical specifications updated in accordance with Article 28.
The messages listed in this Annex do not include the messages to be sent back by ID issuers and providers of data repositories (including the router) to the economic operators, such as acknowledgments of receipt.
All the messages generated within the traceability system shall contain the identification of the message originator and a timestamp up to the millisecond (see Data Type: Time(L)). This timestamp does not replace the time of the occurrence of a reported event, which shall be reported separately in accordance with the data fields prescribed in this Annex. The identification of the message originator, which may concern a third-party IT service provider, does not replace the identification of the economic operator responsible for the reporting activity (via an EOID to be indicated in the EO_ID field). The means of the identification of the message originator shall be specified in the technical specifications established and updated in accordance with Article 28.
ID issuers and providers of data repositories (including the router) shall timestamp each received message up to the millisecond.
In case of amendments to this Annex, any changes in the key messages listed herein become applicable to the economic operators as of the moment such changes are duly reflected in the technical specifications and the common data dictionary established and updated in accordance with Article 28.
CHAPTER I
FIELD DESCRIPTIONS
SECTION 1
Data Type
|
Data Type |
Description |
Example |
|
ARC |
Administrative Reference Code (ARC) or any successive code adopted under the Excise Movement and Control System (EMCS) |
‘15GB0123456789ABCDEF0’ |
|
aUI |
Aggregated level unique identifier coded with: either the invariant set of ISO646:1991 and composed of four blocks: (a) ID issuer's prefix in accordance with ISO15459-2:2015, (b) serialisation element in the format established by the ID issuer, (c) tobacco facility identifier code following the Data Type: FID and (d) timestamp following the Data Type: Time(s) or the invariant set of ISO646:1991 forming a code structured in accordance with ISO15459-1:2014 or ISO15459-4:2014 (or their latest equivalent) |
|
|
Boolean |
Boolean value |
— ‘0’ (false/disabled) — ‘1’ (true/enabled) |
|
Country |
Country name coded with ISO-3166-1:2013 alpha-2 (or its latest equivalent). For overseas and autonomous regions, the country code of the relevant Member State is applicable. In case of Northern Ireland, the ‘XI’ code is applicable. In case of the international waters, the ‘XZ’ code is applicable. |
‘DE’ |
|
Currency |
Currency name coded with ISO 4217:2015 (or its latest equivalent) |
‘EUR’ |
|
Date |
UTC (Coordinated Universal Time) date corresponding to the following format: YYYY-MM-DD |
‘2019-05-20’ |
|
Decimal |
Number values, decimal allowed |
‘1’ or ‘2,2’ or ‘3,33’ |
|
EOID |
Economic operator identifier code corresponding to the format established by the ID issuer coded with the invariant set of ISO646:1991 |
|
|
FID |
Tobacco facility identifier code corresponding to the format established by the ID issuer coded with the invariant set of ISO646:1991 |
|
|
Integer |
Rounded number values, no decimal numbers |
‘1’ or ‘22’ or ‘333’ |
|
MID |
Machine identifier code corresponding to the format established by the ID issuer coded with the invariant set of ISO646:1991 |
|
|
MRN |
Movement Reference Number (MRN) is a unique customs registration number. It contains 18 digits and is composed of the following elements: (a) last two digits of the year of formal acceptance of export movement (YY), (b) country name coded with ISO-3166-1:2013 alpha-2 (or its latest equivalent) of the Member State to which the declaration was sent, (c) unique identifier for entry/import per year and country, and (d) check digit. |
‘11IT9876AB88901235’ |
|
SEED |
Excise number composed of: (a) country name coded with ISO-3166-1:2013 alpha-2 (or its latest equivalent) (e.g. ‘LU’) and (b) eleven alphanumeric characters, if needed, padded to the left with zeroes (e.g. ‘00000987ABC’). |
‘LU00000987ABC’ |
|
ITU |
Individual transport unit code (e.g. SSCC) generated in accordance with ISO15459-1:2014 (or its latest equivalent) |
‘001234560000000018’ |
|
Text |
Set of characters coded with ISO8859-15:1999 |
‘Abcde:12345’ |
|
Time(L) |
UTC (Coordinated Universal Time) in the following format: YYYY-MM- DDTHH:mm:ss.SSSZ |
‘2019-07-16T19:20:30.205Z’ |
|
Time(s) |
UTC (Coordinated Universal Time) in the following format: YYMMDDhh |
‘19071619’ |
|
TPID |
Tobacco Product Identifier (TP-ID) – numeric identifier used in the EU-CEG system in the format: NNNNN-NN-NNNNN |
‘02565-16-00230’ |
|
PN |
Product number – numeric identifier used in the EU-CEG system to identify product presentations (e.g. GTIN (Global Trade Identification Number) of the product) |
‘00012345600012’ |
|
upUI(L) |
Unit packet level unique identifier coded with the invariant set of ISO646:1991 and composed of three blocks: (i) ID issuer’s prefix in accordance with ISO15459-2:2015, (ii) middle block in the format established by the ID issuer and (iii) timestamp following the Data Type: Time(s) |
|
|
upUI(i) |
Unit packet level unique identifier coded with the invariant set of ISO646:1991 and composed of two blocks: (i) ID issuer’s prefix in accordance with ISO15459-2:2015 and (ii) middle block in the format established by the ID issuer (i.e. upUI(i) is upUI(L) without the timestamp, a code to be generated by ID issuers in accordance with Article 8(2) of this Regulation) |
|
|
upUI(s) |
Unit packet level unique identifier coded with the invariant set of ISO646:1991 and composed of two blocks: (i) ID issuer’s prefix in accordance with ISO15459-2:2015 and (ii) serialisation element in the format established by the ID issuer (i.e. UI made visible in the human readable format on the unit packets in accordance with Article 23 of this Regulation) Whenever possible ID issuers are requested not to use upper-case letter ‘O’ (Oscar) and lower-case letter ‘l’ (lima) as well as upper-case letter ‘I’ (India) in order to avoid confusions with digits ‘0’ (zero) and ‘1’ (one), respectively. |
|
|
Year |
UTC (Coordinated Universal Time) year in the following format: YYYY |
‘2024’ |
SECTION 2
Cardinality Type
|
Type |
Description |
|
Simple (S) |
Single value |
|
Multiple (M) |
Multiple values |
SECTION 3
Priority Type
|
Type |
Description |
|
Mandatory (M) |
The variable must be completed to successfully submit the message |
|
Optional (O) |
The variable relates to supplementary fields which remain optional |
CHAPTER II
MESSAGES
SECTION 1
Identifier codes for economic operators, facilities and machines
1.1. Request for an economic operator identifier code
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
1-1 |
|
|
EO_Name1 |
Economic operator's registered name |
Text |
S |
M |
|
|
|
EO_Name2 |
Economic operator's alternative or abridged name |
Text |
S |
O |
|
|
|
EO_street |
Economic operator’s street name and house number (or road number and kilometre) |
Text |
S |
M |
|
|
|
EO_municipality |
Economic operator’s municipality (city, town or village) |
Text |
S |
M |
|
|
|
EO_postcode |
Economic operator’s postal code |
Text |
S |
M |
‘n/a’ is permitted value if no postal code has been assigned |
|
|
EO_A_info |
Additional information on economic operator’s address (e.g. location in the shopping mall or industrial area) |
Text |
S |
O |
|
|
|
EO_CountryReg |
Economic operator's country of registration |
Country |
S |
M |
|
|
|
EO_Email |
Economic operator's email address used to inform about registration process, including subsequent changes and other required correspondence |
Text |
S |
M |
|
|
|
VAT_R |
Indication of the VAT registration status |
Boolean |
S |
M |
0 – No VAT registration 1 – VAT number exists |
|
|
VAT_N |
Economic operator's VAT number |
Text |
S |
M, if VAT_R = 1 |
|
|
|
TAX_N |
Economic operator's tax registration number |
Text |
S |
M, if VAT_R = 0 |
|
|
|
EO_ExciseNumber1 |
Indication if the economic operator has an excise number issued by the competent authority for the purpose of identification of persons/premises |
Boolean |
S |
M |
0 – No SEED number 1 – SEED number exists |
|
|
EO_ExciseNumber2 |
Economic operator's excise number issued by the competent authority for the purpose of identification of persons/premises |
SEED |
S |
M, if EO_ExciseNumber1 = 1 |
|
|
|
OtherEOID_R |
Indication if the economic operator has been allocated an identifier by another ID Issuer |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
OtherEOID_N |
Economic operator identifier codes allocated by other ID Issuers |
EOID |
M |
M, if OtherEOID_R = 1 |
|
|
|
Reg_3RD |
Indication if the registration is made on behalf of a retail outlet operator not involved otherwise in the tobacco trade |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
Reg_EOID |
Identifier of the economic operator that acts on behalf of a retail outlet operator not involved otherwise in the tobacco trade |
EOID |
S |
M, if Reg_3RD = 1 |
|
1.2. Correction of information concerning the economic operator identifier code
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
1-2 |
|
|
EO_ID |
Economic operator identifier code |
EOID |
S |
M |
|
|
|
EO_CODE |
Economic operator's confirmation code provided in response to the registration of economic operator |
Text |
S |
M |
|
|
|
EO_Name1 |
Economic operator's registered name |
Text |
S |
M |
|
|
|
EO_Name2 |
Economic operator's alternative or abridged name |
Text |
S |
O |
|
|
|
EO_street |
Economic operator’s street name and house number (or road number and kilometre) |
Text |
S |
M |
|
|
|
EO_municipality |
Economic operator’s municipality (city, town or village) |
Text |
S |
M |
|
|
|
EO_postcode |
Economic operator’s postal code |
Text |
S |
M |
‘n/a’ is permitted value if no postal code has been assigned |
|
|
EO_A_info |
Additional information on economic operator’s address (e.g. location in the shopping mall or industrial area) |
Text |
S |
O |
|
|
|
EO_CountryReg |
Economic operator's country of registration |
Country |
S |
M |
|
|
|
EO_Email |
Economic operator's email address used to inform about registration process, including subsequent changes |
Text |
S |
M |
|
|
|
VAT_R |
Indication of the VAT registration status |
Boolean |
S |
M |
0 – No VAT registration 1 – VAT number exists |
|
|
VAT_N |
Economic operator's VAT number |
Text |
S |
M, if VAT_R = 1 |
|
|
|
TAX_N |
Economic operator's tax registration number |
Text |
S |
M, if VAT_R = 0 |
|
|
|
EO_ExciseNumber1 |
Indication if the economic operator has an excise number issued by the competent authority for the purpose of identification of persons/premises |
Boolean |
S |
M |
0 – No SEED number 1 – SEED number exists |
|
|
EO_ExciseNumber2 |
Economic operator's excise number issued by the competent authority for the purpose of identification of persons/premises |
SEED |
S |
M, if EO_ExciseNumber1 = 1 |
|
|
|
OtherEOID_R |
Indication if the economic operator has been allocated an identifier by another ID Issuer |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
OtherEOID_N |
Economic operator identifier codes allocated by other ID Issuers |
EOID |
M |
M, if OtherEOID_R = 1 |
|
|
|
Reg_3RD |
Indication if the registration is made on behalf of the retail outlet operator not involved otherwise in the tobacco trade |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
Reg_EOID |
Identifier of the economic operator that acts on behalf of the retail outlet operator not involved otherwise in the tobacco trade |
EOID |
S |
M, if Reg_3RD = 1 |
|
1.3. De-registration of economic operator identifier code
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
1-3 |
|
|
EO_ID |
Economic operator identifier code |
EOID |
S |
M |
|
|
|
EO_CODE |
Economic operator's confirmation code provided in response to the registration of economic operator |
Text |
S |
M |
|
|
|
Reg_3RD |
Indication if the registration is made on behalf of the retail outlet operator not involved otherwise in the tobacco trade |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
Reg_EOID |
Identifier of the economic operator that acts on behalf of the retail outlet operator not involved otherwise in the tobacco trade |
EOID |
S |
M, if Reg_3RD = 1 |
|
1.4. Request for a facility identifier code
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
1-4 |
|
|
EO_ID |
Economic operator identifier code |
EOID |
S |
M |
|
|
|
EO_CODE |
Economic operator's confirmation code provided in response to the registration of economic operator |
Text |
S |
M |
|
|
|
F_street |
Facility’s street name and house number (or road number and kilometre) |
Text |
S |
M |
|
|
|
F_municipality |
Facility’s municipality (city, town or village) |
Text |
S |
M |
|
|
|
F_postcode |
Facility’s postal code |
Text |
S |
M |
‘n/a’ is permitted value if no postal code has been assigned |
|
|
F_A_info |
Additional information on facility’s address (e.g. location in the shopping mall or industrial area) |
Text |
S |
O |
|
|
|
F_Country |
Facility's country |
Country |
S |
M |
|
|
|
F_Type |
Type of facility |
Integer |
S |
M |
1 – manufacturing site with warehouse 2 – standalone warehouse 3 – retail outlet 4 – other |
|
|
F_Type_Other |
Description of other facility |
Text |
S |
M, if F_Type = 4 |
|
|
|
F_Status |
Indication if a part of the facility has a tax (excise) warehouse status |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
F_ExciseNumber1 |
Indication if the facility has an excise number issued by the competent authority for the purpose of identification of persons/premises |
Boolean |
S |
M |
0 – No SEED number 1 – SEED number exists |
|
|
F_ExciseNumber2 |
Facility's excise number issued by the competent authority for the purpose of identification of persons/premises |
SEED |
S |
M, if F_ExciseNumber1 = 1 |
|
|
|
OtherFID_R |
Indication if the facility has been allocated an identifier by another ID Issuer |
Boolean |
S |
M |
0 – No 1 – Yes (possible only for non-EU facilities) |
|
|
OtherFID_N |
Facility identifier codes allocated by other ID Issuers |
FID |
M |
M, if OtherFID_R = 1 |
|
|
|
PrevFID_B |
Indication if the facility was acquired from another operator and had already a facility identifier code |
Boolean |
S |
M |
0 – No (first time registration) 1 – Yes |
|
|
PrevFID_ID |
Previous facility identifier used by the former operator of the facility |
FID |
S |
M, if PrevFID_B = 1 |
|
|
|
Reg_3RD |
Indication if the registration is made on behalf of a retail outlet operator not involved otherwise in the tobacco trade |
Boolean |
S |
M |
0 – No 1 – Yes (possible only if F_Type = 3) |
|
|
Reg_EOID |
Identifier of the economic operator that acts on behalf of the retail outlet operator not involved otherwise in the tobacco trade |
EOID |
S |
M, if Reg_3RD = 1 |
|
1.5. Correction of information concerning the facility identifier code
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
1-5 |
|
|
EO_ID |
Economic operator identifier code |
EOID |
S |
M |
|
|
|
EO_CODE |
Economic operator's confirmation code provided in response to the registration of economic operator |
Text |
S |
M |
|
|
|
F_ID |
Facility identifier code |
FID |
S |
M |
|
|
|
F_street |
Facility’s street name and house number (or road number and kilometre) |
Text |
S |
M |
|
|
|
F_municipality |
Facility’s municipality (city, town or village) |
Text |
S |
M |
|
|
|
F_postcode |
Facility’s postal code |
Text |
S |
M |
‘n/a’ is permitted value if no postal code has been assigned |
|
|
F_A_info |
Additional information on facility’s address (e.g. location in the shopping mall or industrial area) |
Text |
S |
O |
|
|
|
F_Country |
Facility's country |
Country |
S |
M |
|
|
|
F_Type |
Type of facility |
Integer |
S |
M |
1 – manufacturing site with warehouse 2 – standalone warehouse 3 – retail outlet 4 – other |
|
|
F_Type_Other |
Description of other facility |
Text |
S |
M, if F_Type = 4 |
|
|
|
F_Status |
Indication if a part of the facility has a tax (excise) warehouse status |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
F_ExciseNumber1 |
Indication if the facility has an excise number issued by the competent authority for the purpose of identification of persons/premises |
Boolean |
S |
M |
0 – No SEED number 1 – SEED number exists |
|
|
F_ExciseNumber2 |
Facility's excise number issued by the competent authority for the purpose of identification of persons/premises |
SEED |
S |
M, if F_ExciseNumber1 = 1 |
|
|
|
OtherFID_R |
Indication if the facility has been allocated an identifier by another ID Issuer |
Boolean |
S |
M |
0 – No 1 – Yes (possible only for non-EU facilities) |
|
|
OtherFID_N |
Facility identifier codes allocated by other ID Issuers |
FID |
M |
M, if OtherFID_R = 1 |
|
|
|
PrevFID_B |
Indication if the facility was acquired from another operator and had already a facility identifier code |
Boolean |
S |
M |
0 – No (first time registration) 1 – Yes |
|
|
PrevFID_ID |
Previous facility identifier used by the former operator of the facility |
FID |
S |
M, if PrevFID_B = 1 |
|
|
|
Reg_3RD |
Indication if the registration is made on behalf of the retail outlet operator not involved otherwise in the tobacco trade |
Boolean |
S |
M |
0 – No 1 – Yes (possible only if F_Type = 3) |
|
|
Reg_EOID |
Identifier of the economic operator that acts on behalf of the retail outlet operator not involved otherwise in the tobacco trade |
EOID |
S |
M, if Reg_3RD = 1 |
|
1.6. De-registration of facility identifier code
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
1-6 |
|
|
EO_ID |
Economic operator identifier code |
EOID |
S |
M |
|
|
|
EO_CODE |
Economic operator's confirmation code provided in response to the registration of economic operator |
Text |
S |
M |
|
|
|
F_ID |
Facility identifier code |
FID |
S |
M |
|
|
|
Reg_3RD |
Indication if the de-registration is made on behalf of a retail outlet operator not involved otherwise in the tobacco trade |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
Reg_EOID |
Identifier of the economic operator that acts on behalf of the retail outlet operator not involved otherwise in the tobacco trade |
EOID |
S |
M, if Reg_3RD = 1 |
|
1.7. Request for a machine identifier code
|
Item # |
Field |
Comments |
Data Type |
Cardin-ality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
1-7 |
|
|
EO_ID |
Economic operator identifier code |
EOID |
S |
M |
|
|
|
EO_CODE |
Economic operator’s confirmation code provided in response to the registration of economic operator |
Text |
S |
M |
|
|
|
F_ID |
Facility identifier code |
FID |
S |
M |
|
|
|
PrevMID_B |
Indication if the object of this request was already registered, e.g. in relation to another facility identifier code |
Boolean |
S |
M |
0 – No (first time registration) 1 – Yes |
|
|
PrevMID_ID |
Previous machine identifier used for the object of this request |
MID |
S |
M, if PrevMID_B = 1 |
|
|
|
M_entirety |
Indication if this request concerns the machine (v. a part of thereof) |
Boolean |
S |
M |
0 – No (machine part) 1 – Yes (machine) |
|
|
P_Producer |
Part’s producer |
Text |
S |
M, if M_entirety = 0 |
|
|
|
P_Model |
Part’s model |
Text |
S |
M, if M_entirety = 0 |
|
|
|
P_Number |
Part’s serial number |
Text |
S |
M, if M_entirety = 0 |
|
|
|
P_Mobile |
Indication if this part is intended to be used with multiple machines (fixed v. mobile part) |
Boolean |
S |
M, if M_entirety = 0 |
0 – No (fixed part) 1 – Yes (mobile part) |
|
|
P_ATD1 |
Indication if an anti-tampering device in the sense of Article 2(7) records the functioning of this part |
Boolean |
S |
M, if M_entirety = 0 |
0 – No 1 – Yes |
|
|
P_ATD2 |
Anti-tampering device’s serial number |
Text |
S |
M, if M_entirety = 0 and P_ATD1 = 1 |
|
|
|
P_Description |
Part’s description explaining its technical function |
Text |
S |
O |
|
|
|
M_Producer |
Machine’s producer |
Text |
S |
M, if M_entirety = 1 |
|
|
|
M_Model |
Machine’s model |
Text |
S |
M, if M_entirety = 1 |
|
|
|
M_Number |
Machine’s serial number |
Text |
S |
M, if M_entirety = 1 |
|
|
|
M_parts |
Indication if the machine consists of multiple separately identifiable parts |
Boolean |
S |
M, if M_entirety = 1 |
0 – No 1 – Yes |
|
|
M_plist |
List of the identifiable parts |
MID |
M |
M, if M_entirety = 1 and M_parts = 1 |
|
|
|
M_ATD |
Serial number of the anti-tampering device in the sense of Article 2(7) |
Text |
S |
M, if M_entirety = 1 and M_parts = 0 |
|
|
|
M_Capacity |
Maximum capacity over 24-hour production cycle expressed in unit packets |
Integer |
S |
M, if M_entirety = 1 |
|
1.8. Correction of information concerning the machine identifier code
|
Item # |
Field |
Comments |
Data Type |
Cardin-ality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
1-8 |
|
|
EO_ID |
Economic operator identifier code |
EOID |
S |
M |
|
|
|
EO_CODE |
Economic operator’s confirmation code provided in response to the registration of economic operator |
Text |
S |
M |
|
|
|
F_ID |
Facility identifier code |
FID |
S |
M |
|
|
|
M_ID |
Machine identifier code (subject to the correction of information) |
MID |
S |
M |
|
|
|
PrevMID_B |
Indication if the object of this request was already registered, e.g. in relation to another facility identifier code |
Boolean |
S |
M |
0 – No (first time registration) 1 – Yes |
|
|
PrevMID_ID |
Previous machine identifier code used for the object of this request |
MID |
S |
M, if PrevMID_B = 1 |
|
|
|
M_entirety |
Indication if this request concerns the machine (v. a part of thereof) |
Boolean |
S |
M |
0 – No (machine part) 1 – Yes (machine) |
|
|
P_Producer |
Part’s producer |
Text |
S |
M, if M_entirety = 0 |
|
|
|
P_Model |
Part’s model |
Text |
S |
M, if M_entirety = 0 |
|
|
|
P_Number |
Part’s serial number |
Text |
S |
M, if M_entirety = 0 |
|
|
|
P_Mobile |
Indication if this part is intended to be used with multiple machines (fixed v. mobile part) |
Boolean |
S |
M, if M_entirety = 0 |
0 – No (fixed part) 1 – Yes (mobile part) |
|
|
P_ATD1 |
Indication if an anti-tampering device in the sense of Article 2(7) records the functioning of this part |
Boolean |
S |
M, if M_entirety = 0 |
0 – No 1 – Yes |
|
|
P_ATD2 |
Anti-tampering device’s serial number |
Text |
S |
M, if M_entirety = 0 and P_ATD1 = 1 |
|
|
|
P_Description |
Part’s description explaining its technical function |
Text |
S |
O |
|
|
|
M_Producer |
Machine’s producer |
Text |
S |
M, if M_entirety = 1 |
|
|
|
M_Model |
Machine’s model |
Text |
S |
M, if M_entirety = 1 |
|
|
|
M_Number |
Machine’s serial number |
Text |
S |
M, if M_entirety = 1 |
|
|
|
M_parts |
Indication if the machine consists of multiple separately identifiable parts |
Boolean |
S |
M, if M_entirety = 1 |
0 – No 1 – Yes |
|
|
M_plist |
List of the identifiable parts |
MID |
M |
M, if M_entirety = 1 and M_parts = 1 |
|
|
|
M_ATD |
Serial number of the anti-tampering device in the sense of Article 2(7) |
Text |
S |
M, if M_entirety = 1 and M_parts = 0 |
|
|
|
M_Capacity |
Maximum capacity over 24-hour production cycle expressed in unit packets |
Integer |
S |
M, if M_entirety = 1 |
|
1.9. De-registration of machine identifier code
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
1-9 |
|
|
EO_ID |
Economic operator identifier code |
EOID |
S |
M |
|
|
|
EO_CODE |
Economic operator's confirmation code provided in response to the registration of economic operator |
Text |
S |
M |
|
|
|
F_ID |
Facility identifier code |
FID |
S |
M |
|
|
|
M_ID |
Machine identifier code |
MID |
S |
M |
|
SECTION 2
Unique identifiers (UIs)
2.1. Request for unit level UIs
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
2-1 |
|
|
EO_ID |
Economic operator identifier code of the submitting entity (either EU manufacturer or EU importer) |
EOID |
S |
M |
|
|
|
F_ID |
Facility identifier code |
FID |
S |
M |
|
|
|
Process_Type |
Indication if the production process involves machinery |
Boolean |
S |
M |
0 – No (only for fully hand made products) 1 – Yes |
|
|
M_ID |
Machine identifier code |
MID |
S |
M, if Process_Type = 1 |
|
|
|
P_Type |
Type of tobacco product |
Integer |
S |
M |
1 – Cigarette 2 – Cigar 3 – Cigarillo 4 – Roll your own tobacco 5 – Pipe tobacco 6 – Waterpipe tobacco 7 – Oral tobacco 8 – Nasal tobacco 9 – Chewing tobacco 11 – Novel tobacco product 12 – Other (product placed on the market before 19 May 2014, not covered by categories 1-9) |
|
|
P_OtherType |
Description of other type of tobacco product |
Text |
S |
M, if P_Type = 11 |
|
|
|
P_CN |
Combined Nomenclature (CN) code |
Text |
S |
O |
|
|
|
P_Brand |
Brand of tobacco product under which the product will be marketed on its intended market |
Text |
S |
M |
|
|
|
P_SubType_Exist |
Indicates if the product ‘subtype name’ exists. Subtype name provides further product identification beyond a product’s brand name. |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
P_SubType_Name |
The product ‘subtype name’ (if any) as marketed on its intended market |
Text |
S |
M, if P_SubType_Exist = 1 |
|
|
|
P_units |
The number of individual units in the unit packet (number of sticks in the package). |
Integer |
S |
M, if P_Type = 1 or 2 or 3 |
|
|
|
P_weight |
Average gross weight of unit packet, including packaging, in grams with 0,1 gram accuracy |
Decimal |
S |
M |
|
|
|
TP_ID |
Tobacco product identifier used in the EU-CEG system |
TPID |
S |
M, if Intended_Market is an EU country |
|
|
|
TP_PN |
Tobacco product number used in the EU-CEG system (EAN or GTIN or SKU or UPC) |
PN |
S |
M, if Intended_ Market is a Member State O, if Intended_ Market is a third country |
|
|
|
Intended_Market |
Intended country of retail sale |
Country |
S |
M |
|
|
|
Intended_Route1 |
Indication if the product is intended to be moved across country boarders with terrestrial/water/air transport |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
Intended_Route2 |
The first country of terrestrial/water/air transport after the product leaves the Member State of manufacturing or the Member State of importation established on the basis of a check point on the land border, next seaport or next airport respectively |
Country |
S |
M, if Intended_Route1 = 1 |
|
|
|
Import |
Indication if the product is imported into the EU |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
Req_Quantity |
Requested quantity of unit packet level UIs |
Integer |
S |
M |
|
2.2. Request for aggregated level UIs
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
2-2 |
|
|
EO_ID |
Economic operator identifier code of the submitting entity |
EOID |
S |
M |
|
|
|
F_ID |
Facility identifier code |
FID |
S |
M |
|
|
|
Req_Quantity |
Requested quantity of aggregated level UIs |
Integer |
S |
M |
|
2.3. Request for deactivation of UIs
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
2-3 |
|
|
EO_ID |
Economic operator identifier code of the submitting entity |
EOID |
S |
M |
|
|
|
Deact_Type |
Deactivation of unit packet or aggregated level UIs |
Integer |
S |
M |
1 – Unit packet level UIs 2 – Aggregated level UIs |
|
|
Deact_Reason1 |
Identification of the reason for deactivation |
Integer |
S |
M |
1 – Product destroyed 2 – Product stolen 3 – UI destroyed 4 – UI stolen 5 – UI unused 6 – Other |
|
|
Deact_Reason2 |
Description of other reason |
Text |
S |
M, if Deact_Reason1 = 6 |
|
|
|
Deact_Reason3 |
Additional description of the reason |
Text |
S |
O |
|
|
|
Deact_upUI |
List of unit packet level UIs to be deactivated |
upUI(s) |
M |
M, if Deact_Type = 1 |
|
|
|
Deact_upUI |
List of unit packet level UIs to be deactivated |
upUI(L) or upUI(i) or upUI(s) |
M |
M, if Deact_Type = 1 |
|
2.4. Request for reactivation of UIs for products reported as stolen but recovered (only permitted if in preceding message type 2-3, field Deact_Reason1 = 2)
|
Item # |
Field |
Comments |
Data Type |
Cardin-ality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
2-4 |
|
|
EO_ID |
Economic operator identifier code of the submitting entity |
EOID |
S |
M |
|
|
|
F_ID |
Facility identifier code (facility of recovery) |
FID |
S |
M |
|
|
|
React_Type |
Reactivation of unit packet or aggregated level UIs |
Integer |
S |
M |
1 – Unit packet level UIs 2 – Aggregated level UIs |
|
|
React_Reason |
Description of the context of reactivation |
Text |
S |
O |
|
|
|
React_upUI |
List of unit packet level UIs to be reactivated |
upUI(L) or upUI(i) or upUI(s) |
M |
M, if React_Type = 1 |
|
|
|
React_aUI |
List of aggregated level UIs to be reactivated |
aUI |
M |
M, if React_Type = 2 |
|
SECTION 3
Recording and transmission of information on product movements
3.1. Application of unit level UIs on unit packets
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
3-1 |
|
|
EO_ID |
Economic operator identifier code of the submitting entity |
EOID |
S |
M |
|
|
|
F_ID |
Facility identifier code |
FID |
S |
M |
|
|
|
upUI_1 |
List of unit packet level UIs to be recorded (full length) |
upUI(L) |
M |
M |
|
|
|
upUI_2 |
List of corresponding unit packet level UIs to be recorded (as visible in human readable format) indicated in the same order as upUI_1 |
upUI(s) |
M |
M |
|
|
|
upUI_comment |
Comments by the reporting entity |
Text |
S |
O |
|
3.2. Application of aggregated level UIs on aggregated packaging
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
3-2 |
|
|
EO_ID |
Economic operator identifier code of the submitting entity |
EOID |
S |
M |
|
|
|
F_ID |
Facility identifier code |
FID |
S |
M |
|
|
|
Event_Time |
Time of event occurrence |
Time(s) |
S |
M |
|
|
|
aUI |
Aggregated level UI |
aUI |
S |
M |
|
|
|
Aggregation_Type |
Identification of aggregation type |
Integer |
S |
M |
1 – aggregation of only unit packet level UIs 2 – aggregation of only aggregated level UIs 3 – aggregation of both unit packet and aggregated level UIs |
|
|
Aggregated_UIs1 |
List of unit packet level UIs subject to aggregation |
upUI(L) |
M |
M, if Aggregation_ Type = 1 or 3 |
|
|
|
Aggregated_UIs2 |
List of aggregated level UIs subject to further aggregation |
aUI |
M |
M, if Aggregation_ Type = 2 or 3 |
|
|
|
aUI_comment |
Comments by the reporting entity |
Text |
S |
O |
|
3.3. Dispatch of tobacco products from a facility
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
3-3 |
|
|
EO_ID |
Economic operator identifier code of the submitting entity |
EOID |
S |
M |
|
|
|
Event_Time |
Intended time of event occurrence |
Time(s) |
S |
M |
|
|
|
F_ID |
Dispatch facility identifier code |
FID |
S |
M |
|
|
|
Destination_ID1 |
Indication of destination type: if the destination facility is located on the EU territory and if it is delivery to a vending machine (VM) or by means of a vending van (VV) delivering to multiple retail outlets in quantities that have not been predetermined in advance of the delivery |
Integer |
S |
M |
1 – Non EU dest. 2 – EU destination other than VM – fixed quantity delivery 3 – EU VM(s) 4 – EU destination other than VM – delivery with VV |
|
|
Destination_ID2 |
Destination facility identifier code |
FID |
S |
M, if Destination_ID1 = 2 |
|
|
|
Destination_ID3 |
Destination facility identifier code(s) – possible multiple vending machines |
FID |
M |
M, if Destination_ID1 = 3 |
|
|
|
Destination_ID4 |
Destination facility identifier code(s) |
FID |
M |
M, if Destination_ID1 = 4 |
|
|
|
Destination_ID5 |
Destination facility’s street name and house number (or road number and kilometre) |
Text |
S |
M, if Destination_ID1 = 1 |
|
|
|
Destination_ID6 |
Destination facility’s municipality (city, town or village) |
Text |
S |
M, if Destination_ID1 = 1 |
|
|
|
Destination_ID7 |
Destination facility’s postal code |
Text |
S |
M, if Destination_ID1 = 1 |
‘n/a’ is permitted value if no postal code has been assigned |
|
|
Destination_ID8 |
Destination facility’s country |
Country |
S |
M, if Destination_ID1 = 1 |
|
|
|
Transport_mode |
Mode of transport by which the product leaves the facility, see: Commission Regulation (EC) No 684/2009, Annex II, Code List 7 |
Integer |
S |
M |
0 – Other 1 – Sea Transport 2 – Rail transport 3 – Road transport 4 – Air transport 5 – Postal consignment 6 – Fixed transport installations 7 – Inland waterway transport |
|
|
Transport_vehicle |
Identification of the vehicle (i.e. number plates, train number, plane/flight number, ship name or other identification) |
Text |
S |
M |
‘n/a’ is permitted value if Transport_mode = 0 and product movement takes place between adjacent facilities and is delivered manually |
|
|
Transport_cont1 |
Indication if the transport is containerised and uses an individual transport unit code (e.g. SSCC) |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
Transport_cont2 |
Individual transport unit code of the container |
ITU |
S |
M, if Transport_cont1 = 1 |
|
|
|
Transport_s1 |
Indication if the dispatch takes place with the logistic/postal operator who operates its own track and trace system accepted by the Member State of the dispatch facility. Only for small quantities of tobacco products (net weight of the products dispatched below 10 kg) destined for exports to third countries |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
Transport_s2 |
The logistic operator's tracking number |
Text |
S |
M, if Transport_s1 = 1 |
|
|
|
EMCS |
Dispatch under the Excise Movement and Control System (EMCS) |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
EMCS_ARC |
Administrative Reference Code (ARC) |
ARC |
S |
M, if EMCS = 1 |
|
|
|
SAAD |
Dispatch with a simplified accompanying document, see: Commission Regulation (EEC) No 3649/92 |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
SAAD_number |
Reference number of the declaration and/or authorization which has to be given by the competent authority in the Member State of destination before the movement starts |
Text |
S |
M, if SAAD = 1 |
|
|
|
Exp_Declaration |
Indication if the Movement Reference Number (MRN) has been issued by the customs office |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
Exp_ DeclarationNumber |
Movement Reference Number (MRN) |
MRN |
S |
M, if Exp_Declaration = 1 |
|
|
|
UI_Type |
Identification of UI types in the dispatch (recorded at the highest level of available aggregation) |
Integer |
S |
M |
1 – only unit packet level UIs 2 – only aggregated level UIs 3 – both unit packet and aggregated level UIs |
|
|
upUIs |
List of unit packet level UIs subject to the dispatch |
upUI(L) |
M |
M, if UI_Type = 1 or 3 |
|
|
|
aUIs |
List of aggregated level UIs subject to the dispatch |
aUI |
M |
M, if UI_Type = 2 or 3 |
|
|
|
Dispatch_comment |
Comments by the reporting entity |
Text |
S |
O |
|
3.4. Arrival of tobacco products at a facility
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
3-4 |
|
|
EO_ID |
Economic operator identifier code of the submitting entity |
EOID |
S |
M |
|
|
|
F_ID |
Arrival facility identifier code |
FID |
S |
M |
|
|
|
Event_Time |
Time of event occurrence |
Time(s) |
S |
M |
|
|
|
Product_Return |
Indication if the arriving products are a return following complete or partial non-delivery |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
UI_Type |
Identification of UI types received (recorded at the highest level of available aggregation) |
Integer |
S |
M |
1 – only unit packet level UIs 2 – only aggregated level UIs 3 – both unit packet and aggregated level UIs |
|
|
upUIs |
List of unit packet level UIs received |
upUI(L) |
M |
M, if UI_Type = 1 or 3 |
|
|
|
aUIs |
List of aggregated level UIs received |
aUI |
M |
M, if UI_Type = 2 or 3 |
|
|
|
Arrival_comment |
Comments by the reporting entity |
Text |
S |
O |
|
3.5. Trans-loading
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
3-5 |
|
|
EO_ID |
Economic operator identifier code of the submitting entity |
EOID |
S |
M |
|
|
|
Event_Time |
Intended time of event occurrence |
Time(s) |
S |
M |
|
|
|
Destination_ID1 |
Indication if the destination facility is located on the EU territory |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
Destination_ID2 |
Destination facility identifier code |
FID |
S |
M, if Destination_ID1 = 1 |
|
|
|
Destination_ID3 |
Destination facility’s street name and house number (or road number and kilometre) |
Text |
S |
M, if Destination_ID1 = 0 |
|
|
|
Destination_ID4 |
Destination facility’s municipality (city, town or village) |
Text |
S |
M, if Destination_ID1 = 0 |
|
|
|
Destination_ID5 |
Destination facility’s postal code |
Text |
S |
M, if Destination_ID1 = 0 |
‘n/a’ is permitted value if no postal code has been assigned |
|
|
Destination_ID6 |
Destination facility’s country |
Country |
S |
M, if Destination_ID1 = 0 |
|
|
|
Transport_mode |
Mode of transport to which the product is trans-loaded, see: Commission Regulation (EC) No 684/2009, Annex II, Code List 7 |
Integer |
S |
M |
0 – Other 1 – Sea Transport 2 – Rail transport 3 – Road transport 4 – Air transport 5 – Postal consignment 6 – Fixed transport installations 7 – Inland waterway transport |
|
|
Transport_vehicle |
Identification of the vehicle (i.e. number plates, train number, plane/flight number, ship name or other identification) |
Text |
S |
M |
|
|
|
Transport_cont1 |
Indication if the transport is containerised and uses an individual transport unit code (e.g. SSCC) |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
Transport_cont2 |
Individual transport unit code of the container |
ITU |
S |
M, if Transport_cont1 = 1 |
|
|
|
EMCS |
Dispatch under the Excise Movement and Control System (EMCS) |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
EMCS_ARC |
Administrative Reference Code (ARC) |
ARC |
S |
M, if EMCS = 1 |
|
|
|
UI_Type |
Identification of UI types subject to the trans-loading (recorded at the highest level of available aggregation) |
Integer |
S |
M |
1 – only unit packet level UIs 2 – only aggregated level UIs 3 – both unit packet and aggregated level UIs |
|
|
upUIs |
List of unit packet level UIs subject to the trans-loading |
upUI(L) |
M |
M, if UI_Type = 1 or 3 |
|
|
|
aUIs |
List of aggregated level UIs subject to the trans-loading |
aUI |
M |
M, if UI_Type = 2 or 3 |
|
|
|
Transloading_comment |
Comments by the reporting entity |
Text |
S |
O |
|
3.6. Disaggregation of aggregated level UIs
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
3-6 |
|
|
EO_ID |
Economic operator's identifier |
EOID |
S |
M |
|
|
|
F_ID |
Facility's identifier |
FID |
S |
M |
|
|
|
Event_Time |
Time of event occurrence |
Time(s) |
S |
M |
|
|
|
aUI |
Aggregated level UI subject to disaggregation |
aUI |
S |
M |
|
|
|
disaUI_comment |
Comments by the reporting entity |
Text |
S |
O |
|
3.7. Report of delivery carried out with a vending van to retail outlet (required if in message type 3-3, field Destination_ID1 = 4)
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
3-7 |
|
|
EO_ID |
Economic operator identifier code of the submitting entity |
EOID |
S |
M |
|
|
|
F_ID |
Facility identifier code of retail outlet |
FID |
S |
M |
|
|
|
Event_Time |
Time of event occurrence |
Time(s) |
S |
M |
|
|
|
UI_Type |
Identification of UI types delivered (recorded at the highest level of available aggregation) |
Integer |
S |
M |
1 – only unit packet level UIs 2 – only aggregated level UIs 3 – both unit packet and aggregated level UIs |
|
|
upUIs |
List of unit packet level UIs delivered |
upUI(L) |
M |
M, if UI_Type = 1 or 3 |
|
|
|
aUIs |
List of aggregated level UIs delivered |
aUI |
M |
M, if UI_Type = 2 or 3 |
|
|
|
Delivery_comment |
Comments by the reporting entity |
Text |
S |
O |
|
3.8. Dispatch of tobacco products from a facility to laboratories, waste disposal centres, national authorities, international governmental organisations, embassies and military bases
|
Item # |
Field |
Comments |
Data Type |
Cardi-nality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
3-8 |
|
|
EO_ID |
Economic operator identifier code of the submitting entity |
EOID |
S |
M |
|
|
|
Event_Time |
Intended time of event occurrence |
Time(s) |
S |
M |
|
|
|
F_ID |
Dispatch facility identifier code |
FID |
S |
M |
|
|
|
Destination_1 |
Indication of destination type |
Integer |
S |
M |
1 – Laboratory 2 – Waste disposal centre 3 – National authority 4 – International governmental organisation 5 – Embassy 6 – Military base |
|
|
Destination_2 |
Destination’s street name and house number (or road number and kilometre) |
Text |
S |
M |
|
|
|
Destination_3 |
Destination’s municipality (city, town or village) |
Text |
S |
M |
|
|
|
Destination_4 |
Destination’s postal code |
Text |
S |
M |
‘n/a’ is permitted value if no postal code has been assigned |
|
|
Destination_5 |
Destination’s country |
Country |
S |
M |
|
|
|
Transport_mode |
Mode of transport by which the product leaves the facility, see Annex II, Code List 7 of Regulation (EC) No 684/2009 |
Integer |
S |
M |
0 – Other 1 – Sea Transport 2 – Rail transport 3 – Road transport 4 – Air transport 5 – Postal consignment 6 – Fixed transport installations 7 – Inland waterway transport |
|
|
Transport_vehicle |
Identification of the vehicle (i.e. number plates, train number, plane/flight number, ship name or other identification) |
Text |
S |
M |
‘n/a’ is permitted value if Transport_mode = 0 and product movement takes place between adjacent facilities and is delivered manually |
|
|
Transport_cont1 |
Indication if the transport is containerised and uses an individual transport unit code (e.g. SSCC) |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
Transport_cont2 |
Individual transport unit code of the container |
ITU |
S |
M, if Transport_cont1 = 1 |
|
|
|
UI_Type |
Identification of UI types in the dispatch (recorded at the highest level of available aggregation) |
Integer |
S |
M |
1 – only unit packet level UIs 2 – only aggregated level UIs 3 – both unit packet and aggregated level UIs |
|
|
upUIs |
List of unit packet level UIs subject to the dispatch |
upUI(L) |
M |
M, if UI_Type = 1 or 3 |
|
|
|
aUIs |
List of aggregated level UIs subject to the dispatch |
aUI |
M |
M, if UI_Type = 2 or 3 |
|
|
|
S_Dispatch_comment |
Comments by the reporting entity |
Text |
S |
O |
|
SECTION 4
Transactional events
4.1. Issuing of the invoice
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
4-1 |
|
|
EO_ID |
Economic operator identifier code of the submitting entity |
EOID |
S |
M |
|
|
|
Event_Time |
Time of event occurrence |
Time(s) |
S |
M |
|
|
|
Invoice_Type1 |
Type of the invoice |
Integer |
S |
M |
1 – Original 2 – Correction 3 – Other |
|
|
Invoice_Type2 |
Description of the other type of the invoice |
Text |
S |
M, if Invoice_Type1 = 3 |
|
|
|
Invoice_Number |
Number of the invoice |
Text |
S |
M |
|
|
|
Invoice_Date |
Date of the invoice |
Date |
S |
M |
|
|
|
Invoice_Seller |
Identity of the seller |
EOID |
S |
M |
|
|
|
Invoice_Buyer1 |
Indication if the buyer is located in the EU |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
Invoice_Buyer2 |
Identity of the buyer |
EOID |
S |
M, if Invoice_Buyer1 = 1 |
|
|
|
Buyer_Name |
Buyer's registered legal name |
Text |
S |
M, if Invoice_Buyer1 = 0 |
|
|
|
Buyer_Address_1 |
Buyer’s street name and house number (or road number and kilometre) |
Text |
S |
M, if Invoice_Buyer1 = 0 |
|
|
|
Buyer_Address_2 |
Buyer’s municipality (city, town or village) |
Text |
S |
M, if Invoice_Buyer1 = 0 |
|
|
|
Buyer_Address_3 |
Buyer’s postal code |
Text |
S |
M, if Invoice_Buyer1 = 0 |
‘n/a’ is permitted value if no postal code has been assigned |
|
|
Buyer_CountryReg |
Buyer's country of registration |
Country |
S |
M, if Invoice_Buyer1 = 0 |
|
|
|
Buyer_TAX_N |
Buyer's tax registration number |
Text |
S |
M, if Invoice_Buyer1 = 0 |
|
|
|
First_Seller_EU |
Indication if the invoice is issued by the first seller in the EU, i.e. the EU manufacturer or the importer, and the product is destined for the EU market |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
Product_Items_1 |
List of TPIDs corresponding to the product items listed on the invoice |
TPID |
M |
M, if First_Seller_EU = 1 |
|
|
|
Product_Items_2 |
List of product numbers corresponding to the product items listed on the invoice (in the same order as Product_Items_1) |
PN |
M |
M, if First_Seller_EU = 1 |
|
|
|
Product_Price |
Net unit packet price per each pair of TPID and product number (in the same order as Product_ Items_1) |
Decimal |
M |
M, if First_Seller_EU = 1 |
|
|
|
Invoice_Net |
Total net amount of the invoice |
Decimal |
S |
M |
|
|
|
Invoice_Currency |
Currency of the invoice |
Currency |
S |
M |
|
|
|
UI_Type |
Identification of UI types covered by the invoice (recorded at the highest level of available aggregation) |
Integer |
S |
M |
1 – only unit packet level UIs 2 – only aggregated level UIs 3 – both unit packet and aggregated level UIs |
|
|
upUIs |
List of unit packet level UIs covered by the invoice |
upUI(L) |
M |
M, if UI_Type = 1 or 3 |
|
|
|
aUIs |
List of aggregated level UIs covered by the invoice |
aUI |
M |
M, if UI_Type = 2 or 3 |
|
|
|
Invoice_comment |
Comments by the reporting entity |
Text |
S |
O |
|
4.2. Issuing of the order number
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
4-2 |
|
|
EO_ID |
Economic operator identifier code of the submitting entity |
EOID |
S |
M |
|
|
|
Event_Time |
Time of event occurrence |
Time(s) |
S |
M |
|
|
|
Order_Number |
Number of the purchase order |
Text |
S |
M |
|
|
|
Order_Date |
Date of the purchase order |
Date |
S |
M |
|
|
|
UI_Type |
Identification of UI types covered by the purchase order (recorded at the highest level of available aggregation) |
Integer |
S |
M |
1 – only unit packet level UIs 2 – only aggregated level UIs 3 – both unit packet and aggregated level UIs |
|
|
upUIs |
List of unit packet level UIs covered by the purchase order |
upUI(L) |
M |
M, if UI_Type = 1 or 3 |
|
|
|
aUIs |
List of aggregated level UIs covered by the purchase order |
aUI |
M |
M, if UI_Type = 2 or 3 |
|
|
|
Order_comment |
Description of the reason for delayed recording of the purchase order |
Text |
S |
O |
|
4.3. Receipt of the payment
|
Item # |
Field |
Comments |
Data Type |
Cardinality |
Priority |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
4-3 |
|
|
EO_ID |
Economic operator identifier code of the submitting entity |
EOID |
S |
M |
|
|
|
Event_Time |
Time of event occurrence |
Time(s) |
S |
M |
|
|
|
Payment_Date |
Date of the payment receipt |
Date |
S |
M |
|
|
|
Payment_Type |
Type of payment |
Integer |
S |
M |
1 – bank transfer 2 – bank card 3 – cash 4 – other |
|
|
Payment_Amount |
Amount of the payment |
Decimal |
S |
M |
|
|
|
Payment_Currency |
Currency of the payment |
Currency |
S |
M |
|
|
|
Payment_Payer1 |
Indication if the payer is located in the EU |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
Payment_Payer2 |
Identity of the payer |
EOID |
S |
M, if Payment_Payer1 = 1 |
|
|
|
Payer_Name |
Payer's registered legal name |
Text |
S |
M, if Payment_Payer1 = 0 |
|
|
|
Payer_Address_1 |
Payer’s street name and house number (or road number and kilometre) |
Text |
S |
M, if Payment_Payer1 = 0 |
|
|
|
Payer _Address_2 |
Payer’s municipality (city, town or village) |
Text |
S |
M, if Payment_Payer1 = 0 |
|
|
|
Payer _Address_3 |
Payer’s postal code |
Text |
S |
M, if Payment_Payer1 = 0 |
‘n/a’ is permitted value if no postal code has been assigned |
|
|
Payer_CountryReg |
Payer's country of registration |
Country |
S |
M, if Payment_Payer1 = 0 |
|
|
|
Payer_TAX_N |
Payer's tax registration number |
Text |
S |
M, if Payment_Payer1 = 0 |
|
|
|
Payment_Recipient |
Identity of the recipient |
EOID |
S |
M |
|
|
|
Payment_Invoice |
Indication if the payment corresponds to the existing invoice |
Boolean |
S |
M |
0 – No 1 – Yes |
|
|
Invoice_Paid |
Number of the invoice paid with the payment |
Text |
S |
M, if Payment_Invoice = 1 |
|
|
|
UI_Type |
Identification of UI types covered by the payment (recorded at the highest level of available aggregation) |
Integer |
S |
M, if Payment_Invoice = 0 |
1 – only unit packet level UIs 2 – only aggregated level UIs 3 – both unit packet and aggregated level UIs |
|
|
upUIs |
List of unit packet level UIs covered by the payment |
upUI(L) |
M |
M, if Payment_Invoice = 0 and UI_Type = 1 or 3 |
|
|
|
aUIs |
List of aggregated level UIs covered by the payment |
aUI |
M |
M, if Payment_Invoice = 0 and UI_Type = 2 or 3 |
|
|
|
Payment_comment |
Comments by the reporting entity |
Text |
S |
O |
|
SECTION 5
Recalls
5. Recalls of requests, operational and transactional messages (possible for message types 2-1, 2-2, 2-3 (only within 24 hours from the original reporting of message 2-3, for Deact_Reason1 other than ‘2 – Product stolen’), 3-1 to 3-8, 4-1, 4-2 and 4-3)
|
Item # |
Field |
Comments |
Data Type |
Cardi-nality |
Prioritt |
Values |
|
|
Message_Type |
Identification of message type |
Text |
S |
M |
5 |
|
|
EO_ID |
Economic operator identifier code of the submitting entity |
EOID |
S |
M |
|
|
|
Recall_CODE |
Message recall code provided to the message sender in the acknowledgement of the original message to be recalled |
Text |
S |
M |
Recall_CODE |
|
|
Recall_ Reason1 |
Reason for recalling the original message |
Integer |
S |
M |
1 – reported event did not materialise (only for message types 3-3, 3-5 and 3-8) 2 – message contained erroneous information 3 – other |
|
|
Recall_ Reason2 |
Description of the reason for recalling the original message |
Text |
S |
M, if Recall_ Reason1 = 3 |
|
|
|
Recall_ Reason3 |
Any additional explanations on the reason for recalling the original message |
Text |
S |
O |
|
|
Notice: A recall with respect to operational and logistic events results in flagging the recalled message as cancelled but does not lead to the deletion of the existing database record. |
||||||
ANNEX III
Structure of a unit-level unique identifier
|
|
(1) |
(2) |
(3) |
(4) |
(5) |
(6) |
(7) |
(8) |
(9) |
|
Element: |
Symbology identifier |
Mandatory data qualifier |
ID issuer’s identification code |
Optional data qualifier |
Serial number |
Optional data qualifier |
Product code |
Optional data qualifier |
Time stamp |
|
Type: |
Qualifier |
Qualifier |
String (data element) |
Qualifier |
String (data element) |
Qualifier |
String (data element) |
Qualifier |
String (data element) |
|
Position within the unique identifier: |
Fixed |
Fixed |
Fixed |
Non-fixed |
Non-fixed |
Non-fixed |
Non-fixed |
Fixed |
Fixed |
|
Regulated by: |
Art. 21(1) and ID issuer’s coding structure |
Art.3(4), Art.8(1)(a), Art. 21(1) and ID issuer’s coding structure |
Art.3(4) and Art.8(1)(a) |
Art. 21(1) and ID issuer’s coding structure |
Art.8(1)(b) |
Art. 21(1) and ID issuer’s coding structure |
Art.8(1)(c) |
Art. 21(1), Art. 21(4) and ID issuer’s coding structure |
Art.8(1)(d) and Art.21(4) |
|
Applicable international standards: |
ISO/IEC 16022:2006, or ISO/IEC 18004:2015, or ISS DotCode Symbology Spec. |
ISO 15459-2:2015 and ISO 15459-3:2014 |
ISO 15459-2:2015 and ISO 15459-3:2014 |
|
|
|
|
|
|
|
Process: |
Applied by economic operators |
Applied by economic operators |
Generated by ID issuers |
Applied by economic operators |
Generated by ID issuers |
Applied by economic operators |
Generated by ID issuers |
Applied by economic operators |
Applied by economic operators |
|
Transmission to the repositories system: |
No |
No |
Yes |
No |
Yes |
No |
Yes |
No |
Yes |
|
Note: For the purpose of the above schema, group separators (/FNC1) are considered in the same manner as optional data qualifiers, i.e. their use depends on the ID issuer’s coding structure. |
|||||||||
( 1 ) Commission Recommendation of 6 May 2003 concerning the definition of micro, small and medium-sized enterprises (OJ L 124, 20.5.2003, p. 36).
( 2 ) Commission Delegated Regulation (EU) 2018/573 of 15 December 2017 on key elements of data storage contracts to be concluded as part of a traceability system for tobacco products (see page 1 of this Official Journal).