Receipt reconciliation

Compare action receipts with local evidence before treating a requested change as completed.

Step by step

Select the parent relationship Sales Manager

Sales Manager identifies the opportunity and the receipts to inspect within authorized organization scope. Read the action and expected revision before drawing a conclusion from the result label.
- Establish authorized scope
- Updates Opportunities, Operation receipts
Gather local evidence Sales Manager

Sales Manager follows the linked effect references and supporting records. The comparison must establish which business effect occurred and which revision it belongs to.
- Trace declared local effects
- Updates Operation receipts, Referral follow ups, Relationship activities, Record attachments, Review decisions
Classify the result Sales Manager

The reconciliation action marks a receipt Completed only when the declared revision and local effect genuinely match. Otherwise it marks the result for review and records the discrepancy for investigation.
- Completed or needs review
- Updates Operation receipts
Record the reconciliation Sales Manager

Retain the reconciliation summary receipt for the parent opportunity. Sales Manager explains any remaining exception to the Relationship Owner and uses the controlled correction path when the work needs repair.
- Preserve summary and discrepancies
- Updates Operation receipts, Opportunities

And how to keep it from happening.

Result label taken on trust. A successful request response is insufficient if the expected local effect cannot be matched. Inspect the actual reference and revision.
Different action confused with this one. The same opportunity may have proposal, review and referral activity. Use the action and operation key to identify the result under examination.
Repeated repair attempt. Retrying with changed input under an old operation key creates a conflict. Investigate the recorded outcome before choosing another authorized action.

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