Updating or Withdrawing a Due Diligence Statement

The standard window is subject to important lockouts

The Information System rules provide for amendment or withdrawal of an ordinary due diligence statement within 72 hours after its reference number becomes available. This is not an unconditional right to change the record for three days. Article 5 contains lockouts that can prevent amendment or withdrawal earlier, including the relevant market or export event, customs presentation, an authority check and use of the statement in the prescribed grouping mechanism.

Check the amended rules before acting. The July 2026 revision replaced the former broad reference-based lockout with one tied to grouping by the same Information System user under Article 8a. It also revised the transaction wording to refer to a product covered by the statement having been placed on the Union market or exported. Older instructions may therefore describe restrictions using outdated actor or transaction language.

Identify which event has already happened

Before editing, establish when the reference became available and what has happened since. Has a relevant product covered by the statement already been placed on the market or exported? Has the reference been provided or made available to customs before release for free circulation or export? Has the user been notified of an intended check, and is that check ongoing? Has the statement been referenced for grouping under Article 8a?

These facts can be held by different teams. The compliance officer may know the submission time, while the customs representative knows when the reference was presented. A warehouse release record may establish another relevant event. Bring those facts together before assuming that an enabled edit control, a still-open internal task or a remaining portion of the 72-hour period makes the change permissible.

The Information System framework explains why submitted records sit within a wider transaction process. Internal status labels should reflect that relationship rather than treating regulatory submissions as freely editable purchase-order notes.

Reasoned requests after the ordinary period

Article 5(4) permits competent authorities, on an individual reasoned request, to extend the amendment or withdrawal period after the standard period has expired. The extension must not exceed eight calendar days, and the request must be based on reasons beyond the user's control. The user must state that the Article 5(3) circumstances do not apply. The other legal restrictions remain relevant.

This is an authority decision, not an automatic additional eight days for every statement. Explain the circumstances and retain the request, supporting facts and response. Do not train staff to backdate an edit or create a duplicate record whenever the ordinary period has elapsed. If the legal route is unavailable, seek the appropriate authority guidance and address the underlying compliance consequences instead of assuming the database can be corrected informally.

What an amendment changes

An amended statement is subject to risk profiling of the whole amended statement under Article 5(5). Even a correction that appears narrow to the business can therefore affect the processing of the full record. Preserve the previous content, the reason for the change, the person who approved it and the resulting system outcome so the history remains understandable.

A corrected origin file is a useful example. Replacing an incorrectly identified plantation can change the evidence underlying the declaration, rather than simply correcting a spelling error. The operator must review whether the new origins support the required conclusion. The system's ability to receive a change does not establish that the replacement data has been assessed or that already affected products were compliant.

Withdrawal does not erase the underlying transaction

Withdrawing a statement should not be treated as a way to undo the legal history of goods already placed or exported. The lockouts exist partly because other processes may already rely on the record. If a problem indicates potential non-compliance in products previously placed, separate the question of system correction from the operator's notification, cooperation and corrective responsibilities under the EUDR.

Keep an incident record identifying the affected products, customers, customs records and current stock. A business may need to stop further use of an inaccurate record even where it cannot amend or withdraw it itself. Staff should have an escalation route that reaches both legal compliance and logistics, so a correction request does not sit unanswered while more goods are released against the same mistake.

Simplified declarations have their own rules

The amended implementing regulation treats simplified declarations separately in Article 4a. Updates retain the declaration identifier, are recorded and trigger risk profiling of the updated declaration. Withdrawal is prevented after the simplified declaration has been used as a reference by the same user under Article 8a. The September 2026 manual describes deployed version tracking: the identifier is retained while versions are distinguished, and only the current version is available for use. Do not automatically apply the ordinary statement's 72-hour rule to every simplified declaration action.

The evidence checklist helps retain the action history across both record types. Before approving a change, identify the legal record, establish its current status, review the changed facts and document the route used. That sequence is more reliable than asking only whether the account currently shows a button labelled amend or withdraw.

Log unsuccessful amendment attempts as well as completed ones. They can explain why a known error remained visible in a record while the business sought the appropriate authority response. Keep that log connected to the affected products, rather than treating it as an isolated helpdesk ticket with no compliance owner.