Invoice-to-Purchase-Order Matching Checklist and Exception Log Template
accounts payablepurchase ordersthree-way matchinginvoice exceptionsprocurement workflows

Invoice-to-Purchase-Order Matching Checklist and Exception Log Template

IInvoices.page Editorial Team
2026-11-09
7 min read

Use a three-way matching checklist, tolerance examples, and an exception log to review invoices against purchase orders and receipts.

A consistent invoice matching process helps accounts payable and operations teams approve valid invoices, identify exceptions early, and keep disputed charges from becoming avoidable payment delays. This guide provides a reusable three-way matching checklist, a simple way to estimate payable amounts and exception exposure, tolerance examples, and an invoice exception log you can adapt to each supplier or invoice batch.

Overview

Purchase order invoice matching compares three records before payment is approved:

  1. Purchase order (PO): what was requested, including the supplier, item or service, quantity, agreed price, delivery details, and approval information.
  2. Receipt or service record: what was delivered, accepted, completed, or recorded by the responsible team.
  3. Supplier invoice: what the supplier is requesting to be paid, including invoice number, dates, line items, taxes, credits, and payment instructions.

This is commonly called a three-way match. A two-way match may compare only the PO and invoice, while service-based purchases often require an additional approval record, such as a timesheet, milestone sign-off, or completion certificate.

The purpose is not to force every document to look identical. It is to confirm that the invoice relates to an authorized purchase, that the quantity or service was received, and that the amount being approved follows the agreed terms. Your own procurement policy should determine which differences can be approved automatically and which require review.

Use the following checklist for each invoice:

  • Confirm the supplier name, legal entity, and purchase order number.
  • Check that the invoice number is present and has not already been processed.
  • Compare invoice line items with the PO description, quantity, unit price, and currency.
  • Compare invoiced quantities with delivery or acceptance records.
  • Check freight, discounts, surcharges, tax, credits, deposits, and previous payments.
  • Confirm that the invoice total agrees with the line calculations.
  • Route any unresolved difference to the named owner before payment approval.
  • Record the decision and supporting evidence in the invoice or exception log.

For related setup work, use the Client Billing Information Form and Invoice Setup Checklist to standardize the information collected at the start of a billing relationship.

How to estimate

A matching review can also be treated as a repeatable estimate: calculate the amount that appears payable, compare it with the amount authorized by the PO and receiving records, then quantify the difference that needs investigation.

1. Calculate the expected invoice amount

For each line, multiply the accepted quantity by the agreed unit price. Then add approved charges and taxes, and subtract documented credits or discounts.

Expected amount = accepted quantity × agreed unit price + approved additional charges + applicable tax − credits and discounts

Do not treat tax as a simple markup unless the relevant tax treatment has been confirmed. If the transaction involves VAT or another tax requirement, retain the appropriate documentation and use your organization’s tax rules. The Invoice Total Calculator Guide can help structure the arithmetic for tax, discounts, deposits, and amounts due.

2. Calculate the invoice variance

Compare the supplier’s invoice total with the expected amount:

Invoice variance = invoiced amount − expected amount

A positive result means the invoice is higher than the amount supported by the PO and receipt records. A negative result may indicate an underbilling, a credit, a partial invoice, or a receiving record that has not yet been updated.

3. Apply the approved tolerance

A tolerance is a pre-approved range within which a difference may be accepted without a full rework. Tolerances must be set by your business; the examples below are illustrations, not universal rules:

  • Quantity tolerance: allow a small difference when a supplier ships in practical units, provided the received quantity is documented.
  • Price tolerance: allow a limited unit-price difference only when the contract or procurement policy permits it.
  • Amount tolerance: allow a small total difference for minor rounding or approved incidental charges.

For each tolerance, record whether it is a percentage, a fixed amount, or both. Also record whether tax, freight, and service charges are included. An invoice that falls within a tolerance can still require review if the supplier, bank details, PO status, or duplicate-invoice check fails.

Inputs and assumptions

Prepare these inputs before beginning the review:

