Built by an ex-Cargowise engineer
From messy email packets to filing-ready customs entries in minutes
Upload the invoice, packing list, B/L or AWB and certificate of origin. EntryWrite extracts, validates and maps 50+ fields to your entry system, ready for ACE/ABI filing with an audit trail.
No card, no integration work to start. Your first 20 shipments are on us.
Mapped to the entry systems small brokers actually file in
System names and marks are the property of their owners. EntryWrite is not affiliated with or endorsed by them.
The work today
You already know which part of the week this is
None of this is a software problem your team created. It is what happens when the entry data arrives as four documents that were never meant to agree.
Four documents, one shipment, three different numbers
The invoice total, the packing list weight and the B/L do not agree, and someone has to decide which one the entry believes - usually under time pressure, usually with no record of why.
EntryWrite reconciles the whole packet and shows you exactly where the conflict is, before it becomes a correction.
The CF-28 arrives eighteen months later
By then the person who keyed the entry has moved on, and the source packet is somewhere in an email thread nobody can find. The work is not answering the question - it is reconstructing the answer.
Every field traces back to the page it came from, with an immutable log, so the response takes minutes instead of an afternoon.
The afternoon that disappears into re-keying
Fifty shipments, forty-odd fields each, all of it already written down somewhere - typed in again because nothing on the desk can read it.
Clean shipments pass straight through. Your team only opens the ones that genuinely need a human.
45-60 minutes of manual keying per US import entryIndustry benchmark
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.
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.
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.
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.
Export filing-ready data
Push mapped entries into your brokerage system via API, SFTP or CSV, or download ACE-ready files.
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.
Free pilot
Your first 20 shipments, processed end to end
Send real import packets from your own lanes. We map them to your entry schema, run the validation rules, and show you how many went straight through. No obligation, no card, no integration work required to start.
Free pilot
20 shipments, free
Run on your own packets. Nothing to install, nothing to sign beyond a DPA.
- 20 shipments processed end to end
- Field mapping configured for your entry system
- Validation rules tuned to your lanes
- A straight-through-processing report on your real packets
- A data processing agreement before you send anything
After the pilot
Transparent per-shipment or tiered pricing, sized to your volume. No quote-only pricing games, and no enterprise floor that a five-person brokerage cannot justify.
- Priced for small brokerages
- Built for 3 to 25 person independent brokers and forwarders, not for an enterprise procurement cycle.
- No per-seat tax on reviewers
- Exception review is the part that keeps you compliant. Charging per reviewer would penalise the workflow that makes the product safe.
- You keep your data
- Export everything at any time. No lock-in through your own entry history.
We will publish per-shipment pricing once the first pilots tell us the right shape for it.
FAQ
The questions brokers actually ask
Is this just OCR?
No. Raw extraction is commoditised - a general model can read an invoice. The work that actually costs your team time is mapping fields to your entry schema, validating them across four documents that disagree, queueing the exceptions for a person, and keeping an audit trail. That is what EntryWrite does.
Do you file directly to ACE/ABI?
We produce filing-ready, mapped entry data and can integrate with ABI-connected systems. Some partners file directly through our API. EntryWrite is not itself the filing system - it removes the keying that happens before you file.
What document types do you support?
Commercial invoices, packing lists, bills of lading and air waybills, certificates of origin, arrival notices, and common PGA forms. Combined PDFs containing several of these are split automatically.
How long does setup take?
Most brokers are processing live shipments within days using email or folder intake. Deeper system integrations follow once the extraction and validation rules are tuned to your lanes.
Who built this?
EntryWrite is built by Ariel Serravalle, an engineer who worked at WiseTech Global - the company behind CargoWise. That means the field mappings are designed by someone who has worked inside the software you file in, rather than inferred from documentation.
What happens to our documents?
They are encrypted in transit with TLS and at rest with AES-256, on managed infrastructure in the region you choose. They are processed only to produce your entry data - never used to train or fine-tune any model, ours or a vendor’s, and never pooled with another customer’s data. You set the retention window: source documents can be purged as soon as an entry is exported, or held for as long as your compliance policy requires. Role-based access controls who can see which shipments, and every access and field change is written to an immutable log.
Can we get a DPA before sending live documents?
Yes, and you should ask for one. You get a data processing agreement in writing before you send a single live document - it is not gated behind a contract or a signed order. The cloud and model providers involved in processing your documents are listed in it, and you are notified before that list changes.
Are you SOC 2 certified?
Not yet. EntryWrite is early. We build to SOC 2 practices - least privilege, audit logging, encrypted storage, change control - but we have not completed an audit, and we are not going to display a badge we have not earned. If a certification is a hard requirement for you today, say so and we will tell you honestly whether to wait.
Do you file on our behalf?
No. EntryWrite produces mapped, validated entry data. The filing, and the legal responsibility that comes with it, stays with your licensed broker. We are not a customs broker and do not hold a licence.
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.