Filed under EUDR Information System and Due Diligence Statements Explained
Plot record: legal status and review details
- Jurisdiction
- European Union
- Status
- Current amended law, with the substantive application dates distinguished from system operation.
- Application
- General application: 30 December 2026; most qualifying micro and small operators: 30 June 2027, subject to Article 38 exceptions and product-specific dates.
- Relevant provisions
- Implementing Regulation 2024/3084, as amended, Articles 3(f), 7 and 10(3)
Review this page when:
- Amendment of the EUDR or Information System implementing rules
- Commission system release, user manual or API specification change
- Applicable obligation dates pass
A security number attached to a submission
An EUDR verification number is a security number that the Information System assigns to a due diligence statement or simplified declaration. It provides additional security for the information in that record. It is not the statement's reference number, the simplified declaration's declaration identifier or an independent finding that the goods comply with the regulation. The amended implementing rules expressly recognise verification numbers for both types of submission.
Keep the distinction visible in your records. For an ordinary statement, store its reference number in one labelled field and its associated verification number in another. For a simplified declaration, use the declaration identifier with its own associated verification number. A spreadsheet column called simply “EUDR number” invites staff to send or use the wrong value.
What access it supports
Article 10(3) of the amended implementing rules connects a user's access to information submitted by another user with the relevant reference or declaration identifier and associated verification number. The September 2026 guide distinguishes checking a record's validity from consulting its contents. Non-SME downstream operators and traders can consult the contents in the substantiated-concern circumstances described there; visibility of geolocations follows the upstream submitter's choice. Possession of numbers should not be described as unrestricted access to every document the supplier holds outside the platform.
The security implication is still important. Information about production locations or commercial product flows can be sensitive. A user should not publish the verification number in an open product description or assume that a field intended for a customer can safely be indexed by search engines. Manage access according to the legitimate transaction and the official system's current access model.
The difference from the reference number
A reference number identifies an ordinary due diligence statement. A declaration identifier identifies the simplified declaration used by a qualifying micro or small primary operator. The verification number is associated with the record for the additional security purpose. These functions are complementary, but their legal labels should not be collapsed into a single generic code.
For example, a warehouse may need the statement reference associated with a consignment for its allocation record. The person reviewing system information may require the related security information and appropriate access. Giving every warehouse employee the verification number just because they need to identify a consignment is not automatically the best access design. Determine what each task requires before distributing sensitive values broadly.
The reference number explanation covers the identifier's product and transaction role. Separating those tasks makes it easier to design delivery notes, customer portals and internal screens without exposing more information than the workflow needs.
Receiving and storing the number
Obtain submission information through a reliable channel linked to the supplier and affected products. If a number arrives in an unexpected email or an unrecognised file, establish who supplied it and what record it is intended to accompany. A plausible-looking code does not show that it belongs to the goods purchased, and a copied number can create misleading confidence.
Store the relationship between the main identifier, verification number, submitting entity, environment and source of the information. Restrict access to the people and services that need it, and remove access when responsibilities change. Where a service provider manages the record, the contract and handover process should allow the operator to retain control of its own compliance information.
Do downstream duties require publication?
Article 4(7) requires the operator to communicate the relevant reference numbers or declaration identifiers to the downstream businesses it supplies. Article 5 contains the downstream information requirements. The September 2026 official user guide expressly states that sharing verification numbers downstream is not obligatory. Do not rewrite the identifier communication duties as an obligation to distribute security values throughout the supply chain.
A buyer can ask for information needed for its specific review, but a contractual request and a statutory obligation are different things. Explain what access is needed and why. Where a dispute concerns whether geolocation or commercial information must be shared, assess the legal duties and supported system options rather than relying on a blanket claim that every customer needs unrestricted access.
Operational safeguards and mistakes
Use separate acceptance and production records. A verification number associated with a training submission is not evidence for a live transaction. Avoid logging security values in unrestricted technical error reports, public support threads or analytics. If a number is sent to the wrong recipient, record the incident and review the access implications using the current system guidance; do not invent an unsupported procedure for rotating or revoking it.
The Information System overview explains how these identifiers fit into registration, submission and authority checks. A useful internal check is to ask a new staff member to identify which value goes to the transaction record and which controls information access. If the distinction is unclear, improve the labels and instructions before a real consignment depends on them.
Customer portals should reflect the same distinction. A page listing transaction references can use a different permission level from a page providing access-related verification information. Review exports and downloadable reports as well as the visible screen, since a hidden spreadsheet column can disclose a value that the interface correctly restricts. The goal is a deliberate access design that follows the purpose of the information being shared.
Primary sources on the record
Implementing Regulation 2024/3084, as amended, Articles 3(f), 7 and 10(3). This entry was checked against the consolidated text dated 18 September 2026. Consolidated texts are documentation tools; the authentic acts are those published in the Official Journal.
- EUDR consolidated text, 18 September 2026
- Information System implementing rules: Regulation (EU) 2024/3084
- Information System amendment: Regulation (EU) 2026/1565
- Commission User Guide for Economic Operators, version 3.0 (16 September 2026)
Check the current sources and the guidance of the relevant competent authority for your situation. This page is not legal advice or a compliance determination.