Decompose GP sales and purchase document families into D365 order, shipment, receipt and invoice events, resolve the three POP receipt types, and design an open-document load that reconciles headers, lines, freight, tax and distributions.
Procurement and sales is where the posting crosswalk stops being a design artefact and starts producing numbers someone will check. It is also where the largest single behavioural difference between the two systems lives.
The mental shift is from documents to events. A GP document type describes a thing that exists and progresses. A D365 order lifecycle describes a sequence of discrete events, each of which posts.
The source material identifies three receipt types in the source: shipment, shipment and invoice, and invoice. Each implies a different target sequence.
The highest-risk rule in the entire GP set is the SOP posting selector: whether revenue and cost of goods sold follow the item or the customer. Its keys include module, the posting choice, item class, customer class and site — five dimensions of variation in one decision.
The source material calls for reconciliation across header, line, freight, tax and distribution totals. Five separate checks, and the reason is that they fail independently.
Open sales orders and open purchase orders move as a single wave in the dependency-ordered plan, after master data and before inventory positions. The internal sequence within this domain:
Supported by the source material: the document-family mappings and their process-redesign classification, the five posting rules and their risk ratings, the three POP receipt types, the customer-versus-item residue, and the five-way reconciliation requirement.
SOP and POP families become event sequences, not target documents. Both are composite process-redesign mappings at high confidence — the strongest evidence in the GP set. Timing becomes explicit. Cost recognises at shipment or receipt, revenue and payables at invoice.