13.2 Vendor Posting Profiles, AP Parameters & Vendor Bank Accounts
Key Takeaways
- A vendor posting profile maps summary (control), settlement discount, and other accounts, resolved by Table, then Group, then All.
- The default posting profile in Accounts payable parameters is used when a transaction does not specify one.
- Vendor bank accounts hold the IBAN, routing, and SWIFT details used by electronic payment formats.
- Change-based approval workflow on vendor bank details is the standard control against payment-diversion fraud.
13.2 Vendor Posting Profiles, AP Parameters & Vendor Bank Accounts
Quick Summary: Vendor posting profiles connect the Accounts payable subledger to general ledger control accounts using the same Table/Group/All precedence as Accounts receivable. This section also covers vendor bank account setup and the approval workflow that protects bank detail changes.
1. Vendor Posting Profiles Architecture & Account Types
Vendor posting profiles (Accounts payable > Setup > Vendor posting profiles) establish the core accounting bridge between the Accounts Payable subledger and the General Ledger Chart of Accounts. They dictate exactly which balance sheet and clearing accounts receive debits and credits during vendor transactions.
+---------------------------------------------------------------------------------------------------------+
| Vendor Posting Profile Account Matrix |
+---------------------------------------------------------------------------------------------------------+
| Account Type | Ledger Nature | Functional Trigger / Transaction Flow |
| :---------------------- | :------------------ | :-------------------------------------------------------|
| **Summary account** | Balance Sheet Liab. | Credited when posting vendor invoices (AP Liability). |
| | (e.g., 200100) | Debited when posting vendor payments or credit memos. |
| ----------------------- | ------------------- | ------------------------------------------------------- |
| **Settle account** | Balance Sheet / P&L | Used for automatic settlement write-offs, minor penny |
| | (e.g., 200190) | differences, and settlement clearing reconciliations. |
| ----------------------- | ------------------- | ------------------------------------------------------- |
| **Arrival account** | Balance Sheet Liab. | Debited/Credited during Step 1 of the 2-step Invoice |
| | (e.g., 200200) | Register process to record interim unapproved liability.|
| ----------------------- | ------------------- | ------------------------------------------------------- |
| **Offset arrival** | Balance Sheet Clear.| Offset account used in Invoice Register posting prior to |
| | (e.g., 200210) | formal departmental expense approval (Step 2). |
| ----------------------- | ------------------- | ------------------------------------------------------- |
| **Prepayment account** | Balance Sheet Asset | Debited when recording an advance vendor prepayment |
| | (e.g., 140200) | before final purchase goods/invoices are received. |
+---------------------------------------------------------------------------------------------------------+
The Table / Group / All Precedence Hierarchy
Posting profiles utilize Microsoft Dynamics 365 Finance's standard Table / Group / All relationship hierarchy to resolve conflicting account mapping rules:
+---------------------------------------------------------------------------------------------------+
| Posting Profile Precedence Resolution Hierarchy |
+---------------------------------------------------------------------------------------------------+
| Precedence Level | Account Code | Scope / Target | System Evaluation Rule |
| :---------------- | :----------- | :----------------------------- | :--------------------------- |
| **1 (Highest)** | **Table** | Specific Single Vendor Account | Matches exact Vendor ID |
| **2 (Middle)** | **Group** | Specific Vendor Group | Matches Vendor Group ID |
| **3 (Lowest)** | **All** | All Vendors in Legal Entity | Catch-all fallback rule |
+---------------------------------------------------------------------------------------------------+
+---------------------------------------------------------------------------------------------------+
| Worked Hierarchy Example: Summary Account Resolution |
+---------------------------------------------------------------------------------------------------+
| Rule | Account Code | Account / Group Number | Summary Main Account | Applied Scenario |
| :--- | :----------- | :--------------------- | :------------------- | :--------------------------- |
| **A**| **Table** | `VEND-00109` (Strategic) | `200110` (Key AP) | Only Vendor `VEND-00109` |
| **B**| **Group** | `10` (Domestic Vendors) | `200100` (Trade AP) | All Group 10 except 00109 |
| **C**| **Group** | `20` (Foreign Vendors) | `200150` (Foreign AP) | All Group 20 vendors |
| **D**| **All** | `[Blank]` | `200199` (General AP) | Any other vendor group |
+---------------------------------------------------------------------------------------------------+
[!IMPORTANT] If an invoice is posted for vendor
VEND-00109(who belongs to Vendor Group10), Dynamics 365 Finance selects Rule A (200110 - Key AP) because Table has higher priority than Group (Rule B) and All (Rule D).
2. Accounts Payable Parameters & Default Posting Profile Assignment
System-wide posting profile defaults are configured under Accounts payable > Setup > Accounts payable parameters > Ledger and sales tax:
+---------------------------------------------------------------------------------------------------------+
| Accounts Payable Parameter Posting Defaults |
+---------------------------------------------------------------------------------------------------------+
| Parameter Field | Default Value | Functional Role & Application |
| :------------------------------ | :------------ | :---------------------------------------------------- |
| **Posting profile** | `GEN` | Standard posting profile applied to Purchase Orders, |
| | | Vendor Invoice Journals, and Pending Invoices. |
| ------------------------------- | ------------- | ----------------------------------------------------- |
| **Posting profile with** | `PRE` | Mandatory posting profile assigned when creating and |
| **prepayment** | | settling Vendor Prepayment Invoices / Advance Payments.|
+---------------------------------------------------------------------------------------------------------+
Posting Profile Overrides on Documents
While the AP parameter establishes the system default, users with appropriate security permissions can override the posting profile on:
- Purchase Order Header:
Purchase order > Header view > Setup > Posting profile. - Vendor Invoice Journal Lines:
Invoice journal > Lines > General tab > Posting profile. - Pending Vendor Invoice Header:
Pending vendor invoice > Header > Setup > Posting profile.
3. Vendor Bank Accounts & Approval Workflow for Bank Changes
To prevent internal fraud, social engineering, and unauthorized modification of supplier disbursement accounts, Dynamics 365 Finance incorporates a dedicated Vendor bank account change management and approval workflow.
+---------------------------------------------------------------------------------------------------------+
| Vendor Bank Account Security Framework |
+---------------------------------------------------------------------------------------------------------+
| |
| +--------------------------+ +-------------------------------+ +-------------------+ |
| | User Modifies / Adds | ------> | Bank Record Placed 'In Review'| ------> | Automated Workflow| |
| | Vendor Bank Account | | Vendor On Payment Hold | | Routes to Approver| |
| +--------------------------+ +-------------------------------+ +-------------------+ |
| | |
| v |
| +--------------------------+ +-------------------------------+ +-------------------+ |
| | Payments Allowed to New | <------ | Status Changes to 'Approved' | <------ | Financial Officer | |
| | Verified Bank Account | | Payment Hold Released | | Verifies & Approves| |
| +--------------------------+ +-------------------------------+ +-------------------+ |
+---------------------------------------------------------------------------------------------------------+
Configuration & Security Mechanics
- Vendor Bank Accounts Form (
Accounts payable > Vendors > All vendors > Vendor tab > Bank accounts): Stores bank name, routing number/transit code, IBAN, SWIFT/BIC code, and bank account currency. - Enable Vendor Change Management / Bank Workflow:
- Under
Accounts payable > Setup > Accounts payable parameters > General > Vendor change management, activate change management for critical fields. - Configure the Vendor bank account approval workflow (
Accounts payable > Setup > Accounts payable workflows).
- Under
- Administrative Hold on Modification: When an existing bank account's IBAN or routing number is modified, or a new bank account is created:
- The bank record status transitions to In review / Pending approval.
- The vendor can automatically be placed on Payment Hold (Hold type: Payment or All).
- Any payment proposal batch job attempting to generate Electronic Funds Transfer (EFT/ACH) or wire payments to the unapproved bank account is blocked.
- Audit History & Approval: An authorized financial controller reviews the change history in the Proposed changes form, validates external verification documentation (e.g., bank letter or voice confirmation), and approves the workflow, releasing the hold for payment processing.
4. Critical Exam Traps & MB-310 Best Practices
| Scenario / Exam Trap | Common Misconception | Correct D365 Finance Behavior |
|---|---|---|
| Posting Profile Resolution | An 'All' posting profile rule overrides a 'Group' rule if configured with a more recent date. | False. D365 Finance always evaluates Table first, then Group, and finally All, regardless of creation date or description. |
| Shared Vendor Deletion | Deleting a vendor in USMF deletes the vendor and its GAB party record across all legal entities. | False. Deleting a vendor removes only the legal entity subledger record (VendTable in USMF). The global party record (DirPartyTable) remains intact in the GAB and other entities. |
| Prepayment Accounting | Prepayments debit the Summary Account defined in the standard posting profile. | False. Prepayments must use a dedicated Prepayment Posting Profile mapped to a Balance Sheet asset account (e.g., Prepayments to Vendors) to avoid distorting trade AP liabilities. |
| Bank Account Hold Behavior | Creating a new bank account allows immediate payment processing if the vendor master is active. | False. If the Vendor Bank Account Approval Workflow is active, the new bank account remains locked for payment proposals until approved. |
An Accounts Payable manager at a manufacturing corporation is configuring Vendor Posting Profiles in Dynamics 365 Finance. The company has defined three rules for Summary accounts in the 'GEN' posting profile:
Vendor V-100 belongs to Vendor Group 10. When an Accounts Payable clerk posts a $15,000 inventory invoice for vendor V-100, which General Ledger main account is credited for the Accounts Payable liability?
To enhance internal controls and comply with SOX auditing guidelines, a corporation requires that whenever a vendor's bank disbursement details (IBAN, routing number, or bank account) are created or modified in Dynamics 365 Finance, automated vendor payments must be blocked until the changes are formally reviewed and approved by the Treasury Controller. Which set of configurations satisfies this requirement?