10.1 Vendors, Vendor Groups, and Procurement Category Hierarchies
Key Takeaways
- Vendor records are legal entity-specific transactional projections linked to shared party records in the Global Address Book (DirPartyTable), enabling unified tax IDs, contact details, and addresses across entities.
- Vendor groups are mandatory master configurations that assign the Accounts payable summary ledger posting profile, default payment terms, cash discount settlement periods, and sales tax defaults.
- Procurement category hierarchies enable non-inventoried spend management and expense requisitioning without creating released product masters, structured as hierarchical category trees mapped to standard commodity codes (e.g., UNSPSC).
- Category policy rules enforce invoice matching policies (Two-way, Three-way, or Not required) and line price variance tolerances at the category level, overriding global Accounts payable parameters.
- Vendor status controls operational gating through specific hold states (Never, No, Invoice, All, Payment, Requisition), while evaluation criteria and certifications track compliance and performance scoring.
10.1 Vendors, Vendor Groups, and Procurement Category Hierarchies
Quick Answer: In Microsoft Dynamics 365 Supply Chain Management (D365 SCM), vendor masters represent legal entity-specific transactional records (
VendTable) linked to shared party records in the Global Address Book (GAB) (DirPartyTable). Every vendor must belong to a Vendor group, which dictates Accounts payable summary ledger posting profiles, payment terms, and tax defaults. Non-stocked products, expense requisitions, and indirect spend are governed through Procurement category hierarchies, where Category policy rules enforce invoice matching policies (Two-way vs. Three-way) and price variance tolerances. Operational activity is gated using granular On hold statuses (Invoice,All,Payment,Requisition).
1. Vendor Master Architecture and the Global Address Book (GAB)
D365 SCM decouples party identity from transactional accounting through the Global Address Book:
- Party Record (
DirPartyTable): A globally shared record representing an organization or person. Stored centrally across all legal entities, it maintains legal names, tax identification numbers (EIN/TIN), addresses, contacts, and communication channels. - Vendor Record (
VendTable): A company-specific transactional entity created inProcurement and sourcing > Vendors > All vendors(orAccounts payable > Vendors > All vendors). It links a shared party record to an operating company (e.g.,USMF).
Multi-Company Vendor Sharing
When creating a vendor in a second legal entity for an existing supplier, select the existing Party ID:
- Addresses, phone numbers, and tax IDs remain synchronized globally across all entities.
- Financial parameters—such as vendor account numbers, vendor groups, default currencies, payment terms, and posting profiles—are configured independently per company.
- Corporate purchasing teams can aggregate spend analytics across legal entities using the shared Party ID.
- Number Sequences: Vendor IDs are generated automatically via continuous number sequences (
Accounts payable parameters > Number sequences) or entered manually for legacy account IDs.
2. Vendor Groups: Setup and Financial Automation
Every vendor must be assigned exactly one Vendor group (VendGroup) during creation (Procurement and sourcing > Setup > Vendors > Vendor groups). Vendor groups categorize suppliers and drive accounting defaults:
| Parameter | Purpose & System Impact |
|---|---|
| Posting profile | Links the vendor group to the Accounts payable posting profile (VendLedgerProfiles), mapping vendor transactions to General Ledger AP summary liability accounts. |
| Terms of payment | Establishes default credit terms and due date calculation rules inherited by new vendors. |
| Settle period | Defines the default cash discount calendar period used to match invoices against payments during settlement. |
| Default tax groups | Supplies default Sales tax group and Item sales tax group for transactions when not overridden. |
| Currency | Populates the default purchasing and invoicing currency for newly created vendor masters. |
[!IMPORTANT] Vendor Group Assignment Rule: The Vendor group field is mandatory on every vendor record. Changing a vendor's group updates defaults on new purchase orders, but does not alter historical open transactions or the vendor account ID.
3. Commercial Terms: Payment Terms, Cash Discounts, 1099, and Currency
Vendor records establish the financial baseline for procurement contracts and disbursements:
- Terms of Payment (
PaymTerm): Configured inAccounts payable > Setup > Payment > Terms of payment. Controls due date calculation: Net (fixed days after invoice), Current month (specific day of month), Current quarter / End of month, or Payment schedule (installment payments). - Cash Discounts (
CashDisc): Configured inAccounts payable > Setup > Payment > Cash discounts. Specifies discount percentage, discount days (e.g., 2% 10 Net 30), and calculation principle (net vs. gross amount including sales tax). - 1099 Tax Reporting (US): Located under Vendor master > Invoice and delivery FastTab > 1099 reporting. Includes Report 1099 toggle, Federal Tax ID (EIN/SSN), 1099 Box (e.g., 1099-NEC for services, 1099-MISC for rent), and W-9 received compliance checkbox.
- Default Currency: Set on the vendor master (Payment FastTab). Transaction currency for purchase orders and invoices. Foreign transactions convert to accounting currency using the ledger's active Exchange rate type.
4. Procurement Category Hierarchies and Commodity Codes
A Procurement category hierarchy organizes goods and services into a structured taxonomy for indirect spend management, purchase requisitions, and catalog control without requiring released products (InventTable).
- Hierarchy Structure: Configured in
Procurement and sourcing > Setup > Categories > Procurement categoriesas a tree structure (root, parent, and leaf categories). - Role Association: Must be explicitly mapped to the Procurement role under
Product information management > Setup > Categories and attributes > Category hierarchy role associations. - Non-Stocked Purchasing: Workers requisition services and supplies directly by category without creating item masters.
- Commodity Codes: Mapped to standard classification schemes (e.g., UNSPSC) under
Procurement and sourcing > Setup > Categories > Commodity codesfor spend analytics and customs compliance.
5. Category Policy Rules, Matching Policies, and Price Tolerances
Through Category policy rules within Purchasing policies, organizations govern invoice validation per category:
| Matching Policy | Compared Artifacts | Operational Context |
|---|---|---|
| Two-way matching | 1. Purchase Order Unit Price<br/>2. Vendor Invoice Unit Price | Non-inventory items, professional services, subscriptions, and indirect expenses without warehouse receiving slips. |
| Three-way matching | 1. Purchase Order Unit Price<br/>2. Product Receipt Quantity<br/>3. Vendor Invoice Net Price & Quantity | Standard stocked goods and physical materials where warehouse receipt must verify quantity before invoice approval. |
| Not required | No automated matching validation performed. | Utility bills, recurring flat fees, or internal company allocations. |
- Price Tolerances: Configured as percentage or amount variance limits. Exceeding tolerance places invoices on matching hold.
- Category Access Policy Rules: Dictate which category branches specific organizational operating units can view on requisitions.
6. Vendor Evaluation Criteria, Certification, and Status Management
- Vendor Evaluation: Configured in
Procurement and sourcing > Setup > Vendors > Evaluation criteria. Defines criteria groups (Quality, Delivery, Pricing) rated on 1–5 scoring scales and questionnaires. - Vendor Certifications: Configured under
Procurement and sourcing > Setup > Vendors > Vendor certification types. Tracks ISO 9001 or diversity credentials with effective and expiration dates. - Vendor On Hold Controls: Managed on the vendor master (General FastTab):
| On Hold Status | Purchase Order Creation | Product Receipt Posting | Vendor Invoice Posting | Payment Generation | Requisition Selection |
|---|---|---|---|---|---|
| No | Allowed | Allowed | Allowed | Allowed | Allowed |
| Invoice | Allowed | Allowed | Blocked | Allowed | Allowed |
| All | Blocked | Blocked | Blocked | Blocked | Allowed |
| Payment | Allowed | Allowed | Allowed | Blocked | Allowed |
| Requisition | Allowed | Allowed | Allowed | Allowed | Blocked |
| Never | Permanent exemption; the vendor record cannot be placed on hold under any circumstances. |
[!TIP] Exam Tip — On Hold Status Selection: If an audit requires halting cash disbursements while continuing to receive open shipments and post invoices to capture liabilities, set On hold to Payment.
[!WARNING] Exam Trap — Hierarchy Role Association: Creating a procurement hierarchy does not make it visible in requisitions. You must navigate to Category hierarchy role associations and assign it to the Procurement role.
A functional consultant is configuring a multi-company implementation of Dynamics 365 Supply Chain Management for an enterprise operating two legal entities, USMF and DEMF. A key raw material supplier, Acme Industrial, delivers goods to manufacturing plants in both legal entities. The corporate controller requires that Acme Industrial share a single centralized address, tax identification number, and contact directory across both companies, while maintaining distinct general ledger posting profiles, payment terms, and operating currencies in USMF and DEMF. How should the functional consultant configure this supplier?
An enterprise purchases legal and management consulting services categorized under the "Professional Services" procurement category. These service engagements do not involve physical warehouse handling, and operations personnel do not register product receipts. The accounts payable department requires the system to verify that the invoiced unit price matches the purchase order unit price within an allowable 2% variance, while allowing invoice posting to proceed without requiring a product receipt. How should the functional consultant configure the matching rules in Dynamics 365 Supply Chain Management?
An accounts payable manager discovers that an active supplier has submitted conflicting bank routing numbers and unverified tax documentation. To prevent fraudulent cash disbursements, the chief financial officer directs the procurement and finance teams to immediately stop issuing payments to this supplier. However, the purchasing department must still be permitted to create purchase orders for mission-critical parts, and warehouse and accounts payable teams must continue receiving shipments and registering vendor invoices against those orders. Which On hold status should the functional consultant configure on the vendor master record?