Carrier invoice audit
Recon reads every carrier invoice against its rate confirmation and POD, clears the ones that match, and escalates the ones that don’t — with the evidence attached.
| Charge | Rate con | Invoiced | Decision |
|---|---|---|---|
| LinehaulAll-in, fuel included | 1,450.00 | 1,450.00 | Match |
| Fuel surchargeNot billable separately | — | 178.00 | Flag Rate was confirmed all-in. FSC billed as a second line. |
| Detention2 hrs free, then $60/hr | 90.00 | 210.00 | Flag POD: in 08:12, out 11:42 — 3.5 hrs on site, 1.5 billable. Carrier billed from arrival. |
| Total | 1,540.00 | 1,838.00 | Variance +$298 |
Matching invoices are cleared automatically. Reviewers open a short queue of real discrepancies instead of every invoice that arrives.
Fuel on an all-in rate. Detention started at the gate. Lumper over cap. The repeatable gaps that quietly erode margin.
What was flagged, why, who decided, and what they saw. An audit six months later is a search, not a reconstruction.
Carriers email invoices and PODs to an address you control, or your team uploads them. PDFs, scans, faxes, phone photos. Nothing changes in your TMS on day one.
Recon pulls the fields that matter — load and pro numbers, every charge line, in and out timestamps, free time, caps — and tells you when a document is too poor to read.
It compares linehaul, fuel, and detention under your terms: all-in versus broken out, free time by stop, and the dollar and percent tolerance you set.
Invoices that match are cleared. Everything else becomes an exception carrying the specific line, the amount, and a reason a controller can act on.
Your team works a short exception queue. Approve, short-pay, or dispute on one screen — with the documents, the flags, and the full audit trail attached.
Recon never moves money. It records a decision and the evidence behind it. Payment stays exactly where it lives today.
Not exotic fraud. The ordinary, repeatable gaps between what was confirmed, what was billed, and what the dock recorded.
Carrier bills from arrival. Rate con starts after free time. POD timestamps settle it.
Rate confirmed all-in. Invoice arrives as linehaul plus fuel. Small on one load, constant across a lane.
Layover, TONU, driver assist, or a second delivery that was never approved in writing.
Billed above the allowance, or billed with no third-party receipt attached.
Same pro number, submitted again weeks later — often through a factoring company.
Rekeyed with a transposed digit, or attached to the wrong load entirely.
Pieces short, weight off, or an exception written at the dock that nobody read.
An invoice with no POD, a POD with no signature, or a signed bill for the wrong stop.
Recon prepares and records a decision. Payment stays in your TMS, your accounting system, your bank. Nothing about your funding flow changes.
Every flag names the charge, the expected amount, the billed amount, and the reason. Your reviewer confirms in seconds instead of re-auditing.
Every extraction, match, view, and decision is logged. Who decided, what they saw, and what they waived is never reconstruction.
Invoices and PODs arrive by email or upload. Rate confirmations come from a TMS export or the same inbox. Live in days, not a quarter. No IT project required.
Reading rate confirmations and writing approvals and notes directly back into the system your team already lives in — so the audit trail sits with the load.
Set the four numbers you already know. Everything below is arithmetic on your inputs.
Assumes matching invoices are cleared without a human. Surfaced is not the same as recovered — what you collect depends on your carrier terms and how you work a dispute.
These are your numbers, not our results. Recon is in design-partner stage. We would rather you check the arithmetic than take a case study on faith.
Design partners — open now
If you’re moving a few hundred to a couple thousand loads a month and someone on your team is still opening carrier invoices one at a time, we’ll run your last thirty days through Recon and walk you through every discrepancy it finds. No integration. No system access. No commitment.