Why Manual EUDR DDS Filing Fails at Scale

Manual EUDR filing can work when submission volumes are low. The trouble starts when teams are processing hundreds or thousands of Due Diligence Statements, correcting errors under time pressure, and trying to keep customs and internal records aligned.

Three features of the EU Deforestation Regulation's Information System make that difficult:

• A submitted Due Diligence Statement can usually be amended or withdrawn for only 72 hours, and that window may close sooner.
• The Information System stores no reusable master data for fields such as HS codes or scientific names.
• Bulk submission requires a SOAP API integration that must pass Commission conformance testing before it can connect to production.

None of these constraints makes manual filing impossible. Together, however, they make it increasingly fragile as submission volume and operational complexity grow.

This article explains where that fragility comes from, using the regulation, its implementing acts, and the European Commission's own guidance.

Why the 72-hour correction window matters

Article 5(1) of Commission Implementing Regulation (EU) 2024/3084 states that the Information System enables users to amend or withdraw a Due Diligence Statement within 72 hours after the reference number was made available.

That is the standard correction window. Article 5(3) closes it earlier once any of these events occurs:

• you are notified of an intention to carry out a check on the DDS or the product, for the period of the check;
• the relevant product is placed on the Union market or exported;
• the reference number is provided or made available to customs authorities before release for free circulation or export.

Article 5(2), as amended by Implementing Regulation (EU) 2026/1565, adds a fourth: a DDS can no longer be amended or withdrawn once the same user has referenced it in a grouped statement.

Article 5(4) provides a limited exception. A competent authority may extend the period by no more than 8 calendar days, but only after the initial 72 hours have expired, following an individual and reasoned request, and for circumstances beyond the user's control. The request must also confirm that none of the Article 5(3) blockers applies.

For operations teams, the practical implication is straightforward: errors must be found in less than 72 hours and, in many cases, before the reference number reaches customs. A process that finds mistakes during a month-end review will often find them too late to use the normal amendment route.

Reusable product data still needs an owner

Duplicating a statement saves retyping. It does not maintain a checked product master for the next shipment.

Commission FAQ v5, section 7.4, is explicit: the Information System does not store frequently used data such as HS codes or scientific names for autofill. What it offers instead is the ability to duplicate a previously drafted or submitted statement, plus an import button for production place information from a predefined GeoJSON file. The Commission adds that it remains the operator's responsibility to make the necessary changes in any duplicated statement.

Duplicate-and-edit can save time, but it can also carry an old value into a new consignment. A scientific name may be valid in form while being wrong for the current shipment, and the error may not be noticed until the amendment window has closed.

Teams that need reusable master data with validation attached must therefore maintain it outside the Information System.

The size limits are real and they are reachable

FAQ v5, section 7.12, sets out what one DDS can hold:

Section 7.16 adds a 25 MB file limit, which the Commission notes allows for more than one million geolocation points or polygon vertexes in total. Where a file exceeds it, the recommended fixes are cartographic: points instead of polygons for areas under 4 hectares and for cattle supply chains, and reduced vertex resolution that still represents the area legitimately.

At higher volumes, these geometry decisions are safer to validate systematically than during manual filing.

Geolocation has a defined shape

Article 2(28) EUDR requires at least six decimal digits for latitude and longitude. Per FAQ v5, section 7.17, the system validates digit count and, where fewer than six are supplied, fills the remaining digits with zeroes rather than rejecting the file.

In practice, an under-precise coordinate may be accepted and padded rather than rejected. An internal validation step is needed if the original precision matters to the submission.

Section 7.26 confirms GeoJSON is the only accepted format for uploading geolocation data in a file, because it is the only non-proprietary standard supporting the required extra properties with an enforced coordinate system. Exclusive use was announced in April 2024.

What API integration changes operationally

The native EUDR TRACES API uses SOAP rather than REST. Connecting to it requires authenticated requests, conformance testing, and a way to reconcile uncertain submission outcomes. Moving data out of spreadsheets does not remove those responsibilities.

For the operations team, the important questions are who owns a failed submission, how its final status is confirmed, and whether an amendment is still permitted. The integration must preserve that evidence instead of treating every failure as a reason to retry.

Acceptance submissions have no legal value. Testing an integration there is distinct from operating it in production.

Grouping: what changed in July 2026

Guidance written before mid-2026 may not cover one of the provisions most relevant to high-volume filing.

