Operation receipt reconciliation

Read Pending, Failed and needs review receipts against the evidence and resolve each one without repeating the action.

Step by step

Collect the exceptions Operations Analyst

Operations Analyst opens the receipts that are Pending, Failed or needs review, or the routine reconciliation runs on its schedule.
- Exception list prepared
- Updates Operation receipts
Read the linked records Operations Analyst

Each receipt is read with its instruction, evidence lines, review decisions and attachments.
- Context gathered
- Updates Instructions, Execution evidence, Review decisions, Record attachments
Compare with the provider Operations Analyst

Where an external reference exists, the receipt is compared with the provider's evidence for scope, identity, quantities and version.
- Match checked
- Updates Operation receipts, Execution evidence
Resolve Operations Analyst

A receipt whose expected effect is present is marked Completed. One that does not match is marked needs review with the discrepancy.
- Receipt Completed or needs review
- Updates Operation receipts
Follow up Operations Analyst

Operations Analyst raises needs review receipts with the provider or the advisor. The external action is never repeated from this step.
- Discrepancy owned
- Updates Operation receipts, Instructions

And how to keep it from happening.

A failed submission is resent instead of checked, and the provider receives it twice.
A receipt is marked Completed without the linked evidence.
Needs review receipts sit unowned for days.

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