Compare a declared action result with its source revision and saved effects before confirming completion.
Sales Manager identifies the customer work whose operation receipts need checking. Start with the saved records and their evidence. Relationship Owner can explain the intended request, but that explanation should be checked against the retained result.
The reconciliation action reads linked activities, decisions and effect references for each receipt. Verify the submitting actor and operation key before applying a reconciliation result. Keep unrelated customer work outside the selected scope.
Sales Manager reviews whether the receipt's declared revision matches the effect that genuinely exists. A successful request response is insufficient when the saved record differs from the declared result or the relevant evidence cannot be found.
Matching local evidence permits a Completed result. A discrepancy remains in the needs-review state with its explanation. This is an evidence check rather than a new commercial approval decision, and it does not replace downstream confirmation for a pending compensation.
The action writes one summary receipt per parent under its operation-key rule. Sales Manager follows up exceptions, while Auditor can trace the original request and the reconciliation without losing either history.
And how to keep it from happening.
Start free, then use Proto to change fields, steps and approvals before your team goes live.