Sales orders, purchasing, pricing, and open-document migration

How Epicor Kinetic's sales orders, purchase orders, blanket POs, drop-ship, supplier price lists, and contract pricing translate to D365 trade agreements, purchase agreements, and the order-to-cash and procure-to-pay lifecycles — including the open-document migration approach.

What you will be able to do

• Map Epicor sales orders to D365 sales orders and describe the document lifecycle differences
• Translate Epicor purchase orders, blanket POs, and drop-ship to D365 purchase orders, purchase agreements, and direct delivery
• Explain how Epicor supplier price lists and contract pricing map to D365 purchase trade agreements
• Describe the correct approach for migrating open sales orders and purchase orders at cutover
• Identify the CRM/SRM split and the Dataverse decision for customer and supplier relationship data

Introduction

Trade — the combination of order-to-cash and procure-to-pay — is the day-one continuity concern. If open sales orders do not exist in D365 at go-live, customers cannot be shipped. If open purchase orders do not exist, suppliers cannot deliver.

Sales orders — Epicor order entry to D365 sales orders

An Epicor sales order (OrderHed / OrderDtl / OrderRel) carries a header (customer, currency, order date, requested ship date) and lines (item, quantity, price, promised date, release schedule). Lines can be make-to-stock (fulfilled from inventory) or make-to-order (linked to a production job).

Purchase orders, blanket POs, and drop-ship

Epicor purchase orders (POHeader / PODetail / PORel) map directly to D365 purchase orders (PurchTable / PurchLine). The receiving → AP voucher flow maps to D365 product receipt → vendor invoice. Three-way matching (PO → receipt → invoice) works identically in principle.

Purchase requisitions and approval workflows

Epicor purchase requisitions with approval routing map to D365 purchase requisitions (PurchReqTable / PurchReqLine) with workflow-based approval. The D365 workflow engine uses condition-based routing: approval steps are triggered by amount thresholds, procurement categories, requestor attributes, or custom conditions.

Supplier price lists and contract pricing → trade agreements

Epicor supplier price lists store vendor-item prices with quantity breaks and effectivity dates. Contract pricing extends this with negotiated terms tied to a specific agreement period.

The customer and supplier data split

Epicor stores the customer record alongside embedded CRM data — opportunities, cases, activities, and the 360-degree customer view. D365 separates these concerns:

Open-document migration — the Wave 3 approach

Open-document migration at Wave 3 (in the site's canonical wave model) follows these principles:

Sales pricing — Epicor price lists to D365 trade agreements

Epicor sales pricing uses price lists and price list breaks assigned to customers or customer groups. Pricing can include:

Vendor collaboration and the supplier portal

Epicor's supplier relationship management includes a supplier portal for PO acknowledgement, ASN (advance shipping notices), and document exchange. D365 provides vendor collaboration — a web-based portal where vendors can:

Intercompany trade

For multi-company Epicor installations, intercompany sales and purchasing transactions must be mapped to D365 intercompany trading relationships. D365 intercompany trade works through the InterCompanyTradingRelation configuration: when a sales order is confirmed in the selling legal entity, D365 automatically creates a linked purchase…

Knowledge check

Summary

Trade migration is operationally unforgiving — a missed open order is a day-one failure — but structurally the mapping from Epicor to D365 is close. The complexity lies in the open-document migration approach (getting the granularity right so that financial opening balances are not corrupted) and in the CRM/SRM data-ownership decision.