Automatic Acceptance Limit Monitoring for Life Reinsurers

Automatic Acceptance Limit Monitoring: Catching Life Cessions That Should Have Gone Facultative

Last reviewed: November 2026

The most expensive life cession is the one that should never have been automatic. You usually find it on the day the death claim lands.

Short answer: Automatic acceptance limit monitoring tests every life cession against the treaty's automatic limit, jumbo limit and eligibility rules on arrival. Breaches are then resolved while the insured is alive, not argued over at claim.

Key Takeaways

• Define the limit before you test it. Many treaties state the binding limit ambiguously, and the check is only as good as the definition.
• Test the life, not the policy. Two cessions on one insured can each pass while together they breach the limit.
• Re-test on every change. Increases, reinstatements and conversions can push a compliant life over the limit years after issue.
• Fix breaches while the insured is alive. A breach found at claim time becomes a dispute, not an administrative fix.

What Is an Automatic Acceptance Limit?

An automatic acceptance limit is the maximum amount a reinsurer accepts on one life under an automatic treaty without reviewing the case. Above it, the cedent must retain the excess or submit the case facultatively.

Under an automatic treaty, the reinsurer accepts business on the cedent's own underwriting. The Society of Actuaries' commentary on life reinsurance treaties adds that the cedent normally keeps its full retention on each automatic case.

How does a jumbo limit differ?

A jumbo limit caps the total insurance in force and applied for on a life with all companies, not just this cedent. If that total exceeds the jumbo limit, the case cannot be ceded automatically.

Reinsurers use it because their automatic capacity on a wealthy life may already be filled through other clients. Large cases are also harder to underwrite well.

Why Do Over-Limit Cessions Slip Through?

Over-limit cessions slip through because limits are defined loosely, data arrives policy by policy, and nobody re-tests after issue. Each gap is small, but together they leave breaches hidden for years.

Is the limit itself clear?

Often it is not. Participants in the SOA's Life Reinsurance Treaty Construction study said binding limits appear as the reinsurer's share, as share plus retention, or as the whole pool.

That ambiguity changes the answer for the same case. Our illustrative example below shows how.

Who is watching?

Both sides often assume the other is. The same study records cedents expecting reinsurers to police limits, while reinsurers say the cedent underwrites the life and should know the amounts.

There is also no central register of insurance in force and applied for on each life. So the jumbo limit relies on what the applicant discloses and the underwriter finds.

How Can One Case Pass and Fail at the Same Time?

One case can pass and fail because the limit's definition decides the result. Here is an illustrative example with round numbers.

A cedent retains $1 million per life and cedes the rest to two reinsurers, 50% each. The treaty states an automatic limit of $5 million, and a $9 million policy arrives.

The cedent ceded it automatically under the first reading. The reinsurer's claims team may apply the third.

Which Breaches Can a Reinsurer Detect From Cession Data?

A reinsurer can detect most single-cedent breaches from cession data it already receives. Jumbo breaches spread across other insurers are only partly visible.

The facultative check matters because of a long-standing practice. The SOA commentary notes that a case once submitted facultatively generally cannot later qualify for automatic cover, though practice varies.

How Do You Monitor Automatic Limits in Practice?

Monitor automatic limits with a fixed routine that runs on every cession file, not an annual audit. Six steps cover most of the risk.

1. Codify the limit. Agree in writing whether the limit is per reinsurer or per pool, and whether it includes retention.
2. Build a life identifier. Match cessions on name, date of birth and other identity fields, so policies on one life group together.
3. Test at receipt. Run every new cession through the limit, retention, eligibility and facultative checks.
4. Re-test on change. Treat increases, reinstatements and conversions as new tests on the whole life.
5. Resolve with the cedent. Agree an outcome for each breach, such as facultative review, cedent retention or premium correction.
6. Report the pattern. Track breaches by cedent and cause, so repeat issues reach treaty renewal discussions.

Step five needs a recorded decision. A flag that nobody closes is no better than no flag.

Which Changes After Issue Trigger a Breach?

Increases, reinstatements and conversions are the usual triggers after issue. The SOA study notes that reinstatements can breach limits, and participants reported confusion over how increases apply.

A practical rule helps. Any transaction that raises the amount at risk on a life should re-run the full limit test.

Mortality data programmes can add pressure here. Our article on individual life reinsurance mortality data explains how accelerated underwriting changes the risk inside autobind limits.

What Should Happen When a Breach Is Found?

When a breach is found, the reinsurer and cedent should agree a documented outcome quickly. The options depend on the treaty wording and when the breach is found.

The SOA commentary also warns that cedent errors can leave reinsurers over-retained. Early detection keeps both sides' options open.

Where Does Automation Help?

Automation helps by running the same limit tests on every cession and change, with the result recorded. It does not decide whether a breach is accepted, refunded or reviewed.

Those tests need one agreed source for limits, retentions and shares. Reinsurance treaty management holds retention, limit and share configuration as structured, versioned treaty terms with an audit trail.

That gives monitoring rules a single reference instead of a PDF schedule. Treaty and underwriting teams still validate the configuration and decide each breach.

Inconsistent rule application is a wider problem than limits. See our analysis of cession rules applied inconsistently.

Which Metrics Show the Control Is Working?

The best metrics show breaches being found earlier and closed faster. A falling count of breaches found at claim is the clearest sign.

What Should Heads of Life Reinsurance Do Next?

Heads of life reinsurance should fix definitions and data before buying tools. The steps below need no new system to start.

• Review your top treaties and confirm how each binding limit is defined.
• Agree the minimum identity and transaction fields with each cedent.
• Re-test the current in-force book on a per-life basis once.
• Add breach patterns to the agenda for every treaty renewal.

Key Terms

• Automatic acceptance limit: The most a reinsurer accepts on one life under an automatic treaty without case review. Also called the automatic binding or autobind limit.
• Jumbo limit: The cap on total insurance in force and applied for on one life with all companies.
• Retention: The amount of each life the cedent keeps for its own account.
• Facultative submission: Sending a case to a reinsurer for individual underwriting and a separate offer.
• Over-retention: A reinsurer carrying more on a life than it intended, often after a cedent error.
• Innocent breach: A limit breach the cedent did not know about when it ceded the case.

Sources

• Society of Actuaries: Life Reinsurance Treaty Construction (March 2013)
• Society of Actuaries: Commentary on Life Reinsurance Treaties (1994)
• Insurnest: Reinsurance Treaty Management