Review and authorization

An instruction arrives in Review with an owner, counterparty, requested amount and revision. The reviewer checks that it belongs to the right organization and that the requested account scope is supported by the record. The reviewer must be a different person from the submitter. The decision records the source revision, reviewer, time and reason, so a later change to the instruction cannot inherit an earlier approval.

• Present a revision. Operations Analyst brings the instruction, account lines and supporting material to the reviewer.
• Decide independently. Independent Finance Reviewer records a reason and a decision against the same revision.
• Verify the effect. The team checks the decision and operation receipt before treating the request as authorized.

Agree who may review an instruction, how a returned or rejected request is prepared again, and what reason is required for each outcome. Keep membership administration separate from the finance decision. The stable operation key should identify one decision attempt; a retry should inspect its prior receipt rather than create another independent-looking approval.

Ask an analyst to submit a draft and try to approve it themselves. Then let an independent reviewer decide on the current revision. Change the amount after review and check that the earlier decision remains attached to its original revision. Inspect the receipt for the actual effect, including a failed or needs-review result, before considering authorization complete.

Use the same operation key for a repeated decision attempt and inspect the first receipt. If the amount changes after approval, the earlier decision remains evidence for that earlier revision only. A returned request can be edited and sent for another review; a rejected request retains its reason. Keep the reviewer separate from the analyst even when the team is small.

The reviewer should inspect the linked debit and credit lines, the requested amount and the counterparty before deciding. If a line points to an unexpected account, return the request for correction. A decision reason should explain the issue so the analyst can prepare a new revision without rewriting the prior review.

• Instructions in review — Give the reviewer the request amount, owner and current revision.
• Receipts needing review — Follow decisions whose claimed effect needs investigation.
• Confirmed instructions — Trace an approved request through its eventual provider outcome.

See instruction review and provider reconciliation for the full handoff. Implementation sets out the pilot sequence.