Due Diligence Statement (DDS) References are a key part of the EUDR legislation. DDS References are provided by the EU Traces NT system as proof of submission of a DDS Statement and are used by customs at the border to validate Due Diligence has been carried out and also by organisations to reference within their own DDS.
The Traces NT team have been releasing new/updated functionality so we are currently updating integration.
The APIs currently in the documentation are target APIs once the updated work has been completed. You should be able to plan your integration work but be aware that there is currently variable availability of these specific APIs and that they are still subject to change.
A DDS Reference consists of two parts:
The Reference Number must be included on documentation for customs and provided to Customers.
The Validation Number will also need to be provided to Customers to allow them to verify the status and reference DDSs in their own DDS.
You will either receive DDS References from your suppliers or you will generate your own DDS Statements and receive a Reference Number on successful submission to Traces NT.
The following API call can be used to create a DDS Reference number.
DDSReference Schema
An internal reference number that can be user defined to help identify the DDS Reference. If this is the only identifier provided then it is a mandatory field.
The Reference Number as provided by TracesNT.
The Verification Number provided by Traces NT. It is required if you want to reference the related DDS Statement in another DDS Statement.
This is the url of the organisation or connection from which the credentials will be used for submission or retrieval of DDS Statements with Traces NT.
You cannot mix record types that are provided in the relatedRecords. They will either need to be one or more Deliver(ies) or one or more Purchase Orders.
Provide:
- internalReferenceNumber
- relatedRecords
Provide:
- internalReferenceNumber
- referenceNumber
- verificationCode
- relatedRecords
You can update the relatedRecords by using the Patch endpoint:
Once a DDS Reference has been created (you follow the above step) and you have provided all the records that you wish to generate the statement for, you can now ask the system to generate a DDS Statement.
Whilst much of the statement is based off data contained in the relatedRecords, there is still some data that is required in order to build the statement.
Generate DDS Request
IF this is set to true then downstream consumers of your DDS Reference will not have access to the Geo Location information.
If you make changes to the related Records then the DDS Statement will need to be regenerated.
In order to submit a DDS Statement to Traces NT call the following endpoint:
When Traces NT update the status of a DDS Reference number, that will be reflected in the DDSReference.Status field.
DDS Status
The DDS Reference number needs to be included in either documentation for customs and/or your customers. This means your internal system will need to be able to retrieve the DDS Reference(s) for a given record.
A record can have more than 1 DDS Reference related to it if it links back to more than 1 inbound delivery.
There are two context in which to find a DDS Reference. A record either has a DDS Reference directly attached to it (Delivery or PurchaseOrder) or it may have related DDS References (Delivery, Item), i.e. those found on related Deliveries or PurchaseOrders.
In order to find a Reference number for one or more records there is a specific API Call: