Insurance

ENBP Testing Under ICOBS 6B: How to Prove UK Renewal Pricing Compliance

Rishabh Kumar

Published On

ENBP Testing

Summarise this article with AI:

ChatGPT

Perplexity

Claude

Grok

Google AI

Summarise this article with AI:

ChatGPT

Perplexity

Claude

Grok

Google AI

Summarise this article with AI:

ChatGPT

Perplexity

Claude

Grok

Google AI

Table of contents

Lorem ipsum

Lorem ipsum

Lorem ipsum

Lorem ipsum

Lorem ipsum

Under ICOBS 6B, a UK home or motor insurance renewal price must not be higher than the equivalent new business price (ENBP), assessed at the point the renewal notice is prepared. Testing ENBP means proving, for every channel, tenure, incentive and product combination that matters, that the price a renewing customer is offered never exceeds what an equivalent new customer would pay through the same channel.

The rule sounds simple. Implementing it is not, and the public evidence shows what an implementation error can cost: in 2023 one large UK motor and home insurer agreed to pay redress estimated at around £30 million after an error in its ENBP calculation. This guide turns the detail of the rules into a test design that a pricing team, a QA team and a compliance team can all work from.


What Does ICOBS 6B Actually Require?

The core rule is that a renewal price must not exceed the ENBP at the point the renewal notice is prepared. Around it sit detailed rules on how to determine the ENBP, which incentives and discounts it must include, how closed books and add-on products are priced, and how firms must avoid systematically disadvantaging customers by tenure.

The provisions that shape testing most:

Rule area

What the rule says

What it means for testing

Core rule (6B.2.1)

Renewal price no higher than ENBP, at the point the renewal notice is prepared

Compare the renewal price with a new business quote for the same risk at that moment

Combined home and motor (6B.2.2)

The home element, the motor element and the bundle must each be no higher than their ENBP

Test each element and the bundle separately

Channel (6B.2.5 to 6B.2.7)

Assume the customer came through the same channel as originally; if that channel is closed or unknown, use the most common new business channel

Tests need channel history; closed and unknown channels need their own cases

Separate channels (6B.2.6)

Each intermediary chain, price comparison website and affinity scheme is a separate channel

Each price comparison site and broker chain is its own test case, not one "aggregator" bucket

Incentives (6B.2.9 to 6B.2.14)

Cash and cash-equivalent incentives a new customer would get must be included; non-cash incentives are excluded

Percentage and monetary discounts, free months, free add-ons, cashback, vouchers and loyalty points all feed the ENBP

Negotiated discounts (6B.2.16)

Individually negotiated new business discounts must be taken into account

Test the method used to reflect them

Risk information during the term (6B.2.19)

Risk information acquired during the term, such as telematics data or fraud indicators, must be included

Mid-term changes and new data must flow into the ENBP

Closed books (6B.2.25 to 6B.2.31)

Use a close matched product with permitted adjustments, priced as if bought through its most common channel

Each closed book needs its mapping and adjustments tested

Intermediaries (6B.2.34, 6B.2.35)

An intermediary's portion of the price, and any commission forgone or incentives given to new customers, must be reflected

Broker fees and commissions are part of the test

Additional products (6B.2.36, 6B.2.37)

Add-ons at renewal no higher than for a new customer; for premium finance, the APR or cost

Legal expenses, breakdown, key cover and premium finance need their own checks



Tenure and fees (6B.2.39, 6B.2.40)

No systematic discrimination by tenure; fees should not be systematically higher at renewal

Test across tenures and compare renewal and new business fees


Firms must also keep written evidence of how they assess and control their pricing models against these rules, and have policies to stay compliant after material changes to pricing practices, models or products (6B.2.51 to 6B.2.59).


Why Do ENBP Implementations Fail?

Because the ENBP is not one calculation. It is a new business price, recalculated for an existing customer, through the right channel, with the right incentives, at the right moment, compared with a renewal price produced by a different process.

Every one of those inputs can drift, and most drifts produce no error.

The defects that recur:

  • Channel misidentified: The customer's original channel is lost in a migration, or several price comparison sites are treated as one channel.

  • Incentives missed: A new cashback offer, loyalty points scheme or free month is added for new customers but not to the ENBP calculation.

  • Timing: New business rates change between the renewal notice being prepared and the ENBP being assessed, or the ENBP is calculated against the wrong date.

  • Risk data not carried through. Telematics scores, claims or mid-term changes update the policy but not the ENBP inputs.

  • Bundle elements. The bundle passes but one element breaches its own ENBP.

  • Add-ons and fees. An add-on or admin fee is priced higher for renewing customers than for new ones.

  • Closed book mapping. A closed book points at a close matched product that has since changed or been withdrawn.

  • Rounding and tax. Insurance Premium Tax or rounding applied in a different order in the renewal and new business processes.


How Do You Design an ENBP Test Matrix?

Build a matrix of renewing customers that varies the inputs the rules care about, then for each one compare the renewal price with a new business quote for the equivalent risk, through the same channel, at the moment the renewal notice is prepared. The test passes only if the renewal price is no higher.

The dimensions to vary:

  1. Product: home, motor, and combined home and motor, including each element of a bundle.

  2. Channel: direct web, direct phone, each price comparison website separately, each broker chain, each affinity scheme, a closed channel and an unknown channel.

  3. Tenure: first renewal, and several longer tenures, to expose systematic tenure effects.

  4. Incentives: each cash or cash-equivalent incentive currently offered to new customers in that channel, and a non-cash incentive to confirm it is excluded.

  5. Risk changes during the term: a mid-term adjustment, a claim, new telematics data.

  6. Additional products: each add-on available at renewal, and premium finance where offered.

  7. Fees: renewal and new business fees compared.

  8. Closed books: each closed book, priced against its close matched product with permitted adjustments.

