Workflow — Freight Bill Audit

Freight audit at one-third the contingency. Audit every invoice, not a 5% sample.

Carrier invoices line-by-line validated against contract rates, fuel-surcharge tables, accessorial-charge rules (detention, layover, TONU, lumper), and mileage actuals. Overcharge claims filed with carriers automatically. Approved-for-pay queue into the TMS or AP system. Replaces contingency-based FAP firms (Cass, AFS, US Bank, Trax, nVision Global) at a fraction of the per-invoice cost.

Take the AI Assessment Get a Per-Invoice ROI Model

6–12%

Typical contingency on audit savings at FAP firms

Sample audit rate when full-population audit is too expensive

60–85%

Volume off the FAP line after AI cutover

What This Replaces

The FAP Vendor Taking 6–12% of Every Recovery

The work the FAP firm does on every invoice — and the cost of leaving it on contingency.

The labor

Freight bill audit and payment today moves through major FAP firms — Cass Information Systems, AFS Logistics, US Bank (FAP), nVision Global, Trax Technologies — pricing structures around contingency at typically 6–12% of audit savings. Large shippers paying $50M–$500M in annual freight spend can leave seven-figures on the table to FAP contingency every year, with structurally limited audit depth because the FAP economics constrain how granular the audit can go.

The cycle time

Most FAP audits run on a sample (typically 5%) because full-population audit is too expensive at the FAP unit cost. Sample-based audit means recovery rates are bounded by extrapolation — actual overcharges hide in the 95% of invoices that never get reviewed. Disputed accessorial charges (detention, layover, TONU, lumper, fuel-surcharge calculations) are particularly underaudited because the per-invoice analysis takes too long for the FAP economics.

The Workflow

Input · Analysis · Output

What goes into freight audit, what we do to it, and what shows up in the AP system.

Input

Carrier invoice + rate context

Carrier invoice (paper, EDI 210, portal extract)
Contract rates and tariff schedules
Fuel surcharge tables (DOE, carrier-specific)
Accessorial-charge rules (detention, layover, TONU, lumper)
Original BOL and shipment data
Mileage actuals and routing data
Customer-specific freight allowance and chargeback rules

Analysis

Audit, calculate, dispute

Line-by-line rate validation against contract
Fuel-surcharge calculation against current FSC table
Accessorial-charge verification per contract
Mileage validation against carrier vs actuals
Duplicate-invoice detection
Overcharge-claim quantification per invoice
Confidence score per finding; exceptions to AP / freight-management queue

Output

Audit decision into the AP system

Approved-for-pay queue with adjustments
Overcharge claim filed with carrier
Savings report to client / treasury
Direct via TMS API (MercuryGate, Oracle, etc.)
AP-system integration (SAP, Oracle, NetSuite)
Per-invoice audit trail with rule citation
Recovery dashboard for finance

Side by Side

Freight Bill Audit Today vs. With Last Rev

The numbers that matter: cost structure, audit depth, recovery rate, and AP cycle time.

Dimension	Contingency FAP Vendor	Last Rev Freight Bill Audit
Pricing model	6–12% contingency on audit savings	Volume-tiered, benchmarked at one-third the FAP contingency rate
Audit population coverage	Sample (typically 5%)	100% of invoices audited at AI cost
Cycle time, invoice received to audit complete	Days at the FAP vendor	Same-day audit at scale
Accessorial-charge depth	Underaudited because per-invoice analysis takes too long	Full accessorial review per invoice
Overcharge-claim filing	FAP-vendor manual letter, days-to-weeks to file	Auto-drafted with the basis cited per claim
TMS / AP integration	FAP vendor portal handoff	Direct via documented MercuryGate / Oracle / SAP / NetSuite APIs
Audit log per finding	FAP-vendor reports, no rule-level lineage	Source invoice + rule citation + model version + confidence per finding

How It Works

From Carrier Invoice to AP-Cleared Approval

Five steps. Every one logged. Every one reversible if your confidence threshold isn't met.

Submission Lands

Carrier invoice via paper, EDI 210, or portal extract — paired with contract rates, tariff schedules, fuel-surcharge tables, accessorial-charge rules, original BOL, and mileage actuals from the TMS.

Extraction & Classification

Line-by-line rate validation against contract. Fuel-surcharge calculation against current FSC table. Accessorial-charge verification per contract. Mileage validation against carrier vs actuals. Duplicate-invoice detection. Overcharge-claim quantification per invoice.

Validation Against Contract Rules

Findings validated against the shipper's freight contracts and per-lane / per-customer rules. Anything below your confidence threshold per finding is routed to a human exception queue — your call which queue, ours or yours.

Push to AP / TMS

Approved-for-pay queue with adjustments into the AP system (SAP, Oracle, NetSuite) and TMS (MercuryGate, Oracle TMS, Blue Yonder, McLeod LoadMaster) via the documented integration. Overcharge claim filed with carrier with the basis cited.

Audit Log Persisted

Every rate validation, FSC calculation, and accessorial finding logged with the source invoice, rule citation, model version, and confidence score. Carrier-dispute-ready and yours.

