Operation reconciliation

The operation receipt identifies a guarded action through its operation key and action label. The expected revision identifies the opportunity version it was intended to affect. Its result is marked Pending, Completed, Failed or Needs review, with the occurrence date and effect references available to explain the outcome. Keep the receipt attached to the same opportunity as its decisions and customer evidence, including any external reference or failure reason.

Reconciliation starts by reading these records and gathering linked evidence. It should accept completion only when the declared revision and local effect genuinely match. A receipt that disagrees with the evidence belongs in Needs review with the discrepancy recorded. A successful local action also cannot prove an external engineering or compensation effect unless the required external confirmation has been captured and verified.

• Resolve the operation. Sales Manager reads the receipt’s linked opportunity, operation key and expected revision alongside the relevant opportunity. Keep distinct actions distinguishable when the same deal has qualification, review and correction activity.
• Compare the evidence. Inspect linked review decisions, customer activities and supporting files where they support the declared effect. Evidence must relate to the intended revision; a similarly named file or an old approval is insufficient.
• Record the discrepancy. Preserve the existing receipt and its references. A mismatch receives Needs review and failure reason, while the reconciliation action writes an idempotent summary receipt for the linked opportunity.

Agree the completion evidence for each guarded action and how references are resolved. Configure the operation-key rule so retries return an existing result without repeating a business effect. Decide how a changed payload is handled when it arrives with an earlier key, and verify that unauthorized callers cannot use another person’s page-supplied actor identity.

Sales Manager uses a controlled reconciliation action for the allowed receipt update. Authorize that action during setup while retaining the independent review required for changes to business scope. Operation reconciliation does not grant the reconciler unrestricted editing of opportunity history. Auditor reads the evidence and can identify discrepancies without being able to mark them complete.

An opportunity has an Approved engineering inquiry, but its related operation receipt says Completed without a usable effect reference. Sales Manager reads the submitted drawing evidence and the external handoff context. Approval proves the decision; it does not establish that the external effect occurred. Reconciliation must preserve the discrepancy for review rather than using the approval to fill the missing confirmation.

Now supply the verified confirmation for the intended revision and request a fresh reconciliation with its own operation key. Keep the original handoff key and receipt; checking new evidence must not send the handoff again. Replay the new reconciliation key and confirm that it returns the same summary. Rehearse a mismatched revision as well. Auditor should be able to see why that record remains Needs review and which original evidence was preserved during the investigation.

• Pending operation confirmations — Inspect unresolved results alongside the expected revision and supporting references.
• Failed operations — Read the failure reason before choosing a retry or correction path.

Operations Overview brings execution exceptions together with pipeline and engineering review context. Use it as a starting screen, then inspect the actual linked records before resolving a discrepancy.

Reconciliation to verified completion checks the evidence. Scope correction and compensation handles executed effects that need correction. Review the data model before importing historical receipts.