Treasury management: requirements checklist
From the guide at bestfinancesoftware.com/guides/treasury, published 29 October 2026. Use your browser's print command; the site header and footer are left off the page.
| Requirement | Vendor A | Vendor B | Vendor C |
|---|
| Must have |
|---|
| Connections to every bank you use, named in the order form, with the method (API, SWIFT, host-to-host or file) for each. | | | |
| A daily cash position by bank, entity and currency, with the time of the last update. | | | |
| Payment approval rules with dual control, and a log of who created and released each payment. | | | |
| Bank account management: a register of accounts, signatories and mandates. | | | |
| Export of balances, transactions and forecasts. | | | |
| Depends on you |
|---|
| Cash forecasting from ERP, AP and AR data, if you forecast weekly or daily. | | | |
| Payments from the platform, if you want to stop releasing payments in bank portals. | | | |
| Investments, debt and FX exposure, if you hold them. | | | |
| Intercompany netting and in-house banking, if you run a group treasury. | | | |
Questions to ask in the demo
- For each of our banks by name: how do you connect, how often does data arrive, and who maintains it?
- Show the cash position for the previous business day, with balances that do not match a bank statement, and how that is flagged.
- Show a payment created by one user and released by another, with the log.
- How is a payee screened before release?
- Show a forecast versus actual for last month, by category.
- What leaves with us if we cancel?
Back to the guide, with the reasons behind each item and the vendors described from their own pages.