โ† Foundation Course /Module 02 - Inside the Cat Model /Lesson 2.4
MODULE 02 ยท INSIDE THE CAT MODEL: THE FOUR COMPONENTS

The Financial Module

๐Ÿ“– ~25 min ยท Lesson 7 of 15 ยท 3 micro-checks + quiz ยท Foundation Level ยท Free
The Same Earthquake, Three Different Losses

A magnitude 6.8 earthquake strikes the outskirts of Istanbul. One of Meridian's locations, a commercial office tower worth USD 24M, sustains ground-up structural damage the vulnerability module estimates at 35% of TIV: USD 8.4M of physical destruction.

Three insurers each have a share of this risk. The first has written a policy with a USD 500K deductible and a USD 10M limit, it pays USD 7.9M. The second has written the same risk with a USD 2M deductible and a USD 5M limit, it pays USD 5M. The third has written a policy covering only the structure, not the contents, with a 20% co-insurance clause requiring Meridian to bear a fifth of any loss, it pays USD 4.9M.

Three insurers. One earthquake. One building. One USD 8.4M ground-up loss. Three different insured losses.

The vulnerability module produces the ground-up loss. The financial module is what transforms that physical damage figure into the amount each insurer actually owes. What is the financial module doing, and why does it matter that you understand it before you ever look at a cat model output table?

What the Financial Module Does

The financial module is the last step in the cat model's calculation chain. It takes the ground-up loss produced by the vulnerability module, the total physical damage before any insurance terms are applied, and transforms it into the loss the insurance policy actually covers. That transformation is governed by the policy conditions: the specific contractual terms that define what the insurer pays, under what circumstances, and up to what limit.

This step is what makes cat modelling useful for insurers rather than just for engineers. An engineering model can estimate how much a building is damaged by a given force. Only a cat model with a properly configured financial module can translate that damage estimate into the number the insurer cares about: how much of that damage falls within the insurance contract and therefore becomes the insurer's liability.

The financial module does not change the physical reality of the loss. If the building sustains USD 8.4M of damage, USD 8.4M of damage occurred regardless of what any insurance policy says. What changes is the allocation of that loss between the insured (who bears the deductible and anything above the limit) and the insurer (who bears the covered portion between the deductible and the limit). The financial module calculates each party's share.

Why This Matters for Every Number You Produce

Every loss figure a cat model outputs exists at a specific point in this transformation. Ground-up loss is the raw physical damage. Gross loss is after the primary policy conditions are applied. Net loss is after reinsurance recoveries are also applied. When an underwriter asks "what's the model saying?" they need to know which of these three they are looking at, the same event produces three materially different numbers, and confusing them leads to mispriced risk or miscalculated reinsurance recovery.

Policy Conditions - What the Financial Module Reads

Policy conditions are the contractual terms that define the coverage. They tell the financial module exactly how to translate physical damage into insured loss. The four most important conditions for cat modelling purposes are deductibles, limits, coverage scope, and participation.

Condition 01

Deductible

The amount the insured must bear before the insurance pays anything. Acts as a floor below which the insurer has no liability. A higher deductible reduces the insurer's expected loss, the insured absorbs all losses below it.

USD 500K deductible on USD 8.4M loss โ†’ insurer pays USD 7.9M
Condition 02

Policy Limit

The maximum the insurer will pay under any single loss or in any policy period. Acts as a ceiling above which the insured bears the excess themselves. The policy limit caps the insurer's liability regardless of how large the loss grows.

USD 5M limit on USD 8.4M loss โ†’ insurer pays USD 5M, insured absorbs USD 3.4M excess
Condition 03

Coverage Scope

What the policy actually covers - which perils, which types of loss (structure vs contents vs business interruption), and which geographic locations. A policy covering wind but not flood pays nothing for a flood loss, regardless of its limit. Coverage scope is the first filter the financial module applies.

Structure-only policy on USD 8.4M mixed loss โ†’ contents portion excluded from insured loss
Condition 04

Co-insurance / Participation

Some policies require the insured to bear a defined percentage of every loss, typically because the insured is self-insuring part of their own risk. A 20% co-insurance clause means the insurer pays 80% of the covered loss above the deductible, regardless of how large it grows.

