Translate procure-to-pay and order-to-cash across the TCA boundary — supplier and supplier site into vendor and address, customer account and site use into customer and delivery settings — and keep match policy, accrual timing and AutoInvoice line types as explicit design points.
Trade is where the party model and the document model meet, and both change shape on this path.
Start with an inventory of behaviour rather than of records. For each supplier site and each customer site use in live use, record what it determines.
The master-data guidance gives a rule that sounds obvious and is routinely ignored: migrate only live master-data variants, not every historical duplicate.
The purchase order and receipt mapping is direct, and its note carries the warning that matters: retain match policy and accrual timing as explicit design points.
On the sales side, the sharpest instruction in the whole posting rule set applies here: do not collapse AutoInvoice line-type differences into one rule.
Payment terms, customer groups and vendor groups load early, before the active master data that depends on them. Three points from the playbook's controls apply:
Open sales orders and open purchase orders carry across in the third wave of the migration plan, with a gate requiring open document count and value to agree with the source line by line. That gate defines what "carried across" has to mean.
Trade between operating units is the last piece, and it is entirely determined by the organisational design.
The party model reduces on this path — TCA parties, supplier sites and customer site uses carry more structure than the target's customer, vendor and address model. The reduction is manageable if the behaviours attached to each site are inventoried and relocated deliberately, and unmanageable if sites are treated as addresses.