NewDocument validation — now in private beta

The operating system for customs brokers.

Customs OS reads every document in a packet, cross-checks them against each other with a deterministic rule engine, and hands your broker a reviewed file instead of a stack of PDFs. The broker stays in control — we just take out the retyping and the reconciliation.

Fresh Produce · Italy → Ukraine
Packet · 5 documents extracted
Invoice
Packing list
Bill of lading
Certificate of origin
Arrival notice
Validation1 needs review· 11 passed
value_match
incoterms_match
weights_add_up
origin_agrees
parties_match
Country of origin conflictorigin_agrees
invoice.pdf · p.1origin = CN
packing-list.pdf · p.2origin = VN
ConfirmedFalse positive
The problem

Brokers still retype PDFs and reconcile them by hand.

A single entry pulls together a dozen documents, and every figure has to agree across all of them. Today that reconciliation happens by hand — and one mismatch that slips through becomes a costly correction down the line.

8–12Documents in a single import file, each cross-checked by hand
Every fieldValue, origin, incoterms, parties, weights and dates all have to agree across them
By handHow brokers reconcile that stack today — one PDF eyeballed against the next
1 missA single mismatched figure pushes a wrong entry downstream
Platform

What document validation actually does.

Four steps, one continuous flow: AI extracts every field, a deterministic engine cross-checks the documents, and the broker reviews only what needs judgment.

01 · Intake

Extract every field from any layout you throw at us.

Extracted fields
invoice_no884-21
shipperNorthwind GmbH
consigneeRotterdam BV
originCN
incotermsCIF
total_value€48,210.00
02 · Checks

Deterministic rules judge the AI's read.

Rule engine
value_match
origin_agrees
incoterms_match
weights_add_up
parties_match
03 · Evidence

Every value traces back to its source document and page.

p.1 · box
04 · Review

The broker reviews only the exceptions.

Review queue
Country of origin conflictinvoice vs. packing list
ConfirmedFalse positiveExtraction defect
Total value mismatchΔ €450.00
Net weight mismatchpacking list vs. B/L
Deterministic engine

AI reads. Rules decide.

Language models are excellent readers and unreliable judges — and a customs filing is no place for a confident guess. So the AI only extracts what is on the page. Every verdict comes from explicit rules, not a model's opinion.

Auditable
Every pass or fail traces back to a named, versioned rule you can read.
Repeatable
Same packet in, same verdicts out. No temperature, no drift, no surprises.
Reviewable
The AI's read is shown next to the rule that judged it, so a broker can verify in seconds.
rule origin_agrees {
invoice.origin == packing.origin
} → fail
rule value_match {
invoice.total == declared.value
} → pass
How it works

From a pile of PDFs to a reviewable packet.

Drop the documents in. We extract, reconcile, and surface the conflicts — so your brokers spend their time only on the ones that need their judgment.

  1. 01

    Drop the packet.

    Upload or drag in the whole file — commercial invoice, packing list, bill of lading, certificate of origin, arrival notice. Any layout, scanned or digital.

  2. 02

    We extract every field.

    Typed values, each one traceable back to the document and page it came from.

  3. 03

    Deterministic checks run across every document.

    The rule engine cross-checks declared value, country of origin, incoterms, shipper, consignee, weights, and dates. Conflicts are shown side by side.

  4. 04

    The broker reviews the exceptions.

    A single queue of what actually needs judgment. The broker confirms or dismisses each flag, and that decision is recorded against the packet.

Built around the broker

We back your brokers. We don't replace them.

Customs OS is a tool your licensed broker reviews before acting — never an autopilot that files on its own. The reading and the cross-checking are ours; the judgment, the license, and the call stay with your people.

No autopilot

Nothing is ever filed automatically. Every output is review material for a human — not an action taken on your behalf.

Judgment stays human

The broker confirms or dismisses each flag. Their decision is what counts, and it is recorded against the packet.

Your team gets faster, not smaller

We take out the retyping and the reconciliation so brokers spend their hours on the calls that actually need a license.

Trust & compliance

Compliance and data protection, built in.

We handle other people's trade documents for a living. Here is how we treat them — in plain terms, with the legal detail one click away.

GDPR, UK GDPR & Swiss FADP

We process your data as your processor under a DPA with EU Standard Contractual Clauses, ready to sign.

Read the DPA

Your documents never train a model

Extraction runs through the Vercel AI Gateway, configured for no training and no retention on your content.

How we handle data

Encrypted in transit and at rest

TLS 1.2+ on the wire, AES-256 at rest. Authentication secrets and tokens are encrypted separately.

Isolated per tenant

Separation at the application and database layer, with least-privilege internal access.

Transparent sub-processors

A short, published list of every provider that touches data — with 30 days' notice before it ever changes.

See the list

72-hour breach notification

If a breach ever affects your data, we notify the account's primary contact within 72 hours of finding it.

SOC 2 is in progress. Reviewing us before a security questionnaire? Bring it to the demo.

FAQ

Questions brokers ask before a demo.

Short answers. If you want the longer version, book 30 minutes and bring your hardest packet.

Ready when you are

Stop retyping. Start clearing.

A 30-minute demo with your real packets. We'll validate them live — and if we can't, we'll tell you on the call.