A detention charge lands on a structural-steel invoice. The truck's arrival time sits in a superintendent's daily report, the unloading terms sit in the supplier agreement, and accounts payable (AP) has to decide by Friday whether the charge is supported.
A freight audit compares each carrier or supplier invoice against the contracted rate, shipment record, and delivery evidence before approving payment. It catches duplicate invoices, incorrect rates, fuel-surcharge miscalculations, and accessorial charges nobody agreed to. Freight audit and payment extends the same workflow through payment execution and cost allocation, and either scope can run as software, as an outsourced service, or as a hybrid that keeps approvals in-house.
What follows covers the six checks every invoice should pass, how to choose between software and a service, the statutory deadlines that govern a billing dispute, and the points where a person still has to confirm what happened at the point of delivery.
What a Freight Audit Checks Before Payment
Three axes get compared on every invoice: what was billed, what was contracted, and what happened in the field. That comparison depends on structured data extraction from records that were never designed to line up with each other, which is why a workflow that reads well on paper still stalls on a scanned bill of lading.
The Six Core Checks
Invoice collection: Capture carrier invoices and the freight charges buried inside material supplier invoices, whether they arrive as PDFs, spreadsheets, email attachments, or structured records.
Shipment verification: Match the invoice to the purchase order, rate confirmation, bill of lading (BOL), proof of delivery (POD), and the relevant project records.
Rate validation: Recalculate base rates, fuel surcharges, freight classifications, discounts, and agreed accessorial fees against the applicable contract or tariff.
Exception identification: Flag duplicate invoices, incorrect weights, missing discounts, unsupported detention, and anything outside the approved tolerance.
Dispute resolution: Assemble the rate confirmation, invoice, BOL, POD, delivery logs, and correspondence needed to request a corrected invoice or a credit.
Payment and reporting: Route verified charges for approval, cost allocation, payment execution, and analysis by carrier, supplier, project, lane, or material category.
Prepayment, Post-Payment, and the Deadlines That Apply
Prepayment audit stops an unsupported charge before money leaves the company. Post-payment audit reviews paid history to recover credits and surfaces the repeated billing pattern a single-invoice check will never see. Commercial shippers set their own timing on both, which makes the contractual deadline the real constraint rather than any external requirement.
Two clocks matter, and they get conflated all the time. Under 49 U.S.C. 13710, a motor carrier must issue any bill for charges beyond those originally billed within 180 days of the original bill, and a shipper must contest a bill within 180 days of receiving it. Recovering an overcharge is a different remedy on a different clock: 18 months to bring a civil action under 49 U.S.C. 14705. Carrier agreements often impose something shorter than either, so the contract deadline is the one to diary.
Why Freight Audit Matters for Cost Control
Freight is one of the few cost categories where the billing record and the operational record live in different systems, and neither is complete on its own. A supplier can bill freight on structural steel without indicating whether the agreed rate included unloading. An aggregate delivery can carry detention with no note of why the truck waited, and the reason decides the answer. An unavailable crane, a delayed receiving crew, and a carrier arriving outside its appointment window each point to a different payer.
Delivery Conditions Decide Who Pays
A disputed charge turns on whether procurement terms, transportation records, and delivery evidence agree, and the audit's job is to establish that before approval. In practice, that means three checks in order: confirm the contracted term covers the billed condition, confirm the shipment record shows the condition occurring, and confirm the field record identifies the cause. Where any of the three fails, the charge is an operational question rather than an accounting one and routes to the project team instead of being coded to a material budget unreviewed.
The Fuel Surcharge Formula Is Contractual
Fuel surcharges are a recurring checkpoint because the index and the formula are contractual, not standard. The U.S. Energy Information Administration publishes retail diesel prices that many shippers and carriers use in pricing formulas, and it states plainly that it does not calculate or regulate carrier surcharges. The audit confirms the contract's specified index, shipment week, calculation table, linehaul base, and any exclusions for accessorial charges.
Recurring Charges Only Show Up in Aggregate
Clean freight data answers questions a single invoice cannot: which projects generate repeated detention, which suppliers embed freight without enough detail to check, which carriers bill limited-access fees most often, and which lanes drift from contracted rates. Procurement uses those findings in negotiations; operations fixes the receiving conditions that generate legitimate recurring charges. Neither can act on a single freight account total, which is why companies keep charge-level detail through to the ledger.
Freight Audit Software, Services, and In-House Models
Four operating models exist, and the choice turns on invoice volume, contract complexity, in-house freight expertise, and how much field confirmation each exception needs.
Operating model | Who runs the checks | Who controls payment | Strongest fit when |
|---|---|---|---|
Freight audit software | Configured rules, staff resolve exceptions | In-house | Rate tables and shipment identifiers are reliable |
Standalone audit service | Outsourced auditor | In-house | Freight expertise is the gap, not payment capacity |
Freight audit and payment | Outsourced auditor | Outsourced provider | Payment administration is moving outside |
In-house or hybrid | Internal team, optionally with tooling | In-house | Contract and jobsite context decides most charges |
Each model carries a real cost. Software needs somebody to keep rate tables current and shipment identifiers consistent, and the team still needs enough freight expertise to resolve what the rules cannot interpret. A standalone service buys that expertise and adds handoffs between the auditor, AP, project teams, and whoever owns carrier escalation, each of which is a place an exception stalls.
Full audit and payment removes that handoff and moves funding controls outside the company, so you must define segregation of duties, payment authorization, and responsibility for unresolved disputes before the move, not after. In-house review preserves the contract and jobsite context that decides most disputed charges, and it scales poorly across inconsistent supplier invoices.
What Slows a Freight Invoice Down
Three bottlenecks absorb most of the hours. All three share a pattern: somebody has to search across systems or interpret ambiguous evidence instead of applying a rule.
Invoice Matching and Rate Validation
A material invoice, carrier bill, purchase order, and delivery record are all meant to describe the same shipment, but they rarely use the same words. Document processing rules have to absorb differences in layout, carrier terminology, units of measure, and surcharge structure. Mode adds another layer. Flatbed deliveries need checks for tarp, detention, and unloading charges; less-than-truckload (LTL) shipments need checks for freight class, reweigh, liftgate, and limited-access fees. Build a crosswalk of equivalent carrier labels before comparing anything.
Decide which system controls each field, and hold back automated comparison until those records are complete and aligned. Rate repositories need updating after every contract amendment, and ambiguous tariff language belongs with procurement or legal, not inside an automated approval.
Detention, Limited Access, and Jobsite Evidence
When a charge depends on what happened at the delivery point, the evidence is operational. Driver detention is a delay at the start of loading or unloading that eats into a driver's available hours. Validating it means collecting arrival and departure timestamps, the delivery appointment, the POD, driver notes, and confirmation from the receiving crew.
Limited-access fees turn on the contract. Check whether it covers the fee, whether the carrier or supplier disclosed or duplicated it, and whether the supplier's delivered price already included it. A billed liftgate raises a narrower question: was unloading equipment available, and did the carrier actually use a liftgate? Poor scans and handwritten delivery records lead a person, not a system, to generate false positives.
Carrier Dispute Coordination
Open a dispute only once the contract position and the evidence are clear. For a motor-carrier overcharge claim under 49 CFR Part 378, the filing has to name the claimant, the file number, the amount sought, the rate or classification claimed, the complete tariff authority, and freight bill payment information. A strong packet includes the disputed line highlighted, the BOL, the POD, delivery timestamps, and a concise explanation of the requested correction.
Prioritization runs on financial impact, dispute deadline, evidence quality, and recurrence. A small charge repeated across every delivery can carry more total exposure than a single large variance, so recurring charges move ahead in the queue. Where a dispute exposes a stale rate table or an unclear delivery term, the fix belongs in the contract record rather than in the next dispute.
Run Freight Audit Workflows Across Finance and Project Systems
Datagrid's AI agents can execute configured workflows across project, procurement, and finance systems, which matters when the evidence for one approval sits in three of them. Datagrid's integrations reach project context in Procore or Autodesk Construction Cloud alongside financial records in CMiC, Viewpoint Vista, Sage Intacct, QuickBooks, or Oracle NetSuite, and the Audit Agent can verify project files against defined requirements and flag gaps for review.
Two things must be true before any of it runs: source permissions must be granted, and shipment identifiers must be consistent enough to match. Payment authorization and segregation-of-duties controls stay with the company's financial system and its named approvers, and contract ambiguity routes to procurement rather than to an assumed rule. Datagrid's Document Comparison Agent can handle the invoice-against-record side of that matching.
Start with one repeatable exception category, such as detention on steel deliveries or limited-access charges embedded in material invoices. Sample extracted fields against a known-good month, confirm the rate repository, define the required evidence, and work through the false positives before extending across carriers and projects.
Automate Freight Invoice Verification With Datagrid's Agentic AI
Datagrid's Audit Agent and Document Comparison Agent can run the first pass across connected invoices, rate agreements, shipment records, and delivery evidence:
Invoice-to-contract rate validation: Recalculate base rates, fuel surcharges, discounts, and agreed accessorials against the governing rate confirmation or tariff, and flag every line outside tolerance.
Shipment record matching: Compare each invoice against the purchase order, BOL, POD, and delivery log, and identify which required record is missing, not just that the match failed.
Duplicate and accessorial detection: Surface repeated invoice references, duplicated limited-access fees, and detention with no timestamps.
Dispute packet assembly: Collect the invoice, rate terms, BOL, POD, timestamps, and correspondence into one filing-ready packet, with a draft explanation of the requested correction.
Charge-level spend reporting: Structure results by project, supplier, carrier, lane, and exception type. Recurring variances are invisible at the account level and obvious at the charge level, and the difference determines whether a negotiation has evidence to back it up.
Accounts payable and the project team should still confirm the field conditions behind any detention, liftgate, or limited-access charge before approving or disputing it.
Get started with Datagrid, point it at last month's freight invoices, and compare its exception list against the one your own review produced.
Frequently Asked Questions About Freight Audit
What Are the Stages of a Freight Audit?
Six stages: invoice collection, shipment verification, rate validation, exception identification, dispute resolution, and payment and reporting. Together, they match each charge to the applicable purchase order, rate terms, shipment records, and delivery evidence before approval.
When Should Teams Use Prepayment Rather Than Post-Payment Freight Audits?
Most teams run both, and the split depends on what each can still change. A prepayment check can stop the payment; a post-payment pass can only pursue a credit, but it sees patterns across months that no single invoice reveals. Prepayment as the default, post-payment quarterly, is a common shape.
What Records Are Needed to Validate Driver Detention?
The gate timestamps, the scheduled appointment window, proof of delivery, whatever the driver noted at the time, and a statement from whoever received the load. Those get compared against the detention terms in the contract before the charge is approved or disputed.
How Long Do You Have to Dispute a Freight Bill?
A shipper has 180 days from receipt to contest a bill under 49 U.S.C. 13710, and a carrier has 180 days from the original bill to add charges. Recovering an overcharge through a civil action runs on an 18-month clock instead. Carrier agreements often set a shorter period, so check the contract before relying on the statute.
