Services
Engagements written against the application you run.
Each review is scoped in a letter. The list below is how clients usually name the work. Fees are quoted after we know the modules, the banks, and the sample period — this page is not a shop.
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
Payment factory & host-to-host
Payments and bank connectivity audit
Testing of payment factories, host-to-host channels, file encryption, beneficiary changes, and the last mile between the TMS and the bank.
Typically 2–4 weeks
Positions, statements, ledgers
Treasury data integrity and reconciliation testing
Independent testing of cash positions, bank-statement loads, deal valuations, and the reconciliations that feed the general ledger.
Typically 2–3 weeks
Who can do what
Access, segregation of duties, and privileged users
A structured review of roles, conflicting entitlements, shared IDs, and the privileged accounts that can bypass maker-checker in the TMS.
Typically 2–3 weeks
Before the cutover weekend
Pre-go-live assurance for a TMS change
A time-boxed review of configuration, migration, controls, and cutover rehearsal before a new TMS, module, or bank channel goes live.
Typically 3–6 weeks, aligned to your cutover
What the board approved vs what the system allows
Policy and mandate alignment
A comparison of board-approved treasury policy, bank mandates, and the limits, products, and entities actually enabled in the application.
Typically 2–3 weeks