Classify the requested relationship change
Synthetic O-199 belongs to customer C-51. Moving its billing email from accounts-a to accounts-b within C-51 is a recipient update. Asking to bill a different organisation C-52 is a billing-party change requiring a decision on the order baseline. Neither change automatically transfers completed work or the customer record. Use fictional endpoint labels rather than real addresses in this worksheet.
| Request | Customer link | Change class | Required action |
|---|---|---|---|
| accounts-a to accounts-b at C-51 | C-51 unchanged | Recipient update | Confirm endpoint and future notifications |
| Bill C-52 instead | Customer still C-51 until decided | Billing-party change | Review baseline with responsible owner |
| Transfer completed work to C-52 | Separate relationship request | Customer/work transfer | Separate decision; no inferred transfer |
Update the intended layer only
- Identify requested party or recipient
- Compare current order relationships
- Obtain the appropriate baseline decision
- Update related future communication
A changed email display field cannot be used to conceal a different billing organisation.
accounts-b is confirmed within C-51. Must historical completed-task records be moved to C-52?
Show the worked answer
No. This is a recipient update within C-51. There is no supported C-52 relationship change.
No tax-invoice, contract-transfer or credit-control rule is asserted. This fixture identifies the operational decision that must be resolved.