Treasury-Platform Control Recovery Leader

The mandate

A recent treasury-platform release activated new bank interfaces before account, entity and approval data had been fully reconciled. Several cash positions now arrive through duplicate or stale statements, payment repair queues bypass expected visibility and derivative confirmations do not consistently reach accounting. Emergency manual workarounds keep critical vendors paid but weaken segregation and leave regional finance unsure which platform record is authoritative. The transformation director has exited, creating an executive gap across treasury operations, controls and technology during the next release cycle.

In the first thirty days, the leader must establish a safe-payment perimeter, certify active bank accounts and interfaces, classify manual workarounds and reconcile critical cash and deal populations to bank evidence. By day seventy-five, the board needs a root-cause view separating design defects, configuration, master data, access, message mapping, bank implementation and user practice. The first 120-day window must deliver a controlled recovery release, independently tested rollback conditions and a reduced exception queue without freezing legitimate regional operations.

Decision rights include stopping unsafe interfaces, approving temporary treasury procedures, assigning defect owners, prioritising backlog, certifying operational readiness and accepting control evidence inside the approved programme envelope. The interim may require dual authorisation and suspend nonessential functionality where exposure is unquantified. Platform replacement, material vendor claims, bank termination, accounting-policy decisions, cyber-risk acceptance and capital expenditure beyond delegated thresholds remain with named executives and committees.

Recovery must culminate in durable ownership. The leader will appoint or prepare the permanent treasury operations head, establish product, process and control owners, document each bank-interface lineage and run two month-end closes plus one major release with the successor in command. Handover evidence will include the account inventory, access recertification, interface catalogue, open-defect severity, control test results, vendor obligations and decisions that should not be reopened without new facts.

The remit excludes coding, penetration testing, statutory audit conclusions, hedge strategy, bank mandate signatures, payment release outside formal authority and sole approval of accounting treatment. Technology teams remain responsible for builds, cyber for security assurance, banks for their channels and finance control owners for attestation. The interim must not convert urgent workarounds into permanent design merely because they reduce backlog quickly.

Why this seat is open

The failure crosses bank connectivity, treasury practice, systems delivery and financial control, while ownership fragmented after the programme director left. Waiting for permanent recruitment would carry manual exposure through additional closes and a scheduled release. A temporary executive can impose one risk-based sequence, make time-sensitive control decisions and transfer a stable operating model to the incoming leader.

What you will own

• Establish the safe-payment perimeter, critical-account certification, workaround register and daily cash-confidence reporting for executive review.
• Reconcile accounts, bank statements, payment queues, confirmations, deals and ledger feeds across platform and external evidence.
• Separate defects by design, configuration, master data, access, messaging, bank setup and user practice with accountable owners.
• Govern recovery releases through entry criteria, test evidence, segregation checks, rollback conditions and post-deployment observation.
• Direct vendor and bank remediation against contractual obligations, service evidence, defect severity and operational consequence.
• Certify process, product and control ownership for payments, cash positioning, debt, investments, derivatives and reconciliation.
• Hand over the interface catalogue, access model, control library, defect debt, release governance and unresolved risk decisions.

Candidate qualifications

• Has held executive treasury-operations authority through a failed treasury-management-system implementation or control-critical release.
• Understands bank statements, payment messages, confirmations, deal interfaces, cash positioning, access, reconciliation and ledger integration.
• Can distinguish technology defects from poor master data, control design, bank configuration and operating-practice failures.
• Has stopped unsafe functionality while preserving essential payroll, tax, supplier and debt-service payments across multiple entities.
• Brings credible vendor, bank, audit, cyber and finance-control engagement during high-pressure remediation and release governance.
• Has transferred a recovered treasury platform to permanent ownership after observed closes and a successful production release.

Non-negotiables

• Can work onsite in Chennai and complete monthly bank and regional-control visits throughout the assignment.
• Brings direct treasury-platform recovery with payment decision exposure; programme management without treasury depth is insufficient.
• Will not weaken dual approval, conceal exceptions, backdate evidence or accept a release solely to satisfy timetable pressure.
• Has no undisclosed financial interest in the incumbent platform vendor, implementation partner, participating banks or assurance providers.

1. 49 words maximum. Which reconciliation would you complete before allowing repaired payments back into automated release?
2. 49 words maximum. How would you decide whether a manual workaround is temporarily safe or must stop immediately?
3. 49 words maximum. What must the successor demonstrate during the observed release before handover is complete?