10.1 Customer Master, Customer Groups & Shared Customers

Key Takeaways

  • Every customer is a Global Address Book party, which is what allows the same legal person to exist in several legal entities.
  • The customer group defaults terms of payment, settlement period, and the posting profile used for the customer's transactions.
  • Shared customers use cross-company data sharing so one customer record is maintained centrally and replicated to participating legal entities.
  • Customer account numbers must align across entities for sharing to work, which usually means a shared number sequence.
Last updated: August 2026

10.1 Customer Master, Customer Groups & Shared Customers

Quick Summary: Accounts Receivable (AR) in Microsoft Dynamics 365 Finance tracks and manages outgoing customer invoices, incoming collections, customer credit limits, and subledger accounting. At the foundation of AR are three core architectural components: Customer Master Records (built upon the Global Address Book framework), Customer Groups (which standardize payment terms, tax groups, and default accounting rules across customer segments), and Customer Posting Profiles (which dynamically map subledger transaction events to specific balance sheet control accounts in the General Ledger). Mastering how these elements interact—and how the Table / Group / All precedence rule resolves accounting control accounts—is a core requirement for passing the MB-310 exam and architecting robust order-to-cash implementations.


1. Architectural Overview of Accounts Receivable Subledger

Dynamics 365 Finance uses an integrated subledger architecture. Customer transactions (sales orders, free text invoices, payment journals, credit notes, and collection letters) post detailed transaction histories to the Customer Subledger (CustTrans and CustTransOpen tables) while generating balanced vouchers in the General Ledger (GeneralJournalEntry and GeneralJournalAccountEntry tables).

+---------------------------------------------------------------------------------------------------------+
|                         Accounts Receivable Subledger to General Ledger Architecture                    |
+---------------------------------------------------------------------------------------------------------+
|                                                                                                         |
|     PARTY CONTEXT (Global Address Book)                  LEGAL ENTITY CONTEXT (USMF / DEMF)             |
|     [ Global Party Record: Organization / Person ] ----> [ Customer Master: CUST-001001 ]               |
|                                                                      |                                  |
|                                                                      v                                  |
|                                                          +-----------------------+                      |
|                                                          |    Customer Group     |                      |
|                                                          |  - Terms of Payment   |                      |
|                                                          |  - Default Tax Group  |                      |
|                                                          |  - Revenue Account    |                      |
|                                                          +-----------------------+                      |
|                                                                      |                                  |
|                                                                      v                                  |
|                                                          +-----------------------+                      |
|                                                          |   Posting Profile     |                      |
|                                                          |  (Table / Group / All)|                      |
|                                                          +-----------------------+                      |
|                                                                      |                                  |
|                 +----------------------------------------------------+------------------+               |
|                 |                                                                       |               |
|                 v                                                                       v               |
|     +------------------------------+                               +------------------------------+     |
|     |  Customer Subledger Impact   |                               |    General Ledger Voucher    |     |
|     |  - CustTrans (Invoice Entry) |                               |  - Dr. AR Summary Control    |     |
|     |  - CustTransOpen (Balance)   |                               |  - Cr. Sales Revenue         |     |
|     |  - Aging & Credit Exposure   |                               |  - Cr. Sales Tax Payable     |     |
|     +------------------------------+                               +------------------------------+     |
+---------------------------------------------------------------------------------------------------------+

Unlike standalone entry systems, users never enter a raw Accounts Receivable control account on a sales document. Instead, the posting engine evaluates the customer's assigned Customer Posting Profile to dynamically determine the appropriate GL balance sheet control account.


2. Customer Master Record Setup & Global Address Book (GAB)

Every customer account created in Dynamics 365 Finance represents a business relationship established within a specific Legal Entity linked to a centralized Party in the Global Address Book.

Navigation

  • Path: Accounts receivable > Customers > All customers
+---------------------------------------------------------------------------------------------+
|                             Customer Master Anatomy: [ US-001 ]                             |
+---------------------------------------------------------------------------------------------+
| Header Details:                                                                             |
| - Account: [ US-001 ]                   - Name: [ Contoso Retail San Diego ]                |
| - Party ID: [ Party-99402 ]             - Customer Group: [ 10 - Commercial Wholesale ]     |
| - Currency: [ USD ]                     - Search Name: [ CONTOSO_SD ]                       |
+---------------------------------------------------------------------------------------------+
| Invoice and Delivery FastTab:                                                               |
| - Sales Tax Group: [ CA_SAN_DIEGO ]     - Terms of Payment: [ Net30 ]                       |
| - Method of Payment: [ CHECK ]          - Cash Discount: [ 2% 10 Net 30 ]                   |
| - Delivery Terms: [ FOB_DEST ]          - Mode of Delivery: [ GROUND ]                      |
+---------------------------------------------------------------------------------------------+
| Credit and Collections FastTab:                                                             |
| - Credit Limit: [ $250,000.00 ]         - Mandatory Credit Limit: [ Yes ]                   |
| - Credit Management Group: [ TIER_1 ]   - Temporary Credit Limit: [ $0.00 ]                 |
+---------------------------------------------------------------------------------------------+
| Ledger and Sales Tax FastTab:                                                               |
| - Posting Profile: [ (Blank - Inherit Default) ] -> Resolves to AR Parameters 'GEN'        |
| - Withholding Tax Group: [ (Blank) ]    - Tax Exempt Number: [ (Blank) ]                    |
+---------------------------------------------------------------------------------------------+

