Bancassurance concepts
Bancassurance is the distribution of insurance through a bank’s channels and customer base. It looks like ordinary distribution and behaves very differently, because two separately regulated institutions with separate systems have to present one journey to one customer.
Nextera Flow exists to be the seam between them. This page is about why that seam is hard.
The four models, and why the model determines everything
Section titled “The four models, and why the model determines everything”| Model | How it works | Who carries what |
|---|---|---|
| Referral / introducer | The bank identifies interest and passes the customer to the insurer, who sells | Lowest bank obligation; lowest bank revenue. Bank staff usually cannot advise |
| Distribution agreement | The bank sells the insurer’s products as an agent | Bank staff sell and must be licensed and trained; bank earns commission |
| Strategic alliance / exclusive | A long-term exclusive tie, often with volume commitments and upfront access fees | Deep systems integration; deep dependency |
| Joint venture / owned insurer | The bank owns or part-owns the manufacturer | Full economics, full regulatory weight |
Two things follow from the model, and they are decided commercially long before any system is configured:
- Who owns the customer relationship, and therefore who may contact them, for what, and with what consent.
- What bank staff are permitted to say. In a referral model, a branch employee who recommends a product has stepped outside it. The system has to make the permitted path the easy path.
In most markets the bank and the insurer are supervised separately — in Indonesia, both under OJK — and each carries its own conduct obligations for the same sale. There is no version of bancassurance where one side can assume the other has it covered.
The product mapping problem
Section titled “The product mapping problem”This is the single most underestimated part of a bancassurance implementation.
The insurer defines a product the way a manufacturer does: cover, sums insured, exclusions, rating factors, underwriting rules. The bank sells it the way a distributor does: to a particular customer segment, through a particular channel, alongside a particular banking product, subject to what its staff are licensed to sell.
Neither definition is wrong, and neither is sufficient. A mapping layer has to hold:
- Which insurer product is sellable through which bank channel.
- Which bank customer segments are eligible, which is usually narrower than the insurer’s own eligibility.
- Which bank staff, by licence and training, may sell it.
- Which banking product it is attached to, if any — a credit-life policy attached to a loan behaves very differently from a standalone savings-linked policy.
- Effective dates on both sides, which rarely align.
When mapping is done in spreadsheets, three predictable failures follow: products remain sellable after the insurer withdrew them, eligibility drifts apart between the two sides, and commission is calculated against a product definition one party no longer recognises.
The journey across the boundary
Section titled “The journey across the boundary”A bancassurance sale crosses an institutional boundary at least twice, and each crossing is a place where cases go missing:
- Identification — the bank recognises a need, often from data the insurer will never see.
- Offer — within the bank’s channel, using the mapped product.
- Application — customer data captured once, on the bank’s side.
- Submission to the insurer — the first crossing.
- Underwriting — the insurer’s decision, which may be instant, referred, or declined.
- Status back to the bank — the second crossing, and the one most often left to email.
- Issue and onboarding — the policy exists, the customer is told, and the premium collection begins, frequently by direct debit from the bank account.
The property that matters more than any other: both sides should see the same case in the same state at the same time. Almost every bancassurance service failure — a customer told “it’s with the insurer” for two weeks, a branch chasing an already-issued policy — traces back to state living in two places.
Free-look and cancellation deserve a specific note. Most markets require a cooling-off period during which the customer may cancel for a full refund. A cancellation in that window reverses premium, commission and revenue share across both institutions — so it has to flow back through the same path the sale came in on, not be handled manually.
Money: commission and revenue share
Section titled “Money: commission and revenue share”Bancassurance economics are usually a revenue share rather than a simple commission, and the arrangement typically layers several components:
- Commission on premium, often split first-year and renewal.
- Profit share — a share of underwriting profit on the distributed portfolio, calculable only after a measurement period and a loss-ratio calculation.
- Access or exclusivity fees — paid up front in strategic alliances, then amortised.
- Marketing and campaign contributions — funded by the insurer, spent by the bank.
- Clawback on lapse and free-look cancellation, reaching back through whichever of the above already paid out.
Two structural difficulties make this harder than agency commission:
It is calculated on data neither party owns completely. Premium collection sits with the bank; policy status and claims sit with the insurer. A profit share needs both.
Both sides recognise the revenue in their own books. If the two calculations disagree, the dispute is between two finance functions and two auditors. This is exactly why “zero manual commission files” is the outcome Nextera puts against Flow: the fix is not a better spreadsheet, it is both sides computing from the same transaction record.
Reporting, twice over
Section titled “Reporting, twice over”Bank and insurer each report to their own supervisor, on their own cycles, in their own formats — but about the same policies. Reporting built separately on each side will disagree, and reconciling two regulatory submissions after the fact is far more expensive than generating both from one dataset.
Practical implication for implementation: agree the shared transaction record first, then derive both sides’ reporting from it. Do not agree the reports first.
How these concepts map to Nextera Flow
Section titled “How these concepts map to Nextera Flow”| Concept on this page | Nextera Flow module |
|---|---|
| Putting insurance inside the bank’s existing channels and systems | Bank integration |
| Products, submission and status kept in sync with partner insurers | Insurer integration |
| Mapping insurer products to how the bank sells them, with rules and eligibility | Product management |
| Offer to onboarded policy across the bank–insurer boundary | Sales & onboarding |
| Commission, revenue share and clawback between the two parties | Commission engine |
| Reporting both institutions need from the same data | Regulatory reporting |