Extract data from policy endorsements

A policy endorsement, also called a rider or an amendment, changes a policy that is already in force instead of opening a new contract. It attaches to one policy by its policy number and inherits that policy's inception and expiration dates, then states exactly what is being altered: a limit raised, a party added, an exclusion removed, or a premium recalculated. A risk manager updating a certificate program, an underwriter booking the premium change, and a broker confirming the amendment to a lender all read the same endorsement. When Meridian Casualty Company (NAIC 10657) issues an endorsement dated 2026-07-01 to Harbor Point Logistics LLC on Commercial General Liability policy CGL-2025-884120, in force from 2026-03-01 to 2027-03-01, the document records a mid-term change to coverage that is already running. What matters on an endorsement is the coverage changes it lists and the premium adjustment that follows. This endorsement raises the each-occurrence limit from 1,000,000 USD to 2,000,000 USD, names Dockside Property Trust as an additional insured, and adds a premium of 2,400 USD prorated across the eight months left in the term. The endorsement type classifies the change, the authorized_by and authorization_date record who signed it, and the coverage type fixes which line of business is affected. Because the amendment rides on an in-force policy, the base policy_effective_date and policy_expiration_date carry through unchanged while only the amended terms move. Fed to Talonic, an endorsement returns the policy header, the endorsement type, and the premium adjustment as typed fields, keeping the coverage changes as a table so each altered limit or added party is a row with its own effective date. An endorsement dated 2026-07-01 that lifts the occurrence limit to 2,000,000 USD and adds a 2,400 USD premium loads into a policy administration system as structured values rather than a re-keyed rider. Neither the binding nor the effective status is judged: the change is captured as written and left for the carrier and broker to confirm.

What gets extracted from policy endorsements

How extraction works for policy endorsements

Endorsements reach a carrier or broker as ACORD-based change forms, insurer-generated rider PDFs, and scanned amendments, and the altered terms sit wherever the form places them, sometimes as a single sentence and sometimes as a schedule. To read them consistently, Talonic aligns the document to the endorsement schema held in the Field Registry, which keeps the policy header, the endorsement type, the premium adjustment, and the coverage changes as separate fields. Premium adjustments are typed as a signed number in ISO 4217 currency, so a positive 2,400 USD addition is distinguished from a return premium, and the coverage_changes table returns each modification with its amount and its own effective and expiration dates. Where the endorsement restates them, the each-occurrence and general aggregate limits are read as numbers, while the additional_insured and subrogation_waived flags are captured as booleans and the base policy_effective_date and policy_expiration_date are preserved so the amendment stays tied to the term it modifies. Confidence scores and source-region pointers accompany every value under DIN SPEC 91491, so an underwriter can check the new limit or the premium against the signed rider before booking it. Structuring the amendment as written is the whole job, and no ruling is made on whether the endorsement is in force.

Sample extraction

A mid-term endorsement raising a limit and adding an insured

{
  "document_number": "END-2026-00417",
  "document_date": "2026-07-01",
  "policy_number": "CGL-2025-884120",
  "effective_date": "2026-07-01",
  "expiration_date": "2027-03-01",
  "insured_name": "Harbor Point Logistics LLC",
  "insurer_name": "Meridian Casualty Company",
  "insurer_naic_number": "10657",
  "endorsement_type": "coverage_amendment",
  "coverage_type": "COMMERCIAL GENERAL LIABILITY",
  "premium_adjustment": 2400,
  "each_occurrence_limit": 2000000,
  "general_aggregate_limit": 4000000,
  "additional_insured": true,
  "subrogation_waived": false,
  "authorized_by": "Elena Vasquez, Underwriting Manager",
  "authorization_date": "2026-07-01",
  "policy_effective_date": "2026-03-01",
  "policy_expiration_date": "2027-03-01",
  "coverage_changes": [
    {
      "coverage_changes_type": "Each-occurrence limit increased from 1,000,000 to 2,000,000",
      "coverage_changes_amount": 2000000,
      "effective_date": "2026-07-01",
      "expiration_date": "2027-03-01"
    },
    {
      "coverage_changes_type": "Additional insured added: Dockside Property Trust",
      "coverage_changes_amount": 0,
      "effective_date": "2026-07-01",
      "expiration_date": "2027-03-01"
    }
  ]
}

Frequently asked