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.
The second problem appears after you "solve" capture. 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.
We also heard the twin case from multi-entity commercial teams: upload a quote and prefill a PO. Different motion, same idea. Price authority starts before the invoice.
Benchmarks around PO-linked invoices
Ardent Partners' State of ePayables 2025 (Bottomline-sponsored edition) reports that 65.4 percent of invoices are linked to a purchase order on average, with best-in-class at 84.0 percent, and an average invoice exception rate of 18.4 percent. The Metrics That Matter 2025 companion figures put exceptions nearer 14 percent depending on the survey cut. Either way, exceptions remain the drag.
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.
What we show, and what we will not overclaim
In demos we show quote attachment and quote-to-PO prefill motions, and we talk through invoice match against that bundle for teams whose POs start without amounts. Line-level match matters here more than a green total check.
Honest limit: this is a deep edge. Qty-only PO with quote as sole price source sits next to unmet or unmet-adjacent notes in our own mining. We will not write as if every government packing list already posts itself. Confirm depth on your documents in a working session before you rewrite policy around it.
What we refuse is pretending a blank price on a PO is "close enough" to match on header totals. That is how unauthorized price drift enters quietly.
Who this applies to
This matters most if purchase orders carry quantities without prices and the dollars still live on a quote or price confirmation that AP has to join by hand.
Where this does not help
If your POs already carry firm prices and receipts, classic three-way match is the centre of gravity. Quote bundling is supporting evidence, not the plot.
We also do not replace procurement policy. 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.
Deliberate choice: support quote-backed price authority for teams that already work that way, without claiming a universal 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 called 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 lit up when a quote upload could prefill a PO. 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.
Honest limits, repeated for clarity
We will say it twice because overclaiming here is the failure mode. Qty-only PO with quote as sole price source is a deep edge. Confirm it on your documents before you rewrite policy. A good working session beats a blog post. Use this article to ask better demo questions, not to declare the problem finished in every government office.
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.
Can Telpay or payment-only tools solve this?
Payment rails move cash. They do not create a quote-PO-invoice audit pack. Buyers who dual-reconcile bank and payment portals feel that gap weekly.
