DEC-AP-001 · Design decision
What level of invoice matching control applies, and does it vary by spend category?
A decision a human must make between defensible options. The configuration records it governs cannot be completed until it is taken.
Partly verified
Options
ATwo-way globally — lowest friction, weakest control.BThree-way globally — strongest control, blocks any unreceipted spend.CThree-way default with two-way overrides for defined vendor/item groups — strongest fit, highest config and maintenance cost.Recorded recommendation
| Recommendation | C, where indirect spend is material. A or B only where the spend profile is genuinely uniform. |
|---|---|
| Depends on |
|
| Owner | Finance process owner + AP lead |
| FDD wording | Not recordedUnverified |
Configuration it governs
AP-INVMATCH-040Set the default line matching policyParameter · Accounts payable > Setup > Accounts payable parametersProcess: Perform invoice matching in Dynamics 365 Finance
Partly verifiedAP-INVMATCH-050Decide whether matching policy override is allowedParameter · Accounts payable > Setup > Accounts payable parametersProcess: Perform invoice matching in Dynamics 365 Finance
Partly verifiedAP-INVMATCH-070Define price tolerances by item, vendor or combinationMaster data · Accounts payable > Invoice matching setup > Price tolerancesProcess: Perform invoice matching in Dynamics 365 Finance
Partly verifiedVerification
| Verified by | Microsoft business process catalog July 2026 |
|---|---|
| Environment | Not recorded |
| Note | Transcribed verbatim from the DEC-AP-001 worked example in the v0.1 step model. fdd_wording is a placeholder in the source and is left null rather than drafted, since the wording is owner IP and not derivable. Corroborated by the July 2026 catalog, which splits the invoice matching scenario 75.50.020.300 into exactly this fork at level 5: 75.50.020.300.100 Perform two-way invoice matching and 75.50.020.300.200 Perform three-way invoice matching. That is structural confirmation that the two-way / three-way choice is the real decision point, not a preference. Option C, the mixed model, has no catalog equivalent - it is Beyond ERP ground. |
| Still to check | Fdd_wording |
| Source | https://aka.ms/BusinessProcessCatalog |