Freight Audit and Payment: Catch Rating Errors Without Breaking the Operation

Freight audit should replay the agreed rate against verified shipment events, route only genuine exceptions, protect payee changes, and pay clean invoices without making carriers finance an internal data problem.

A freight invoice is not a purchase order for a fixed box of goods. The final charge can depend on miles, weight, class, fuel index, stops, free time, equipment, redelivery, reweigh, storage, tolls, or events that were unknown when the load was tendered.

That makes freight audit necessary. It also makes a crude “invoice must equal tender” rule destructive.

An effective freight audit and payment process, or FAP process, does three things at once:

1. pays valid charges accurately and on time;
2. catches duplicates, rating errors, unsupported accessorials, and fraud;
3. turns recurring exceptions into pricing and operating corrections.

The practical rule is:

Audit by replaying the accepted commercial terms against verified shipment facts. Automate clean matches, route material exceptions with reason codes and evidence, and never use silent short payment as the dispute process.

The objective is not to reject the most invoices. It is to make the expected charge reproducible before the invoice arrives, then resolve the remaining differences without stopping capacity or hiding true transportation cost.

Build the audit before tender

Most invoice problems are designed upstream:

• a quote lacks an expiration date;
• the tender changes weight but does not rerate;
• a contract says “fuel per schedule” without identifying the schedule;
• an accessorial has a price but no event definition;
• the BOL carries a different bill-to party;
• a facility does not record arrival and release;
• no one owns approval for additional services;
• multiple systems create different shipment IDs;
• AP accepts remittance changes through ordinary email.

An audit team cannot reconstruct a clean agreement from bad source data at month-end.

Before tender, store a machine-readable expected-cost record:

counterparty and contract
+ accepted rate or tender version
+ linehaul or base rate
+ fuel formula, index, base, date rule, and rounding
+ stops, minimums, class, density, mileage, zone, or weight basis
+ included services and free time
+ accessorial rate, trigger, notice, approval, and evidence rule
+ tax, toll, pass-through, and currency treatment
+ payment and dispute terms
= expected charge architecture

Do not flatten that architecture into one all-in number unless the agreement is genuinely all-in and defines its exceptions. The freight-pricing guide provides the underlying rate model; the audit process should implement it, not reinterpret it.

Use one shipment identity across systems

Every invoice line should connect to a canonical shipment ID and, as applicable:

• BOL and PRO number;
• carrier load or trip number;
• broker load number;
• order and purchase-order references;
• origin and destination;
• equipment or container;
• service dates;
• payer, bill-to, and payee;
• original and corrected invoice numbers.

Identity matching should tolerate controlled formatting differences, not ambiguous shipments. Stripping punctuation from a PRO number can be reasonable. Matching on amount, date, and carrier because the shipment number is absent is a risk decision that should enter an exception queue.

For brokered freight, preserve the two commercial legs. The carrier invoice to the broker and the broker invoice to the shipper are not duplicates simply because they reference the same physical load. The document-control guide explains which record supports each relationship.

Validate the invoice packet before rating

The first audit is structural:

• Is the invoice from the contracted legal party?
• Is the payee and remittance instruction verified?
• Is the invoice number unique for that payee?
• Does it reference a valid, non-canceled shipment?
• Is it a first bill, corrected bill, credit, or balance-due bill?
• Are the required BOL, POD, receipts, logs, or other documents present?
• Do the dates and parties make sense?
• Does the arithmetic add?
• Is the currency explicit?

For covered for-hire motor service, 49 CFR § 373.103 describes freight-bill information including parties, origin, destination, freight description, rating measurement, exact rates, total charges, special-service charges and locations, route, participating carriers, and remittance address. Its regulatory scope should be checked; operationally, the listed fields are a strong baseline for an auditable invoice.

Do not reject a legitimate invoice solely because a customer's preferred attachment filename is wrong. Separate legal, commercial, rating, evidence, and administrative defects, then apply proportional rules.

Run the audit in layers

Layer 1: Identity and duplicate control

Detect:

• same payee and invoice number;
• same shipment, charge code, service date, and amount;
• original invoice resubmitted after payment;
• corrected invoice billed without reversing the original;
• duplicate through both EDI/API and email;
• carrier and factor both seeking payment;
• broker and carrier improperly billing the same payer.

Use more than an exact hash. Two invoices can demand the same payment with different PDF metadata or invoice numbers. Conversely, two valid charges can have the same amount.

