Customs & Foreign Trade
Customs Declaration / Commercial Invoice
Extract commodity, value and party data from commercial invoices and customs paperwork for declaration filing.
The Challenge
Commercial invoices for customs mix HS/commodity codes, Incoterms, multiple currencies and country-of-origin data across non-standard layouts. Errors trigger fines and shipment delays, so accuracy and completeness are critical.
Industries
Customs brokers, exporting manufacturers, logistics & forwarding, trade.
Who Uses It
Customs clearance agents, trade-compliance officers, forwarders.
BASE Schema
Exporter / consignor — Key value set (name, street, postal code, city, country)
Importer / consignee — Key value set (name, street, postal code, city, country)
Invoice number & date — Key value set (number, date)
Line items (description, HS code, qty, value) — Table
Country of origin — Enumeration (ISO 3166 country codes)
Incoterms — Enumeration (EXW, FCA, FAS, FOB, CFR, CIF, CPT, CIP, DAP, DPU, DDP)
Currency & total value — Number
Gross/net weight — Number
EORI number — Text
Recommended pipeline settings — Checkbox detection, Context (internal HS code assignment rules)
OPTIONAL Validation
HS code plausibility vs. goods description; EORI/VAT format checks; value totals reconciliation; country-of-origin and Incoterms presence.
Frequently ASked Questions
How can AI speed up customs declarations?
By extracting commodity codes, values, parties and origin from the commercial invoice into a validated dataset that feeds the customs declaration directly.
Can document AI read HS codes from commercial invoices?
Yes — it captures stated HS codes and flags lines where the code and goods description don’t plausibly match.
Why automate customs document processing?
It cuts clearance time, reduces costly declaration errors and penalties, and scales trade volume without adding customs staff.
See more use cases.
Get inspired by further sample data schemas.