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 · CFO, treasurer, and company secretarial
Treasury policy is often updated after a board cycle; the application is updated when someone has time. The gap between the two is where unauthorised products, entities, or limits live. We read the current policy, the bank mandates, and the live configuration, then set them side by side.
We pay attention to dormant entities still enabled, products that were ‘just for testing’, and approval matrices that still reflect an organisation chart from two restructures ago. Breach reporting — what the system can detect versus what the policy says must be escalated — is part of the same comparison.
The deliverable is a gap table the treasurer can take to the next policy review, with a recommended sequence for closing the gaps that actually move cash.
What the work usually includes
- Limit, product, and entity mapping from policy to TMS
- Bank-mandate versus application-entitlement comparison
- Exception and breach-reporting path review
- Board-ready summary of gaps