Study guide

13.1 Shared Vendors, Global Address Book & Vendor Groups

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.1 Shared Vendors, Global Address Book & Vendor Groups

Key Takeaways Explain This Topic AI

Vendors are Global Address Book parties, so one supplier can exist in multiple legal entities under a single party record.

Cross-company data sharing replicates the vendor master to participating legal entities so master data is maintained once.

The vendor group defaults terms of payment, settlement period, and the vendor posting profile.

Vendor account numbers must be consistent across entities for sharing, which normally requires a shared number sequence.

Last updated: August 2026

13.1 Shared Vendors, Global Address Book & Vendor Groups

Quick Summary: Managing supplier relationships and Accounts Payable liabilities in Microsoft Dynamics 365 Finance requires a robust foundational setup. By leveraging the Global Address Book (GAB) , organizations maintain a single master party record for a supplier while configuring entity-specific commercial terms, tax profiles, and ledger posting controls across multiple legal entities. Vendor posting profiles act as the subledger-to-General Ledger bridge, directing invoice balances, settlements, arrival hold accounts, and advance prepayments to designated balance sheet accounts following a strict Table / Group / All precedence hierarchy.

1. Global Address Book (GAB) & Shared Vendor Architecture

In Dynamics 365 Finance, every vendor record is built upon the Global Address Book (GAB) . A vendor is not simply a row in a single company's ledger; it is linked to a global Party record ( DirPartyTable ) that centralizes core organizational data across the entire enterprise. +---------------------------------------------------------------------------------------------------------+

  • | Global Address Book (GAB) Shared Architecture |
  • +---------------------------------------------------------------------------------------------------------+
  • | |
  • | +------------------------------+ |
  • | | GLOBAL PARTY RECORD | |
  • | | Party ID: PARTY-000842 | |
  • | | Name: Fabrikam Logistics | |
  • | | Type: Organization / Co. | |
  • | | Tax ID / Addresses / Ph. | |
  • | +------------------------------+ |
  • | | |
  • | +------------------------------+------------------------------+ |
  • | | | |
  • | v v |
  • | +-----------------------------------+ +-----------------------------------+ |
  • | | LEGAL ENTITY: USMF (US Entity) | | LEGAL ENTITY: DEMF (DE Entity) | |
  • | | Vendor ID: VEND-00101 | | Vendor ID: DE-VEND-501 | |
  • | | Vendor Group: 10 (Domestic) | | Vendor Group: EU-CORP | |
  • | | Currency: USD | | Currency: EUR | |
  • | | Terms of Payment: Net 30 | | Terms of Payment: Net 60 | |
  • | | Posting Profile: GEN | | Posting Profile: EU-GEN | |
  • | | Bank: Chase Commercial USD | | Bank: Deutsche Bank EUR | |
  • | +-----------------------------------+ +-----------------------------------+ |
  • +---------------------------------------------------------------------------------------------------------+
  • Dual-Layer Vendor Architecture

Shared Party Layer ( DirPartyTable ): Shared across all legal entities. Contains legal name, registered business addresses, electronic contact information (phone, email), global tax identification numbers, and relationship hierarchies.

Legal Entity Subledger Layer ( VendTable ): Specific to the operating legal entity ( DataAreaId ). Controls transactional accounting parameters, including:

Vendor Group: Determines default terms, settlement rules, and posting behavior.

Currency & Payment Terms: Base transactional currency, cash discount codes, and payment schedules.

Vendor Posting Profile: Directs subledger transactions to legal-entity-specific GL accounts.

Tax Configuration: Sales tax group, 1099/1042-S tax reporting codes, and withholding tax groups.

Bank Account Setup: Legal-entity-specific bank disbursement accounts and remit-to specifications.

Shared Vendor Master Workflow

When adding an existing enterprise vendor to a new legal entity:

Navigate to Accounts payable > Vendors > All vendors in the target legal entity.

Click New and select the existing Party ID or begin typing the vendor's legal name in the Name field.

Dynamics 365 Finance identifies the existing GAB record and prompts to associate the new vendor ID with the existing Party record.

Address books, tax IDs, and global contact records synchronize automatically, preventing duplicate master data and enabling enterprise-wide vendor spend reporting.

