Study guide
11.2 Purchase Orders Creation, Over/Under-Delivery Tolerances, Delivery Schedules, and Product Receipt
Microsoft Dynamics 365 Supply Chain Management Functional Consultant MB-330
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Product Master and Released Products
1.1 Product Masters, Variants, and Configuration Technologies 1.2 Product Templates, Category Hierarchies, and Product Lifecycle States 1.3 Product Attributes, Attribute Types, and Attribute Groups
2 Chapter 2: Bills of Materials (BOM) and Formulas
2.1 BOM Lines, Line Types, and Component Configurations 2.2 BOM Versions, Activation, Approvals, and Circularity Checks 2.3 BOM Calculations, Cost Group Types, Flushing Principles, and Scrap Handling
3 Chapter 3: Product Prerequisites and Dimension Groups
3.1 Product, Storage, and Tracking Dimension Groups 3.2 Item Model Groups, Inventory Models, and Physical/Financial Posting 3.3 Reservation Hierarchies and Unit Sequence Groups
4 Chapter 4: Additional Product Details and Warehouse Fit
4.1 Bar Codes, GTINs, and Product Unit Conversions 4.2 Default Order Settings and Site-Specific Order Settings 4.3 Product Filter Codes and Physical Warehouse Dimensions
5 Chapter 5: Inventory Costing and Pricing
5.1 Costing Versions, Costing Sheets, and Standard Costing 5.2 Base Item Prices, Price Groups, and Price Tolerances 5.3 Trade Agreements, Price/Discount Journals, and Smart Rounding
6 Chapter 6: Inventory Journals and Core Transactions
6.1 Movement, Adjustment, and Transfer Journals 6.2 Counting Journals, Tag Counting, and Cycle Count Adjustments 6.3 Item Arrival Journals, Output Orders, and BOM Journals
7 Chapter 7: Inventory Operations, Blocking, and Closing
7.1 Transfer Orders, In-Transit Warehouses, and Delivery Schedules 7.2 Inventory Blocking Mechanisms, Batch Disposition Codes, and Inventory Status 7.3 Inventory Closing, Recalculation, Settlement, and ABC Classification
8 Chapter 8: Quality Management and Nonconformance
8.1 Quality Control Setup: Tests, Test Groups, and Item Sampling 8.2 Quality Associations, Automatic Generation, and Quality Orders Processing 8.3 Nonconformances, Corrections, Corrective Operations, and Quarantine Orders
9 Chapter 9: Asset Management: Setup and Maintenance
9.1 Assets, Asset Types, and Functional Locations Setup 9.2 Asset Lifecycle Models, Lifecycle States, and Asset Loans 9.3 Work Orders Configuration, Work Order Settings, and Maintenance Capacity Management 9.4 Maintenance Plans, Maintenance Requests, Work Order Scheduling, and Journal Consumption
10 Chapter 10: Procurement and Sourcing Configuration
10.1 Vendors, Vendor Groups, and Procurement Category Hierarchies 10.2 Purchasing Policies, Spending Limits, Procurement Workflows, and Charge Codes 10.3 Purchase Agreements, Vendor Rebates, and Vendor Collaboration Portal
11 Chapter 11: Purchase Order Lifecycle and Consignment
11.1 Purchase Requisitions, Requests for Quotation (RFQs), and Bidding Processes 11.2 Purchase Orders Creation, Over/Under-Delivery Tolerances, Delivery Schedules, and Product Receipt 11.3 Consignment Inventory Replenishment/Ownership Change and Vendor Return Orders
12 Chapter 12: Landed Cost and Inbound Logistics
12.1 Landed Cost Architecture: Voyages, Shipping Containers, Folios, and Journey Templates 12.2 Cost Type Codes, Auto-Costs, and Allocation Methods 12.3 Tracking Control Center, Goods in Transit Orders, and Over/Under Tolerances
13 Chapter 13: Sales Management and Order Processing
13.1 Customers, Customer Groups, Sales Agreements, and Sales Quotations 13.2 Sales Order Processing, Manual and Automatic Reservation, and Sales Returns 13.3 Order Promising: ATP, CTP, Delivery Schedules, and Product Bundles 13.4 Intercompany Trading Chains, Sales Commissions, and Customer Rebates
14 Chapter 14: Warehouse Setup and Core Infrastructure
14.1 Warehouse Topology: Sites, Warehouses, Locations, Profiles, Formats, and Zones 14.2 Work Policies, Work Breaks, and Packing Dimensions 14.3 Wave Templates, Work Templates, and Location Directives Configuration 14.4 Label Layouts, Document Routing, Wave Label Printing, and GS1 Number Sequences
15 Chapter 15: Warehouse Execution Processes
15.1 Inbound Receiving Processes, Planned Cross-Docking, and Putaway 15.2 Outbound Waves, Wave Processing, Picking (Order, Cluster, Batch), and Manual Packing 15.3 Replenishment Strategies (Wave vs. Min/Max) and Inventory Movements via Warehouse Work 15.4 Cycle Counting Plans, Thresholds, Blind Counting, and Automated Containerization
16 Chapter 16: Transportation Management and Logistics
16.1 Shipping Carriers, Carrier Groups, Carrier Services, and Rate/Route Engines 16.2 Route Plans, Route Guides, Inbound/Outbound Loads, and Dock Appointment Scheduling 16.3 Freight Bills, Freight Invoicing, and Manual/Automatic Freight Reconciliation
17 Chapter 17: Warehouse Management Mobile App
17.1 Mobile App Installation, Display Settings, Connection Profiles, and Warehouse Worker Setup 17.2 Mobile Device Menus, Work-Based and Indirect Menu Items, and Inventory Inquiries 17.3 Step Detours Configuration and GS1 Barcode Scanning Implementation
18 Chapter 18: Master Planning and Planning Optimization
18.1 Master Planning Parameters, Coverage Groups, and Planning Optimization Cloud Service Architecture 18.2 Item Coverage Settings, Positive/Negative Days, Time Fences, and Action Messages 18.3 Running Master Planning, Analyzing Results, Planned Orders Firming, and Supply Schedule 18.4 Safety Stock Journals, Safety Margins, and Copilot in Dynamics 365 Supply Chain Management
11.2 Purchase Orders Creation, Over/Under-Delivery Tolerances, Delivery Schedules, and Product Receipt
Key Takeaways Explain This Topic AI
Purchase orders track operational progress across Open order, Received, Invoiced, and Cancelled statuses, integrated with formal document approval states (Draft, Approved, Confirmed).
Change Management workflow locks confirmed purchase orders, requiring a formal Request change that preserves active confirmed versions for warehouse receiving while amendments undergo re-approval.
Over-delivery and under-delivery percentage tolerances enforce rigid variance thresholds at line or item levels, blocking non-compliant receipt overages and facilitating clean closure of short shipments.
Delivery schedules split a single commercial parent accounting line into multiple staggered delivery lines across dates, sites, or warehouses while preserving bulk contractual volume pricing.
Inbound fulfillment differentiates between non-financial dock Item registration and formal Product receipt posting, the latter generating physical inventory transactions and General Ledger liability accruals (GRNI).
Last updated: September 2026
11.2 Purchase Orders Creation, Over/Under-Delivery Tolerances, Delivery Schedules, and Product Receipt
Quick Answer: The Purchase Order lifecycle in Microsoft Dynamics 365 Supply Chain Management (D365 SCM) spans both Document status ( Draft , In review , Approved , Confirmed ) and Operational status ( Open order , Received , Invoiced , Cancelled ). Enabling Change Management enforces governance by locking confirmed orders, requiring a Request change to modify fields while preserving active confirmed versions for ongoing warehouse receipt. Variances in delivery quantities are strictly regulated using Over-delivery and Under-delivery tolerances defined at the item or line level. To fulfill staggered demand under single-line volume contracts, Delivery schedules split a commercial Accounting line into transactional Delivery lines . Physical receiving proceeds from non-financial dock Item registration to formal Product receipt posting , which posts unbilled inventory liability accruals ( Accrue liability on product receipt ) in the General Ledger.
1. Purchase Order Lifecycle, Document Statuses, and Order Types
A Purchase order (PO) represents an explicit commercial and legal contract between the buying legal entity and an external supplier.
- Navigation : Procurement and sourcing > Purchase orders > All purchase orders
- Purchase Order Types
When creating a PO header, the Purchase type defines system behavior:
Purchase order : Standard commercial order used to procure stocked goods, assets, or expensed services. Updates inventory on-order balances and generates general ledger postings.
Journal : Non-transactional exploratory draft. Generates no inventory transactions, does not reserve inventory, and cannot post physical receipts or financial invoices.
Returned order : Special purchase order type used to return previously received inventory to a vendor for financial credit, requiring a Return Material Authorization (RMA) number.
The Dual-Track Status Model
D365 SCM evaluates purchase orders across two concurrent status dimensions: +-------------------------------------------------------------------------------------------------+
- | PURCHASE ORDER CONCURRENT STATUS MATRIX |
- +------------------------------------+------------------------------------------------------------+
- | Document Status (Approval State) | Operational Status (Fulfillment State) |
- | • Draft (Editable unapproved) | • Open order (Confirmed, un-received or partial receipt) |
- | • In review (Workflow locked) | • Received (Full quantity posted via Product Receipt) |
- | • Approved (Workflow sign-off) | • Invoiced (Full quantity matched on Vendor Invoice) |
- | • Confirmed (Legally binding) | • Cancelled (Remaining or total quantity revoked) |
- +------------------------------------+------------------------------------------------------------+
- 2. Purchase Order Confirmation, Change Management, and Revision History
- Confirmation Document Generation
Confirming a purchase order establishes a binding commercial commitment:
Navigation : PO Action Pane > Purchase tab > Generate > Confirmation .
Creates a permanent historical journal record in VendPurchOrderJour .
Generates the external document transmitted to the vendor and sets document status to Confirmed .
Change Management Workflow Architecture
Change management enforces rigid approval governance, preventing buyers from unilaterally modifying quantities, costs, or delivery terms after vendor confirmation:
Activation Hierarchy :
Global toggle: Procurement and sourcing parameters > General > Activate change management .
Global override toggle: Allow override of settings per vendor .
Vendor master setting: Vendors > All vendors > Purchase order defaults FastTab > Allow change management on vendor (can be set to Yes or No ). CHANGE MANAGEMENT OPERATIONAL CYCLE
- [New PO] --> [Draft] --> (Submit Workflow) --> [In review] --> [Approved] --> [Confirmed]
- |
- +-------------------------------------+
- | (Click "Request change")
- v
- [Active Confirmed Version] <---> [Draft Revision Version]
- (Warehouse dock can continue (Buyer edits prices, dates,
- receiving arriving goods) or quantities in Draft)
- |
- v
- (Re-submit to Workflow)
- |
- v
- [Approved & Confirmed]
- (Overwrites active version)
- The "Request Change" Mechanism and Receiving Continuity
When change management is active, confirmed orders are read-only. To alter any field, the buyer clicks Request change on the Action Pane:
The order's document status reverts from Confirmed to Draft .
Critical Architectural Resilience : Reverting to Draft does not cancel or block receiving operations! The system retains the previous Confirmed version in the background database. Warehouse personnel can continue processing dock arrival and product receipts against the confirmed quantities while the buyer modifies draft lines.
After edits are completed, the draft order must be re-submitted to the PurchTableReview workflow. Once approved and re-confirmed, the new version supersedes the previous active version.
Version Comparison and Audit Trail
Under Purchase order > Manage > Versions , users open Purchase order versions and select Compare versions . D365 SCM displays an audit grid highlighting precise line-level delta changes in unit prices, net amounts, promised dates, and delivery addresses between revisions.
3. Over-Delivery and Under-Delivery Tolerances
In raw material, agricultural, chemical, and bulk commodity procurement, delivered quantities frequently deviate from ordered amounts due to tank capacities, truck weight limits, or cutting tolerances.
Configuration Hierarchy and Parameters
Tolerances are configured across a two-tier hierarchy:
Item Master Default : Released products > Purchase FastTab > Over-delivery % and Under-delivery % .
PO Line Override : Defaults from the released product but can be modified per transaction under Purchase order lines > Line details > Delivery FastTab .
Global Enforcement Parameters : Procurement and sourcing parameters > Delivery FastTab :
Accept overdelivery : Must be enabled to permit receipts exceeding ordered quantities.
Accept underdelivery : Must be enabled to allow closing lines that fall short of ordered quantities.
Mathematical Validation Rules Max Allowable Receipt = Ordered Quantity × ( 1 + Over-delivery % 100 ) \text{Max Allowable Receipt} = \text{Ordered Quantity} \times \left(1 + \frac{\text{Over-delivery \%}}{100}\right) Max Allowable Receipt = Ordered Quantity × ( 1 + 100 Over-delivery % ) Min Closure Threshold = Ordered Quantity × ( 1 − Under-delivery % 100 ) \text{Min Closure Threshold} = \text{Ordered Quantity} \times \left(1 - \frac{\text{Under-delivery \%}}{100}\right) Min Closure Threshold = Ordered Quantity × ( 1 − 100 Under-delivery % )
Operational Behavior Scenarios
Over-Delivery Enforcement :
Order: 500 units; Over-delivery = 10.0% . Max allowable receipt = 550 units.
If the supplier delivers 530 units, the product receipt posts successfully without error.
If the supplier delivers 560 units, D365 SCM throws a hard-stop exception: Overdelivery of line is 12.00 percent, but the allowed overdelivery is only 10.00 percent. Physical receipt is blocked until the buyer amends the line tolerance.
Under-Delivery Line Closure :
Order: 1,000 units; Under-delivery = 5.0% . Min closure threshold = 950 units.
The supplier ships 960 units and confirms no additional units will follow. Because 960 units exceeds the 950-unit threshold, the user selects Close during product receipt posting (or cancels the deliver remainder). D365 SCM transitions line operational status directly to Received , cleanly releasing open reservations without leaving backorder balances.
4. Delivery Schedules: Commercial vs. Delivery Lines
When procurement negotiates annual high-volume pricing (e.g., 24,000 bearings at a 30% volume discount), warehouse space constraints often prevent receiving the entire order at once. Delivery schedules solve this by staggering deliveries across dates, sites, or warehouses.
Navigation : Purchase order lines > Inventory dropdown > Delivery schedule +-------------------------------------------------------------------------------------------------+
- | DELIVERY SCHEDULE TWO-TIER STRUCTURE |
- +-------------------------------------------------------------------------------------------------+
- | COMMERCIAL PARENT LINE (Accounting Line) |
- | • Contracted total: 24,000 ea @ $12.00/ea |
- | • Non-transactional: Has NO inventory transactions (Zero 'On order' quantity) |
- | • Cannot be registered or received at warehouse docks |
- +-------------------------------------------------------------------------------------------------+
- |---> Child Delivery Line 1: 6,000 ea | Delivery Date: Jan 15 | Warehouse 11 | (Inventory Ordered)
- |---> Child Delivery Line 2: 6,000 ea | Delivery Date: Apr 15 | Warehouse 11 | (Inventory Ordered)
- |---> Child Delivery Line 3: 6,000 ea | Delivery Date: Jul 15 | Warehouse 22 | (Inventory Ordered)
- |---> Child Delivery Line 4: 6,000 ea | Delivery Date: Oct 15 | Warehouse 22 | (Inventory Ordered)
- +-------------------------------------------------------------------------------------------------+
- Structural Separation: Parent vs. Child Lines
Commercial Parent Line (Accounting Line) :
Holds overall contracted quantity, base price, and commercial contract terms.
Marked with an order line indicator showing it possesses delivery schedules.
Crucial Rule : The accounting line is completely non-transactional. It creates no inventory transactions and cannot be registered or received against.
Fulfillment Child Lines (Delivery Lines) :
Created by the delivery schedule creation wizard.
Each line possesses its own Confirmed delivery date , Quantity , Site , Warehouse , and Delivery address .
Physical inventory transactions ( Ordered ) exist exclusively on child lines, and all receiving occurs against these child lines.
Allocation of Commercial Charges
When creating delivery schedules, the user selects how header and line charges (e.g., freight, import duties) distribute:
Apportion to delivery lines : Distributes total charges proportionally across child lines based on line quantity or amount.
Keep on parent line : Retains charges at the parent level, posting upon first invoice.
Loading diagram... Purchase Order Receiving and General Ledger Accrual Lifecycle
5. Inbound Receiving Mechanics: Registration vs. Product Receipt and GL Accruals
Warehouse inbound fulfillment in D365 SCM follows a strict two-phase execution separating physical dock handling from formal legal and financial commitment.
Phase 1: Item Registration (Dock Receipt)
Execution : Completed via the Item arrival journal , PO line Registration form ( Line details > Inventory > Registration ), or the Warehouse Management mobile app .
Inventory Status : Updates inventory transaction state from On order to Registered .
Physical Impact : Updates on-hand physical inventory at the specific dock receiving location.
Financial Impact : Zero General Ledger impact . No ledger vouchers, cost adjustments, or unbilled liability entries are posted.
Phase 2: Product Receipt Posting
Execution : Posted from the PO Action Pane ( Receive > Product receipt ) or automated via Advanced Warehouse Management work completion.
Inventory Status : Transitions inventory transaction state from Registered to Received .
Legal Impact : Establishes formal legal title transfer and ownership acknowledgment for commercial goods.
General Ledger Liability Accruals (Goods Received Not Invoiced - GRNI)
In accrual accounting, receiving goods creates an immediate legal liability before the vendor's commercial invoice arrives. D365 SCM automates this through the Product Receipt Accrual framework:
Required Parameter Prerequisites :
Accounts payable parameters > Ledger and sales tax > Accrue liability on product receipt = Yes .
Inventory management > Setup > Inventory > Item model groups > Post physical inventory = Yes .
Item model group > Accrue liability on physical inventory = Yes .
Product Receipt Accounting Posting Voucher :
Debit : Purchase expenditure, un-invoiced (or Inventory - physical receipt cost asset account).
Credit : Purchase accrual (Current liability account representing un-invoiced vendor receipts).
Subsequent Vendor Invoice Reconciliation :
When Accounts Payable posts the formal vendor invoice:
D365 SCM automatically reverses the original Product Receipt accrual voucher in full.
The final commercial voucher is posted:
Debit : Inventory cost financial (or Purchase expenditure for expense).
Debit : Input sales tax / Value-added tax (VAT).
Credit : Accounts payable vendor balance.