How IFS customer orders, sales pricing (price lists, campaigns, rebates), customer agreements, purchase orders, supplier agreements, charges, intercompany, and the IFS supply chain matrix translate into D365 sales and purchase order lifecycles, trade agreements, purchase agreements, charges, and intercompany.
IFS's commercial capabilities span the full order-to-cash and procure-to-pay cycles, with rich pricing (price lists, campaign pricing, rebate agreements), customer and supplier blanket agreements, and a distinctive concept called the supply chain matrix — a rule-based engine that defines how internal demand in one site or company is…
The IFS Customer Order (CUSTOMER_ORDER) is the sales document. It carries an order type (normal, direct delivery, project, intercompany), delivery terms, payment terms, currency, and requested delivery date.
The IFS Purchase Order (PURCHASE_ORDER) mirrors the Customer Order on the supply side. Purchase Orders carry vendor, terms, currency, and lines for items, services, or charges. PO lifecycle statuses (Planned, Released, Partial Receipt, Received, Invoiced) map directly to D365 purchase order statuses.
Charges in IFS (freight, handling, insurance, customs duty) are attached to order headers and lines as additional cost lines. Charges post to specific GL accounts and can be billable to the customer or absorbed by the selling company.
D365 trade agreements are stored in PriceDiscTable and evaluated at document entry. The evaluation follows the trade agreement search criteria configured in the accounts receivable or accounts payable parameters:
IFS customer data has both a global party shape and a company-specific trading shape. D365 makes that distinction explicit through the global address book and per-legal-entity customer records.
IFS's commercial capabilities map cleanly to D365 with one significant design task: the supply chain matrix. The matrix is IFS's most distinctive commercial concept, and translating it into D365's distributed intercompany and direct-delivery configuration requires deliberate design work before Wave 3.