Freight’s paperwork, on autopilot — with your team in control.
The load delivered days ago. The money is stuck in the paper: a proof of delivery photographed in the cab, an invoice that says more than the rate confirmation did, a detention charge nobody can prove and nobody will drop. We automate the reconciliation — every document read on arrival, every charge matched to its evidence, the unproven ones held with the file open — for carriers billing, brokers auditing, and shippers paying. What gets paid is the contract’s call and yours; the system just brings the proof.
- On a carrier invoice, each charge is traced to the proof that settles it: linehaul to the rate confirmation; detention to the in-and-out POD timestamps; lumper to its receipt.
- The last charge — an accessorial with no proof attached — is held with the request already sent, for a person to decide with the evidence open.
The paper trail
Every load ships with a second cargo.
- Booked
- rate confirmations · load tenders
- Moved
- bills of lading · driver-photographed PODs · delivery receipts, signed and exception-noted
- Charged
- carrier invoices · detention and layover records · lumper and accessorial receipts · fuel and toll where the contract cares
- Disputed
- OS&D notes · freight claims · the correspondence that follows
Photographed on a dashboard at dusk, three carriers’ formats in one inbox — read anyway, or held for a person. Never guessed.
Who this is for
Carrier, broker, shipper — same paper, different pain.
- The carrier
- bills faster because the POD is read the minute it’s photographed, not the Friday it’s found.
- The broker
- audits every carrier invoice against the rate con automatically; margin stops leaking through unproven accessorials.
- The shipper
- pays what the contract and the evidence support, with the file to show why.
The truck waited two hours. The argument lasted three weeks.
Detention is real money on both sides — the fix is proof that’s already attached.
The practices behind it
- AI Automation the match that runs as documents arrive
- AI Integration the entry into the TMS you already run
Questions
Asked from the ops desk.
Our PODs are photos from a cab at night.
That’s the canonical input. Reading is content-based and tested on your real PODs during the X-Ray — signatures, stamps, exception notes and all; the unreadable ones hold for a person instead of billing wrong.
Every carrier formats everything differently.
Which is why nothing here is template-matching. The system reads what the document says — a new carrier is onboarding paperwork, not a development project.
How do accessorial disputes actually change?
They start with the file already open: the charge, the contract term, and the evidence — or its absence — side by side. Most arguments end when the proof is one click away; the rest at least start honest.
Does it work with our TMS?
The one you run — reading in, matched results out, holds surfaced where your team already works. That wiring is our AI Integration practice; closed systems have patterns of their own.
Can it handle OS&D and freight claims?
The document side, yes — the claim file assembles the way everything else here does: notes, photos, correspondence, deadlines tracked. The negotiation stays human, with the folder complete.
One lane or the whole board — where do we start?
One lane or one customer’s freight, end to end — prove the match rate and the holds on real volume, then widen. Audit desks usually feel it first: the same stack, arriving already matched.