Freight Audit and Payment (FAP), Explained

What freight audit and payment (FAP) means, how FAP providers use EDI 210/820 to catch billing errors, and how FAP differs from a TMS.

Share

What is freight audit and payment?

Freight audit and payment (FAP) is the outsourced or automated process of checking every carrier freight invoice against the contracted rate and the shipment record before money moves, then releasing payment and feeding the cleaned cost data back into the business. It is the process of verifying that every carrier invoice matches the agreed rate, contract terms, and shipment documentation before the bill gets paid, and then executing payment to the carrier.

That distinction matters because people often treat FAP as a feature inside a bigger platform. It isn't, really. FAP is a two-part system: audit, meaning verifying invoice accuracy, and payment, meaning releasing approved funds. Whether a human team runs that process, a piece of software runs it, or a third-party provider like Cass Information Systems or Trax Technologies runs it on your behalf, FAP describes the function, not a specific product category.

What an FAP provider actually checks

An FAP provider matches three things on every freight bill: the contracted rate for that lane and mode, the shipment record showing what actually moved, and the paperwork backing up any accessorial charge. Before payment, each invoice is matched against the contracted rate for that lane and service, the shipment record showing what actually moved, and the documentation supporting any accessorial, and anything that doesn't line up gets flagged before the money leaves the building.

In practice that audit catches the usual suspects: duplicate invoices from carriers that bill twice on the same PRO number, fuel surcharges calculated off the wrong index, LTL weight and freight-class discrepancies after reweigh, and detention or liftgate charges with no supporting proof of service. Cass, for one, builds this directly into its freight payment service, covering rate management, EDI setup, exception handling, accruals and GL coding, and carrier support as one bundled workflow rather than separate tools bolted together. The GL coding step matters more than people give it credit for: a correct invoice amount sitting in the wrong cost center still produces a bad month-end report.

The reason this is worth outsourcing or automating rather than eyeballing in AP: industry estimates put invoice error rates at 5 to 10% of freight bills, with most of those errors favoring the carrier. At 100+ trading partners and a few thousand invoices a month, that's not a rounding error, it's a line item.

Where EDI fits into the FAP workflow

FAP engines don't generate their own shipment data. They consume carrier EDI transactions as audit input and then issue a single EDI transaction back to confirm payment. Four inbound transaction sets do most of the work, each tied to a transport mode:

  • EDI 210 – the Motor Carrier Freight Details and Invoice, typically sent from the carrier to a shipper, consignee, or third-party payment center for payment of freight charges, with one 210 per shipment carrying the itemized charge detail an audit engine needs.
  • EDI 110 – Air Freight Details and Invoice, the air-mode equivalent of the 210, used for air cargo billing.
  • EDI 404 – Rail Carrier Shipment Information, which carries waybill and rating detail that FAP platforms ingest to validate the corresponding rail invoice against what was actually moved.
  • EDI 310 – Freight Receipt and Invoice (Ocean), the ocean-mode billing transaction FAP engines audit against the booking and contracted ocean tariff.

Before any of that reaches the audit engine, standard acknowledgment transactions (997 or 999) confirm the inbound file was syntactically valid and received, a housekeeping step that exists on this blog's EDI 210 and EDIFACT coverage already. Once the audit clears, the FAP provider issues one outbound transaction: the EDI 820 Payment Order/Remittance Advice. In freight specifically, the 820's remittance detail against EDI 210 freight bills is what keeps carrier AR teams from chasing paper, telling the carrier exactly which invoices were paid, at what amount, and what, if anything, was adjusted.

FAP vs. TMS vs. EDI VAN — don't confuse these three

These three sit next to each other in the same transportation stack, which is exactly why people mix them up. A TMS executes the move. A VAN delivers the document. FAP judges whether the invoice for that move is correct and pays it.