Implementing Regulation (EU) 2026/1565 of 13 July 2026 amends 2024/3084 as regards the submission of due diligence statements, simplified declarations for micro or small primary operators, contingency arrangements, and other measures simplifying use of the Information System. Its new Article 8a introduces grouping.

Users may group individual Due Diligence Statements or Simplified Declarations by submitting a new statement that references previously submitted ones via their reference numbers or declaration identifiers. The Information System then assigns a specific status to the individual statements marking them as grouped and replaced. The grouped statement represents them for compliance purposes, and for Articles 4(7) and 26(4) EUDR you communicate the grouped reference number rather than the individual ones.

Recital 7 explains that grouping was introduced to address technical limitations on statement file sizes and to avoid disruptions to customs procedures.

Grouping can make large submissions more manageable, but it also creates another lifecycle to track. An individual reference number changes status when it is absorbed into a group, Article 5(2) affects whether it can later be amended, and the grouped reference number must reach customs. Teams therefore need a reliable record of both the individual statements and the group that replaced them.

Two system states users cannot fully control

Your risk status is hidden. Under the amended rules, each submitted statement is subjected to automated electronic risk profiling and assigned a risk status which is not disclosed to the Information System user. Competent authorities may review a statement at any stage after submission, including after grouping, and assign a new status that takes precedence.

Because users cannot see the assigned risk status, the part they can control is the quality and defensibility of the submission. That makes an internal evidence record important rather than relying on the portal as the sole record.

A rejection reclassifies your product immediately. Where a DDS or Simplified Declaration is rejected, the relevant product is deemed not covered by a statement as required by Article 3(c) EUDR from the moment of rejection, and the rejection is reflected by a specific status in the system.

Questions people actually ask

Is there an EUDR API, and where is the documentation?

Yes. The Commission's Information System guide links the API documentation and access requirements. The native interface uses SOAP, WSDL and XSD. Follow the current conformance process before requesting production API access.

How often do I have to submit a DDS?

For an upstream operator using a DDS, submit before placing the covered goods on the market or exporting them. A DDS can cover multiple batches or shipments within its covered quantity; it is not automatically one statement per shipment. Eligible primary operators have a separate simplified-declaration regime, and downstream operators and traders do not file their own DDS.

Can I fix a mistake after submitting?

Normally within 72 hours of reference-number availability, subject to the earlier blockers described above. An authority may grant the limited extension after expiry; it does not override placement, export, customs, check or grouping restrictions.

Do I need a separate DDS for each export destination?

No. Per FAQ v5, section 7.20, the destination country is not entered when submitting for export, so multiple destinations do not require separate statements.

Does the reference number have to appear on my shipping documents?

Not on every shipping document. Article 26(4) requires the applicable reference or identifier to be available to customs before release for free circulation or export, subject to its electronic-interface and downstream-export exceptions. That is different from requiring it on every transport document.

Do I need separate accounts for different roles?

No. Per FAQ v5, section 7.29, a single economic operator account can carry multiple roles: operator, non-SME downstream operator, non-SME trader, and authorised representative.

Can I check whether a reference number is valid?

Yes. FAQ v5, section 7.25, describes a dedicated feature that checks DDS reference numbers, simplified declaration identifiers, and related verification numbers, and which also accepts CSV files for bulk checking.

Should I keep my own records if the system stores everything?

Yes. FAQ v5, section 7.14, notes that storage in the Information System is time-limited by the implementing regulation, and that users have the option to export a DDS to PDF and extract geolocation coordinates to a separate file for their own record-keeping. The system is a submission channel, not your archive.

Where manual work actually breaks

Manual filing usually breaks down gradually, through a series of operational problems.

First, the correction loop exceeds the window. Errors surface at review rather than at entry. The normal amendment route may already be closed. Escalation is then necessary, but an extension request cannot undo an earlier customs or placement blocker.

Second, duplicate-and-edit drift compounds. Because the system holds no master data, every statement inherits from the last one someone copied. Errors propagate rather than repeat.

Third, reconciliation grows faster than volume. Once statements can be individually submitted, grouped, replaced, rejected, risk-profiled, or referenced at customs, the number of states exceeds what a spreadsheet column can express. Teams start spending more time locating status than moving submissions.

