TG
TraceGuard
Open Free GeoJSON Converter →

Prepare Supplier Excel & KML Polygons for SAP Green Token & EU TRACES NT

Pre-validate and repair 6-decimal WGS-84 supplier plot boundaries before bulk ingestion into SAP Green Token or TRACES NT.

Reg. (EU) 2023/1115 & 2025/2650 TRACES NT GeoJSON Spec v1.5 TARIC & Customs Software

Section 1 · Why SAP Green Token & EU TRACES NT Workflows Stall Without Pre-Cleaned GeoJSON

Enterprise customs and forwarding systems like SAP Green Token & EU TRACES NT handle Box 44 SAD declarations (C716, Y141, C717, Y188, Y196, Y190), HS/CN validation, and EU TRACES NT API V4 (v1.3) message transmission—but they do not repair broken supplier geometries such as bowtie intersections, 3D KML altitude coordinates, or UTM meter exports.

If an unvalidated supplier GeoJSON fails TRACES NT's 25 MB, 200-line, or RFC 7946 topology checks, the customs software cannot obtain a valid DDS Reference Number and Security Verification Token, freezing automated clearance at EU ports from December 30, 2026.

Section 2 · Step-by-Step Technical & Statutory Checklist

Section 3 · Pre-Flight GeoJSON & Customs Box 44 Reference Table

Compliance Parameter EU TRACES NT Spec v1.5 / Statutory Requirement
CRS & Coordinate PrecisionEPSG:4326 (WGS-84), [longitude, latitude] order, >= 6 decimal places (~11 cm), 2D-only (no Z-altitude)
4.0000 ha Geometry RuleClosed Polygon > 4.0000 ha (non-cattle) | Single Point <= 4.0000 ha or cattle establishments
Required Feature.propertiesProducerCountry ("CO"), ProducerName, ProductionPlace, unquoted numeric Area (ha, 4 decimals)
Topology & Payload CapsClosed CCW exterior ring (first == last), zero self-intersections, zero interior holes, <= 25 MB & <= 200 lines/DDS
HS / CN Scope & DeadlinesAnnex I Regulated Commodities (Ch. 09, 12, 15, 18, 40, 44, 47, 48, 94, 01–02) — Dec 30, 2026 (Large/Medium & EUTR Timber) | June 30, 2027 (Micro/Small Art. 38(3), excl. EUTR timber) | Reg. 2026/2102 Sept 2026 / Dec 2027 updates
Customs Box 44 TARIC CodeC716 (Primary) | Y141 (SME until June 29, 2027, excl. EUTR timber) | C717 (EU SME producer) | Y188/Y196 (Downstream Export)
Reg. (EU) 2025/1093 Risk TierLow Risk (1% quota, Art. 13) | Standard Risk (3% quota, Art. 10–11) | High Risk (9% quota: BY, KP, MM, RU) — Art. 9 GeoJSON mandatory across all tiers; Art. 10/11 required unless 100% segregated Low-Risk origin
Valid EU TRACES NT Spec v1.5 GeoJSON Reference Example:
{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": {
        "ProducerCountry": "CO",
        "ProducerName": "Verified Cooperative Lot 01",
        "ProductionPlace": "Verified Production Plot #1",
        "Area": 6.4215
      },
      "geometry": {
        "type": "Polygon",
        "coordinates": [
          [
            [
              -75.612345,
              2.192346
            ],
            [
              -75.609845,
              2.192346
            ],
            [
              -75.609845,
              2.194666
            ],
            [
              -75.612345,
              2.194666
            ],
            [
              -75.612345,
              2.192346
            ]
          ]
        ]
      }
    }
  ]
}

Section 4 · Technical FAQ (EU TRACES NT Spec v1.5 & 2026/2027 Compliance)

Does SAP Green Token & EU TRACES NT automatically fix broken supplier KML or bowtie polygons?

Customs platforms like SAP Green Token & EU TRACES NT validate Box 44 TARIC declarations and transmit API payloads, but typically reject invalid geometries rather than repairing self-intersections, UTM projections, or 3D Z-coordinates.

What TARIC Box 44 codes must brokers configure in customs software?

Brokers configure C716 for Primary Operator DDS filings, Y141 (until June 29, 2027) for qualifying micro/small operators, C717 for EU small primary producers, Y188/Y196 for downstream exports, and Y190/Y187 for exempt packaging/samples.

How does TraceGuard EUDR integrate with customs brokerage workflows?

TraceGuard acts as a zero-upload pre-flight repair station in browser RAM, outputting clean Spec v1.5 .geojson, TRACES DDS JSON, and Box 44 invoice clauses ready for customs software.

Section 5 · Related EUDR Technical Guides (Internal Pillar Hub)

100% Client-Side Browser RAM · Zero Cloud Upload

Validate, Convert & Auto-Repair Supplier Files in 10 Seconds

100% Client-Side Browser RAM Processing (Zero Cloud Upload, Zero GDPR Supplier Exposure). Supports Excel/CSV, KML, GPX, UTM, WKT, WhatsApp DMS & GeoJSON.

Open Free GeoJSON Converter →