Carry customer orders and purchase orders across as sales and purchase orders — then do the harder work of normalising the revenue, accrual and intercompany determinants that decide where those documents post.
This is the domain where the mapping table and the risk register disagree, and the disagreement is instructive.
Three source rules cover the sales side: shipment with revenue and cost of goods sold, the invoice itself as part of that rule, and returns.
Two source rules cover the purchasing side, and their common theme is event separation.
Where two locations landed in the same legal entity, movement between them is a transfer order and belongs to Inventory. Where they landed in different legal entities, movement between them is a trade flow, and it belongs here.
The evidence base does not describe CloudSuite Industrial's pricing model at all. That is a genuine gap, and the honest response is a discovery specification rather than a mapping.
The wave model places open sales orders and open purchase orders together, with a gate that is refreshingly specific: open document count and value agree with the source, line by line.
The documents map directly. A customer order becomes a sales order, a purchase order becomes a purchase order, and the header-and-line structures correspond well enough that the load is routine.