insonl
← journal

Three-Way Invoice Matching Exceptions: Queue Rules

date
20 November 2026
by
Insonl
read
7 min read

Document extraction in front of an ERP can speed up invoice intake while leaving downstream matching delays in place. The real gate sits in three-way invoice matching exceptions: invoices flagged for review because the supplier bill disagrees with the purchase order (PO) or warehouse receipt.

Exception queues break in two ways. Leave tolerances at zero everywhere and accounts payable (AP) staff drown in minor rounding and freight differences. Leave posting open with warnings and no owner, and unreceived goods or price overruns slip onto the ledger.

This guide covers what three-way matching compares, how to scope policies and tolerances, which discrepancies belong in the exception queue with an owner, and where AI fits beside deterministic ERP checks.

What three-way matching actually compares

Using Microsoft Dynamics 365 Finance’s Accounts payable invoice matching overview and Three-way matching policies as an ERP reference model, Microsoft’s overview lists four types of invoice matching:

  • Two-way matching compares invoice line prices against PO line prices, without checking receipts.
  • Three-way matching compares invoice line prices against PO lines and invoiced quantities against matched product receipt quantities.
  • Invoice totals matching compares six header totals—labeled Subtotal, Total discount, Charges, Sales taxes, Round off, and Invoice amount in Microsoft’s invoice matching validation setup guide—against expected totals derived from PO prices, charges, and sales tax with invoice quantities.
  • Charges matching compares amounts by charges code (such as shipping and handling or licensing) between the PO and invoice for charges codes enabled for comparison.

At the line level, both two-way and three-way matching check net unit price and can also be configured to check line price totals:

  1. Net unit price matching compares Net amount of the line / Quantity of the line on the invoice against the PO line net unit price.
  2. Price totals matching compares the line net amount—(Unit price * Line quantity) + Line charges - Line discounts—across the current invoice plus all pending and previously posted invoice lines against the PO line net amount. Microsoft notes this check fits vendors sending multiple invoices against one PO line; for partial invoices, validation runs on the final invoice for that line. Percentage tolerances compare transaction currency values; amount tolerances compare accounting currency values.

Separating these types matters because a missing receipt, price jump, unbudgeted freight fee, and tax mismatch require different owners.

Policy hierarchy: not every line needs three-way matching

For purchases without a product receipt—such as services, software renewals, or consumables—three-way matching can create exceptions that need manual review until someone bypasses the control.

Microsoft’s invoice matching validation setup guide resolves matching policies through a four-level hierarchy, from most specific to broadest:

  1. Item and vendor combination
  2. Item
  3. Vendor
  4. Legal entity default

Where overrides are permitted, buyers can also change the matching policy on an individual PO line.

Microsoft’s three-way matching policy examples illustrate a two-way legal-entity default with three-way matching for selected item-and-vendor combinations and an override on an individual PO line. For an inventory-heavy operation, another design to consider is a three-way default with two-way matching for selected services whose approval is tracked outside product receipts.

Keep that boundary in ERP configuration rather than AP notes. If a clerk must guess whether a missing receipt is a shortage or a service purchase, routing breaks.

Setting tolerances without hiding real errors

Three configuration choices separate a clean exception queue from daily noise:

  • Set unit-price tolerances deliberately. In Dynamics 365 Finance, the default legal entity unit price tolerance is 0% across all items and accounts and cannot be deleted. Set explicit tolerances for item groups, vendors, or item-and-vendor pairs where small variances are normal, and keep fixed-price contracts tight.
  • Pair percentage tolerances with a not-to-exceed amount cap. A 5% tolerance allows $1 on a $20 part, but $5,000 on a $100,000 line; a flat cap fails in reverse on cheap parts. On line price totals matching, Dynamics 365 Finance supports None, Percentage, Amount, or Percentage and amount, where the amount limit acts as a not-to-exceed cap and exceeding either threshold flags a discrepancy. Replicate that dual check in custom ERP validators.
  • Configure negative variances and unbudgeted charges explicitly. By default in Dynamics 365 Finance, negative price discrepancies are allowed and negative tolerance percentages cannot be entered. To flag underbilling—such as a missed line, wrong unit of measure, or misapplied credit—enable flagging when variances are greater than or less than the tolerance. When charges matching is enabled for a code, Dynamics 365 Finance shows a variance of 99,999,999,999.99% if the expected PO charge is zero and the invoice charge is positive, and reports a matching discrepancy when that variance exceeds the configured tolerance. If buyers omit freight from POs while freight charges matching is enabled, AP will see recurring discrepancies until purchasing records expected freight or sets a rule.