InputWhat to captureWhy it matters
PO recordPO number, approved lines, quantities, prices, currency, terms, and buyerEstablishes the authorized purchase
Receipt recordDelivery date, accepted quantity, condition, or service approvalConfirms what was received or completed
InvoiceSupplier, invoice number, dates, lines, taxes, credits, and totalDefines the requested payment
Payment historyPrior invoices, deposits, credits, and payments against the POHelps identify duplicates and remaining balances
Approval rulesDelegated approver, tolerance limits, and escalation routeDetermines whether the invoice can proceed

State assumptions explicitly. For example, you might assume that a receipt marked “accepted” represents the final approved quantity, that prices are exclusive of tax, or that a separate service approval is required for non-physical work. If an assumption is uncertain, do not silently use it to approve payment; mark it as an exception.

For recurring services, compare the invoice with the agreed billing schedule and the approved period rather than expecting a delivery quantity. The Recurring Invoice Template and Billing Schedule Guide is useful when reviewing retainers or subscription-style charges.

Reusable invoice exception log

Use one row per issue, not one vague note per invoice. Include these fields:

  • Exception ID and date identified
  • Supplier and invoice number
  • PO number, if available
  • Exception type: missing PO, duplicate, quantity, price, tax, receipt, coding, or disputed charge
  • Invoiced amount, expected amount, and variance
  • Evidence reviewed
  • Assigned owner and target resolution date
  • Supplier contact or internal requester
  • Decision: approve, hold, reject, credit requested, or escalate
  • Resolution notes and approval reference

Worked examples

Quantity difference

A PO authorizes 100 units at 12 currency units each. The receiving record confirms 96 units, but the invoice bills 100 units. The supported amount before tax is 96 × 12 = 1,152. The invoice line is 1,200, creating a variance of 48. The reviewer should hold or adjust the invoice unless the remaining four units were delivered but not recorded. If the receipt is updated with evidence, the match can be performed again.

Price difference

A PO lists 20 hours at 75 per hour, while the invoice lists 20 hours at 80 per hour. The expected service amount is 1,500, and the invoice amount is 1,600, producing a 100 variance. Check for an approved change order, renewed rate, or contract amendment. Do not use a price tolerance to conceal an unapproved rate change.

Partial delivery

A supplier invoices the full PO, but the receipt confirms only half the items. The AP reviewer should determine whether the supplier intended a progress invoice, whether the terms allow partial billing, and whether a second delivery is pending. The invoice may be approved only for the accepted portion if the supplier issues a corrected invoice or the system supports partial matching.

Missing PO or duplicate invoice

For a missing PO, place the invoice on hold, identify the requester, and determine whether the purchase was authorized under an approved non-PO process. For a possible duplicate, compare supplier, invoice number, amount, date, currency, and line details against prior submissions. Never resolve a duplicate merely because the invoice number differs; suppliers may resend a document with formatting changes.

When to recalculate

Recalculate the expected amount whenever an input changes. This includes a new PO revision, change order, receipt correction, approved service milestone, supplier credit, tax treatment, currency, deposit, or payment already applied to the order.

Review the checklist and exception log fields when your accounting or procurement system changes, when electronic-invoicing requirements are introduced or revised, or when approval responsibilities move between teams. Update quantity, price, and amount tolerances when the organization changes its risk controls or purchasing categories. Keep the effective date and policy owner beside each tolerance so reviewers know which rule applies.

At the end of every invoice batch, use this short closeout routine:

  1. Filter the exception log for open items and overdue owners.
  2. Recalculate each variance using the latest PO, receipt, and invoice data.
  3. Attach the approval, credit note, corrected invoice, or other resolution evidence.
  4. Confirm that holds, rejected invoices, and duplicate flags are reflected in the accounting system.
  5. Review recurring exception types and adjust the purchasing or receiving workflow if the same issue repeats.

Use this process alongside your existing invoice payment terms and late payment reminder templates so a matching hold is documented separately from a payment follow-up. A clear record of what was checked, what differed, and who approved the resolution makes the checklist reusable for every supplier review and invoice batch.

Related Topics

#accounts payable#purchase orders#three-way matching#invoice exceptions#procurement workflows
I

Invoices.page Editorial Team

Editorial Team

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.