Skip to content
EntryWrite

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

Packet in, filing-ready entry out, in four steps

Extraction on its own is commoditised. What removes hours from someone's week is what happens on either side of it.

STEP 01

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.

Four shipment documents - commercial invoice, packing list, bill of lading and certificate of origin - being combined into a single reconciled shipment record.
STEP 02

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.

A grid of shipments processed in one batch, most cleared straight through with a handful flagged for review.
STEP 03

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.

An exception queue where most entry rows are cleared and only a mismatched field and a low-confidence field require a reviewer.
STEP 04

Export filing-ready data

Push mapped entries into your brokerage system via API, SFTP or CSV, or download ACE-ready files.

An extracted field linked by a provenance line back to the exact page of the source document it was read from.

Capabilities

What you get on day one

Any model can read an invoice. Only ours can tell you that the invoice and the packing list disagree, which of the two your entry system should believe, and prove where the number came from eighteen months later.

  • 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, so output arrives in the field names your system expects - with a confidence score on every mapped value.

  • Exception queue

    Clean shipments process straight through, so the queue in front of your team is the short one: low-confidence fields and genuine mismatches, with the source document open beside them.

  • 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, backed by immutable logs built for CF-28 responses and post-entry audits. 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.