What three-way match exceptions look like in a healthcare AP team
A three-way match exception occurs when an invoice line differs from its purchase order line or goods receipt line by more than the allowed tolerance for quantity or price, so payment is held until someone resolves it.
Healthcare buying is full of partial deliveries. A distributor ships 8 of 12 cases of exam gloves and backorders the rest. A lab receives reagents in two drops a week apart. A pharmacy gets a substitute NDC because the ordered one is short. Shortages make this worse: in Premier's 2024 supply chain survey, 67% of providers said their teams spend 10 or more hours a week mitigating supply chain challenges and shortages.[2] Every workaround on the dock shows up later as a mismatch in AP.
Here is the typical sequence. The PO says 12. The supplier invoices for 12 because the full order was confirmed. The clinic received 8 but nobody posted a receipt, or posted 12 out of habit. AP sees three numbers that disagree, puts the invoice on hold, and emails a site manager who is running a clinic session. Two weeks later the supplier calls asking why they have not been paid.
AP Manager / Controller
Carries a growing hold queue that nobody outside AP feels responsible for clearing.
"Half my week is chasing receipts, not paying invoices."Clinic or Lab Manager
Gets AP emails about deliveries from weeks ago with no easy way to check what came in.
"I signed for a box. I don't know which PO it was."Supply Chain Lead
Loses supplier goodwill and early-pay terms when invoices sit on hold for backordered lines.
"The rep is asking why we still haven't paid for March."CFO / Finance Leader
Cannot trust accruals at month end because received but uninvoiced and invoiced but unreceived items are unclear.
"How much do we actually owe suppliers right now?"Are partial deliveries clogging your invoice matching?
Tick every statement that is true today. Three or more means the problem is likely costing you real money.
Six root causes of match exceptions on partial shipments
Clearing holds one by one keeps AP busy but does not shrink the queue. These are the causes that keep refilling it in provider networks.
Receiving is treated as optional
Clinical staff unpack supplies and move on. The receipt in the system is posted late, in bulk, or copied from the PO quantity instead of the packing slip.
Suppliers invoice on order, not on shipment
Some distributors bill the full ordered quantity, then ship the balance later. The invoice runs ahead of what the site has actually received.
Substitutions are not recorded against the PO
A different pack size or an equivalent product arrives during a shortage. The item code on the invoice no longer matches the PO line, so the match fails on a line that was clinically fine.
Matching happens at invoice level only
If the system or the process cannot pay the matched lines and hold the rest, one backordered item blocks the whole invoice.
Tolerances are either zero or missing
A zero tolerance sends every rounding difference and freight line to a person. No tolerance at all lets real overbilling through. Neither fits the mix of low-cost consumables and high-value implants.
Exceptions have no owner
Holds sit in an AP inbox with a generic subject line. The person who can answer, usually at the site, never sees a clear question with the PO, receipt and invoice side by side.
What unresolved match exceptions cost a provider
Exceptions are one of the main drivers of AP workload. Published AP benchmarks show how common they are and what each invoice costs to process.
The direct cost is the staff time to investigate each hold across AP, the site and the supplier.[1] The indirect costs build up quietly: late payment fees and lost early-pay discounts, suppliers who put the account on credit hold during a shortage, duplicate payments when the backordered balance is invoiced separately, and month-end accruals that finance cannot rely on.
Estimate the annual cost of your match exceptions
Enter your figures. Nothing is stored or sent anywhere.
The expert playbook: six practices that shrink the hold queue
These practices work with any AP system, including a shared spreadsheet. Start with receiving, because most quantity exceptions are born on the loading dock, not in AP.
"In my years on the Ariba Network at SAP Labs, the pattern was always the same. AP got blamed for holds that started at receiving. If confirming a delivery takes longer than opening the box, people skip it. Make receipt a ten-second step on a phone at the site, and the match starts working before AP ever touches the invoice."Md. Kafil, Co-founder and CEO, Zapro. Former senior product specialist on SAP Ariba Network and procurement transformation manager at KPMG.
Measure exceptions by type, site and supplier
Make receiving same-day and line-level
Match and pay at line level
Set tolerances by category and value
Record substitutions against the original PO
Give every exception an owner and a deadline
"We once had five to six thousand suppliers emailing invoices into one inbox and calling to ask where their payment was. The fix was not more AP staff. It was showing suppliers and site teams the same PO, receipt and invoice status. Once everyone could see which line was short, most calls stopped."Daniel Sagayaraj, Co-founder and CTO, Zapro. Previously built and ran supplier onboarding and payments for a 15,000-supplier marketplace at Voonik.
How Zapro clears match exceptions before they become holds
Zapro keeps the purchase order, the goods receipt and the invoice in one record, so partial deliveries and backorders are visible to AP, the site and procurement at the same time.
| Root cause | Zapro capability | What changes |
|---|---|---|
| Late or copied receipts | Procurement: POs and receiving in one workflow | Sites confirm deliveries against the PO they raised, so the receipt reflects what actually arrived. |
| Manual invoice keying and comparison | AP Automation: invoice capture, data extraction and three-way matching | Invoices are captured and matched to POs and receipts automatically, and Z1 flags the lines that differ. |
| Exceptions with no owner | AP Automation: dispute and exception handling with role-based routing | Each exception goes to the right approver with the documents attached, and every decision is logged in the audit trail. |
| Suppliers chasing payment status | Vendor Management: centralized profiles with documents and conversations | Supplier questions about a held invoice sit in one place with the PO and receipt, not in scattered email threads. |
| No view of exception patterns | Spend Analytics dashboards and reports | Spend and invoice activity by supplier and location in one view, so repeat problem suppliers and sites stand out. |
Zapro syncs vendors, POs and payment status with your ERP or accounting system, and can receive invoices via API or SFTP from distributors that already send them electronically. See Zapro integrations and Zapro for Healthcare.
A 30, 60, 90 day plan
Days 1 to 30: Diagnose
- Export three to six months of held invoices
- Tag holds by type, site and supplier
- Measure delivery-to-receipt time per site
- Pick the two sites with the most quantity holds
Days 31 to 60: Fix receiving
- Roll out same-day line-level receiving at pilot sites
- Agree category tolerances with finance
- Switch to line-level approval and payment
- Ask top distributors to invoice backorders separately
Days 61 to 90: Sustain
- Extend receiving practice to all sites
- Set exception owners and escalation deadlines
- Publish a monthly exception report by site
- Review tolerances and substitution lists
KPIs to track progress
| KPI | How to calculate | Review |
|---|---|---|
| Invoice exception rate | Invoices placed on hold at least once divided by total invoices received | Monthly, by site and supplier |
| Quantity exception share | Holds caused by quantity differences divided by total holds | Monthly |
| Delivery-to-receipt time | Median hours between delivery and posted goods receipt | Weekly, by site |
| Exception age | Average days an exception stays open before resolution | Weekly in AP |
| First-pass match rate | Invoices matched and approved with no human touch divided by total invoices | Monthly |
| On-time payment rate | Invoices paid by due date divided by invoices due in the period | Monthly |
Go deeper with our guide to accounts payable automation guide.
What a Zapro customer saw after moving this work into one workflow
"Zapro made procurement effortless with a user-friendly interface and stellar support. Our team and suppliers adapted quickly, and we're now seeing faster approvals and smoother collaboration."Maria Rowan, Business Controller, Repromed
Why Zapro for this challenge
Most three-way match exceptions in healthcare start at receiving, not in AP. Zapro puts the PO, the receipt and the invoice in one place, so a short shipment is recorded once and every team sees the same answer.
PO, receipt and invoice in one record
Procurement and AP run on the same data, so a backordered line is visible from the site to payment without re-keying.
Z1 does the first pass
Zapro's AI layer matches invoices to POs and receipts and flags only the lines that need a person.
Built for multi-site providers
Role-based access lets each clinic or lab receive against its own orders, while AP keeps one view across locations.
Unlimited users on every plan
Every receiving site can have access without per-seat costs, starting at $699 per month.
When Zapro may not be the right fit
- Your invoice volume is small enough that one person clears every exception in an hour a week.
- Your ERP already handles line-level receiving and matching well, and your exceptions come from a single supplier you can fix with a conversation.
- You need point-of-use tracking of implants and lot numbers in the operating room. Zapro handles POs, receipts and invoice matching, and works alongside dedicated clinical inventory systems.
Frequently asked questions
What is a three-way match exception?
It is an invoice that cannot be approved automatically because its quantity or price differs from the purchase order or the goods receipt by more than the allowed tolerance. The invoice is held until someone confirms what was ordered, what arrived and what should be paid.
How should AP handle an invoice for a partial delivery?
Pay for what was received and hold the rest. The clean approach is to receive the delivered quantity against the PO, mark the remaining quantity as backordered, and approve only the matched lines. Ask the supplier to invoice the backordered balance separately when it ships.
What is a reasonable match tolerance?
There is no single standard. Many teams allow small tolerances on low-value consumables to absorb rounding and pack-size differences, and set zero tolerance on high-value, controlled or implantable items. The right setting is one that removes trivial holds without letting real overbilling through, so review it against your own exception data.
Why do most match exceptions come from receiving?
Because the goods receipt is the only record of what physically arrived. When clinical staff post receipts late, in bulk, or by copying the PO quantity, every split shipment or substitution turns into a mismatch that AP has to investigate.
Can software clear exceptions without weakening controls?
Yes, if it matches at line level, applies tolerances you set, and keeps an audit trail of every decision. Tools like Zapro automate the matching and route only real differences to a person, which usually tightens control because fewer holds are cleared in a hurry.
About the experts behind this page
Sources
- Tungsten Automation (citing Ardent Partners), AI in Accounts Payable: Metrics that Matter, 2025
- Premier Inc., New Premier Data Reveals Healthcare Supply Chain Trends, Challenges and Actionable Solutions, 2024
Editorial note: this page is published by Zapro, which sells procurement software. Best practices are written to work with any tool, and figures are cited to their original publishers. Last reviewed 29 September 2026; next review due March 2027. See how the Procurement Challenges Directory is researched and reviewed.