Matching Loss Adjustment Expenses to Claims

Why Claim-Level Expense Matching Matters

A claim file can contain both indemnity payments and costs incurred while investigating, evaluating, defending, or settling the claim. If an expense can be linked to a particular claim, it should be joined to that claim before the claim totals are grouped into experience periods. This keeps loss and expense measures aligned: the claim and its directly attributable adjustment costs are treated as a unit under the chosen period basis.

The claim’s occurrence, policy, report, and payment dates can differ, and an expense may be paid well after the claim occurs. The appropriate date therefore depends on the measure being prepared. For example, an accident-year paid measure groups payments by the accident year of the claim, while a calendar-year paid measure groups them by the date the payment was made. These are different views of the same transactions.

The label alone does not determine how a transaction should be assigned. A useful claim-level record needs a valid claim identifier, an amount, the transaction type, and the dates needed for the measure being prepared. A direct claim link answers which claim?; the period basis answers which experience period? A claim link does not by itself determine whether a transaction belongs in a calendar-year or accident-year summary.

Define the Measure Before Grouping

Let \(c\) denote a claim and let \(A_{c,k}\) denote the amount of the \(k\)th ALAE transaction linked to claim \(c\). For a paid measure, include the qualifying paid transactions in the stated observation window. For an incurred measure at a stated valuation date, use paid amounts plus the applicable outstanding ALAE estimate at that date. The two views are not interchangeable: a paid amount and the remaining estimate describe different parts of the claim cost.

Let \(b(c)\) be the period assignment for claim \(c\) under the selected basis. For accident-year grouping, \(b(c)\) is determined by the claim’s accident date; for policy-year grouping, it follows the applicable policy-period assignment; and for report-year grouping, it follows the report-date assignment. A calendar-year paid summary instead groups paid transactions by their transaction dates. The assignment conventions for the relevant period basis must be applied consistently to losses and claim-linked expenses.

Here \(\mathcal{P}(c)\) is the set of qualifying paid ALAE transactions linked to claim \(c\) within the defined observation window. For an accident-year paid total for year \(Y\), sum those claim-level paid totals for claims assigned to accident year \(Y\). For a calendar-year paid total, sum paid transactions whose payment dates fall in calendar year \(Y\), regardless of the claims’ accident years.

Why the Claim-Date Rule Works

The reason for assigning claim-linked ALAE with the claim under an accident-year measure is that the measure groups claim experience by the accident that produced it. A later invoice payment remains an expense of handling that same claim; changing the payment date does not change the claim’s accident date. This rule does not mean every period summary uses the accident date. It means the date rule follows the measure’s stated basis.

The claim identifier is what permits the first sum to use the claim’s period assignment. The transaction date is what permits the second sum to use the payment’s calendar period. In either case, each qualifying transaction should appear once in the relevant total. Corrections, reversals, or duplicate records must be handled according to the data convention before aggregation; otherwise even a correct period rule can produce an incorrect total.

Data Controls Before Aggregation

A claim-level expense summary is only as reliable as the links and transaction records that feed it. Before summing, confirm that each expense record points to a valid claim and that the record is classified as an adjustment expense under the applicable definitions. Check for missing claim identifiers, duplicate transaction entries, reversals, and amounts stored with an inconsistent sign. If an invoice covers more than one claim, it is not directly claim-specific until the amount has been split using a documented allocation method.

Keep the underlying transaction detail when possible. It allows the analyst to build paid views using payment dates and claim-period views using the claim assignment, rather than forcing one grouping into a data set that cannot support another. A reconciliation is also useful: the total of qualifying claim-linked transactions should agree with the corresponding detail-level total after any documented exclusions or adjustments.

Shared Costs Need a Separate Convention

Some claim-handling costs support many claims rather than one identifiable claim. General staff salaries, office costs, or shared systems expenses may not have a defensible direct claim link. Calling such costs ALAE and dividing them among claims simply because a claim-level total is desired would disguise an allocation as a direct match. They should remain separately identified as shared or unallocated costs until an appropriate assignment convention is specified.

That convention might use a chosen exposure, claim count, or another documented basis, depending on the purpose and applicable reporting rules. The choice affects the resulting claim or period measures; it is not determined by the claim identifiers used for ALAE. The detailed methods for assigning shared costs are a distinct task. For this topic, the essential control is to avoid silently mixing those costs into directly matched claim expense.

Common Mistakes and a Reconciliation Check

• Using payment year for every measure. Payment date controls a calendar-year paid measure, but a claim-period measure follows its specified claim assignment.
• Grouping before validating claim links. A missing or invalid identifier can leave a claim-specific cost out of the correct claim total or attach it to the wrong claim.
• Mixing paid and incurred amounts. Do not add an outstanding estimate to a paid total unless the target is an incurred measure and the components are defined consistently.
• Counting a transaction twice. Duplicate records, reversals, or a detail-to-summary join that multiplies rows can inflate totals. Check transaction identifiers and reconcile sums.
• Forcing shared expense into claim totals. A shared amount needs an explicit assignment convention; it is not a direct claim match merely because a claim-level report is desired.

A practical final check is to compare the sum of the included claim-linked transactions with the aggregate produced by the period report, using the same expense scope, observation window, and period basis. If the totals differ, investigate the record links, date filters, transaction status, and any adjustments before interpreting the result.