20% co-insurance on USD 8.4M loss โ†’ insured bears USD 1.68M, insurer pays USD 6.72M (less deductible)

The financial module applies these conditions in sequence for every event in the stochastic catalogue. For each of the tens of thousands of simulated events, it takes the ground-up loss the vulnerability module produced, subtracts the deductible, caps at the limit, applies coverage scope filters, and calculates the insured's participation share. The result, applied across every event in the catalogue, produces the gross loss distribution from which the EP curve and AAL are derived.

Micro-Check ยท Before You Continue

The Meridian Tokyo office tower has a cat model ground-up loss of USD 14.2M for a 1-in-100 year earthquake event. The policy has a USD 1M deductible, a USD 10M limit, and no co-insurance. What is the insured loss, and what happens to the remaining USD 4.2M of ground-up loss?

The insured loss is USD 10M, the policy limit, not USD 13.2M. The financial module applies the deductible first (USD 14.2M โˆ’ USD 1M = USD 13.2M eligible), then caps at the policy limit (min of USD 13.2M and USD 10M = USD 10M). The insurer pays USD 10M. The remaining USD 4.2M above the limit is borne by Meridian, it is an uninsured loss unless Meridian has additional coverage elsewhere in its programme. This is the critical insight: for a large loss event, the insurer's liability is not the ground-up loss. It is the covered portion between the deductible and the limit. Understanding this distinction is what allows a cat modelling analyst to explain to an underwriter why the model shows USD 14.2M of physical damage but only USD 10M of insurer exposure.

Ground-Up, Gross, and Net Loss - The Three Numbers

Cat model output exists at three distinct levels of the loss calculation chain. Each level strips away another layer of financial transformation to show the loss from a different perspective. Knowing which level you are looking at is not optional, the same event produces three meaningfully different numbers and conflating them is one of the most consequential errors a practitioner can make.

The Three Loss Levels - Meridian Istanbul Tower, 1-in-100 Year Earthquake

Ground-Up Loss
USD 8.4M, total physical damage
Before any policy
Gross Loss
USD 6.1M, after deductible & limit
Primary policy applied
Net Loss
USD 3.7M, after reinsurance recovery
Cat XL recovery deducted
Ground-Up USD 8.4M
Total physical damage to the building. No insurance terms applied. What the vulnerability module produces. Used to understand the full economic scale of the event.
Gross Loss USD 6.1M
What the primary insurer owes after applying the policy, deductible, limit, coverage scope, co-insurance. This is Halcyon's liability before its own reinsurance protections are applied.
Net Loss USD 3.7M
What Halcyon retains after recovering from its Cat XL reinsurance programme. The net loss is what the syndicate's capital must actually absorb. This is the number that drives solvency capital requirements.

The distinction matters differently for different stakeholders. An underwriter pricing a single risk thinks primarily in gross loss, what is Halcyon's liability on this policy? A reinsurance actuary structuring the Cat XL programme thinks in the difference between gross and net, what recovery does Halcyon expect from its reinsurers in a major event? The capital model and CRO think in net loss, what does Halcyon actually need to hold capital against after all reinsurance recoveries? The financial module is what makes all three calculations possible from the same underlying ground-up loss.

Micro-Check ยท Before You Continue

Halcyon's active underwriter looks at a cat model summary table and says: "The 1-in-100 year loss for the Meridian account is USD 38M, that's what we'd expect to pay in a bad year." You know the USD 38M figure is the gross loss. Why is his statement imprecise, and in which direction does it err?

His statement overstates Halcyon's actual retained loss in a bad year, because gross loss is before reinsurance recoveries. If Halcyon's Cat XL programme attaches at, say, USD 15M and provides USD 30M of cover, then a USD 38M gross loss event would generate approximately USD 23M of reinsurance recovery, leaving Halcyon's net retained loss at around USD 15M, not USD 38M. The gross loss is what Halcyon owes to Meridian under the policy. The net loss is what Halcyon actually pays after its own reinsurance responds. An underwriter who manages accumulation using gross loss figures is holding a more conservative view of retained exposure than the net position warrants, which is not necessarily wrong as a risk management posture, but it is imprecise as a description of actual capital exposure. The distinction matters most when Halcyon is deciding whether its reinsurance programme is adequate, that decision must be made on net loss, not gross.

