Commercial document flows, pricing, and procurement translated
How Sage X3's sales and purchase document flows, pricing and discount structures, charges, delivery terms, intercompany trade and EDI translate to D365 sales orders, purchase orders, trade agreements, unified pricing management and charges; and how open commercial documents load at Wave 3.
What you will be able to do
Map the X3 sales document flow (quote → order → delivery → invoice) to the D365 order-to-cash lifecycle
Map the X3 purchase document flow (request → order → receipt → invoice) to the D365 procure-to-pay lifecycle
Explain the choice between D365 trade agreements and unified pricing management for an X3 pricing estate
Describe how X3 intercompany trade translates to D365 intercompany trading relationships
Plan the Wave 3 open-order load including partial-delivery and partial-invoice states
Introduction
Trade — the flow of sales and purchase documents that drives revenue and cost — is the domain where X3 and D365 overlap most naturally. Both systems model the same business lifecycle: quote, order, delivery, invoice. The conceptual distance is short; the implementation detail is where the difficulty lives.
Sales document flow
X3's order-to-cash lifecycle follows a standard commercial document sequence: Quote → Sales order → Delivery → Invoice. Each stage creates a distinct document in X3, and the sales order carries status fields that track which downstream documents have been generated.
Purchase document flow
X3's procure-to-pay lifecycle mirrors the sales side: Purchase request → Purchase order → Receipt → Supplier invoice. D365 carries the same lifecycle with equivalent document types.
Pricing: trade agreements versus unified pricing management
X3's pricing model uses price lists that define prices and discounts by customer (or customer group), item (or item category), quantity break, date range and currency. The price list resolution follows a hierarchy: the system searches for the most specific applicable price and applies discounts according to priority and combination rules.
Charges, landed costs and delivery terms
X3 supports charges (freight, handling, packaging, surcharges) at both header and line level on sales and purchase documents. D365 reproduces this through the charges framework:
Intercompany trade and EDI
X3 supports intercompany transactions within a folder: a sales order in one company generates a linked purchase order in another company within the same folder, enabling transfer pricing and intercompany settlement.
Wave 3: loading open commercial documents
Open sales orders and open purchase orders migrate at Wave 3 — open sales orders and open purchase orders. At this point, customers, vendors and products must already exist in D365 (loaded in Wave 2).
Knowledge check
Summary
Trade is the domain where X3 and D365 are closest conceptually but where implementation detail creates migration risk. The document flows are structurally equivalent; the complexity lives in pricing architecture, partial-order states, EDI re-platforming and intercompany reconciliation.