Multi-Jurisdiction Payments Reporting Blueprint Consultant

The mandate

The defined issue is inconsistent reconciliation between payment operating metrics, local financial balances and the regional management pack. Differences may reflect entity scope, settlement cut-off or reporting policy, but currently appear as unexplained adjustments. The consultant will produce a Payments Control-Reporting Blueprint that identifies those bases and makes the approved bridge repeatable.

The six-month assignment begins on 19 October 2026 at four days a week. Mumbai is the working location with remote access to agreed regional counterparts. Selected entity and reporting interfaces are frozen at inception; the blueprint includes a metric dictionary, source-to-ledger mapping, reconciliation rules and a control-ownership matrix, supported by a representative two-entity pilot.

By 18 December 2026, milestone one delivers the entity-scope inventory, signed definition baseline and a classification of existing breaks. Milestone two on 18 February 2027 provides the mapped reporting bridge and tested exception workflow using representative settlement periods. Milestone three on 18 April 2027 is the corrected pilot, accepted operating guidance and retained-reviewer reproduction of both entity and regional views.

Acceptance is jointly given by the regional sponsor and the affected local finance owners. Key operating volumes and financial amounts must reconcile using approved scope and cut-off definitions; legitimate differences require a documented basis rather than forced numerical equality. Users must trace a selected metric to its source and demonstrate escalation of a new exception without consultant intervention. The blueprint is not an opinion that every local regulatory return is legally compliant.

The sponsor supplies settlement extracts, local reporting policies, finance ledgers and named reviewers with access and time to resolve questions. The consultant does not prepare licence applications, submit regulatory returns, implement a payment platform or take daily settlement control. Additional jurisdictions and historical remediation require change approval. The engagement closes with the accepted blueprint and replay tests, leaving residual policy interpretations with appointed specialists.

What you will own

• Inventory reporting scopes and metric definitions across the agreed entities, identifying where apparently comparable volumes refer to different processing or settlement populations.
• Map operating evidence to ledger balances and regional adjustments, preserving cut-off assumptions and local-policy references in the blueprint's lineage catalogue.
• Classify reconciliation breaks as source errors, timing, scope, policy or unresolved ownership, with distinct evidence and escalation requirements for each class.
• Design exception controls that prevent repeated unexplained adjustments from entering the management pack without an accountable reviewer and documented approval.
• Run the two-entity pilot through representative settlement periods, recording legitimate reporting differences rather than forcing local and regional amounts to match artificially.
• Transfer the reporting dictionary, reconciliation rules and ownership workflow through retained-reviewer tests on newly introduced metrics and exceptions that were not rehearsed during design.

Candidate qualifications

• Demonstrate senior finance delivery in payments, fintech or related multi-entity technology operations with a verifiable chronological record. Provide a reporting or control blueprint you personally authored, the hardest operating-to-financial mismatch and how acceptance was obtained. Leadership title alone is insufficient; the work requires detailed reconciliation and clear policy boundaries.
• Show practical understanding of settlement cut-off, entity scope, fee recognition and management reporting interfaces. Explain a case where a regional metric could not be matched directly to a local balance, and how your lineage or definition work established a legitimate bridge instead of an unsupported adjustment.
• Bring professional accounting competence and experience collaborating with local regulatory or statutory owners across jurisdictions. Describe how you documented policy dependencies and prevented a central reporting design from overriding local responsibility. Candidates are not expected to provide every local compliance opinion, but must know when specialist interpretation is necessary.
• Prove fixed-scope project discipline with stakeholder acceptance, data access controls and retained-user transfer. Evidence should include a pilot, an exception taxonomy and a replay test using unfamiliar records. Explain how you managed additional entity requests or incomplete inputs without silently broadening the engagement or claiming untested completeness.

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