When Freight and Shipping Charges Break Your 3-Way Match: A Controller’s Guide

It’s 4pm on a Thursday. Your AP manager pings you: “We’ve got 23 vendor invoices stuck in the match queue.” You pull up the list. Same story as last month. The invoices are from vendors you trust, for goods you ordered, at prices you agreed to. The POs are clean. The receipts are confirmed. So what’s the problem?

‍

Freight. Shipping surcharges. Delivery fees. Line items that appear on the invoice but were never on the purchase order—because nobody knew what they’d be until the truck showed up. And now your 3 way matching in accounts payable process has flagged every single one as an exception, and your team is spending the afternoon calling vendors and manually clearing matches instead of closing the books.

‍

If this sounds familiar, you’re not alone. Freight and shipping charges are the single most common reason 3 way match processes break down in mid-market AP departments—and almost nobody talks about how to fix it. This guide does.

‍

‍

What Is 3-Way Matching and Why Does It Exist?

Before we get into the freight problem, let’s make sure we’re on the same page about what 3 way matching in accounts payable actually does—and why your company can’t afford to skip it.

‍

The 3 way matching process compares three documents match before any payment goes out: the purchase order po (what you ordered), the goods receipt (what you received), and the supplier invoices (what the vendor is charging you). When all three align—same quantities, same prices, same line item descriptions—the invoice is approved for payment. When they don’t, it’s flagged as an exception.

‍

The purpose is straightforward: 3 way matching in accounts payable prevents your company from paying for things it didn’t order, didn’t receive, or is being overcharged for. It catches fraudulent invoice attempts. It catches human error. It creates the order receipt trail your auditors will ask for. For finance teams serious about controls, it’s non-negotiable.

‍

The problem isn’t the process itself—it’s what happens when reality doesn’t fit the process. And nothing breaks the process faster than freight.

‍

‍

Why Freight and Shipping Charges Break the 3-Way Match 

Here’s the fundamental problem: when your procurement team creates a purchase order, they know the quantity, the unit price, and the vendor. What they often don’t know—and can’t predict—is the exact cost of getting those goods from the vendor’s warehouse to your dock. Shipping charges depend on carrier rates, fuel surcharges, weight, distance, and sometimes even the weather. So the PO ships without a freight line item. The goods arrive. And then the invoice shows up with a $847 freight charge that has no corresponding line on the purchase order po.

‍

Your 3 way matching system does exactly what it’s designed to do: it flags the mismatch. The invoice has a line the PO doesn’t. Exception. Held for review. And now someone on your ap teams has to stop what they’re doing and manually investigate a charge that everyone already knows is legitimate.

‍

Multiply that by dozens of invoices a week and you start to understand why controllers call freight “the sand in the gears” of invoice matching.

‍

The Four Most Common Freight Exception Scenarios 

Not all freight mismatches are the same. Understanding the specific scenario helps determine the right fix. Here are the four patterns that ap teams encounter most often in the 3 way matching process.

‍

‍

Scenario 1: Freight as a Standalone Line on the Invoice 

This is the most common scenario. The PO covers the goods—100 units of Widget A at $50 each. The invoice arrives with the same 100 units at $50 each, plus a separate line for “Freight: $375.” The invoice matching system can’t find a PO line to match the freight charge against, so the entire invoice is flagged. The goods lines match perfectly. But the orphan freight line breaks the whole thing.

‍

Scenario 2: Freight Bundled Into the Unit Price 

Some vendors don’t break out freight separately—they add it to the unit price. Your PO says $50 per unit, but the invoice says $52.40 per unit because the vendor rolled shipping charges into the cost. Now you have a rate mismatch on every single line of the invoice. The three way invoice matching system flags it as a pricing discrepancy, even though the total difference is just the cost of shipping.

‍

Scenario 3: Partial Shipments With Split Freight 

