Wiki/Invoice exceptions/
Tax and freight discrepancies

Tax and freight discrepancies

Invoice exceptions
·
2 min read
·
Updated July 2026
Joshua Kurian
Joshua Kurian
On this page

A tax or freight discrepancy is raised when the tax, freight, or other charges on an invoice do not reconcile with what the order or the tax rules expect. The amount for the goods may be correct while the invoice still fails, because the add-on charges do not line up. It is a common and easily missed exception.

These charges are awkward because they often are not on the purchase order at all, so there is nothing to match them against.

Add-on charges fail invoices that matched cleanly

An invoice is more than a price times a quantity. It carries tax, and it often carries freight, handling, fuel surcharges, or other fees. Each of these is a separate figure the company has to verify. When the tax does not match the expected rate, or a freight line appears that was never quoted, the invoice stops even if the underlying goods matched cleanly.

Tax is a rules problem, and the rules live outside the invoice

Tax is hard because the correct amount depends on rules the invoice itself does not carry: the jurisdiction, the tax status of the goods, where they shipped from and to, and the company's own tax determination logic. A supplier can apply the wrong rate, charge tax on something exempt, or omit tax the company is liable to self-assess. The system checks the invoiced tax against what it calculates and flags any gap, and confirming which figure is right takes tax knowledge, not just a look at the order.

Freight arrives with no order line to match

Freight and surcharges are usually not on the purchase order, because the amount is not known when the order is cut. The invoice arrives with a shipping line, a fuel surcharge, or a handling fee, and there is no order line to match it to. The company has to decide whether the charge is legitimate and agreed, often by checking the carrier contract or the incoterms that set who pays for shipping.

The reference data lives outside the purchase order

Ordinary matching compares like against like: an ordered line against an invoiced line. Tax and freight break that model, because the reference is a rule or a separate contract rather than a purchase-order line. The check has to reach outside the order to a tax engine, a carrier agreement, or the incoterms, and that context rarely sits in one place.

Three departments to clear one invoice is the real cost

A clerk confirms the tax against the tax determination rules, or routes it to a tax specialist, and checks freight against the carrier contract or the agreed shipping terms. Because the answer depends on external rules and agreements, these exceptions often move between AP, tax, and logistics before they clear, which is what makes them slow out of proportion to their dollar value.

Fragment resolves tax and freight discrepancies autonomously by reading the order, the tax rules, and the carrier terms in place, without ripping out or replacing your existing systems. See how it works or request a demo.

From Fragment
See exception resolution on your own data
Fragment resolves invoice exceptions autonomously across your existing ERP and documents.
Request demo