CrunchCode.

The quietest margin losses are not in linehaul. They are in audit and exception recovery.

Everybody watches the linehaul rate, the fuel table and the deadhead miles. Nobody watches the detention charge that never became a billable line, or the accessorial a carrier billed you twice. It never shows up as a loss. It shows up as margin that was never there.

01Accessorials that never reach the invoice
Detention runs at a shipper's dock. The driver reports it, the note lands in an email, and it never becomes a billable record. Same pattern for demurrage on an intermodal move, reconsignment, layover, limited access.
02Rates applied from a stale table
The rate structure changed in the contract and not in the code. Every load after that date is quietly mispriced, and nothing errors.
03Variance under a threshold, written off unchallenged
At the broker in C06, building one manual dispute took 45 minutes — so anything under $50 was written off. At 12,000 invoices a month, thousands of small variances were never challenged.
04Invoices in mixed formats
That broker took ~12,000 carrier invoices a month across 8 carriers as PDFs and EDI 210, eight rate structures, normalized by hand in spreadsheets by an AP team of four (C06).
05No line from a charge back to the event that caused it
The 990 says the load was accepted, the 214s say where it went, the POD is somewhere — and nothing joins any of it to the invoice line. Every dispute becomes an investigation.
01Every individual invoice looks plausible. Only the aggregate tells you
That is why it survives both audit season and budget season: there is no line item called leakage, so there is nothing to cut or defend.
02To operations it reads as margin per load drifting down while volume goes up — blamed on the market, because the market is always available
03To finance it reads as a recovery number flat for three years and a write-off threshold nobody has revisited since it was set
04It runs both directions at once: you under-bill customers for services you delivered, and over-pay carriers for charges nobody verified
At the 3PL in C01, retroactively reconciled accessorials — fuel surcharge, detention, residential — plus services delivered and never billed at all, ran $45,000 a month.
$45,000 a month (C01)
05The carriers' side of this is automated
Yours probably is not, and that asymmetry compounds every year you grow.

A finance-looking problem with an engineering root. Three mechanics, all fixable.

01Weak event capture
A billable event — a detention clock starting, a second stop, a missed appointment — either becomes a structured record when it happens or it does not exist. Most systems capture it as free text in a note field, which for billing is the same thing.
02No canonical invoice object
Eight carriers, eight rate structures, PDFs and 210s side by side. Until they normalize into one shape, billed-against-contracted cannot be compared programmatically and every check falls to a person.
03Audit logic lives in people, not in code
The rate card, the fuel formula, the accessorial schedule and the contract clause governing each are known by your AP lead. So the dispute threshold is not set by the size of the error — it is set by how long a human takes to build a case. Fix capture and normalization and the threshold moves on its own.

What changes

EXH. C06Monthly recovery from carrier overcharges
WAS
$8,000
NOW
$67,000
The AP team absorbed 40% volume growth with no added headcount
EXH. C06Dispute threshold
WAS
$50
NOW
$5
Every variance flagged with its evidence
EXH. C06Invoice normalization · manual work
WAS
3 hours a day
NOW
Automatic
Every invoice line traces back to its shipment event
EXH. C01Monthly losses
WAS
$45,000
NOW
$3,800
Freight audit covers 87% of invoice volume with no manual touch
EXH. C01New carrier onboarding
WAS
3 weeks
NOW
4 days
Cascading carrier-API outages: zero in the six months after launch

When the leak is process, not code

No 01Out of scope

Ask AP what share of variances they actually file.

If they know the number, it is high, and disputes are won but slowly — your constraint is capacity, not software. Engineering is the expensive way to solve that.

No 02Out of scope

Check whether your rate cards are digitized.

If the contracts are PDFs in a shared drive and nobody has structured the accessorial schedules, the first job is contract normalization — a data project, and we are an expensive way to do data entry.

No 03Out of scope

Read what the contract entitles you to.

If the tariff says the charge is valid, no software recovers it. Automation finds errors; it does not renegotiate deals you already signed.

No 04Out of scope

The gap we will not paper over:

We have no case in cross-border duty calculation, claims automation or parcel rate optimization. Our customs-adjacent work (C11) is document checks at a container terminal, not duty. If that is where your money goes, we would be learning on your budget — the exact arrangement this page argues against.

How we start — the two-week margin reconciliation.

$7,500. Fixed scope. Two weeks. Run against 90 days of your own invoice data — not a benchmark, not an industry average. Yours. What we hand back: the size of the leak in dollars, with the evidence line by line. The split between under-billing customers and over-paying carriers — two different fixes. The variance bands you write off and what they add up to over a year. And the recovery available without renegotiating a single carrier contract. For scale, not as a promise: the improvement at the broker in C06 was $59,000 a month — the distance between $8,000 recovered before and $67,000 after. Two weeks is how you find out what your number is. If you are not sure where the problem is, start here. Nothing after it is required.

Start the margin reconciliationWhat the two weeks contain
InputWhat we ask you for
  • 0190 days of carrier invoices however they arrive — PDF, EDI 210, portal export
  • 02The contracted rate cards and accessorial schedules that govern them
  • 03Last quarter's write-off report
  • 04Read access to the operational events behind the loads: 214s, PODs, appointment records

Or bring in the people who fix this:

Engineers who have built invoice matching and accessorial capture, on your team — staff augmentationAn audit and dispute engine, delivered end to end — custom software deliveryBilling engineers you keep — contract-to-hire
01Article — Your margin is not leaking from linehaul
From event capture to the write-off threshold.
02C09 — US 3PL hub, 35,000+ shipments a day
P1 MTTR 45–90 min → 11 min; 100% of night incidents closed without the client.
03C05 — non-asset 3PL with major US retail accounts
Onboarding 8–10 weeks → 12 days; 856 ASN discrepancy 4% → 0.3%.
04Next door — PE-backed and post-acquisition