Solutions
One packet in. Filing-ready entry data out.
The work that costs your team hours is not reading a document. It is reconciling four of them, deciding which one your entry system should believe, and being able to prove that decision to CBP eighteen months later.
How it works
Four steps, and a reason each one matters to you
Extraction on its own is commoditised. What removes hours from someone's week is what happens on either side of it.
Ingest the whole packet
Forward the email, drop the PDFs, or connect an inbox or shared folder. One upload per shipment - invoice, packing list, B/L or AWB, and certificate of origin together.
No new system to learn
Your team keeps working the way it already does. Packets arrive by email today, so EntryWrite reads them where they already land instead of asking anyone to change their process.
Extract and reconcile 50+ fields
Importer and consignee, MID, seller, HTS, value, freight, insurance, origin, container references and line items - pulled from every document in the packet and reconciled against each other.
One shipment, not four documents
The hard part was never reading a single invoice. It is deciding which of four documents is right when they disagree. EntryWrite reconciles the packet and shows you where the conflict is.
Validate, then review only exceptions
Rules check invoice totals against line totals, weights and package counts across PL and B/L, HTS against description, and PGA data completeness. Low-confidence fields are flagged.
Your team touches the 20% that needs a human
Clean shipments pass straight through. People spend their time on genuine mismatches instead of re-typing fields that were already correct.
Export filing-ready data
Push mapped entries into your brokerage system via API, SFTP or CSV, or download ACE-ready files.
Mapped to your schema, not a generic spreadsheet
Output lands in the field names your entry system expects, with field-level confidence scores and every value traced back to its source page for CF-28 and post-entry audits.
Capabilities
What you get on day one
Everything below is aimed at one number: how many of your shipments get through without a person touching them.
Packet-level ingestion
One upload per shipment: commercial invoice, packing list, bill of lading or air waybill, and certificate of origin. Combined PDFs are split automatically.
50+ fields per entry
Importer and consignee, MID, seller, HTS, value, freight, insurance, origin, container references, line items and more - extracted per entry, not per page.
Cross-document validation
Totals match line totals. Weights and package counts align across packing list and B/L. HTS codes are checked against descriptions. Missing PGA data raises an alert.
Schema mapping to your system
Pre-built mappings for CargoWise, Descartes, NetCHB, Magaya and QP/WP, with a field-level confidence score on every mapped value.
Exception queue
Review only low-confidence fields and cross-document mismatches. Approve or correct in a few clicks, with the source document open beside the field.
Batch processing
Upload 50 to 200 shipments at once and get reconciled, validated entry drafts back in minutes rather than over an afternoon.
Audit trail and provenance
Click any field to see the exact source page it came from. Export complete entry packets when CBP asks.
Integrations and exports
Push to your brokerage software or TMS by API, SFTP or CSV. ACE/ABI-ready output formats.
Security and compliance
Role-based access, SSO, encryption in transit and at rest, and immutable logs for compliance reviews.
Stop re-keying 50+ fields per shipment
Run a no-obligation pilot on your real import packets and see how many entries go straight through.
- 01You forward one shipment packet from a real lane.
- 02We map it to your entry schema and run the validation rules.
- 03You see exactly which fields came through clean, and which needed a human.