Start with a decision the treasurer makes
A fictional manufacturer, Willow Components, wants a daily view of available cash across three accounts. The treasurer needs to know which balances are current, which obligations are due and whether a review is needed before payroll. The first agent task is to assemble that evidence and explain changes; it is not to choose investments or transfer money independently.
Define the question in operational terms: “Which permitted accounts have a recent available balance, and what changes could affect Friday's payroll review?” This gives the agent a bounded reason to retrieve records. A general request to optimize liquidity leaves the action, assumptions and acceptable risk undefined.
Use the responsibility map to assign the analysis, proposal and decision. A treasury agent can prepare a finding while a treasurer remains responsible for the business judgment. If your workflow later includes payment preparation, document that action and its controls separately.
Treasury work by responsibility
Scroll the table to compare all columns.
| Task | Agent output | Human decision | Separate authority needed |
|---|---|---|---|
| Cash visibility | Dated balances with missing sources marked | Confirm completeness for the decision | Read access to permitted accounts |
| Forecast review | Scenario with explicit receipt and obligation assumptions | Accept or revise assumptions | Permission to edit the forecast if enabled |
| Transfer preparation | Versioned proposal between defined accounts | Approve amount, accounts and timing | Draft-instruction access |
| Transfer execution | Provider reference and returned status | Release under the approved policy | Execution permission and valid approval |
Read the source timestamps before the total
Willow's example has an operating account showing $80,000 as of 09:00, a reserve account showing $40,000 as of 08:55 and a collections account showing $15,000 as of the prior day. Adding the displayed numbers gives $135,000, but it does not make the collection balance current. The agent should preserve that difference.
Also distinguish available balance from another balance type. A data connector may return a booked balance, a pending transaction list or a provider-specific field. Ask the integration owner to explain the meaning before the model combines values. A label such as cash available should follow the defined source field, rather than a generated interpretation.
The freshness table is a recommended reporting pattern. It records the source time, the observation time and the limitation beside each number. If a connection fails, keep the last confirmed value marked as old. Replacing it with zero would imply an empty account; repeating it as current would imply fresh evidence that the agent does not have.
A total does not make every input fresh
Scroll the table to compare all columns.
| Account | Displayed USD | Source timestamp | Observation | Treatment |
|---|---|---|---|---|
| Operating | 80000 | October 8, 09:00 | October 8, 09:05 | Current within the example review window |
| Reserve | 40000 | October 8, 08:55 | October 8, 09:05 | Current within the example review window |
| Collections | 15000 | October 7, 17:00 | October 8, 09:05 | Flag as stale; refresh before action |
| Displayed sum | 135000 | Mixed timestamps | October 8, 09:05 | Do not label wholly current available cash |
Evaluate analysis tools at their documented scope
Palm describes Pulse as a treasury data and analysis assistant, with scheduled agents for treasury findings. Its public page is relevant to a shortlist for analysis and reporting. It does not, by itself, establish that a selected Pulse workflow can release a bank transfer. [1]
Ask a vendor to demonstrate the source records behind a finding and how account permissions affect the result. A conversational explanation should lead back to the balance, transaction or forecast assumption used. A chart that cannot be connected to those records is difficult to review when the treasurer needs to act.
Check the meaning of a recommendation as well. An alert about an account approaching a threshold may be an analytical finding. A draft transfer between accounts is a proposed financial instruction. A released instruction is an execution event. A product description using the word agent should not cause those outputs to be treated as interchangeable.
Connect forecasts to obligations and assumptions
Willow expects a $25,000 customer receipt on Thursday and $70,000 payroll on Friday. The receipt is a forecast until supported by the appropriate evidence; payroll is a planned obligation with its own approval process. The agent should keep both dates, their sources and their status visible.
If the customer pays later than expected, the agent can recalculate the scenario and explain the effect. It should not change the expected receipt date merely to avoid showing a shortfall. A useful scenario keeps the original assumption and the revised assumption together so the treasurer can see which difference caused the new result.
Document the treatment of inter-account transfers. A transfer between Willow's own accounts changes account-level liquidity but does not create new company cash. When an agent consolidates records, it should not count the sending and receiving sides as unrelated external outflow and inflow without identifying the transfer.
Use the detailed cash-management guide for a four-week calendar. This category page focuses on the decision boundaries and data needed before a forecast can support an action. Neither example offers investment, tax or regulated financial advice.
Set the limits before preparing an action
For a later transfer-preparation task, specify permitted accounts, currencies, amount limits and the person authorized to approve the proposal. Include a rule for what happens when a balance is older than the workflow permits. These are recommended controls for the task, not a claim that every treasury system supplies identical settings.
An approval should refer to the same proposal that the execution system receives. If the agent changes the amount, destination account or planned date, return the relevant version for review. Otherwise the treasurer may approve one decision while the system performs another.
Consider concurrent work. If two agent runs both see the same available funds, each may prepare a proposal that appears affordable in isolation. The application needs a way to review the combined commitments before execution. A prompt asking the model to remember the daily budget is insufficient evidence that simultaneous actions stay within it.
Revocation belongs in the test plan. Remove the agent's access and confirm that scheduled tasks stop using that connection. Previously prepared proposals should remain visible for the owner to resolve, while revoked credentials should no longer authorize new work.
Test the finding before granting more authority
Build a small test around Willow's stale collection balance, a delayed customer receipt and an internal transfer. Write the expected explanation for each. The agent should identify the stale source, preserve the delayed receipt as an assumption and avoid presenting the transfer as newly earned cash.
Measure answer correctness against the source records and separately assess whether the output helps the treasurer make the intended decision. Count missing accounts and unsupported totals, not only successful retrievals. A finding can be arithmetically correct while incomplete because it omits a material account.
Have the treasurer reproduce one report manually using the same dated inputs. The purpose is to establish an expected result for that set, not to claim a universal performance percentage. Save the test and repeat it when the connector, account scope or model instructions change.
The final pilot decision should identify the permitted data, output and reviewer. A successful analysis test supports that analysis workflow. It does not automatically justify execution permissions. The controls guide provides a way to document any proposed expansion.