Evidence reconciliation

Compare guarded action receipts with the effects they claim and surface discrepancies.

Step by step

Select the receipt Sales Manager

Sales Manager starts with a pending operation receipt and its parent opportunity.
- Pending action located by parent
- Updates Operation receipts, Opportunities
Read the declared action Sales Manager

The manager checks the stable operation key, action, expected revision and any linked effect references.
- Operation key and expected revision checked
- Updates Operation receipts
Compare local evidence Sales Manager

The opportunity, inquiry, review decision, activity and attachment trail are inspected as relevant to the action.
- Linked effect inspected
- Updates Opportunities, Group stay inquiries, Review decisions, Record attachments, Relationship activities
Reconcile evidence Sales Manager

When the declared revision and local effect agree, the receipt is completed; when they differ, it needs review with a discrepancy. The reconciliation itself writes a summary receipt.
- Pending → Completed or needs review; summary receipt
- Updates Operation receipts
Resolve exceptions Sales Manager

The owner and reviewer use the recorded reason to correct the business case or investigate the effect before another guarded action.
- Discrepancy investigated without deleting history
- Updates Operation receipts, Opportunities

And how to keep it from happening.

A receipt says completed while the local linked effect does not match its expected revision.
An external reference is treated as proof of a local status move without checking the local record.
A retry uses a new operation key and obscures the original attempt.
A discrepancy is cleared by editing history rather than investigating and recording the correction.

Start free, then use Proto to change fields, steps and approvals before your team goes live.