Why Financial Module Configuration Drives Output Reliability

The financial module can only apply policy conditions it has been told about. If the exposure file does not include the deductible amount, the module cannot apply a deductible, it defaults to zero, treating every dollar of ground-up loss as insured. If the limit is missing, the module cannot cap the loss. If coverage scope is not specified, it applies the broadest available coverage. Every missing policy condition biases the gross loss estimate upward.

This creates a systematic relationship between exposure data quality and loss output. The three preceding lessons established that exposure data quality affects the hazard assignment (geocoding), the damage ratio (COPE), and the financial multiplier (TIV). The financial module adds a fourth dimension: the quality of the policy condition inputs determines how accurately the ground-up loss is converted to insured loss. A model run with perfectly geocoded locations, confirmed COPE, and accurate TIVs will still produce unreliable gross loss estimates if the policy structure has not been configured correctly.

The Complete Data Picture

By the end of Module 02, the pattern should be clear. The cat model chain, hazard โ†’ vulnerability โ†’ financial, has an exposure data input at every stage. Geocoding quality determines hazard. COPE quality determines vulnerability. TIV and policy conditions determine the financial output. A model run is only as reliable as its weakest data input, and that weakest input can sit at any of the three stages. Checking data quality means checking all three, not just the location coordinates.

Micro-Check ยท Before You Continue

When Ardent Re submits the Meridian SOV to Halcyon, the coverage terms, deductibles, limits, coverage scope, are specified in the policy slip, not in the SOV itself. The cat modelling analyst has the SOV but needs to configure the financial module separately using the slip terms. Why does this two-document structure create a data quality risk?

Because the financial module configuration and the exposure data must be kept consistent with each other, and they come from separate sources that can fall out of sync. If the slip is amended mid-negotiation (the deductible is raised, a sublimit is added for a specific peril, a location is endorsed out of coverage) and the cat model is not reconfigured to match the updated slip terms, the gross loss estimate no longer reflects what the insurer actually owes. The slip defines the legal liability; the financial module must mirror it exactly. In practice, policy conditions are one of the most frequently misconfigured elements in a cat model run, particularly for complex international programmes where different locations may have different deductibles, perils covered by different sublimits, or currency denomination mismatches between the SOV and the slip.

Common Misconceptions

01
"The financial module only matters for large losses"

Deductibles affect the insured loss at every event size, not just large ones. A USD 500K deductible eliminates the insurer's liability for any ground-up loss below USD 500K, which may be a significant fraction of all events in a high-frequency, moderate-severity peril like severe convective storm. The financial module affects the AAL (expected annual loss) materially because it shapes the entire loss distribution, not just the tail.

02
"Gross loss and net loss are just different names for the same thing"

They are fundamentally different quantities. Gross loss is what the primary insurer owes the policyholder. Net loss is what the primary insurer retains after its own reinsurance pays. For a well-reinsured syndicate, net loss in a major event could be a fraction of gross loss. Presenting gross loss as the retained exposure overstates the capital requirement; presenting net loss to the policyholder understates their coverage.

03
"A policy with a high limit always produces a higher insured loss"

Only if the ground-up loss exceeds the deductible and is large enough to benefit from the higher limit. For small events where ground-up loss is below the deductible, both a USD 5M and a USD 50M limit produce zero insured loss. The financial module produces the same outcome for both policies at low severity levels. The limit only matters when the loss is large enough to approach or exceed it.

04
"The financial module is just arithmetic, it cannot introduce uncertainty"

The financial module applies deterministic arithmetic to the ground-up loss. But if the policy conditions fed into it are wrong or incomplete, it introduces systematic bias into every output it produces. A misconfigured deductible does not introduce statistical uncertainty, it introduces a directional error that shifts the entire gross loss distribution. This is worse than statistical uncertainty because it is consistent and undetectable without knowing the correct policy terms.

Key Terms

Financial Module

The fourth cat model component. Takes the ground-up loss from the vulnerability module and applies policy conditions to produce the insured loss. Operates on every event in the stochastic catalogue to produce the gross loss distribution.

Ground-Up Loss

Total physical damage to the insured property before any policy terms are applied. The output of the vulnerability module and the input to the financial module. Represents the full economic scale of the damage regardless of insurance structure.

Gross Loss

