Learn how freight audit and payment works, which invoice errors to catch, and how to build a controlled process from rating through settlement.
Freight audit and payment is the process of validating carrier invoices against agreed rates, shipment records, and delivery events before approving payment. A strong process protects margin, gives accounting teams cleaner data, and helps carriers receive accurate payment without avoidable disputes.
1) What a freight audit should verify
An audit starts by matching the invoice to a real shipment. The shipper should confirm the carrier, origin, destination, mode, equipment, shipment date, bill of lading or tracking number, and billed party. Duplicate invoice checks are essential because the same charge can arrive through more than one channel or be resubmitted after a status delay.
The next step is rate validation. Base transportation charges should match the applicable contract, tariff, spot quote, or shipment-specific confirmation. Fuel surcharge calculations need the correct index, effective date, and agreed formula. Accessorials such as detention, liftgate, residential delivery, redelivery, reclassification, and limited-access service should have both contractual support and shipment evidence.
2) Why three-way matching matters
Reliable freight audit resembles a three-way match: the shipment or tender record shows what was requested, the carrier agreement shows what should be charged, and the invoice shows what the carrier billed. Delivery events and supporting documents add evidence when a charge depends on time, location, weight, class, or service completion.
This structure avoids two common mistakes: approving an invoice merely because its total looks reasonable, or rejecting a valid exception without reviewing the operational record. Good audit rules identify discrepancies for review while allowing clean invoices to move quickly.
3) Build an exception workflow, not a bottleneck
Not every mismatch should stop the entire payment cycle. Define tolerances for small rounding differences, route material exceptions to an owner, and record a reason code for every adjustment. High-value discrepancies, duplicate charges, missing proof, and out-of-contract rates deserve priority. Review queues should show the invoice, shipment, contract terms, documents, and communication in one place.
Track exception volume by carrier, charge type, facility, lane, and root cause. A recurring detention charge may point to a dock scheduling problem rather than a billing problem. Reclassification disputes may indicate inaccurate product master data. Audit findings are most valuable when they improve upstream operations.
4) Connect audit to payment and accounting
After approval, the process should create a clear payment status and an accounting-ready record. Use consistent general-ledger coding, cost centers, business units, and shipment references. Preserve the original invoice, adjustments, approvals, and remittance details so finance teams and carriers can understand the final amount.
Separate duties where practical: the person who changes a rate or approves an exception should not have unlimited control over payment. Maintain an audit trail, approval thresholds, and access controls. These controls matter whether payment is executed inside a platform or exported to an ERP or accounts-payable system.
5) Metrics that reveal process health
Useful measures include first-pass match rate, exception rate, duplicate invoices prevented, average approval time, unresolved exception age, recovered or avoided charges, and on-time payment rate. Interpret savings carefully: an identified discrepancy is not a realized saving until the charge is corrected or avoided.
Start with the lanes and carriers that represent the most spend, document current rules, and test results against real invoices before expanding automation. Keep a human review path for ambiguous charges and update rules when contracts change.
Standard Connect brings shipment records, rating logic, documents, exceptions, and settlement workflows together so teams can audit with operational context rather than disconnected spreadsheets. Explore Freight Audit & Settlement at /solutions/freight-audit and Analytics & Reporting at /solutions/analytics-reporting, or request a demo to map the workflow to your freight network.