Study guide
13.3 Invoice Matching Setup (2-Way, 3-Way), Tolerances & Exceptions
Microsoft Certified: Dynamics 365 Finance Functional Consultant Associate MB-310
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: MB-310 Exam Overview & Financial Architecture
1.1 MB-310 Exam Structure, Skills Measured & Consultant Role 1.2 Dynamics 365 Finance Architecture, Legal Entities & Global Address Book 1.3 Hands-on Lab Strategy & Preparation Framework
2 Chapter 2: Chart of Accounts & Main Accounts
2.1 Designing Chart of Accounts & Main Account Types 2.2 Main Account Categories & Ledger Account Aliases 2.3 Balance Control Accounts & Year-End Opening Account Setup 2.4 Legal Entity Overrides for Main Accounts & Dimensions
3 Chapter 3: Financial Dimensions & Account Structures
3.1 Custom & Entity-Backed Financial Dimensions 3.2 Financial Tags: Limits, Storage & Ledger Settlement Use 3.3 Account Structures, Segment Criteria & Activation 3.4 Advanced Rules & Advanced Rule Structures 3.5 Derived Dimensions & Dimension Default Templates
4 Chapter 4: Ledgers, Calendars & Currencies
4.1 Fiscal Calendars, Period Statuses & Module Access Control 4.2 Posting Layers, Multi-GAAP Reporting & the Ledger Form 4.3 Currency Exchange Types, Rate Providers & Triangulation 4.4 Accounting & Reporting Currencies (Dual-Currency Architecture) 4.5 Foreign Currency Revaluation & Revaluation Posting Profiles
5 Chapter 5: General Ledger Journals & Allocations
5.1 Journal Names & Voucher Number Sequences 5.2 Journal Control & Posting Restriction Rules 5.3 Journal Entry, the One-Voucher Rule, Validation & Posting 5.4 Reversals, Storno Corrections & Excel Integration 5.5 Ledger Allocation Rules & the Four Allocation Methods 5.6 Allocation Processing & Periodic (Recurring) Journals
6 Chapter 6: Intercompany Accounting & Settlements
6.1 Intercompany Accounting Setup & Due-To / Due-From Postings 6.2 Intercompany Journal Processing & Multi-Company Vouchers 6.3 Ledger Settlements Configuration & Processing
7 Chapter 7: Cash and Bank Management
7.1 Bank Groups, Bank Accounts & Ledger Integration 7.2 Payment Formats, Bank FX Revaluation & Shared Payment Setup 7.3 Manual vs. Advanced Bank Reconciliation & Statement Formats 7.4 Matching Rule Sets, Reconciliation Execution & Reversals 7.5 Cash Flow Forecasting Setup & Automation 7.6 Customer and Vendor Netting
8 Chapter 8: Periodic Closing & Financial Consolidations
8.1 Financial Period Close Workspace, Closing Roles & Schedules 8.2 Year-End Close Configuration & General Ledger Balance Carryforward 8.3 Consolidations Online: Legal Entity Setup, COA Mapping & Currency Translation 8.4 Import Consolidations & Intercompany Elimination Rules
9 Chapter 9: Sales Tax & Withholding Tax
9.1 Sales Tax Engine Hierarchy, Authorities & Settlement Periods 9.2 Ledger Posting Groups, Sales Tax Codes & Calculation Methods 9.3 Sales Tax Groups, Item Sales Tax Groups & Tax Exemptions 9.4 Sales Tax Adjustments and Settle and Post Sales Tax 9.5 Withholding Tax & US 1099 Vendor Reporting
10 Chapter 10: Accounts Receivable Setup & Invoicing
10.1 Customer Master, Customer Groups & Shared Customers 10.2 Customer Posting Profiles & Account Code Precedence 10.3 Free Text Invoices, Recurring Invoice Templates & AR Charges 10.4 Sales Order Invoicing, Billing Classifications & Prepayments 10.5 Customer Payment Methods, Payment Processing & Customer Bank Accounts
11 Chapter 11: Credit Management & Collections
11.1 Credit Management Architecture & Customer Credit Groups 11.2 Risk Scoring, Credit Limits, Blocking Rules & Credit Holds 11.3 Aging Definitions, Collections Workspace & Customer Pools 11.4 Collection Letter Sequences & Interest Notes 11.5 Customer Write-Offs, Bad Debt & Write-Off Reversals
12 Chapter 12: Subscription Billing & Revenue Deferrals
12.1 Recurring Contract Billing, Billing Schedules & Milestones 12.2 Deferral Principles, Deferral Defaults & Schedule Calculation Methods 12.3 Recognition Processing, Expense Deferrals & Modifying Schedules 12.4 Multiple Element Revenue Allocation (MEA / ASC 606)
13 Chapter 13: Accounts Payable & Invoice Processing
13.1 Shared Vendors, Global Address Book & Vendor Groups 13.2 Vendor Posting Profiles, AP Parameters & Vendor Bank Accounts 13.3 Invoice Matching Setup (2-Way, 3-Way), Tolerances & Exceptions 13.4 Vendor Invoicing Methods, Journals & Invoice Automation
14 Chapter 14: Vendor Payments & Expense Management
14.1 Methods of Payment & the Vendor Payment Proposal Engine 14.2 Generating Payments, Centralized Payments & Check Lifecycle 14.3 Expense Management Configuration, Categories & Policies 14.4 Expense Reports Processing, Mobile Receipts & Intercompany Expenses
15 Chapter 15: Budgeting & Budget Control
15.1 Budget Models, Budget Codes & Allocation Terms 15.2 Budget Register Entries, Workflows & Budget vs. Actual 15.3 Budget Transfer Rules & Processing Budget Transfers 15.4 Budget Control Configuration, Cycles, Rules & Budget Groups 15.5 Budget Funds Available, Over-Budget Permissions & Document Budget Check 15.6 Budget Planning Framework, Organization Hierarchies & Planning Processes 15.7 Budget Plans, Scenarios, Allocations & Generating Register Entries
16 Chapter 16: Fixed Assets Configuration & Transactions
16.1 Fixed Asset Groups, Asset Records & Group/Book Mapping 16.2 Depreciation Profiles: Methods & Conventions 16.3 Fixed Asset Books, Derived Books & Posting Profiles 16.4 Fixed Asset Acquisition Pathways 16.5 Depreciation Proposals, Multi-Company Runs & Fixed Asset Budgets 16.6 Fixed Asset Disposals: Sale, Scrap & Disposal Accounting 16.7 Fixed Asset Splits, Transfers & Reclassification 16.8 Asset Leasing (IFRS 16 / ASC 842)
13.3 Invoice Matching Setup (2-Way, 3-Way), Tolerances & Exceptions
Key Takeaways Explain This Topic AI
Accounts payable invoice matching (Accounts payable > Setup > Accounts payable parameters > Invoice validation) verifies unit prices, quantities, price totals, and charges across Purchase Orders, Product Receipts, and Vendor Invoices to ensure accurate vendor disbursements and inventory valuation.
Dynamics 365 Finance supports two primary matching policies: 2-way matching (validates Net Unit Price between Purchase Order and Invoice) and 3-way matching (validates Net Unit Price between PO and Invoice, AND validates Invoiced Quantity against Product Receipt Received Quantity).
Line matching policy resolution follows a strict four-level hierarchy: Purchase Order Line (highest priority) -> Item Master -> Vendor Master -> Accounts Payable Parameters / Legal Entity (lowest priority).
Price tolerances can be configured as Percentage Tolerances or Unit Price Amount Tolerances across Table, Group, and All scopes to define acceptable variance bands before an invoice fails matching.
When matching discrepancies exceed configured tolerances, the invoice status displays a failed matching icon, preventing posting until authorized via the 'Authorize posting with matching discrepancies' workflow or manual approval with audit reason codes.
Last updated: August 2026
13.3 Invoice Matching Setup (2-Way, 3-Way), Tolerances & Exceptions
Quick Summary: Accounts Payable invoice matching is a critical financial control framework in Microsoft Dynamics 365 Finance that protects organizations from overpaying vendors, billing for unreceived inventory, and absorbing unauthorized price increases or shipping charges. Configured under Accounts payable > Setup > Accounts payable parameters > Invoice validation , invoice matching automates the cross-verification of Purchase Orders , Product Receipts , and Vendor Invoices , enforcing strict 2-way or 3-way matching rules and configurable tolerance thresholds.
1. Invoice Matching Validation Framework & Master Parameters
The Accounts Payable invoice matching framework provides automated validation at the line level, charge level, and document total level. +---------------------------------------------------------------------------------------------------------+
- | Invoice Matching Core Configuration Matrix |
- +---------------------------------------------------------------------------------------------------------+
- | Parameter (`AP parameters > Invoice validation`) | Configuration Options | Operational Impact |
- | :----------------------------------------------- | :------------------------ | :---------------------- |
- | **Enable invoice matching validation** | Yes / No | Master toggle for engine|
- | **Automatically update invoice header status** | Yes / No | Live matching evaluation|
- | **Match invoice totals** | Yes / No | Header amount validation|
- | **Invoice totals tolerance percentage** | E.g., 1.00% / $50.00 | Allowable total variance|
- | **Line matching policy** (Legal Entity Default) | Not required / 2-way / 3-way| Company baseline policy |
- | **Price tolerance** | Percentage / Group link | Unit price variance band|
- | **Match charges** | Yes / No | Freight & fee validation|
- | **Require authorization for discrepancies** | Yes / No | Enforces approval lock |
- +---------------------------------------------------------------------------------------------------------+
- Core Validation Engines
Line Matching (2-Way / 3-Way): Compares unit prices and received physical quantities against invoice lines.
Price Totals Matching: Compares line extended net price totals against PO expected net totals.
Invoice Totals Matching: Compares gross invoice document totals (including taxes and charges) against purchase order expected totals.
Charges Matching: Compares miscellaneous markup/freight charges added to the invoice against approved purchase order charges.
2. 2-Way vs. 3-Way Matching Mechanics
Dynamics 365 Finance supports two primary matching policies that align with different procurement scenarios: +---------------------------------------------------------------------------------------------------------+
- | 2-Way vs. 3-Way Matching Comparison |
- +---------------------------------------------------------------------------------------------------------+
- | Feature / Dimension | 2-Way Matching | 3-Way Matching |
- | :------------------------ | :------------------------------------ | :--------------------------------- |
- | **Documents Compared** | 1. Purchase Order | 1. Purchase Order |
- | | 2. Vendor Invoice | 2. Product Receipt (Packing Slip) |
- | | | 3. Vendor Invoice |
- | ------------------------- | ------------------------------------- | ---------------------------------- |
- | **Validation Criteria** | - Net Unit Price (PO vs. Invoice) | - Net Unit Price (PO vs. Invoice) |
- | | - Line Amount Tolerance | - Quantity (Receipt vs. Invoice) |
- | | | - Line Amount Tolerance |
- | ------------------------- | ------------------------------------- | ---------------------------------- |
- | **Physical Receipt Req.** | **No.** Product receipt not required. | **Yes.** Invoiced Qty cannot exceed|
- | | Invoices can post prior to receipt. | posted Product Receipt quantity. |
- | ------------------------- | ------------------------------------- | ---------------------------------- |
- | **Best-Fit Procurement** | - Non-stock expense items | - Stocked inventory products |
- | | - Professional service contracts | - Physical raw materials & assets |
- | | - Procurement categories (Consulting) | - Tangible goods with warehouse flow|
- | ------------------------- | ------------------------------------- | ---------------------------------- |
- | **Matching Status Check** | `Invoice Net Price <= PO Net Price` | `Invoice Price <= PO Price` AND |
- | | (within configured price tolerance) | `Invoice Qty <= Receipt Qty` |
- +---------------------------------------------------------------------------------------------------------+
Note
A third option, Not required , completely bypasses invoice line matching validation. It is typically used for intercompany transactions or specialized service vendors where payment validation is performed externally.
3. Line Matching Policy Precedence Hierarchy
When a line item is added to a Purchase Order, Dynamics 365 Finance determines the effective line matching policy by evaluating a strict four-level hierarchy from most specific to broadest: +---------------------------------------------------------------------------------------------------+
- | Line Matching Policy Resolution Hierarchy |
- +---------------------------------------------------------------------------------------------------+
- | Precedence Level | Configuration Location | Scope / Description |
- | :---------------- | :---------------------------- | :------------------------------------------- |
- | **1 (Highest)** | **Purchase Order Line** | Explicit override on the specific PO line. |
- | **2** | **Item Master (Released Prod)**| `Released product > Purchase fasttab` |
- | **3** | **Vendor Master** | `Vendor master > Invoice and delivery fasttab`|
- | **4 (Lowest)** | **AP Parameters** | `AP parameters > Invoice validation` (Company)|
+---------------------------------------------------------------------------------------------------+ +---------------------------------------------------------------------------------------------------+
- | Hierarchy Resolution Decision Matrix Example |
- +---------------------------------------------------------------------------------------------------+
- | Scenario | AP Parameter | Vendor Master | Item Master | PO Line Override | Effective Policy Applied|
- | :--- | :----------- | :------------ | :---------- | :--------------- | :-----------------------|
- | **1**| 3-way | [Blank/Null] | [Blank/Null]| [Blank/Null] | **3-way** (From Parameter)|
- | **2**| 3-way | 2-way | [Blank/Null]| [Blank/Null] | **2-way** (Vendor wins) |
- | **3**| 3-way | 2-way | 3-way | [Blank/Null] | **3-way** (Item wins) |
- | **4**| 3-way | 3-way | 3-way | 2-way | **2-way** (PO Line wins)|
- +---------------------------------------------------------------------------------------------------+
Important
On the MB-310 exam, remember that PO Line always overrides Item , Item overrides Vendor , and Vendor overrides the legal entity AP Parameters default.
4. Price & Charges Tolerances Configuration
Tolerances establish allowable variance thresholds so minor penny variances or agreed-upon shipping uplifts do not stall invoice processing.
1. Price Tolerances Setup
Navigate to Accounts payable > Setup > Invoice matching > Price tolerances .
Configure tolerances using Percentage (e.g., 5.0%) or Unit price tolerance amount (e.g., $2.00).
Uses the Table / Group / All structure:
Table: Specific Item and Vendor combination.
Group: Item Price Tolerance Group or Vendor Price Tolerance Group.
All: Enterprise-wide fallback price tolerance. +---------------------------------------------------------------------------------------------------+
- | Price Tolerance Mathematical Calculation |
- +---------------------------------------------------------------------------------------------------+
- | Parameter / Field | Numerical Values |
- | :-------------------------------- | :------------------------------------------------------------- |
- | **Purchase Order Line Net Price** | $100.00 / unit |
- | **Configured Price Tolerance %** | 5.00% (Allowable range: $95.00 to $105.00) |
- | **Scenario A: Invoice Net Price** | **$104.00 / unit** -> **PASSED** (Variance +$4.00 is <= 5%) |
- | **Scenario B: Invoice Net Price** | **$108.00 / unit** -> **FAILED** (Variance +$8.00 exceeds 5%) |
- +---------------------------------------------------------------------------------------------------+
- 2. Charges Matching Tolerances Setup
Navigate to Accounts payable > Setup > Invoice matching > Charges tolerances .
Matches miscellaneous charges (e.g., Freight, Handling, Insurance) entered on the vendor invoice against charges on the original PO.
Allows defining maximum allowable charges variance percentages or fixed amounts per charge code.
3. Invoice Totals Tolerances Setup
Navigate to Accounts payable > Setup > Invoice matching > Invoice totals tolerances .
Validates the overall invoice gross amount against the expected PO total, catching unexpected roundings, unassigned fees, or miscalculated tax subtotals.
5. Handling Discrepancies, Matching Details & Authorization Workflow
When a vendor invoice is created in Pending vendor invoices ( Accounts payable > Invoices > Pending vendor invoices ), the system automatically computes matching results. +---------------------------------------------------------------------------------------------------------+
- | Invoice Matching Status Icons & Indicators |
- +---------------------------------------------------------------------------------------------------------+
- | Status Icon | Technical Status | Operational Meaning & Posting Eligibility |
- | :---------------- | :------------------- | :----------------------------------------------------------- |
- | 🟢 **Green Check** | **Passed** | All prices, quantities, and totals match PO / Receipts. |
- | | | **Eligible for immediate posting or touchless automation.** |
- | 🟡 **Yellow Sign** | **Passed w/ Warning**| Discrepancy exists but falls strictly within tolerances. |
- | | | **Eligible for posting without manual override.** |
- | 🔴 **Red X** | **Failed Matching** | Price, quantity, charge, or total exceeds allowable tolerance.|
- | | | **BLOCKED FROM POSTING until officially authorized.** |
- +---------------------------------------------------------------------------------------------------------+
- Investigating Variances: The Matching Details Form
To inspect a failed matching status:
Open the pending invoice and click Review > Matching details on the Action Pane.
The Invoice matching details form displays side-by-side comparisons:
Unit Price Comparison: PO Price vs. Invoice Price vs. Tolerance Amount.
Quantity Comparison: Ordered Qty vs. Product Receipt Qty vs. Invoiced Qty.
Match Status Highlights: Red highlights pinpoint the exact line item and variance type causing failure.
Resolving Discrepancies & Authorization Workflow
When an invoice fails matching, organizations have four operational resolution paths: +---------------------------------------------------------------------------------------------------+
- | Discrepancy Resolution Pathways |
- +---------------------------------------------------------------------------------------------------+
- | Resolution Path | Action Taken in D365 Finance |
- | :-------------------------- | :------------------------------------------------------------------ |
- | **1. Correct Invoice Data** | If clerk miskeyed price/qty, edit pending invoice line to match PO. |
- | **2. Post Pending Receipt** | If goods arrived but receipt unposted, post Product Receipt first. |
- | **3. Update Purchase Order**| Buyer amends PO (e.g., approved price increase) and re-confirms PO. |
- | **4. Authorize Override** | Authorized manager toggles 'Approve posting with matching |
- | | discrepancies' and submits Reason Code into audit log. |
- +---------------------------------------------------------------------------------------------------+
Tip
Enabling the Vendor invoice matching discrepancy approval workflow ( Accounts payable > Setup > Accounts payable workflows ) automatically routes failed invoices to designated department managers or procurement leads for electronic review, comment, and digital sign-off.
6. Critical Exam Traps & MB-310 Best Practices
Scenario / Exam Trap Common Misconception Correct D365 Finance Behavior
2-Way Match Quantity Check 2-Way matching checks whether the invoiced quantity matches the product receipt quantity. False. 2-Way matching validates only Net Unit Price against the PO. Product receipt quantity is validated exclusively under 3-Way matching.
Tolerance Precedence Table price tolerances apply only if Group and All tolerances are blank. False. D365 Finance evaluates Table tolerances first. If a Table rule matches the Item/Vendor, it is applied immediately, ignoring Group and All rules.
Posting Blocked Invoices An AP clerk can post an invoice with a Red X matching status if they have General Ledger posting rights. False. Posting is completely locked until the discrepancy is resolved, the PO/receipt is updated, or an authorized user approves the override.
Charges Tolerance Scope Charges tolerances apply to the entire invoice total. False. Charges tolerances validate individual miscellaneous charge codes (e.g., Freight code vs. PO Freight code). Invoice Totals tolerances validate overall document totals.