Freight Audit Software: 9 Checks Before You Approve a Carrier Invoice

Freight Audit Software checks carrier invoices against shipment records, agreed rates, and supporting evidence. It flags possible duplicates, unexpected fees, and other differences before or after payment. The aim is to give reviewers a clear reason to approve, question, or dispute a charge.

The software should explain each finding rather than simply mark a bill as wrong. This article covers nine checks, a practical Freight Invoice Auditing workflow, rate-data requirements, and the tests that matter when you compare tools.

What does a freight audit compare?

An audit connects the invoice to the shipment and the applicable pricing agreement. It may check the route, service, weight, dimensions, freight class, fuel charge, and extra services. The exact checks depend on transport mode and contract terms.

For example, a parcel audit needs different data from an ocean freight audit. A domestic truckload contract may use lane rates and detention rules, while less-than-truckload pricing may involve class and weight. Therefore, start with your shipment mix.

GSA’s transportation invoice audit guidance distinguishes prepayment and post-payment audits in its federal context. The useful general distinction is timing: one checks before funds leave, while the other reviews charges already paid. Federal requirements do not automatically apply to a private shipper.

Anomoz’s article on transportation management software covers planning and execution. Freight audit focuses on the later financial check, using the records those operational systems create.

9 invoice checks worth evaluating

1. Shipment and invoice matching

The system should match bills to actual shipments using stable references. These might include a tracking number, bill of lading, purchase order, or internal shipment ID. A carrier name and date alone may not identify the right movement.

Also support consolidated invoices and several invoices for one shipment. A base charge and later adjustment can both be valid. Matching needs to preserve those relationships rather than force every shipment into one bill.

2. Duplicate detection with context

A repeated invoice number is a useful signal, but carriers may use different number formats or issue corrected bills. Check carrier, account, shipment, amount, currency, and document type together. The result should show why the system suspects a duplicate.

Do not reject every similar amount automatically. Two shipments can have the same price. Instead, route uncertain matches to review and preserve the decision so later bills receive consistent treatment.

3. Correct contract and effective date

A rate agreement can change over time. The audit must apply the version that governs the shipment or charge under the contract. Using today’s rate for an older movement can create a false dispute.

Record lane, service, account, region, and date rules clearly. Also keep the original agreement and approved amendments. A spreadsheet of rates without its source and effective dates can be hard to defend.

4. Weight, dimensions, and class

Shipping data may include measured weight, declared weight, dimensional weight, or freight class. These values serve different purposes. Compare them under the carrier’s applicable rules rather than assuming the smallest value determines the bill.

FedEx’s dimensional-weight explanation shows why parcel size can affect pricing. For an audit, the key is to retain measurements and apply the correct service and contract rule. Do not use one divisor for every carrier or account.

Where class changes affect a freight bill, request the supporting basis and route the case to someone who understands the shipment. A software flag is a starting point for review, not a final technical judgment.

5. Fuel surcharge calculations

Fuel charges may use a contract table, a published index, and a defined calculation basis. Keep the applicable dates and source values. Then show the expected charge alongside the billed amount.

Check whether the percentage applies to the base freight charge or another defined amount. A correct percentage on the wrong base can still produce a wrong total. Also define rounding and currency precision.

6. Accessorial charges and evidence

Accessorials are charges for services beyond basic transport, such as liftgate use, waiting time, or special handling. The audit should check whether the service occurred and whether the contract allows the charge.

Evidence may include a delivery record, signed instruction, appointment history, or arrival and departure times. However, missing evidence does not always prove the charge is invalid. Create a request and review path instead of deleting the line.

7. Currency, tax, and arithmetic

Check line totals, invoice totals, currency, and any applicable tax treatment. Multi-currency work also needs a clear rule for exchange rates and reporting currency. Keep the original invoice values even when finance reports in another currency.

Separate arithmetic validation from contract review. A bill can add up correctly while using the wrong rate. Conversely, a small rounding difference may be valid under agreed rules, so set tolerances deliberately.

8. Credits and prior settlements

A credit note or corrected invoice changes the amount still due. Link it to the original bill and shipment. Otherwise, the system may approve both the old amount and the revised amount.

Also check whether a disputed charge has already been settled through another route. A post-payment audit should not count a recovered amount twice. Store the credit, cash receipt, or adjustment reference that proves the outcome.

9. Approval and payment handoff

Show which lines passed, which need review, and which remain in dispute. Some businesses allow partial payment, while others hold the invoice. Configure that choice according to the agreement and finance process.

Keep approved, sent for payment, and paid as separate states. An audit approval does not prove that the accounting system completed payment. Record the export and payment references so staff can trace the handoff.

