11.2 Purchase Orders Creation, Over/Under-Delivery Tolerances, Delivery Schedules, and Product Receipt

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:
  1. Global toggle: Procurement and sourcing parameters > General > Activate change management.
  2. Global override toggle: Allow override of settings per vendor.
  3. 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:

1. The order's document status reverts from Confirmed to Draft.
2. 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.
3. 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:

1. Item Master Default: Released products > Purchase FastTab > Over-delivery % and Under-delivery %.
2. PO Line Override: Defaults from the released product but can be modified per transaction under Purchase order lines > Line details > Delivery FastTab.
3. 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

$\text{Max Allowable Receipt} = \text{Ordered Quantity} \times \left(1 + \frac{\text{Over-delivery \%}}{100}\right)$

$\text{Min Closure Threshold} = \text{Ordered Quantity} \times \left(1 - \frac{\text{Under-delivery \%}}{100}\right)$

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

1. 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.
2. 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.

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:

1. 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.
2. 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).
3. Subsequent Vendor Invoice Reconciliation:
   • When Accounts Payable posts the formal vendor invoice:
     1. D365 SCM automatically reverses the original Product Receipt accrual voucher in full.
     2. 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.