Data Issues
Study guides: Exam DISC-DA, Exam 5, Exam 7
Data Issues are defects in the data behind a ratemaking or reserving analysis — errors, omissions, inconsistent definitions, anomalous values and structural irregularities — that would bias the result if the data were used as delivered. The actuary must find them, then correct, adjust for, work around or disclose them.
\text{CY}_Y\ \text{paid} = \sum_{\text{AY}} \left( P_{\text{AY}}^{(Y)} - P_{\text{AY}}^{(Y-1)} \right)
P_{\text{AY}}^{(Y)}is cumulative paid for an accident year as of year-endY: the latest diagonal of a paid triangle less the previous diagonal is the calendar year's payments. That identity is what lets a triangle be reconciled to financial statements, a standard first check on any reserving or ratemaking extract.- Friedland's verification checklist (not an audit — see Data Quality): consistency with financial statement data; consistency with the prior analysis's data, with any difference explained; reasonableness — questionable values such as large negative paid claims or fields that contradict each other are investigated, though not presumed wrong; and definitions — know what each field means (incurred, reserves and paid all mean different things to different departments) and how often default values stand in for missing information.
- Typical errors: transactions coded to the wrong accident period, line or coverage; payments not yet allocated to an accident period; impossible dates (a claim reported before it occurred, a policy effective after it expires); zero or negative exposure; duplicated or missing months; catastrophes and large losses flagged inconsistently.
- Definitional changes masquerade as trends: counting per claimant instead of per occurrence, treating reopened claims as new, including ALAE, recording claims net or gross of recoveries. See Claims Coding Changes and Changing Conditions.
- In a modelling data set (the record-level data behind a predictive model), the common issues are found by looking at each variable and are handled case by case:
- Unusual values: an outlier may be a data entry error, a genuine extreme or a real discovery. Repeat the analysis with and without it; if it changes the result, find its cause before dropping it and disclose the removal. A value that cannot be true is better replaced by a missing value than deleted with its whole row (Outlier).
- Missing values in disguise: an impossible zero, such as a zero dimension, is often a missing value coded as zero, which a search for missing values will not find (Missing Data).
- Duplicates: a record loaded twice, or a join on a key that repeats, inflates counts and totals. Counting occurrences of each key finds them.
- Inconsistent coding and definitions: the same quantity in different units, formats or bases across sources has to be put on one basis, as described under Data Documentation and Data Validation.
- Exam 7 — issues in a stochastic triangle model (Shapland's ODP bootstrap): negative incremental values (a modified log link handles them unless a whole column sums negative, which needs a constant shift; or model salvage and subrogation separately); missing values (estimate from surrounding cells, or exclude from the factors and residuals); outliers (exclude with care — skewed residuals are expected); heteroscedasticity (group development periods and adjust residuals, or sample within groups); heteroecthesious data — a partial first development period or partial last diagonal; and exposure changes (model losses per exposure). See Data Diagnostic Analysis, Stochastic Reserving, Missing Data, Outlier.
- The end-of-analysis counterpart is reasonableness testing of the results: implied frequencies, severities, loss ratios and average unpaid per open claim by year.
A Paid Triangle That Does Not Reconcile Cumulative paid ($000):
AY 12 24 36 48 20214{,}2007{,}1008{,}3008{,}70020224{,}5007{,}5008{,}90020234{,}8008{,}10020245{,}000The accounting records show calendar year
2024payments on AY2021–2024of\$10{,}700k, of which\$5{,}600k is on AY2024. The selected paid CDF at12months is2.10. Reconcile and assess the effect.Answer
\begin{align*} \text{Latest diagonal} &= 8{,}700 + 8{,}900 + 8{,}100 + 5{,}000 \\ &= 30{,}700 \\ \text{Prior diagonal} &= 8{,}300 + 7{,}500 + 4{,}800 = 20{,}600 \\ \text{Triangle CY 2024} &= 30{,}700 - 20{,}600 = 10{,}100 \end{align*}The triangle is
\$600k short. By accident year its CY2024increments are400,1{,}400,3{,}300and5{,}000; the first three match the accounting records, so the gap is entirely in AY2024— typically payments made but not yet allocated to an accident period when the extract was cut.
\$600\text{k} \times 2.10 = \$1{,}260\text{k}of AY
2024ultimate would be missing from a paid projection, and next year's12–24factor would be overstated when the payments surface. Correct the extract (or reallocate the\$600k) before selecting anything.
A Keying Error in the Development Factors Paid
12–24age-to-age factors for AY2019–2023are1.62,1.66,2.945,1.67and1.63. Investigation of AY2021finds a\$580{,}000payment keyed as\$5{,}800{,}000; the AY had\$4{,}000k paid at12months. AY2024has\$4{,}300k paid at12months.Quantify the effect and the right treatment.
Answer
\begin{align*} \text{Corrected AY 2021 at 24} &= 11{,}780 - 5{,}220 = 6{,}560 \\ \text{Corrected factor} &= 6{,}560 / 4{,}000 = 1.640 \\ \text{Average as keyed} &= 9.525 / 5 = 1.905 \\ \text{Average corrected} &= 8.220 / 5 = 1.644 \end{align*}(The keyed value at
24months was6{,}560 + 9 \times 580 = 11{,}780.) Left in, the error would add4{,}300 \times (1.905 - 1.644) = \$1{,}122k at the12–24step alone for AY2024, before the rest of the CDF compounds it; it would also depress AY2021's later factors, since its base is inflated.Correcting the record is better than excluding the cell: exclusion loses a genuine observation, and in an ODP bootstrap an error left in the triangle becomes an extreme residual that is resampled into every other cell's variability.
How it appears on the exam
- Exam 5 and Exam 7 test data issues in reserving and ratemaking data: reconciling a triangle to the financial statements, spotting a keying error through an anomalous development factor, and recognising a definitional change that looks like a trend.
- DISC-DA covers addressing common data issues in its topic on working with different types of data, after structured and unstructured data. Application questions describe a problem in a modelling data set (an outlier, a duplicated record, an impossible value, inconsistent units) and ask how to detect it or what to do about it.
Exam traps
- Investigate before deleting: An extreme value that is genuine carries information. Dropping it without a cause, or without disclosing it, biases the data.
- Drop the value, not the row: Replacing one impossible value with a missing value keeps the rest of the record's information; deleting the row loses it.
- A definitional change is not a trend: A shift caused by counting claims differently, or by including ALAE, moves the data without any change in the underlying losses.