13.1 Shared Vendors, Global Address Book & Vendor Groups
Key Takeaways
- 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.
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 vendorsin 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 IndustrialisV-0001in USMF andV-0247in 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.
A multinational enterprise operating in Dynamics 365 Finance procures raw materials from supplier 'Acme Industrial' across two legal entities: USMF (United States) and DEMF (Germany). The accounting team needs to set up Acme Industrial in DEMF while ensuring that global party information, registered business addresses, and tax identifiers are shared with the existing USMF setup, but with distinct payment terms (Net 60 for DEMF vs. Net 30 for USMF) and distinct euro bank accounts. How should the Functional Consultant configure this requirement?
A consultant changes the terms of payment on the DOMESTIC vendor group from Net 30 to Net 45. Existing vendors in that group continue to produce invoices with 30-day due dates. What explains this?