About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.
Step by step, with screenshots
Set up Vendor reasons1 screen
Set up the reason codes that are recorded against vendor accounts and transactions.
Screen 1
Create the vendor reason code
Go to Accounts payable > Setup > Vendor reasons
Select New
Enter the reason code and default comment
Tick Vendor
1Reason code
BEAT-CRED
Default comment
Credit adjustment
Vendor
Yes
Show the full screen page title tab to open what to set or check
How to use it
Go to Accounts payable > Setup > Vendor reasons.
Select New to add a row.
Enter the Reason code and the Default comment.
Select the Vendor check box if it applies.
Select a row and select Edit to change it, or select Delete to remove it.
Source: Checked in Dynamics 365
Fields on the page
Field
What it means
Example
Table column
Reason code
The code that identifies the vendor reason.Checked in Dynamics 365
PrivilegesMaintain vendor reason codes VendReasonMaintainView vendor reason codes VendReasonViewDutiesEnable invoice and payment process VendInvoiceInvoicePaymentProcessEnableInquire into invoice and payment process reference data VendInvoiceInvoicePaymntProcessRefDataI3 security rolesAccounting manager LedgerAccountingManagerAccounting supervisor LedgerAccountingSupervisorAccounts payable manager VendInvoiceAccountsPayableManagerChecked in Dynamics 365
Roles to set it up and use it
To set it up or change itAccounts payable manager VendInvoiceAccountsPayableManagerAccounting supervisor LedgerAccountingSupervisorTo use itAccounting manager LedgerAccountingManagerGive people one of these roles. On this system, 3 roles can open this page.Checked in Dynamics 365
VendVendorReasonsEntity (Vendor reasons): loaded for each company, in Microsoft's default template 120 - Accounts payable.LedgerFinancialReasonEntity (Financial reasons): loaded for each company, in Microsoft's default template 025 - General ledger.Load order: Microsoft's default template 120 - Accounts payable loads Vendor reasons at execution unit 1, level 30, sequence 10. Lower levels load first, and entities at the same level load in sequence order.Load first: the default templates at lower levels (System setup to General ledger)Microsoft Learn
Checked in a working Dynamics 365 system, version 10.0.49: the menu item, form, table and security, the page, the demo records and the values in the screenshots.
To cite this step: AP-SETUP-180, Set up Vendor reasons. Beyond ERP Atlas Hub, 2026-11-11. https://www.beyonderp.cloud/atlas/step/AP-SETUP-180