A drywall and light manufacturing group with multiple legal entities runs purchase orders through a manufacturing system and books payables in QuickBooks. The AP clerk opens an invoice that totals to the PO. The header match is green. Then someone reads the lines: three SKUs, one pack size that does not match the PO unit, and a price that drifted after the last price list landed. The total still ties. The inventory and the books do not.
Header match is not line match. If your auto match only compares invoice total to PO total, it will approve documents that are wrong on every line that matters for receiving, costing, and vendor kickbacks.
This matters most if you buy the same materials across jobs or plants, if vendors invoice in different units than you purchase (sheets versus pounds, cases versus eaches), and if price lists move after POs are cut.
Why a matching total still leaves work on the desk
Manufacturing and materials buyers already know the failure mode. An incumbent or ERP matcher clears the invoice because the dollars equal the dollars. Nobody on that screen asked whether SKU A on the invoice is the same item as line 4 on the PO, whether forty sheets equals the poundage the mill billed, or whether the unit price is the PO price or the newer, lower list price the vendor emailed last Tuesday.
Operations and finance leads ask for the same thing in plain language: can matching cross reference item by item, not only total to total. Metals and specialty materials teams describe the poundage edge: the PO is in one unit, the invoice arrives in another, and someone edits by hand so the receipt and the bill agree.
Solving that exposes the real issue. Once totals match, the invoice leaves the exception queue. The packing slip, the inventory receipt, and the price variance never get a forced look. Variance is not always fraud. Sometimes it is a pack size. Sometimes it is a legitimate price drop you want to take. Either way, total only matching hides it.
What the benchmarks say about exceptions that never look like exceptions
Ardent Partners’ Accounts Payable Metrics That Matter in 2025 (drawn from The State of ePayables 2024 survey of 212 AP professionals) puts average invoice processing cost at $9.40 and average touchless processing at 32.6% of invoices. Their State of ePayables 2025 reporting puts the industry average exception rate at 18.4%. Those figures are US heavy and process wide. They still explain why total only match feels productive: the invoice clears the metric, even when a human still has to reconcile units and SKUs offline.
Line disagreements are a quiet exception class. They do not always raise a red flag in a header matcher. They raise a receiving issue, a costing issue, or a vendor dispute three weeks later.
A ten minute diagnostic you can run without buying anything
Pull twenty recently paid PO backed invoices and score each one:
- Did header total match the PO within tolerance?
- Did every invoice line map to a PO line by item (not only by amount)?
- Did unit of measure convert cleanly, or did someone edit quantity by hand?
- Was unit price equal to PO, equal to a later price list, or merely close enough?
- Would you have wanted a lower of PO versus price list rule on that vendor?
If more than a handful fail questions 2 through 4 while passing question 1, your matcher is measuring the wrong thing.
Ask the vendor questions while you are evaluating tools. Can match fail a line when the header passes. Can UOM conversions be remembered per vendor. Can a price list update change the payable price without rewriting the PO. If the answers are vague, assume you are buying a total matcher with better marketing.
Item by item matching, and the variance we refuse to hide
Finofo matches item by item against linked purchase orders and packing slips, with unit conversion memory and variance actions, including lower of PO versus a later price list when that is the commercial rule. The point is not another explainer titled "what is three way matching." The point is that a green header is insufficient when SKUs disagree, and Finofo is built to say so before the bill posts.
We refused to treat "totals match" as success. That is the deliberate choice. A tool that only clears on totals will always look faster in a demo and then recreate the poundage edit, the SKU argument and the price list chase in production. For the drywall group, the invoice that tied at the header now stops at the line that drifted, with the PO line, the packing slip quantity and the price list beside it, and the reviewer decides in one screen.
The memory is the part that compounds. Once someone teaches the first sheets to pounds conversion for a mill, Finofo remembers it for that vendor. Once the commercial rule is set to take the lower of PO or current price list, the variance action fires without a conversation. The team’s pack sizes and pricing rules become configuration rather than folklore.
Matching lives on the same engine as everything else. Finofo runs accounts payable, expense management and purchasing on one AI native platform, built in Calgary for the documents Canadian finance teams actually process, so the PO raised in purchasing, the packing slip attached at receiving and the invoice arriving in AP meet on one object with one approval path into the ERP. Quantities, units and prices reconcile where the documents already live.
What stays with your team
Finofo is designed so that the people who sign off on the numbers stay in control of them. A few things are deliberately yours.
Line matching grips what your POs contain. Where POs carry item detail, every line is checked. Where a PO is a soft placeholder, the header check still runs and Finofo tells you which lines had nothing to match against, so the choice to tighten PO discipline is an informed one rather than a surprise at close.
Commercial rules are yours to set. Whether a lower invoice price is taken automatically, routed for approval, or held for a vendor conversation is a policy decision, and Finofo exposes the variance and applies the rule you chose. Quantity only POs with prices held in a separate quote process are handled as a scoped workflow with the quote linked, so the price source is visible rather than assumed.
Unit conversions are taught once by your team. Finofo does not invent pack sizes from silence; it remembers the conversion your buyer confirmed and applies it every time that vendor bills in the other unit.
Back to the green header
The drywall invoice that tied at the header and lied on the lines is not a rare edge. It is what total only matching systematically produces. Match the items. Convert the units you already argue about. Decide the variance action before the bill posts. Then the green light means something a plant manager and a controller can both trust.
Frequently asked questions
**Is line level PO matching the same as three way matching?**
Three way matching usually means PO, receipt or packing slip, and invoice. Line level matching is the granularity inside that idea: each item, quantity, and price must reconcile, not only the document totals. Finofo does the three way match at line level, with the packing slip linked on the same object as the PO and invoice.
**What should happen when the invoice price is lower than the PO?**
That is a policy choice. Some teams take the lower price automatically when a current price list supports it. Others route a variance for approval. The matcher should expose the difference, not bury it inside a matching total. Finofo surfaces the variance and applies whichever rule your team configured for that vendor.
**Do packing slips have to live in the ERP first?**
They need to be available to the match. In Finofo, packing slips link on the same invoice object as the PO, so the comparison is visible in one place during review, and the matched result posts to the ERP once.
About Finofo
Finofo is the AI native platform built in Calgary for Canadian finance teams. It brings accounts payable, expense management and purchasing onto one engine, on the cards, bank and ERP a business already uses, with line level extraction, Canadian tax handling and approval workflows designed for multi entity, multi province operations. Finofo does the verification. Finance keeps the judgment.
