A finance administrator in a remote community government described purchase orders that list quantities without unit prices. Five cans of paint. A count of supplies. The quote holds the dollars. The invoice arrives later. They do not want three disconnected PDFs. They want the quote, the purchase order, and the invoice to match as a bundle.
The direct answer: when the PO is quantity-first, the quote has to travel with the PO as the price source, and the invoice has to match against that bundle. Total-only matching against an amount-empty PO will either false-pass or false-fail.
This matters most if you work in municipal-style or community government AP, if procurement culture writes qty-only POs, or if quotes are the real commercial document and the PO is the authorization shell.
Why standard three-way match tutorials miss this
Most AP education assumes the PO already carries price and quantity. Three-way match then compares PO, receipt, and invoice. That model is fine for many manufacturers. It is incomplete when local practice deliberately omits price on the PO.
Capture turns out to be the easy half. Beautiful invoice OCR still has nothing solid to match if the PO lines have no amounts and the quote lives in someone's email. Clerks re-key prices from the quote into a comment field. Approvers trust memory. Audit asks where the authorized price came from.
Multi entity commercial teams describe the twin case from the other direction.
Benchmarks around PO-linked invoices
Ardent Partners' Accounts Payable Metrics That Matter in 2025 puts the average invoice exception rate at 14 percent and the average cost per invoice at $9.40. Exceptions remain the drag, and a PO that cannot be matched on price is an exception waiting to happen.
Those numbers assume a PO worth matching. A qty-only PO without an attached price source inflates exceptions or teaches people to bypass match entirely. Measure your own share of POs that contain quantities but no unit prices. If that share is material, generic three-way marketing will not describe your week.
Bundle test for buyers evaluating AP tools
Ask these questions in the demo, with your own redacted quote and qty-only PO.
1. Can the quote attach to the PO as a first-class document, not only as an unclassified PDF?
2. When the PO has quantities and no prices, what does the system use as the price source at invoice match?
3. Can invoice lines match item by item, or only on a total?
4. What happens when the invoice price differs from the quote?
5. Can an approver see quote, PO, and invoice in one object without hunting email?
If the answer to 2 is "we do not support that," believe them. Do not accept a roadmap slide as a workaround for next month's paint order.
Line level match matters here more than a green total check. In Finofo, the quote attaches to the purchase order as a first class document, so when the PO carries quantities and no amounts, the quote is the price source the invoice lines are matched against. Quote, PO and invoice sit on one object; a line where the invoice price differs from the quote is flagged as a variance rather than absorbed into a header total; and the approver sees all three documents in one record. A blank price on a PO is never treated as "close enough" to match on totals, because that is how unauthorised price drift enters quietly.
Purchasing and payables are the same engine, which is why the bundle holds together. Finofo runs accounts payable, expense management and purchasing on one AI native platform, built in Calgary for Canadian finance teams. The PO raised in purchasing, the quote attached to it and the invoice arriving in AP are one record with one approval path into the ERP, whichever order the documents were created in.
What stays with your team
The judgment in this workflow stays with your team. That is a design decision, not a gap, and it shows up in a few specific places.
Where your POs already carry firm prices and receipts, classic three way match is the centre of gravity and Finofo runs it at line level. Quote bundling is supporting evidence in that world, not the plot.
Procurement policy stays procurement's. If your board requires prices on every PO, the software should not become an excuse to keep writing empty amount fields forever. Sometimes the fix is the PO template, and Finofo's PO creation can require a price or a linked quote at the point of purchase.
Quote backed price authority is supported for teams that already work that way, as configuration on the same purchasing module, rather than as a separate government AP suite. Depth over brochure coverage.
Back to five cans of paint
The PO said five cans. The quote said the price. The invoice should meet both. Keep them in one bundle so matching has somewhere true to land.
Why email folders make the problem worse
In community and municipal-style teams, the quote often lives with the person who requested the purchase. The PO lives with finance. The invoice lands in a shared inbox. Matching becomes archaeology. When staff turn over, the archaeology skill leaves with them.
A bundle will not replace procurement judgement. It will replace the scavenger hunt that currently pretends to be judgement.
What good looks like in a working session
Bring three redacted packets: a qty-only PO, the quote that priced it, and the invoice that billed it. Watch whether the tool keeps them related after upload. Watch whether match messages mention price source. Watch whether an approver can open all three without leaving the record.
If the demo only shows a priced PO happy path, you have not tested your reality. Community government and other qty-first cultures are not broken procurement. They are a different document order. Software that cannot admit that order will force you back into email bundles.
Training continuity is part of the product requirement
Community teams call out staff turnover explicitly. When the person who understood the quote-PO ritual leaves, the next hire inherits inbox archaeology. A durable bundle in the AP object is institutional memory. That is not soft culture talk. It is how you keep paying the right amounts for paint after the administrator changes.
Quote prefill is related but not identical
Commercial teams also want a quote upload to prefill a PO, which Finofo supports. That motion helps when price authority starts on the quote and the PO is created afterward. Qty-only government POs are the harder sibling: the PO may already exist with quantities and still lack amounts. Evaluation should test both. Do not let a pretty quote-to-PO demo stand in for qty-only match against an existing PO.
Test it on your documents before you rewrite policy
This is a deep edge of purchasing practice, and the right way to evaluate it is a working session on your own packets rather than a slide. Bring the quantity only PO, the quote and the invoice, and confirm the bundle behaves the way your procurement policy needs before you change the policy around it. Use this article to ask sharper demo questions. Use the session to see the answer.
Frequently asked questions
Is this the same as three-way matching?
It is related. Classic three-way assumes priced PO lines. Quote-backed match adds the commercial price document when the PO is quantity-first and Finofo runs both on the same purchasing object.
Can payment-only tools solve this?
Payment rails move cash. They do not create a quote, PO and invoice audit pack. Teams who dual reconcile bank and payment portals feel that gap weekly, which is why Finofo keeps purchasing, matching and payment on one record.
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.
