Two-Way Matching Process: How Accounts Payable Teams Avoid Delays

Two-way matching process means accounts payable compares a supplier invoice against the related purchase order before approving payment. It is simpler than three-way matching because it does not require a separate receiving report, but it still gives finance teams a documented control before cash leaves the business.

That makes it useful for services, retainers, subscriptions, low-risk catalog purchases, and trusted vendor relationships where a goods receipt is not the main proof point. It is not a shortcut for every invoice. The decision is whether a PO and invoice give enough evidence to pay, or whether the invoice needs delivery, acceptance, quality, tax, or budget review.

What’s in this article?

• What two-way matching checks in accounts payable
• When finance teams should use two-way instead of three-way matching
• A practical workflow for purchase order and invoice matching

Why two-way matching matters

AP teams are often balancing two risks: paying too quickly without enough evidence, or slowing every invoice with controls that do not match the risk. Two-way matching helps by confirming that the invoice is tied to an approved PO, uses the right vendor, matches the expected scope or item, and stays inside agreed pricing and terms.

Public procurement policies show the same control logic. The City of Houston procurement and payment policy says departments review and approve invoices using two-way or three-way match as applicable, with service invoices compared against the contract and goods invoices compared against proof of delivery. Rockefeller University’s purchasing guidance similarly describes two-way matching for services and other cases where no receiving report exists.

Two-way matching process for accounts payable

A clean two-way matching process should be consistent enough for automation and clear enough for a reviewer to follow when an exception appears.

1. Create or confirm the purchase order. The PO should include the supplier, buyer, scope, line items or service description, quantity or period, price, payment terms, tax treatment when relevant, and approval owner.
2. Receive the supplier invoice. Capture the invoice from email, portal, EDI, or AP intake. Keep the original invoice and extract invoice number, vendor, PO number, invoice date, due date, amount, currency, tax, and remittance details.
3. Match invoice fields to the PO. Compare vendor name, PO reference, line descriptions, price, quantity or service period, taxes, freight, discounts, currency, and payment terms.
4. Apply tolerance rules. Small variances may be acceptable if policy allows them. Larger price, quantity, tax, or address mismatches should route to an owner instead of moving to payment.
5. Approve, hold, or reject the invoice. Matched invoices can move to payment approval. Unmatched invoices should be held with a reason code, owner, due date, and vendor communication path.
6. Store the audit trail. Keep the PO, invoice, match result, tolerance decision, approval, exception notes, and payment reference together.

When to use two-way matching

Two-way matching works best when the PO and invoice are the right evidence for the payment. It is usually a strong fit for software subscriptions, consulting retainers, recurring professional services, utility-style expenses, simple catalog purchases, and approved blanket PO releases.

What to check during the match

The match should cover both header-level and line-level evidence.

• Vendor legal name, tax profile, and remittance details match the approved vendor record.
• PO number is valid, approved, open, and belongs to the same vendor.
• Invoice number has not already been submitted or paid.
• Line description, service period, quantity, unit price, subtotal, tax, freight, and total match the PO or approved tolerance.
• Payment terms, due date, currency, discounts, and withholding treatment are consistent with the PO.

Set tolerances before exceptions happen

Tolerances decide which differences can move forward automatically and which differences need review. They should be written as policy, not improvised invoice by invoice. Common examples include a small dollar variance for tax or shipping, a percentage variance for line price, or a rule that no variance is allowed for vendor identity, invoice number, or currency.

Keep tolerance logic specific. A low dollar tolerance may be reasonable for freight on office supplies, but not for a foreign contractor invoice with withholding implications. A percentage tolerance may work for simple purchases, but not for regulated materials, project milestones, or grant-funded work. Washington State Auditor guidance on segregation of duties is a useful reminder that controls should separate incompatible responsibilities and add compensating review when separation is limited.

Exception workflow for unmatched invoices

Two-way matching only works if unmatched invoices have a disciplined path.

1. Assign the exception to the right owner: buyer, department approver, AP specialist, procurement, tax, or vendor manager.
2. Record the reason: price variance, missing PO, closed PO, duplicate invoice, wrong vendor, wrong remittance details, tax issue, unsupported service period, or exceeded amount.
3. Choose the resolution path: correct the invoice, adjust or close the PO, request approval, reject the invoice, or escalate for fraud or bank verification review.
4. Close the loop by updating the invoice status, match result, payment hold, and audit record.

Common mistakes to avoid

• Using two-way matching for physical goods without receiving evidence: If delivery matters, add receiving confirmation.
• Letting AP override PO mismatches without ownership: The buyer or budget owner should resolve commercial differences.
• Mixing bank verification into invoice matching: Bank-detail changes need their own control, even when the invoice matches the PO.
• Failing to preserve the match evidence: The audit trail should show what matched, what did not, who approved the exception, and when payment was released.

Where Workhint fits

Workhint helps finance and operations teams turn two-way matching into a live workflow instead of a loose AP checklist. A company can route invoice intake, pull PO context, assign mismatches, hold payment until exceptions clear, track approvals, store documents, and report bottlenecks across vendors, contractors, departments, and projects.

That matters when payment work crosses finance, procurement, operations, and vendor owners. The matching rule is simple. The operating system around it is what keeps invoices from getting paid too early, stuck too long, or approved without a record.

FAQ

What is two-way matching in accounts payable?

Two-way matching in accounts payable compares a supplier invoice with the related purchase order before payment approval. The goal is to confirm that vendor, amount, scope, terms, and PO details agree.

What documents are used in two-way matching?

The two documents are the purchase order and the vendor invoice. If receiving evidence is also required, the workflow becomes a three-way match.

When should a business use two-way matching?

Use it for lower-risk services, subscriptions, retainers, catalog purchases, or trusted vendor arrangements where a receiving report would not add meaningful evidence. Use stronger controls for goods, high-value purchases, regulated items, or disputed work.

Does two-way matching prevent duplicate payments?

It helps, especially when invoice number, vendor, PO, and amount checks are enforced. Duplicate-payment prevention also depends on vendor master controls, payment status tracking, and reconciliation.

Conclusion

The two-way matching process is useful because it gives AP teams a fast control for the right invoices. It should confirm the invoice against the approved purchase order, apply clear tolerances, route exceptions to accountable owners, and preserve evidence for audit and reconciliation.

Use two-way matching where the PO and invoice are enough. Escalate to three-way, four-way, tax, bank, or management review when the payment risk needs more proof.