Finance Master Data Remediation Director

The mandate

This four-month engagement will remediate the finance master-data conditions that generate payment, posting, reconciliation and reporting exceptions. It is intentionally bounded: the objective is to evidence critical populations, correct agreed high-risk records, implement durable ownership and prove a controlled maintenance route. It is not a general data-cleaning exercise or a replacement of the underlying platform.

In the first month, the director will deliver a risk-ranked baseline for selected finance master domains, including duplicate indicators, incomplete control attributes, inactive records still in use, unauthorised changes and conflicting ownership. The baseline must distinguish erroneous records from legitimate variants. Remediation may begin only after the relevant control owner accepts the classification and rollback approach.

Four artifacts govern the work: an evidenced population and risk baseline, a signed remediation rulebook, an executed correction-and-validation pack, and a future-state ownership handbook with 90-day assurance tests. Milestones fall at the end of each project month. Acceptance requires traceability from affected record to rule, approval, action and downstream validation.

Management will supply approved extracts, record histories, policy requirements, control descriptions and qualified domain owners. The director may design correction logic and coordinate its controlled execution but cannot grant access, alter live records personally, override approval segregation or conclude on balances. Any missing history or ambiguous authority is documented as residual risk.

The Group Controller accepts the final milestone after sampling shows that high-risk corrections are complete, downstream processes reconcile, and new maintenance requests follow the agreed route. Excluded domains or lower-risk populations will be left in a sequenced backlog with effort ranges, dependencies and recommended ownership rather than silently absorbed into the fixed fee.

What you will own

• Define critical finance master-data populations and rank risks by payment, posting, reporting, control and privacy consequence.
• Produce exception rules with false-positive testing so legitimate variants are not erased in the pursuit of superficial cleanliness.
• Create a remediation rulebook covering approval, rollback, evidence, segregation and downstream validation for each correction class.
• Coordinate controlled correction of the accepted high-risk population while preserving an auditable record-to-action trail.
• Validate downstream effects through payment, subledger, general-ledger and reporting checks appropriate to each domain.
• Establish request, review, approval, periodic recertification and emergency-change ownership for future maintenance.
• Recommend, but not approve, access changes, system configuration or investment required beyond the bounded project.
• Deliver a residual backlog with exposure, effort, dependency and accountable disposition for each excluded population.

Candidate qualifications

• Demonstrate finance master-data remediation where record correction was proven through downstream accounting or payment outcomes.
• Show an instance in which a simplistic duplicate rule would have destroyed legitimate variants and how you prevented it.
• Bring command of approval segregation, effective dating, record history, rollback, reconciliation and evidence retention.
• Provide a traceable example from exception identification through owner acceptance, controlled correction and post-change validation.
• Evidence the ability to coordinate technical execution without seeking privileged access or bypassing operational control owners.
• Describe how a permanent ownership model reduced recurrence after a concentrated remediation effort.
• Show fixed-fee discipline when excluded domains, poor history or expanding record populations threatened the project boundary.

Working terms and boundaries

• Four monthly milestones cover baseline, rulebook, executed correction pack and ownership handover at four days a week.
• The Group Controller accepts each artifact against population completeness, approval traceability, rollback readiness and downstream validation.
• Management provides approved extracts, record histories, policy constraints and authorised personnel for live changes.
• The director cannot grant access, make unapproved live changes, certify balances or replace the platform.
• Scope additions require a signed change note; unresolved lower-risk populations remain in the transparent residual backlog.

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-DXB-13.