Tutorials › CAS Exam 5 - Basic Ratemaking and Estimated Claim Liabilities › Allocating Losses Across Classification Cells

CAS Exam 5 · Classification Relativities · Tutorial 405 of 989

Allocating Losses Across Classification Cells

Learn to map loss records to the correct classification cell, preserve aggregate totals, and identify losses that cannot be assigned reliably.

Intermediate 11 min read

What You'll Learn

  • Match loss records to policy and coverage records using reliable identifiers.
  • Select the applicable classification using the loss date and coverage period.
  • Allocate multi-cell losses using documented, supportable allocation weights.
  • Reconcile assigned amounts to the selected paid or incurred loss total.
  • Flag unmatched, ambiguous, duplicate, or incomplete records rather than forcing an assignment.

Why Loss Allocation Requires Reliable Matching

Class experience is meaningful only when the losses assigned to a classification cell belong to the policies and coverages represented by that cell. A claim record may identify a policy but not a coverage, include several payment transactions for one claim, or lack a usable policy number. A seemingly small matching error can put a loss in the wrong cell, count it more than once, or leave it out of the analysis.

The allocation task is therefore more than joining two spreadsheets. The analyst must decide which loss measure is being used, identify the coverage and policy in force when the loss occurred, apply the classification information for that period, and reconcile the assigned amounts to the source total. If those steps do not support a reliable assignment, the loss should be flagged rather than placed arbitrarily.

Definition: A classification cell is a defined combination of the classification attributes used to group policies or exposures for analysis. Loss allocation is the process of assigning a selected paid or incurred loss amount to the cell or cells to which it belongs, using policy, coverage, time-period, and, where needed, documented allocation information.

Choose the Loss Basis and the Matching Key

Before matching records, define the loss measure being allocated. A paid-loss analysis uses paid amounts measured on a specified basis and as of a specified date. An incurred-loss analysis uses incurred amounts on a specified basis and as of a specified date. In common reporting, incurred loss is paid loss plus case outstanding amounts, subject to the organization’s definitions and treatment of recoveries. Do not add paid and incurred totals together: paid loss is already included in incurred loss under that definition.

The analysis should also say whether the selected amounts are gross or net of specified recoveries, and should apply that treatment consistently. The relevant records may be claim-level summaries, transaction records, or both. If both are present, determine which source is authoritative for the selected measure. Summing a claim summary and its underlying transactions would count the same loss twice.

A policy number alone may not uniquely identify a classification cell. A policy can cover more than one coverage, location, or insured item, and its classification may change over time. A robust matching key will often include the policy identifier, coverage identifier, and loss date, with a policy-term or item identifier when necessary. Use the classification information applicable to the insured risk and coverage at the loss date, not automatically the policy’s current classification or the date the claim was reported.

Record fieldWhy it matters for matching
Policy identifierLinks a loss record to a policy record, but may not distinguish coverages or terms by itself.
Coverage or item identifierDistinguishes the insured coverage, location, or item when a policy has more than one.
Loss dateIdentifies the applicable policy term and the classification in force for the loss.
Claim or transaction identifierHelps distinguish separate claims and avoid counting multiple transactions as separate losses.
Selected loss amount and basisEstablishes whether the allocation uses paid or incurred amounts and how recoveries are treated.

Formal Allocation and the Conservation Check

Let \(L_j\) be the selected loss amount for record \(j\), on the chosen paid or incurred basis. Let \(w_{jc}\) be the share of that amount assigned to classification cell \(c\). If the record belongs wholly to one cell, its weight is 1 for that cell and 0 for all others. If a loss is supportably split across cells, the weights can be fractional.

Definition: For a fully allocated loss record, allocation weights satisfy \(w_{jc} \ge 0\) and \(\sum_c w_{jc}=1\). The amount assigned to cell \(c\) is \(L_jw_{jc}\), and its total allocated loss is \(\sum_j L_jw_{jc}\). If the record cannot be assigned or split reliably, it is not a fully allocated record and should be reported separately until resolved.

The weights must reflect evidence or a documented allocation rule, not a convenient way to make cell totals balance. For example, if a claim’s itemized loss amounts identify the covered locations, those amounts can support a split. A policy-wide amount with no item, coverage, or other reliable basis for splitting does not become assignable merely because the policy has multiple cells.

$$ \sum_c \left(\sum_j L_jw_{jc}\right) =\sum_j L_j\left(\sum_c w_{jc}\right) =\sum_j L_j $$

