Extract data from proof of coverage letters
A proof of coverage letter confirms that a policy is in force. Unlike a claim document, it makes no reference to a loss; its single purpose is to state that named coverage exists, for whom, with what limits, and through what date. A landlord verifying a tenant's liability cover, a general contractor checking a subcontractor before letting it on site, and a lender confirming a borrower's insurance all ask for this letter. When Continental Guaranty Insurance (NAIC 20443) issues a proof of coverage on 2026-07-03 for Summit Ridge Contractors LLC on Commercial General Liability policy CGL-2026-559871, effective 2026-02-15 through 2027-02-15, the letter answers one question: is the coverage active. Fields that carry the weight are the ones a reader relies on to say yes. Its is_active flag reads true, the each_occurrence_limit is 1,000,000 USD and the general_aggregate_limit is 2,000,000 USD, and the products_completed_operations_aggregate and personal_advertising_injury_limit round out the liability tower. Named on the letter, the certificate_holder_name is Alder Street Holdings LLC, the landlord requiring proof, and the renewal_date of 2027-02-15 tells the holder when to ask again. Because the letter confirms an existing policy rather than creating one, it restates the policy_effective_date and policy_expiration_date exactly as the underlying contract shows them. Handed to Talonic, a proof of coverage letter returns the insured, the carrier, the limits, and the active status as typed fields, keeping the coverage lines as a table where several lines are confirmed at once. A letter dated 2026-07-03 confirming an active CGL policy with a 1,000,000 USD occurrence limit through 2027-02-15 loads into a vendor-compliance system as structured values instead of a filed PDF. What the letter states, including the active flag, is captured as written, and current standing is not itself confirmed with the carrier.
What gets extracted from proof of coverage letters
How extraction works for proof of coverage letters
Proof of coverage letters arrive as carrier letterhead PDFs, ACORD 25 certificates, and broker-issued confirmations, so the limits and the active status appear in prose on one and in a grid on another. Classification aligns the letter with the proof-of-coverage schema in the Field Registry, which separates the insured and carrier identity, the limit set, the certificate holder, and the in-force status. An is_active boolean is captured as its own field so a reader is not left inferring status from dates, the each_occurrence_limit, general_aggregate_limit, products_completed_operations_aggregate, and personal_advertising_injury_limit are typed as numbers, and the coverage_lines table returns each confirmed line with its policy number and effective and expiration dates. Certificate holder name and address are read because the letter is issued to a specific holder, and the renewal_date is parsed so a compliance team knows when the confirmation lapses. Every field returns with a confidence score and a source-region pointer consistent with DIN SPEC 91491, so a landlord or lender can verify a limit or the active flag against the letter. Reporting what the letter asserts is the boundary of the extraction, which does not confirm current standing with the carrier.
Sample extraction
A proof of coverage letter confirming an in-force CGL policy
{
"document_number": "POC-2026-11928",
"document_date": "2026-07-03",
"insured_name": "Summit Ridge Contractors LLC",
"insured_address": "2200 Granite Way, Boise, ID 83702",
"policy_number": "CGL-2026-559871",
"policy_effective_date": "2026-02-15",
"policy_expiration_date": "2027-02-15",
"insurer_name": "Continental Guaranty Insurance",
"insurer_naic_number": "20443",
"coverage_type": "COMMERCIAL GENERAL LIABILITY",
"each_occurrence_limit": 1000000,
"general_aggregate_limit": 2000000,
"products_completed_operations_aggregate": 2000000,
"personal_advertising_injury_limit": 1000000,
"certificate_holder_name": "Alder Street Holdings LLC",
"certificate_holder_address": "15 Alder St, Boise, ID 83702",
"additional_insured": true,
"subrogation_waived": false,
"is_active": true,
"renewal_date": "2027-02-15",
"coverage_lines": [
{
"insurer_letter": "A",
"coverage_type": "Commercial General Liability",
"policy_number": "CGL-2026-559871",
"policy_effective_date": "02/15/2026",
"policy_expiration_date": "02/15/2027",
"each_occurrence_limit": 1000000,
"aggregate_limit": 2000000
}
]
}Frequently asked
Does it capture whether the policy is active?
Yes. The is_active boolean is read as its own field and returns true when the letter states the coverage is in force, so a reader is not left inferring status from the effective and expiration dates alone.
How is a proof of coverage different from a binder?
A binder provides temporary coverage before the full policy issues, while a proof of coverage confirms a policy that is already in force. Talonic reads each on its own schema and captures the is_active flag on the proof of coverage rather than the short term of a binder.
Who is the letter addressed to?
The certificate_holder_name and certificate_holder_address are read, here Alder Street Holdings LLC, since a proof of coverage is issued to a specific holder such as a landlord or lender who required evidence of the insured coverage.
Does Talonic confirm the policy is still in force with the carrier?
No. It returns the limits, the dates, and the active flag as the letter states them and links each to its source region. Confirming current standing directly with the carrier is a separate step the extraction does not perform.
How is a proof of coverage letter different from a certificate of insurance?
A certificate of insurance, typically an ACORD 25, is the summary a broker issues to a third party listing coverage lines, policy numbers, and their limits as of the date it was issued. A proof of coverage letter instead states whether the policy is currently in force through its own is_active field, so a landlord or lender reading it gets a present-tense confirmation of standing rather than a point-in-time record of limits. Talonic keeps the two on separate schemas: one captures coverage lines at issuance, the other captures active status.
Ready to extract from your own proof of coverage letters?
Author note
Reviewed by Talonic engineering, insurance schema review · last reviewed 2026-07-08