1. Healthcare CRM
  2. Features
  3. Operation Reconciliation
Feature · Operation Reconciliation

Operation Reconciliation

Check guarded action results against their expected revision and recorded local effects.

OverviewReceipt Exceptions
Healthcare CRM · Operation Reconciliation

Receipt Exceptions

Operation receipts

New
Operation keyActionParentExpected revisionResult stateOccurred at
OK-614ACT-828OPP-20000720Failed11 Oct
OK-416ACT-105OPP-83144250Needs review16 Oct
OK-560ACT-721OPP-46497940Failed23 Oct
OK-894ACT-808OPP-72709230Needs review16 Oct
OK-703ACT-250OPP-81113700Failed08 Oct
6 of 6 records
OK-614Operation receipts · OR-17950
Failed
ActionACT-828
ParentOPP-20000
Expected revision720
Occurred at11 Oct
Failure reasonCut to length
Example screen with sample data

What you can do

Confirm what the action actually changed

A submitted action can leave the team with a question: did the intended change happen, or does someone need to investigate? Operation receipts preserve the action, its operation key and expected revision beside the parent opportunity. The Sales Manager uses these details to compare the requested work with the local evidence of its effect.

An action can be pending, completed, failed or awaiting review. A completed result requires a matching effect and revision. A result awaiting review carries the discrepancy that prevents that conclusion. The Relationship Owner can use the exception information when deciding what to do next, while the Auditor can trace the recorded result without repeating the business action.

How the work is organized

  • Stable attempts. A guarded action uses an operation key to recognize an equivalent retry. Repeating the same request should return the original result; reusing the key with conflicting input must be refused.
  • Evidence comparison. Reconciliation reads linked local evidence and compares it with the declared revision. The receipt keeps effect references and any failure reason so the team can inspect why the result needs attention.
  • Controlled correction. Correcting or canceling work requires an authorized actor, a reason and the current revision. Executed work needs reviewer-approved compensation and stays pending until downstream confirmation arrives.

What to agree during setup

Agree what local effect each action is expected to produce and how the team identifies it from the receipt. A referral completion should be traceable to the intended follow-up under the correct opportunity. A receipt for a different action or revision cannot establish that the requested completion occurred.

Name the Sales Manager who investigates exceptions and the independent reviewer who approves a compensating action when needed. Agree how an external reference is supplied if the work reaches a connected system. The existence of that reference is a starting point for inspection; the confirmation must establish the actual downstream result before pending compensation can be treated as complete.

Check the handoff on an actual case

Rehearse a completed referral action whose response the Relationship Owner did not receive. Retry with the original operation key and equivalent input. The team should receive the original outcome without creating another effect. Then change the input while retaining the key and confirm that the conflict is refused.

Next, inspect a receipt whose recorded effect does not match the expected revision. Reconciliation should mark the result for review with a useful discrepancy. Ask the Sales Manager to explain the mismatch and agree the authorized next action. Where work already took effect downstream, retain the original history and rehearse reviewer approval of compensation while its confirmation remains pending.

What your team sees

  • Receipt Exceptions — Failed actions and evidence discrepancies requiring investigation.
  • Decision Register — Review reasons used to establish whether a correction has independent authority.
  • Outcome Register — Closed relationships whose evidence can be checked against action results.

Follow the work through

Use receipt reconciliation for the evidence check and correction and compensation for work that needs a controlled repair.

What it keeps track of

Data model
Operation receipts
Stable operation receipts recording guarded action outcomes and effects.
Opportunities
Relationship opportunities with lifecycle, expected value and expected close date.
Referral follow ups
Nonclinical referral follow-up extensions routed through independent review.
Review decisions
Independent review decisions recorded against a source revision.
Relationship activities
Qualification, proposal and outcome activity evidence for an opportunity.
Record attachments
Uploaded evidence files linked to an opportunity with a visibility scope.

Who uses it

Permissions
Sales Manager
Reconciles evidence and coordinates exceptions.
Relationship Owner
Supplies context and executes eligible actions.
Auditor
Inspects receipts and the preserved history.

Set up Healthcare CRM your way.

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

How to get started