You ordered 500 units on one PO. The vendor ships 300 now and 200 later. Each shipment includes its own freight charge. Now you have two invoices, each with a partial goods receipt and a different freight amount, both referencing the same PO. Your ap process has to reconcile partial quantities against partial deliveries against freight charges that didn’t exist when the PO was created.

‍

Scenario 4: Freight Surcharges After Delivery 

The goods arrive. The initial invoice matches. Everyone’s happy. Then a second invoice shows up two weeks later: a fuel surcharge, a liftgate fee, or a residential delivery upcharge from the carrier. There’s no PO for it. There’s no receipt. It’s a legitimate charge with no documents match path in your 3 way matching in accounts payable system. Your AP team either creates a dummy PO to clear it—introducing audit risk—or manually overrides the match, which defeats the purpose of having controls in the first place.

‍

‍

‍

How Controllers Handle Freight Exceptions Today (And Why It’s Not Working) 

If you’re a controller reading this, you probably already have a workaround. Most finance teams do. The problem is that every common workaround creates its own set of risks.

‍

The “Manual Override” Approach

AP staff manually clear the exception, adding a note that says something like “freight charge — approved per [manager name].” This works in the moment but creates audit trail gaps. When auditors ask why 40% of your invoices were manually overridden, the answer “freight” doesn’t inspire confidence. Manual overrides also mask other legitimate discrepancies that should have been caught.

‍

The “Dummy PO” Approach 

Some teams create blanket POs for freight—a standing purchase order with an estimated annual freight budget. Invoices are matched against this blanket PO to clear the exception. The problem: blanket POs are notoriously hard to control. They tend to become catch-all buckets where all kinds of charges get parked, and they make it nearly impossible to track freight costs back to specific orders. Your ap process looks clean, but your cost allocation is a mess.

‍

The “Add Freight to Every PO” Approach 

The most disciplined teams add an estimated freight line to every purchase order at creation. If the actual charge comes in close, the match passes. But freight is inherently variable—estimates are frequently wrong, which means you’re either setting tolerance threshold ranges so wide they defeat the purpose of matching, or you’re still getting flagged exceptions when the estimate is off by more than a few percent.

None of these approaches actually solve the root problem: the 3 way matching process wasn’t designed to handle charges that don’t appear on the original PO. To fix that, you need a system that understands the difference between a suspicious charge and a predictable one.

‍

What a Good Freight Exception Solution Actually Looks Like 

The best ap automation solutions don’t just flag mismatches—they know which mismatches matter. When it comes to freight and shipping charges, a well-designed invoice matching system should be able to:

‍

• Recognize standalone freight lines: Identify freight, tax, and delivery charges as accepted standalone lines that don’t need a corresponding PO line—instead of flagging them as exceptions.
• Apply configurable tolerance threshold rules: Allow small variances (a fixed dollar amount or a percentage) to pass through automatically without manual review, so a $12 freight difference on a $8,000 invoice doesn’t hold up payment.
• Route true exceptions to the right person: When freight charges fall outside tolerance or look unusual, route them to the right stakeholder—procurement, receiving, or a manager—with full context, not just a generic “mismatch” alert.
• Learn from history: If you receive a $200–$300 freight charge from the same carrier every month, the system should learn that pattern and stop treating it as an exception.
• Maintain a complete audit trail: Every match, mismatch, tolerance pass, and manual resolution should be logged automatically—so when auditors ask, you have the answer in seconds, not hours.

‍

This isn’t theoretical. This is exactly how Centime’s PO matching handles freight exceptions—and it’s the reason mid-market finance teams are replacing their manual override workflows with ap automation that actually understands how freight works in the real world.

‍

How Centime Handles Freight in 3-Way Matching 

Centime is a NetSuite-certified AP automation SuiteApp with AI-powered po matching built directly into your ERP. Here’s how it solves each of the freight scenarios described above—without custom scripting, dummy POs, or manual workarounds.

‍

Standalone Line Acceptance 

