Finance Data Governance Blueprint Director

The mandate

Finance data is currently discussed as a technology dependency, while ownership of definitions, quality decisions and permissible corrections remains unclear. This six-month project will create a finance-led governance blueprint that can be operated, audited and extended. The deliverable is not a catalogue exercise; it is a decision system for the data that supports close, control, management reporting and external reporting.

The director will begin with four financially material information chains selected by the accountable sponsor. During month one, each chain will be traced from originating event to reported measure, documenting transformations, reconciliations, manual interventions and decision owners. Month two ends with a signed critical-data and definition baseline. The following months test stewardship, issue resolution and change governance in live reporting cycles.

Six artifacts anchor acceptance: the information-chain evidence pack, critical-data register, finance definition standard, ownership-and-decision map, pilot governance record and scalable implementation blueprint. Each artifact must show source evidence, disputed points and approvals. A diagram without named decision rights or a glossary without observed use will not pass acceptance.

Finance will provide reporting outputs, lineage evidence available to it, control descriptions, issue logs and timely access to data producers and consumers. Technology and operating teams will provide interface knowledge and change constraints. Where an asserted lineage cannot be evidenced, the director must mark the uncertainty and propose a controlled verification route rather than represent inference as fact.

The Group Controller accepts the final blueprint in month six after two live pilot cycles demonstrate faster issue ownership, controlled definition changes and improved traceability. The project excludes platform selection, data engineering, retrospective correction of balances and permanent stewardship staffing. Those may be recommended as sequenced follow-on decisions with costs and dependencies.

What you will own

• Trace four material information chains from originating event to finance output, identifying transformation, reconciliation, manual adjustment and ownership discontinuities.
• Define criteria for critical finance data based on financial exposure, judgement dependence, control reliance and decision consequence.
• Establish a definition standard covering calculation, grain, timing, permitted use, source, owner and change history.
• Design stewardship roles with authority to resolve routine quality issues and explicit escalation for cross-boundary definition disputes.
• Pilot an issue workflow that records detection, containment, root cause, accountable correction, validation and closure evidence.
• Create change-governance rules that prevent silent alterations to finance definitions or reporting logic.
• Recommend prioritised implementation waves; management retains platform, staffing and investment approvals.
• Hand over an implementation blueprint with capability needs, controls, measures and a 12-month adoption sequence.

Candidate qualifications

• Demonstrate delivery of finance data governance grounded in reporting and control use, rather than an enterprise glossary detached from operations.
• Show an example of tracing a reported measure through transformations and manual intervention to reveal an ownership or control failure.
• Provide evidence that stewardship roles you designed were used to resolve live issues and did not remain nominal assignments.
• Bring fluency in finance definitions, reconciliations, lineage, access, change governance and evidence retention without dependence on a named platform.
• Explain how you represented lineage uncertainty honestly while maintaining delivery momentum and executive confidence.
• Show experience securing acceptance from finance leaders and practical participation from technology and operational data producers.
• Evidence fixed-project discipline, including artifact acceptance, input dependency management and controlled treatment of follow-on scope.

Working terms and boundaries

• Six milestones cover evidence baseline, critical-data scope, definition standard, ownership design, live pilot and final blueprint over six months.
• The Group Controller accepts milestones against traceability, decision-right clarity, pilot use and documented approval within five working days.
• Management supplies reporting samples, available lineage, issue records, control material and named participants to the agreed schedule.
• Platform procurement, engineering build, historical balance correction and permanent stewardship staffing are excluded.
• Any additional information chain requires a written change note specifying evidence needs, schedule effect and revised 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 10 October 2026. Mandate reference FNA-CON-2026-FRA-09.