A record of AI treasury activity for the examiner
Author
Audrey
NobleCloak's AI Correspondent · AI-drafted, fact-checked against our sourced evidence before publishing.
Date Published
Sooner or later an examiner asks a bank a plain question: where is AI being used, and what has it done? In treasury the question has an edge, because the actions in question move money.
A bank that has put assistants in front of its treasury team can usually answer the first half from memory. The second half is harder. What did the assistants actually do last quarter? Which actions were refused? Who said yes to the ones that needed a yes? Reconstructing that from chat transcripts and screenshots is slow, and the transcripts were never meant to be evidence.
The problem in the treasurer's terms
The treasurer is not looking for a clever answer. The goal is to hand over a record that was kept as the work happened, in a form someone outside the team can read. That means three things.
- It covers every AI-assisted treasury action that runs through NobleCloak, not a sample the team picked.
- It includes the attempts that were refused, because a policy that never refuses anything proves little.
- It names the person each action ran for and, where approval was needed, the person who approved.
A record assembled after the question arrives is a reconstruction. One that was written as each decision was made is a record.
The policy
The record is only as meaningful as the policy behind it. For a treasury team the rules are the same per-tool lines used everywhere else in NobleCloak.
Action | Who | Decision |
|---|---|---|
Read balances, positions, and statements | Treasury assistants and the cash agent | Allowed |
Release a wire | AI-initiated release | Needs approval, routed to a named officer or role |
Tools for roles outside treasury | Everyone else | Not listed |
Each line produces entries. An allowed read is a line. An approved release is a line. A declined release is a line. The policy decides and the record keeps what it decided.
Who approves, and where
Where a tool is set to needs approval, the request goes to a named approver or role, such as a Treasury Officer. They answer in Slack or the web inbox. The approval is what puts a name on the action.
For the examiner conversation this matters twice. Operationally, the right person made the call. As evidence, the answer to "who authorized this wire" is a line in a record, not a recollection.
What the Record of Decisions shows
The Record of Decisions has one entry per decision: who asked, which agent, which tool, the decision, who approved, and when. Pulled for a quarter, it lets the treasurer answer the examiner's questions in the examiner's order.
- What did the assistants do? The entries for allowed reads and approved releases, grouped by tool.
- What was refused? The denied entries on any tool set to deny. Roles outside treasury do not have the wire tools at all, so the tools are not available to them.
- Who approved? The approver on each entry that needed one, with the time.
- Whose session was it? The user each entry ran for.
The record sits alongside the bank's own systems rather than replacing them. The wire platform still has its logs, and the core still has its journal. What the Record of Decisions adds is the AI-specific layer those systems cannot see: which agent asked, which tool, the decision, and who said yes. Describe it to an examiner as it is, a working record of policy decisions, and show the real entries rather than a summary.
What this does not do. It says nothing about whether the bank meets any particular rule, and it is not a substitute for the bank's own controls and procedures. It is evidence of what happened, kept as it happened. What the bank concludes from it is the bank's judgment.
Related scenarios
- Wire release goes to a treasury officer: the approval line that produces the entries an examiner will ask about.
- SOX evidence for AI-touched entries: the same record, pulled by internal audit for journal entries.
- Hospital AP sees invoice evidence: an AP manager exporting the record of AI-created bills.
- New beneficiaries denied to AI: a denied tool, and the refusals that show up in the record.
Get started and see the record on your own treasury tools.

