1. Automotive Dealers CRM
  2. Features
  3. Evidence and Reconciliation
Feature · Evidence and Reconciliation

Evidence and Reconciliation

Trace customer evidence and guarded action results before deciding that an operating step is complete.

OverviewReceipt Exceptions
Automotive Dealers CRM · Evidence and Reconciliation

Receipt Exceptions

Operation receipts

New
ParentActionExpected revisionResult stateOccurred atFailure reason
OPP-76317ACT-323840Failed17 OctCut to length
OPP-61278ACT-147960Needs review06 OctWeld frame
OPP-61103ACT-830140Failed10 OctDrill and tap
OPP-32099ACT-979720Needs review17 OctDeburr
OPP-77003ACT-50120Failed03 OctAssemble
6 of 6 records
ACT-323Operation receipts · OR-97497
Failed
ParentOPP-76317
Expected revision840
Occurred at17 Oct
Failure reasonCut to length
Operation keyOK-709
Example screen with sample data

What you can do

Explain the result from the retained evidence

An opportunity’s evidence includes relationship activities, uploaded files, independent review decisions and operation receipts. Attachments carry a title, evidence type, uploader, upload date and an Internal or Shared visibility choice. Decisions retain the source revision and reviewer reason. Together these records help the team explain what was requested, what was reviewed and what result followed.

An operation receipt identifies the action and its stable operation key, expected revision and result state. It can also retain effect references, an external reference and a failure reason. Sales Manager uses read-first reconciliation to compare that declared result with the linked local evidence. A mismatch remains available for review instead of being treated as completed work merely because a request was submitted.

How the work is organized

  • Supporting files. Attach evidence to the correct opportunity and choose its visibility deliberately. A clear title and evidence type help the reviewer distinguish the current customer scope from earlier material.
  • Action result. Use the receipt to identify the requested operation and revision. Pending, Completed, Failed and the needs-review state describe different results that the owner must interpret before taking another action.
  • Reconciliation. Compare the receipt’s declared revision with its linked effect. Complete only the result supported by that evidence, and retain the discrepancy when the record needs further investigation.

What to agree during setup

Agree which evidence belongs in Internal or Shared scope and who can access the underlying file. Define who investigates a failed operation and who can reconcile a result. Make sure the team can trace a repeated operation key to its original request rather than creating another customer effect because a screen response was uncertain.

Decide how corrections distinguish work that has not executed from work whose effect already exists. Cancel unexecuted scope without deleting its history. When executed scope needs a compensating action, obtain independent approval and keep it pending until the responsible downstream system confirms the result. Agree how those external confirmations reach the reviewer and how unresolved discrepancies are followed up.

Check the handoff on an actual case

After a reviewed proposal, ask Sales Manager to inspect the operation receipt and the corresponding decision evidence. Run reconciliation and confirm that the declared revision and saved effect support the result. Repeat the same operation key and inspect the retained outcome rather than creating another proposal action.

Then use a rehearsal receipt whose effect does not match the declared revision. Reconciliation should retain a needs-review result with an explanation. Attach a supporting document as Internal and check access with an authorized reviewer and an unrelated organization’s user. Finally, rehearse a correction to executed scope: the approved compensating request must remain pending until its downstream confirmation arrives. Auditor should be able to trace both the original action and the correction without losing the earlier evidence.

What your team sees

  • Receipt Exceptions — Failed actions and discrepancies that need investigation before the team proceeds.
  • Pending Operation Receipts — Requested work whose completion still needs to be established.
  • Internal Evidence — Supporting files with internal visibility for the opportunity review.

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 reviewer decisions on a frozen source revision.
Relationship activities
Calls, meetings, emails and tasks logged against an opportunity.
Opportunities
Vehicle sales and service opportunities with a guarded lifecycle.

Who uses it

Permissions
Sales Manager
Reconciles eligible results.
Relationship Owner
Prepares supporting evidence and follows up exceptions.
Auditor
Reads the authorized history.

Set up Automotive Dealers CRM your way.

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

How to get started