Party Record vs. Customer Record

Understanding the separation between the Global Address Book Party and the Legal Entity Customer record is critical for enterprise architectures:

Attribute / FieldGlobal Address Book (Party Record)Legal Entity Customer Record
ScopeCross-Company / Enterprise-wideSpecific to a single Legal Entity (e.g., USMF)
Data ElementsLegal Name, Organization Type, Physical Addresses, Phone/Email, ContactsCustomer Account Number, Credit Limit, Payment Terms, Posting Profile, Currency
Sharing MechanismAutomatically shared across all legal entitiesIsolated subledger master, linked via PartyID
Address ChangesUpdating an address on the party updates the address across all linked customer and vendor rolesLocal delivery addresses can be designated for specific shipping operations

3. Customer Groups Configuration & Defaulting Dynamics

Customer Groups categorize customers for operational, financial, and reporting purposes. Every customer must belong to exactly one customer group.

Navigation

  • Path: Accounts receivable > Setup > Customer groups
+---------------------------------------------------------------------------------------------------+
|                                 Customer Groups Configuration Grid                                |
+---------------------------------------------------------------------------------------------------+
| Customer Group | Description                | Terms of Payment | Settlement Period | Default Tax Group |
| -------------- | -------------------------- | ---------------- | ----------------- | ----------------- |
| **10**         | Commercial Wholesale       | `Net30`          | `MONTHLY`         | `COMM_TAX`        |
| **20**         | Enterprise Retail Chains   | `Net60`          | `MONTHLY`         | `RETAIL_TAX`      |
| **30**         | Government & Public Sector | `Net45`          | `QUARTERLY`       | `EXEMPT_GOV`      |
| **INTERCO**    | Intercompany Affiliates    | `Net30`          | `MONTHLY`         | `INTER_TAX`       |
| **BAD_DEBT**   | Suspended / In Litigation  | `COD`            | `MONTHLY`         | `STANDARD`        |
+---------------------------------------------------------------------------------------------------+

Key Financial & Operational Defaults Driven by Customer Groups

  1. Terms of Payment: Automatically populates on newly created customer master records (e.g., Net30, 2% 10 Net 30, COD), which in turn defaults onto sales order headers and free text invoices.
  2. Settlement Period: Associates customer transactions with a specific Sales Tax Settlement Period for indirect tax reporting and frequency.
  3. Default Sales Tax Group: Specifies the default geographic/jurisdictional tax group assigned to new customer accounts.
  4. Ledger Account Defaults (Optional / Country-Specific): In certain regional localizations, default revenue accounts or write-off accounts can be defined directly on the customer group.
  5. Trade Agreements & Pricing Groups: Customer groups serve as the primary grouping mechanism for sales price trade agreements, line discounts, multiline discounts, and total order discounts (Sales and marketing > Prices and discounts > Trade agreement journals).

4. Shared Customer Records Across Legal Entities

Global enterprises operating multiple legal entities often transact with the same corporate customer across subsidiaries. Dynamics 365 Finance provides multiple strategies for managing shared customer entities:

1. Global Address Book (GAB) Party Association (Standard Framework)

  • A customer exists as a single Party (e.g., Party-0042: Airbus SE) in the Global Address Book.
  • When Airbus is created as a customer in company USMF (US operations) and company DEMF (German operations), both customer accounts link to Party-0042.
  • Benefit: Contact details, postal addresses, and tax registration identifiers are maintained centrally. However, subledger transactional data, credit limits, currencies, and GL posting profiles remain separate in each company.

2. Cross-Company Data Sharing (SysDataSharing Framework)

  • Utilizes the Cross-company data sharing engine (System administration > Setup > Configure cross-company data sharing).
  • Synchronizes specific tables (e.g., CustTable, DirPartyTable, CustGroup) across designated legal entities in near real-time.
  • Restrictions: Transactions cannot exist in shared tables prior to enabling data sharing. Furthermore, financial dimensions, posting profiles, and bank account setups that vary by legal entity must be carefully managed or excluded from the sharing policy.

Comparison of Customer Master Data Sharing Methods

CapabilityGAB Party Linking (Standard)Cross-Company Data SharingCustomer Copy Framework (Data Management)
Account IDCan be identical or differentMust be identical across entitiesCan be mapped via entity templates
Credit LimitIndependent per legal entityShared globally across entitiesIndependent per legal entity
Payment TermsCan vary by entitySynchronized / IdenticalCan vary by entity
Posting ProfileIndependent per legal entityMust match chart of accountsIndependent per legal entity
Implementation EffortNative / Out of the BoxHigh / Requires Data Sharing PolicyLow / On-demand batch execution

Test Your Knowledge

A global enterprise operates two legal entities: USMF (United States) and DEMF (Germany). A multinational client, Fabrikam International, is created as a customer in both legal entities and linked to a single Global Address Book party record. Which of the following customer attributes can be configured with different values in USMF and DEMF without breaking data integrity?

A
B
C
D
Test Your Knowledge

An organisation wants to maintain one customer record centrally for a multinational client while keeping each legal entity's receivable balance and control accounts separate. What is the correct approach?

A
B
C
D