The loss the primary insurer owes the policyholder after applying primary policy conditions, deductible, limit, coverage scope, and co-insurance. Before the insurer's own reinsurance protections are applied.

Net Loss

The loss the primary insurer retains after all reinsurance recoveries, Cat XL and other protections, have been applied to the gross loss. The net loss is what the insurer's capital must absorb. The relevant figure for solvency capital calculations.

Deductible

The amount the insured bears before the insurance policy pays. Acts as a floor on the insurer's liability, every dollar of ground-up loss below the deductible falls entirely on the insured. Reduces the insurer's expected loss across the full event distribution.

Policy Limit

The maximum amount the insurer will pay under a policy. Acts as a ceiling on the insurer's liability, losses above the limit fall on the insured unless additional coverage exists. The insurer's maximum single-event exposure at a location is the limit, not the TIV.

Coverage Scope

The contractual definition of what the policy covers, which perils, which loss types, which locations. The first filter the financial module applies. A flood loss on a wind-only policy produces zero insured loss regardless of the ground-up damage.

Policy Conditions

The full set of contractual terms that govern the financial module's transformation of ground-up loss into insured loss, deductible, limit, coverage scope, co-insurance, and any special conditions or sublimits. Configured from the policy slip, not the SOV.

Knowledge Check - Lesson 2.4

Five questions ยท 4 of 5 correct (80%) to pass

1. A hurricane produces a ground-up loss of USD 6.8M at Meridian's Miami office (TIV USD 18M). The policy has a USD 750K deductible, a USD 8M limit, and no co-insurance. What is the gross loss, and what portion of the ground-up loss does the insured bear?

AGross loss: USD 6.8M. The insured bears nothing, the policy limit of USD 8M is higher than the ground-up loss, so the full damage is covered after the deductible is applied.
BGross loss: USD 6.05M (USD 6.8M โˆ’ USD 750K deductible = USD 6.05M, which is below the USD 8M limit so the limit does not bite). The insured bears USD 750K, the deductible. The insurer pays USD 6.05M. The policy limit of USD 8M is not reached in this event, so it plays no role here.
CGross loss: USD 8M. The policy limit caps the insurer's liability at USD 8M regardless of where the deductible falls, the limit is always the binding constraint.
DGross loss: USD 6.8M. Deductibles only apply when the loss exceeds the deductible threshold, since USD 6.8M exceeds USD 750K, the full ground-up loss becomes the gross loss and the deductible is disregarded.

2. The cat model produces a 1-in-250 year gross loss of USD 62M for Halcyon's full property portfolio. Halcyon's Cat XL reinsurance programme provides USD 45M of cover above a USD 20M retention. What is the net loss at the 1-in-250 year return period, and what does it tell you about Halcyon's capital adequacy at this severity level?

ANet loss: USD 62M. Reinsurance recoveries are not applied in the cat model's net loss calculation, net loss refers to the loss net of co-insurance and participation clauses on the primary policy, not reinsurance. Reinsurance is a separate financial arrangement outside the model's scope.
BNet loss: USD 17M. The Cat XL attaches at USD 20M retention, Halcyon bears the first USD 20M. The USD 45M of reinsurance cover then pays the next USD 45M, taking the programme to USD 65M. A USD 62M gross loss falls within the programme: Halcyon retains USD 20M and recovers USD 42M from reinsurers, leaving a net retained loss of USD 20M. Wait, actually USD 62M โˆ’ USD 20M retention = USD 42M recovery from Cat XL, so net = USD 62M โˆ’ USD 42M = USD 20M. This tells you the reinsurance programme is adequate at the 1-in-250 level, Halcyon's capital only needs to absorb USD 20M at this severity, not USD 62M. If the gross loss exceeded USD 65M (retention + limit), Halcyon would face an uncovered layer above the top of the programme.
CNet loss: USD 45M. The Cat XL pays its full limit of USD 45M, and Halcyon retains the remainder, USD 62M โˆ’ USD 45M = USD 17M. This is the net loss Halcyon's capital must absorb.
DNet loss cannot be calculated from this information, you need to know the specific events that drive the 1-in-250 year gross loss before you can calculate how the Cat XL responds, because the reinsurance trigger is event-based not aggregate-based.

