AP-INVMATCH-040 · Parameter · Legal entity
Set the default line matching policy
Establish whether invoice lines are validated against the PO only, or against the PO and the product receipt, as the organisation's default control level.
Where
| Menu path | Accounts payable > Setup > Accounts payable parametersUnverified |
|---|---|
| Menu item | Display:VendParameters |
| Form | Not recordedUnverified |
| Tables affected | Not recordedUnverified |
| Data entity | VendorParameters |
| Scope | Legal entity |
| Country or region | Not recordedUnverified |
Value
| Recommended value | Three-way matching for stocked items; two-way where no receipt is recorded (services, some indirect spend) |
|---|---|
| Rationale | Three-way matching is the control auditors expect for goods, but it fails operationally wherever receipting isn't actually performed — it will block invoices that have no receipt to match against. Do not set three-way globally unless receipting discipline is confirmed in the to-be process. |
| Decision | DEC-AP-001 · What level of invoice matching control applies, and does it vary by spend category? |
Dependencies and access
| Prerequisites | AP-INVMATCH-030 Enable invoice matching validation |
|---|---|
| Required by | AP-INVMATCH-050 Decide whether matching policy override is allowed |
| Security duty | Not recordedUnverified |
| Feature flag | Not recorded |
| Feature state | Not recorded |
Versions
| Introduced | Not recordedUnverified |
|---|---|
| Behaviour changed | Not recorded |
| Deprecated | Not recorded |
| Verified on version | Not recorded |
| Verified on date | Not recorded |
Risk and evidence
| Irreversibility | Reversible — Reversible in config; hard to reverse operationally once AP has trained on it and vendors have been told. |
|---|---|
| Common pitfall | Set to three-way in design workshops on the strength of an aspiration to receipt everything, then relaxed under go-live pressure. Decide against the actual receipting process, not the intended one. |
| Test case | Not recordedUnverified |
| Assets | Not recorded |
Verification
Partly verified
| Verified by | Microsoft business process catalog July 2026; personal sandbox metadata; USMF demo screenshot and scoped OData read 2026-09-26; Microsoft Learn |
|---|---|
| Environment | USMF demo sandbox |
| Note | USMF VendorParameters returned LineMatchingPolicy=NoMatch, displayed as Not required on the supplied screenshot. This is the demo's current default, not a change to the recommended two-/three-way design. Item/vendor exceptions and matching behavior were not tested. The AOT form, underlying table, security duty, full UI navigation, application version and outcome remain unverified. See docs/T136-USMF-readonly-2026-09-26.md. |
| Still to check | Applies_to_country, Form_name, Menu_path, Security_duty, Tables_affected, Test_case_id, Version_introduced |
Cite this record
AP-INVMATCH-040 — Set the default line matching policy. Beyond ERP Config Atlas, snapshot 2026-10-05, partly verified. https://www.beyonderp.cloud/atlas/step/AP-INVMATCH-040