Compare three different freight review tasks: invoice-to-contract checks, public carrier-record lookups, and broker transaction files.
Freight audit includes three different review jobs
Freight audit may mean checking an invoice against a contract, reviewing public carrier information, or retaining broker transaction records. The first is a payment-control workflow; the second supports carrier review; the third is a recordkeeping duty. Each relies on different information and leads to a different decision.
Invoice audit: compare the bill to the shipment and rate
Finance or transportation teams match an invoice to shipment details, the applicable contract or rate confirmation, and supporting documents. A missing POD, duplicate bill, or disputed accessorial goes to an authorized reviewer. Cass describes comparing transactions with supplier contracts and routing exceptions to audit professionals on its freight-audit page. Trimble’s freight-audit service combines audit and payment options with visibility into rate discrepancies and carrier performance. A3 Freight Payment describes freight payment alongside spend analytics and business-intelligence tools on its service page. Shippers and brokers comparing them should distinguish invoice comparison, managed exception review, spend reporting, and payment; those are separate deliverables.
Carrier-record review: organize the public check and follow-up
A carrier onboarding or operations team can record the source checked, review date, and follow-up owner. FMCSA’s SAFER Company Snapshot provides identification and safety-record information for a one-company lookup. Use it alongside the insurance documents and other checks required by your carrier onboarding and shipment process.
Broker records: retain the transaction trail
49 CFR 371.3 specifies broker transaction records, including freight-charge and carrier-payment details, and provides for retention and inspection. A broker’s records workflow should make the required transaction information retrievable from agreement through payment. This is a rule reference rather than legal advice; brokers should confirm how it applies to their operation with qualified counsel.
Put one invoice through the process
For a freight invoice, follow the original bill, rate, shipment records, exception, reviewer, and final disposition. Distinguish a flagged difference from a confirmed billing error, a carrier claim, and an actual recovery. For a carrier check, log which source was reviewed and who handles follow-up. For broker transaction records, retrieve a completed file from the agreed transaction and verify that the required charge and payment entries are present.
Does an invoice flag prove an overcharge?
No. A difference may result from a missing document, approved service, or an incorrect charge. Check the contract and shipment records before disputing it.
Does a freight audit include payment?
Not necessarily. Audit compares the bill to the agreement; a separate payment workflow releases approved funds. Cass and Trimble describe both audit and payment capabilities, so identify which activities the service proposal actually includes.
Audit and Automation buying guidance
At a glance: Audit automation organizes a defined review of freight invoices, carrier or contractor records, or transaction documents and routes exceptions for human resolution. These review domains are distinct; software flags are not proof of an error, violation, legal compliance or financial recovery. Freight Audit; Cass Freight Expense Accounting; SAFER Company Snapshot; 49 CFR 371.3 — Records to be kept by brokers
Common workflows
- Freight invoice contract review: Compare an invoice with applicable contracts, shipment details and supporting records; route exceptions for review and distinguish a potential mismatch from an accepted claim or recovered amount. Cass describes contract comparison and exception routing as its service workflow. Freight Audit
- Public carrier-record lookup: Use official public records as one input to a broader qualification or monitoring procedure. FMCSA describes SAFER as a one-company lookup with identification and safety-record information; it is not a complete insurance or service qualification decision. SAFER Company Snapshot
- Broker transaction recordkeeping: Map required record fields, retention, ownership and retrieval for the relevant broker transaction. The current eCFR text of 49 CFR 371.3 specifies transaction information and related recordkeeping requirements for brokers; the applicability of the rule should be confirmed for each situation. 49 CFR 371.3 — Records to be kept by brokers
Questions to ask providers
- What exact record, invoice or document is being checked, and what is the authoritative source for the decision?
- Which fields and rules create an exception, and can a reviewer inspect the evidence behind a flag?
- How are valid charges distinguished from duplicates, missing data, disputed accessorials and unresolved cases?
- Who owns review, dispute, approval and final status, and how is that decision retained?
- Can the tool export an auditable record tied to shipment, contract and accounting IDs?
- Which business roles, transaction types, documents, jurisdictions and source systems are outside scope?
- How are data freshness, permissions and source-record corrections handled?
- What measurement separates flagged amounts from accepted claims and actual recovery?
Frequently asked questions
Does an audit alert prove an invoice is incorrect?
No. A flag prompts review of the contract, shipment and supporting evidence. Cass describes exception routing, not independent proof that an exception is an overcharge. Freight Audit
Does freight audit software guarantee savings?
No. Outcome depends on actual invoices, contract terms, evidence, disputes and recovery. No general recovery or error rate is established by this review. Freight Audit
What does FMCSA SAFER provide?
FMCSA describes a one-company lookup with identification and safety-record information. It is not complete verification of insurance, payment history or load-level qualification. SAFER Company Snapshot
What does 49 CFR 371.3 require brokers to record?
The current eCFR text specifies transaction records and fields for brokers, a retention period and transaction-record review rights. Confirm current applicability with qualified counsel or the responsible agency. 49 CFR 371.3 — Records to be kept by brokers
Does carrier record monitoring replace qualification?
No. A public lookup or reminder workflow is only one input. Apply your documented procedures and verify relevant records with authoritative sources and counterparties. SAFER Company Snapshot
How should we measure a freight-audit pilot?
Use a representative invoice sample and separately count reviewed items, confirmed discrepancies, disputed charges, accepted claims, recoveries and unresolved exceptions. Freight Audit
Sources (4)
- Freight Audit — Cass Information Systems
- Cass Freight Expense Accounting — Cass Information Systems
- SAFER Company Snapshot — Federal Motor Carrier Safety Administration
- 49 CFR 371.3 — Records to be kept by brokers — Electronic Code of Federal Regulations / FMCSA