Operations control

An operation receipt records an action under a stable key, the instruction revision expected at the time, a result state and references to the effects claimed. The team can use it to check whether a decision, instruction change or provider submission really persisted. A receipt marked pending does not mean the work succeeded. A failed or needs-review result directs the Independent Finance Reviewer to the actual discrepancy.

This matters when a submission times out or a user repeats an action. If the first request already produced a provider reference, repeating it should not create another external instruction. The reviewer checks the existing receipt and its effect references before allowing any further work. Once the real records confirm the claimed effect, the receipt can be completed. An unresolved difference retains a failure reason for follow-up.

• Operation key. A stable identifier ties equivalent action attempts to one intended effect.
• Expected revision. The receipt records which version of the parent instruction the action concerned.
• Outcome. Pending, completed, failed and needs-review states distinguish verification from an assumption.

The App Administrator maintains organizations, counterparties and team membership. These records establish where instructions belong and who can work on them. Financial counterparties carry an eligibility note, contact and active state; financial accounts carry provider identifiers and currency. A membership or configuration change should be visible before a new instruction relies on it. Administrative setup does not confer independent finance approval.

Decide which actions need an operation key and how external references are returned. Agree who investigates a needs-review receipt and what evidence can close it. A retry should inspect existing effects before contacting the provider again. Make the review procedure clear for a missing local decision row, an unexpected instruction revision and a provider identifier that has no matching confirmation.

Set the organization’s time zone and currency with its operators. Confirm which team members are active and which counterparty belongs to each organization. The Auditor needs read access to the recorded action and its eventual resolution, while only the proper operating role should make changes.

Create an action with an operation key and expected revision. Simulate a response whose local effect was written, then repeat the same request and confirm it refers to the existing effect. Simulate a missing effect and mark the receipt for review with a concrete reason. Finally, resolve the missing record and verify the receipt without sending the external instruction again. Check that the instruction’s organization and reviewer remain consistent across the trail.

• Operations needing review — Find pending, failed and discrepant action receipts.
• Active counterparties — Check eligible counterparties in their organization scope.
• Review decision register — Compare claimed effects with recorded reviewer decisions.

See completion verification and provider confirmation for the checks that close an action.