When a vendor invoice includes a freight or tax charge that doesn’t appear on the PO, Centime’s AI doesn’t immediately flag it as an exception. Instead, AP users can mark these as accepted standalone lines—a purpose-built feature for charges like freight, shipping, and tax that are common, expected, and don’t need a PO line to justify them. The goods lines are matched normally through Centime’s AI-powered line item linking. The freight line is acknowledged and logged. The invoice moves forward.

‍

Configurable Tolerance Thresholds 

For invoices where freight is bundled into the unit price, Centime lets finance teams set configurable tolerance threshold rules—either as a fixed dollar amount or a percentage—for rate, quantity, and amount variances. If a vendor’s unit price is $52.40 instead of $50.00 and that falls within your configured tolerance, the invoice passes through automatically. No exception. No manual review. No AP clerk spending fifteen minutes on a $2.40-per-unit difference on a legitimate payment process. Invoices that fall outside tolerance are flagged for review with clear labels: Rate Mismatch, Quantity Mismatch, or Amount Mismatch—so your team sees exactly what’s off and can resolve it fast.

‍

‍

AI-Powered Matching That Learns 

Centime’s matching engine uses AI that continuously learns from historical transactions. If vendor X consistently adds a $250–$350 freight charge on every order, the system recognizes the pattern and stops treating it as a surprise. Over time, this means fewer false exceptions, faster processing, and less manual intervention—what the industry calls straight-through processing. Centime customers report up to 70% reduction in invoice matching time after implementation.

‍

Built-In Exception Resolution 

When a freight charge genuinely needs review—maybe it’s unusually high, or from a new vendor—Centime routes it directly to the right stakeholder with full context. Resolution options include Accept (approve and proceed), Await Receipt (hold for delivery confirmation), Dispute (send back to the vendor), or Reject. Every action is logged with timestamps and approver details, creating a complete audit trail without manual tracking. Your supplier relationships stay intact because disputes are handled quickly and professionally, not through weeks of email chains.

‍

‍

Manual Freight Handling vs. Centime: A Quick Comparison 

Here’s how the common workarounds stack up against a purpose-built solution for handling freight in 3 way matching in accounts payable:

‍

‍

How to Get Started With Better Freight Matching 

If your ap teams are spending hours every week clearing freight exceptions manually, here’s the path to fixing it—whether you choose Centime or another ap automation platform.

‍

Step 1: Quantify Your Freight Exception Volume 

Pull a report of all invoices that were manually overridden or exception-cleared in the last quarter. How many were freight-related? For most mid-market AP departments, the answer is 30–50% of all exceptions. That number tells you exactly how much time and risk you’re carrying. If your 3 way matching process is flagging freight on half your invoices, you don’t have a matching problem—you have a freight problem.

‍

Step 2: Evaluate Your Current Workarounds 

Are you using manual overrides, dummy POs, or estimated freight lines? Each workaround carries specific risks: audit exposure, cost allocation inaccuracy, or tolerance ranges so wide they defeat matching controls. Understanding which risks you’re currently carrying helps you evaluate what a better solution needs to do.

‍

Step 3: Look for Standalone Line + Tolerance Threshold Capabilities 

When evaluating ap automation platforms, the two features that matter most for freight are standalone line acceptance and configurable tolerance threshold rules. If a vendor’s platform can’t handle a freight charge without creating a dummy PO or manually overriding the match, it’s going to recreate the same problems you already have. Centime handles both natively, with AI-powered matching that gets smarter over time. See how it works in our PO matching feature overview.

‍

For a deeper look at how 3 way match fits into the broader AP automation landscape, see our guide to 3-way matching: the secret to stopping duplicate payments and fraud. And for teams also dealing with invoice approval bottlenecks, our invoice coding best practices guide covers how coding accuracy and matching invoices to purchase orders work together to reduce exceptions across the board.

‍

‍

‍

‍