GL Per Occurrence vs Aggregate Checker
Route actual independently covered GL occurrence amounts chronologically through per-occurrence and shared aggregate limits; no occurrence clustering/deductible adjudication or coverage determination.
Description
Per-occurrence and aggregate limits constrain different dimensions of general liability (GL) cover.
Per-occurrence and aggregate limits constrain different dimensions of general liability (GL) cover. Chronological routing exposes aggregate exhaustion.1
The returned values include Caller occurrence payments minor, Closing gl aggregate remaining minor, Total amount beyond caller gl limits minor. The How section below explains the calculation, input rules and interpretation.
When to use GL Per Occurrence vs Aggregate Checker
Use GL Per Occurrence vs Aggregate Checker when you need to evaluate the supplied records under the calculation and evidence rules below. No occurrence clustering, deductible adjudication or coverage determination is supplied.
Prepare the observed policy, claim or quote evidence and independently verified policy tables. Monetary fields use integer minor units in one currency: for a currency with 100 minor units per major unit, enter 12345 for 123.45. One basis point is 0.01 percentage points, so 10000 basis points represents 100%.
How to use GL Per Occurrence vs Aggregate Checker and understand its results
- Prepare the observed policy, claim or quote evidence and independently verified policy tables. Monetary fields use integer minor units in one currency: for a currency with 100 minor units per major unit, enter 12345 for 123.45. One basis point is 0.01 percentage points, so 10000 basis points represents 100%.
- Enter callerGlPerOccurrenceLimitMinor, callerGlAggregateLimitMinor, callerIndependentlyCoveredOccurrenceAmountsMinor using the field table and calculation rules, then run the tool.
- Read callerOccurrencePaymentsMinor, closingGlAggregateRemainingMinor, totalAmountBeyondCallerGlLimitsMinor. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| callerGlPerOccurrenceLimitMinor | Caller gl per occurrence limit minor | number | Required |
| callerGlAggregateLimitMinor | Caller gl aggregate limit minor | number | Required |
| callerIndependentlyCoveredOccurrenceAmountsMinor | Caller independently covered occurrence amounts minor | list of number | Required |
Enter integer limits and independently covered occurrence amounts 0–10¹² each in chronological order. The amount list may be empty. Return each payment, closing aggregate and total covered amount beyond limits, with safe-integer sums.
payment_i=min(coveredAmount_i,occurrenceLimit,remainingAggregate); remainingAggregate−=payment_i Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| callerOccurrencePaymentsMinor | Caller occurrence payments minor | list of number |
| closingGlAggregateRemainingMinor | Closing gl aggregate remaining minor | number |
| totalAmountBeyondCallerGlLimitsMinor | Total amount beyond caller gl limits minor | number |
{
"input": {
"callerGlPerOccurrenceLimitMinor": 10000,
"callerGlAggregateLimitMinor": 15000,
"callerIndependentlyCoveredOccurrenceAmountsMinor": [
12000,
8000
]
},
"output": {
"callerOccurrencePaymentsMinor": [
10000,
5000
],
"closingGlAggregateRemainingMinor": 0,
"totalAmountBeyondCallerGlLimitsMinor": 5000
}
}Limitations and assumptions
No occurrence clustering, deductible adjudication or coverage determination is supplied.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Numeric lists are limited to 10,000 entries; string lists to 128 strings of at most 128 characters each. The rules above may impose smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Water Backup Endorsement Limit Checker: A water-backup endorsement may have a term limit already partly consumed. The current deductible reduces eligible loss before remaining-limit application. For a complementary task, use Loss Of Use Additional Living Expense Daily Calculator: Additional living expense compares displaced spending with normal spending for independently eligible days. A remaining limit caps the pooled incremental amount.
References
-
GL Per Occurrence vs Aggregate Checker — tool.io
Similar or alternative tools
- Water Backup Endorsement Limit Checker
A water-backup endorsement may have a term limit already partly consumed. The current deductible reduces eligible loss before remaining-limit application.
- Loss Of Use Additional Living Expense Daily Calculator
Additional living expense compares displaced spending with normal spending for independently eligible days. A remaining limit caps the pooled incremental amount.