Policy Number

Overview

The Policy Number is the identifier the insurance carrier uses to locate a specific policy contract in its systems. Every coverage row on the ACORD 25 — General Liability, Auto, Umbrella, Workers' Compensation, and any Other coverages — carries its own policy number, because each represents a separate contract even when all are placed with the same carrier.

The policy number is the anchor a compliance reviewer uses when they pick up the phone to verify coverage. A producer's name might be common, an insured's name might be contested, but a policy number is unambiguous: it either matches the carrier's records or it does not. This makes it the most operationally important identifier on the certificate for live verification workflows.

How It Works

When a carrier binds a policy, they assign it an identifier drawn from their internal numbering scheme. Formats vary by carrier — some use sequential integers, some use prefixed alphanumerics (GL1234567, CPP-98-45-1122), some use hashes. There is no ACORD-mandated format; the field simply accepts whatever string the carrier uses.

On the ACORD 25, the policy number travels with its coverage row. A vendor carrying GL with Travelers and Auto with Progressive will show two different policy numbers on two different rows, each tied via the Insurer Letter back to the correct carrier in the INSURERS AFFORDING COVERAGE block at the top of the form.

Common Patterns and Variations

A policy number listed as "Pending," "TBD," or left blank is a compliance defect on any coverage row the insured needs. The policy either exists or it does not; a certificate that cannot produce a policy number is not evidence of in-force coverage. This differs from the Certificate Number, which is optional and routinely blank without concern.

Where It Appears on ACORD 25

The policy number appears in the POLICY NUMBER column within each coverage row, positioned to the right of the coverage type description and before Effective Date and Expiration Date. Inori's extraction schema captures it per coverage: gl.policy_number, al.policy_number, umbrella.policy_number, wc.policy_number, and inside each other_coverages entry.

Policy numbers on the certificate must match those on the underlying Declarations Page. Any discrepancy between certificate and dec page is a material defect — the certificate is supposed to summarize the dec page, and if the identifiers do not match, the certificate may be describing a different policy than the one actually in force.

Why It Matters for Compliance

• Verification calls: When Inori or a reviewer calls the carrier or producer to confirm coverage, the policy number is the lookup key. Without it, no verification is possible.
• Renewal continuity: A renewed policy may keep the same base policy number with an incremented suffix (GL-2025-448 becomes GL-2026-448) or receive a fresh number entirely. Inori tracks both patterns to link certificates across policy periods.
• Duplicate detection: The platform uses the combination of policy number, carrier, and insured to detect when the same policy is being re-certified on multiple certificates, which is important for audit de-duplication.

Related Concepts

The policy number identifies a contract summarized on the Certificate of Insurance and fully documented on the Declarations Page. It is the primary lookup used during Insurance Verification, and it anchors the per-coverage dates (Effective Date, Expiration Date) that drive compliance checks on the ACORD 25.