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 · Programme sponsors and treasury project leads
A new treasury application, a payment-factory cutover, or a bank-channel replacement is not the moment to discover that dual control was never configured. We join late enough to see the real build, early enough that findings can still be fixed. The work is scoped to the change, not a full historical audit.
We sample migrated standing data and open deals, watch a rehearsal if one exists, and read the runbook as an operator would at 2 a.m. on Saturday. Open defects are classified by whether they can wait, must be mitigated, or should stop the cutover.
The steering committee receives a short opinion: ready, ready with named conditions, or not ready. We stay available through the first week of live running if you want a follow-up on the conditions.
What the work usually includes
- Readiness review of controls, roles, and bank channels
- Migration-reconciliation sampling
- Cutover runbook and rollback-path critique
- Go-live opinion letter for the steering committee