Place suspect duplicates on hold before payment, but identify the held transaction to the submitter. A black-box rejection invites resubmission and makes the duplicate problem worse.

Layer 2: Commercial authority

Confirm:

• the applicable master agreement;
• accepted shipment-specific rate or tender;
• incorporated tariff, rules, or schedule and effective version;
• approved amendment;
• correct counterparty;
• contract and rate effective dates;
• lane, equipment, commodity, volume, and service applicability.

The invoice is not allowed to choose its own governing rate. If several records conflict, use the transportation contract and tariff framework and escalate genuine ambiguity.

Layer 3: Rating facts

Validate the variables that drive price:

• origin, destination, zone, lane, or mileage;
• actual equipment;
• shipment date;
• weight, dimensions, density, class, pallets, pieces, or containers;
• fuel index and lookup date;
• distance source and route rule;
• number of stops;
• minimum or deficit-weight logic;
• service level;
• dimensional or oversize thresholds;
• rounding and currency.

Preserve the source for each fact. “System-calculated weight” is not a source if no one can tell whether it came from the BOL, scale, manifest, reweigh, or item master.

Layer 4: Accessorial evidence

An accessorial should pass four tests:

1. Authority: Is the charge and rate permitted?
2. Trigger: Did the defined event occur?
3. Responsibility: Does the agreement allocate it to this payer?
4. Evidence: Was required notice, approval, and support produced?

For detention, compare appointment, arrival, readiness, dock, release, free time, exclusions, and notice. For lumper service, check authorization, receipt, facility, and markup rule. For reweigh or reclassification, retain the inspection or scale record and rerating logic. For redelivery, establish the failed attempt, cause, notice, and new completion.

The detention, demurrage, per diem, and storage guide shows why one generic “delay fee” code is not auditable.

Layer 5: Delivery and exception status

Validate that the billed service reached its defined completion state. Use the proof-of-delivery evidence chain, not merely a signature image.

A missing POD does not prove non-delivery. It means the required evidence gate has not been met. Route it for retrieval or event validation. Likewise, a delivery exception may affect only a line item, customer charge, or claim reserve—not automatically invalidate the entire transportation invoice.

Layer 6: Payee and payment security

Treat a remittance change as a high-risk master-data event. Before changing bank, factoring, or address information:

• verify through an independently sourced contact;
• use dual approval;
• separate vendor-master access from invoice approval and payment release;
• validate carrier, broker, and factoring identities against existing records;
• preserve the request and verification;
• apply a risk-based hold or callback;
• notify the established counterparty through a known channel.

Do not trust the phone number or link contained only in the change request. The double-brokering and cargo-theft controls apply identity discipline to the physical load; payment needs the same discipline.

Make exceptions precise and owned

An exception queue should say what failed and what would resolve it.

Give each exception:

• reason code;
• material amount;
• disputed and undisputed portions;
• owner;
• created date;
• response due date;
• required evidence;
• communication history;
• current state;
• final resolution and root cause.

Avoid emailing “invoice incorrect.” State, for example: “Detention line 3 is held because the agreed two-hour free period ends at 14:12 and the submitted log shows release at 14:05. Provide a corrected invoice or evidence supporting a different release time.”

Pay clean charges without surrendering the dispute

If the contract and system permit, separate undisputed charges from disputed ones. That can keep valid carrier revenue moving while a material accessorial or rating issue is resolved. But do not assume partial payment, setoff, netting, or short payment is authorized. Check the agreement and applicable law.

A sound workflow is:

1. receive and timestamp the invoice;
2. validate structure, identity, and payee;
3. match the shipment and accepted commercial record;
4. recalculate expected charges;
5. validate event evidence;
6. auto-approve within defined tolerances;
7. route material exceptions;
8. communicate the reason and required cure;
9. approve, reject, credit, or correct through a traceable decision;
10. release payment with remittance detail;
11. preserve the audit result;
12. feed recurring causes upstream.

Tolerance is a management control, not a secret rate amendment. Define it by charge type and risk. A small rounding variance may auto-pass; a small duplicate should not. A bank-account mismatch should not pass because the invoice amount is low.

Understand the legal clocks without turning them into universal policy

Federal motor billing rules are scoped and can interact with negotiated contracts and waivers.

