Review and decisions

The Case Analyst prepares a vault transfer and moves it to Review. A Credit Reviewer examines the amount, party, account scope and supporting documents for that revision. The decision record holds the source revision, reviewer, decision, date, reason and operation key. It points to the parent transfer. This makes the decision understandable later, even when the transfer has progressed to another status.

Approval is an act by a named person. The reviewer must be independent of the preparer. An App Administrator can maintain people and organization settings but does not gain that approval authority from membership administration. The Auditor can read the resulting evidence without editing the decision or executing a transfer.

• Review queue. Bring requests in Review to the Credit Reviewer with revision and amount visible.
• Decision record. Capture Approve, Reject or Return with a reason and the revision examined.
• Receipt trail. Retain the operation key and effect references that explain what the action changed.

Agree what the Credit Reviewer must inspect before approving. Account scope and supporting attachments should be ready when the transfer reaches Review. Define who can return an incomplete case, what reason is useful to the Case Analyst, and how a changed revision comes back for a fresh decision. The review practice should distinguish a rejected request from a request returned for correction.

Decide how the team handles an operation receipt left Pending or marked needs review. A receipt represents an attempted effect under a stable operation key. Review its actual references and failure reason before anyone treats it as complete. A repeated request with the same key should lead to the existing outcome rather than a second provider effect.

Have one Case Analyst prepare a draft with a transfer amount, party and debit and credit scope. Move it to Review. A different Credit Reviewer records a decision on that source revision and provides a concrete reason. Check that the decision points to the same parent transfer and that the transfer status reflects the outcome. Change the draft detail in a second rehearsal: the earlier decision should not cover the changed revision. Also try a self-review attempt and confirm that the independent reviewer rule is upheld.

Finally, open the related operation receipt. Its expected revision and operation key should connect the action to the decision. If its effect references cannot be verified, keep the case in the review path rather than calling the operation complete.

• Transfer review inbox — Requests waiting for a decision with revision, amount and owner in view.
• Receipts needing review — Operations whose claimed effects need a human check.
• Transfer status board — Requests grouped by their current status without losing their decision trail.

Read transfer authorization for the human decision and completion verification for receipt review.