1. Remittance Platform
  2. Features
  3. Review and evidence
Feature · Review and evidence

Review and evidence

Retain the decision and supporting material for each instruction revision.

OverviewRecorded Review Decisions
Remittance Platform · Review and evidence

Recorded Review Decisions

Review decisions

New
Source revisionDecisionDecided atReasonParentReviewer
30Approve05 OctApprove rd-452BI-60808
240Return11 OctReject rd-649BI-42167
670Approve10 OctReturn rd-684BI-29717
520Return13 OctApprove rd-834BI-58082
520Approve12 OctReject rd-531BI-31623
6 of 6 records
Approve rd-452Review decisions · RD-22727
Approve
Source revision30
Decided at05 Oct
ParentBI-60808
Example screen with sample data

What you can do

Decisions tied to a revision

Review decisions records reviewer, source revision, decision, time, reason and operation key. Record attachments carries a title, file, upload identity, evidence type and visibility. Operation receipts records guarded action keys, expected revisions, result states and effect references. These records let a reviewer locate both the decision and the material used at the time.

How the work is organized

  • Identify the record. Consider an instruction returned for correction. Treasury Approver records Return with a reason against the source revision. Treasury Operator attaches the corrected supporting file and updates the instruction. A later approval belongs to the new revision. Audit Viewer can trace the earlier return, the later decision and the receipt for the authorized action without treating the first attachment as if it had been overwritten.
  • Keep the decision attached. review decisions retains the reviewer, reason and source revision. A later correction needs its own independent decision.
  • Follow the action. operation receipts keeps the action key and expected revision, so a retry can be checked against the original effect.

The attachment parent and uploader identify the supporting file for an instruction. Its visibility value controls whether the file is internal or shared; the decision record supplies the separate review trail.

What to agree during setup

Agree which evidence is internal and which is shared, and who may upload each type. Decide which changes require renewed approval. A reviewer should inspect the amount, counterparty and account scope before approving; an operation key must identify a retry of the same action. Agree who investigates receipts that show Failed or needs review and how the team records an outcome.

Treasury Manager should assign an investigator for Failed and needs review receipts. Rehearse a stale approval, a returned instruction and a repeated operation key. Keep the attachment and earlier decision available after a corrected revision is submitted.

Check the handoff on an actual case

Prepare an instruction with an attachment and submit it for review. Record a return with a reason. Change the amount and add a revised attachment, then ask an independent reviewer to inspect the new revision. Check that Recorded Review Decisions shows both events and that Failed Operations highlights an unresolved receipt. Confirm an Audit Viewer can read the permitted history without changing it.

The approver receives the current revision, attachments and account scope. After a return, verify that the corrected instruction carries a new decision and that the earlier reason remains visible to Audit Viewer.

What your team sees

  • Pending Review Instructions — Instructions in review with revision, owner and amount visible.
  • Recorded Review Decisions — Reviewer decisions tied to source revisions and reasons.

Follow the work through

Use the related process to rehearse the handoff. Review the data model for the source records and roles for access.

What it keeps track of

Data model
Review decisions
Independent review decisions recorded against an instruction revision.
Record attachments
Uploaded supporting files with visibility scope.
Operation receipts
Durable receipts for guarded operations with stable operation keys.
Bank instructions
Typed banking instructions with revision control and lifecycle state.
Team members
Authenticated platform identities with an operational role in an organization.

Who uses it

Permissions
Treasury Approver
Makes the decision.
Treasury Operator
Supplies corrections.
Treasury Manager
Investigates unresolved actions.
Audit Viewer
Reads the retained history.

Set up Remittance Platform your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started