Compliance & Defensibility

Built to Meet the Quality Bar Freight Audit Already Runs On

Carrier-tariff and contract-rate fidelity

Per-carrier tariff schedules and contract rates indexed and applied per shipment. Fuel-surcharge calculations track DOE national average and carrier-specific FSC tables with publication-date awareness. Accessorial rules respect per-contract definitions (detention timing windows, layover thresholds, TONU rules, lumper terms).

EDI 210 / 214 / 820 conformance

EDI 210 (Freight Invoice), 214 (Carrier Status Message), and 820 (Payment Order / Remittance) message handling supports the carrier-shipper-bank exchange. Per-trading-partner EDI mapping configurable per onboarding.

Carrier-dispute defensibility

When carriers dispute an overcharge claim, the audit log produces the per-line basis — what rate was applied, which contract clause was cited, what the underlying BOL showed, and what the calculation was. Cleaner chain of custody than the FAP-vendor reconstruction post-claim.

Customer pricing and lane confidentiality

Freight invoice data contains customer pricing, lane structure, and accessorial commitments. Deployable in your VPC or our SOC 2 environment. Encryption in transit and at rest; retention policies tied to your customer contracts and FMC recordkeeping rules.

Common Questions

What Shippers Ask About Freight Bill Audit

Those are the FAP vendors that run the audit work today on contingency at typically 6–12% of audit savings. The competitor on this page is the FAP labor itself plus the contingency margin. We integrate directly into your existing TMS and AP system, audit 100% of invoices at AI cost, and deliver overcharge claims, approved-for-pay queues, and savings reports without the FAP contingency margin.

Most shippers keep the FAP arrangement in place during pilot and early production — we route exceptions, complex disputed claims, and any case that genuinely requires senior-FAP-analyst judgment to the team you already have. Volume to the FAP drops 60–85% on routine invoice audit once cutover completes. You renegotiate at the next renewal from a much better position, often shifting the relationship to higher-complexity work like global-trade-management consulting or specialized industry compliance.

Our pilot success threshold is rate-validation and accessorial-finding accuracy at parity with or above your incumbent FAP, measured on the same shadow-data sample of historical invoices. Anything below your defined confidence threshold per finding is routed to a human exception queue — your call which queue, ours or yours.

Per-invoice AI audit costs are largely fixed regardless of audit population, so 100% audit becomes economically feasible where 5% sampling was the only option before. Recovery rates routinely surface materially higher because the actual overcharges hidden in the 95% of unaudited invoices come out. The audit log records every audit decision so the savings recovery is fully traceable.

Accessorial rules are encoded per contract — detention timing windows, layover thresholds, TONU rules, lumper authorization. Each accessorial charge is verified against the contract definition and the underlying BOL / event data. Auto-flagged disputes for unauthorized accessorials, mistimed detention, or TONU rate misapplication.

Yes — through the documented integration surface each platform supports. MercuryGate via REST APIs; Oracle TMS via Cloud Integration; Blue Yonder TMS via APIs; McLeod LoadMaster via APIs; SAP and Oracle ERP via standard ERP integration; NetSuite via REST APIs. Your IT, finance, and operations teams review and approve service accounts. We do not require platform-side custom development.

Freight-audit pilots typically run 6–8 weeks: 1–2 weeks of integration and per-carrier contract / tariff mapping with the freight-management team, 4 weeks of shadow-mode running on real invoices with no AP-side approvals, 1–2 weeks of supervised cutover on a constrained scope (one carrier, one customer tier). Production rollout is staged after the pilot meets your accuracy and finance sign-off.

We benchmark against your current FAP contingency rate (6–12% of audit savings) restructured around volume tiers and outcome SLAs rather than contingency. Our target is one-third the FAP contingency rate fully loaded, while auditing 100% of invoices instead of a 5% sample. Recovery typically goes up while the cost structure goes down.

Two Ways to Start

Take the AI assessment for a structured read on freight-audit feasibility. Or talk to us if you already know your FAP contingency is the line item you want off your operating budget.

Self-serve · 8 minutes

Take the AI Assessment

A short structured assessment that maps your monthly freight-invoice volume, TMS, and current FAP arrangement to AI feasibility and ROI.

Talk to a specialist

Get a Per-Invoice ROI Model

Send us your monthly freight-invoice volume, your TMS, and your current FAP arrangement. We'll come back with a per-invoice unit-cost comparison and a 6–8 week pilot plan in 5 business days.

Other Workflows

More Logistics & Trade Workflows We Replace

The same approach, applied to the other document-heavy labor lines on your operations and trade-compliance budget.

BOL Processing

BOL extraction → MercuryGate, Oracle TMS, Blue Yonder, Manhattan Active, McLeod LoadMaster.

Detention & Demurrage Tracking

Container event data → FMC-reasonableness analysis and dispute-letter draft.

POD Processing

Signed PODs, manifests → OS&D categorization and freight-claim-letter draft.

Customs Entry Preparation

Entry Summary 7501 — HTS classified, valuation determined → ABI/ACE filing for licensed broker review.