Premium-to-Reserving Finance Reconciliation — Consulting Lead

The mandate

Premium records, reserving inputs and general-ledger outputs cannot be explained through a single controlled lineage. The consulting problem is to identify where timing, mapping and ownership differences create financial exceptions. It does not ask the consultant to calculate actuarial reserves or pronounce on the adequacy of insurance pricing.

The named deliverable is a Premium-to-Reserving Finance Reconciliation Pack: source maps, cutoff definitions, exception rules, reconciliation samples and a treasury-control interface register. Each rule must distinguish a genuine financial inconsistency from an expected methodological difference. The pack will preserve the identity of the responsible specialist instead of manufacturing a finance-owned answer for every break.

Starting 19 October 2026, the project reaches its first milestone on 30 November with a source-and-cutoff inventory and tested sample. The second milestone, on 11 January 2027, delivers reconciled premium, reinsurance and reserving-input modules. Final acceptance on 18 February covers the complete pack, treasury interface tests and internal operator rehearsal; payments are 25%, 35% and 40% respectively.

The finance head and risk operations sponsor accept deliverables only when sampled balances reproduce from approved extracts, exceptions route to the correct owner and historical cutoff differences are explicitly explained. An actuarial liaison validates interpretation of reserving inputs, not a consultant-produced reserve opinion. Final tests include rerunning a new period without altering rules simply to force agreement.

The sponsor supplies anonymised transaction samples, ledger extracts, approved reserve-input definitions, treaty references and access to treasury reviewers. Production access is read-only and any customer-sensitive data is minimised. System replacement, regulatory filing, actuarial model development and historical restatement are outside the fixed fee; a material discovered dependency must be handled through signed change control.

What you will own

• Map premium and reserving-input sources to ledger outcomes, retaining transformation logic and cutoff rules at each relevant boundary for reviewer reproduction of sampled balances.
• Select samples that include cancellations, amendments and late postings, avoiding a test population containing only straightforward completed transactions that would conceal the principal reconciliation risks.
• Define exception categories with finance, actuarial and reinsurance owners so expected methodological differences are not misclassified as accounting errors or resolved through arbitrary ledger adjustments.
• Reconcile reinsurance-linked movements through documented references, preserving disputed contractual interpretations for authorised specialist resolution while assigning an accountable interim finance treatment and review date.
• Test treasury interfaces against payment instruction, settlement and ledger evidence, identifying control gaps distinct from ordinary posting timing and showing their potential financial consequence.
• Produce reproducible reconciliation scripts or documented calculations with access controls, version history and explicit limits on unattended use, including named review gates for overrides.
• Train internal operators through a fresh-period rerun and deliver accepted remediation options for unresolved dependencies without implementing unapproved system changes.

Candidate qualifications

• Demonstrate insurance reconciliation or finance transformation work connecting source transactions to ledger reporting. Show a difficult exception resolved through lineage rather than a balancing journal. Explain the sampling population, cutoff assumptions and personal role; routine month-end processing alone is not enough for this defined cross-functional project.
• Provide sufficient understanding of premium accounting, reinsurance interfaces and reserving inputs to ask precise questions without assuming actuarial expertise. Bring evidence of working with qualified specialists and recording disagreements accurately. Candidates must recognise when a difference reflects model scope or policy interpretation rather than poor ledger control.
• Show data-handling discipline: reproducible transformations, version-controlled logic, minimum necessary customer information and controlled reviewer access. Describe a prior test that failed on a new period and the correction made. Demonstrate reruns from approved extracts, documented transformation changes and a permissions check that preserves insurer-controlled access throughout reconciliation and operator transfer.
• Substantiate delivery against objective acceptance tests, with a redacted milestone record demonstrating reviewer challenge and rework. The role requires eighteen years of relevant finance or specialist career evidence, credible insurance judgement and a method for leaving maintainable rules behind. Implementation revenue or software resale must not bias the diagnosis or recommended remediation options.

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