Fourth, integration becomes difficult to avoid. Above a certain volume, the API is likely to become the practical submission channel. It requires schema-valid payloads, credential management, conformance-tested error handling, and amendment and retraction paths. At that point, the organisation is effectively operating integration infrastructure, whether or not it was designed as such from the start.

What deterministic engineering changes

In EUDR work specifically, this means:

• structured intake with validation at entry, not at review, so errors surface inside the 72-hour window;
• your own master data for HS codes, scientific names, and production places, since the Information System holds none;
• deterministic geometry handling against the 25 MB and per-statement limits before submission, not after rejection;
• explicit lifecycle state per reference number, including grouped, replaced, and rejected;
• submission evidence and response logs with credentials redacted, restricted access and a defined retention policy;
• exception queues with named owners, because the deadline for a correction is measured in hours.

The useful measure of automation here is whether it helps the team detect and correct errors within the available window.

Case study: engineering an EUDR submission system

We built an EUDR submission bridge for Baldwin Global Consulting. The documented testing relates to the 2025 acceptance environment, not measured production throughput or current-version conformance.

The engineered backend included:

• an internal JSON-based API wrapping the Commission's SOAP interface, so product teams never hand-build envelopes;
• deterministic schema and geo-data validation ahead of submission;
• automated SOAP envelope construction against the published WSDL and XSD files;
• an explicit error taxonomy mapped to the CF2 through CF7 conformance scenarios: submission, reference retrieval, error handling, amendment, retraction, and cross-operator retrieval;
• controlled retry logic for transient failures;
• submission state and history per reference number;
• amendment and retraction endpoints built against the 72-hour constraint;
• full request and response logging;
• explicit operator context for submission handling, with the authenticated role and any representative mandate checked separately.

The design reduces repeated data entry and makes submission state and failures inspectable. These are implementation capabilities, not a quantified production-results claim.

The EUDR Compliance Bridge case study describes the implementation and its testing boundaries.

When manual filing is still the right answer

Manual filing remains a reasonable choice when submission volume is low, consignment patterns are stable, and someone can reliably check a statement on the day it is filed. Many operators may never need more than the Commission's web interface.

The threshold is not a volume number. It is this question: can you detect and correct an error within the available amendment window, including the week your specialist is on leave? A process that depends on one person deserves attention before volumes grow.

Evaluating your readiness

• expected monthly submission volume and burst variability;
• time from reference availability to the earliest amendment blocker, including customs handoff;
• who validates a statement, and how quickly;
• whether master data lives anywhere other than previous statements;
• integration surface with ERP or internal systems;
• how a rejected submission is traced and corrected, and by whom;
• whether you hold exportable evidence independent of the Information System.

If those questions are difficult to answer, it is worth testing the workflow before a live deadline exposes the gaps.

Dates and where this sits

The current EUDR application dates are 30 December 2026 for large and medium operators, downstream operators and traders, and for micro and small operators handling products already covered by the EU Timber Regulation. Most other qualifying micro and small operators have until 30 June 2027. Regardless of date, production and acceptance require separate TRACES NT registration and roles.

At scale, this becomes a RegOps operating-model problem: ownership, exceptions, evidence, and state must remain coherent across the process. The native EUDR API integration handles the submission edge, while controlled compliance workflow automation defines the guardrails around it.

If EUDR is material to your operations and volume will not stay small, treat it as integration and state management now. You can also get in touch.

Sources

The regulatory and portal guidance comes from the sources below. The workflow recommendations are our engineering assessment; the case example describes historical project work.

• Regulation (EU) 2023/1115: the EU Deforestation Regulation itself
• Commission Implementing Regulation (EU) 2024/3084: functioning of the Information System, including Article 5 on amendment and withdrawal
• Commission Implementing Regulation (EU) 2026/1565: 13 July 2026 amendment introducing Article 8a grouping, Article 4a simplified declarations, and contingency arrangements
• Regulation (EU) 2025/2650: current application dates
• EUDR implementation FAQ, 5th iteration: European Commission, sections 7.4, 7.12, 7.14, 7.16, 7.17, 7.20, 7.21, 7.25, 7.26, 7.29
• The Information System of the Deforestation Regulation: European Commission
• Deforestation due diligence registry: European Commission guidance on bulk API submission and CIRCABC documentation
• EUDR roles and responsibilities: European Commission

Reviewed against these sources on 16 August 2026. EUDR has been amended more than once; confirm the current position against the primary sources before acting. This is operational guidance, not legal advice.