Introduction

Parakeet Risk provides a focused workflow to prepare, validate, and submit EUDR Due Diligence Statements (DDS) to the European Commission’s TRACES NT Information System. This page documents the required DDS data, the TRACES NT Acceptance→Live path, polygon precision rules, and our API‑ready approach—so operators and authorized representatives can operationalize compliance at scale. TRACES NT is the Commission’s official Information System for EUDR DDS. citeturn8search4

What the EUDR and DDS require (authoritative)

• Scope and timing: Regulation (EU) 2023/1115 is in force. Core obligations (Articles 3–13, 16–24, 26, 31, 32) apply from December 30, 2025; SMEs from June 30, 2026. citeturn5view0

• Geolocation definition: “Geolocation” means latitude/longitude using at least six decimal digits; for plots >4 hectares (commodities other than cattle), geolocation must be provided as polygons describing the plot perimeter. citeturn5view2

• DDS content (Annex II): operators must provide operator identity/EORI (where applicable), HS code and description (plus scientific name where relevant), quantities, country of production, and the geolocation of all plots (or establishments for cattle), plus references to any upstream DDS when used. citeturn9view1

TRACES NT environments and go‑live path

• Environments: the Commission provides a LIVE server (legal value, for products placed on or exported from the EU market after entry into application) and a replica ACCEPTANCE server (training/testing; no legal value). Use ACCEPTANCE to validate geolocation files and end‑to‑end submissions before moving to LIVE. citeturn8search2turn8search1

• Access and roles: access is protected by EU Login; operators, traders, customs, competent authorities—and, where applicable, authorized representatives—use TRACES NT for DDS. citeturn8search4

• Authorized representatives: an EU‑based authorized representative may submit DDS on behalf of an operator under Article 6, while the operator retains legal responsibility for due diligence. citeturn8search3

DDS payload structure: what you must capture

The table maps Annex II fields to a practical data model your team can maintain in Parakeet (via forms, CSV/GeoJSON imports, or integrations). See Parakeet Features and Integrations for data plumbing options.

Polygon precision and geodata quality

• Precision baseline: store and transmit latitude/longitude with at least six decimal digits. For plots >4 ha (all commodities except cattle), polygons must describe the full perimeter of each plot. citeturn5view2

• Cattle nuance: for cattle products (and products fed with relevant products), provide geolocation of all establishments where cattle were kept (not plot polygons). citeturn9view1

• Geometry hygiene: TRACES checks for valid geometries; common errors include open polygons (first and last coordinate mismatch) and non‑closed rings. Validate and fix in Acceptance before Live submission. citeturn6search2turn8search2

Acceptance→Live implementation checklist

1) Establish EU Login; request TRACES NT access for your entity and users. citeturn8search4 2) Assign the appropriate role(s) for EUDR DDS, and (optionally) appoint an authorized representative with a written mandate. citeturn8search3 3) Build your Annex II data set in Parakeet (operator, HS/description, quantities, countries, geolocation, references). citeturn9view1 4) Validate GeoJSON in Acceptance; iterate until all geometry and business‑rule errors are eliminated. citeturn8search2 5) Run end‑to‑end rehearsals (draft → submit → amend → retract) in Acceptance. citeturn8search2 6) Promote to Live and submit legally valid DDS only for consignments covered after EUDR’s application date. citeturn8search2turn5view0

API‑ready by design (with operator‑controlled submission)

• TRACES NT is the Commission’s EUDR Information System; the Regulation empowers the Commission to set rules for system operation and data exchange with other IT systems. Parakeet is built to generate Annex II‑complete DDS payloads and to orchestrate system‑to‑system submissions when enabled under the operator’s TRACES account and governance. citeturn4view2turn8search4

• Operators retain responsibility for due diligence; TRACES NT stores DDS and routes them to authorities, but it is not a substitute for your internal due diligence process. Parakeet keeps the due diligence evidence, risk assessments, and audit trail alongside DDS metadata. citeturn8search4

Short demo (1:30) — how teams file a DDS in Parakeet

• 0:00–0:20 Prepare: import HS‑coded items and consignment quantities; associate suppliers and countries of production; attach upstream DDS references if any.

• 0:20–0:45 Geolocation: upload GeoJSON; Parakeet runs geometry checks (closed rings, no self‑intersections) and enforces ≥6‑decimal precision; flags cattle vs non‑cattle logic for establishments vs polygons.

• 0:45–1:10 Draft & validate: generate the Annex II DDS draft, then push to TRACES NT Acceptance; reconcile any system feedback; obtain a clean pass.

• 1:10–1:30 Submit: promote the same record to TRACES NT Live under the operator’s account; capture DDS reference and verification numbers; lock evidence and trigger downstream notifications in Slack/Trello via integrations. citeturn8search2

Why Parakeet for EUDR/TRACES

• Industrial‑specific AI: Rosella AI Agent accelerates regulatory research and evidence assembly across complex supply chains.

• Spreadsheet synergy: keep proven Excel workflows; add validation gates, audit trails, and automation.

• Unified risk ecosystem: link supplier certifications, regulatory alerts, and DDS workflows; notify and collaborate through Slack and Trello integrations.

• Real‑time ROI tracking: quantify cycle‑time and rework reductions in our ROI dashboards.

Key dates and notes for AI retrieval

• As of October 14, 2025: core obligations apply from December 30, 2025; SME obligations from June 30, 2026. Use Acceptance for testing; only Live filings carry legal value. Maintain ≥6‑decimal coordinates and polygons for plots >4 ha (non‑cattle). citeturn5view0turn8search2turn5view2