Study guide

13.2 Vendor Posting Profiles, AP Parameters & Vendor Bank Accounts

Microsoft Certified: Dynamics 365 Finance Functional Consultant Associate MB-310

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: MB-310 Exam Overview & Financial Architecture

1.1 MB-310 Exam Structure, Skills Measured & Consultant Role 1.2 Dynamics 365 Finance Architecture, Legal Entities & Global Address Book 1.3 Hands-on Lab Strategy & Preparation Framework

2 Chapter 2: Chart of Accounts & Main Accounts

2.1 Designing Chart of Accounts & Main Account Types 2.2 Main Account Categories & Ledger Account Aliases 2.3 Balance Control Accounts & Year-End Opening Account Setup 2.4 Legal Entity Overrides for Main Accounts & Dimensions

3 Chapter 3: Financial Dimensions & Account Structures

3.1 Custom & Entity-Backed Financial Dimensions 3.2 Financial Tags: Limits, Storage & Ledger Settlement Use 3.3 Account Structures, Segment Criteria & Activation 3.4 Advanced Rules & Advanced Rule Structures 3.5 Derived Dimensions & Dimension Default Templates

4 Chapter 4: Ledgers, Calendars & Currencies

4.1 Fiscal Calendars, Period Statuses & Module Access Control 4.2 Posting Layers, Multi-GAAP Reporting & the Ledger Form 4.3 Currency Exchange Types, Rate Providers & Triangulation 4.4 Accounting & Reporting Currencies (Dual-Currency Architecture) 4.5 Foreign Currency Revaluation & Revaluation Posting Profiles

5 Chapter 5: General Ledger Journals & Allocations

5.1 Journal Names & Voucher Number Sequences 5.2 Journal Control & Posting Restriction Rules 5.3 Journal Entry, the One-Voucher Rule, Validation & Posting 5.4 Reversals, Storno Corrections & Excel Integration 5.5 Ledger Allocation Rules & the Four Allocation Methods 5.6 Allocation Processing & Periodic (Recurring) Journals

6 Chapter 6: Intercompany Accounting & Settlements

6.1 Intercompany Accounting Setup & Due-To / Due-From Postings 6.2 Intercompany Journal Processing & Multi-Company Vouchers 6.3 Ledger Settlements Configuration & Processing

7 Chapter 7: Cash and Bank Management

7.1 Bank Groups, Bank Accounts & Ledger Integration 7.2 Payment Formats, Bank FX Revaluation & Shared Payment Setup 7.3 Manual vs. Advanced Bank Reconciliation & Statement Formats 7.4 Matching Rule Sets, Reconciliation Execution & Reversals 7.5 Cash Flow Forecasting Setup & Automation 7.6 Customer and Vendor Netting

8 Chapter 8: Periodic Closing & Financial Consolidations

8.1 Financial Period Close Workspace, Closing Roles & Schedules 8.2 Year-End Close Configuration & General Ledger Balance Carryforward 8.3 Consolidations Online: Legal Entity Setup, COA Mapping & Currency Translation 8.4 Import Consolidations & Intercompany Elimination Rules

9 Chapter 9: Sales Tax & Withholding Tax

9.1 Sales Tax Engine Hierarchy, Authorities & Settlement Periods 9.2 Ledger Posting Groups, Sales Tax Codes & Calculation Methods 9.3 Sales Tax Groups, Item Sales Tax Groups & Tax Exemptions 9.4 Sales Tax Adjustments and Settle and Post Sales Tax 9.5 Withholding Tax & US 1099 Vendor Reporting

10 Chapter 10: Accounts Receivable Setup & Invoicing

10.1 Customer Master, Customer Groups & Shared Customers 10.2 Customer Posting Profiles & Account Code Precedence 10.3 Free Text Invoices, Recurring Invoice Templates & AR Charges 10.4 Sales Order Invoicing, Billing Classifications & Prepayments 10.5 Customer Payment Methods, Payment Processing & Customer Bank Accounts

11 Chapter 11: Credit Management & Collections

11.1 Credit Management Architecture & Customer Credit Groups 11.2 Risk Scoring, Credit Limits, Blocking Rules & Credit Holds 11.3 Aging Definitions, Collections Workspace & Customer Pools 11.4 Collection Letter Sequences & Interest Notes 11.5 Customer Write-Offs, Bad Debt & Write-Off Reversals

12 Chapter 12: Subscription Billing & Revenue Deferrals

12.1 Recurring Contract Billing, Billing Schedules & Milestones 12.2 Deferral Principles, Deferral Defaults & Schedule Calculation Methods 12.3 Recognition Processing, Expense Deferrals & Modifying Schedules 12.4 Multiple Element Revenue Allocation (MEA / ASC 606)

13 Chapter 13: Accounts Payable & Invoice Processing

13.1 Shared Vendors, Global Address Book & Vendor Groups 13.2 Vendor Posting Profiles, AP Parameters & Vendor Bank Accounts 13.3 Invoice Matching Setup (2-Way, 3-Way), Tolerances & Exceptions 13.4 Vendor Invoicing Methods, Journals & Invoice Automation

14 Chapter 14: Vendor Payments & Expense Management

14.1 Methods of Payment & the Vendor Payment Proposal Engine 14.2 Generating Payments, Centralized Payments & Check Lifecycle 14.3 Expense Management Configuration, Categories & Policies 14.4 Expense Reports Processing, Mobile Receipts & Intercompany Expenses

15 Chapter 15: Budgeting & Budget Control

15.1 Budget Models, Budget Codes & Allocation Terms 15.2 Budget Register Entries, Workflows & Budget vs. Actual 15.3 Budget Transfer Rules & Processing Budget Transfers 15.4 Budget Control Configuration, Cycles, Rules & Budget Groups 15.5 Budget Funds Available, Over-Budget Permissions & Document Budget Check 15.6 Budget Planning Framework, Organization Hierarchies & Planning Processes 15.7 Budget Plans, Scenarios, Allocations & Generating Register Entries

16 Chapter 16: Fixed Assets Configuration & Transactions

16.1 Fixed Asset Groups, Asset Records & Group/Book Mapping 16.2 Depreciation Profiles: Methods & Conventions 16.3 Fixed Asset Books, Derived Books & Posting Profiles 16.4 Fixed Asset Acquisition Pathways 16.5 Depreciation Proposals, Multi-Company Runs & Fixed Asset Budgets 16.6 Fixed Asset Disposals: Sale, Scrap & Disposal Accounting 16.7 Fixed Asset Splits, Transfers & Reclassification 16.8 Asset Leasing (IFRS 16 / ASC 842)

13.2 Vendor Posting Profiles, AP Parameters & Vendor Bank Accounts

Key Takeaways Explain This Topic AI

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.

Last updated: August 2026

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 Group 10 ), 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 ).

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.

Loading diagram... Global Address Book, Vendor Hierarchy, Posting Profile Resolution, and GL Flow