Skip to main content
Each carrier delivers invoice data in its own CSV format. The pages in this group document those formats individually — what columns appear, what each column means, how multi-row shipments are structured, and where line-item charges live. Each integration has a downloadable synthetic CSV you can parse against without needing a live integration.
All sample data on these pages is synthetic. Tracking numbers, account numbers, addresses, and reference fields are fabricated and do not correspond to any real shipments or customers.

​
Integrations

IntegrationRegional variantsDelimiterColumn countCharge structure
DHL eCommerce—,78One row per shipment; charges spread across named columns (Charge*, ZFuel*, ZSC*, ZRM*)
DHL Express—,153Line Type marker (I / S); charges in XC1–XC9 column groups
DPDEnglish, Dutch, German;30–43One row per shipment; charges in named columns (Base price / Tarief / Toeslag, etc.)
FedExUS, UK, NL,168 (UK/NL) or 210 (US)One row per shipment; 51 (Label, Amount) charge-pair columns
Royal Mail—,38SAP BEx report with 2 header rows; shipments combined with separate tracking file
UPS—,252One row per charge; multiple rows per shipment share a tracking number
USPS—,21One row per transaction (1:1 with line items)

​
How to use these samples

  • Prototype your integration without needing a live carrier connection. Download the CSV, run it through your own ingestion code, and compare against the schema documented on each page.
  • Understand the Trackstar invoice_line_items schema in context. Each page lists which raw columns Trackstar maps to which normalized field (tracking_number, invoice_id, charge_description, gross_cost, net_cost, etc.).
  • Test your downstream systems against realistic-shaped data, including multi-row shipments, multi-currency invoices, and empty optional columns.
For the normalized API that sits over all these formats, see Invoice Line Items. For the raw-file endpoint that returns presigned URLs to a customer’s actual (non-synthetic) files, see Files.