A transportation management system handles tendering, routing, and track-and-trace, the execution layer that decides how freight gets from A to B. Platforms like MercuryGate, Descartes, Transporeon, Uber Freight, and Cargoson sit here, and many of them generate the contracted rate data an FAP audit checks against. But a TMS rating engine and an FAP rating engine aren't built for the same job: a best-of-breed freight audit and payment solution generates high-volume, touchless throughput and a small, manageable number of exceptions, which is a different engineering problem than planning a load. Where transportation spend management overlaps with execution planning, a tool like Cargoson is typically feeding rate and shipment data into the audit rather than performing the audit itself. An EDI VAN, meanwhile, does none of this judgment work. A VAN is essentially a mailbox: your trading partner sends an EDI document to the VAN, and the VAN holds it until your system picks it up, and critically, the VAN doesn't validate the data, doesn't integrate with your ERP, and doesn't handle non-EDI orders. A VAN can route a 210 with a wrong fuel surcharge just as reliably as a correct one. It has no opinion on whether the invoice is right.

LayerPrimary jobTypical playersJudges invoice accuracy?
TMSPlan, tender, track shipmentsMercuryGate, Descartes, Transporeon, CargosonNo
EDI VANRoute the EDI document between partnersGeneric VAN/network providersNo
FAP providerAudit the invoice, then pay itCass Information Systems, Trax Technologies, nVision GlobalYes

A worked example

The Hershey Company's relationship with Cass is a useful real-world case because it's been running for decades and is well documented. Hershey's 60 to 80 freight carriers rely on Cass for accurate, timely information about the status of payment, after Hershey outsourced its freight audit and payment function rather than running it internally. Part of that engagement involves carrier onboarding onto electronic billing: Cass works with carriers to convert them to EDI billing, and nearly all of Hershey's U.S.-based carriers now use EDI, while some Canadian carriers were still being converted. In that model, each carrier's 210 lands at Cass, gets matched against Hershey's contracted rates, and any flagged line is held pending resolution before the approved amount is paid and the 820 goes back to the carrier. DuPont runs a similar model with Cass and even tracks EDI percentage as a formal metric, since a higher share of invoices arriving electronically improves audit quality and accrual accuracy. Neither company's AP team is matching freight bills by hand. That's the point of FAP.

Build vs. outsource: when a company needs an FAP provider

Manual, invoice-by-invoice matching works fine at low volume with a handful of carriers. It stops working once invoice counts climb and rate structures multiply across lanes, modes, and accessorials. In-house audit makes sense at low volume or with a small, stable carrier base, but it costs staff time and depends on someone maintaining rate tables carefully, which is exactly the maintenance burden that grows fastest as a supplier or carrier network scales past a few hundred invoices a month. Outsourced providers price differently than you'd expect from a software vendor. Enterprise FAP providers typically price per invoice or as a percentage of freight spend, which is worth comparing directly against the fully loaded cost of an internal team doing EDI setup, exception handling, and carrier payment inquiries, the same cost categories that show up in any "build an EDI team in-house" analysis.

FAQ

Is freight audit and payment the same as a TMS? No. A TMS plans and executes the shipment; FAP audits and pays the resulting invoice. A TMS can theoretically be used to manage audit and payment and eliminate the need for a freight payment provider, but that's a scope expansion, not what most TMS platforms are built to optimize for.

Do I need EDI to use an FAP provider? Not strictly, but it's the stated goal of most providers, since carriers submit electronic freight bills through EDI or APIs and EDI volume directly improves audit speed and accuracy.

How much do FAP providers typically charge? Pricing is usually per invoice or a percentage of total freight spend, not a flat software license.

What's the difference between freight audit and regular accounts payable? Regular AP assumes the invoice is correct and pays it. Freight audit assumes it might not be and checks first, which is why every day an invoice sits in audit adds a day to days-to-bill and, downstream, to DSO for 3PLs managing that cycle.

Does an FAP provider replace my EDI VAN? No. The VAN still routes the 210 and 820 documents between you and the carrier. FAP decides what happens to the numbers inside them.