10.2 Purchasing Policies, Spending Limits, Procurement Workflows, and Charge Codes
Key Takeaways
- Purchasing policies enforce procurement governance across legal entities and operating units by scoping rules through organization hierarchies assigned the Purchasing internal control purpose.
- The five critical purchasing policy rule types govern catalog availability, category access, category invoice matching/tolerances, mandatory RFQ generation thresholds, and automatic purchase order conversion/consolidation.
- Signing limit policies govern employee procurement authorization by mapping spending limits (maximum submission amount) and approval limits (maximum authorization amount) to Human Resources job levels.
- Procurement workflows manage requisition approvals and purchase order change management, requiring users to request change and re-route draft orders upon modifying confirmed purchase orders.
- Charge codes allocate landed costs and procurement expenses using specific Debit/Credit posting types (Item, Ledger, Customer/Vendor) to capitalize inventory value or recognize operational expenses.
10.2 Purchasing Policies, Spending Limits, Procurement Workflows, and Charge Codes
Quick Answer: In Microsoft Dynamics 365 Supply Chain Management (D365 SCM), enterprise procurement governance is enforced through Purchasing policies scoped to Organization hierarchies with the
Purchasing internal controlpurpose. Policies contain specialized rules—including Category access, Category policy, and Purchase order creation and demand consolidation. Employee authorization is controlled via Signing limit policies mapped to Human Resources job levels, differentiating Spending limits (worker request ceiling) from Approval limits (managerial sign-off ceiling). Purchase order edits are audited through Change management workflows, while ancillary freight and handling costs are distributed using Charge codes withItem,Ledger, orCustomer/Vendorposting types.
1. Purchasing Policies Framework and Organization Hierarchy Scoping
Purchasing policies define business rules that regulate requisitioning, catalog exposure, invoice validation, and purchase order creation across operating units and legal entities (Procurement and sourcing > Setup > Policies > Purchasing policies).
Scoping through Organization Hierarchies
Purchasing policies are applied to nodes within an Organization hierarchy (Organization administration > Organizations > Organization hierarchies):
- An organization hierarchy is created containing legal entities, operating units, business units, or departments.
- The hierarchy must be assigned the Purchasing internal control purpose under
Organization administration > Organizations > Organization hierarchy purposes. - In the Purchasing policy header, the policy is associated with one or more specific organizational operating units within that hierarchy.
Policy Rule Resolution and Inheritance
- Inheritance: A child operating unit (e.g., Plant 101 - Manufacturing) automatically inherits policy rules from its parent operating unit (e.g., North American Operations) unless an explicit rule is configured at the child level.
- Most Specific Node Wins: If rules exist at both parent and child levels, the rule at the lowest, most specific organizational node takes precedence.
- Effective Dates: Policy rules utilize Effective date and Expiration date parameters, allowing scheduled governance changes without system downtime.
2. Comprehensive Breakdown of Purchasing Policy Rule Types
A purchasing policy serves as a container for five critical policy rule types:
| Policy Rule Type | Governance Scope | Operational Impact & System Behavior |
|---|---|---|
| Catalog policy rule | Internal Procurement Catalogs | Controls which procurement catalog is presented to workers in the target operating unit when opening the purchase requisition portal. |
| Category access policy rule | Category Hierarchy Visibility | Dictates which procurement category branches are exposed or hidden when workers create requisition lines, preventing unauthorized purchases. |
| Category policy rule | Accounting & Invoice Validation | Enforces line matching policies (Two-way, Three-way, Not required), price variance tolerances, GL expense accounts, and inventory accruals. |
| Purchase requisition RFQ rule | Sourcing Thresholds | Defines criteria (such as requisition line total exceeding $10,000) that mandate generating a Request for Quotation (RFQ) before converting to a purchase order. |
| Purchase order creation and demand consolidation rule | Automation & Order Generation | Dictates whether approved requisitions automatically convert to purchase orders or route to the Consolidation opportunities workbench for manual demand grouping by vendor and currency. |
[!NOTE] Demand Consolidation Workbench: When the Purchase order creation and demand consolidation rule specifies manual consolidation, approved requisition lines route to
Procurement and sourcing > Purchase requisitions > Purchase requisition consolidationfor bulk ordering.
3. Spending Limits vs. Approval Limits (Signing Limits)
Signing limits establish financial controls over document submission and approval (Organization administration > Setup > Signing limits > Signing limit parameters and Signing limit policies):
- HR Job Level Basis: Signing limits are mapped to Job levels defined within Human Resources (
Human resources > Jobs > Jobs). When a worker is assigned a position linked to a job, they inherit the signing limits configured for that job level. - Spending Limit: The maximum cumulative monetary amount an employee is authorized to request or submit on an operational document (e.g., a purchase requisition line).
- Approval Limit: The maximum cumulative monetary amount an authorized manager can approve for another worker's document in an approval workflow.
- Hierarchy Traversal: If a supervisor's approval limit is lower than the document total, the workflow engine automatically routes the document up the managerial reporting chain until reaching an authority whose approval limit meets or exceeds the document value.
4. Procurement Workflows and Change Management
Workflows automate document routing, compliance validation, and approvals across requisitions and purchase orders:
- Purchase Requisition Workflows: Configured in
Procurement and sourcing > Setup > Procurement and sourcing workflows. The Purchase requisition review workflow (PurchReqReview) routes the overall document, while line-level sub-workflows evaluate independent commodity lines concurrently. - Activate Change Management: Enabled globally in
Procurement and sourcing > Setup > Procurement and sourcing parameters > General > Activate change management, or overridden on specific vendor records. - Approval Status Lifecycle:
- Draft: Newly authored purchase orders start in
Draftstatus and cannot be confirmed or sent to suppliers. - In Review: Clicking Submit initiates the purchase order workflow.
- Approved: Completing the workflow transitions the status to
Approved, permitting purchase order confirmation (Open order). - Request Change: Once approved or confirmed, modifying critical order fields requires clicking Request change. This reverts the status to
Draft, requiring workflow re-approval.
- Draft: Newly authored purchase orders start in
5. Charge Codes (Markup Codes) and Cost Capitalization
Charge codes capture ancillary procurement overhead—such as freight, insurance, customs duties, and handling—and allocate costs to inventory or ledger accounts (Procurement and sourcing > Setup > Charges > Charge codes).
Debit and Credit Posting Types
| Posting Side | Posting Type | System Accounting Impact |
|---|---|---|
| Debit | Item | Capitalizes the charge directly into the inventory valuation (asset cost basis) of the purchased product. |
| Ledger | Debits a specified General Ledger expense account (e.g., Freight Expense). | |
| Customer/Vendor | Debits the vendor account (rarely used in procurement). | |
| Credit | Customer/Vendor | Credits the vendor's Accounts Payable balance, adding the charge to the vendor invoice total payable to the supplier. |
| Ledger | Credits a specified General Ledger clearing account (e.g., Freight Accrual), used when a third-party logistics carrier bills freight separately. |
[!IMPORTANT] Third-Party Freight Accounting: When an item supplier ships goods but a separate carrier bills the freight, configure the charge code with Debit Type = Item (capitalizing inventory cost) and Credit Type = Ledger (crediting a freight clearing account). The carrier invoice subsequently debits the clearing account and credits the carrier.
Auto-Charges and Allocation
- Automatic Charges: Configured in
Procurement and sourcing > Setup > Charges > Automatic chargesby combinations of Vendor relation, Item relation, and Delivery mode. - Allocate Charges: Header-level charges can be prorated across lines using five allocation methods: Net amount, Gross amount, Quantity, Weight, or Volume.
A corporate procurement director at an enterprise wants to prevent approved purchase requisitions for standard office supplies from automatically generating individual purchase orders for every employee request. Instead, the purchasing department must hold and aggregate approved requisition lines across all departments into consolidated bulk orders by vendor and currency to negotiate volume discounts. Which purchasing policy rule must the functional consultant configure?
An organization is setting up signing limit policies in Dynamics 365 Supply Chain Management to enforce internal financial controls. A maintenance coordinator assigned to Job Level 2 needs authorization to submit purchase requisitions for machine replacement parts up to $5,000, but must not be allowed to approve requisitions submitted by other workers. Conversely, the maintenance supervisor assigned to Job Level 4 requires authorization to approve worker requisitions up to $25,000. How should the functional consultant configure the signing limit policy?
A heavy equipment manufacturer purchases specialized hydraulic valves from an overseas supplier. The company incurs third-party ocean freight charges that must be capitalized directly into the inventory valuation (asset cost basis) of the received valves. However, the ocean freight invoice is billed by an independent maritime logistics carrier rather than the valve supplier, and the carrier will be paid via Accounts Payable in a separate invoice voucher. How should the functional consultant configure the Debit and Credit posting types on the freight charge code?