A loss run can look like a simple table of claim numbers and amounts. But every amount belongs to a view of the claim at a particular point in time. A claim that is open in one report may be closed in a later report; a case reserve may be adjusted; a payment may be added after the first extract was produced.
That makes the valuation date part of the data, not a footnote. Two reports with different dates can both be accurate and still be unsafe to compare as if they described the same snapshot. A useful intake process keeps the date, report scope, carrier and policy period attached to each claim and total.
Separate the dates before comparing claims
Insurance documents can carry several dates that answer different questions: when the loss occurred, when the claim was reported, the policy’s effective period, when the report was generated, and the date through which claim values were evaluated. The last is often called the valuation or as-of date. A generated date tells you when a file was produced; it does not, by itself, tell you which claim activity the amounts include.
Preserve the label and source location for each date. If a report does not identify the valuation date clearly, mark it as unknown and request confirmation instead of substituting the download date. When a reviewer compares carriers or renewal periods, line up the documented as-of dates and the scope of the reports first.
Paid losses and reserves are different facts
A paid amount records payments made by the valuation date. A case reserve is an estimate of unpaid amounts associated with a reported claim. An incurred figure may combine paid amounts with amounts held in reserve, depending on the report’s definitions. These values can change as claims develop; they are not interchangeable labels for one fixed “claim cost.”
The NAIC’s loss-reporting instructions distinguish paid losses, reported losses and unreported losses as of a report date, and explain that reported loss amounts can include payments already made and development on reported claims. The NAIC glossary also describes loss reserves as estimates for incurred claims not yet paid. Those sources illustrate why a pipeline should preserve each supplied field and its definition instead of calculating a new total from columns whose meanings are unclear. They do not establish one mandatory layout for every carrier’s loss run.
Four checks make the snapshot reviewable
Before a loss run moves into an underwriting or renewal workflow, an extraction system can make four boundaries explicit:
| Check | What to capture | What to do when it is missing or different |
|---|---|---|
| Valuation date and scope | As-of date, report creation date, covered policy periods, and the source page for each. | Keep an unknown date unknown. Ask for a comparable report before treating two snapshots as a trend. |
| Paid versus open reserves | Claim status, paid amount, case reserve, and the report’s own incurred or total fields. | Preserve the carrier’s definitions. Flag a mismatch or an unexplained total for review; do not silently recalculate it. |
| Carrier-level totals | Carrier identity, policy or account reference, currency, row count and any stated subtotal. | Reconcile totals within a matching scope. Keep carrier subtotals visible instead of flattening them into a single number. |
| Policy years and gaps | Policy-year or effective-date range requested, years represented, and the source document for each period. | Mark an unrepresented year as missing information. A blank period is not proof of no claims or proof that coverage existed. |
The point is not to make a coverage decision. It is to give the reviewer a traceable set of facts: what the document says, which period it covers, what the carrier reported, and where a comparison needs confirmation.
A missing year is a question, not a zero
A request may ask for several years of claims history, while the packet contains fewer reports. The absent period could reflect a missing upload, a change of carrier, a different policy identifier, or a report that was not available. An extraction system cannot infer which explanation is correct from an empty row.
Represent the requested years separately from the years actually found. For each report, retain the named insured, policy reference, carrier, effective dates and report date. Then show the unmatched period as an exception with the evidence that would resolve it. This is more useful than filling a gap with a zero, because zero reads like a measured result.
Keep each report in its own context
Loss-run layouts and labels can vary. A carrier may give a claim-level detail, a summary, or both; one report may separate paid losses and case reserves while another presents a carrier-defined incurred total. Currency, claim status, and policy-year conventions also need to be read from the source rather than assumed.
- Keep the original field — store the label, extracted value, page or row, and normalized value together.
- Keep the report identity — associate every claim and subtotal with the carrier, insured, policy reference and valuation date that produced it.
- Compare like with like — align period, carrier scope and definitions before calculating a portfolio view.
- Route uncertainty with evidence — show the source and the exact mismatch so a reviewer can decide whether to request a replacement report or clarify a field.
This separation also helps when a later report changes. The old snapshot remains evidence of what was available at the earlier review; the new report can be added as a newer observation without rewriting the prior extraction.
Use automation to prepare the review
Cogneris can classify insurance documents, extract claim and policy fields, retain source evidence, and route uncertain results for review. The claims document processing page describes that document layer, while the ACORD extraction guide covers forms and supporting claim documents. The reports still need the customer’s rules for matching insureds, policies and carriers.
Automation can surface a missing valuation date, a reserve/status conflict, a carrier subtotal that does not reconcile, or a requested policy year with no supporting report. It should not decide whether a risk is acceptable, assume a missing year means no losses, or replace an insurer’s figures with a guessed total. Those are reviewer decisions, and the source trail should make them easier to verify.
Sources
- NAIC Statistical Handbook, Report 1 instructions — defines paid, reported and unreported loss fields by report date, and distinguishes reported-loss development from true IBNR in that reporting context.
- NAIC Glossary of Insurance Terms — definitions for loss reserves, incurred losses and IBNR.
This article explains document extraction and review handoffs. It is not underwriting, coverage, actuarial or insurance advice.