AP-INVMATCH-030 · Parameter · Legal entity
Enable invoice matching validation
Turn on the control that compares vendor invoice lines against purchase order and receipt data before posting, so price and quantity discrepancies are caught at entry rather than at reconciliation.
Where
| Menu path | Accounts payable > Setup > Accounts payable parametersUnverified |
|---|---|
| Menu item | Display:VendParameters |
| Form | VendParametersUnverified |
| Tables affected | VendParametersUnverified |
| Data entity | VendorParameters |
| Scope | Legal entity |
| Country or region | Not recordedUnverified |
Value
| Recommended value | Yes |
|---|---|
| Rationale | Without this, the matching policy, tolerance and discrepancy settings downstream have no effect. Every subsequent step in this process is inert until it is on — which is why it sequences before them rather than alongside. |
| Decision | Not recorded |
Dependencies and access
| Prerequisites | AP-INVMATCH-010 Confirm procurement and AP number sequences exist |
|---|---|
| Required by | AP-INVMATCH-040 Set the default line matching policy, AP-INVMATCH-060 Configure price total matching and tolerance, AP-INVMATCH-090 Set the posting rule for invoices with discrepancies, AP-INVMATCH-100 Assign matching-related duties to AP roles |
| Security duty | Maintain accounts payable parametersUnverified |
| Feature flag | Not recorded |
| Feature state | Not recorded |
Versions
| Introduced | Long-standing baseline capabilityUnverified |
|---|---|
| Behaviour changed | Not recorded |
| Deprecated | Not recorded |
| Verified on version | Not recorded |
| Verified on date | Not recorded |
Risk and evidence
| Irreversibility | Reversible — Switching it on mid-project changes behaviour for in-flight invoices. |
|---|---|
| Common pitfall | Enabled in one legal entity during a pilot and never replicated to the others, so matching silently does nothing in the entities that went live later. It is per-legal-entity, and there is no cross-entity warning. |
| Test case | TC-AP-INVMATCH-01 · Matching validation test pack |
| 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 | The July 2026 catalog and Microsoft Learn support this control. USMF VendorParameters returned EnableInvoiceMatchingValidation=Yes, matching the supplied Invoice validation screenshot. This is a stored demo setting, not an operational test or an Atlas recommendation. 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, Version_introduced |
Cite this record
AP-INVMATCH-030 — Enable invoice matching validation. Beyond ERP Config Atlas, snapshot 2026-10-05, partly verified. https://www.beyonderp.cloud/atlas/step/AP-INVMATCH-030