Cross-Entity Regulatory and Management Reporting Reconciliation Lead

The mandate

The defined problem is that cross-entity reporting differences cannot consistently be explained as source defects, legitimate definitions or unresolved policy questions. The consultant will build the reconciliation design for agreed report families. The project does not prepare regulatory filings or issue a prudential interpretation.

Deliverables are a reporting definition book, source-lineage map and reconciliation operating pack. The design must preserve differences that genuinely arise from measure or entity scope, rather than force totals to match. Each unresolved item should identify the evidence missing and the authorised owner of the next decision.

Five months of design work begin on 19 October 2026 and conclude on 18 March 2027. The first milestone, 30 November, delivers sampled definitions and source gaps. The second, 25 January, supplies the lineage and pilot reconciliation pack. The final 18 March milestone completes fresh-report validation and custodian transfer. Three delivery days weekly are required.

Acceptance is by the regional CFO and reporting sponsor with nominated entity owners. They must reproduce selected differences from source, classify a fresh exception and route a policy question without consultant arbitration. The pilot includes a changed definition and a late source correction. A balanced total achieved through unexplained adjustments will not meet acceptance.

The sponsor provides authorised reporting records, definition ownership and access to nominated accounting and policy specialists. Gurugram remains primary with planned global remote workshops. Filing execution, accounting-policy approval and full reporting-platform implementation are excluded. Additional report families with materially different regulatory or entity mechanics need approved scope control before the fee or completion date changes.

What you will own

• Catalogue reporting definitions and entity scope from authorised records, identifying which measures are genuinely comparable before constructing a cross-entity reconciliation rule.
• Trace sampled measures through entity filters, cutoff rules and source transformations, recording where missing data, classification defects or legitimate definition differences first alter the reported value.
• Build exception files that identify the affected measure, unmatched scope and next authorised decision, preventing unsupported adjustments from making genuinely incompatible management and regulatory totals appear reconciled.
• Map policy and accounting escalation routes to authorised owners, preserving the distinction between analytical classification and approval of a regulatory interpretation.
• Pilot changed definitions and late corrections through the pack, testing whether users can explain the resulting movement without rewriting prior assumptions privately.
• Validate fresh report cases with entity and reporting users, revising ambiguous rules while retaining legitimate differences in scope and source mechanics.
• Transfer lineage maintenance through a custodian-led late-correction case, checking that the affected report measure, residual limitation and policy escalation remain traceable before sponsors accept the reconciliation procedure.

Candidate qualifications

• Demonstrate hands-on regulatory or management reporting reconciliation in financial services. Explain a cross-entity difference, the source transformation involved and why the measures should or should not have matched.
• Show technical finance judgement about definitions and classification. Candidates should describe a balanced total that concealed unsupported adjustments and the evidence used to expose the underlying defect.
• Provide a reconciliation design tested through changed definitions or late corrections. Explain a user failure, the rule or ownership ambiguity discovered and the revision made before sign-off.
• Evidence consulting acceptance with fresh report cases and internal transfer. Show how users reproduced a difference and how additional report families were kept inside approved scope rather than silently extending ongoing support.
• Demonstrate controlled handling of confidential reporting records and professional finance capability. The project does not confer filing or prudential approval authority. Candidates should explain how a policy question remained visible after the pack was accepted, what authorised evidence could resolve it and why deliverable completion did not imply that the consultant had assumed entity responsibility for every unresolved reporting judgement. Show how a fresh report family was assessed after transfer when its title resembled an existing measure but its regulatory scope differed. Candidates should explain the comparison test, the limitation retained and why the case needed new authorised interpretation rather than automatic reuse of the original reconciliation rule.

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 PCT-CON-2026-IND-20.