Client notes
Specific notes from cash desks and controllership teams who invited us into their treasury applications.
They sat with our cash desk in Pattaya for three days, followed a week of FX settlements through the application, and showed us where a dual-approval setting was silently skipped on weekend batches. The findings memo named the exact payment IDs, which made remediation straightforward.
The reconciliation review caught an in-transit FX deal that our month-end position had been overstating for two closes. I wish we had scheduled it before year-end rather than after the board pack went out, but the correction path was clear.
Mandate check was narrower than a full audit, which was what we needed. Three inactive signatories still had release rights in the application. We revoked them the same afternoon and kept the discrepancy register for internal audit.
Communication was calm during a busy payment week. One limitation: read-only access took our IT team longer than promised, so fieldwork slipped two days. Once inside the application, the sample testing was thorough without drowning us in jargon.
Extended story: payment factory after a bank migration
A Bangkok-based group moved beneficiary files to a new bank channel while keeping the same treasury management application. Dev Route Path ran a payment control walkthrough on the first ten business days of live traffic. Operators demonstrated template edits; we matched each released file to bank acknowledgements and flagged two beneficiary changes that bypassed the secondary approver because of a copied template. The desk added a forced re-approval rule and asked us back for the flagship financial audit the following quarter.