2. Vendor Groups Setup & Master Defaults

Vendor groups ( Accounts payable > Setup > Vendors > Vendor groups ) represent the primary organizational and categorization mechanism for vendor subledger records. Every vendor master must be assigned to exactly one Vendor Group. +---------------------------------------------------------------------------------------------------+

  • | Vendor Group Configuration Matrix |
  • +---------------------------------------------------------------------------------------------------+
  • | Configuration Parameter | Functional Impact / Purpose | Inherited Default Level|
  • | :------------------------- | :---------------------------------------- | :--------------------- |
  • | **Vendor group ID** | Unique alphanumeric key (e.g., 10, 20, FOR)| Master Group Key |
  • | **Description** | Business categorization (e.g., Domestic) | Reporting Categoriz. |
  • | **Terms of payment** | Default payment due date calculation | Vendor Master Default |
  • | **Settlement period** | Sales tax settlement period linkage | Tax Settlement Default |
  • | **Default tax group** | Item sales tax / Sales tax calculation | Tax Group Default |
  • | **Default posting group** | Default ledger posting group assignment | Posting Profile Mapping|
  • | **Exclude from automation**| Excludes group from touchless processing | Invoice Automation Opt |
  • | **Time between invoice** | Minimum lead time required between invs | Operational Control |
  • +---------------------------------------------------------------------------------------------------+
  • Core Functional Roles of Vendor Groups

Subledger Parameter Defaulting: When a new vendor is created, selecting a Vendor Group instantly populates mandatory transactional attributes (Payment Terms, Cash Discounts, Sales Tax Group), reducing data entry errors.

Vendor Posting Profile Grouping: Posting profiles can bind GL main accounts to an entire Vendor Group rather than configuring individual vendor accounts one by one.

Financial Reporting & Aging Analytics: Vendor aging reports, cash flow forecasts, and AP trial balances utilize Vendor Groups as standard primary sorting, filtering, and summarizing dimensions.

3. What a Vendor Group Actually Defaults

The vendor group is the defaulting layer between the Global Address Book party and the individual vendor record. Setting it correctly removes most repetitive data entry and most posting errors.

  • Vendor group field Defaults onto the vendor Consequence if wrong
  • Terms of payment Due date calculation on every invoice Payment proposals select the wrong invoices
  • Settle period (settlement period) Cash discount timing Discounts are missed or wrongly taken
  • Vendor posting profile The general ledger control account used Posting fails or hits the wrong summary account
  • Default tax group Sales tax calculation on purchases Under- or over-accrued use tax
  • Number sequence group Vendor account numbering Breaks shared-vendor alignment across entities

Group defaults are copied at the moment the vendor is created. Changing the group later does not retroactively update existing vendors, which is why a mid-project change to a group's terms of payment appears to have no effect.

4. Setting Up Shared Vendors Step by Step

Confirm the vendors to be shared exist as a single Global Address Book party — the same legal person, not two similarly named parties.

Align the vendor account number sequence across the participating legal entities, normally by using a shared number sequence. Sharing fails if Acme Industrial is V-0001 in USMF and V-0247 in DEMF.

Configure cross-company data sharing for the vendor tables in System administration > Setup > Configure cross-company data sharing , adding each participating legal entity to the sharing policy.

Enable the policy and let the initial synchronisation run.

Validate that a change made in one entity replicates to the others.

What Is Shared and What Is Not

Data Shared across entities?

  • Vendor name, party, addresses, contact details Yes
  • Vendor group assignment Yes, if the group codes exist in every entity
  • Vendor posting profile No — resolved per legal entity
  • Vendor transactions and balances No — each entity keeps its own subledger
  • Vendor bank accounts Depends on the sharing policy scope

This split is the point of the design: one supplier identity, but each legal entity keeps its own ledger, its own control accounts, and its own payable balance. On a case study, the phrase "maintain the supplier once but keep separate balances per company" is a direct pointer to shared vendors through cross-company data sharing — not to a single legal entity, and not to intercompany trade.

Exam trap: Shared vendors do not create intercompany transactions. If USMF buys from a sister legal entity rather than from an external supplier, that is intercompany trade and needs intercompany accounting setup, not vendor sharing.