What to send to the exception queue—and who owns each class

Queues clog when every failed check drops into one “AP Hold” bucket. AP clerks did not negotiate unit prices and were not on the loading dock. The table below shows a recommended hold policy for an exception queue. Configure your ERP or approval workflow to enforce those holds and route each discrepancy to its owner.

Exception class Trigger condition Block? Primary owner Resolution path
Missing receipt Three-way line has no linked receipt Yes Receiving / Warehouse Confirm delivery and post receipt; AP never invents receipts
Quantity mismatch Invoiced qty differs from receipt qty Yes Receiving + Purchasing Confirm short vs. partial shipment; link receipt, adjust qty, or request credit
Price over tolerance Unit price or price total exceeds cap Yes Purchasing / Buyer Verify contract price, amend PO if valid, dispute, or document override
Unexpected charge Tracked charge missing or over tolerance Yes Purchasing / Logistics Verify freight/fee terms; allocate approved charge or reject
Header / tax mismatch Totals check flags tax, discount, or total Yes Accounts Payable / Tax Reconcile tax codes, rounding, or header discount before posting
Intake failure Missing PO, unknown vendor, or bad OCR Yes (pre-ERP) AP Ops / Integration Fix extraction or SKU/vendor mapping before ERP matching

Check how your ERP enforces posting stops. In Dynamics 365 Finance, Post invoice with discrepancies controls whether posting requires approval or permits posting with a warning (Allow with warning). When approval is required, an authorized user must select Approve posting with matching discrepancies on the Invoice matching details page before posting. Microsoft notes that when discrepancy approvals run through a workflow, Post invoice with discrepancies should be set to Allow with warning to avoid double approval. As an implementation check, verify the workflow blocks posting until approval completes.

Illustrative worked example: one three-line invoice

(Illustrative example—not a real company or an Insonl client.)

Consider one invoice matched against a PO with a 2% net unit price tolerance:

Line Item Policy PO Receipt Invoice Result and owner
1 Steel bracket Three-way 100 @ $50.00 100 100 @ $50.50 (+1.0%) Pass — qty matches; price within 2% tolerance
2 Control module Three-way 10 @ $400.00 8 10 @ $400.00 (0%) Exception -> Receiving & Purchasing — invoiced 10 vs. received 8
3 Packing labels Two-way 500 @ $2.00 None 500 @ $2.20 (+10.0%) Exception -> Purchasing — price exceeds 2%; no receipt check

Line 1 passes the matching checks. Under the hold policy above, lines 2 and 3 route to different owners and remain on hold until resolved or approved. Emitting structured codes (RECEIPT_QTY_MISMATCH, UNIT_PRICE_OVER_TOLERANCE) with the PO line, receipt reference, and invoice excerpt removes manual triage emails.

Where AI fits—and where ERP rules stay in charge

Keep deterministic software in charge of matching. Comparing quantities, computing net unit prices, summing partial invoices across currencies, enforcing tolerances, and blocking posting are deterministic operations. Never ask an LLM whether a price discrepancy is close enough to pay.

AI fits upstream of the match and around exception preparation:

  • Structured intake. Extracting header fields, line items, quantities, prices, and charges from irregular PDFs into a strict schema before ERP validation, as examined in our teardown of AI document and order processing pipelines.
  • Supplier-to-PO resolution. Mapping supplier descriptions to open PO lines and internal SKUs when vendors omit item codes, routing low-confidence matches to pre-ERP review.
  • Exception packets. Bundling the PO line, receipt status, prior invoices, and supplier email context so the owner clears the hold on one screen.

Before automating extraction or triage, measure why invoices fail today. As outlined in our guide on what an AI workflow audit covers, sample historical invoices and count how many stalled from keying errors versus late receipts or stale PO prices. If receiving posts receipts three days late, AI extraction only fills the hold queue faster.

Audit your invoice flow before automating it

Insonl is a Ho Chi Minh City engineering studio building ERP systems and operational AI. If your AP team is evaluating invoice automation or dealing with a crowded exception queue, start with a free AI workflow audit.

The audit is free. We examine how POs, receipts, and invoices move through your systems and deliver a written workflow map, recommendations—including where ERP configuration or process changes beat AI—and a fixed-scope estimate. Follow-on work is optional; Insonl charges only for work after the audit.

Sources