This identity is the basic conservation check. Because the weights for each fully allocated record sum to 1, summing its allocations across cells returns its original amount. Summing across all fully allocated records therefore returns their total source amount. It does not imply that every source loss was assigned: amounts held as unmatched, ambiguous, or otherwise unallocated must be shown separately in the reconciliation.

Worked Examples

Worked Example: Matching Policy, Coverage, and Loss Date

An analyst is preparing a hypothetical incurred-loss file as of December 31. The source contains four records: claim 501, policy P-18, general liability coverage, loss date April 12, incurred loss $3,200; claim 502, policy P-18, general liability coverage, loss date October 8, incurred loss $1,800; claim 503, policy P-44, general liability coverage, loss date August 16, incurred loss $5,400; and claim 504, policy P-44, property coverage, loss date August 16, incurred loss $2,600. The policy and classification records show that P-18 general liability is in cell A for both loss dates, P-44 general liability is in cell B, and P-44 property is in cell C. Assign the losses and reconcile them.

Method. Match each claim using policy, coverage, and loss date. The stipulated records provide a unique applicable cell for every claim, so each record receives weight 1 in that cell.

Cell A. Claims 501 and 502 both match P-18 general liability in cell A. The assigned amount is \(3{,}200+1{,}800=\$5{,}000\).

Cell B. Claim 503 matches P-44 general liability in cell B. The assigned amount is \(\$5{,}400\).

Cell C. Claim 504 matches P-44 property in cell C. The assigned amount is \(\$2{,}600\).

Reconciliation. The source total is \(3{,}200+1{,}800+5{,}400+2{,}600=\$13{,}000\). The cell total is \(5{,}000+5{,}400+2{,}600=\$13{,}000\), so all four records are assigned once and the amounts reconcile.

Common mistake avoided. Matching on policy number alone would not distinguish P-44’s general liability and property coverages. The coverage identifier is necessary because those records map to different cells.

Worked Example: Splitting a Multi-Location Loss

A hypothetical property policy covers two scheduled locations in different classification cells. A single incurred claim is $23,000. The claim file itemizes $12,000 of building damage at the first location and $8,000 at the second. The remaining $3,000 is a shared debris-removal cost. The documented allocation rule assigns shared costs in proportion to the itemized building damage. Allocate the claim.

Method and assumption. Use the itemized amounts for the location-specific damage. Split the shared cost in proportion to the itemized damage, since that is the stated, supportable rule. This rule is appropriate here because the problem specifies it; it should not be assumed for other claims without a basis.

The itemized damage total is \(12{,}000+8{,}000=\$20{,}000\). The first location’s share is \(12{,}000/20{,}000=0.60\), and the second location’s share is \(8{,}000/20{,}000=0.40\).

The shared cost assigned to the first location is \(3{,}000(0.60)=\$1{,}800\). Its total allocation is \(12{,}000+1{,}800=\$13{,}800\). The shared cost assigned to the second location is \(3{,}000(0.40)=\$1{,}200\). Its total allocation is \(8{,}000+1{,}200=\$9{,}200\).

Check. The weights for the shared cost sum to \(0.60+0.40=1.00\), and the cell allocations sum to \(13{,}800+9{,}200=\$23{,}000\), the original claim amount.

Common mistake avoided. Assigning the full $23,000 to each location would produce $46,000 and double count the claim. Assigning the full amount to just one location would ignore the itemized evidence for the other.

Worked Example: Reconciling Transactions and an Unmatched Record

A hypothetical file contains transaction rows for claim 801 under policy Q-11, property coverage: payments of $4,000 and $1,000, followed by a $500 recovery. The claim summary reports paid loss of $4,500. The classification records map Q-11 property at the loss date to cell D. A second claim, 802, has paid loss of $1,200 but no policy identifier, coverage identifier, or other reliable link to the policy file. The selected measure is net paid loss after the listed recovery. Determine what can be allocated.

Method. Use the transaction detail to verify the claim summary, but do not add the summary to its own transaction rows. Calculate claim 801’s net paid amount as \(4{,}000+1{,}000-500=\$4{,}500\). This agrees with the summary and maps to cell D.

Claim 802 has no reliable matching key. Its $1,200 cannot be placed in a classification cell based on the information given, so report it as unallocated pending resolution.

Reconciliation. The total source amount is \(4{,}500+1{,}200=\$5{,}700\). Cell D has $4,500 assigned and $1,200 remains unallocated; \(4{,}500+1{,}200=\$5{,}700\).

