Operations control

An operation receipt keeps a stable operation key, action, expected revision, result state and references to effects. It records what a guarded action attempted and what the system can actually verify afterward. The completion workflow reads local records before declaring success. If a claimed decision, instruction status or provider reference is absent, the receipt moves to needs review with a concrete reason. The verification step never sends the external action again.

Operations Overview gives the team a place to see current work and recorded exceptions. A pending provider result, an unverified evidence item and a receipt that needs review have different owners and next actions. The Auditor can inspect the trail without changing it. The App Administrator manages membership and organization setup, but does not gain authority over an instruction simply because they can maintain access records.

• Effect trail. Operation receipts bind an attempted action to an expected instruction revision and effect references.
• Read-first check. Verification inspects persisted decisions, provider identifiers and status before completion.
• Scoped access. Organization membership separates the preparer, independent approver, administrator and auditor.

Choose who investigates a receipt in needs review, how the provider is contacted when an external effect is uncertain, and how the resolution is documented. Keep operation keys stable across retries so equivalent requests remain idempotent. Review user-to-team-member mappings and active status before assigning any operational role. Set the organization boundary and time zone for each team. Reports and exports should follow the same access scope as the underlying records.

A provider submission may time out after the provider accepts it. The preparer sees an uncertain result and should not simply press submit again with a new key. The team checks the existing receipt, provider instruction reference and evidence. If the local effect is missing, the receipt records a needs-review discrepancy. A repeated verification reads the same evidence and does not issue a second provider instruction. The investigator can then resolve the difference using provider confirmation and retained local history.

Rehearse a successful operation with all expected records present and an incomplete operation missing its claimed effect. The first may become completed; the second must keep a clear discrepancy for the reviewer. Retry verification with the same operation key and confirm that the result remains consistent. Test an Auditor account against a guarded action and verify that read access does not allow execution. Test an App Administrator account as well: membership maintenance alone should not approve or submit financial work.

• Receipts Needing Review — Investigate actions whose persisted effects do not support completion.
• Instruction Status Board — See current work by instruction state without treating every state as final.
• Unverified Bank Evidence — Identify provider material awaiting a check.

Read completion verification, independent authorization and bank reconciliation.