Primary engagement
TMS application controls review
An independent walkthrough and test of the controls inside your treasury management application — configuration, maker-checker paths, standing data, and the points where cash instructions can be altered.
Typically 3–5 weeks · Treasurers, internal audit, and finance systems owners
Most treasury management systems are implemented under time pressure. Parameters that seemed harmless at go-live — default approval limits, editable payment templates, open standing-data screens — become the path an error or an insider takes years later. We sit with the live application, not a slide deck, and reconstruct how a cash instruction actually travels from request to bank file.
The review covers the modules you actually use: cash positioning, payments, in-house banking, deal capture, bank-statement import, and user administration. We do not audit modules you have licensed but never switched on. Evidence is taken from system extracts, screenshots of configuration, and sampled transactions that you nominate from a recent period.
You receive a findings register, a control map of the application, and a conversation with the people who have to fix what we found. The register is written so internal audit and the treasury operations lead can both use it without translation.
What the work usually includes
- Configuration and parameter review against your treasury policy
- Sample testing of payment, deal, and standing-data changes
- Maker-checker and override path mapping
- Written findings with ranked remediation