1. Treasury Bills & Bonds
  2. Features
  3. Activity and Evidence
Feature · Activity and Evidence

Activity and Evidence

Keep bank evidence and documents on each instruction and a receipt of every guarded treasury action.

OverviewUnverified Bank Evidence
Treasury Bills & Bonds · Activity and Evidence

Unverified Bank Evidence

Bank evidence

New
ParentLine numberEvidence typeProvider event IDAmount USDOccurred at
BI-33202470StatementPEI-11154019 Oct
BI-79976610ConfirmationPEI-82052011 Oct
BI-33279610SettlementPEI-46628009 Oct
BI-60310810CorrectionPEI-58370014 Oct
BI-41085350StatementPEI-54461003 Oct
6 of 6 records
PEI-111Bank evidence · BE-72196
Statement
ParentBI-33202
Line number470
Amount USD540
Occurred at19 Oct
Example screen with sample data

What you can do

Keep the proof behind every instruction

Each instruction collects evidence from the provider: statements, confirmations, settlements and corrections. Every evidence line has a line number, the provider event ID, the time, the amount, the evidence type and whether it is verified. Documents such as trade tickets, auction results and board mandates are attached with a title, evidence type, uploader, time and visibility of Internal or Shared.

Every guarded action, such as an authorization, a submission or a reconciliation, leaves an operation receipt with the action, a unique operation key, the version it expected, the outcome, the time, any external reference and the failure reason. Outcomes are Pending, Completed, Failed or needs review. A repeated action with the same key returns the original receipt.

How the work is organized

  • Evidence verified by settlements. The Settlement Analyst marks evidence verified after checking it against the provider.
  • Receipts for every guarded action. A retry never sends an instruction twice; it returns the original receipt.
  • Exceptions in one list. Failed and needs review receipts sit together for the analyst.

What to agree during setup

Agree who verifies provider evidence and how. Decide the evidence types you attach and which documents may be shared with auditors or banks. Agree how a needs review receipt is resolved and who signs off. Set the schedule for the routine receipt reconciliation.

Check the handoff on an actual case

During a bank outage, the Settlement Analyst submits an authorized sale instruction and the connection times out. The receipt stays Pending and the instruction stays Submitted. The analyst does not resend. The routine reconciliation later finds the bank’s confirmation evidence for the same provider identity, verifies it, and the receipt is marked Completed.

Another submission has no matching evidence by the end of the day. Its receipt is marked needs review with the reason, and the analyst calls the bank before deciding anything further.

What your team sees

  • Unverified Bank Evidence — Evidence lines waiting for verification, with type, amount and time.
  • Failed Receipts — Receipts that failed or need review, with action and failure reason.
  • Operation Receipts — Every receipt with its outcome and external reference.

Follow the work through

Plan the provider connection before submitting instructions.

What it keeps track of

Data model
Bank evidence
Provider statements, confirmations, settlements and corrections attached to an instruction.
Record attachments
Supporting documents uploaded against a treasury instruction.
Operation receipts
Durable idempotency receipts for every guarded treasury operation.
Bank instructions
Typed banking instructions raised by treasury and authorized by an independent approver.

Who uses it

Permissions
Settlement Analyst
, Treasury Approver, Admin.
The Settlement Analyst verifies evidence and resolves receipts.
The Treasury Approver reads the trail when deciding.
Admin
Reviews receipts during audits.

Set up Treasury Bills & Bonds your way.

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

How to get started