> For the complete documentation index, see [llms.txt](https://docs.onre.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onre.finance/reinsurance-framework/onyc-loss-absorption-and-reserving.md).

# ONyc Loss Absorption and Reserving

### Overview

OnRe’s portfolio is structured so that, in most modeled scenarios, claims are absorbed through four layers of protection before they reach ONyc’s NAV. This page explains how the portfolio is constructed, how premium is reserved, how each layer absorbs claims and how a claim payment flows through to NAV.

ONyc is a NAV-based asset whose value reflects the performance of OnRe’s reinsurance portfolio and the yield on its collateral. Holders carry underwriting risk, and the structures described here determine how much of that risk is absorbed before it reaches principal.

### Portfolio Structure and Exposure Limits <a href="#portfolio-structure-and-exposure-limits" id="portfolio-structure-and-exposure-limits"></a>

Three structural features define how much capital is at risk on each contract and when it can be affected.

{% stepper %}
{% step %}

#### No Leverage

The portfolio carries no leverage. Each contract is fully collateralized, so the capital deployed against it represents the maximum possible loss on that position. The [Capital Deployed](https://app.onre.finance/earn/transparency#:~:text=RENEWAL-,CAPITAL%20DEPLOYED,-NET%20PREMIUM) figure on the Transparency Dashboard therefore sets the ceiling on loss for each contract.
{% endstep %}

{% step %}

#### Attachment Points and Limits

Each reinsurance contract defines the covered events, an attachment point and a payout limit. Claims are paid only under those terms.

{% hint style="info" %}
For example, a contract covering U.S. windstorm losses with a $10 billion attachment point pays nothing until losses exceed that threshold. Once triggered, payments follow the contract terms up to the contractual limit. Exposure is spread across multiple structures, layers and limits, so portfolio performance does not depend on any single trigger.
{% endhint %}
{% endstep %}

{% step %}

#### Retrocession

The majority of OnRe’s current exposure is retrocession, reinsurance provided to other reinsurers and underwriters. In these structures, OnRe’s capital attaches above the losses those reinsurers retain, so those retained losses must be exceeded before OnRe’s capital is drawn on.
{% endstep %}
{% endstepper %}

### Premium Reserving <a href="#premium-reserving" id="premium-reserving"></a>

Before any yield is recognized, OnRe reserves premium against the expected loss of each contract. ONyc’s quoted yield combines the underwriting return remaining after that reserve with the return earned on collateral.

* Reserving is an actuarial process. Expected loss is modeled for each contract using a conservative actuarial approach, and that amount is held back from premium at inception. Reserves cover claims that have been reported as well as losses that have occurred but have not yet been reported.
* The [Expected Loss](https://app.onre.finance/earn/transparency#:~:text=NET%20PREMIUM-,EXPECTED%20LOSS,-EXPECTED%20YIELD) figure published for each contract on the Transparency dashboard is the amount OnRe has reserved against claims on that contract. Summed across active contracts, Expected Loss gives the total reserved for claims across the portfolio.
* In a typical year, OnRe reserves up to 50% of premium, with reserves built ahead of peak catastrophe season so that the majority of expected losses can be met as they arise.
* Premium is paid to OnRe upfront by the cedent. The portion remaining after reserves is earned as underwriting yield over the coverage period of each contract, alongside the yield earned on collateral. Learn more about OnRe's [Collateral Composition](https://docs.onre.finance/for-capital-providers/collateral-composition.md).

### The Four Layers of Loss Absorption <a href="#the-four-layers-of-loss-absorption" id="the-four-layers-of-loss-absorption"></a>

Claims are absorbed in sequence, and ONyc’s NAV is affected only once claims exceed all four layers.

{% stepper %}
{% step %}

#### Layer 1: Claims Reserves

Expected losses are conservatively estimated upfront and reserved before any yield is paid, so quoted APY already reflects them. Claims within that estimate are paid from the reserve and leave NAV unchanged.
{% endstep %}

{% step %}

#### Layer 2: Underwriting Yield

Claims that exceed reserves are absorbed through yield first. APY recalibrates over the remaining contract duration, so the adjustment is spread across the term and principal remains intact.
{% endstep %}

{% step %}

#### Layer 3: Portfolio Diversification

OnRe underwrites multiple reinsurance contracts at once, across different structures, layers and limits. Earned premium from performing contracts helps absorb unexpected claims on any single contract, because ONyc’s NAV reflects the results of the whole portfolio.
{% endstep %}

{% step %}

#### Layer 4: Yielding Asset Reserve

A portion of the pool is held in yielding assets behind the reinsurance book. This reserve supports secondary market liquidity, backstops gaps in insurance contracts and provides an additional capital buffer.
{% endstep %}

{% step %}

#### Net Asset Value

Principal is affected only once claims exceed all four layers, which requires an event beyond modeled expectations.
{% endstep %}
{% endstepper %}

### How Claims Affect NAV <a href="#how-claims-affect-nav" id="how-claims-affect-nav"></a>

A claim payment and a NAV loss are separate events. When a potential loss event is identified, each affected policy’s case estimate is offset against that policy’s unearned premium reserve (UPR) first, and only the excess reduces NAV.

#### Case Estimates and UPR

A case estimate is set for each affected policy as a best estimate plus a margin proportional to the uncertainty around the ultimate loss. For an ILW, which pays a fixed limit once the reported industry loss exceeds its trigger, the best estimate is the probability of trigger multiplied by OnRe’s limit. For indemnity contracts, it is the modeled loss to the cedent’s portfolio multiplied by OnRe’s share.

Where a case estimate is smaller than the policy’s UPR, NAV is unchanged and the loss shows only as premium that will no longer be earned. This is the outcome in OnRe’s Hurricane Ida, Typhoon Jebi and Storm Bernd historical scenarios. Case estimates are carried as claim reserves alongside the pool’s other reserves and insurance contract liabilities.

#### Worked Example: 1.5x Hurricane Ian Stress Scenario

The example applies OnRe’s procedure to a fictional hurricane, sized to reproduce the 1.5x Ian stress scenario from OnRe’s investor reporting as at 31 March 2026. The event, policies, triggers and probabilities are illustrative, and all other NAV components are held constant.

Offsetting the case estimates against UPR absorbs $3.70m of the loss. The remaining $11.10m reduces NAV by 6.45%, from $172.0m to $160.9m.

Once the affected policies’ UPR is consumed, that premium stops earning, so forward APY falls until the released capacity is redeployed.

#### Revisons as Information Arrives

Estimates are revised as post-event modeled losses, cedent notices and PCS industry loss estimates are published. The table shows how the illustrative event could develop from its initial estimate, with the two PCS rows as alternative outcomes.

When an estimate falls, the reduction is released through increased APY and restoration of UPR, including any reinstatement premium. If a forecast storm weakens or misses, the loss is withdrawn and reserves are released the same way.

<table data-header-hidden="false" data-header-sticky><thead><tr><th width="111.15625">Claim</th><th width="101.0546875">Paid from
Reserve</th><th width="101.8359375">Absorbed
by Yield</th><th width="101.27734375">Remaining</th><th>Outcome</th></tr></thead><tbody><tr><td>$400,000</td><td>$400,000</td><td>$0</td><td>$0</td><td>Paid within reserve, NAV unchanged</td></tr><tr><td>$900,000</td><td>$600,000</td><td>$300,000</td><td>$0</td><td>Yield lower for the term, NAV unchanged</td></tr><tr><td>$1,500,000</td><td>$600,000</td><td>$600,000</td><td>$300,000</td><td>Shortfall offset by the rest of the portfolio and the yielding asset reserve</td></tr></tbody></table>

In every case, the maximum possible loss on this contract is its $10,000,000 of capital deployed, because the portfolio carries no leverage.

#### Across the Portfolio <a href="#across-the-portfolio" id="across-the-portfolio"></a>

If ten contracts each reserve $1,000,000 and nine of them incur $500,000 of claims while one incurs $3,000,000, total claims are $7,500,000 against $10,000,000 reserved. The single contract runs $2,000,000 over its reserve, while the portfolio remains within its aggregate reserve.

### Reading the Transparency Dashboard

The [Transparency Dashboard](https://app.onre.finance/transparency) publishes contract-level data for every active contract in the portfolio.

<table data-header-hidden="false" data-header-sticky><thead><tr><th width="158.76953125">Column</th><th>What it Shows</th></tr></thead><tbody><tr><td>Structure</td><td>The reinsurance structure of the contract, such as an ILW.</td></tr><tr><td>Status</td><td>The current stage of the contract. Bound means the cedent has accepted terms, and the reinsurance contract is binding.</td></tr><tr><td>Inception</td><td>The start of the coverage period.</td></tr><tr><td>Renewal</td><td>The end of the coverage period, at which the contract expires or is renewed.</td></tr><tr><td>Capital Deployed</td><td>Collateral committed to the contract. As the portfolio carries no leverage, this is the maximum possible loss on the contract.</td></tr><tr><td>Net Premium</td><td>Premium received by OnRe after brokerage and other deductions.</td></tr><tr><td>Expected Loss</td><td>The modeled loss on the contract, held in reserve against claims before any yield is recognized.</td></tr><tr><td>Expected Yield</td><td>The annualized return on the contract, composed of the pure underwriting return and an adjusted T-bill return on collateral.</td></tr></tbody></table>

Three portfolio measures can be derived directly from the dashboard. Summing Expected Loss across active contracts gives the total held in reserve for claims. Dividing Expected Loss by Net Premium gives the share of each contract’s premium reserved before yield is recognized, and Capital Deployed by contract shows how exposure is distributed across the portfolio.

### Loss Event Response

OnRe follows a Board-approved provisional loss adjustment procedure. Where an event has the potential to cause a NAV drawdown, OnRe’s insurance committee convenes within 24 hours, and it can act on a forecast before landfall.

See additional details under [Claims and Risk Management](https://docs.onre.finance/reinsurance-framework/claims-and-risk-management.md).

### Risk Considerations

The primary risk to ONyc holders is underwriting risk. If claims exceed premium income and the layers described above, NAV may decline, including in extreme or correlated loss scenarios.

Reserving reduces the effect of expected claims, and actual outcomes can differ from modeled estimates. Positions built on ONyc with borrowed capital, such as looped positions on lending markets, amplify both yield and any NAV movement.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.onre.finance/reinsurance-framework/onyc-loss-absorption-and-reserving.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
