Operations reconciliation

An operation receipt records the action, operation key, expected revision, parent case, occurrence time and result state for guarded work. External reference, effect references and failure reason help the Operations Analyst decide what happened. Pending, Failed and marked for review are work states, not proof that an external effect should be repeated. Completed requires evidence of the actual local effect.

The analyst checks the case revision, organization scope and matching activity before resolving a receipt. A duplicate operation key, missing evidence or partial local effect needs investigation. Where an external provider is involved, its reference should be verified under the configured integration rules. An ambiguous acknowledgement must remain visible until the team can establish the outcome.

For example, a payment request may time out after the provider has accepted it. The receipt might still read Pending. Reconciliation compares the provider reference, case and existing disbursement event. If an effect exists, the team records the verified outcome once. If the external state cannot be established, the analyst retains a review-needed state and a reason. Closing a case with an unresolved receipt would hide a potential duplicate payment.

• Prepare. The responsible person records the case or activity with its current scope and evidence before asking for a decision.
• Decide. The assigned reviewer checks the record, authority and revision before changing its outcome.
• Verify. Finance and operations staff compare the saved effect with the source evidence before treating work as complete.

Assign an analyst with authority to inspect provider references, case evidence and local activity. Agree how long pending actions may stay unresolved and who escalates an external uncertainty. Set a clear rule for marking Completed only after the effect is verified. Decide which failure reasons need the finance owner before closure.

Run a known completed action through reconciliation and compare its receipt with the actual event and case revision. Then test a pending receipt with no verified effect, a duplicate key and a cross-organization reference. The analyst should be able to explain each result from evidence. Confirm that a case cannot be treated as fully closed while a material receipt remains unresolved.

• Operations Needing Reconciliation — Pending, failed and review-needed actions with their keys and failure reasons.
• My Funding Cases — Assigned requests with their due dates and current state.

Read the related process and the implementation plan before the first live cycle.