Use case · Logistics

Check every extra chargeagainst the bill of lading.

Your agent reads the bill of lading next to the invoice and the tariff, and says whether each extra charge holds up.

EXTRA CHARGE · WAS IT AUTHORIZED?FREIGHT AUDIT AGENT
RATE DECISION AThe charge wasn't annotated on the bill of lading
not supported
RATE DECISION BThe shipper authorized the billing
supported
Same question, opposite outcomes. What the bill of lading shows decides it.PAST RATE DECISIONS · CITED

The work today

The bill of lading decides
whether a charge holds up.

THE DOCUMENTS

Bills of lading, receipts, invoices.

Plus the tariff and the tender that set the rules, often scanned, stamped and written on.

THE CHECK

Charge to authorization.

Each extra charge matched to an annotation, a tariff item or the shipper's approval.

THE COST

Paper that never meets the invoice.

The bill of lading sits in one place, the invoice in another, and the charge gets paid.

How it works

Read it. Connect it.
Decide it.

01 · DOCUMENTS

Scans and handwriting too.

Bills of lading are read with their annotations, stamps and handwriting, each scored and located.

Document Intelligence →
02 · DATA

Every document joined.

Bill of lading, delivery receipt, invoice and shipment, linked in one query.

Data Explorer →
03 · AGENTS

Supported or not.

The agent says whether each charge is supported, citing the annotation or the rule.

Agent Builder →

Run at scale

Every bill,
every charge.

Run the agent in batch across every shipment. You decide what a low score triggers, so people only handle the exceptions.

How to start

Start with charges you've already disputed.

Run them through Meibel and compare: what it caught, what it missed and how confident it was.

A starting point, not a packaged tool. Build it your way: your rules, your data, your systems.

How agents are built →
PALETTE