Vice President, Engineering Group Reporting and Cross-border Controls

The mandate

An engineering group produces consolidated reporting from project entities using different local accounting practices and submission conventions. Central adjustments make the published totals agree, but too many material treatments cannot be traced back to an accepted entity position. The Vice President will own the reporting control that makes consolidation technically credible and explainable across the group's Indian and overseas finance interfaces.

Financial reporting needs to preserve the distinction between local books, group accounting and an additional reporting-framework requirement. A correctly translated entity submission may still contain inconsistent estimate treatment or an intercompany entry that lacks a supported counterparty position. The leader will investigate those differences before they become recurring central corrections, maintaining a transparent bridge through the frameworks and approval routes relevant to each reporting obligation.

Twenty-seven specialists and controller counterparts will operate through the VP's reporting perimeter. The initial twenty-four-month agenda establishes submission evidence, adjustment ownership and technically sound review of material framework differences. The function will use the group's existing consolidation environment, including controlled application configuration where necessary. It should not require a new platform merely to make the current treatments and interfaces understandable.

The VP approves reporting procedures, delegated consolidation adjustments and technical review priorities, with material policy changes and significant historical corrections submitted to the CFO and appropriate governance body. Qualified country advisers own local legal and regulatory interpretations; treasury owns risk policy and project teams supply execution evidence. Statutory signing responsibilities remain with authorised officers. This role does not independently restructure entities, certify project progress or determine tax positions.

The employment contract is permanent and open-ended; the two-year reporting agenda defines initial performance expectations, not an expiry date. The first anniversary should bring a defensible material-adjustment register and entity-to-group bridge, followed by stronger controller ownership and fewer unexplained repeat entries. Ongoing leadership maintains technical quality, audit coordination and practitioner development as project structures and financial reporting requirements change.

What you will own

• Establish an entity-to-group reporting bridge showing local balances, framework adjustments and consolidation entries separately, ensuring material figures remain traceable rather than emerge only as accepted central totals.
• Decide the technical review agenda for significant Ind AS and US GAAP reporting differences, assigning competent treatment owners and escalating unresolved positions before the reporting timetable confers apparent approval.
• Govern intercompany submission consistency through paired records and approved counterpart positions, distinguishing translation or timing differences from unsupported entries that cannot safely be eliminated without investigation.
• Build a material-adjustment register with source evidence, rationale and approving authority, testing why repeated corrections remain necessary and whether the underlying entity reporting weakness has genuinely changed.
• Lead consolidation application-control reviews with technology owners, verifying mapping, access and configuration evidence without allowing system convenience to dictate an unsupported accounting treatment or reporting classification.
• Coordinate external audit and country-controller challenge on material reporting judgements, maintaining clear ownership of responses and transparent limitations where factual or specialist evidence is still incomplete.
• Develop regional reporting managers through technical case reviews and submission rehearsals, reducing dependence on central explanations and ensuring incoming controllers can maintain the accepted group reporting logic.

Candidate qualifications

• Demonstrate senior engineering, infrastructure or comparable cross-border group reporting leadership with direct consolidation and control responsibility. Describe a central adjustment whose underlying entity position you rebuilt, the evidence inspected and the reporting decision reached. Participation in group reporting is insufficient without proof that you personally challenged technical substance and established continuing ownership of a material treatment.
• Bring practical knowledge of Ind AS and US GAAP reporting interfaces, with disciplined investigation of framework differences and project-related estimates. Relevant experience should distinguish local-book accuracy from group-policy application and an additional reporting requirement. Explain a difference that could not be solved by currency translation or mapping alone, and how you secured an appropriately reviewed accounting conclusion.
• Show strong consolidation systems and audit-evidence judgement, including controlled mapping, reciprocal submissions and reproducible adjustment trails. Familiarity with Hyperion or an equivalent enterprise reporting environment is useful when supported by technical understanding. Describe a case where a functioning application produced a misleading treatment because the underlying source or configuration assumption was wrong, and explain the repair and validation performed.
• Establish a record of developing reporting specialists and influencing overseas controllers constructively under deadline pressure. This VP needs clear technical communication, delegation and material escalation. Provide a disputed group treatment you led through review, the authority retained by the CFO or statutory officer and how later reporting cycles demonstrated that entity teams could sustain the accepted position without relying on your personal intervention.

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 13 October 2026. Mandate reference CVU-PER-2026-IND-070.