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