1. Technology CRM
  2. Features
  3. Evidence and reconciliation
Feature · Evidence and reconciliation

Evidence and reconciliation

Preserve the files, review reasons and operation evidence that explain each opportunity's history.

OverviewOperation Exceptions
Technology CRM · Evidence and reconciliation

Operation Exceptions

Operation receipts

New
ParentActionExpected revisionResult stateOccurred atExternal reference
OPP-48722ACT-392940Pending17 OctER-231
OPP-58923ACT-182700Failed11 OctER-393
OPP-94796ACT-89360Needs review07 OctER-135
OPP-22746ACT-179330Pending05 OctER-880
OPP-54344ACT-735600Failed21 OctER-853
6 of 6 records
ACT-392Operation receipts · OR-47826
Pending
ParentOPP-48722
Expected revision940
Occurred at17 Oct
External referenceER-231
Effect referencesER-921
Example screen with sample data

What you can do

Explain what happened to the opportunity

An opportunity’s final stage is easier to trust when the team can follow the evidence behind it. Attachments keep supporting files with the opportunity, including their title, evidence type, uploader and upload date. Internal or Shared visibility distinguishes the intended audience for each file.

Review decisions and operation receipts answer different questions. The decision identifies who reviewed a revision and why. The receipt describes the requested action, expected revision and recorded result, including any failure reason or effect reference. Sales Manager uses this evidence when an operation needs reconciliation; Auditor can inspect the same authorized history without changing it.

How the work is organized

  • Supporting files. Relationship Owner attaches the evidence needed for qualification, evaluation or a commercial decision. Useful titles and evidence types make the file recognizable without forcing the reviewer to guess its purpose from the attachment alone.
  • Recorded authority. Sales Manager leaves a reason with each independent decision. The source revision connects that judgment to the submitted opportunity content and prevents an old decision from becoming approval for a later change.
  • Outcome reconciliation. Unresolved operation claims are compared with their linked local evidence. A matching revision and genuine effect can support completion. A discrepancy remains visible with an explanation that the team can investigate.

What to agree during setup

Agree which evidence types the team will use and when a file can be marked Shared. Rehearse the actual file access path as well as the label, especially when an external document system is connected. Decide what a useful review reason looks like for an approval, rejection or return.

For each guarded action, agree which effect demonstrates completion. A receipt should not be marked complete just because the opportunity’s current stage looks plausible. Define who investigates a revision mismatch and how an executed action will be compensated when a correction is approved. Retain the original history so the later action can be explained alongside it.

Check the handoff on an actual case

Use an opportunity with a reviewed Won outcome and an unresolved operation receipt. Sales Manager compares the receipt’s expected revision with the local opportunity, activity evidence and review decision. If the recorded claim genuinely matches the effect, reconciliation can confirm completion. If it does not, keep a specific discrepancy for follow-up.

Next, have Relationship Owner request a correction to executed scope. Sales Manager must independently authorize the compensating action, and it remains Pending until any required downstream confirmation is real. Confirm that reconciliation does not replay the underlying action to make the records appear consistent. Finish by asking Auditor to reconstruct the original win and the later correction without relying on deleted or rewritten evidence.

What your team sees

  • Operation Exceptions — Pending, failed and review-needed actions with their revision and discrepancy context.
  • Shared Opportunity Evidence — Supporting files marked Shared, with upload responsibility visible.
  • Decision History — The independent decisions behind proposal and outcome changes.

Follow the work through

What it keeps track of

Data model
Operation receipts
Durable receipts for guarded operations with stable operation keys.
Record attachments
Evidence files attached to an opportunity with visibility scope.
Review decisions
Independent review decisions recorded against an opportunity revision.
Opportunities
Sales opportunities with lifecycle, expected value and expected close date.
Relationship activities
Calls, meetings, emails and tasks logged against an opportunity.
Technical evaluations
Technical evaluation records supporting a recorded evaluation outcome.

Who uses it

Permissions
Sales Manager
, Relationship Owner, Auditor.
Sales Manager
Reconciles evidence and authorizes executed-scope compensation; Relationship Owner prepares authorized corrections; Auditor remains read-only.

Set up Technology CRM your way.

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

How to get started