Commission Implementing Regulation (EU) 2025/1290 of 2 July 2025 laying down rules for the application of Regulation (EU) 2024/1157 of the European Parliament and of the Council as regards the requirements necessary for the interoperability between the central system for the electronic submission and exchange of information and documents related to shipments of waste and other systems or software, as well as other technical and organisational requirements necessary for the practical implementation of such electronic submission and exchange of information and documents
CHAPTER 1 — GENERAL PROVISIONS
Subject matter
This Regulation establishes the requirements necessary for the interoperability between the central system for the electronic submission and exchange of data, information and documents related to shipments of waste, as referred to in Article 27(3) of Regulation (EU) 2024/1157, and other systems or software.
It also lays down other technical and organisational requirements necessary for the practical implementation of such electronic submission and exchange of information and documents pursuant to that Regulation.
Definitions
1. The definitions set out in Article 3 of Regulation (EU) 2024/1157 shall apply.
2. For the purposes of this Regulation, the following definitions apply:
(1)
‘central system’ means a digital system for shipments of waste referred to in Article 27(3) of Regulation (EU) 2024/1157 and operated by the Commission;
(2)
‘local system’ means a system that is operated by a competent authority in accordance with Article 27(4) of Regulation (EU) 2024/1157 and that connects with the central system through an API;
(3)
‘systems’ means the central system and the local systems;
(4)
‘software’ means any software other than the central system or local system, which is used for the purpose of submitting and exchanging information and documents referred to in Article 27(1) of Regulation (EU) 2024/1157 and that connects with the central system via an API;
(5)
‘inspection system’ means a system that is operated by an inspection authority in a Member State or by the Commission, for the purposes of retrieving information and documents referred to in Article 27(1) of Regulation (EU) 2024/1157 and that connects with the central system through an API;
(6)
‘Graphical User Interface’ or ‘GUI’ means the visual interface used to access the central system directly through a website that is operated by the Commission as a part of the central system;
(7)
‘Application Programming Interface’ or ‘API’ means the technical interface used for machine-to-machine connection, that allows access to the central system;
(8)
‘eFTI platform’ means eFTI platform as defined in Article 3, point (10), of Regulation (EU) 2020/1056 of the European Parliament and of the Council ( 10 ) ;
(9)
‘movement document number’ means the number assigned in the systems to a specific submission of information in accordance with the movement document set out in Annex IB to the Regulation (EU) 2024/1157;
(10)
‘Annex VII document number’ means the number assigned in the systems to a specific submission of information in accordance with the form set out in Annex VII of Regulation (EU) 2024/1157;
(11)
‘user’ means any natural person using the central system, local system or other software;
(12)
‘Economic Operator Registration and Identification number (EORI number)’ means ‘Economic Operator Registration and Identification number (EORI number)’ as defined in Article 1, point (18), of Commission Delegated Regulation (EU) 2015/2446 ( 11 ) ;
(13)
‘operator’ means any natural or legal person, who carries out, plans to carry out or is involved in carrying out a shipment of waste, and acts as a notifier, a person who arranges a shipment, a carrier, a consignee, a waste producer or a waste management facility, irrespective of whether this person acts in a professional capacity or not, excluding competent authorities and authorities involved in inspections;
(14)
‘site’ means a location of an operator having a different address or name from the address or name indicated by such operator during their first registration in the systems or software, that is allowed under the respective national law to use the same main identification number as the operator concerned;
(15)
‘authorities’ means the competent authorities defined in Article 3, point (9), of Regulation (EU) 2024/1157 and authorities involved in inspections;
(16)
‘working day’ means any day from Monday to Friday excluding 1 January, 1 May, 15 August, 1 November, 25 December, 26 December.
Ownership and responsibilities for data, information and documents
Each user shall own and be responsible for the data, information and documents this user inserts or produces in the systems. Competent authorities shall own and be responsible for the data, information and documents inserted or produced on their behalf by users authorised to perform competent authority’s role in the systems.
In addition to the provisions of the first paragraph, national laws regulating liability of individuals acting on behalf of any natural or legal person, including competent authorities shall also apply.
Declaration on how to access the central system
1. By 3 February 2026, competent authorities shall declare to the Commission how they and users representing operators with a registered office in their Member State shall access the central system. For the purposes of such declaration, the competent authorities shall complete the form set out in Annex I to this Regulation.
2. After the date referred to in paragraph 1, a competent authority may change the declaration, in which case this authority shall submit to the Commission the revised declaration. The new rules on how to access the central system, indicated in the revised declaration shall start to apply 20 working days after the submission of the revised declaration, provided that the conditions set out in Articles 5 and 11 are met, unless the competent authority indicates, in the revised declaration, a specific date after 20 working days from the submission of the revised declaration.
3. A competent authority may indicate in the declaration referred to in paragraph 1 that this authority uses its local system only for the purpose of exchanging data, information and documents concerning the following:
(a)
shipments of waste referred to in Article 4(1), (2) and (3) of Regulation (EU) 2024/1157;
(b)
shipments of waste referred to in Article 4(4) and (5) of Regulation (EU) 2024/1157;
(c)
approving and refusing the requests of recovery facilities for pre-consent, as well as revoking pre-consents referred to in Article 14(8) and (10) of Regulation (EU) 2024/1157.
4. Where, in its declaration, a competent authority includes the indication referred to in paragraph 3 of this Article, local system operated by this authority shall not be required to comply with the following requirements of this Regulation:
(a)
Article 11(5) and (12), Article 15(5) and Article 16 where the declaration is made pursuant to paragraph 3, point (a) of this Article;
(b)
Article 11(5) and (12), Article 15(1) to (4), Article 15(6) to (8), Article 16, Article 17(5) to (11) and Article 17(13) and (14), where the declaration is made pursuant to paragraph 3, point (b) of this Article;
(c)
Article 10, Article 11(5) and (12), Article 14, Article 15, Article 17(2), (3) and (5) to (14), where the declaration is made pursuant to paragraph 3, point (c) of this Article.
User access obligations
1. Users who represent operators or competent authorities acting in the roles referred to in Article 10(1), first subparagraph, points (a), (b) and (c) and points (e) to (g) shall only access the central system in the manner indicated in the declaration of the competent authority referred to in Article 4(1).
2. Users who represent operators acting only in the role referred to in Article 10(1), first subparagraph, point (d) shall access the central system through GUI or using an eFTI platform interconnected with the central system through an API.
3. Users who represent authorities involved in inspections acting in the role referred to in Article 10(1), first subparagraph, point (h) may access the central system in one of the following ways:
(a)
through GUI;
(b)
using an inspection system or Authority Access Point, as defined in Article 1, point (11), of Commission Implementing Regulation (EU) 2024/1942 ( 12 ) , that are interconnected with the central system through an API, where the requirements mentioned in Article 11(5), first subparagraph, are fulfilled;
(c)
using an inspection system interconnected to an eFTI Gate, as defined in Article 1, point (12), of Implementing Regulation (EU) 2024/1942, that is interconnected to the central system through an API, where the requirements mentioned in Article 11(5), first subparagraph, are fulfilled.
4. Notwithstanding the provisions of paragraphs 1, 2 and 3, users representing operators may access the central system through API using software that allows such a connection under the following conditions:
(a)
the software complies with the relevant requirements of this Regulation;
(b)
it is indicated by a competent authority in the declaration submitted in accordance with Article 4(1) for exchanges of information and documents concerning shipments of waste, or certain shipments of waste.
5. Where the competent authority declares that this authority accesses the central system through the API, users representing that authority may still access the central system through GUI for the purposes of the following activities:
(a)
API configuration;
(b)
verification of whether the local system correctly interoperates with the central system.
User registration
1. Each user shall create a personal account in the system that this user uses to access the central system in accordance with Article 5 and Article 11(9).
2. Access to the data and information in the central system shall only be possible where a user represents operators or authorities. Each user may:
(a)
represent one or more operators;
(b)
represent one competent authority;
(c)
represent one authority involved in inspections;
(d)
represent a competent authority and an authority involved in inspections;
(e)
not represent any authority if it represents an operator.
3. The central system shall differentiate between the following types of users:
(a)
users that are authorised to add further users or remove users within an operator or an authority, referred to as master users;
(b)
users that are not authorised to add further users or remove users within an operator or an authority, referred to as standard users.
4. Master users shall, when authorising a new user to represent an operator or an authority, determine whether the newly added user is a master user or a standard user.
5. Each operator shall have at least one master user and each authority shall have at least two master users to ensure service in cases of absence of one of the master users.
Registration of operators and sites in the central system
1. Where an operator or one of sites of the operator involved in the shipment of waste is not registered in the central system, the user representing them shall provide to the competent authority of the Member State in which the operator concerned has a registered office, the data regarding that operator that are set out in Annex II, Part E, point 2 and shall request for the operator or the site of the operator concerned to be registered in the central system.
2. The competent authority referred to in paragraph 1 shall, no later than five working days from the receipt of the request referred to in paragraph 1, verify the information received and take one of the following actions:
(a)
register the operator, or the site of the operator, and authorise the first user to represent the operator or site concerned;
(b)
ask for additional information;
(c)
refuse the registration.
3. The competent authority referred to in paragraph 1 shall review the additional information received in accordance with paragraph 2, point (b), within three working days and shall take one of the following actions:
(a)
register the operator, or the site of the operator, and authorise the first user to represent the operator or site concerned;
(b)
refuse the registration.
4. The competent authority referred to in paragraph 1 shall inform the operator, or the site of the operator, of the action taken pursuant to paragraph 3 no later than five working days from the receipt of the request referred to in paragraph 1 or no later than three working days after having received the additional information pursuant to paragraph 2, point (b).
Where the competent authority refuses the registration of the operator, or the site of the operator, it shall inform the user requesting that registration about the reasons for the refusal.
5. Where the competent authority referred to in paragraph 1 authorises the first user to represent the operator or site concerned, such authorised user shall be a master user.
6. Where an operator based in a third country not connected to the central system is not registered in the central system, the Member State’s competent authority which in the context of a notification would act as competent authority of dispatch or destination, respectively, shall register the operator concerned based in the third country in the central system. The registration shall be performed at the request of the operator intending to act as a notifier or waste receiving facility, respectively, by recording in the central system the data of the operator referred to in Annex II Part E, point 2.
7. When registering operators in the central system, the competent authorities shall only verify whether the operator concerned exists and whether the user claiming to represent it is entitled to represent the operator concerned.
When registering a site of an operator in the central system, the competent authority shall, in addition to the information indicated in the first subparagraph, verify whether the site is actually linked with the operator concerned.
8. Where a Member State has more than one competent authority, that Member State shall lay down rules on the division of competences between the competent authorities carrying out the registration of operators having a registered office in the territory of that Member State in the central system.
9. Where there is more than one competent authority in a Member State, the user representing an operator having a registered office in the territory of that Member State, shall indicate which of the competent authorities is competent for the registration of the operator in accordance with the applicable national rules referred to in paragraph 8.
Registration of authorities in the central system
1. Where an authority of a Member State is not registered in the central system, users representing that authority shall request the registration of that authority and provide the Commission with the relevant information of that authority and indicate whether that authority is a competent authority or an authority involved in inspections.
2. The Commission shall, no later than five working days from the receipt of such request, verify the information received pursuant to paragraph 1 and take one of the following actions:
(a)
register the authority, authorise the authority to act in one or more of roles referred to Article 10(3) and (4) and authorise the first user to represent the authority concerned;
(b)
ask for additional information;
(c)
refuse the registration.
3. The Commission shall review the additional information received in accordance with paragraph 2, point (b), within three working days and shall take one of the following actions:
(a)
register the authority, authorise the authority to act in one or more of roles referred to Article 10(3) and (4) and authorise the first user to represent the authority concerned;
(b)
refuse the registration.
4. The Commission shall inform the authority of the decision on registration no later than five working days from the receipt of the request referred to in paragraph 1 or no later than three working days from the receipt of the information referred to in paragraph 2, point (b).
5. Where the Commission has authorised the first user to represent the authority concerned, such authorised user shall be a master user.
6. Where a competent authority of a third country not connected to the central system is not registered in the central system, the Commission shall register that competent authority in the central system no later than five working days from the receipt of request to register such authority.
The registration request shall be submitted by Member State’s competent authority which in the context of a notification would act as competent authority of dispatch, transit or destination, respectively. The competent authority of that Member State shall contact the Commission following a request of the operator that intends to export waste to such third country or to import from such third country and shall ensure the correctness of the information provided to the Commission.
CHAPTER 2 — REQUIREMENTS FOR INTEROPERABILITY BETWEEN THE CENTRAL SYSTEM AND LOCAL SYSTEMS OR SOFTWARE
Identification of operators and competent authorities in the systems
1. The systems and software shall identify operators on the basis of their main identification number.
2. Where the operator is registered for customs purposes pursuant to Article 9 of Regulation (EU) No 952/2013, the operator shall provide its EORI number as the main identification number under this Regulation.
3. Member States shall communicate, by 3 February 2026, to the Commission and to the operators what identification number shall be the main identification number for operators based in their Member State and not identified pursuant to paragraph 2. Member States shall also specify what registration numbers are required to be provided for purposes of registration in the systems or software.
4. The main identification number for operators based in third countries that are not required to register for customs purposes pursuant to Article 9 of Regulation (EU) No 952/2013, shall be another identification number, as provided by the legislation of the country, where this operator is based.
5. The systems and software shall allow for the identification of operators also on the basis of other identification numbers.
6. An operator may indicate in the systems or software whether it has one or more sites. Where an operator has one or more sites, the operator shall indicate whether and which of its sites is concerned by a given operation each time the operator acts in the systems or software.
7. The systems and software shall identify competent authorities based on their codes referred to in box 15 (b) of the form set out in Annex IA to Regulation (EU) 2024/1157.
8. The central system shall assign a specific code to the competent authority when the Commission authorises the first user to act on behalf of such authority. The code shall have the following characteristics:
(a)
be unique;
(b)
be prefixed with a two-letter country code of the country of dispatch in accordance with the ISO standard 3166-1 alpha-2 abbreviation list;
(c)
after the code referred to in point (b), comprise two numerical characters.
In cases referred to in Article 8(6), the specific code shall be assigned when the competent authority of the third country concerned is registered in the central system.
Roles
1. The systems shall allow operators and authorities to act in one or more of the following roles:
(a)
competent authority of:
(i)
dispatch;
(ii)
transit;
(iii)
destination;
(b)
waste producer;
(c)
notifier;
(d)
carrier;
(e)
consignee;
(f)
facility receiving waste;
(g)
person who arranges the shipment;
(h)
authority involved in inspections.
Software shall allow operators to act in one or more of the roles referred to in points (b), (c), and (e) to (g) of the first subparagraph.
2. Operators shall act in the systems or software in one or more of the roles referred to in paragraph 1, first subparagraph, points (b) to (g).
3. Competent authorities shall act in the systems in one or more of the roles referred to in paragraph 1, first subparagraph, point (a). Where relevant, competent authorities may also act in the systems in any of the roles referred to in paragraph 1, first subparagraph, points (b) to (g).
4. Authorities involved in inspections shall act in the systems in the role referred to in paragraph 1, first subparagraph, point (h).
5. The roles referred to in paragraph 1, first subparagraph, point (a) shall be assigned as follows, depending on the declaration of the competent authority on how to access the central system, submitted in accordance with Article 4(1):
(a)
access to the central system through GUI: assignment through the central system by the Commission;
(b)
access to the central system through API: assignment in a manner that the competent authority concerned considers appropriate.
6. The role referred to in paragraph 1, first subparagraph, point (h) shall be assigned through the central system by the Commission.
Interoperability testing process
1. The local systems shall be able to perform the operations set out in Annex II, in accordance with paragraphs 2 to 4 of this Article.
2. Where the competent authority indicates in the declaration referred to in Article 4(1) that the authority shall access the central system through an API with respect to the following actions, the local system operated by this authority shall be able to perform the following operations:
(a)
as regards the submission and exchange of information and documents concerning shipments of waste referred to in Article 4(1), (2) and (3) of Regulation (EU) 2024/1157, all operations marked as ‘PIC’ in the column ‘Waste shipment procedure’ in the table set out in Annex III to this Regulation;
(b)
as regards the submission and exchange of information and documents concerning shipments of waste referred to in Article 4(4) and (5) of Regulation (EU) 2024/1157, all operations marked as ‘Annex VII’ in the column ‘Waste shipment procedure’ in the table set out in Annex III to this Regulation;
(c)
as regards communicating decisions on pre-consenting the facilities or revocation of the pre-consent, all operations marked as ‘for pre-consented facilities’ in the column ‘Comments’ in the table set out in Annex III to this Regulation.
3. Where the competent authority indicates in the declaration referred to in Article 4(1) that the authority shall access the central system through an API, the following rules apply:
(a)
where the competent authority acts as competent authority of dispatch, the local system operated by this authority shall:
(i)
be required to perform all the operations marked as ‘CA’ and ‘CA dispatch’ in the column ‘Role of the user(s) performing operation’ in the table set out in Annex III to this Regulation;
(ii)
not be required to perform operations marked as ‘CA transit’ or ‘CA destination’ in the column ‘Role of the user(s) performing operation’ in the table set out in Annex III to this Regulation;
(b)
where the competent authority acts as competent authority of transit, the local system operated by this authority shall:
(i)
be required to perform all the operations marked as ‘CA’ and ‘CA transit’ in the column ‘Role of the user(s) performing operation’ in the table set out in Annex III to this Regulation;
(ii)
not be required to perform operations marked as ‘CA dispatch’ or ‘CA destination’ in the column ‘Role of the user(s) performing operation’ in the table set out in Annex III to this Regulation;
(c)
where the competent authority acts as competent authority of destination, the local system operated by this authority shall:
(i)
be required to perform all the operations marked as ‘CA’ and ‘CA destination’ in the column ‘Role of the user(s) performing operation’ in the table set out in Annex III to this Regulation;
(ii)
not be required to perform operations marked as ‘CA dispatch’ or ‘CA transit’ in the column ‘Role of the user(s) performing operation’ in the table set out in Annex III to this Regulation.
4. To facilitate the process of registration of users and authorising users to represent operators or their sites in the central system accessed through GUI, the local system of the competent authority responsible for such registration and authorisation may perform operations listed in Annex II Part G, where the competent authority indicates in the declaration referred to in Article 4(1) that:
(a)
users representing operators shall access the central system through the API using a local system for the purpose of the submission and exchange of information and documents concerning certain shipments of waste, while for the purpose of the submission and exchange of information and documents concerning other shipments of waste these users shall access the central system through GUI;
(b)
users representing operators shall access the central system through GUI and the competent authority shall access the central system through the API;
(c)
users representing operators can access the central system through the API using software and the competent authority shall access the central system through the API using a local system.
5. Inspection systems shall be required to perform the operations set out in Part F of Annex II to this Regulation relevant to the data that such system is intended to obtain from the central system.
Software shall be required to perform the operations set out in Annex II to this Regulation relevant to the scope of the functionalities it intends to offer.
6. The competent authority intending to access the central system through API shall perform tests confirming the ability of its local system to perform all the relevant operations referred to in Annex II or offer other functionalities implemented in the central system, where appropriate and relevant.
7. The tests referred to in paragraph 6 shall be completed at the latest 25 working days before the date from which the competent authority intends to access the central system through API.
8. The competent authority shall inform the Commission in writing whether the tests referred to in paragraph 6 were successfully completed or not.
9. Where the competent authority indicated in its declaration referred to in Article 4(1) that all users representing the operators referred to in Article 5(1) that have a registered office under the jurisdiction of that competent authority shall access the central system through local system, these users shall access the central system through GUI until that competent authority successfully completes the tests referred to in paragraph 6.
10. The competent authority referred to in paragraph 9 may further perform tests pursuant to paragraphs 7 and 8 to ensure the interoperability of the local system operated by this authority with the central system.
11. Where the tests referred to in paragraph 6 are successfully completed, the users referred to in paragraph 9 shall access the central system through API using the local system of the competent authority having jurisdiction over the operators represented by those users, in accordance with the competent authority’s declaration referred to in Article 4(1). That obligation shall apply after 25 working days from the date on which the competent authority provided the Commission with written confirmation of the successful completion of the tests. The competent authority may indicate in such confirmation a specific date falling after those 25 working days, in which case the users shall access the central system through API from that date.
12. Inspection systems and software may perform tests to confirm their ability to perform all the relevant operations referred to in paragraph 5 or other functionalities implemented in the central system, where appropriate and when relevant.
Protocol for exchange of data
1. Local systems shall use the protocol for exchange of data set out in Annex II for all relevant operations referred to in Article 11(1).
2. For the purposes of Article 5(4), the software shall use the protocol for exchange of data set out in Annex II for relevant operations.
Requirements for exchanging attached documents
The systems and software shall allow for exchange of attached documents only in accordance with the following conditions:
(a)
in the formats pdf, jpeg;
(b)
of a size not exceeding 32 MB per attachment.
Authentication of documents
1. All systems and software shall require their users to authenticate the following documents or elements:
(a)
as regards the notifier:
(i)
the notification document upon submission in accordance with Article 5 of Regulation (EU) 2024/1157 or upon submission of additional information and documentation in accordance with Article 8(3) and (8) of Regulation (EU) 2024/1157;
(ii)
the movement document set out in Annex IB to that Regulation (‘the movement document’) as completed in accordance with Article 16(2) of that Regulation;
(iii)
a request to change details or conditions related to a shipment in accordance with Article 17(1) of that Regulation;
(b)
as regards the competent authority:
(i)
the information it requests or provides in accordance with Article 8(1), (4) to (7), (9), (10) and (11) or (12) of Regulation (EU) 2024/1157, or where relevant its acknowledgment of receipt;
(ii)
any decision concerning a notification in accordance with Article 9 or Article 17(2) of that Regulation;
(c)
as regards the facility to which waste under a consented notification is shipped:
(i)
the receipt of the waste in accordance with Article 15(3) or Article 16(5) of Regulation (EU) 2024/1157;
(ii)
as appropriate, the certificates upon submission in accordance with Article 15(5) or Article 16(6) of that Regulation;
(d)
as regards the person who arranges the shipment:
(i)
the submission of the form set out Annex VII of Regulation (EU) 2024/1157 (‘Annex VII document’);
(ii)
the transfer of waste to a carrier;
(e)
as regards the facility to which waste subject to Article 18 of Regulation (EU) 2024/1157 is shipped:
(i)
the receipt of the waste in accordance with Article 18(8) of that Regulation;
(ii)
the certificates upon submission, as relevant, in accordance with Article 18(9) of that Regulation;
(f)
as regards the carrier: the taking over of the waste the carrier transports in accordance with box 8 of the movement document or in accordance with box 5 of the Annex VII document;
(g)
as regards the consignee: receipt of the waste in accordance with box 17 of the movement document or in accordance with box 13 of the Annex VII document;
(h)
as regards the original waste producer: the submission of the notification document as required pursuant to Article 5(2) of Regulation (EU) 2024/1157 and the Annex VII document as required pursuant to Article 18(4) of that Regulation.
2. The authentication referred to in paragraph 1 shall provide the following information:
(a)
date and time of authentication, accurate to seconds, including time zone code;
(b)
name and surname of the user performing the authentication;
(c)
function of the user performing the authentication of documents in the competent authority or for the operator, as appropriate.
3. All systems and software shall exchange the information referred to in paragraph 2 in accordance with Article 12.
4. All systems and software shall record and maintain audit logs containing the information set out in paragraph 2 and provide those logs upon request of the authorities.
Notification number, Annex VII document number, movement document number
1. Before a notifier submits a notification for shipments that start within the Union, the system or software the notifier is using shall allow for the generation of a notification number, in accordance with the provisions of paragraphs 2 and 3 of this Article.
2. For the generation of a notification number referred to in paragraph 1, the system or software used by the notifier shall require the notifier to provide the following information:
(a)
its name, address and main identification number;
(b)
name and address of its site, if applicable;
(c)
the country of dispatch;
(d)
the competent authority of dispatch.
3. A notification number for shipments where the country of dispatch is a Member State shall have the following characteristics:
(a)
be unique;
(b)
be prefixed with the code of the competent authority of dispatch concerned, referred to in Article 9(8);
(c)
after the prefix, indicate the two last digits of the calendar year, in which the notification number was generated;
(d)
consist of 12 characters;
(e)
where the number is generated in the central system, the last additional character shall be the letter ‘i’;
(f)
not contain blank spaces, letters other than those referred to in points (b) and (e), punctuation marks or other symbols.
4. Where waste is imported to the Union or transits through the Union from and to third countries, the systems or software shall perform the following functions:
(a)
verify whether the notification number complies with requirement set out in paragraph 3, point (a);
(b)
allow a user that submits all relevant information to the system pursuant to Article 51(2) point (b), Article 53(2) point (d), Article 57 or Article 58(1) and (2) of Regulation (EU) 2024/1157 to introduce in the system that the user uses the notification number attributed by the competent authority of dispatch.
5. Paragraph 3 of this Article shall apply to the attribution of numbers to Annex VII documents with the following modifications:
(a)
an Annex VII document number shall be generated when an Annex VII document is submitted;
(b)
each Annex VII document number shall be prefixed with ‘GLW’ followed by the code of the country of dispatch referred to in Article 9(8), point (b) of this Regulation, and the two last digits of the calendar year in which the Annex VII document was submitted;
(c)
Annex VII document number shall consist of 16 characters;
(d)
the abbreviation ‘GLW’ and the country code should be separated by a full stop.
6. Regarding shipments of waste referred to in Article 4(1), (2) or (3) of Regulation (EU) 2024/1157 that start within the Union, the systems or software shall assign a movement document number upon submission of a movement document. The movement document number shall have the following characteristics:
(a)
be unique;
(b)
start with the notification number of the notification document on the basis of which the movement document is prepared;
(c)
the notification number shall be followed by the movement document serial number referred to in box 2 of Annex IB to the Regulation (EU) 2024/1157;
(d)
the numbers referred to in points (b) and (c) shall be separated by a full stop;
(e)
not contain blank spaces, punctuation marks, letters other than those referred to in point (b) or symbols other than those referred to in point (d).
A movement document serial number shall be assigned by the systems or software when the movement document is submitted. It shall consist of 6 digits. Where relevant, that serial number shall be prefixed with one or more zeros.
7. Where waste is imported into the Union or transits through the Union from and to third countries, the systems shall perform the following functions:
(a)
verify whether the movement document number complies with the requirement set out in paragraph 6, point (a);
(b)
allow a notifier to introduce the movement document number attributed by the competent authority of dispatch in the third country in accordance with its national rules to the system the notifier uses.
8. Where waste is imported into the Union or transits through the Union from and to third countries, and where there are no national rules on the structure and assignment of movement document numbers in the country of dispatch and no such number was attributed to the movement document, the notifier shall introduce the movement document number in the system the notifier is using in accordance with the requirements referred to in paragraph 6.
9. A notification number, an Annex VII document number and a movement document number shall not be used again even where that submitted notification, Annex VII document or movement document was cancelled, withdrawn or otherwise ineffective.
Pre-consented facilities
1. The systems shall allow the competent authorities to submit the following information concerning pre-consented facilities, referred to in Article 14 of Regulation (EU) 2024/1157:
(a)
the name of the facility, the main identification number of the operator of that facility and address of the facility;
(b)
the name of the site and its address, if applicable;
(c)
the R-code or codes referred to in Annex II to Directive 2008/98/EC, for the recovery operation or operations for which the pre-consent is issued;
(d)
the waste identification code or codes for the wastes for which the pre-consent is issued and the total pre-consented quantity of such waste;
(e)
the start and end date of validity of the pre-consent;
(f)
information about whether the pre-consent was revoked wholly or partially, together with the date from which the revocation is effective;
(g)
a copy of a decision on the pre-consent.
2. The systems shall make the information referred to in paragraph 1 available for all the users.
3. The systems and software shall allow the notifiers, when submitting the notification, to indicate whether the shipment is destined to a pre-consented facility.
Where the notifier indicates that the shipment is destined to a pre-consented facility, the systems shall apply the procedures set out in Article 14(12) and (14) to (16) of Regulation (EU) 2024/1157. The competent authority concerned may refuse to apply such procedures, in which case the systems shall allow the competent authorities to inform about such refusal.
Functionalities of the systems
1. The systems, and where relevant, software shall have all the functionalities referred to in this Article.
2. Where in the notification document or the Annex VII document the operator indicates the same entity for the ‘importer – consignee’ and the ‘facility’ to which waste is shipped, the systems shall not allow the execution of the following operations referred to in Annex II, Parts B and C:
(a)
‘submit consignee reception confirmation’;
(b)
‘update consignee reception confirmation’;
(c)
‘submit consignee reception confirmation – Annex VII document’;
(d)
‘update consignee reception confirmation – Annex VII document’.
3. The systems shall allow users performing the operations ‘submit new notification’, ‘update notification’, ‘submit movement document’, ‘update movement document’, ‘submit Annex VII document’ and ‘update Annex VII document’, where relevant, referred to in Annex II to this Regulation to insert multiple entries regarding the following:
(a)
carriers, as indicated in box 8 of Annexes IA and IB to Regulation (EU) 2024/1157, and box 5 of Annex VII to Regulation (EU) 2024/1157;
(b)
facilities receiving waste after an interim waste treatment operation;
(c)
waste producers;
(d)
waste identification lists and codes;
(e)
customs codes (HS) and commodity codes;
(f)
packaging types codes;
(g)
physical characteristics codes;
(h)
recovery operation codes or disposal operation codes;
(i)
countries of transit, competent authorities of transit and custom offices of transit.
4. The systems shall allow users performing operations ‘create operator’ and ‘update operator’ referred to in Annex II Part E to this Regulation to insert multiple entries regarding the following:
(a)
registration numbers of operators or sites;
(b)
other identifiers of operators or sites.
5. The systems shall require the provision of a separate facility reception confirmation for each movement document submitted. The provisions of this paragraph shall apply as appropriate to consignee reception confirmations and to facility completion certificates.
6. The systems shall ensure that data in movement documents corresponds to the respective data in the notification document in the following manner:
(a)
information in box 3 of the movement document shall be identical as information in box 1 of the notification document;
(b)
information in box 4 of the movement document shall be identical as information in box 2 of the notification document;
(c)
information in box 7 of the movement document shall be completed by indicating types of packaging in a way compliant with information listed in box 7 of the notification document;
(d)
information in box 7 of the movement document concerning the special handling requirements shall be identical as information in box 7 of the notification document in that regard;
(e)
information in box 8 of the movement document shall be completed by indicating one of the operators in listed in box 8 of the notification document;
(f)
information in box 9 of the movement document shall be identical as information in box 9 of the notification document;
(g)
information in box 10 of the movement document shall be identical as information in box 10 of the notification document;
(h)
information in box 11 of the movement document shall be identical as information on D-code/R-code in box 11 of the notification document;
(i)
information in box 12 of the movement document shall be identical as information in box 12 of the notification document;
(j)
information in box 13 of the movement document shall be identical as information in box 13 of the notification document;
(k)
information in box 14 of the movement document shall be identical as information in box 14 of the notification document.
Where new data that is not included in the notification document is to be added to the movement documents, the consignee reception confirmations, the facility reception confirmations or the facility completion certificates, the systems shall require that the notification document be first updated with such new data.
7. The systems shall not generate more movement documents than the total number of shipments indicated in box 4 of the corresponding notification document or in the conditions attached to the consent of any of the competent authorities concerned, if those conditions specify a smaller number than that indicated in the notification document.
8. Where a movement document is cancelled and the shipment covered by such movement document does not take place, such cancelled movement document shall not be counted in the systems towards the number of movement documents, referred to in paragraph 7, that can be generated following a notification.
9. Where the notifier indicates in the notification document that it intends to carry out an ‘individual shipment’, the systems shall only allow to indicate ‘1’ in box 4 of the notification document.
Where the notifier indicates in the notification document that it intends to carry out ‘multiple shipments’, the systems shall only allow to indicate numbers greater than 1 in box 4 of the notification document.
10. The systems shall allow the notifier to indicate in the movement documents only the quantity of waste to be shipped that is equal or less than the value of the ‘total intended quantity of waste’ referred to in box 5 of the notification document or in conditions attached to the consent of any of the competent authorities concerned, if these conditions specify lower quantity than indicated in the notification document.
11. The systems shall only allow the competent authorities to perform the operation ‘update decision’ referred to in Annex II, Part A, in relation to decisions they submitted in accordance with Article 9(1) of Regulation (EU) 2024/1157 in the following manner:
(a)
‘consent’ may be updated to ‘objection’ or ‘withdrawn’;
(b)
‘objection’ may be updated only to ‘consent’;
(c)
conditions referred to in Article 9(1), point (b), of Regulation (EU) 2024/1157 may be added, modified or removed.
12. The systems shall only allow users that represent the competent authority who submitted the request to perform the operations ‘update take-back request’ and ‘update take-back request – Annex VII document’, referred to in Annex II Parts B and C.
13. The systems shall consider, and duly mark, the notification as properly completed in accordance with Article 8(11) of Regulation (EU) 2024/1157 by the competent authority of transit, in the following cases:
(a)
the competent authority of transit did not submit a request for additional information and documentation within the timeline referred to in Article 8(7) of Regulation (EU) 2024/1157;
(b)
the competent authority of destination indicated that the notification is properly completed in accordance with Article 8(12) of Regulation (EU) 2024/1157;
(c)
the competent authority of dispatch indicated that the notification is properly carried out in accordance with Article 8(6) of Regulation (EU) 2024/1157.
14. Where the notifier requests a change in the consented notification in accordance with Article 17(1) of Regulation (EU) 2024/1157, the systems and software shall presume that the consent for such a change was agreed by all the competent authorities, in accordance with Article 17(2) of Regulation (EU) 2024/1157, only where all the competent authorities concerned indicated in the systems that they agree with the requested change.
Where there is agreement pursuant to the first subparagraph, the competent authority of dispatch shall introduce in the systems the agreed change in the consented notification.
In case of import of waste to the Union, the change shall be introduced in the systems by the competent authority of destination. Where waste transits through the Union, the change shall be introduced by the competent authority of transit of the first Member State through which that waste transits.
CHAPTER 3 — REQUIREMENTS FOR THE PRACTICAL IMPLEMENTATION OF THE ELECTRONIC SUBMISSION AND EXCHANGE OF INFORMATION AND DOCUMENTS
Access requirements
1. Each operator shall have access to the information and documents they submitted or manage through the systems or software.
2. Each operator acting in the systems or software in the role of a waste producer, a notifier, a consignee or a facility receiving waste shall have access to the information and documents concerning shipments of waste referred to in in Article 4(1), (2) and (3) of Regulation (EU) 2024/1157 in which they are involved.
3. Each operator acting in the systems or software in the role of a waste producer, a person who arranges the shipment, a consignee or a facility receiving waste shall have access to the information and documents concerning shipments of waste referred to in Article 4(4) or (5) of Regulation (EU) 2024/1157 in which they are involved.
4. Each operator acting in the central system or software in the role of carrier shall have access to the following documents and information:
(a)
notification documents in which this operator is indicated as carrier, after all relevant competent authorities provide their consent, where relevant;
(b)
consents, including the attached conditions, where relevant, of the competent authorities referred to in point (a);
(c)
movement documents created on the basis of the notification documents referred to in point (a);
(d)
Annex VII documents in which this operator is indicated as a carrier, after they are authenticated by the person who arranges the shipment.
5. Each authority acting in the systems in the role of a competent authority shall have access to the following:
(a)
information and documents which are submitted, managed or exchanged by this competent authority through the central system or its local system;
(b)
information and documents concerning the shipments of waste referred to in Article 4(1), (2) and (3) of Regulation (EU) 2024/1157 in which they are involved;
(c)
information and documents concerning shipments of waste referred to in Article 4(4) and (5) of Regulation (EU) 2024/1157 that are intended to be or are carried out from, through or to the territory of their Member State.
6. Each authority acting in the role of authority involved in inspections shall have access to all data, information and documents concerning any shipment of waste, and may store such relevant data, information and documents for the purposes of enforcement, in particular criminal proceedings, in accordance with national rules regarding storage of such data, information and documents.
7. The systems and, where relevant, software shall display the following information:
(a)
the number of days for performing the actions listed in entries 2, 4, 8 and 14 to 16 of the table set out in Annex III to this Regulation, in accordance with the deadlines set out in Articles 8, 9 and 14 of Regulation (EU) 2024/1157;
(b)
the number of days that have passed from the expiry of the deadlines referred to in point (a).
8. The systems and software shall display the information referred to in paragraph 7 starting from the date on which a user authenticated a document submitted in the system, as referred to in Article 14(2), point (a).
9. The local systems and software shall display the information referred to in paragraph 7 in a clear and visible manner for all users involved in a given shipment, in such a way that the stage of the procedure can be clearly identified at any time.
10. The Commission may access information and documents exchanged in the central system in order to comply with its obligations pursuant to Regulation (EU) 2024/1157 and to ensure the proper functioning of the central system.
Storage requirements
1. The systems and software shall store all the information and documents exchanged through the central system in accordance with Article 20 of Regulation (EU) 2024/1157.
2. Where the information or documents were updated after submission in the central system by any of the users, the provisions of paragraph 1 shall concern the storage of the following information and documents:
(a)
the updated versions of the information, documents and attachments as well as all changes introduced from its initial submission;
(b)
all attachments uploaded after the initial submission.
Reciprocal exchange of data and their synchronisation
1. The exchange of data between the central system and local systems or software shall be reciprocal.
2. Synchronisation of data introduced in a system shall be performed after every operation referred to in Annex II Parts A to E, and in any case at least every 12 hours.
3. The provisions of this Article do not apply to inspection systems and any software that interoperates with the central system only for the purposes of information and document retrieval.
Security
The systems and software shall be designed and developed in such a way that they achieve an appropriate level of security, in particular cybersecurity, and that they perform consistently in those respects throughout their lifecycle.
Data governance
The systems and software shall ensure that the data they collect is of high quality, including by application of data quality verification mechanisms and data accuracy monitoring tools.
Data confidentiality
The systems and software shall be designed and developed in such a way that they ensure confidentiality of the data exchanged, including protection against unauthorized or unlawful access and against accidental loss, destruction or damage, using appropriate technical measures.
Storage of personal data
1. The systems or software shall store personal data from information and documents exchanged in accordance with Article 27(1) of Regulation (EU) 2024/1157 for five years as follows:
(a)
from the date of submission of a certificate in the systems or software in accordance with Article 15(4) or Article 16(6) of Regulation (EU) 2024/1157 in the context of a notification;
(b)
from the date of submission of the last certificate in the systems or software in accordance with Article 15(4) or Article 16(6) of Regulation (EU) 2024/1157 in context of a general notification;
(c)
from the date of submission of a certificate in the systems or software in accordance with Article 18(9) of Regulation (EU) 2024/1157 in context of an Annex VII document.
2. Where the certificates referred to in paragraph 1 are not issued within one year following the deadlines referred to, respectively, in Article 15(4), Article 16(6) or Article 18(9) of Regulation (EU) 2024/1157, the systems or software shall store personal data from information and documents exchanged in accordance with Article 27(1) of that Regulation for the following time periods:
(a)
ten years from the date on which a notification was submitted in the systems or software;
(b)
five years from the date on which the Annex VII document was submitted in the systems or software.
3. Where not all the concerned competent authorities consented to the notification, the systems or software shall store personal data from information and documents exchanged in accordance with Article 27(1) of Regulation (EU) 2024/1157 for five years from the date on which a notification was submitted in the systems or software.
4. Data, information and documents containing personal data stored by the authorities involved in inspections for the purposes of enforcement, as referred to in Article 18(6), shall be stored no longer than necessary for that purpose in accordance with national laws.
General provision on data protection
1. Processing of personal data may take place in the systems and software for the purposes of achieving the objectives of Regulation (EU) 2024/1157, in particular to ensure the protection of the environment and human health related to shipments of waste. The systems and software shall enable the exchange of information, documents or data between competent authorities, authorities involved in inspections and operators and consequently the processing of personal data, to ensure the following activities:
(a)
issuing by the competent authorities of decisions concerning shipments of waste referred to in Article 4(2) and (3) of Regulation (EU) 2024/1157 in accordance with that Regulation;
(b)
proper enforcement measures taken by competent authorities and authorities involved in inspections related to shipments of waste, in accordance with Articles 60 to 66 of Regulation (EU) 2024/1157 and where relevant in accordance with Article 67 to 71 of that Regulation.
2. Processing of personal data may take place in the systems or software only in respect of the following categories of data subjects:
(a)
natural persons who use the systems;
(b)
natural persons whose personal information is contained in documents concerning shipments of waste, in particular the notification document, the movement document or the Annex VII document;
(c)
natural persons whose personal information is contained in additional documents concerning shipments of waste, in particular in the documents listed in Annex II to Regulation (EU) 2024/1157;
(d)
authorised staff of competent authorities or authorities involved in inspections whose personal information is contained in any documents referred to in points (b) and (c);
(e)
Commission staff and third-party providers acting on behalf of the Commission that perform operations and maintenance activities in relation to the central system.
3. Processing of personal data may take place in the systems or software only in respect of the following categories of personal data:
(a)
name, address, e-mail address, phone number, signature, function performed when representing the operator and identification number of natural persons referred to in paragraph 2, points (a), (b) and (c), required under Union law;
(b)
the name, signature and function performed by staff referred to in paragraph 2, points (a), (d) and (e), when representing the authority concerned.
4. The competent authorities of the Member States, and where relevant, of the third countries, shall be regarded as the controllers within the meaning of Article 4(7) of Regulation (EU) 2016/679 with respect to personal data exchanged through the central system in accordance with Article 27(1) of Regulation (EU) 2024/1157 and this Regulation. The competent authorities of the Member States, and where relevant, of the third countries, shall process such data for the purposes referred to in paragraph 1 of this Article.
Controllers shall ensure the security, integrity, authenticity and confidentiality of the data processed for the purposes set out in Article 25(1) of this Regulation.
5. Notwithstanding paragraph 4, the Commission shall be regarded as controller within the meaning of Article 3(8) of Regulation (EU) 2018/1725 with respect to personal data exchanged through the central system in accordance with Article 27(1) of Regulation (EU) 2024/1157 and this Regulation. The Commission may process such data for the following purposes:
(a)
publishing information on shipments of waste in accordance with Article 21 of Regulation (EU) 2024/1157;
(b)
preparation of statistics related to shipments of waste and reports on that matter, including reports referred to in Articles 62(5), 67(4), 73(4) and (5) and 84 of Regulation (EU) 2024/1157;
(c)
exercise of the inspection powers provided to the Commission in accordance with Articles 67 to 71 of Regulation (EU) 2024/1157.
CHAPTER 4 — OTHER REQUIREMENTS
Other obligations of competent authorities
1. Competent authorities shall provide the Commission, no later than 3 June 2026, a list of facilities for which they issued pre-consents in accordance with Article 14(1) of Regulation (EC) No 1013/2006 of the European Parliament and of the Council ( 13 ) , indicating the following information:
(a)
the name of the facility, the main identification number and address of the facility;
(b)
the name and address of the site, where applicable;
(c)
the R-code or codes referred to in Annex II to Directive 2008/98/EC, for which the pre-consent is issued;
(d)
the waste identification code or codes for the waste to which the pre-consent is issued and the total pre-consented quantity of such waste;
(e)
the end date of validity of the pre-consent;
(f)
the period of validity of the pre-consent, in accordance with Article 85(7) of Regulation (EU) 2024/1157;
(g)
a copy of the decision regarding the pre-consent.
2. Competent authorities shall without undue delay inform operators under their jurisdiction of the following elements:
(a)
the content of the declaration referred to in Article 4(1) and any changes thereof, and on the obligation to use a local system for accessing the central system;
(b)
the obligation to access the central system through GUI from a certain date referred to in Article 11(9);
(c)
the successful completion of the tests referred to in Article 11(8) and the obligation to access the central system through the local system from a certain date referred to in Article 11(11).
3. Competent authorities shall provide the Commission with the e-mail addresses of contact points responsible for the functioning of the local system or, in cases where competent authorities access the central system through GUI, the e-mail addresses of contact points responsible for the electronic exchange of information and documents pursuant to Regulation (EU) 2024/1157.
4. Competent authorities shall ensure that operators with a registered office in their Member State can address to them any question on the use of the systems or software, including through organising a helpdesk function and offering trainings on the use of the system.
Obligation of the Commission
1. The Commission shall publish on its website the following information concerning all the competent authorities:
(a)
content of the declaration referred to in Article 4, including the date from which a certain system is to be used for exchange of information and documents pursuant to Regulation (EU) 2024/1157;
(b)
the obligation for users to use the central system for the purpose of exchanging information and documents pursuant to Regulation (EU) 2024/1157 from a certain date referred to in Article 11(9);
(c)
the main identification number to be used for registration in the central system referred to in Article 9(1);
(d)
the user obligation to use the local system for the purpose of exchanging information and documents pursuant to Regulation (EU) 2024/1157 from a certain date after compliance with Article 11(8) or (11);
(e)
the contact points as notified in accordance with Article 26(3).
2. The Commission shall provide support as follows to the following entities:
(a)
competent authorities, by offering trainings on the use of the central system;
(b)
operators, by providing support in technical issues related to the functioning of the central system.
CHAPTER 5 — FINAL PROVISIONS
This Regulation shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union .
Supplementary provisions
DECLARATION ON HOW TO ACCESS
ANNEX ISupplementary provisions
ANNEX I
DECLARATION ON HOW TO ACCESS
PROTOCOL FOR THE EXCHANGE OF DATA
ANNEX IISupplementary provisions
ANNEX II
PROTOCOL FOR THE EXCHANGE OF DATA
1.
For the purposes of this Annex:
(a)
‘CA’ means competent authority;
(b)
‘UUID’ means a label uniquely identifying data elements and the relationship between them; in this Annex, this relationship concerns the role of the actor performing authentication of a given submission of documents or information and the authentication details;
(c)
‘interim facility’ means a facility that carries out interim recovery or interim disposal operations of waste;
(d)
‘subsequent interim or non-interim facility located in the country of destination’ means a facility that carries out interim or non-interim recovery or interim or non-interim disposal operations of waste after it was shipped pursuant to Article 15(5) of Regulation (EU) 2024/1157.
2.
For the purpose of this Annex, the letters used in the column ‘mandatory’ in the tables in Parts A to E shall have the following meaning:
(a)
‘Y’ means that introducing data in a given field shall be mandatory;
(b)
‘N’ means that introducing data in a given field shall not be mandatory.
3.
For the purpose of this Annex, terms used in the column ‘other constraints’ in in the tables in Parts A to E shall have the following meaning:
(a)
‘Validated’ means that the systems are required to automatically verify the data provided in a given field;
(b)
‘Boolean’ means that the value shall be either ‘yes’ or ‘no’.
PART A
PROTOCOL FOR EXCHANGE OF DATA RELATED TO THE NOTIFICATION REFERRED TO IN ARTICLE 27(1) POINT (A), (I) TO (VIII), (X) AND (XV) AND ARTICLE 24(1) POINT (C), OF REGULATION (EU) 2024/1157
1. SUBMIT NEW NOTIFICATION
This operation is used to submit a new notification.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex IA box
General
CA role
Y
On behalf of CA code
N
CA code
On behalf of CA country code
N
Validated
On behalf of role
N
Validated
Notification created due to take-back
Y
Boolean
Notification created due to detection of illegal activity
Y
Boolean
Notification is related to notification or Annex VII document No
N
Validated
Exporter – Notifier
Operator ID
Y
Validated
Contact person name
Y
1
Phone number
Y
1
Email address
Y
1
UUID
Y
Importer – Consignee
Operator ID
Y
Validated
Contact person name
Y
2
Phone number
Y
2
Email address
Y
2
Submission
Notification No
Y
Validated
3
Individual shipment
Y
Boolean
3
Destined for
(recovery / disposal)
Y
Boolean
3
Destined for pre-consented recovery facility
Y
3
Total intended number of shipments
Y
4
Total waste quantity mass (in tonnes/Mg)
Y, unless volume is provided
5
Total waste quantity volume (in m 3 )
Y, unless mass is provided
5
Intended period of time of shipment(s): first departure
Y
6
Intended period of time of shipment(s): last departure
Y
6
Packaging type (code(s))
Y
7
Packaging description
N
Language code: value
Special handling
Y
Boolean
7
Disposal / recovery operation(s)
D-code / R-code:
Y
11
Technology employed
Y
Language code: value
11
Reason for export
Y
Language code: value
11
Designation and composition of waste
Y
Language code: value
12
Physical characteristics (code)
Y
13
Physical characteristics description
N
Language code: value
13
Waste identification (list)
Y
14
Waste identification (code)
Y
14
Customs codes (HS)
Y for extra-EU shipments
14
Address of the location from which the shipment starts
Operator ID
Y, unless notification is created due to take-back
Validated
Address details
N, unless notification is created due to take-back
Intended carrier(s)
Operator ID
Y
Validated
Contact person name
Y
8
Phone number
Y
8
Email address
Y
8
Means of transport (code)
Y
Validated
8
Waste generator(s) – producer(s)
Operator ID
Y
Validated
Contact person name
Y
9
Phone number
Y
9
Email address
Y
9
Site of generation description
Y
Language code: value
9
Process of generation description
Y
Language code: value
9
UUID
Y
Facility
Operator ID
Y
Validated
Facility type
Y
Recovery / Disposal
10
Interim facility
Y
Boolean
Subsequent interim or non-interim facility located in the country of destination
Y
Boolean
Subsequent interim or non-interim facility located in another country than the country of destination
Y
Boolean
Contact person name
Y
10
Phone number
Y
10
Email address
Y
10
Actual site of disposal / recovery
Y
10
Countries / States concerned
State of export – dispatch
Y
Validated
15
Code No of competent authority
Y
Validated
15
Specific point of exit (border crossing or port)
Y
15
State of import – destination
Y
Validated
15
Code No of competent authority
Y
Validated
15
Specific point of entry (border crossing or port)
Y
15
State(s) of transit
N
Validated
15
Code No of competent authority
N
Validated
15
Specific point of entry (border crossing or port)
N
15
Specific point of exit (border crossing or port)
N
15
Customs offices of entry and/or exit and/or export
EU entry office
N
16
EU exit office
N
16
EU export office
N
16
Alternative routing – Customs offices of entry and/or exit and/or export
EU entry office
N
EU exit office
N
EU export office
N
Exporter’s – notifier’s – generator’s – producer’s declaration
Name of the person authenticating the submission on behalf of exporter/notifier
Y
17
Email of the person authenticating the submission on behalf of the exporter / notifier
N
17
Role of the person authenticating the submission on behalf of exporter / notifier in its organisation
Y
Language code: value
17
Exporter’s – notifier’s authentication timestamp
Y
17
Exporter’s – notifier’s additional authentication string
N
17
UUID
Y
Exporter’s – notifier’s – generator’s – producer’s declaration
Name of the person authenticating the submission on behalf of generator / producer
Y
17
Email of the person authenticating the submission on behalf of generator / producer
N
17
Role of the person authenticating the submission on behalf of generator / producer in its organisation
Y
Language code: value
17
Generator’s – producer’s authentication timestamp
Y
17
Generator’s – producer’s additional authentication string
N
17
UUID
Y
Attachment
List of attachment IDs
N
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Errors and warnings
Warning message
Error message
2. SUBMIT REQUEST FOR INFORMATION
This operation is used to submit a request for information and documentation in accordance with Article 8 of Regulation (EU) 2024/1157. This operation can be used by any CA concerned.
Input parameters:
Section
Field
Mandatory
Other constraints
General
CA role in the notification
Y
Validated
On behalf of CA code
N
CA code
On behalf of CA country code
N
Validated
On behalf of role
N
Validated
UUID
Y
Request for information
Notification No
Y
Notification No (existing)
Request language
Y
Validated
Request content
Y
CA authentication details
Name of the person authenticating the submission on behalf of CA
Y
Email of the person authenticating the submission on behalf of CA
N
Role of the person authenticating the submission on behalf of CA in its organization
Y
CA representative authentication timestamp
Y
CA representative authentication string
N
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Request for information ID
Errors and warnings
Warning message
Error message
3. UPDATE REQUEST FOR INFORMATION
This operation is used to update a request for information and documentation in accordance with Article 8 of Regulation (EU) 2024/1157. This operation can be used by any CA concerned in order to extend the time for reply.
Input parameters:
Section
Field
Mandatory
Other constraints
General
CA role in the notification
Y
Validated
On behalf of CA code
N
CA code
On behalf of CA country code
N
Validated
On behalf of role
N
Validated
UUID
Y
Request for information
Notification No
Y
Notification No (existing)
Request for information ID
Y
Request for information number (existing)
Request language
Y
Validated
Request content
Y
Additional time for reply
N
CA authentication details
Name of the person authenticating the submission on behalf of CA
Y
Email of the person authenticating the submission on behalf of CA
N
Role of the person authenticating the submission on behalf of CA in its organization
Y
CA representative authentication timestamp
Y
CA representative authentication string
N
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Request for information ID
Errors and warnings
Warning message
Error message
4. SUBMIT REPLY TO REQUEST FOR INFORMATION
This operation is used by the notifier to submit a reply to competent authority’s request for information and documentation.
Input parameters:
Section
Field
Mandatory
Other constraints
General
On behalf of operator (Operator ID)
N
Validated
UUID
Y
Reply for Request for information
Request for information ID
Y
Request for information number (existing)
Reply language
Y
Validated
Reply content
Y
Notifier’s authentication details
Name of the person authenticating the submission on behalf of the notifier
Y
Email of the person authenticating the submission on behalf of the notifier
N
Role of the person authenticating the submission on behalf of the notifier in its organization
Y
Notifier’s representative authentication timestamp
Y
Notifier’s representative authentication string
N
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Request for information ID
Reply ID
Errors and warnings
Warning message
Error message
5. SUBMIT ACKNOWLEDGEMENT
This operation is used by competent authority to submit an acknowledgement of receipt of a properly completed notification for waste imported into the EU, exported from the EU or transited through the EU.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex IA box
General
CA role in the notification
Y
Validated
On behalf of CA code
N
CA code
On behalf of CA country code
N
Validated
On behalf of role
N
Validated
UUID
Y
Acknowledgment
Notification No
Y
Notification No (existing)
19
Notification receipt date
Y
Date format
19
Acknowledgement date
Y
Date format
19
CA authentication details
Name of the person authenticating the submission on behalf of CA
Y
19
Email of the person authenticating the submission on behalf of CA
N
19
Role of the person authenticating the submission on behalf of CA in its organization
Y
19
CA representative authentication timestamp
Y
19
CA representative authentication string
N
19
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Acknowledgment ID
Errors and warnings
Warning message
Error message
6. DECLINE THE ‘PRE-CONSENTED FACILITY’ STATUS OF WASTE RECEIVING FACILITY FOR THE NOTIFICATION CONCERNED
This operation is used by CAs to decline the ‘pre-consented facility’ status of waste receiving facility for a given notification in case the shipment does not fall into the scope of pre-consent.
Input parameters:
Section
Field
Mandatory
Other constraints
General
CA role
Y
Validated
On behalf of CA code
N
On behalf of CA country code
N
On behalf of role
N
UUID
Y
Action
Notification No
Y
Validated
Action code
Y
Name of the person authenticating the action on behalf of CA
Y
Email of the person authenticating the action on behalf of CA
N
Role of the person authenticating the action on behalf of CA in its organisation
Y
Language code: value
Authentication timestamp
Y
Additional authentication string
N
UUID
Y
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Action ID
Errors and warnings
Warning message
Error message
7. DISREGARD TIMELINES (ARTICLE 14(16) OF REGULATION (EU) 2024/1157)
This operation is used by CAs to inform the notifier and other CAs that they need more time to decide over a notification destined for pre-consented facility, as referred to in Article 14(16) of Regulation (EU) 2024/1157.
Input parameters:
Section
Field
Mandatory
Other constraints
General
CA role
Y
Validated
On behalf of CA code
N
On behalf of CA country code
N
On behalf of role
N
UUID
Y
Action
Notification No
Y
Validated
Action code
Y
Name of the person authenticating the action on behalf of CA
Y
Email of the person authenticating the action on behalf of CA
N
Role of the person authenticating the action on behalf of CA in its organisation
Y
Language code: value
Authentication timestamp
Y
Additional authentication string
N
UUID
Y
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Action ID
Errors and warnings
Warning message
Error message
8. SUBMIT DECISION
This operation is used to submit a decision concerning a notification, by referring to its number. Each competent authority is allowed to submit only one decision, that can be later updated.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex IA box
General
CA role in the notification process
Y
Validated
On behalf of CA code
N
CA code
On behalf of CA country code
N
Validated
On behalf of role
N
Validated
UUID
Y
Decision
Notification No
Y
Notification no (existing)
Decision date
Y
Date format
20
Decision type
(consent / consent with conditions / objection / withdrawal of tacit consent)
Y
Validated
Specific conditions on consenting to the movement document
N (Y for consent with conditions)
Language code: value
21
Specific conditions: consent valid only for waste quantity not exceeding the following mass (in tonnes/Mg):
N
Specific conditions: consent valid only for waste quantity not exceeding the following volume (in m 3 ):
N
Specific conditions: consent valid only for the following number of shipments:
N
Consent valid from date
N (Y for consent type)
Date format
20
Consent valid until date
N (Y for consent type)
Date format
20
Reasons for objection
N (Y for objection)
Language code: value
21
Duly reasoned justification of the decision
Y
Language code: value
Name of the person authenticating the submission on behalf of CA
Y
20
Email of the person authenticating the submission on behalf of CA
N
20
Role of the person authenticating the submission on behalf of CA in its organization
Y
20
CA representative authentication timestamp
Y
20
CA representative additional authentication string
N
20
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Decision ID
Errors and warnings
Warning message
Error message
9. UPDATE INFORMATION ON CONFIDENTIALITY OF WASTE RECEIVING FACILITY NAME
This operation is used by CAs to indicate, that the name of the waste receiving facility shall not be published by the Commission in accordance with Article 21 of Regulation (EU) 2024/1157, as it is confidential in accordance with Union or national law.
Input parameters:
Section
Field
Mandatory
Other constraints
General
Notification No
Y
Operator ID
Y
Name of the waste receiving facility is confidential and shall not be publicly disclosed
Y
Explanation why the name of waste receiving facility is confidential under Union or national law
Y
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Operator ID
Name of the waste receiving facility is confidential and shall not be publicly disclosed
Explanation why the name of waste receiving facility is confidential under Union or national law
Errors and warnings
Warning message
Error message
10. UPDATE NOTIFICATION
This operation is used to update the notification
Input parameters:
Section
Field
Mandatory
Other constraints
Annex IA box
General
CA role in the notification process
Y
Validated
On behalf of CA code
N
CA code
On behalf of CA country code
N
Validated
On behalf of role
N
Validated
Notification created due to take-back
Y
Boolean
Notification created due to detection of illegal activity
Y
Boolean
Notification is related to notification No or Annex VII document No
N
Validated
Exporter – Notifier
Operator ID
Y
Validated
UUID
Y
Contact person name
Y
1
Phone number
Y
1
Email address
Y
1
Importer – Consignee
Operator ID
Y
Validated
Contact person name
Y
2
Phone number
Y
2
Email address
Y
2
Submission
Notification No
Y
Validated
3
Individual shipment
Y
Boolean
3
Destined for
(recovery / disposal)
Y
3
Destined for pre-consented recovery facility
Y
Boolean
3
Total intended number of shipments
Y
4
Total waste quantity mass (in tonnes/Mg)
Y, unless volume is provided
5
Total waste quantity volume (in m 3 )
Y, unless mass is provided
5
Intended period of time of shipment(s): first departure
Y
6
Intended period of time of shipment(s): last departure
Y
6
Packaging type (code(s))
Y
7
Packaging description
N
Special handling
Y
Boolean
7
Disposal / recovery operation(s)
D-code / R-code:
Y
11
Technology employed
Y
Language code: value
11
Reason for export
Y
Language code: value
11
Designation and composition of waste
Y
Language code: value
12
Physical characteristics (code)
Y
13
Physical characteristics description
N
Language code: value
13
Waste identification (list)
Y
14
Waste identification (code)
Y
14
Customs code(s) (HS)
Y for extra-EU shipments
14
Address of the location from which the shipment starts
Operator ID
Y, unless notification is created due to take-back
Validated
Address details
N, unless notification is created due to take-back
Intended carrier(s)
Operator ID
Y
Validated
Contact person name
Y
8
Phone number
Y
8
Email address
Y
8
Means of transport (code)
Y
Validated
8
Waste generator(s) – producer(s)
Operator ID
Y
Validated
Contact person name
Y
9
Phone number
Y
9
Email address
Y
9
Site of generation description
Y
Language code: value
9
Process of generation description
Y
Language code: value
9
UUID
Y
Facility
Operator ID
Y
Validated
Facility type
Y
Recovery / Disposal
10
Interim facility
Y
Boolean
Subsequent interim or non-interim facility located in the country of destination
Y
Boolean
Subsequent interim or non-interim facility located in another country than the country of destination
Y
Boolean
Contact person name
Y
10
Phone number
Y
10
Email address
Y
10
Actual site of disposal / recovery
Y
10
Countries / States concerned
State of export – dispatch
Y
Validated
15
Code No of competent authority
Y
Validated
15
Specific point of exit (border crossing or port)
Y
15
State of import – destination
Y
Validated
15
Code No of competent authority
Y
Validated
15
Specific point of entry (border crossing or port)
Y
15
State(s) of transit
N
Validated
15
Code No of competent authority
N
Validated
15
Specific point of entry (border crossing or port)
N
15
Specific point of exit (border crossing or port)
N
15
Customs offices of entry and/or exit and/or export
EU entry office
N
16
EU exit office
N
16
EU export office
N
16
Alternative routing – Customs offices of entry and/or exit and/or export
EU entry office
N
EU exit office
N
EU export office
N
Exporter’s – notifier’s – generator’s – producer’s declaration
Name of the person authenticating the submission on behalf of exporter / notifier
Y
17
Email of the person authenticating the submission on behalf of the exporter / notifier
N
17
Role of the person authenticating the submission on behalf of exporter / notifier in its organisation
Y
17
Exporter’s – notifier’s authentication timestamp
Y
17
Exporter’s – notifier’s additional authentication string
N
17
UUID
Y
Exporter’s – notifier’s – generator’s – producer’s declaration
Name of the person authenticating the submission on behalf of generator / producer
Y
17
Email of the person authenticating the submission on behalf of generator / producer
N
17
Role of the person authenticating the submission on behalf of generator / producer in its organisation
Y
Language code: value
17
Generator’s – producer’s authentication timestamp
Y
17
Generator’s – producer’s additional authentication string
N
17
UUID
Y
Attachment
List of attachment IDs
N
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Errors and warnings
Warning message
Error message
11. UPDATE DECISION
This operation is used to update the decision based on its ID. The update may take one of the following forms: changing of the decision type or changing the conditions of the consent.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex IA box
General
CA role in the notification process
Y
Validated
On behalf of CA code
N
CA code
On behalf of CA country code
N
On behalf of role
N
Validated
UUID
Y
Decision
Notification No
Y
Notification no (existing)
Decision ID
Y
Validated
Decision date
Y
Date format
20
Decision type
(consent / consent with conditions / objection / consent withdrawal)
Y
Validated
Specific conditions on consenting to the movement document
N (Y for consent with conditions)
Language code: value
21
Specific conditions: consent valid only for waste quantity not exceeding the following mass (in tonnes/Mg):
N
Specific conditions: consent valid only for waste quantity not exceeding the following volume (in m 3 ):
N
Specific conditions: consent valid only for the following number of shipments:
N
Consent valid from date
N (Y for consent type)
Date format
20
Consent valid until date
N (Y for consent type)
Date format
20
Reasons for objection
N (Y for objection)
Language code: value
21
Duly reasoned justification of the decision
Y
Language code: value
CA authentication details
Name of the person authenticating the submission on behalf of CA
Y
20
Email of the person authenticating the submission on behalf of CA
N
20
Role of the person authenticating the submission on behalf of CA in its organization
Y
20
CA representative authentication timestamp
Y
20
CA representative additional authentication string
N
20
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Decision ID
Errors and warnings
Warning message
Error message
12. SUBMIT REQUEST FOR CHANGE AFTER CONSENT (ARTICLE 17 OF REGULATION (EU) 2024/1157)
This operation is used by a notifier to submit a request for changes of the notification after it has been already consented to, in accordance with Article 17 of Regulation (EU) 2024/1157.
Input parameters:
Section
Field
Mandatory
Other constraints
General
Notification No
Y
Validated
Operator ID
Y
Validated
UUID
Y
Request for change after consent
Does the request cover change of the route of the shipment?
Y
Boolean
Request language
Y
Validated
Request content
Y
Exporter’s – notifier’s – generator’s – producer’s declaration
Name of the person authenticating the submission on behalf of exporter / notifier
Y
Email of the person authenticating the submission on behalf of the exporter / notifier
N
Role of the person authenticating the submission on behalf of exporter / notifier in its organisation
Y
Exporter’s – notifier’s authentication timestamp
Y
Exporter’s – notifier’s additional authentication string
N
UUID
Y
Attachment
List of attachment IDs
N
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Request for change after consent ID
Errors and warnings
Warning message
Error message
13. SUBMIT REPLY TO REQUEST FOR CHANGE AFTER CONSENT (ARTICLE 17 OF REGULATION (EU) 2024/1157)
This operation is used by the CAs to submit a reply to notifier’s request to change after consent.
Input parameters:
Section
Field
Mandatory
Other constraints
General
CA role in the notification process
Y
Validated
On behalf of CA code
N
CA code
On behalf of CA country code
N
On behalf of role
N
Validated
UUID
Y
Reply for request for change
Request for change after consent ID
Y
Request for change after consent number (existing)
Agreement for change after the consent as requested by notifier
Y
Boolean
Reasons for agreement / disagreement
N
Language code: value
CA authentication details
Name of the person authenticating the submission on behalf of CA
Y
Email of the person authenticating the submission on behalf of CA
N
Role of the person authenticating the submission on behalf of CA in its organization
Y
CA representative authentication timestamp
Y
CA representative additional authentication string
N
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Request for change after consent ID
Reply ID
Errors and warnings
Warning message
Error message
14. PROPERLY CARRIED OUT
This operation is used by the CA of dispatch to inform that they are satisfied with the notification and consider it properly carried out.
Input parameters:
Section
Field
Mandatory
Other constraints
General
CA role
Y
Validated
On behalf of CA code
N
On behalf of CA country code
N
On behalf of role
N
UUID
Y
Action
Notification No
Y
Validated
Action code
Y
Name of the person authenticating the action on behalf of CA
Y
Email of the person authenticating the action on behalf of CA
N
Role of the person authenticating the action on behalf of CA in its organisation
Y
Language code: value
Authentication timestamp
Y
Additional authentication string
N
UUID
Y
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Action ID
Errors and warnings
Warning message
Error message
15. PROPERLY COMPLETED
This operation is used by the CA of destination and/or transit to inform that they are satisfied with the notification and consider it properly completed.
Input parameters:
Section
Field
Mandatory
Other constraints
General
CA role
Y
Validated
On behalf of CA code
N
On behalf of CA country code
On behalf of role
N
UUID
Y
Action
Notification No
Y
Validated
Action code
Y
Name of the person authenticating the action on behalf CA
Y
Email of the person authenticating the action on behalf of CA
N
Role of the person authenticating the action on behalf of CA in its organisation
Y
Language code: value
Authentication timestamp
Y
Additional authentication string
N
UUID
Y
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Action ID
Errors and warnings
Warning message
Error message
16. NOTIFICATION INVALID
This operation is used by the CA to decide that the notification is not valid in accordance with Article 8(5) or (10) of Regulation (EU) 2024/1157.
Input parameters:
Section
Field
Mandatory
Other constraints
General
CA role
Y
Validated
On behalf of CA code
N
On behalf of CA country code
N
On behalf of role
N
UUID
Y
Action
Notification No
Y
Validated
Action code
Y
Name of the person authenticating the action on behalf CA
Y
Email of the person authenticating the action on behalf of CA
N
Role of the person authenticating the action on behalf of CA in its organisation
Y
Language code: value
Authentication timestamp
Y
Additional authentication string
N
UUID
Y
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Action ID
Errors and warnings
Warning message
Error message
17. NOTIFICATION REVALIDATED
This operation is used by the CA to revalidate a notification.
Input parameters:
Section
Field
Mandatory
Other constraints
General
CA role
Y
Validated
On behalf of CA code
N
On behalf of CA country code
N
On behalf of role
N
UUID
Y
Action
Notification No
Y
Validated
Action code
Y
Name of the person authenticating the action on behalf CA
Y
Email of the person authenticating the action on behalf of CA
N
Role of the person authenticating the action on behalf of CA in its organisation
Y
Language code: value
Authentication timestamp
Y
Additional authentication string
N
UUID
Y
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Action ID
Errors and warnings
Warning message
Error message
18. CANCEL NOTIFICATION
This operation is used to cancel the already submitted notification.
Input parameters:
Section
Field
Mandatory
Other constraints
General
Notification No
Y
Notification No (existing)
Action code
Y
Cancelation reasons or details
N
Language code: value
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Action ID
Errors and warnings
Warning message
Error message
19. NOTIFICATION COMPLETED
This operation is used by the CA to close a completed notification.
Input parameters:
Section
Field
Mandatory
Other constraints
General
CA role
Y
Validated
On behalf of CA code
N
On behalf of CA country code
N
On behalf of role
N
UUID
Y
Action
Notification No
Y
Validated
Action code
Y
Name of the person authenticating the action on behalf of CA
Y
Email of the person authenticating the action on behalf of CA
N
Role of the person authenticating the action on behalf of CA in its organisation
Y
Language code: value
Authentication timestamp
Y
Additional authentication string
N
UUID
Y
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Action ID
Errors and warnings
Warning message
Error message
PART B
PROTOCOL FOR EXCHANGE OF DATA RELATED TO THE MOVEMENT DOCUMENT REFERRED TO IN ARTICLE 27(1), POINT (A) (XI) AND (XIV), AND ARTICLE 24(1), POINT (C), OF REGULATION (EU) 2024/1157
1. SUBMIT MOVEMENT DOCUMENT
This operation is used to submit a movement document based on the consented notification.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex IB box
Movement
Notification No
Y
Validated
1
Movement document created due to take-back
Y
Boolean
Movement documents created due to detection of illegal activity
Y
Boolean
Movement document is related to movement document No
N
Validated
Serial / total number of shipments
Y
2
Container identification number
N
2 a
Actual quantity of waste mass (in tonnes/Mg)
Y, unless volume is provided
5
Actual quantity of waste volume (in m 3 )
Y, unless mass is provided
5
Actual date of shipment
Y
Date format
6
Packaging type (code(s))
Y
Validated
7
Packaging description
N
7
Number of packages
Y
7
Additional information related to the shipment
N
16
Address of the location from which the shipment starts
Address details
N, unless movement document is created due to take-back
Carrier(s)
Operator ID
Y
Validated
Contact person name
Y
8
Phone number
Y
8
Email address
Y
8
Disposal / recovery facility
Actual site of disposal / recovery
Y
10
Exporter’s – notifier’s declaration
Operator submitting the declaration
Y
Exporter – notifier / generator – producer
15
Name of the person authenticating the submission on behalf of exporter / notifier
Y
15
Email of the person authenticating the submission on behalf of the exporter / notifier
N
15
Role of the person authenticating the submission on behalf of exporter / notifier in its organisation
Y
15
Exporter’s – notifier’s authentication timestamp
Y
15
Exporter’s – notifier’s additional authentication string
N
15
UUID
Y
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Movement document No
Errors and warnings
Warning message
Error message
2. UPDATE MOVEMENT DOCUMENT
This operation is used to update a movement document.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex IB box
Movement
Notification No
Y
Validated
1
Movement document No
Y
Validated
Movement document created due to take-back
Y
Boolean
Movement document created due to detection of illegal activity
Y
Boolean
Movement document is related to movement document No
N
Validated
Serial / total number of shipments
Y
2
Container identification number
N
2 a
Actual quantity of waste mass (in tonnes/Mg)
Y, unless volume is provided
5
Actual quantity of waste volume (in m 3 )
Y, unless mass is provided
5
Actual date of shipment
Y
Date format
6
Packaging type (code(s))
Y
Validated
7
Packaging description
N
7
Number of packages
Y
7
Additional information related to the shipment
N
16
Address of the location from which the shipment starts
Address details
N, unless movement document is created due to take-back
Carrier(s)
Operator ID
Y
Validated
Contact person name
Y
8
Phone number
Y
8
Email address
Y
8
Disposal / recovery facility
Actual site of disposal / recovery
Y
10
Exporter’s – notifier’s declaration
Operator submitting the declaration
Y
Exporter – notifier/generator-producer
15
Name of the person authenticating the submission on behalf of exporter / notifier
Y
15
Email of the person authenticating the submission on behalf of the exporter / notifier
N
15
Role of the person authenticating the submission on behalf of exporter / notifier in its organisation
Y
15
Exporter’s – notifier’s authentication timestamp
Y
15
Exporter’s – notifier’s additional authentication string
N
15
UUID
Y
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Movement document No
Errors and warnings
Warning message
Error message
3. SUBMIT CARRIER TRANSFER CONFIRMATION
This operation is used by carrier(s) to submit a confirmation of receipt of waste with respect to waste shipped based on a given movement document.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex IB box
Movement
Movement document No
Y
Validated
Additional information related to the shipment
N
16
Carrier Transfer
Operator ID
Y
Validated
UUID
Y
Means of transport
Y
8
Transfer date
Y
Date format
8
Declaration of the carrier who takes-over the shipment
Name of the person authenticating the submission on behalf of carrier
Y
8
Email of the person authenticating the submission on behalf of carrier
N
8
Role of the person authenticating the submission on behalf of carrier in its organization
Y
8
Authentication timestamp
Y
8
Additional authentication string
N
8
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Movement document No
Confirmation ID
Errors and warnings
Warning message
Error message
4. UPDATE CARRIER TRANSFER CONFIRMATION
This operation is used to update an existing carrier transfer confirmation.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex IB box
Movement
Movement document No
Y
Validated
Additional information related to the shipment
N
16
Transfer ID
Y
Validated
Carrier Transfer
Operator ID
Y
Validated
UUID
Y
Means of transport
Y
Validated
8
Transfer date
Y
Date format
Declarations of carrier who takes-over the shipment
Name of the person authenticating the submission on behalf of carrier
Y
8
Email of the person authenticating the submission on behalf of carrier
N
8
Role of the person authenticating the submission on behalf of carrier in its organization
Y
8
Authentication timestamp
Y
8
Additional authentication string
N
8
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Movement document No
Confirmation ID
Errors and warnings
Warning message
Error message
5. SUBMIT CONSIGNEE RECEPTION CONFIRMATION
This operation is used to submit a consignee reception confirmation of shipped waste in case the consignee is not a waste treatment facility.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex IB box
Movement
Movement document number
Y
Validated
Additional information related to the shipment
N
16
Importer – Consignee
Operator ID
Y
Validated
UUID
Y
Contact person name
Y
4
Phone number
Y
4
Email address
Y
4
Reception
Reception Date
Y
17
Importer’s – consignee’s declaration
Name of the person authenticating the submission on behalf of consignee
Y
17
Email of the person authenticating the submission on behalf of consignee
N
17
Role of the person authenticating the submission on behalf of consignee in its organization
Y
17
Authentication timestamp
Y
17
Additional authentication string
N
17
UUID
Y
Attachment
List of attachment IDs
N
Output parameters:
Section
Parameter
General
Call status code
Specific
Movement document No
Confirmation ID
Errors and warnings
Warning message
Error message
6. UPDATE CONSIGNEE RECEPTION CONFIRMATION
This operation is used to update a consignee reception confirmation of shipped waste in case the consignee is not a waste treatment facility.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex IB box
Movement
Movement document No
Y
Validated
Confirmation ID
Y
Validated
Additional information related to the shipment
N
16
Importer – Consignee
Operator ID
Y
Validated
UUID
Y
Contact person name
Y
4
Phone number
Y
4
Email address
Y
4
Reception
Reception Date
Y
Date format
17
Importer’s – consignee’s declaration
Name of the person authenticating the submission on behalf of consignee
Y
17
Email of the person authenticating the submission on behalf of consignee
N
17
Role of the person authenticating the submission on behalf of consignee in its organization
Y
17
Authentication timestamp
Y
17
Additional authentication string
N
17
UUID
Y
Attachment
List of attachment IDs
N
Output parameters:
Section
Parameter
General
Call status code
Specific
Movement document No
Confirmation ID
Errors and warnings
Warning message
Error message
7. SUBMIT FACILITY RECEPTION CONFIRMATION
This operation is used by waste treatment facility to submit a confirmation of receipt of shipped waste.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex IB box
Movement
Movement document No
Y
Validated
Additional information related to the shipment
N
16
Disposal / recovery facility
Facility type
Y
Disposal / recovery
18
Operator ID
Y
Validated
UUID
Y
Contact person name
Y
18
Interim facility
Y
Boolean
Phone number
Y
18
Email address
Y
18
Actual site of disposal/recovery
Y
18
Reception
Reception Date
Y
18
Accepted quantity mass (in tonnes/Mg)
Y, unless volume is provided
18
Accepted quantity volume (in m 3 )
Y, unless mass is provided)
18
Rejected quantity mass (in tonnes/Mg)
Y, unless volume is provided
18
Rejected quantity volume (in m 3 )
Y, unless mass is provided
18
Rejection description
Y
Language code: value
18
Approximate date of disposal/recovery
Y
Date format
18
Disposal/Recovery operation (code)
Y
Validated
18
Waste identification (list)
Y
Waste identification (code)
Y
Designation and composition of the waste received
Y
Disposal/recovery facility’s declaration
Name of the person authenticating the submission on behalf of the facility
Y
18
Email of the person authenticating the submission on behalf of the facility
N
18
Role of the person authenticating the submission on behalf of the facility in its organization
Y
18
Authentication timestamp
Y
18
Additional authentication string
N
18
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Movement document No
Confirmation ID
Errors and warnings
Warning message
Error message
8. UPDATE FACILITY RECEPTION CONFIRMATION
This operation is used by waste treatment facility to update confirmation of receipt of shipped waste.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex IB box
Movement
Movement document No
Y
Validated
Confirmation ID
Y
Validated
Additional information related to the shipment
N
16
Disposal / recovery facility
Facility type
Y
Disposal / recovery
18
Operator ID
Y
UUID
Y
Contact person name
Y
18
Interim facility
Y
Boolean
Phone number
Y
18
Email address
Y
18
Actual site of disposal / recovery
Y
18
Reception
Reception Date
Y
18
Accepted quantity mass (in tonnes/Mg)
Y, unless volume is provided
18
Accepted quantity volume (m 3 )
Y, unless the mass is provided
18
Rejected quantity mass (in tonnes/Mg)
Y, unless the volume is provided
18
Rejected quantity volume (m 3 )
Y, unless the mass is provided
18
Rejection description
Y
Language code: value
18
Approximate date of disposal / recovery
Y
Date format
18
Disposal / Recovery operation (code)
Y
Validated
18
Waste identification (list)
Y
Waste identification (code)
Y
Designation and composition of the waste received
Y
Disposal/recovery facility’s declaration
Name of the person authenticating the submission on behalf of the facility
Y
18
Email of the person authenticating the submission on behalf of the facility
N
18
Role of the person authenticating the submission on behalf of the facility in its organization
Y
18
Authentication timestamp
Y
18
Additional authentication string
N
18
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Movement document No
Confirmation ID
Errors and warnings
Warning message
Error message
9. SUBMIT FACILITY COMPLETION CERTIFICATE
This operation is used by waste treatment facility to submit a certificate confirming completion of treatment of waste shipped thereto.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex IB box
Movement
Movement document No
Y
Validated
Additional information related to the shipment
N
16
Facility
Facility type
Y
Disposal / recovery
10
Operator ID
Y
Validated
UUID
Y
Contact person name
Y
10
Phone number
Y
10
Email address
Y
10
Interim facility
Y
Actual site of disposal / recovery
Y
10
Completion certificate
Certificate Date
Y
19
Waste identification (list)
Y
Waste identification (code)
Y
Quantity prepared for re-use or recycled mass (tonnes/Mg)
Y, unless volume is provided
19
Quantity prepared for re-use or recycled volume (m 3 )
Y, unless mass is provided
19
Quantity recovered in other manner mass (tonnes/Mg)
Y, unless volume is provided
19
Quantity recovered in other manner volume (m 3 )
Y, unless mass is provided
19
Quantity disposed mass (tonnes/Mg)
Y, unless volume is provided
19
Quantity disposed volume (m 3 )
Y, unless mass is provided
19
Disposal / recovery facility’s declaration
Name of the person authenticating the submission on behalf of the facility
Y
19
Email of the person authenticating the submission on behalf of the facility
N
19
Role of the person authenticating the submission on behalf of the facility in its organization
Y
19
Authentication timestamp
Y
19
Additional authentication string
N
19
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Movement document No
Certificate ID
Errors and warnings
Warning message
Error message
10. UPDATE FACILITY COMPLETION CERTIFICATE
This operation is used by waste treatment facility to update a certificate confirming completion of treatment of waste shipped thereto.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex IB box
Movement
Movement document No
Y
Validated
Additional information related to the shipment
N
16
Certificate ID
Y
Validated
Facility
Facility type
Y
Disposal / recovery
10
Operator ID
Y
Validated
UUID
Y
Contact person name
Y
10
Phone number
Y
10
Email address
Y
10
Interim facility
Y
Actual site of disposal / recovery
Y
10
Completion certificate
Certificate Date
Y
19
Waste identification (list)
Y
Waste identification (code)
Y
Quantity prepared for re-use or recycled mass (tonnes/Mg)
Y, unless volume is provided
19
Quantity prepared for re-use or recycled volume (m 3 )
Y, unless mass is provided
19
Quantity recovered in other manner mass (tonnes/Mg)
Y, unless the volume is provided
19
Quantity recovered in other manner volume (m 3 )
Y, unless the mass is provided
19
Quantity disposed mass (tonnes/Mg)
Y, unless the volume is provided
19
Quantity disposed volume (m 3 )
Y, unless the mass is provided
19
Disposal / recovery facility’s declaration
Name of the person authenticating the submission on behalf of the facility
Y
19
Email of the person authenticating the submission on behalf of the facility
N
19
Role of the person authenticating the submission on behalf of the facility in its organization
Y
19
Authentication timestamp
Y
19
Additional authentication string
N
19
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Movement document No
Certificate ID
Errors and warnings
Warning message
Error message
11. SUBMIT TAKE-BACK REQUEST
This operation is used to submit a take-back request by CA.
Input parameters:
Section
Field
Mandatory
Other constraints
Movement
Movement document No
Y
Validated
Take-back
Quantity for take-back mass (tonnes/Mg)
Y, unless volume is provided
Quantity for take-back volume (m 3 )
Y, unless mass is provided
Reasons for requesting take-back
Y
Language code: value
Requirements related to take-back based on a new movement document under the existing notification
N
Language code: value
Date of take-back request
Y
Date format
CA code
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Movement document No
Request ID
Errors and warnings
Warning message
Error message
12. UPDATE TAKE-BACK REQUEST
This operation is used to update an already submitted take-back request.
Input parameters:
Section
Field
Mandatory
Other constraints
Movement
Movement document No
Y
Validated
Request ID
Y
Validated
Take-back
Quantity for take-back mass (tonnes/Mg)
Y, unless volume is provided
Quantity for take-back volume (m 3 )
Y, unless mass is provided
Reasons for requesting take-back
Y
Language code: value
Requirements related to take-back based on a new movement document under the existing notification
N
Language code: value
Date of take-back request
Y
Date format
CA code
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Movement document No
Request ID
Errors and warnings
Warning message
Error message
13. CANCEL MOVEMENT DOCUMENT
This operation is used to cancel the already submitted movement document.
Input parameters:
Section
Field
Mandatory
Other constraints
General
Movement document No
Y
Notification No (existing)
Action code
Y
Cancelation reasons or details
N
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Movement document No
Action ID
Errors and warnings
Warning message
Error message
14. SUBMIT FACILITY COMPLETION CERTIFICATE UNDER ARTICLE 15(5) OF REGULATION (EU) 2024/1157
This operation is used by the subsequent interim or non-interim facility located in the country of destination to submit a certificate confirming completion of treatment of waste shipped thereto according to Article 15(5) of Regulation (EU) 2024/1157.
The column ‘box of Annex I’ refers to box of Annex I of the Delegated Regulation (EU) 2024/2571.
Input parameters:
Section
Field
Mandatory
Other constraints
Box of Annex I
General
Notification No
Y
Validated
1
Movement document No(s)
Y
Validated
2
Facility
Facility type
Y
Disposal / recovery
3
Interim facility
Y
Boolean
3
Operator ID
Y
Validated
UUID
Y
Contact person name
Y
3
Phone number
Y
3
Email address
Y
3
Waste received
Waste identification (list)
Y
4
Waste identification (code)
Y
4
Reception Date
Y
5
Accepted quantity mass (in tonnes/Mg)
Y, unless volume is provided
5
Accepted quantity volume (m 3 )
Y, unless the mass is provided
5
Designation and composition of the waste received
Y
6
Completion certificate
Quantity prepared for re-use or recycled mass (tonnes/Mg)
Y, unless volume is provided
7
Quantity prepared for re-use or recycled volume (m 3 )
Y, unless mass is provided
7
R-code (preparation for re-use or recycling)
Y
7
Quantity recovered in other manner mass (tonnes/Mg)
Y, unless the volume is provided
7
Quantity recovered in other manner volume (m 3 )
Y, unless the mass is provided
7
R-code (other recovery)
Y
7
Quantity disposed mass (tonnes/Mg)
Y, unless the volume is provided
7
Quantity disposed volume (m 3 )
Y, unless the mass is provided
7
D-code
Y
7
Disposal / recovery facility’s declaration
Name of the person authenticating the submission on behalf of the facility
Y
8
Email of the person authenticating the submission on behalf of the facility
N
8
Role of the person authenticating the submission on behalf of the facility in its organization
Y
8
Authentication timestamp
Y
8
Additional authentication string
N
8
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Certificate ID
Errors and warnings
Warning message
Error message
15. UPDATE FACILITY COMPLETION CERTIFICATE UNDER ARTICLE 15(5) OF REGULATION (EU) 2024/1157
This operation is used by the subsequent interim or non-interim facility located in the country of destination to update the already submitted certificate confirming completion of treatment of waste shipped thereto according to Article 15(5) of Regulation (EU) 2024/1157.
The column ‘box of Annex I’ refers to box of Annex I of the Delegated Regulation (EU) 2024/2571.
Input parameters:
Section
Field
Mandatory
Other constraints
Box of Annex I
General
Certificate ID
Y
Validated
Notification No
Y
Validated
1
Movement document No(s)
Y
Validated
2
Facility
Facility type
Y
Disposal / recovery
3
Interim facility
Y
Boolean
3
Operator ID
Y
Validated
UUID
Y
Contact person name
Y
3
Phone number
Y
3
Email address
Y
3
Waste received
Waste identification (list)
Y
4
Waste identification (code)
Y
4
Reception Date
Y
5
Accepted quantity mass (in tonnes/Mg)
Y, unless volume is provided
5
Accepted quantity volume (m 3 )
Y, unless the mass is provided
5
Designation and composition of the waste received
Y
6
Completion certificate
Quantity prepared for re-use or recycled mass (tonnes/Mg)
Y, unless volume is provided
7
Quantity prepared for re-use or recycled volume (m 3 )
Y, unless mass is provided
7
R-code (preparation for re-use or recycling)
Y
7
Quantity recovered in other manner mass (tonnes/Mg)
Y, unless the volume is provided
7
Quantity recovered in other manner volume (m 3 )
Y, unless the mass is provided
7
R-code (other recovery)
Y
7
Quantity disposed mass (tonnes/Mg)
Y, unless the volume is provided
7
Quantity disposed volume (m 3 )
Y, unless the mass is provided
7
D-code
Y
7
Disposal / recovery facility’s declaration
Name of the person authenticating the submission on behalf of the facility
Y
8
Email of the person authenticating the submission on behalf of the facility
N
8
Role of the person authenticating the submission on behalf of the facility in its organization
Y
8
Authentication timestamp
Y
8
Additional authentication string
N
8
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Certificate ID
Errors and warnings
Warning message
Error message
PART C
PROTOCOL FOR EXCHANGE OF DATA RELATED TO INFORMATION AND DOCUMENTATION REFERRED TO IN ARTICLE 27(1), POINTS (B) AND (C), OF REGULATION (EU) 2024/1157
1. SUBMIT ANNEX VII DOCUMENT
This operation is used to submit an Annex VII document. Once submitted, Annex VII document number is generated.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex VII box
Person who arranges the shipment
Operator ID
Y
Validated
UUID
Y
Contact person name
Y
1
Phone number
Y
1
Email address
Y
1
Importer / Consignee
Operator ID
Y
Validated
Contact person name
Y
2
Phone number
Y
2
Email address
Y
2
General
Annex VII document No
N (Y when document is submitted by a CA)
Validated
Shipment
Actual quantity of waste mass (in tonnes/Mg)
Y, unless volume is provided
3
Actual quantity of waste volume (in m 3 )
Y, unless mass is provided
3
Actual date of shipment
Y
4
Container identification no
N
4 a
Recovery operation (or if appropriate disposal operation in the case of waste referred to in Article 4(5) of Regulation (EU) 2024/1157)
R-code / D-code
Y
8
Usual description of the waste
Y
9
Waste identification (list)
Y
10
Waste identification (code)
Y
10
Commodity code(s)
Y for extra-EU shipments
Annex VII document created due to take-back
Y
Boolean
Annex VII document created due to detection of illegal activity
Y
Annex VII document is related to notification No
N
Annex VII document is related to movement document No
N
Annex VII document is related to Annex VII document No
N
Carrier(s)
Operator ID
Y
Validated
Contact person name
Y
5
Phone number
Y
5
Email address
Y
5
Means of transport code
Y
5
Waste producer
Is the person who arranges the shipment also the original waste producer, waste collector or new waste producer?
Y
Boolean
If the answer is No, then the person who arranges the shipment needs to fill in the data of the waste producer
Operator ID
N, unless the ‘Is the person who arranges the shipment also the original waste producer, waste collector or new waste producer?’ is N
Validated
UUID
N, unless the ‘Is the person who arranges the shipment also the original waste producer, waste collector or new waste producer?’ is N
Contact person name
N, unless the ‘Is the person who arranges the shipment also the original waste producer, waste collector or new waste producer?’ is N
6
Phone number
N, unless the ‘Is the person who arranges the shipment also the original waste producer, waste collector or new waste producer?’ is N
6
Email address
N, unless the ‘Is the person who arranges the shipment also the original waste producer, waste collector or new waste producer?’ is N
6
Address of the location from which the shipment starts
Operator ID
Y, unless the rest of the box 6a details are provided
Country code
N
ISO country code
6 a
Postal code
N
6 a
City name
N
6 a
Address details
N
6 a
Longitude
N
Latitude
N
Name of the person responsible for this location
Y
6 a
Phone number
Y
6 a
Email address
Y
6 a
Recovery facility / laboratory
Operator ID
Y
Validated
Facility type
Y
Recovery / Laboratory
7
Interim facility
Y
Contact person name
Y
7
Phone number
Y
7
Email address
Y
7
Name of the waste receiving facility is confidential and shall not be publicly disclosed
Y
Boolean
Explanation why the name of waste receiving facility is confidential under Union or national law
Y if name of the waste treatment facility is confidential
Countries / States concerned
Export / dispatch country
Y
ISO country code
11
Import / destination country
Y
ISO country code
11
Transit country
N
ISO country code
11
Declarations of the person who arranges the shipment
Name of the person authenticating the submission on behalf of the person who arranges the shipment
Y
12
Email of the person authenticating the submission on behalf of the person who arranges the shipment
N
12
Role of the person authenticating the submission on behalf of the person who arranges the shipment in its organization
Y
12
Authentication timestamp
Y
12
Additional authentication string
N
12
UUID
Y
Declarations of the waste producer
Name of the person authenticating the submission on behalf of the waste producer
Y
12
Email of the person authenticating the submission on behalf of the waste producer
N
12
Role of the person authenticating the submission on behalf of the waste producer in its organization
Y
12
Authentication timestamp
Y
12
Additional authentication string
N
12
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Annex VII document No
Errors and warnings
Warning message
Error message
2. UPDATE ANNEX VII DOCUMENT
This operation is used to update Annex VII document.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex VII box
General
Annex VII document No
Y
Person who arranges the shipment
Operator ID
Y
Validated
UUID
Y
Contact person name
Y
1
Phone number
Y
1
Email address
Y
1
Importer / Consignee
Operator ID
Y
Validated
Contact person name
Y
2
Phone number
Y
2
Email address
Y
2
Shipment
Actual quantity of waste mass (in tonnes/Mg)
Y, unless volume is provided
3
Actual quantity of waste volume (in m 3 )
Y, unless mass is provided
3
Actual date of shipment
Y
4
Container identification no
N
4 a
Recovery operation (or if appropriate disposal operation in the case of waste referred to in Article 4(5) of Regulation (EU) 2024/1157)
R-code/D-code
Y
8
Usual description of the waste
Y
9
Waste identification (list)
Y
10
Waste identification (code)
Y
10
Commodity code(s)
Y for extra-EU shipments
Annex VII document created due to take-back
Y
Boolean
Annex VII document created due to detection of illegal activity
Y
Annex VII document is related to notification No
N
Annex VII document is related to movement document No
N
Annex VII document is related to Annex VII document No
N
Carrier(s)
Operator ID
Y
Validated
Contact person name
Y
5
Phone number
Y
5
Email address
Y
5
Means of transport code
Y
5
Waste producer
Is the person who arranges the shipment also the original waste producer, waste collector or new waste producer?
Y
Boolean
If the answer is No, then the person who arranges the shipment needs to fill in the data of the waste producer
Operator ID
N, unless the ‘Is the person who arranges the shipment also the original waste producer, waste collector or new waste producer?’ is Y
Validated
UUID
N, unless the ‘Is the person who arranges the shipment also the original waste producer, waste collector or new waste producer?’ is Y
Contact person name
N, unless the ‘Is the person who arranges the shipment also the original waste producer, waste collector or new waste producer?’ is Y
6
Phone number
N, unless the ‘Is the person who arranges the shipment also the original waste producer, waste collector or new waste producer?’ is Y
6
Email address
N, unless the ‘Is the person who arranges the shipment also the original waste producer, waste collector or new waste producer?’ is Y
6
Address of the location from which the shipment starts
Operator ID
Y, unless the rest of the box 6a details are provided
Country code
N
6 a
Postal code
N
6 a
City name
N
6 a
Address details
N
6 a
Longitude
N
6 a
Latitude
N
Name of the person responsible for this location
Y
6 a
Phone number
Y
6 a
Email address
Y
6 a
Recovery facility / laboratory
Operator ID
Y
Validated
Facility type
Y
Recovery / Laboratory
7
Interim facility
Y
Contact person name
Y
7
Phone number
Y
7
Email address
Y
7
Name of the waste receiving facility is confidential and shall not be publicly disclosed
Y
Boolean
Explanation why the name of waste receiving facility is confidential under Union or national law
Y if name of the waste treatment facility is confidential
Countries / States concerned
Export / dispatch country
Y
ISO country code
11
Import / destination country
Y
ISO country code
11
Transit country
N
ISO country code
11
Declarations of the person who arranges the shipment
Name of the person authenticating the submission on behalf of the person who arranges the shipment
Y
12
Email of the person authenticating the submission on behalf of the person who arranges the shipment
N
12
Role of the person authenticating the submission on behalf of the person who arranges the shipment in its organization
Y
12
Authentication timestamp
Y
12
Additional authentication string
N
12
UUID
Y
Declarations of the waste producer
Name of the person authenticating the submission on behalf of the waste producer
Y
12
Email of the person authenticating the submission on behalf of the waste producer
N
12
Role of the person authenticating the submission on behalf of the waste producer in its organization
Y
12
Authentication timestamp
Y
12
Additional authentication string
N
12
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Annex VII document No
Errors and warnings
Warning message
Error message
3. SUBMIT CARRIER TRANSFER CONFIRMATION – ANNEX VII DOCUMENT
This operation is used by carrier(s) to submit a confirmation of receipt of waste with respect to waste shipped based on a given Annex VII document.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex VII box
Movement
Annex VII document No
Y
Validated
Carrier Transfer
Operator ID
Y
Validated
UUID
Y
Means of transport
Y
Validated
5
Transfer date
Y
Date format
Declaration of the carrier who takes-over the shipment
Name of the person authenticating the submission on behalf of carrier
Y
5
Email of the person authenticating the submission on behalf of carrier
N
5
Role of the person authenticating the submission on behalf of carrier in its organization
Y
5
Authentication timestamp
Y
5
Additional authentication string
N
5
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Annex VII document No
Confirmation ID
Errors and warnings
Warning message
Error message
4. UPDATE CARRIER TRANSFER CONFIRMATION – ANNEX VII DOCUMENT
This operation is used by carrier(s) to update a confirmation of receipt of waste with respect to waste shipped based on a given Annex VII document.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex VII box
Movement
Annex VII document No
Y
Validated
Confirmation ID
Y
Validated
Carrier Transfer
Operator ID
Y
Validated
UUID
Y
Means of transport
Y
Validated
5
Transfer date
Y
Date format
Declaration of the carrier who takes-over the shipment
Name of the person authenticating the submission on behalf of carrier
Y
5
Email of the person authenticating the submission on behalf of carrier
N
5
Role of the person authenticating the submission on behalf of carrier in its organization
Y
5
Authentication timestamp
Y
5
Additional authentication string
N
5
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Annex VII document No
Confirmation ID
Errors and warnings
Warning message
Error message
5. SUBMIT CONSIGNEE RECEPTION CONFIRMATION – ANNEX VII DOCUMENT
This operation is used to submit consignee reception confirmation concerning waste shipped based on Annex VII documents.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex VII box
Movement
Annex VII document No
Y
Validated
Importer / Consignee
Operator ID
Y
Validated
UUID
Y
Contact person name
Y
2
Phone number
Y
2
Email address
Y
2
Reception
Reception Date
Y
13
Declarations of the consignee
Name of the person authenticating the submission on behalf of the consignee
Y
13
Email of the person authenticating the submission on behalf of the consignee
N
13
Role of the person authenticating the submission on behalf of the consignee in its organization
Y
13
Authentication timestamp
Y
13
Additional authentication string
N
13
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Annex VII document No
Confirmation ID
Errors and warnings
Warning message
6. UPDATE CONSIGNEE RECEPTION CONFIRMATION – ANNEX VII DOCUMENT
This operation is used to update consignee reception confirmation concerning waste shipped based on Annex VII documents.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex VII box
Movement
Annex VII document No
Y
Validated
Confirmation ID
Y
Validated
Importer / Consignee
Operator ID
Y
Validated
UUID
Y
Contact person name
Y
2
Phone number
Y
2
Email address
Y
2
Reception
Reception Date
Y
13
Declarations of the consignee
Name of the person authenticating the submission on behalf of the consignee
Y
13
Email of the person authenticating the submission on behalf of the consignee
N
13
Role of the person authenticating the submission on behalf of the consignee in its organization
Y
13
Authentication timestamp
Y
13
Additional authentication string
N
13
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Annex VII document No
Confirmation ID
Errors and warnings
Warning message
7. SUBMIT FACILITY RECEPTION CONFIRMATION – ANNEX VII DOCUMENT
This operation is used to submit facility reception confirmation concerning waste shipped based on Annex VII documents.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex VII box
Movement
Annex VII document No
Y
Validated
Recovery facility / laboratory
Facility type
Y
Recovery / Laboratory
7
Operator ID
Y
Validated
UUID
Y
Interim facility
Y
Contact person name
Y
7
Phone number
Y
7
Email address
Y
7
Reception
Reception Date
Y
14
Accepted quantity mass (tonnes/Mg)
Y, unless volume is provided
14
Accepted quantity volume (m 3 )
Y, unless mass is provided
14
Rejected quantity mass (tonnes/Mg)
Y, unless volume is provided
14
Rejected quantity volume (m 3 )
Y, unless mass is provided
14
Rejection description
Y
Language code: value
14
Waste identification (list)
Y
Waste identification (code)
Y
Designation and composition of the waste received
Y
Declarations of the facility
Name of the person authenticating the submission on behalf of the facility
Y
14
Email of the person authenticating the submission on behalf of the facility
N
14
Role of the person authenticating the submission on behalf of the facility in its organization
Y
14
Authentication timestamp
Y
14
Additional authentication string
N
14
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Annex VII document No
Confirmation ID
Errors and warnings
Warning message
Error message
8. UPDATE FACILITY RECEPTION CONFIRMATION – ANNEX VII DOCUMENT
This operation is used to update facility reception confirmation concerning waste shipped based on Annex VII documents.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex VII box
Movement
Annex VII document No
Y
Validated
Confirmation ID
Y
Validated
Recovery facility / laboratory
Facility type
Y
Recovery / Laboratory
7
Operator ID
Y
Validated
UUID
Y
Interim facility
Y
Contact person name
Y
7
Phone number
Y
7
Email address
Y
7
Reception
Reception Date
Y
14
Accepted quantity mass (tonnes/Mg)
Y, unless volume is provided
=
14
Accepted quantity volume (m 3 )
Y, unless mass is provided
14
Rejected quantity mass (tonnes/Mg)
Y, unless volume is provided
14
Rejected quantity volume (m 3 )
Y, unless mass is provided
14
Rejection description
Y
Language code: value
14
Waste identification (list)
Y
Waste identification (code)
Y
Designation and composition of the waste received
Y
Declarations of the facility
Name of the person authenticating the submission on behalf of the facility
Y
14
Email of the person authenticating the submission on behalf of the facility
N
14
Role of the person authenticating the submission on behalf of the facility in its organization
Y
14
Authentication timestamp
Y
14
Additional authentication string
N
14
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Annex VII document No
Confirmation ID
Errors and warnings
Warning message
Error message
9. SUBMIT FACILITY COMPLETION CERTIFICATE – ANNEX VII DOCUMENT
This operation is used to submit facility completion certificate concerning treatment of waste shipped based on Annex VII documents.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex VII box
Movement
Annex VII document No
Y
Validated
Facility
Facility type
Y
Recovery/Laboratory
7
Operator ID
Y
Validated
UUID
Y
Interim facility
Y
Contact person name
Y
7
Phone number
Y
7
Email address
Y
7
Fax number
N
7
Website URL
N
7
Completion certificate
Certificate Date
Y
15
Quantity prepared for re-use or recycled mass (tonnes/Mg)
Y, unless volume is provided
15
Quantity prepared for re-use or recycled volume (m 3 )
Y, unless mass is provided
15
Quantity recovered in other manner mass (tonnes/Mg)
Y, unless volume is provided
15
Quantity recovered in other manner volume (m 3 )
Y, unless mass is provided
15
Waste identification (list)
Y
Waste identification (code)
Y
Designation and composition of the waste received
Y
Declarations of the facility
Name of the person authenticating the submission on behalf of the facility
Y
15
Email of the person authenticating the submission on behalf of the facility
N
15
Role of the person authenticating the submission on behalf of the facility in its organization
Y
15
Authentication timestamp
Y
15
Additional authentication string
N
15
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Annex VII document No
Certificate ID
Errors and warnings
Warning message
Error message
10. UPDATE FACILITY COMPLETION CERTIFICATE – ANNEX VII DOCUMENT
This operation is used to update facility completion certificate concerning treatment of waste shipped based on Annex VII documents.
Input parameters:
Section
Field
Mandatory
Other constraints
Annex VII box
Movement
Annex VII document No
Y
Validated
Certificate ID
Y
Validated
Facility
Facility type
Y
Recovery / Laboratory
7
Operator ID
Y
Validated
UUID
Y
Interim facility
Y
Contact person name
Y
7
Phone number
Y
7
Email address
Y
7
Fax number
N
7
Website URL
N
7
Completion certificate
Certificate Date
Y
15
Quantity prepared for re-use or recycled mass (tonnes/Mg)
Y, unless volume is provided
15
Quantity prepared for re-use or recycled volume (m 3 )
Y, unless mass is provided
15
Quantity recovered in other manner mass (tonnes/Mg)
Y, unless volume is provided
15
Quantity recovered in other manner volume (m 3 )
Y, unless mass is provided
15
Waste identification (list)
Y
Waste identification (code)
Y
Designation and composition of the waste received
Y
Declarations of the facility
Name of the person authenticating the submission on behalf of the facility
Y
15
Email of the person authenticating the submission on behalf of the facility
N
15
Role of the person authenticating the submission on behalf of the facility in its organization
Y
15
Authentication timestamp
Y
15
Additional authentication string
N
15
UUID
Y
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Annex VII document No
Certificate ID
Errors and warnings
Warning message
Error message
11. SUBMIT TAKE-BACK REQUEST – ANNEX VII DOCUMENT
This operation is used to submit a take-back request concerning waste to be shipped based on Annex VII document.
Input parameters:
Section
Field
Mandatory
Other constraints
Movement
Annex VII document No
Y
Validated
Take-back
Quantity for take-back mass (tonnes/Mg)
Y, unless volume is provided
Quantity for take-back volume (m 3 )
Y, unless mass is provided
Reasons for requesting take-back
Y
Language code: value
Date of take-back request
Y
Date
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Annex VII document No
Request ID
Errors and warnings
Warning message
Error message
12. UPDATE TAKE-BACK REQUEST – ANNEX VII DOCUMENT
This operation is used by competent authority to update the submitted take-back request concerning waste to be shipped based on Annex VII document.
Input parameters:
Section
Field
Mandatory
Other constraints
Movement
Annex VII document No
Y
Validated
Request ID
Y
Take-back
Quantity for take-back mass (tonnes/Mg)
Y, unless volume is provided
Quantity for take-back volume (m 3 )
Y, unless mass is provided
Reasons for requesting take-back
Y
Language code: value
Date of take-back request
Y
Date
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Annex VII document No
Request ID
Errors and warnings
Warning message
Error message
13. CANCEL ANNEX VII DOCUMENT
This operation is used to cancel the already submitted Annex VII document.
Input parameters:
Section
Field
Mandatory
Other constraints
General
Annex VII document No
Y
Annex VII document No (existing)
Action code
Y
Cancelation reasons or details
N
Attachment
List of attachment IDs
N
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Annex VII document No
Action ID
Errors and warnings
Warning message
Error message
PART D
PROTOCOL FOR EXCHANGE OF DATA RELATED TO DECISIONS TO ISSUE PRE-CONSENTS TO SPECIFIC RECOVERY FACILITIES REFERRED TO IN ARTICLE 27(1), POINT (A)(IX), OF REGULATION (EU) 2024/1157
1. SUBMIT INFORMATION ON NEW PRE-CONSENTED FACILITY
This operation is used to submit information on a new pre-consented facility.
Input parameters:
Section
Field
Mandatory
Other constraints
Pre-consented facility
Main identification number (name)
N
Main identification number (value)
N
Facility name
Y
Validated
Operator ID
Y
Validated
Country code
Y
Postal code
Y
City name
Y
Address details
Y
Latitude
N
Longitude
N
Pre-Consent
Waste treatment operation code
Y
Validated
Waste identification (list)
Y
Waste identification (code)
Y
Pre-consented quantity of waste mass (in tonnes/Mg)
Y, unless volume is provided
Pre-consented quantity of waste volume (in m 3 )
Y, unless mass is provided
Start date
Y
Date format
End date
Y
Date format
Code of the CA who issued a pre-consent for the facility
Y
Attachment
List of attachment IDs
Y
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Entry ID
Errors and warnings
Warning message
Error message
2. UPDATE INFORMATION ON PRE-CONSENTED FACILITY
This operation is used to update information on pre-consented facility.
Input parameters:
Section
Field
Mandatory
Other constraints
Pre-consented facility
Main identification number (name)
N
Main identification number (value)
N
Facility name
Y
Validated
Operator ID
Y
Validated
Country code
Y
Postal code
Y
City name
Y
Address details
Y
Latitude
N
Longitude
N
Pre-Consent
Entry ID
Y
Validated
Waste treatment operation code
Y
Validated
Waste code(s)
Y
Validated
Pre-consented quantity of waste mass (in tonnes/Mg)
Y, unless volume is provided
Pre-consented quantity of waste volume (in m 3 )
Y, unless mass is provided
Start date
Y
Date format
End date
Y
Date format
Code of the CA who issued and updated the pre-consent for the facility
Y
Attachment
List of attachment IDs
Y
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Entry ID
Errors and warnings
Warning message
Error message
PART E
PROTOCOL FOR EXCHANGE OF DATA RELATED TO OTHER OPERATIONS
1. UPLOAD ATTACHMENT
This operation is used to upload attachments to a given file in the system.
Input parameters:
Section
Field
Mandatory
Other constraints
Attachments
Attachment type
Y
Validated
MIME code
Y
File name
Y
File content
Y
Attachment contains personal data
Y
Boolean
Output parameters:
Section
Parameter
General
Call status code
Specific
Attachment ID
Errors and warnings
Warning message
Error message
2. CREATE OPERATOR
This operation is used to create a new operator in the system.
Input parameters:
Section
Field
Mandatory
Other constraints
Operator
Main identification number (name)
Y, unless linked with another operator
Main identification number (value)
Y, unless linked with another operator
Linked operator’s ID
N
Validated
Registration number (name)
Y
Registration number (value)
Y
Other identifier name
N
Other identifier value
N
Operator’s name
Y
Country code
Y
Postal code
Y
City name
Y
Address details
Y
Latitude
N
Longitude
N
Contact person name
Y
Phone number
Y
Email address
Y
Fax number
N
Website URL
N
CA responsible for operator’s registration
Y
Business chapter
Y
Validated
Business section
Y
Validated
Role in the system
Y
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Main identification number (name)
Main identification number (value)
Operator ID
Errors and warnings
Warning message
Error message
3. UPDATE OPERATOR
This operation is used to update a new operator in the system.
Input parameters:
Section
Field
Mandatory
Other constraints
Operator
Main identification number (name)
Y, unless linked with another operator
Main identification number (value)
Y, unless linked with another operator
Operator ID
Y
Linked operator’s ID
N
Validated
Registration number (name)
Y
Registration number (value)
Y
CA responsible for operator’s registration
Y
Other identifier name
N
Other identifier value
N
Operator’s name
Y
Country code
Y
Postal code
Y
City name
Y
Address details
Y
Latitude
N
Longitude
N
Contact person name
Y
Phone number
Y
Email address
Y
Fax number
N
Website URL
N
Business chapter
Y
Validated
Business section
Y
Validated
Role in the system
Y
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Main identification number (name)
Main identification number (value)
Operator ID
Errors and warnings
Warning message
Error message
PART F
PROTOCOL FOR EXCHANGE OF DATA RELATED TO OTHER SYNCHRONISATION OPERATIONS
Operations listed in this Part are used by users accessing the central system via the API in order to retrieve the data that was inserted in the central system by users accessing it via the GUI or API.
1. GET ALL ACTIONS
This operation allows to retrieve the list of actions IDs in which a given actor is involved. In result of its performance, a list of notifications, movement documents and Annex VII documents will be displayed.
Input parameters:
Section
Field
Mandatory
Other constraints
General
From date
N
Date
To date
N
Date
Notification No
N
Movement document No
N
Annex VII document No
N
Output parameters:
Section
Parameter
General
Call status code
Specific
Action ID(s) (list)
Errors and warnings
Warning message
Error message
2. GET ALL NOTIFICATIONS
This operation allows to retrieve a list of notifications submitted in a given period of time.
Input parameters:
Section
Field
Mandatory
Other constraints
General
From date
N
Date
To date
N
Date
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Submission date (timestamp)
Last update date (timestamp)
Errors and warnings
Warning message
Error message
3. GET NOTIFICATION BY ID
Description: This operation allows to retrieve the content of a notification searched based on its number.
Input parameters:
Section
Field
Mandatory
Other constraints
General
Notification No
Y
Validated
Output parameters:
Section
Field
General
Call status code
Errors and warnings
Warning message
Error message
Exporter – Notifier
Operator ID
UUID
Contact person name
Phone number
Email address
Importer – Consignee
Operator ID
UUID
Contact person name
Phone number
Email address
Address of the location from which the shipment starts
Operator ID
Address details
Submission
Notification No
Notification status
Timestamp of the submission
Individual shipment
Destined for (recovery / disposal)
Destined for pre-consented recovery facility
Declined pre-consented facility status for a given notification
Extended timeline for decision even though shipment is destined for pre-consented facility
Total intended number of shipments
Total waste quantity mass (in tonnes/Mg)
Total waste quantity volume (in m 3 )
Intended period of time of shipment(s): first departure
Intended period of time of shipment(s): last departure
Packaging type (code(s))
Packaging description
Special handling
Disposal / recovery operation(s)
D-code / R-code:
Technology employed
Reason for export
Designation and composition of waste
Physical characteristics (code)
Physical characteristics description
Customs code(s) (HS)
Waste identification (list)
Waste identification (code)
Eligible for pre-consent
Some shipments under the notification are subject to take-back
Notification created due to take-back
Notification created due to detection of illegal activity
Notification is related to notification or Annex VII document no
Notification is related to other notification Nos: (list them)
Intended carrier(s)
Operator ID
UUID
Contact person name
Phone number
Email address
Means of transport (code)
Waste generator(s) – producer(s)
Operator ID
UUID
Contact person name
Phone number
Email address
Site of generation description
Process of generation description
Facility receiving waste
Operator ID
UUID
Facility type
Interim facility
Subsequent interim or non-interim facility located in the country of destination
Subsequent interim or non-interim facility located in another country than the country of destination
Contact person name
Phone number
Email address
Actual site of disposal/recovery
Countries / States concerned
State of export – dispatch
Code No of competent authority of state of export – dispatch
Specific point of exit (border crossing or port)
State of import – destination
Code No of competent authority of state of import – destination
Specific point of entry (border crossing or port)
State(s) of transit
Code No of competent authority of state of transit
Specific point of entry (border crossing or port)
Specific point of exit (border crossing or port)
Customs offices of entry and/or exit and/or export
EU entry office
EU exit office
EU export office
Alternative routing – Customs offices of entry and/or exit and/or export
EU entry office
EU exit office
EU export office
Exporter’s – notifier’s – generator’s – producer’s declaration
Name of the person authenticating the submission on behalf of exporter/notifier
Email of the person authenticating the submission on behalf of the exporter / notifier
Role of the person authenticating the submission on behalf of exporter / notifier in its organisation
Exporter’s – notifier’s authentication timestamp
Exporter’s – notifier’s additional authentication string
UUID
Name of the person authenticating the submission on behalf of generator / producer
Email of the person authenticating the submission on behalf of generator / producer
Role of the person authenticating the submission on behalf of generator / producer in its organisation
Generator’s – producer’s authentication timestamp
Generator’s – producer’s additional authentication string
UUID
Submission’s attachment(s)
Attachment ID
Attachment type
Attachment file name
Attachment contains personal data
Deadlines
Deadline for considering the notification properly carried out
Deadline for considering the notification properly completed (CA code: date)
Deadline for considering the notification invalid (CA code: date)
Deadline for submission of request for additional information (CA code: date)
Deadline for submission of decision
Properly carried out
Timestamp of the operation
CA code
Action ID
On behalf of CA code
On behalf of role
Properly completed
Timestamp of the operation
CA code
Action ID
On behalf of CA code
On behalf of role
Notification invalidated
Timestamp of the operation
CA code
Action ID
On behalf of CA code
On behalf of role
Notification re-validated
Timestamp of the operation
CA code
Action ID
On behalf of CA code
On behalf of role
Notification completed
Timestamp of the operation
CA code
Action ID
On behalf of CA code
On behalf of role
Notification cancelled
Timestamp of the operation
Cancelation reasons or details
List of attachment IDs
Action ID
On behalf of CA code
On behalf of role
Request(s) for information
Timestamp of the request for information
Additional time for reply
Deadline for submission of reply for request for information
ID of the request for information
CA code
CA role in the notification
On behalf of CA code
On behalf of role
Request language
Request content
Attachment ID
Attachment type
Attachment file name
Attachment contains personal data
Name of the person authenticating the submission on behalf of CA
Email of the person authenticating the submission on behalf of CA
Role of the person authenticating the submission on behalf of CA in its organization
CA representative authentication timestamp
CA representative authentication string
Reply to request for information
Timestamp of the reply
ID of the reply
ID of the request for information
Role who provided the reply
Code who provided the reply
Reply language
Replay content
Attachment ID
Attachment type
Attachment file name
Attachment contains personal data
Name of the person authenticating the submission on behalf of the notifier
Email of the person authenticating the submission on behalf of the notifier
Role of the person authenticating the submission on behalf of the notifier in its organization
Notifier’s representative authentication timestamp
Notifier’s representative authentication string
Acknowledgement
CA code
On behalf of CA code
On behalf of CA country code
On behalf of CA role
CA role in the notification
Acknowledgement date
Acknowledgment ID
Notification receipt date
Name of the person authenticating the submission on behalf of CA
Email of the person authenticating the submission on behalf of CA
Role of the person authenticating the submission on behalf of CA in its organization
CA representative authentication timestamp
CA representative additional authentication string
Acknowledgment attachment(s) ID(s)
Pre-consented facility status declined
On behalf of CA code
On behalf of CA country code
On behalf of CA role
CA code
CA role in the notification
Date of action
Name of the person authenticating the submission on behalf of CA
Email of the person authenticating the submission on behalf of CA
Role of the person authenticating the submission on behalf of CA in its organization
CA representative authentication timestamp
CA representative additional authentication string
Disregarded timelines (Article 14(16) of Regulation (EU) 2024/1157)
On behalf of CA code
On behalf of CA country code
On behalf of CA role
CA code
CA role in the notification
Date of action
Name of the person authenticating the submission on behalf of CA
Email of the person authenticating the submission on behalf of CA
Role of the person authenticating the submission on behalf of CA in its organization
CA representative authentication timestamp
CA representative additional authentication string
Decision
CA code
CA role in the notification process
On behalf of CA code
On behalf of CA country code
On behalf of role
Decision ID
Decision date
Decision type
(consent / consent with conditions / objection)
Specific conditions on consenting to the movement document
Specific conditions: consent valid only for waste quantity not exceeding the following mass (in tonnes/Mg)
Specific conditions: consent valid only for waste quantity not exceeding the following volume (in m 3 ):
Specific conditions: consent valid only for the following number of shipments:
Consent valid from date
Consent valid until date
Reasons for objection
Duly reasoned justification of the decision
Name of the person authenticating the submission on behalf of CA
Email of the person authenticating the submission on behalf of CA
Role of the person authenticating the submission on behalf of CA
CA representative authentication timestamp
CA representative additional authentication string
Decision attachment ID
Decision attachment type
Decision attachment file name
Decision attachment contains personal data
Decision withdrawn
CA code
CA role in the notification process
On behalf of CA code
On behalf of CA country code
On behalf of role
Decision ID
Timestamp of the operation
Reasons for withdrawal
Withdrawal date
Attachment ID
Attachment type
Attachment file name
Attachment contains personal data
Action ID
Name of the person authenticating the submission on behalf of CA
Email of the person authenticating the submission on behalf of CA
Role of the person authenticating the submission on behalf of CA
CA representative authentication timestamp
CA representative additional authentication string
Request for change after consent (Article 17 of Regulation (EU) 2024/1157)
Timestamp of the request for change after consent
ID of the request for change
Request status
Does the request cover change of the route of the shipment?
Request language
Request content
Attachment ID
Attachment type
Attachment file name
Attachment contains personal data
Name of the person authenticating the submission on behalf of the notifier
Email of the person authenticating the submission on behalf of the notifier
Role of the person authenticating the submission on behalf of the notifier in its organization
Notifier’s representative authentication timestamp
Notifier’s representative authentication string
Name of the person authenticating the submission on behalf of generator / producer
Email of the person authenticating the submission on behalf of generator / producer
Role of the person authenticating the submission on behalf of generator / producer in its organisation
Generator’s – producer’s authentication timestamp
Generator’s – producer’s additional authentication string
Reply to request for change after consent (Article 17 of Regulation (EU) 2024/1157)
Timestamp of the request for change after consent
ID of the request for change after consent
CA role in the notification
On behalf of CA code
On behalf of role
Agreement
Reasons for agreement / disagreement
Attachment ID
Attachment type
Attachment file name
Attachment contains personal data
Name of the person authenticating the submission on behalf of CA
Email of the person authenticating the submission on behalf of CA
Role of the person authenticating the submission on behalf of CA in its organization
CA representative authentication timestamp
CA representative authentication string
Facility completion certificate under Article 15(5) of Regulation (EU) 2024/1157
Certificate ID
Notification No
Movement document No(s)
Facility type
Interim facility
Operator ID
Contact person name
Phone number
Email address
Waste identification (list)
Waste identification (code)
Reception Date
Accepted quantity mass (in tonnes/Mg)
Accepted quantity volume (m 3 )
Designation and composition of the waste received
Quantity prepared for re-use or recycled mass (tonnes/Mg)
Quantity prepared for re-use or recycled volume (m 3 )
R-code (preparation for re-use or recycling)
Quantity recovered in other manner mass (tonnes/Mg)
Quantity recovered in other manner volume (m 3 )
R-code (other recovery)
Quantity disposed mass (tonnes/Mg)
Quantity disposed volume (m 3 )
D-code
Name of the person authenticating the submission on behalf of the facility
Email of the person authenticating the submission on behalf of the facility
Role of the person authenticating the submission on behalf of the facility in its organization
Authentication timestamp
Additional authentication string
Attachment ID
Attachment file name
Attachment type
Attachment contains personal data
Movement documents
Movement documents(s) ID(s)
4. GET ALL MOVEMENT DOCUMENTS BY NOTIFICATION NUMBER
The operation allows to retrieve a list of movement documents related to a specific notification based on its number.
Input parameters:
Section
Field
Mandatory
Other constraints
General
Notification No
Y
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
Movement document no
Submission date (timestamp)
Last update date (timestamp)
Errors and warnings
Warning message
Error message
5. GET MOVEMENT DOCUMENT BY ID
Description: This operation allows to retrieve the content of a movement document searched based on its number.
Input parameters:
Section
Field
Mandatory
Other constraints
General
Movement document No
Y
Validated
Output parameters:
Section
Field
General
Call status code
Errors and warnings
Warning message
Error message
Movement
Movement document No
Movement document status
Notification No
Movement document created due to take-back
Movement document created due to detection of illegal activity
Movement document is related to movement document No
Serial/total number of shipments
Container identification number
Actual quantity of waste mass (tonnes/Mg)
Actual quantity of waste volume (m 3 )
Actual date of shipment
Packaging type (code(s))
Packaging description
Number of packages
Additional information related to the shipment
Address of the location from which the shipment starts
Address details
Carrier(s)
Operator ID
Contact person name
Phone number
Email address
Waste generator(s) – producer(s)
Operator ID
Contact person name
Phone number
Email address
Site of generation description
Disposal / recovery facility
Actual site of disposal / recovery
Declarations and authentications
Operator submitting the declaration
Name of the person authenticating the submission on behalf of exporter / notifier
Email of the person authenticating the submission on behalf of the exporter / notifier
Role of the person authenticating the submission on behalf of exporter / notifier in its organisation
Exporter’s – notifier’s authentication timestamp
Exporter’s – notifier’s additional authentication string
Carrier Transfer(s)
Confirmation ID
Operator ID
Means of transport
Transfer date
Name of the person authenticating the submission on behalf of carrier
Email of the person authenticating the submission on behalf of carrier
Role of the person authenticating the submission on behalf of carrier in its organization
Authentication timestamp
Additional authentication string
Carrier transfer’s attachment ID
Carrier transfer’s attachment type
Carrier transfer’s attachment file name
Carrier transfer’s attachment contains personal data
Consignee reception confirmation
Confirmation ID
Operator ID
Contact person name
Phone number
Email address
Reception Date
Name of the person authenticating the submission on behalf of consignee
Email of the person authenticating the submission on behalf of consignee
Role of the person authenticating the submission on behalf of consignee in its organization
Authentication timestamp
Additional authentication string
Consignee reception attachment ID
Consignee reception attachment type
Consignee reception attachment file name
Consignee reception attachment contains personal data
Facility reception confirmation
Confirmation ID
Operator ID
Contact person name
Phone number
Email address
Interim facility
Actual site of disposal/recovery
Reception Date
Accepted quantity mass (tonnes/Mg)
Accepted quantity volume (m 3 )
Rejected quantity mass (tonnes/Mg)
Rejected quantity volume (m 3 )
Rejection description
Approximate date of disposal / recovery
Disposal / Recovery operation code
Waste identification (list)
Waste identification (code)
Designation and composition of the waste received
Name of the person authenticating the submission on behalf of the facility
Email of the person authenticating the submission on behalf of the facility
Role of the person authenticating the submission on behalf of the facility in its organization
Authentication timestamp
Additional authentication string
Facility reception attachment ID
Facility reception attachment type
Facility reception attachment file name
Facility reception attachment contains personal data
Facility completion certificate
Certificate ID
Facility type
Operator ID
Contact person name
Phone number
Email address
Interim facility
Actual site of disposal/recovery
Certificate Date
Waste identification (list)
Waste identification (code)
Quantity prepared for re-use or recycled mass (tonnes/Mg)
Quantity prepared for re-use or recycled volume (m 3 )
Quantity recovered in other manner mass (tonnes/Mg)
Quantity recovered in other manner volume (m 3 )
Quantity disposed of mass (tonnes/Mg)
Quantity disposed of volume (m 3 )
Name of the person authenticating the submission on behalf of the facility
Email of the person authenticating the submission on behalf of the facility
Role of the person authenticating the submission on behalf of the facility in its organization
Authentication timestamp
Additional authentication string
Attachment ID
Attachment type
Attachment file name
Attachment contains personal data
Take-back
Action ID
Quantity for take-back mass (tonnes/Mg)
Quantity for take-back volume (m 3 )
Reasons for requesting take-back
Requirements related to take-back based on a new movement document under the existing notification
Date of take-back request
Attachment ID
Attachment type
Attachment file name
Attachment contains personal data
Cancelation
Action ID
Timestamp of the operation
Cancelation reasons or details
Attachment ID
Attachment type
Attachment file name
Attachment contains personal data
CA code who performed the action
Operator ID who performed the action
Customs offices actions
Action ID
Country of export – dispatch
Customs office of exit
Date when waste left the country
Competent customs office
Action timestamp
Action ID
Country of import – destination
Customs office of entry
Date when waste entered the country
Competent customs office
Action timestamp
Action ID
Country of transit
Customs office of transit
Date when waste entered the country
Date when waste left the country
Competent customs office
Action timestamp
Movement document attachments
Attachment ID
Attachment type
Attachment file name
Attachment contains personal data
6. GET ATTACHMENT DETAILS BY ID
This operation allows to retrieve details and content of an attachment searched based on its ID.
Input parameters:
Section
Field
Mandatory
Other constraints
General
Attachment ID
Y
Output parameters:
Section
Parameter
General
Call status code
Specific
Attachment ID
Attachment type
Attachment contains personal data
MIME code
Encoding code
File name
File content
Errors and warnings
Warning message
Error message
7. GET ALL ANNEX VII DOCUMENTS
This operation allows to retrieve a list of all the Annex VII documents submitted in a given period of time.
Input parameters:
Section
Field
Mandatory
Other constraints
General
From date
N
Date
To date
N
Date
Output parameters:
Section
Parameter
General
Call status code
Specific
Annex VII documents No(s) (list)
Submission date (timestamp)
Last update date (timestamp)
Errors and warnings
Warning message
Error message
8. GET ANNEX VII DOCUMENT BY ID
This operation allows to retrieve the content of an Annex VII document searched based on its number.
Input parameters:
Section
Field
Mandatory
Other constraints
General
Annex VII document No
Y
Validated
Output parameters:
Section
Parameter
General
Annex VII document No
Annex VII document status
Annex VII document submission date
Annex VII document created due to take-back
Annex VII document created due to detection of illegal activity
Annex VII document is related to notification No
Annex VII document is related to movement document No
Annex VII document is related to Annex VII document No
Errors and warnings
Call status code
Warning message
Error message
Person who arranges the shipment
Operator ID
Contact person name
Phone number
Email address
Importer / Consignee
Operator ID
Contact person name
Phone number
Email address
Shipment
Actual quantity of waste mass (tonnes/Mg)
Actual quantity of waste volume (m 3 )
Actual date of shipment
Container identification no
Recovery operation (or if appropriate disposal operation in the case of waste referred to in Article 4(5) of Regulation (EU) 2024/1157)
R-code / D-code
Usual description of waste
Waste identification (list)
Waste identification (code)
Commodity code(s)
Carrier(s)
Operator ID
Contact person name
Phone number
Email address
Means of transport code
Waste producer
Is the person who arranges the shipment also the original waste producer, waste collector or new waste producer?
Operator ID
Contact person name
Phone number
Email address
Fax number
Website URL
Address of the location from which the shipment starts
Operator ID
Country code
Postal code
City name
Address details
Longitude
Latitude
Name of the person responsible for this location
Phone number
Email address
Contact person name
Phone number
Email address
Facility
Operator ID
Facility type
Interim facility
Contact person name
Phone number
Email address
Name of the waste receiving facility is confidential and shall not be publicly disclosed
Explanation why the name of waste receiving facility is confidential under Union or national law
Countries / States concerned
Export / dispatch country
Import / destination country
Transit country
Declarations of the person who arranges the shipment
Name of the person authenticating the submission on behalf of the person who arranges the shipment
Email of the person authenticating the submission on behalf of the person who arranges the shipment
Role of the person authenticating the submission on behalf of the person who arranges the shipment in its organization
Authentication timestamp
Additional authentication string
Declarations of the waste producer
Name of the person authenticating the submission on behalf of the waste producer
Email of the person authenticating the submission on behalf of the waste producer
Role of the person authenticating the submission on behalf of the waste producer in its organization
Authentication timestamp
Additional authentication string
Annex VII document attachment(s)
Attachment ID
Attachment type
Attachment file name
Attachment contains personal data
Carrier transfer confirmation(s)
Confirmation ID
Operator ID
Means of transport
Transfer date
Name of the person authenticating the submission on behalf of carrier
Email of the person authenticating the submission on behalf of carrier
Role of the person authenticating the submission on behalf of carrier in its organization
Authentication timestamp
Additional authentication string
Attachments ID
Attachment type
Attachment file name
Attachment contains personal data
Consignee reception confirmation
Operator ID
Contact person name
Phone number
Email address
Reception Date
Name of the person authenticating the submission on behalf of the consignee
Email of the person authenticating the submission on behalf of the consignee
Role of the person authenticating the submission on behalf of the consignee in its organization
Authentication timestamp
Additional authentication string
Attachment ID
Attachment type
Attachment file name
Attachment contains personal data
Facility reception confirmation
Confirmation ID
Operator ID
Contact person name
Phone number
Email address
Interim facility
Reception Date
Accepted quantity mass (tonnes/Mg)
Accepted quantity volume (m 3 )
Rejected quantity mass (tonnes/Mg)
Rejected quantity volume (m 3 )
Rejection description
Waste identification (list)
Waste identification (code)
Designation and composition of the waste received
Name of the person authenticating the submission on behalf of the facility
Email of the person authenticating the submission on behalf of the facility
Role of the person authenticating the submission on behalf of the facility in its organization
Authentication timestamp
Additional authentication string
Facility reception attachment ID
Facility reception attachment type
Facility reception attachment file name
Facility reception attachment contains personal data
Facility completion certificate
Certificate ID
Operator ID
Contact person name
Phone number
Email address
Facility type
Interim facility
Certificate Date
Quantity prepared for re-use or recycled mass (tonnes/Mg)
Quantity prepared for re-use or recycled volume (m 3 )
Quantity recovered in other manner mass (tonnes/Mg)
Quantity recovered in other manner volume (m 3 )
Waste identification (list)
Waste identification (code)
Designation and composition of the waste received
Name of the person authenticating the submission on behalf of the facility
Email of the person authenticating the submission on behalf of the facility
Role of the person authenticating the submission on behalf of the facility in its organization
Authentication timestamp
Additional authentication string
Facility completion attachment ID
Facility completion attachment type
Facility completion attachment file name
Facility completion attachment contains personal data
Take-back request(s)
Request ID
Quantity for take-back mass (tonnes/Mg)
Quantity for take-back volume (m 3 )
Reasons for requesting take-back
Date of take-back request
Attachment ID
Attachment type
Attachment file name
Attachment contains personal data
Cancelation
Action ID
Timestamp of the operation
Cancelation reasons or details
Attachment ID
Attachment type
Attachment file name
Attachment contains personal data
CA code who performed the action
Operator ID who performed the action
9. GET ALL INFORMATION ON PRE-CONSENTED FACILITIES
This operation allows to retrieve information on pre-consented facilities. If none of input parameters is provided the entire list will be retrieved.
Input parameters:
Section
Field
Mandatory
Other constraints
Pre-Consent
Main identification number (name)
N
Main identification number (value)
N
Operator ID
N
Validated
Waste treatment operation code
N
Validated
Waste code
N
Validated
Start date
N
Date format
End date
N
Date format
Code of the CA who pre-consented the facility
N
Output parameters:
Section
Field
General
Call status code
Pre-consented facility
Main identification number (name)
Main identification number (value)
Facility name
Operator ID
Country code
Postal code
City name
Address details
Latitude
Longitude
Pre-Consent
Entry ID
Waste treatment operation code
Waste code
Pre-consented quantity of waste mass (in tonnes/Mg)
Pre-consented quantity of waste volume (in m 3 )
Start date
End date
Code of the CA who issued a pre-consent for the facility
Attachment ID
Attachment type
Attachment file name
Attachment contains personal data
Errors and warnings
Warning message
Error message
10. GET ACTION DETAILS BY ACTION ID
This operation allows to retrieve the details of an action searched based on its ID.
Input parameters:
Section
Field
Mandatory
Other constraints
General
Action ID
Y
Output parameters:
Section
Parameter
General
Call status code
Specific
Action ID
Action timestamp
Action type
Action details (operation details / document)
Operator ID / CA code who performed the action
Errors and warnings
Warning message
Error message
11. GET OPERATOR DETAILS
This operation allows to retrieve the details of an operator based on its Operator ID.
Input parameters:
Section
Field
Mandatory
Other constraints
General
Operator ID
N
Output parameters:
Section
Parameter
General
Call status code
Specific
Main identification number (name)
Main identification number (value)
Operator ID
Linked operator’s ID
CA responsible for operator’s registration
Registration number (name)
Registration number (value)
Other identifier type
Other identifier value
Operator name
Country code
Postal code
City name
Address details
Latitude
Longitude
Contact name
Phone number
Email address
Fax number
Website URL
Business chapter
Business section
Role in the system
Errors and warnings
Warning message
Error message
12. GET INFORMATION ON CONFIDENTIALITY OF THE WASTE RECEIVING FACILITY NAME
This operation allows to retrieve the details of whether confidentiality of the waste receiving facility name or not.
Input parameters:
Section
Field
Mandatory
Other constraints
General
Notification No
Y
Operator ID
N
Name of the waste receiving facility is confidential and shall not be publicly disclosed
N
Output parameters:
Section
Parameter
General
Call status code
Specific
Notification No
Operator ID
Name of the waste receiving facility is confidential and shall not be publicly disclosed
Explanation why the name of waste receiving facility is confidential under Union or national law
Errors and warnings
Warning message
Error message
13. GET ALL OPERATORS
This operation allows to retrieve the list of operator IDs that meet the provided input parameters.
Input parameters:
Section
Field
Mandatory
Other constraints
General
Other identifier type
N
Other identifier value
N
Main identification number (name)
N
Main identification number (value)
N
Operator name
N
Country code
N
CA responsible for operator’s registration
N
Linked operator’s ID
N
Output parameters:
Section
Parameter
General
Call status code
Specific
Operator ID(s) (list)
Errors and warnings
Warning message
Error message
PART G
PROTOCOL FOR EXCHANGE OF DATA RELATED TO OPERATIONS CONCERNING USER MANAGEMENT, REFERRED TO IN ARTICLE 11(4) OF THIS REGULATION
1. GET AUTHORISATION REQUESTS
This operation is used by CAs to retrieve the pending requests of users that asked for authorisation to represent an operator in the central system.
Input parameters: no input parameters are needed. The CA performing this operation will retrieve all the requests of users that that asked for authorisation to represent an operator, for which the CA is selected as the registering CA.
Output parameters:
Section
Parameter
General
Call status code
Specific
Request ID
User’s email
User’s EU Login
Operator ID
Errors and warnings
Warning message
Error message
2. APPROVE AUTHORISATION REQUESTS
This operation is used by CAs to approve the pending requests of users that asked for authorisation to represent an operator in the central system.
Input parameters:
Section
Field
Mandatory
Other constraints
General
Request ID
Y
Validated
Action code
Y
Validated
Output parameters:
Section
Parameter
General
Call status code
Specific
User’s email
User’s EU Login
Operator ID
Request ID
Errors and warnings
Warning message
Error message
OPERATIONS TO BE PERFORMED BY THE SYSTEMS, REFERRED TO IN ARTICLE 11
ANNEX IIISupplementary provisions
ANNEX III
OPERATIONS TO BE PERFORMED BY THE SYSTEMS, REFERRED TO IN ARTICLE 11
1.
For the purposes of the Annex, the following abbreviations shall apply:
(a)
‘CA’ means a competent authority;
(b)
‘PWAS’ means a person who arranges the shipment;
(c)
‘PIC’ means the procedure of prior written notification, as referred to in Article 5 of Regulation (EU) 2024/1157;
(d)
‘Annex VII’ means Annex VII to the Regulation (EU) 2024/1157, that is used for shipments of waste subject to the general information requirements referred to in Article 18 of that Regulation;
(e)
‘Facility’ means a facility receiving waste or a consignee.
2.
Fields marked with ‘*’ indicate that users acting in a given role shall be able to perform this operation when they are acting on behalf of operator or competent authority of a third country that is not connected to the central system.
No.
Name of the operation (as used in Annex II)
Waste shipment procedure
Role of the user(s) performing operation
Comments
1.
Submit new notification
PIC
Notifier
CA*
2.
Submit request for information
PIC
CA
3.
Update request for information
PIC
CA
4.
Submit reply to request for information
PIC
Notifier
CA*
5.
Submit acknowledgement
PIC
CA
6.
Decline the ‘pre-consented facility’ status of waste receiving facility for the notification concerned
PIC
CA
7.
Disregard timelines (Article 14(16) of Regulation (EU) 2024/1157)
PIC
CA
8.
Submit decision
PIC
CA
9.
Update information on confidentiality of waste receiving facility name
PIC
CA
10.
Update notification
PIC
Notifier
CA*
11.
Update decision
PIC
CA
12.
Submit request for change after consent (Article 17 of Regulation (EU) 2024/1157)
PIC
Notifier
CA*
13.
Submit reply to request for change after consent (Article 17 of Regulation (EU) 2024/1157)
PIC
CA
14.
Properly carried out
PIC
CA dispatch
CA transit*
CA destination*
15.
Properly completed
PIC
CA dispatch*
CA transit
CA destination
16.
Notification invalid
PIC
CA
17.
Notification revalidated
PIC
CA
18.
Cancel notification
PIC
Notifier
CA*
19.
Notification completed
PIC
Notifier
CA*
20.
Submit movement document
PIC
Notifier
CA dispatch
CA transit*
CA destination*
21.
Update movement document
PIC
Notifier
CA dispatch
CA transit*
CA destination*
22.
Submit carrier transfer confirmation
PIC
Carrier
Notifier*
CA*
23.
Update carrier transfer confirmation
PIC
Carrier
Notifier*
CA*
24.
Submit consignee reception confirmation
PIC
Notifier
Facility
CA*
25.
Update consignee reception confirmation
PIC
Notifier
Facility
CA*
26.
Submit facility reception confirmation
PIC
Notifier
Facility
CA*
27.
Update facility reception confirmation
PIC
Notifier
Facility
CA*
28.
Submit facility completion certificate
PIC
Notifier
Facility
CA*
29.
Update facility completion certificate
PIC
Notifier
Facility
CA*
30.
Submit take-back request
PIC
CA
31.
Update take-back request
PIC
CA
32.
Cancel movement document
PIC
Notifier
CA*
33.
Submit facility completion certificate under Article 15(5) of Regulation (EU) 2024/1157
PIC
Facility
CA*
34.
Update facility completion certificate under Article 15(5) of Regulation (EU) 2024/1157
PIC
Facility
CA*
35.
Submit Annex VII document
Annex VII
PWAS
CA*
Facility*
36.
Update Annex VII document
Annex VII
PWAS
CA*
Facility*
37.
Submit carrier transfer confirmation – Annex VII document
Annex VII
Carrier
PWAS
CA*
Facility*
38.
Update carrier transfer confirmation – Annex VII document
Annex VII
Carrier
PWAS
CA*
Facility*
39.
Submit consignee reception confirmation – Annex VII document
Annex VII
PWAS
Facility
CA*
40.
Update consignee reception confirmation – Annex VII document
Annex VII
PWAS
Facility
CA*
41.
Submit facility reception confirmation – Annex VII document
Annex VII
PWAS
Facility
CA*
42.
Update facility reception confirmation – Annex VII document
Annex VII
PWAS
Facility
CA*
43.
Submit facility completion certificate – Annex VII document
Annex VII
PWAS
Facility
CA*
44.
Update facility completion certificate – Annex VII document
Annex VII
PWAS
Facility
CA*
45.
Submit take-back request – Annex VII document
Annex VII
CA
46.
Update take-back request – Annex VII document
Annex VII
CA
47.
Cancel Annex VII document
Annex VII
PWAS
CA*
Facility*
48.
Submit information on new pre-consented facility
CA
for pre-consented facilities
49.
Update information on the pre-consented facility
CA
for pre-consented facilities
50.
Upload attachment
PIC
Annex VII
Notifier
CA
Waste producer
Facility
PWAS
Carrier
for pre-consented facilities
51.
Create operator
PIC
Annex VII
Notifier
CA
Waste producer
Facility
PWAS
for pre-consented facilities
52.
Update operator
PIC
Annex VII
Notifier
CA
Waste producer
Facility
PWAS
for pre-consented facilities
53.
Get all actions
PIC
Annex VII
CA
Notifier
Waste producer
Facility
PWAS
Carrier
54.
Get all notifications
PIC
CA
Notifier
Waste producer
Facility
Carrier
55.
Get notification by ID
PIC
CA
Notifier
Waste producer
Facility
Carrier
56.
Get all movement documents by notification No
PIC
CA
Notifier
Waste producer
Facility
Carrier
57.
Get movement document by ID
PIC
CA
Notifier
Waste producer
Facility
Carrier
58.
Get attachment details by ID
PIC
Annex VII
CA
Notifier
Waste producer
Facility
PWAS
Carrier
59.
Get all Annex VII documents
Annex VII
CA
PWAS
Waste producer
Facility
Carrier
60.
Get Annex VII document by ID
Annex VII
CA
PWAS
Waste producer
Facility
Carrier
61.
Get all information on pre-consented facilities
CA
Notifier
Facility
for pre-consented facilities
62.
Get action details by action ID
PIC
Annex VII
CA
Notifier
PWAS
Waste producer
Facility
Carrier
63.
Get operator details
PIC
Annex VII
Notifier
CA
Waste producer
Facility
PWAS
64.
Get information on confidentiality of the waste receiving facility name
PIC
CA
65.
Get all operators
PIC
Annex VII
Notifier
CA
Waste producer
Facility
PWAS
66.
Get authorisation requests
PIC
Annex VII
CA
67.
Approve authorisation requests
PIC
Annex VII
CA
Source: EUR-Lex (Publications Office of the EU), © European Union, reuse permitted under Commission Decision 2011/833/EU.