3. Halcyon writes a property policy on a Meridian warehouse in Houston. The policy covers wind and fire but explicitly excludes flood. A hurricane makes landfall nearby, causing USD 3.1M of wind damage and USD 4.2M of storm surge flooding at the warehouse. What is the gross loss?

AUSD 7.3M, the total ground-up damage. The policy covers the hurricane event, and storm surge is a consequence of the hurricane, so all damage arising from the hurricane event is covered regardless of the specific cause of damage at the property.
BUSD 3.1M, the wind damage only. The financial module applies the coverage scope filter first: flood is explicitly excluded, so the USD 4.2M of storm surge damage produces zero insured loss. Only the USD 3.1M of wind damage falls within the covered perils. This is a critically important principle, a large physical loss from a named peril event can produce a much smaller insured loss if the dominant damage mechanism falls outside the policy's coverage scope. The ground-up loss is USD 7.3M. The insured loss is USD 3.1M. The insured bears the remaining USD 4.2M regardless of how severe the storm was.
CUSD 4.2M, the flood damage only. Storm surge from a hurricane is classified as a marine peril under most policy wordings, which means it falls under the flood exclusion rather than the wind coverage. Wind-driven rain damage is separately covered, but the structural wind damage at USD 3.1M would need to be assessed against the specific wording.
DThe gross loss depends on the specific policy wording's definition of flood, if surge is defined separately from inland flooding, wind-driven surge may be covered under the wind peril and produce a USD 7.3M gross loss.

4. An analyst runs the Meridian portfolio without configuring the financial module, leaving all deductibles at zero and all limits at TIV. The resulting AAL is USD 5.8M. After correctly configuring the actual policy conditions (deductibles ranging from USD 250K to USD 2M per location), the AAL drops to USD 3.9M. Which statement best describes what happened?

AThe second run is more conservative, applying deductibles reduces the modelled loss, which means the insurer is underestimating its true exposure. The first run without deductibles was the correct basis for accumulation monitoring.
BThe first run overstated the insurer's actual liability by treating every dollar of ground-up loss as insured. Deductibles mean the insured absorbs the first portion of every loss, the insurer only pays above the deductible threshold. The USD 1.9M difference between USD 5.8M and USD 3.9M represents losses that the policy conditions place on the insured, not the insurer. The second run is the correct representation of Halcyon's actual gross loss exposure. Using the first run for pricing or accumulation monitoring would systematically overstate how much the insurer owes, which sounds conservative but actually leads to mispriced premium (too high relative to covered risk) and inaccurate accumulation management.
CBoth runs produce valid outputs for different purposes, the unconfigured run gives the ground-up perspective useful for engineering assessment, while the configured run gives the gross loss perspective for underwriting. Neither is more correct than the other.
DThe difference of USD 1.9M indicates the deductibles are too high, the policy structure is shifting too much loss onto the insured, which will make Meridian's programme uncompetitive in the market and is a signal to renegotiate the terms.

5. Why does the cat model need a financial module at all? The vulnerability module already produces a loss estimate. Why is another step necessary?

AThe financial module is needed to convert the vulnerability module's output from a physical unit (percentage damage) into a monetary value (dollars). Without it, the model would produce ratios rather than loss amounts that underwriters and actuaries can work with.
BThe financial module is needed to aggregate individual location losses into a portfolio total, the vulnerability module calculates loss per location, while the financial module sums them into the portfolio-level output the underwriter and actuary need.
CThe vulnerability module produces the ground-up loss, total physical damage, as if the building had no insurance at all. But what an insurer cares about is not the total physical damage: it is the specific portion of that damage that falls within the contract it has written. Two insurers with identical exposure to the same building sustain completely different losses if their policy conditions differ. The financial module exists because a cat model that could not apply policy conditions would estimate physical damage to buildings, which an engineer can do, but could not estimate insured loss, which is what the insurance industry actually prices, manages, and holds capital against. The distinction between ground-up and insured loss is the entire reason the financial module is a separate component rather than a rounding step at the end of the vulnerability calculation.
DThe financial module is needed to apply demand surge adjustments, the increase in repair costs that occurs in the aftermath of a major catastrophe when labour and materials are in short supply. This demand surge cannot be estimated by the vulnerability module alone because it depends on the scale of the event and the broader market response, not just the damage to individual buildings.