Three-Way Matching in D365 Finance: Setup and Resolution

Alfredo Iorio
May 24
4 min read

Three-way matching compares three documents at invoice posting time: the purchase order, the product receipt, and the vendor invoice. The price on the invoice line is checked against the price on the PO line. The quantity on the invoice line is checked against the matched product receipt quantity. If both sides line up within the configured tolerances, the invoice can post. If either fails, the line is flagged.

Two-way matching only does the price check. Three-way adds the receipt-to-invoice quantity check, which is what gives the control its name and its purpose: confirming that the goods invoiced were physically received. For services and other non-inventory items where product receipts aren't part of the AP process, two-way is the setting that fits.

Net unit price matching is the default price test. Price totals matching can be enabled alongside it, comparing the net line amount (unit price × quantity + line charges - line discounts) against the corresponding PO total. Charges matching is a separate, optional layer for line charges against PO charges.

Configuring matching policies and price and quantity tolerance rules

The matching configuration lives across three pages.

Accounts payable parameters > Invoice validation. The legal entity defaults are set here. Enabling invoice matching validation turns the engine on. Line matching policy sets the default for the legal entity. Allow matching policy override controls whether more specific policies can override the default. Post invoice with discrepancies controls what happens to a failed invoice: Allow, Require approval, or Block.

Invoice matching setup > Matching policy. Granular policies that override the legal entity default. The hierarchy from least to most specific is legal entity, then vendor, then item, then item and vendor. A more specific entry overrides a less specific one. This is the layer where three-way matching gets applied selectively to fixed-asset items or high-value categories without forcing every minor purchase through the same control.

Invoice matching setup > Price tolerances. Net unit price tolerance percentages are defined here. Levels include legal entity, vendor, vendor group, item, item group, and item and vendor combination, with the same inheritance principle. The Purchase price total tolerance percentage and amount on the AP parameters page govern price totals matching at the legal-entity level, with vendor-specific overrides available on Invoice totals tolerances.

The configuration choices that drive exception volume are the tolerance percentages and the matching policy granularity. Tight tolerances applied universally produce more exceptions than tight tolerances applied to selected items or vendor combinations.

How Dynamics 365 Finance flags discrepancies on vendor invoices

Matching calculations run automatically when an invoice is saved on the Vendor invoice page, or on demand if the legal entity is configured for manual matching. The automatically update invoice header status setting on AP parameters governs which mode applies.

On the Vendor invoice page, match variance icons appear next to lines that failed the check. The Last match status field on the invoice header shows Passed, Failed, or Not yet calculated. The Matching details page accessed from the Review tab shows the per-line breakdown of which test failed and by how much.

Invoice totals matching, if enabled, runs a separate check on six categories of totals, each with its own tolerance and variance icon: subtotal, total discount, charges, sales taxes, round-off, and invoice amount.

The flagging is preventive only if the post-invoice with discrepancies is set to Require approval or Block. With the parameter set to Allow, a flagged invoice can still post, and the variance icons become documentation rather than a control.

Resolving a matching exception and approving an invoice for payment

A failed invoice goes to the Pending vendor invoices list. From there, the review process moves through Matching details to identify which line failed and why.

Three resolution paths are available, each with a different consequence.

Accept the variance. If the parameter is set to Require approval, the variance must be explicitly approved (with an optional comment) before the invoice can post. The variance remains in the audit trail. This is the path when the difference is small, and the cost of pursuing the vendor exceeds the difference.

Revise the invoice amount or quantity. The invoice line can be edited to match the PO or product receipt. Posting then proceeds normally. This is the path when the invoice contains a vendor error that the AP team can correct unilaterally.

Reject the invoice. Request a credit and a corrected invoice from the vendor. The original invoice is removed; the corrected one is processed when it arrives. This is the path when the difference is material or the vendor is responsible for resolving it.

The choice of path is a control decision, not a system decision. The system enforces that one of these three actions happens before posting. Workflow configuration can route different variance sizes to different approvers, separating the line-level review from the posting authority.

Training an AP team on three-way matching and the wider invoice processing cycle? Start with our free user training starter kit, a 3-step video course with two downloadable templates for planning training around real D365 transactions.