Treasury Accounting Operating Model Director

The mandate

This six-month project will design a treasury accounting operating model that separates transaction execution from accounting ownership while preserving complete handoffs between them. The work addresses deal capture, confirmation, settlement, valuation inputs, ledger posting, reconciliation and close evidence. It does not replace treasury policy, accounting policy or the underlying transaction environment.

The first six weeks will trace selected transaction classes through their full accounting journey and evidence decision delays, duplicate review, manual intervention and ownership gaps. By month three, the director will deliver evaluated design options and a selected accountability architecture. Months four and five pilot critical handoffs; month six finalises the operating handbook and transition roadmap.

Five artifacts govern acceptance: current-state transaction-to-ledger evidence, decision-and-control architecture, evaluated operating-model options, pilot result pack, and final service-and-transition blueprint. Each must distinguish who executes, who supplies evidence, who concludes, who posts, who reconciles and who signs. A single broad owner label will not be accepted.

Management supplies representative transaction and accounting evidence, policy boundaries, control material and access to authorised treasury, accounting and operations leaders. The consulting director may recommend roles, service design and control changes, but cannot execute transactions, make technical accounting conclusions, grant access, choose a platform or sign balances.

The Group Controller accepts the final blueprint after pilot evidence shows timely, controlled handoffs and fewer unexplained breaks across selected transaction classes. Organisation implementation, system configuration, historical remediation and policy rewriting are excluded and appear as sequenced follow-on decisions with prerequisites.

What you will own

• Trace selected treasury transactions from approval and execution through confirmation, settlement, accounting, reconciliation and close evidence.
• Map decision rights separately for treasury execution, valuation input, accounting conclusion, posting, reconciliation and balance sign-off.
• Develop operating options that test centralisation, service delivery, local expertise, resilience and peak-cycle capacity.
• Define evidence and timing standards at each treasury-to-accounting handoff, including exception escalation.
• Pilot critical transaction classes and measure breaks, manual intervention, elapsed time and reviewer effort.
• Recommend a selected service and accountability model; management retains policy, organisation, platform and investment decisions.
• Specify retained capabilities needed to challenge valuations, judgements and unusual events after any execution shift.
• Deliver a transition roadmap with prerequisites, controls, owners and acceptance tests for each wave.

Candidate qualifications

• Demonstrate operating-model work across treasury execution and accounting without collapsing their distinct responsibilities.
• Show a transaction-to-ledger ownership gap you exposed and the control or service consequence it caused.
• Bring depth in confirmation, settlement, valuation inputs, accounting handoffs, posting and reconciliation.
• Provide an example of preserving specialist accounting challenge after operational work was centralised.
• Evidence live-pilot testing of handoffs rather than acceptance based solely on workshops or design documents.
• Show clear respect for reserved treasury, accounting-policy and access authorities.
• Demonstrate fixed-project control when historical remediation or technology build sat outside scope.

Working terms and boundaries

• Five milestones over six months at three days a week cover evidence, architecture, options, pilot and final blueprint.
• The Group Controller accepts each artifact against traceability, decision separation, pilot results and transition usability.
• Management provides authorised transaction evidence, policy boundaries, controls and accountable participants.
• Transaction execution, technical accounting conclusions, access, platform choice, historical cleanup and implementation are excluded.
• Expansion requires a written change note defining added artifacts, inputs, acceptance, schedule and fee.

Application

Applications for this mandate are received in one way only: through the India Board Terminal's application process. It is automated end to end. Your Executive Passport travels to the mandate holder in its confidential form, your answers to the three questions below are read before anything else in your file, and every stage that follows is recorded on your applications page.

There is no address to write to and no intermediary to call. The mandate holder reads what the Terminal delivers and nothing else, which is what keeps the process the same for every applicant and keeps your name out of it until you release it. Applications close on 6 October 2026. Mandate reference FNA-CON-2026-LUX-37.