Review and authorization

An instruction in review needs a human decision before it can move to provider submission. The Independent Finance Reviewer checks the organization, counterparty, amount, account directions and supporting material. The review decision records the reviewer, source revision, decision, reason, time and operation key. A decision belongs to that revision; changing the instruction after review calls for a fresh look.

The reviewer cannot approve a submission they prepared. The analyst’s ownership and the reviewer’s member identity make that separation visible. A rejected instruction remains in the trail with its reason. Returning work for correction should also preserve what was reviewed, so the analyst can address the actual issue instead of guessing from a status.

• Queue. Instructions marked Review form the decision inbox.
• Evidence. Attachments and account scope give the reviewer a concrete basis.
• Outcome. The decision row and instruction status show what happened to the submitted revision.

Set the reviewer assignment rules by organization and confirm who may see financial detail. Keep administrative membership distinct from reviewer entitlement. Agree when a changed amount, counterparty or account scope creates a new revision and which supporting records must be present before a reviewer approves. These rules need to hold when someone uses an action outside the visible screen.

Decide how to handle rejection and correction. An analyst should understand whether to revise the existing instruction or prepare a new one for a materially different provider request. In either case, retain the original decision and evidence. The operation receipt gives a stable key for the decision action and lets the team inspect a repeated request.

An analyst asks to send a provider instruction for a USD amount. The reviewer sees the instruction in the inbox and notices the credit account points to a different counterparty’s account. They record a rejected decision with the reason. The analyst corrects the account scope and submits a new revision. A different reviewer checks the corrected scope and approves it. The two decision rows make the sequence understandable later; the earlier rejection does not disappear when the instruction becomes authorized.

During rehearsal, try a reviewer acting on their own submission and an approval request carrying an outdated revision. Both should be rejected before a status change or provider action occurs. An auditor should be able to inspect the reason without editing the decision.

• Instructions needing review — Revisions waiting for a finance decision.
• Instruction workboard — The boundary between preparation and authorized work.
• Receipts needing verification — Decision attempts whose recorded effect needs checking.

Review an instruction and verify operation completion.