A practical audit workflow

Consider a distributor that receives a monthly carrier invoice covering many shipments. The system imports the bill and checks required fields. It then matches each line to shipment data and the relevant rate agreement.

First, routine matches pass the configured checks. Next, exceptions enter queues by reason, such as unmatched shipment, rate difference, or unsupported waiting charge. Each queue has an owner and a target review date.

A reviewer opens a waiting-charge case and compares the invoice with the site’s arrival and departure records. If the evidence supports a dispute, they send a clear request with the shipment reference and expected adjustment. If the charge is valid, they record that finding.

Finally, finance receives the approved amount and the unresolved items. The case remains open until any agreed credit or payment adjustment appears. This is an illustrative workflow, not a claimed savings result.

Prepayment and post-payment audits

Prepayment checks can prevent some incorrect payments, but they need timely data and review. If every small variance stops the bill, the process may create delays and carrier friction. Use tolerances and exception rules that fit your agreement.

Post-payment review can work with fuller records and historical data. However, recovery may depend on dispute windows and evidence. Record the relevant contract dates and do not assume every old charge remains recoverable.

Some businesses use both approaches. They run core checks before payment and review patterns later. For example, a post-payment analysis might reveal repeated fees that deserve a contract or operating-process change.

Data quality determines audit quality

Start with invoice line detail, shipment references, contract versions, and supporting documents. A PDF total alone may not provide enough information for line-level checks. Ask how the tool obtains and validates the data it needs.

If it reads invoices with OCR, review uncertain fields before matching. A misread decimal or reference can produce false exceptions. Use validation rules and preserve the original file for comparison.

Also standardize carrier names and charge codes. One carrier may use several labels for related fees, while two carriers may use the same label differently. Keep mappings explicit and assign an owner to approve changes.

Anomoz’s guide to TMS logistics capabilities explains related operational records. Connect the audit to these records where useful, while keeping finance approval in the correct system.

How to handle disputes without losing the trail

A dispute should state the invoice, shipment, charge, reason, and requested amount. Attach relevant evidence and record the date sent. A clear case reduces the need for the carrier to ask basic questions again.

Next, track replies and outcomes against the same case. Avoid storing the decision only in one employee’s inbox. Staff should see whether the carrier accepted, rejected, or requested more information.

Also distinguish a suspected error from a confirmed adjustment. Do not report every flagged amount as savings. A valid measure uses credits or other documented outcomes and avoids counting the same recovery twice.

In-house tool, managed service, or custom integration?

An in-house tool gives your team direct control over rules and reviews. Yet it needs staff who understand rates, evidence, and carrier communication. The software cannot replace that knowledge.

A managed audit service may handle parts of the process for you. Ask how it calculates fees, defines savings, handles disputes, and returns your data. Also check who owns the relationship with the carrier.

Custom integration fits when your records sit across a CRM, dispatch platform, and accounting system. Anomoz’s custom crm development can connect exceptions and evidence to the wider business process. Use established finance and carrier interfaces where they already meet the need.

Demo tests that reveal practical limits

Give vendors the same sample set: a clean invoice, a duplicate candidate, a rate change, a credit note, and an unmatched shipment. Include a valid accessorial and one that needs evidence. Ask the tool to explain each result.

Then change a contract version and repeat the test. The system should show which rule it used, not merely a new total. Also test who can approve a variance or alter a rate table.

Finally, inspect an export failure and a repeated payment handoff. The integration should identify completed records before retrying. A successful audit can still create a finance problem if the export duplicates payable lines.

Measures to track after launch

Track match rate, false exceptions, review time, dispute age, and confirmed adjustments. Also measure how much manual rate maintenance the process needs. These values help you assess total operating effort.

Review recurring charges by lane, site, and service where the data allows it. A valid waiting charge may point to a loading delay rather than a billing mistake. The best next action may be an operational fix.

Start with one carrier or mode, then expand when the data and rule process are stable. A focused audit with defensible results is more useful than broad coverage with unclear calculations.

Separate rate errors from operational cost drivers

A charge can be accurate and still deserve attention. For example, repeated waiting fees may point to slow loading at one site. Record that finding as an operational issue rather than an invoice error.

Then route it to the team that can change the process. Finance may confirm the bill, while operations reviews appointment timing or site access. This separation keeps dispute reporting honest and helps the business act on valid costs. It also avoids sending carriers weak disputes when the real solution sits inside the shipping process.

Make every audit finding explainable

Freight Audit Software should connect bills, shipment facts, contract rules, and documented outcomes. Start with clean references and a small set of defensible checks. Then expand the audit once reviewers can explain and resolve its exceptions reliably.