Preparing to launch bancassurance on Nextera Flow
Konten ini belum tersedia dalam bahasa Anda.
A bancassurance launch has an unusual property: most of the preparation is not technical and not yours alone. Two institutions have to agree a set of commercial and regulatory positions before any of it can be configured, and no amount of implementation effort compensates for an unagreed one.
This page is written for whoever is running the launch on either side.
Before you start
Section titled “Before you start”Decisions the two institutions must agree
Section titled “Decisions the two institutions must agree”- The distribution model. Referral, distribution agreement, strategic alliance, or joint venture. This determines who owns the customer relationship, what bank staff may say, and what each side’s conduct obligations are. Every subsequent decision follows from it.
- Which products, through which channels, to which segments. Not the insurer’s full catalogue — the specific mapped subset, with the bank’s eligibility applied on top of the insurer’s.
- Who may sell. Which bank staff, by licence and training, may sell which products, and who maintains that register on an ongoing basis.
- The full revenue-share structure. Commission split first-year and renewal; profit share and how the underlying loss ratio is measured and by whom; any access or exclusivity fees; marketing contributions; and clawback on lapse and free-look cancellation.
- Customer data and consent. What may be shared, in which direction, under what consent, and who is the controller of what. This is a legal position, not a system setting, and it constrains the integration design.
- The service commitments each side makes to the other — underwriting turnaround, status updates, complaint handling — because those become the SLAs the system is built to meet.
- Free-look and cancellation handling. How a cooling-off cancellation reverses premium, commission and revenue share on both sides.
Data and specifications you must gather
Section titled “Data and specifications you must gather”| Input | Typical owner | Why it is needed |
|---|---|---|
| Insurer product definitions with rating and underwriting rules | Insurer product team | The source side of the mapping |
| Bank channel and segment definitions | Bank distribution | The selling side of the mapping |
| The agreed product mapping | Both, jointly | The layer that makes the two definitions reconcile |
| Bank staff register with licences and training status | Bank HR / compliance | Who may sell what |
| Commission and revenue-share schedules | Both finance functions | The commission engine |
| Bank system interface specifications | Bank IT | Core banking, CRM, channel systems |
| Insurer system interface specifications | Insurer IT | Policy administration, underwriting |
| Regulatory reporting requirements for both institutions | Both compliance functions | What has to come out at the end |
| Premium collection mechanism | Bank operations | Usually direct debit from the bank account |
The row that gets underestimated every time is the agreed product mapping. It is not a data extract from either side; it is a jointly-owned artefact that has to be maintained forever. Decide who owns it before you build it.
People you need available
Section titled “People you need available”From the bank: a bancassurance lead with commercial authority, a channel or branch operations owner, an IT integration owner, compliance, and finance for the revenue share.
From the insurer: a partnership manager, a product owner, an underwriting contact who can answer the synchronous-versus-asynchronous question, IT integration, and finance.
Both sides need someone who can make a decision in the room. Bancassurance launches stall on questions that need two approvals in two organisations, and the fix is representation, not escalation.
What “done” looks like
Section titled “What “done” looks like”Your launch is ready when:
- The distribution model is agreed and documented, and the system’s permitted path matches it — a referral model does not present advice; a distribution model captures suitability.
- Every launch product is mapped, with both sides’ eligibility applied and effective dates on both sides aligned.
- A case can be created in a bank channel, submitted to the insurer, underwritten, and returned with status — and both institutions see the same case in the same state at the same time.
- A policy can be issued and onboarded, with premium collection established.
- A free-look cancellation reverses correctly on both sides — premium, commission and revenue share.
- A commission and revenue-share calculation for a period is agreed by both finance functions from the same transaction record.
- Both institutions’ regulatory reporting is produced from that same data and reconciles.
Steps 5 and 7 are the real tests. Step 5 exercises the reversal path that manual processes always get wrong; step 7 proves the two sides will not drift apart.
Working through it in the product
Section titled “Working through it in the product”Getting access
Section titled “Getting access”See Getting access to Nextera products. Nextera Flow normally runs
at flow.nextera.id.