Operations control

An operation receipt records a stable operation key, action, expected revision, result state, occurrence date and parent accounting document. It can also hold an external reference, effect references and a failure reason. These fields make a financial action traceable after a retry, interruption or uncertain provider response. They help the team ask what was attempted and what actually happened rather than equating an attempted action with a completed one.

The verification work is read first. The reviewer checks whether the effects named by the operation receipt really exist in local records. If the referenced decision, status or provider evidence is missing, the receipt needs review with the discrepancy recorded. A verification pass does not submit a second external instruction. An equivalent repeated verification should produce the same result.

• Stable identity. The operation key and expected revision identify the action being checked.
• Effect references. Linked record identifiers tell the reviewer where to verify the claimed outcome.
• Resolution. Completed and needs-review results distinguish observed effects from discrepancies.

Choose how operation keys are generated for each guarded action and how long retry records remain visible. Agree who investigates a needs-review receipt and what evidence is sufficient to close it. A failure reason should point to the concrete missing or conflicting effect, not just say that a check failed. Keep the parent document and its organization in the investigation path.

The team should test interrupted submissions as part of the pilot. A provider may have accepted an instruction while the local response was lost. The reviewer must inspect the provider reference and local records before any further execution. A repeat request with the same operation key must not create a second financial effect. A changed document revision needs its own controlled decision.

An approved document is submitted and the operation receipt remains pending because the response path stops. The reviewer first checks the parent document, provider instruction identifier and supporting event evidence. If the stated effects exist, the receipt can be marked completed. If the provider reference exists but the local status is inconsistent, the receipt needs review with that difference recorded. The verification step never sends the instruction again merely to make the receipt look complete.

A second verification of the same operation key should leave the recorded outcome stable. An auditor can follow the receipt to the originating document, decision and external reference. This is especially useful when a correction occurs later, because the earlier verified effect remains part of the history rather than disappearing behind the latest status.

• Open operation receipts — Find pending and needs-review actions with their expected revisions.
• Confirmed documents — Compare the claimed outcome with the document and provider evidence.

Verify an operation and check roles.