You do not need every combination. Use risk-weighted and pairwise selection to cover each value of each dimension and the combinations most likely to interact, such as incentives by channel and tenure by product.


How Do You Test the Timing of the ENBP Check?

Run the comparison at the point the renewal notice is prepared, using the rates and incentives live at that moment. That means creating renewing policies in a known state, triggering renewal invitation generation, and quoting the equivalent new business risk in the same channel immediately afterwards, against the same rating configuration.

Two timing cases deserve their own tests.

First, a new business rate or incentive change scheduled between invitation and inception, to confirm which point the firm's approach uses and that it matches its documented policy. Second, renewals generated in a batch, to confirm every invitation in the batch was checked against the configuration live when it was prepared.


When Should ENBP Tests Run?

On every change that could move either price: rating model and table deployments, new or changed incentives, channel and partner changes, fee changes, add-on pricing changes, closed book reassessments, platform releases and data migrations. ICOBS 6B expects firms to stay compliant after material changes to pricing practices, models or products, and regression is how that expectation is met day to day.


How Does Testing Evidence Support Compliance and Attestation?

ICOBS 6B asks firms to keep written evidence of how they assess and control their pricing, and a senior manager attests to compliance each year. Testing evidence does not replace that governance, but it strengthens it: it shows, change by change, that the controls over pricing models and configuration actually worked.

Useful evidence for pricing committees and attesting senior managers includes the matrix tested for each pricing change, the results, any breaches found and fixed before release, and the approvals of the requirements behind the tests.


How Does Virtuoso QA Touchstone Test ENBP?

Touchstone turns the ICOBS 6B rules, the firm's own pricing policy and its rating guide into approved requirements, then runs the ENBP matrix as automated journeys on every pricing change.

Each requirement cites the rule or policy paragraph it implements, so the evidence speaks the language compliance teams use.

  • The Analyst reads ICOBS 6B, the firm's documented pricing approach, its incentive terms and its rating guide, and proposes requirements for each rule, channel and product, each citing its source.

  • The Architect builds journeys that create renewing policies with a given channel history and tenure through API steps, trigger renewal invitations, quote the equivalent new business risk in the same channel, and compare the two prices.

  • The Autopilot runs the matrix on a deterministic engine in your CI pipeline, so the same matrix against the same configuration always gives the same answer.

  • Data checks compare renewal and new business prices for each element, add-on and fee, and flag any case where the renewal price is higher.

  • Change tracing links a new incentive, rating table or channel to every affected requirement and test, with updates proposed for the pricing owner to approve.

  • Evidence for each pricing change shows the matrix, the results, the approvals and any breach found before release.

When a pricing committee or attesting senior manager asks how a change was controlled, Virtuoso QA’s release evidence already holds the requirement, result, approver and build behind every ENBP test.

Renewal pricing is one part of a wider lifecycle, and Virtuoso QA’s insurance testing carries the same approved expectations through quote, renewal, billing and claims.


Illustrative Scenario: A Loyalty Points Offer on One Comparison Site

This scenario is illustrative and doesn’t describe a specific firm.

A UK motor insurer launches a retail loyalty points offer for new customers buying through one price comparison website. The marketing change is configured in the quote journey for that channel. Nobody thinks of it as a pricing change.

Because loyalty points are a cash-equivalent incentive, they must be included in the ENBP for renewing customers who originally came through that site. The incentive terms are loaded into Touchstone as a source, and The Analyst proposes a requirement under the incentive rules. The ENBP matrix for that channel fails in pre-production, because the calculation ignores the points. The pricing team corrects the calculation before launch, and the evidence shows the incentive, the rule it engages, the failed and passing runs, and the approval.

Frequently Asked Questions

What is the equivalent new business price?

What is ENBP testing?

How do you test ENBP compliance?

Are price comparison websites one channel or several?

Do incentives count towards the ENBP?

See what your next release looks like with Virtuoso

Book a walkthrough on your applications and your workflows. Bring a requirement, a user journey, or a brittle Selenium script, and watch the loop run on something you recognise.

See what your next release looks like with Virtuoso

Book a walkthrough on your applications and your workflows. Bring a requirement, a user journey, or a brittle Selenium script, and watch the loop run on something you recognise.

See what your next release looks like with Virtuoso

Book a walkthrough on your applications and your workflows. Bring a requirement, a user journey, or a brittle Selenium script, and watch the loop run on something you recognise.

Virtuoso QA is establishing the standard of proof for software releases. Its governed QA loop turns business requirements into tests for any browser-based application: AI proposes, a deterministic engine executes, a person approves what matters, and every decision leaves evidence.

Trust Center

AICPA

SOC

WAVE STRONG PERFORMER

@ Copyright 2026 SpotQA, Creators of Virtuoso QA

Virtuoso QA is establishing the standard of proof for software releases. Its governed QA loop turns business requirements into tests for any browser-based application: AI proposes, a deterministic engine executes, a person approves what matters, and every decision leaves evidence.

Trust Center

AICPA

SOC

WAVE STRONG PERFORMER

@ Copyright 2026 SpotQA, Creators of Virtuoso QA

Virtuoso QA is establishing the standard of proof for software releases. Its governed QA loop turns business requirements into tests for any browser-based application: AI proposes, a deterministic engine executes, a person approves what matters, and every decision leaves evidence.

Trust Center

AICPA

SOC

WAVE STRONG PERFORMER

@ Copyright 2026 SpotQA, Creators of Virtuoso QA