Operations Overview surfaces execution exceptions alongside the sales and engineering context. Reconciliation then reads the underlying records to establish whether a guarded action produced its declared effect. A visible Completed label is a claim to check against evidence, rather than evidence on its own.
Sales Manager inspects Pending operation confirmations and Failed operations within authorized opportunity scope. Resolve linked opportunity, action and operation key before deciding which evidence belongs to the result.
The configured reconciliation action validates the actor and reads local evidence associated with the receipt. Compare its expected revision with the relevant opportunity and the revision retained on the independent decision. Inspect applicable activities or attachments for the declared effect.
Sales Manager uses the controlled action to accept Completed only where the declared revision and local effect genuinely match. A discrepancy becomes Needs review with failure reason. Required external confirmation remains necessary for engineering completion or compensation.
The action retains a reconciliation summary receipt per linked opportunity using its operation-key idempotency rule. Replay returns the existing result without another summary or a repeated business effect. A fresh check after new evidence uses a distinct reconciliation key, retaining the original business operation and its receipts.
Relationship Owner supplies missing evidence or prepares an authorized correction. Auditor can trace why a result was accepted or left unresolved. Reconciliation itself does not approve revised proposal scope or invent an external acknowledgment.
And how to keep it from happening.
Start free, then use Proto to change fields, steps and approvals before your team goes live.