Preparing to launch bancassurance on Nextera Flow

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

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 has 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

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

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

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 its status — from Draft through to Issued — 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

Nextera Flow is a web application. You sign in through the Sign In page with a username and password from your administrator, and land on the Dashboard for your account’s role. The top of the sidebar shows your name, your role and the organisation you are currently in — the three things to check first whenever someone asks why their menu differs from a colleague’s.

The menus genuinely do differ by user type. Flow is multi-tenant with role-based access control, and each type — Bank, Leasing, Insurance, Broker, Agent, Car Dealer, Property Developer, Customer, and Nextera as super admin — has navigation of its own.

1. Set up the organisation and its permissions

All of it sits under User Management:

Screen	What you set there
Organization	Your institution’s own details on the platform
Users	User accounts, role assignment, and account status
Roles & Permissions	Permissions per module — view, create, edit, delete, approve, export
Branches	Branch offices, which double as a user’s data scope
Workflow	Approval chains, per process type

Workflow is where your service commitments become real. A workflow is built for one process type — Policy, Claim, Endorsement, Cancellation or Renewal — and holds ordered steps, each with an approver role, a time limit in hours, and markers for whether the step is mandatory, may reject, and may be escalated. The workflow itself carries a status of Active, Inactive or Draft. Each institution’s structure may differ: one bank uses a preparer, reviewer then underwriter chain, another leaves the whole thing to one person. Both are valid, and both are configured on the same screen.

2. Register the counterparty

The bank side opens Partners → Insurance Partners to register its insurance partners, each with a status of Active, Inactive or Pending. The insurer side sees the mirror image under Distribution Partners, which separates All Partners from Bank Partners. Nextera as super admin sees both through Platform → Organizations and Platform → Partner Network.

This registration is what makes a partnership workable, so do it before products or users.

3. Set up the products

The insurer maintains its products in Products → Product Catalog, with Rate Tables for pricing and Underwriting Guidelines for selection rules. Each product carries a status of Draft, Active or Inactive, and only Active products can be sold — that is where both sides’ effective dates finally meet.

Flow pulls the product catalogue, premium calculation, quotation and policy issuance from the core insurance platform over an API, so product definitions never have to be retyped on the bank side.

4. Work a case

Day-to-day work runs through two paired records, both sitting under a single Case.

New Business → Loan Application holds the credit application. The + New button opens a four-step wizard — Customer Info, Object Details, Product Selection and Summary. After the first step Flow runs a party match: if the customer already exists in the database, you use the existing record instead of creating a duplicate. This is the point where “customer data captured once” is actually enforced.

New Business → Insurance Application holds the insurance, and attaches to that Loan Application. Its wizard is four steps too — Insurance Type (pick the loan number and the type of insurance), Insured Info (debtor and insured details, down to the name and contact of the bank officer handling it), Health Questionnaire, and Summary.

For applications that start from paperwork, there is a document-led path at New Business → Application: upload the customer’s documents — KTP, SIM, STNK, BPKB, family card — and Flow reads them by OCR, shows you what it read for checking and correction, then moves straight on to configuring the insurance package.

After Submit, both records move along the same sequence: Draft → Submitted → Underwriting → Approved → Issued, with Rejected and Cancelled as the ways out.

Different sides drive different transitions. The bank side moves Draft to Submitted. After that the application enters the insurer’s Underwriting Queue — a queue in its own right, with a priority of standard, referred, high-value or urgent, and a decision of approved, declined, referred or counter-offer. Because underwriting is asynchronous, the branch does not wait for an answer in front of the customer; it waits for the status to change. The insurer closes it out through New Business → Issuance, which produces the policy document, schedule, certificate and receipt, and moves the status to Issued.

5. Collect the premium

New Business → Billing & Collection bills the premium and records what comes in. The available methods include bank transfer, auto debit, virtual account, credit card and cash, and a bill runs through pending, partial, paid, overdue or failed. For insurance attached to a loan, deduction from the credit facility is available as a payment method too.

6. Service the policy through its life

Policy Admin holds the rest: Policies, Claims, Endorsement, Cancellation and Renewal. The last three are open to the bank, leasing and insurer sides alike — and each has a workflow type of its own, so you set their approval chains yourself.

7. Bring the customer in where needed

The customer can be sent a time-limited link to complete their own application: checking the loan and object details, choosing an insurance package, uploading documents, then agreeing the declaration and its consent. Once the policy is issued, the customer has a portal of their own holding My Policies, My Applications, Claims, Payments, Documents and Support.

8. Calculate commission

Commissions → Statement shows one row per policy — policy number, customer, product type, premium, commission rate and commission amount — with a status of Pending, then Approved, then Paid. Commissions → History keeps the settlement record, the broker and insurer roles get an extra Payout screen, and the summary sits in Reports → Commission Report.

9. Pull the reporting

Reports offers Production Report, Sales Report, Claims Report, Commission Report and Custom Reports. Custom Reports are built yourself by category — sales, claims, customers, financial, operations — and each report can be active, scheduled, draft or archived. Access to Reports is governed by rights that separate viewing, creating and exporting.

Integrating with the bank’s origination systems

Besides the screens above, Flow offers an API path so the bank’s own origination systems can call it, which puts bancassurance inside the credit process already running rather than in a separate application. The flow has six stages, in the same order as the screens:

Start the credit application — loan type, limit, tenor, debtor details and collateral. Flow answers with a loan reference and the list of eligible insurance types for that loan.
Fetch the products available for those types, with their insurer, sum assured limits, and the plans on offer.
Calculate the premium, broken down into base premium, loading, discount, tax, stamp duty, admin fee and the commission component.
Create the quote, with its policy holder, insured, beneficiary and validity period.
Submit the proposal with the underwriting declarations, the payment information, and the customer’s consent. The outcome is approved, declined, referred or counter-offer.
Issue the policy once payment is confirmed, then receive the policy number, the period of cover and the documents.

Other third-party connections — SMS gateways, email services, payment gateways, document storage — are registered under Settings → Integrations.

Roles and visibility

What a user can see is decided by three layers at once: their organisation type, their role within that organisation, and their branch. That is why the same job title at two institutions can end up with different permissions, and it is deliberate.

The bank side does not get the insurer’s underwriting, claims investigation, claims assessment or reinsurance screens. The insurer side does not get the bank’s Insurance Partners screen. What they share is the case — its number, its contents and its status.

Getting access

Nextera Flow normally runs at flow.nextera.id. Accounts are provided by the product administrator in your organisation. The address above is the production address; if your organisation uses a dedicated environment, use the address in your onboarding pack.