Global Programs: One Client, Twelve Countries, No Single View

A multinational client buys one program. Underneath it sits a master policy plus a set of local policies issued in each country where the client operates, each in local currency, under local regulation, often on a different system or through a different network partner. The client experiences it as one relationship. The insurer, internally, frequently cannot see it as one thing at all — and that gap shows up exactly when it matters: at renewal, during a large loss, or when the client asks a simple question about their own program.

Why the single view doesn't exist

Global programs are assembled from parts that were never designed to be assembled. Local policies live in local systems, with local product codes, local currencies, and local claims processes. Network partners issue some of them entirely outside your estate. Rolling that into a coherent view of one client's total exposure, premium and loss experience means resolving the client across countries, normalising products and currencies, and consolidating claims data of varying quality and timeliness. Each of those is hard; together they're why the consolidated view is usually a spreadsheet someone rebuilds before every renewal.

Where it breaks down

  • The client isn't resolved globally. Subsidiaries appear as unrelated entities, so nobody can total the relationship.
  • Local product codes don't reconcile. "The same" coverage is described differently in each territory.
  • Currency and timing. Premiums and losses land in different currencies at different times, so comparisons need careful, consistent conversion.
  • Partner-issued policies are opaque. Data from network partners arrives late, summarised, and in their format.

Why it's a data-foundation problem

A global program view is fundamentally an entity-resolution and normalisation problem: resolve the client and its subsidiaries into one hierarchy, map local products to a common structure, apply consistent currency handling, and ingest partner data into the same model. Once that exists, the questions that currently take weeks — total exposure for this client, aggregate loss experience, profitability across the program — become queries. It's the same MDM and ingestion foundation used elsewhere in the business, applied to your largest and most demanding customers.

What good looks like

  1. A resolved client hierarchy that ties subsidiaries in every country to one global relationship.
  2. Local products mapped to a common coverage structure so the program is comparable.
  3. Consistent currency and timing rules so aggregates mean something.
  4. Partner data ingested into the same model rather than reconciled by hand at renewal.

Global programs are high-value, high-visibility business where the client expects you to know your own book better than they do. Building the resolution and integration foundation that makes that possible is exactly the kind of work we do with insurers at IntelliBooks.

Your client sees one program. It's worth being able to see the same thing they do.

Comments

Post a Comment

Popular posts from this blog

Why Your Insurance Data Warehouse Didn't Fix Anything

You built the data warehouse. It took eighteen months and cost more than planned. Policy data, claims data, billing — it's all in there. The project was declared a success and everyone moved on. And yet: underwriting still can't see the whole customer. The AI initiative is still stalled. Someone still asks for a report and waits three weeks. Nobody says it out loud, but the question hangs there — what exactly did we buy? You're not alone, and it isn't because you built it badly. It's because a warehouse solves a problem you didn't have. The problem a warehouse solves Warehouses solve location . Before: your data was in eight systems. After: it's in one place. That's genuinely valuable — you can run a query across policy and claims without begging two teams for extracts. But notice what that fixes: it fixes where the data is . It doesn't touch what the data means , whether it's trustworthy, or whether the records refer to who you think t...
Read more

Embedded Insurance: Why the API Is the Easy Part

Embedded insurance is the idea that coverage should be offered at the moment of need, inside someone else's product — travel insurance at checkout, device protection when you buy the phone, cover for the rental car in the booking flow. It's one of the fastest-growing distribution models in the industry, and every insurer has a strategy slide about it. Most of those strategies underestimate the same thing, and it isn't the partnerships or the product. It's the data plumbing. Everyone assumes the API is the hard part. The API is the easy part. What embedded insurance really demands The promise of embedded is speed and invisibility: a customer buys a flight and, in the same breath, is offered exactly the right travel cover at exactly the right price, and accepts with one tap. No forms, no friction. Deliver that and you've won. But "exactly the right cover at exactly the right price in one tap" makes brutal demands on your back end: You must price i...
Read more

Insurance Knowledge Graphs: The Foundation AI Needs Before It Can Think

Every insurer wants enterprise AI. Few realise they're missing something much more fundamental. Knowledge. Not data. Knowledge. Insurance companies already possess enormous amounts of information. Policy systems contain customer records. Claims platforms hold loss histories. CRM systems track interactions. Document repositories store underwriting reports. Data warehouses consolidate analytics. Yet AI still struggles to answer surprisingly simple questions. Not because the information doesn't exist. Because the relationships between that information remain invisible. Data tells you what exists A customer database tells you who someone is. A policy database tells you what they bought. A claims system tells you what happened. An accounting platform tells you what was paid. Each system is internally consistent. Together they rarely behave like a connected enterprise. Humans mentally assemble those relationships every day. Computers usually canno...
Read more