BeyondERP.Subscribe

AP-INVMATCH-090 · Policy · Legal entity

Set the posting rule for invoices with discrepancies

No intent has been recorded for this step.

Where

Menu pathNot recordedUnverified
Menu itemNot recordedUnverified
FormNot recordedUnverified
Tables affectedNot recordedUnverified
Data entityVendorParameters
ScopeLegal entity
Country or regionNot recordedUnverified

Value

Recommended valueNot recordedUnverified
RationaleNot recordedUnverified
DecisionNot recorded

Dependencies and access

PrerequisitesAP-INVMATCH-030 Enable invoice matching validation
Required byNot recorded
Security dutyNot recordedUnverified
Feature flagNot recordedUnverified
Feature stateNot recorded

Versions

IntroducedNot recordedUnverified
Behaviour changedNot recorded
DeprecatedNot recorded
Verified on versionNot recorded
Verified on dateNot recorded

Risk and evidence

IrreversibilityReversible
Common pitfallNot recordedUnverified
Test caseNot recordedUnverified
AssetsNot recorded

Verification

Partly verified

Verified byPersonal sandbox metadata; USMF demo screenshot and scoped OData read 2026-09-26; Microsoft Learn
EnvironmentUSMF demo sandbox
NoteUSMF VendorParameters returned PostInvoiceMatchDiscrepancies=AllowWithWarning, displayed as Allow with warning on the supplied screenshot. This is the stored demo rule; no mismatched invoice was posted or tested. The AOT form, underlying table, security duty, full UI navigation, application version, test case and outcome remain unverified. See docs/T136-USMF-readonly-2026-09-26.md.
Still to checkApplies_to_country, Common_pitfall, Feature_flag, Form_name, Menu_item_name, Menu_path, Recommended_value, Security_duty, Tables_affected, Test_case_id, Value_rationale, Version_introduced

Cite this record

AP-INVMATCH-090 — Set the posting rule for invoices with discrepancies. Beyond ERP Config Atlas, snapshot 2026-10-05, partly verified. https://www.beyonderp.cloud/atlas/step/AP-INVMATCH-090