Does the reference number change when a DDS is amended?

No. The amendment keeps the reference and verification numbers. TRACES re-runs the risk analysis and the DDS returns to AVAILABLE with the same numbers.

How long do I have to withdraw a DDS?

72 hours from the moment it becomes AVAILABLE. It cannot be withdrawn if it is grouped in another DDS or if the competent authority is checking it.

What if the 72 hours have passed?

Ask the competent authority for an extension or submit a new DDS. Without an extension, TRACES rejects the amendment with EUDR_API_AMEND_DEADLINE_ELAPSED.

Can I amend a DDS that is still SUBMITTED?

No. According to the TRACES documentation, amending and withdrawing only work with the DDS in AVAILABLE. While it is being analysed, you have to wait.

What happens to a rejected DDS?

It stays REJECTED and does not block the shipment: you fix the data that failed and submit a new DDS, which gets its own number.

Amend or withdraw a DDS in TRACES: statuses and deadlines

A DDS submitted in TRACES stays SUBMITTED while the system analyses it and becomes AVAILABLE once it gets a reference number. From then on you have 72 hours to amend it, keeping the same number, or withdraw it; after that only with an extension from the competent authority, otherwise you submit a new DDS.

What statuses can a DDS have in TRACES?

When you submit a due diligence statement, TRACES returns an internal identifier (UUID) and sets it to SUBMITTED. The system then runs an automatic risk analysis. If all goes well, it assigns the reference and verification numbers and the DDS becomes AVAILABLE. In the Commission's test environment this takes from one to a few minutes; production may differ.

If the analysis profiles it as high risk, it waits for manual review by the competent authority (Art. 17), and TRACES shows the text “Under Competent Authority review”. These are the statuses of the current API version (V4):

DDS statuses in TRACES (API V4)
Status	What it means	What you can do
SUBMITTED	Received and being analysed. No reference number yet.	Wait for AVAILABLE.
AVAILABLE	Has reference and verification numbers. This is the one customs accepts.	Use it. Amend or withdraw within 72 h.
REJECTED	Failed TRACES validation.	Fix and submit a new DDS.
WITHDRAWN	Withdrawn by the operator within the window.	Nothing. Submit a new DDS if needed.
GROUPED	Referenced by another DDS in a grouped declaration.	No amending or withdrawing while grouped.
OBSOLETE	Superseded by another declaration.	Nothing.
ARCHIVED	Historical.	Nothing; keep it in your record.
CANCELLED	Legacy V1 value; the migration guide lists it as removed.	Should not appear.

V4 also defines SUSPENDED and UPDATED, but the official documentation says they are not active in this release.

The 72-hour window to amend or withdraw

According to the TRACES API documentation, a DDS can be amended or withdrawn for 72 hours, counted from the moment it becomes AVAILABLE. Both operations require the AVAILABLE status: while it is SUBMITTED you cannot touch it, and you cannot touch a rejected one either.

After 72 hours, amending is only possible if the operator's competent authority grants an extension, and that extension has to be requested. Without it, the documentation itself says what to do: submit a new DDS.

A DDS with GROUPED status cannot be withdrawn.
A DDS cannot be withdrawn while the competent authority is checking it.
The TRACES documentation does not deal separately with a DDS whose number is already in a customs declaration. If you have already used it for clearance, talk to your customs broker and the authority before withdrawing it.

What changes when you amend a DDS

Amending keeps the reference and verification numbers. We checked it in the test environment: after the amendment the DDS went back to AVAILABLE with the same numbers, and the DDS date did not change. So the number you already gave your customer or customs broker remains valid.

What does happen is that TRACES runs the risk analysis again: the DDS goes back to SUBMITTED and then to AVAILABLE. Two things cannot be changed:

The activity type (import, export or domestic trade within the EU).
Grouped declarations: they can only be set on the first submission. If the amendment includes them, TRACES answers EUDR-GROUPING-NOT-ALLOWED-ON-AMEND.

If you need to change one of those two things, or the window has closed, the way out is to withdraw (if you still can) and submit a new DDS with its own number.

Grouped statements: why sometimes nothing can be changed

Grouping is voluntary: when submitting a new DDS you can cite, by reference number, statements already submitted (up to 2,000). The new DDS gets its own number, inherits the geolocation of the statements it cites and represents all of them. The cited statements become GROUPED.

While that grouping is active, the cited statements cannot be amended or withdrawn individually. TRACES also refuses to group a statement that is already GROUPED: every cited statement must be AVAILABLE. If a source DDS needs correcting, do it before you cite it.

What the errors look like

For these operations the API returns two kinds of fault: BusinessRulesValidationException, when the data breaks a rule, and PermissionDeniedException, when the operation is not allowed. Inside there is a code in EUDR-UPPER-CASE format. Some you will see:

EUDR_API_AMEND_DEADLINE_ELAPSED: the amendment window has closed. It comes as a PermissionDeniedException.
EUDR-GROUPING-NOT-ALLOWED-ON-AMEND: you tried to add or change grouped declarations in an amendment.
EUDR-OPERATOR-EORI-FOR-ACTIVITY-MISSING: the operator has no EORI on its TRACES profile and the activity is import or export.

A rejected DDS is not fixed by amending it: you correct the data and submit another one. Before submitting, it is worth going over what makes a valid DDS.

How Sourevo handles it

Sourevo queries TRACES for submitted statements every 15 minutes until the reference number arrives, and for available and grouped ones once a day, in case they become grouped, archived, withdrawn or obsolete. Each DDS page shows the date and time until which it can be amended or withdrawn, counting 72 hours from the first AVAILABLE.

To change the plots of a DDS already submitted, the changes are staged and only reach the batch once TRACES accepts the amendment; if TRACES rejects it, the batch stays as it was. Every submission and every amendment stores a snapshot of the record, without deleting the previous one, so you can show an inspector what was declared at each point. If you submit on behalf of clients, the authorised representative guide explains how that role fits.

Frequently asked questions

Does the reference number change when a DDS is amended?: No. The amendment keeps the reference and verification numbers. TRACES re-runs the risk analysis and the DDS returns to AVAILABLE with the same numbers.
How long do I have to withdraw a DDS?: 72 hours from the moment it becomes AVAILABLE. It cannot be withdrawn if it is grouped in another DDS or if the competent authority is checking it.
What if the 72 hours have passed?: Ask the competent authority for an extension or submit a new DDS. Without an extension, TRACES rejects the amendment with EUDR_API_AMEND_DEADLINE_ELAPSED.
Can I amend a DDS that is still SUBMITTED?: No. According to the TRACES documentation, amending and withdrawing only work with the DDS in AVAILABLE. While it is being analysed, you have to wait.
What happens to a rejected DDS?: It stays REJECTED and does not block the shipment: you fix the data that failed and submit a new DDS, which gets its own number.