Cross-Border Finance Cutover Evidence Lead — Aerospace

The mandate

The defined problem is an evidence gap between finance data conversion and the operational schedules that support aerospace programme balances. A technically completed migration can still leave warranty estimates, programme inventory and intercompany charges impossible to reproduce. The consultant will construct a Finance Cutover Evidence Pack that demonstrates what transferred, what changed legitimately and what remains an approved exception.

The project starts on 19 October 2026 and spans six months at four days a week. Work combines Bengaluru workshops with remote reconciliation development; planned manufacturing visits focus on testing inventory and programme interfaces, not conducting a general operational audit. The deliverable includes a balance lineage catalogue, signed reconciliation protocols, reporting-framework bridge and a controlled exception register suitable for the retained finance team.

Milestone one is due on 18 December 2026: an approved critical-balance inventory, source-to-target map and baseline control-gap assessment. Milestone two, on 18 February 2027, comprises a rehearsed reconciliation suite using a representative conversion and documented corrections. Milestone three, on 18 April 2027, is the final evidence pack, two repeatable reporting rehearsals and completed training transfer. The dates deliberately include validation after design rather than charging the full fee for an early slide deck.

The divisional controller and transformation sponsor jointly accept each milestone. Final acceptance requires every critical balance to reconcile within written tolerances, differences to have an authorised accounting basis, and retained users to reproduce the checks without consultant intervention. Unresolved legal or tax interpretations may remain only as explicitly approved exceptions with owners and deadlines. A functioning software screen is not evidence that financial completeness has been achieved.

The sponsor supplies ledger extracts, migration rules, programme schedules, intercompany agreements and named finance reviewers with authority to resolve issues. The consultant will not configure the ERP, provide statutory audit assurance or decide transfer-pricing policy. Additional entities, new modules or implementation remediation beyond the agreed evidence perimeter require priced change control; the project ends when the pack and reproduction tests are accepted.

What you will own

• Catalogue critical programme balances and rank reconciliation depth by financial materiality, operational dependency and conversion risk, explaining the selected evidence threshold for each.
• Construct source-to-target lineage for inventory, warranty, contract revenue and intercompany accounts, preserving transformation rules, accounting rationale and reviewer identity for independent cutover challenge.
• Design a multi-framework adjustment bridge that explains legitimate Ind AS and international reporting differences without treating every mismatch as migration failure.
• Execute representative conversion rehearsals, distinguishing mapping defects, cut-off errors and pre-existing source inaccuracies in separate issue classes with different correction owners and acceptance consequences.
• Produce a transfer-pricing interface checklist showing where charge bases and entity responsibilities must survive migration, with policy decisions referred to tax owners.
• Hand over acceptance scripts, signed tolerances and reviewer training evidence so retained controllers can repeat the suite after project closure.

Candidate qualifications

• Demonstrate eighteen or more years across financial controllership and transformation, including a cross-border reporting or ERP migration in aerospace or comparable complex manufacturing. Explain your personally authored acceptance evidence, the balance that proved hardest to substantiate and the defect you prevented from passing cutover. Implementation sponsorship alone does not demonstrate the required reconciliation depth.
• Show practical capability in Ind AS and US GAAP or IFRS interfaces involving inventory, contract estimates, provisions and intercompany activity. Provide an example where a legitimate framework difference was initially misclassified as a data defect, and describe how your working paper preserved both the accounting rationale and the migration audit trail.
• Bring a disciplined project-delivery record with bounded scope, reviewer commitments and milestone acceptance. Describe how you dealt with incomplete extracts, late policy decisions or repeated source changes without weakening the evidence threshold. You should be able to specify tolerances and explain why their economic significance matters more than a convenient spreadsheet match.
• Prove retained finance users can operate what you build. Supply an anonymised training or replay test, explain how you transferred exception ownership and identify an item you deliberately kept outside the engagement. Experience with tax interfaces is valuable, but the role must not be presented as a substitute for qualified tax, legal or statutory assurance providers.

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 9 October 2026. Mandate reference PCT-CON-2026-IND-41.