Fraud-to-Financial-Loss Control Map and Pilot Lead

The mandate

The defined problem is that operational fraud indicators do not consistently explain recognised financial loss or contingent exposure. The consultant will map that relationship for agreed platform flows and test an exception-control pilot. The project does not authorise investigations, user sanctions or legal conclusions about suspected conduct.

Deliverables are a fraud-to-financial-loss state map, a control-and-evidence matrix and a live-tested exception pack. The map must distinguish suspicion, confirmed event, recoverable balance and recognised loss. Each transition should identify the evidence needed and the internal authority responsible, rather than allowing a risk label to become an automatic accounting entry.

Case-lineage work runs from 19 October 2026 through 18 February 2027 over four months. The 23 November first milestone provides the state definitions and sampled incident reconciliation. Milestone two on 11 January delivers the control map and pilot design. Milestone three on 18 February delivers live pilot findings, revised rules and user transfer. Three days weekly are required.

Acceptance is shared by the CFO and risk operations sponsor. They must trace selected cases from incident evidence to financial treatment, reproduce the loss calculation and route a fresh exception without consultant interpretation. The pilot includes reversals and recovery events. It cannot claim acceptance by reporting fewer alerts where the financial consequence remains unexplained.

The sponsor supplies authorised minimised incident records, finance entries and named risk and accounting reviewers. Work is hybrid from Mumbai with planned operating workshops. Investigation execution, customer sanction policy and wholesale transaction remediation are excluded. Additional incident families require an approved scope change; confidential evidence must stay inside authorised systems and cannot be reused in other security or finance work.

What you will own

• Define incident-to-finance states with risk and accounting owners, recording the evidence required before suspicion, recovery or loss can change reporting treatment.
• Reconcile sampled incidents to financial entries, separating missing source support, timing differences and genuinely unresolved recovery assumptions in the first milestone.
• Build a controls matrix that identifies who detects, investigates and approves each consequence, preserving segregation between operating evidence and accounting decisions.
• Design the live exception pilot around material and recurring flows, specifying baseline quality measures and authorised handling of sensitive case records.
• Test reversals and recoveries through the pilot, ensuring the same event cannot remain counted as both full loss and recovered value.
• Analyse pilot failures and revise rules without concealing inconclusive cases, documenting what evidence remains necessary for an internal judgement on the financial consequence.
• Transfer the operating pack through fresh-case execution by nominated users, retaining unresolved limitations and maintenance ownership before seeking final acceptance.

Candidate qualifications

• Show hands-on finance assurance or loss-control work in a consumer platform or comparable transaction environment. Explain how incident evidence was connected to accounting consequence and identify the authority you did not hold.
• Demonstrate technical judgement about recovery, reversals and contingent exposure. Candidates should describe a loss estimate that changed when event states were clarified, including the evidence that prevented double counting.
• Provide a control map or exception pilot that users could operate after transfer. Explain the fresh cases tested and how the pack distinguished missing evidence from a decision requiring specialist approval.
• Evidence disciplined consulting boundaries around sensitive incidents. Show how access was minimised, how investigative work remained with authorised owners and how scope expansion was approved rather than silently absorbed.
• Demonstrate professional finance capability and analytical delivery at functional-head or senior-specialist level. The project needs reproducible evidence and practical control design, not unsupported claims of legal, forensic or executive authority over every incident outcome. Explain the treatment of an incident with a confirmed operating event but uncertain recovery value. Show the evidence required for finance judgement, the unresolved assumption retained in the pilot and how the pack prevented a provisional estimate from becoming an unquestioned reporting fact.

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-09.