Common mistake avoided. Adding the $4,500 claim summary to the $4,500 net transaction total would count claim 801 twice, yielding a false source total of $10,200 after including claim 802. The correct total is $5,700.

Unassigned Losses and Quality Controls

An unassigned amount is not necessarily an error in the claim itself. It may reflect incomplete data, an ambiguous match, or a loss whose relationship to multiple cells is not documented. Keeping such amounts visible is preferable to making an unsupported assignment. Depending on the purpose of the analysis, the analyst may seek corrected identifiers, policy documents, coverage details, or claim-level allocation information before deciding whether the loss can be included.

A practical review should distinguish among the following situations:

  • Unmatched: the claim has no reliable link to a policy or classification record.
  • Ambiguous: more than one policy term, coverage, or cell could match, and available fields do not resolve which one applies.
  • Partially allocable: a documented portion can be assigned, but another portion cannot be allocated on available evidence.
  • Potential duplicate: the same claim may appear in both summary and transaction records, or the same transaction may appear more than once.
  • Inconsistent: identifiers or dates conflict across records, so the apparent match needs review before assignment.

A good reconciliation reports the source amount, the amount assigned to cells, and any amount held out as unallocated. If the file uses different sources for paid and incurred amounts, or if recoveries are treated differently, the reconciliation should make that basis clear. A cell total that happens to equal a target total does not prove that the individual claims were correctly classified; matching and allocation need their own evidence.

1
Fix the basis.
Specify paid or incurred loss, the valuation date, and the treatment of recoveries. Select one authoritative amount for each claim and avoid adding summaries to their underlying transactions.
2
Match the insured risk.
Use policy, coverage or item, and loss-date information, adding term or location identifiers when needed. Apply the classification effective for that risk and period.
3
Allocate only with support.
Assign a whole claim to one cell when the match is unique. Split it only when itemized information or a documented rule supports the allocation weights.
4
Reconcile and investigate.
Compare assigned cell amounts with the fully allocated source amount, list unallocated amounts separately, and investigate duplicates, missing links, and conflicting records.

Common Exam Traps

  • Using the wrong date. The report date or policy’s current classification may differ from the classification applicable on the loss date. Match the loss to the relevant policy term and insured risk.
  • Using policy alone as the key. A policy may include several coverages or items that belong to different cells. Include the identifiers needed to distinguish them.
  • Counting a claim more than once. Transaction rows, claim summaries, and coverage rows may all represent the same underlying loss. Establish the unit being totaled and reconcile sources before summing.
  • Forcing a match. A missing or conflicting identifier is not permission to assign a loss to the most convenient cell. Flag it and show its amount separately until reliable information is available.
  • Creating unsupported allocation weights. Splitting a claim equally across cells is not automatically reasonable. Use equal weights only if a documented rule or evidence supports them.
Key takeaway: A defensible cell allocation preserves the selected source loss total, matches each loss to the correct policy, coverage, and period, and makes any unsupported or unresolved amounts visible rather than disguising them in cell totals.

Check Your Understanding

For each problem, identify the assignment or reconciliation supported by the stated information.

  1. A hypothetical claim has incurred loss of $2,750. Its policy and coverage identifiers uniquely match cell R for the loss date. What amount is assigned to cell R, and what is the claim’s allocation weight? (Answer: $2,750; weight 1.00 in cell R.)
  2. A policy has two covered units in cells S and T. Itemized loss is $6,000 for the unit in S and $4,000 for the unit in T, with no shared costs. How much is assigned to each cell, and what is the check total? (Answer: $6,000 to S and $4,000 to T; total $10,000.)
  3. A single claim has $7,500 of itemized damage at a location in cell U and $2,500 at a location in cell V. A documented rule allocates a shared $1,000 expense in proportion to itemized damage. Find each cell’s total allocation. (Answer: $8,250 to U and $2,750 to V.)
  4. A selected paid-loss file has a $3,600 claim summary and transaction rows of $2,400, $1,500, and a $300 recovery for the same claim. The summary is net of the recovery. What amount should be counted, assuming the summary is authoritative and the rows verify it? (Answer: $3,600, counted once.)
  5. A $4,800 claim has a policy identifier and loss date, but the policy file has two possible coverage records in different cells and the claim has no coverage identifier or item detail. What amount should be assigned to either cell using only these facts? (Answer: $0 to either cell; report $4,800 as unresolved or unallocated pending reliable matching information.)
Clinical Biostats