Confidential mandate
Premium and Commission Accounting Lineage Lead
Planned Hiring / New
Premium and Commission Accounting Lineage Lead mandate in Bengaluru, India · Insurance Services
A three-month project will build premium and commission source-to-ledger lineage and an exception operating pack, enabling finance users to reproduce balances and route defects without assuming statutory assurance or product accounting-policy authority.
The mandate
The narrow problem is that premium and commission balances cannot consistently be traced from operational source records to ledger and close schedules. The consultant will build lineage for agreed flows and design an exception pack users can maintain. This is not an engagement to certify insurance compliance or correct every historic transaction.
Deliverables are a source-to-ledger lineage map, reconciliation rules and a live-tested exception operating pack. Each rule must explain how a source item is transformed, matched or left unresolved. Unmatched records must remain visible with a reason and owner instead of disappearing through manual netting that produces an apparently clean total.
The project starts on 19 October 2026 and ends on 18 January 2027, requiring three days weekly. Milestone one on 16 November delivers source definitions and a sampled lineage baseline. Milestone two on 14 December provides the reconciliation rules and pilot pack. Milestone three on 18 January delivers operating test results, revised instructions and analyst transfer.
Acceptance is by the controller and nominated source-process owner. They must trace selected premium and commission items through the map, reproduce reconciliation outputs and classify a fresh exception without consultant assistance. The test includes reversals, late postings and incomplete records; passing only clean matching transactions will not establish the pack's usefulness.
The sponsor provides authorised extracts, ledger access and an internal analyst with scheduled source-owner support. Bengaluru is the primary location, with remote US-facing process sessions agreed in advance. Accounting policy changes, external assurance and mass transaction remediation are excluded. New flow families or substantially different source mechanics require an approved scope change rather than uncontrolled expansion of the project fee.
What you will own
- Map selected premium and commission flows from source event to ledger, recording transformations and ownership changes that can explain a financial discrepancy.
- Reconcile the sampled baseline with explicit matching rules, separating reversals, late postings and missing records rather than netting unrelated items to achieve a total.
- Build an exception taxonomy that directs each defect to an accountable process owner, distinguishing data correction from accounting judgement requiring controller approval.
- Specify the evidence retained for every resolved exception, ensuring users can explain both the original mismatch and the basis for closing it.
- Pilot the pack through a live operating period, testing whether fresh records can be classified without rewriting the rule for each new case.
- Analyse pilot failures and revise the matching logic, preserving uncertainty where the source does not support a defensible reconciliation conclusion.
- Transfer the lineage map and refresh instructions through observed analyst execution, documenting residual source limitations and maintenance ownership before final acceptance.
Candidate qualifications
- Demonstrate hands-on reconciliation or accounting-data lineage work involving insurance services or analogous transaction flows. Explain a source-to-ledger mismatch, the transformation that caused it and how the evidence was preserved for later review.
- Show technical understanding of reversals, cut-off and commission or service accrual support. Candidates should describe when a discrepancy was a data defect and when it required an accounting judgement beyond the analyst's authority.
- Provide a practical exception pack that remained usable after transfer. Explain the taxonomy, retained evidence and fresh-case test used to prove an internal analyst could maintain it without the original consultant.
- Evidence consulting scope and acceptance discipline at specialist level. Show how incomplete records were reported honestly, how additional flows were handled through change control and how acceptance differed from responsibility for every downstream remediation.
- Be able to work with authorised sensitive records using minimised fields, versioned rules and controlled access. Professional accounting capability matters, but the assignment does not confer statutory-audit, legal or CFO authority; candidates must demonstrate careful escalation rather than inflate their role in the financial conclusion. Explain how the pack treats a fresh reversal whose original source identifier is missing.
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 14 October 2026. Mandate reference PCT-CON-2026-IND-08.
More seats like this one
This mandate is confidential. The client is named only under a mutual NDA, and your own record is never listed, sold or shown to a company under your name until you release it for this specific mandate.