An invoice audit is a line-level review of supplier bills that confirms every charge, rate, and tax matches the contract before finance approves payment.
Key Takeaways
- The review checks each line on a supplier bill against the rate agreement, the shipment or service record, and the applicable tax rule, then routes clean charges to payment and disputed charges back to the vendor.
- 39% of invoices contain errors, and processing one bill manually costs an average of $15 and takes 14.6 days.
- Timing decides the economics. A pre-payment check stops a bad charge before cash leaves the account. A post-payment check recovers money already gone, and the recovery effort often costs more than the charge on small items.
- Freight audit, parcel audit, and 3PL audit are three different services covering three different bill types. Buying one does not cover the other two.
- FreightOptics recovers 4 to 8% on freight audit and up to 9% on parcel, and exports validated charges as AP-feed files for accrual and coding.
Most finance teams approve carrier and warehouse bills without ever seeing the line items behind the total. The invoice arrives as a PDF, the amount looks close to last month, and the payment clears. Nearly 4 in 10 bills carry an error, which means a meaningful share of what your accounts payable team approves this quarter is wrong. This article defines the review that catches those errors: what it is, who runs it, where it sits inside the accounts payable cycle, how the timing models differ, and which error categories it exists to find. It is a primer, not a procedure.
The Plain Definition, and Who Actually Runs It
An audit of your invoices is a structured comparison. On one side sits the bill a vendor submitted. On the other sits the contract you signed, the service that was actually performed, and the tax treatment that applies. Where the two sides disagree, the review produces an exception.
Ownership splits across three roles, and confusing them is where programs stall:
- Accounts payable executes. AP captures the invoice, runs the match, and holds the exception before payment releases.
- The controller or VP Finance sets the standard. Finance decides what tolerance triggers a hold, what evidence a dispute needs, and how validated cost flows into accruals and general ledger coding.
- Logistics and procurement consume the output. Logistics works the exception with the carrier or warehouse provider. Procurement carries the billing history into the next contract negotiation.
Many shippers assign execution to a third-party audit provider rather than staffing it internally, because the volume of line-level checking exceeds what an AP team of three or four people can absorb alongside close.
Research puts the manual cost at $15 per bill and 14.6 days of cycle time.[1] Those figures compound quickly for a mid-market shipper handling hundreds of freight and warehouse bills each month.
Where the Check Sits Inside Accounts Payable
This is not a separate department or an annual event. It is a control embedded in the payables cycle, and it touches five stages.
| AP stage | What the review contributes | Who typically owns it |
|---|---|---|
| Invoice receipt | Line items are extracted from the PDF or EDI feed into structured records that can be compared | AP or the audit provider |
| Contract match | Each charge is tested against the negotiated rate, surcharge schedule, and service record | AP analyst or the audit provider |
| Exception handling | Disputed charges are grouped and routed to the carrier or provider for resolution | Logistics, with finance approval |
| Approval and payment | Only validated charges release; held charges stay out of the payment run | AP, with controller sign-off |
| Accrual and close | Audited cost, not billed cost, feeds accruals and GL coding | Controller |
| Contract renewal | Billing history and dispute patterns become negotiation evidence | Procurement |
The last two rows are the ones finance teams underweight. When accruals are built on billed amounts rather than validated amounts, every recovered dollar later shows up as a reconciling item at close. When a contract comes up for renewal and nobody can produce twelve months of charge-level history, the negotiation runs on assertion instead of evidence.
Two Timing Models, and Why the Choice Is Financial
Every program picks a point in the cash cycle. That choice determines what the review can accomplish.
| Consideration | Pre-payment review | Post-payment review |
|---|---|---|
| When it runs | Before the invoice enters the payment run | After the payment has cleared |
| What it produces | A held charge and a corrected invoice | A claim, a credit, or a refund |
| Cash effect | The overcharge never leaves the account | Cash is out until the vendor issues credit |
| Effort to resolve | One exception, one conversation | Dispute workflow, follow-up, and vendor escalation |
| Practical limit | Can delay payment if exception volume outruns the team | Small charges get abandoned because recovery costs more than the charge |
| Best fit | High-volume, high-error-rate billing such as parcel and warehouse | Historical spend, newly onboarded carriers, contract disputes already in motion |
Healthcare billing solved this timing problem decades ago. Claims teams scrub for errors before submission, at the point where a correction costs nothing. Freight and warehouse billing runs the opposite way: the bill arrives, gets approved, and only then gets examined, which inverts the cost curve. Moving validation earlier in the workflow means anomalies surface while you still hold the leverage of an unpaid invoice.
The trust problem is real and it is not unique to logistics. In medical billing, 44 percent of adults reported they did not pay a bill in full, or paid only part of it, because they were not sure the bill was accurate.[2] Complex rate tables produce the same doubt in freight. The difference is that a shipper with a validation process can act on the doubt instead of absorbing it.
Freight Audit, Parcel Audit, and 3PL Audit Are Not the Same Service
This distinction gets blurred constantly, and the cost of blurring it is a coverage gap nobody notices until year end. Three different bill types, three different rate structures, three different error profiles.
| Service | Bills it covers | Errors it is built to find | What it does not touch |
|---|---|---|---|
| Freight audit | LTL (Less Than Truckload) and FTL (Full Truckload) carrier invoices | Rate variance against the contracted tariff, fuel surcharge tier errors, unauthorized accessorials, duplicate bills of lading, reweigh and reclass disputes | Small package billing, warehouse and fulfillment fees |
| Parcel audit | Small package carrier invoices, ground and express | Dimensional weight miscalculation, service failure refunds, residential and address correction surcharges, incorrect zone assignment | LTL rate tables, warehouse storage and handling |
| 3PL audit | Warehouse and fulfillment provider invoices | Pick and pack charges, storage overbilling, supplies, marked-up rebills, incorrect minimums, charge codes with no contractual basis | Carrier transportation billing of any mode |
A parcel program will not read a warehouse invoice. A freight program will not catch a dimensional weight error on a small package. FreightOptics runs freight audit and payment, parcel spend management, and 3PL audit as separate services for exactly this reason, because the rate logic behind each one is different.
Warehouse invoices are the most commonly skipped of the three. They arrive as dense PDFs with no structured line detail, so hand-auditing gets deferred and then dropped, and overbilled storage and marked-up rebills accumulate unchallenged.
The Error Categories the Review Exists to Catch
Billing errors are not random. They cluster in the same fields, for the same structural reasons, across nearly every shipper.
| Error category | How it appears on the bill | Why it survives a quick approval |
|---|---|---|
| Rate variance | The billed rate differs from the contracted rate for that lane or service | Nobody has the tariff open next to the invoice |
| Duplicate billing | The same shipment or storage period is billed twice, often across two billing cycles | The second bill arrives weeks later with a different invoice number |
| Unauthorized accessorial | A charge code appears with no basis in the rate agreement | The code looks legitimate and the amount is small |
| Dimensional weight | Billed weight exceeds actual weight because of a dimension or divisor error | The calculation is invisible on the invoice summary |
| Fuel surcharge tier | The wrong index tier is applied for the billing week | Tiers change weekly and are rarely re-checked |
| Tax and exemption | Tax is applied to an exempt freight charge, or the wrong jurisdiction rate is used | Tax lines are assumed correct by default |
| Storage minimums and rebills | A monthly minimum is charged incorrectly, or a pass-through cost carries an undisclosed markup | The underlying cost is not visible to the shipper |
| Vendor identity | The bill-to entity, remit-to address, or bank detail does not match the approved vendor record | Math-only checks never look at this field |
That last row belongs to a different problem than the seven above it, and it deserves its own section.
Checking the Math Does Not Catch Fraud
Line-item arithmetic finds billing errors. It does not find a vendor that should not exist.
Ghost vendor fraud has moved well past invented suppliers. Fraudsters now blend real identity data with fabricated details to create vendors that pass surface-level checks, complete with a registered address, a plausible trading history, and professionally produced invoices.[3] The tell is rarely in the document. It is in whether a human decision-maker had to approve that vendor record before any payment could route to it.[3]
Nearly half of all fraud cases are enabled by a lack of controls, or by the ability to override the controls that exist.[3] A process that stops at line-item math leaves vendor identity, payment routing, and contract linkage unchecked. For a finance team, that gap is not an operational annoyance. It is an unmitigated financial risk sitting inside the payment run.
Sampling Leaves a Door Open
Most programs review a fraction of total invoice volume, usually the largest bills or a random sample. Anyone who understands that a review covers a minority of invoices can structure charges to stay under the threshold that triggers manual attention. Sampling cannot detect that pattern, by design.
Full coverage changes the calculation rather than just raising the catch rate. When every bill is checked, no safe threshold exists. Over the last year, AI-enabled fraud attempts surged by more than 1,200%, which means controls built around manual sampling are already behind.[3] The same evolution applies to ordinary error: identity data blended with fabricated details passes exactly the kind of surface check that a sampled program relies on.[3]
Coverage across every invoice also surfaces patterns that no single bill reveals. Duplicate charges that repeat across carriers, a remit-to address that changed without a contract amendment, tax applied on lanes where none is owed. IRIS, the FreightOptics AI agent, answers those questions in plain language against the full invoice record, so a controller can check a suspicion without waiting on an analyst to build a report.
What Finance Gets Out of It
The recovery number is the headline. It is not the most valuable part.
Accruals stop drifting. When validated cost feeds the accrual instead of billed cost, the reconciling items at month-end close shrink. Recovered credits stop arriving as surprises in the following period.
Coding gets consistent. Charges arrive grouped by type and by facility, so the same accessorial lands in the same GL account every month instead of following whichever AP clerk touched it.
Margin math becomes defensible. Landed cost per order rests on charges that were tested against a contract, which matters when the CFO asks why fulfillment cost per unit moved three points.
The data trail survives scrutiny. Every held charge, dispute, and credit carries a record of what was compared and what was decided. That is what an external auditor, a compliance review, or a contract renewal actually needs.
39% of invoices contain errors.[1] FreightOptics recovers 4 to 8% on freight audit and up to 9% on parcel, and exports validated charges as AP-feed files in CSV, XLSX, or PDF over SFTP or email, so the numbers finance accrues against are the audited ones.
Conclusion
An audit of your invoices is a financial control, not a logistics chore. It confirms that each charge matches a contract, catches the error categories that cluster in rate, surcharge, tax, and minimum fields, and produces the record that accruals, close, and contract renewals depend on. The timing decision matters more than the tooling decision: catching a charge before payment costs one conversation, and recovering it afterward costs a workflow. Freight, parcel, and warehouse bills each need their own review, because the rate logic behind each one is different. With the definition settled, the next question is operational, which is what a line-by-line review actually looks like when you sit down to run one.
Start With the Invoices Nobody Audits
Freight and parcel invoices get reviewed far more often than warehouse invoices, and warehouse invoices are the harder read. FreightOptics 3PL Audit pulls the line items out of the PDF, checks each one against the rate agreement, and surfaces incorrect minimums and marked-up rebills. See what a first 3PL audit surfaces
Frequently Asked Questions
What counts as a red flag on an invoice?
Any charge that does not match the contracted rate, the service level, or the shipment and service record. The common ones are duplicate bills, accessorial codes with no contractual basis, dimensional weight overcharges, misapplied fuel surcharge tiers, and storage minimums billed against the wrong period. A changed remit-to address with no corresponding contract amendment is the flag that finance teams miss most often.
How long does an invoice review take?
A manual pass stretches across days or weeks depending on volume and carrier complexity. An automated program runs continuously against every bill as it arrives. FreightOptics implementation takes 4 to 6 weeks, and parcel clients typically see the first recoveries within 30 days.
Does being audited mean something is wrong?
No. This is a routine financial control, the same category as a bank reconciliation. It checks whether invoices match contracts, whether coding is consistent, and whether charges are legitimate. Problems surface only where bills have gone unchecked long enough for errors to accumulate.
Can a company fail a compliance audit over invoices?
Yes. A compliance review can find that invoices were approved without matching contract terms, that GL coding was inconsistent across periods, or that carriers billed outside agreed lanes and modes. The failure is in the accounts payable process, not in any single invoice, and it exposes the business to both overpayment and fraud.
Do we still need this if our carriers are reliable?
Yes. Error rates in carrier and warehouse billing reflect rate table complexity rather than vendor intent. Fuel tiers change weekly, dimensional divisors change by contract, and warehouse minimums depend on volume thresholds that shift month to month. Reliable partners still send incorrect bills.
Sources Cited
- “The Most Shocking Accounts Payable Stats.” ascendsoftware.com, https://www.ascendsoftware.com/blog/the-most-shocking-accounts-payable-stats.
- “Issue Spotlight: Medical Billing and Collections Among Older Americans | Consumer Financial Protection Bureau.” Consumer Financial Protection Bureau, https://www.consumerfinance.gov/data-research/research-reports/issue-spotlight-medical-billing-and-collections-among-older-americans/.
- “Accounts payable fraud schemes: How to spot and stop them.” blog.approvalmax.com, https://blog.approvalmax.com/accounts-payable-fraud-schemes.