As reviewed July 27, 2026, 49 CFR Part 377 applies its credit rules to specified for-hire, non-exempt motor carriers and household-goods freight forwarders, subject to exceptions. It provides a 15-day credit period after presentation of the freight bill unless a qualifying tariff establishes a different period, capped at 30 calendar days under that rule. It also contains freight-bill presentation and notice provisions. That is not a universal declaration that every broker, shipper, exempt carrier, ocean provider, warehouse, or negotiated freight contract is legally “net 15.”

49 U.S.C. § 13710 gives a shipper a right, in its stated motor-carrier scope, to request the rate, classification, rules, and practices supporting a rate. Its billing-dispute provision says a covered motor carrier seeking contested additional charges must issue the additional bill within 180 days after receipt of the original bill, and a shipper seeking the described Board determination must contest a bill within 180 days after receipt. The text excludes household goods and noncontiguous domestic trade from portions of that procedure.

Do not turn that 180-day provision into the company's only deadline. Contracts may require much faster invoice submission, exception notice, audit challenge, or dispute escalation. Civil actions and administrative complaints can have separate statutory limitation periods; 49 U.S.C. § 14705 contains mode- and remedy-specific clocks for covered carrier charge and overcharge matters. Calendar the actual contract and legal regime.

Recover overpayments through a controlled claim

Post-payment audit can find:

• duplicates;
• wrong rate or fuel;
• incorrect class, weight, zone, or mileage;
• services never performed;
• missed contract discounts;
• accessorials lacking a trigger;
• unapplied credits;
• overcollections.

For covered motor-carrier matters, 49 CFR Part 378 establishes procedures for processing overcharge, duplicate-payment, and overcollection claims. Section 378.3 directs that a written claim be filed with the carrier that collected the charges; the part addresses documentation, investigation, records, acknowledgment, and disposition. Section 378.9 includes procedures for unidentified payments and certain discovered overpayments.

Operationally, a recovery claim should identify:

• claimant and collecting carrier;
• shipment and invoice;
• payment date and reference;
• amount paid, amount supported, and amount claimed;
• contract, rate, tariff, or rule basis;
• calculation;
• documents;
• filing and limitation dates;
• requested disposition.

Do not automatically deduct an alleged overpayment from an unrelated current invoice. Setoff and recoupment can raise contractual and legal issues, and unannounced deductions corrupt both parties' ledgers.

Measure more than savings

“Audit savings” can be inflated by comparing invoices with bad accruals or by rejecting valid charges that later return.

Track:

• clean-invoice rate;
• first-pass match rate;
• invoice-to-approval and invoice-to-payment time;
• exception age by reason and owner;
• corrected-invoice cycle time;
• duplicate attempts and prevented duplicate payments;
• actual recovered overpayments;
• valid charges initially rejected;
• late fees, lost discounts, and carrier service holds;
• accrual-to-actual variance;
• accessorial cost by facility and cause;
• manual touches per invoice;
• payee-change exceptions;
• repeat defect by carrier, lane, facility, customer, and contract.

Separate verified prevention or recovery from theoretical variance. A charge held for review is not a saving. A negotiated credit is not recovered until it is posted or paid.

Operating takeaway

Freight audit is a shipment replay:

1. Who contracted with whom?
2. Which rate and rules were accepted?
3. Which shipment facts drive the calculation?
4. Which additional events occurred and who caused them?
5. Does the evidence meet the agreed rule?
6. Is the payee legitimate and the charge unique?
7. What is approved, disputed, corrected, credited, or paid?

Build the expected charge at tender. Preserve execution facts as they occur. Automate genuine clean matches. Give every exception a reason, owner, evidence requirement, and clock. Then use the pattern of exceptions to fix contracts, facility processes, integrations, and rate data.

The best FAP operation is nearly invisible to a carrier with a correct invoice—and extremely specific when something is wrong.

Anchor settlement to the wider operator's map of U.S. freight handoffs.

This article provides operational education, not legal, tax, or accounting advice. Payment responsibility, credit rules, dispute periods, setoff rights, tariff treatment, and limitation periods vary by contract, mode, role, jurisdiction, and facts. Obtain qualified advice for material or contested matters.

Sources and further reading

• 49 CFR Part 373: Motor-carrier bills of lading, freight bills, and records
• 49 CFR Part 377: Payment of transportation charges
• 49 CFR Part 378: Motor overcharge, duplicate-payment, and overcollection claims
• 49 U.S.C. § 13710: Additional motor-carrier billing and collecting practices
• 49 U.S.C. § 14705: Limitation periods for covered carrier charge matters
• 49 CFR Part 371: Broker records and duties
• NMFTA Digital Standards Development Council: Freight API standards