Document Extraction Engine
The extraction engine inside your customs workflow.
Every trade document type, every field, every customs format — extracted, validated, and filed before your vessel berths.
Pipeline
Five stages, zero manual intervention for clean documents.
Email, API, SFTP, or manual upload. PDF, TIFF, JPEG, EDI.
Page segmentation, table detection, handwriting recognition.
40+ fields extracted per document with confidence scores.
HS code verified against destination country tariff schedule.
Validated entry packet delivered to your broker's queue.
Document Ingestion
Tradevynt accepts trade documents via four channels: email forwarding to a dedicated address, REST API push, SFTP drop into your designated bucket, or manual upload through the web interface. Format support covers the full range of what freight forwarders encounter: PDF scans, TIFF scans, JPEG captures, and EDI X12 856 advanced ship notices. Multi-page documents are handled as a single ingestion unit.
OCR & Layout Analysis
Before extraction begins, Tradevynt builds a structural model of the document. Page regions are segmented into header blocks, data tables, signature areas, and freeform text zones. Table detection identifies rows, columns, and spanning cells — the most common source of field-boundary errors in trade documents. Handwriting recognition covers the supplements and annotations customs personnel add to pre-printed forms. Multi-language support handles Chinese, Spanish, German, and English trade documents in a single processing pass.
Field Extraction
Each field is extracted with a confidence score. Fields scoring below threshold are placed in a review queue — not silently dropped, not guessed. The system extracts 40+ fields per document including all CBP ACE required fields for the entry type. Document-type-specific field models handle the structural differences between a bill of lading and a commercial invoice. Related fields are cross-referenced within the document: declared weight on the packing list checked against the bill of lading, for example.
Tariff Cross-Check
Every extracted HS code is looked up against the destination country's current tariff schedule. Anti-dumping and countervailing duty flags are applied where applicable. Partner Government Agency (PGA) requirements are detected and flagged — FDA, USDA, EPA, and others depending on the commodity. Ambiguous classifications (where a code could map to multiple tariff headings) are flagged for broker review rather than auto-resolved.
Broker Routing
The complete entry packet is delivered to your broker's designated endpoint: webhook push, API response, or direct TMS/broker portal integration. Each delivery includes the full extracted field set, confidence scores, exception log, and a timestamped entry summary PDF. Exception log details every field that was flagged for review, with the specific reason — malformed HS code, weight discrepancy, missing required field, or tariff conflict.
Coverage
Supported document types
Every document class that moves through the customs declaration process.
What gets extracted
Every field your broker needs to file.
Freight forwarders evaluate extraction tools by whether their specific fields are covered. Here's the full list.
Validation
Extraction is only half. Validation is the other.
We flag ambiguity rather than guess. Freight forwarders can't afford silent errors reaching ACE.
Required fields for the entry type must be present. If a field is missing from the source document, the entry is flagged — not processed with a blank. Schema rules are maintained per CBP ACE entry type (01, 02, 06, 07, 11, 23, 86).
Every HS code is verified against the destination country's current tariff schedule — not a cached snapshot. Anti-dumping and countervailing duty applicability is checked. If an HS code has been updated in the current HTS revision and the document uses an outdated code, the discrepancy is flagged.
Low-confidence fields, cross-document discrepancies (weight on BoL vs packing list), and fields with multiple plausible interpretations are placed in a human review queue. Every flagged field includes the specific conflict description. Your broker sees the issue, not a silently-passed error that becomes a CBP inquiry.
See the extraction engine on your documents.
Request access or book a walkthrough with our team.