Operation Reconciliation

An advisor may submit an action and still need to confirm what happened. Operation receipts keep the action name, expected revision and result state together with the parent opportunity. The receipt also carries references to local effects and, when relevant, a reference in an external system. Sales Manager uses that evidence to investigate an uncertain outcome.

A receipt can be pending, completed, failed or in need of review. Relationship Owner can see why an action needs attention without assuming that another click is the right remedy. Auditor can inspect the action and its evidence in the authorized scope. The operation key identifies the request so an equivalent retry can return the original result.

• Request identity. Keep the same operation key when repeating an equivalent request. A different payload with that key is a conflict to resolve. The expected revision identifies the opportunity version the action intended to change, protecting work that another person has already updated.
• Effect matching. Sales Manager compares the selected receipt with sibling receipts for the same opportunity, the parent revision and the linked local effects. When an external reference exists, inspect the configured authoritative source before deciding that the action finished.
• Exception handling. Read the recorded failure reason and keep the uncertain action visible until its effects can be explained. Correction or cancellation begins with the current record and the evidence of what already executed. Preserve accepted outcomes while resolving the remaining scope.

Choose who watches the exception queue and how Relationship Owner hands an unresolved case to Sales Manager. Agree which source is authoritative for each external reference and who can obtain its result. A local receipt should not be treated as confirmation from a separate system when that confirmation is required for the action.

Rehearse the difference between unexecuted work and a completed effect before introducing corrections. The reviewer needs enough context to identify the parent opportunity, action and intended revision. Plan a route for cases that need further investigation; do not remove them from attention merely to make the queue appear empty. See the connections plan for source ownership.

Use a fictional proposal action whose response is interrupted after submission. Relationship Owner finds its receipt and asks Sales Manager to check the outcome. The manager compares the expected revision with the opportunity and opens the effect references before choosing the next action.

Repeat the identical request using its original operation key. Confirm it resolves to the original result without another business effect. Then try a changed request with that key and a request against an older revision. Both need to be rejected as conflicts. If the receipt names an external result, rehearse an unavailable source and keep the exception open until the reviewer can inspect authoritative evidence.

• Operation Exceptions — Investigate pending, failed and review-needed actions using their failure reasons and effect references.
• Review Decision Register — Check the decision history when a correction concerns a previously reviewed opportunity.

Use operation reconciliation for investigation and correction, and customer outcome before closing a household’s advisory opportunity.