Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionaryIInsurance Policy
ServiceIntermediate

Insurance Policy

An Insurance Policy in Salesforce Financial Services Cloud is a record on the InsurancePolicy standard object representing the active contract between an insurer and a policyholder.

Insurance Policy record for a Homeowners Policy with policy number, account, status, term dates, and a related claims panel.
Illustrative mock of the Insurance Policy page in Lightning Experience
§ 01

Definition

An Insurance Policy in Salesforce Financial Services Cloud is a record on the InsurancePolicy standard object representing the active contract between an insurer and a policyholder. The object holds the policy number, the issuing carrier (typically an Account), the policyholder (a Contact or Person Account), the policy type (Auto, Home, Life, Health, Commercial), the effective and expiration dates, the premium amount, and the coverage details. Insurance Policy is the centerpiece of the Financial Services Cloud Insurance data model, with child objects for InsurancePolicyAsset (insured items), InsurancePolicyCoverage (coverage limits), InsuranceClaim (claims filed), and InsurancePolicyParticipant (named insureds, beneficiaries, agents).

The object replaces the Asset-based and custom-object approaches insurance carriers used before Salesforce released the Insurance data model. The Financial Services Cloud Insurance package layers on Account record types (Policyholder, Carrier, Broker), Lightning components (Policy Summary, Coverage Grid), and Flow templates (Quote-to-Policy, Renewal). The combined model supports both personal lines (auto, home, life) and commercial lines (workers compensation, business owners, general liability), with field-level extensions per product line.

§ 02

How the Insurance Policy object structures the policy lifecycle

The InsurancePolicy standard object

InsurancePolicy is the parent record for everything related to a single insurance contract. Fields include PolicyNumber, NameInsuredId (the policyholder), PolicyType (Auto, Home, Life, Commercial), EffectiveDate, ExpirationDate, Premium, Status (In Force, Lapsed, Cancelled), CarrierId (the insurer), and ProducerId (the issuing agent or broker). Custom fields extend the model for product-specific attributes.

Child objects that complete the picture

The full data model includes InsurancePolicyAsset (the insured item: car, home, business), InsurancePolicyCoverage (each coverage type with limits and deductibles), InsurancePolicyParticipant (additional named insureds, beneficiaries, lien holders), and InsuranceClaim (claims filed against the policy). These children let the same Policy record support complex multi-vehicle, multi-property, or multi-beneficiary scenarios.

Personal lines vs. commercial lines

Personal lines policies (auto, home, life) have one policyholder, one or two named insureds, and a simpler coverage structure. Commercial lines policies (workers comp, general liability, business owners) have a business policyholder, many named insureds (every employee), and complex coverage grids. The InsurancePolicy object supports both; the differences are in record type and field configuration, not in the object itself.

Renewal and endorsement workflow

Renewals are typically modeled as a new InsurancePolicy record with a Parent Policy lookup to the prior term. Endorsements (mid-term changes) can be tracked on the existing record or as a child Endorsement object depending on the carrier''s model. Flow templates ship with the Financial Services Cloud Insurance package to automate the renewal generation.

Claims integration

When a claim is filed, an InsuranceClaim record is created with a lookup to the InsurancePolicy. The claim has its own lifecycle (FNOL, Investigation, Adjudication, Settlement, Closed) and integrates with Field Service for adjuster scheduling. Claims reporting joins back to the policy to surface loss ratio, claim frequency, and severity per product line.

Underwriting workflow integration

Pre-bind underwriting workflows use the InsurancePolicy record in a draft state. The underwriter reviews exposure, applies rating factors, and approves or declines. Once approved, the policy moves to In Force status and the carrier issues coverage. The underwriting and binding workflow leverages Flow Orchestration for multi-step handoffs between agent, underwriter, and compliance.

Compliance and regulatory reporting

Insurance is heavily regulated. The InsurancePolicy data model supports regulatory reporting requirements (Statutory financial reporting, state-specific filings, NAIC compliance). Custom fields capture the data elements regulators require; standard reports aggregate them.

§ 03

Set up the Insurance Policy data model in Financial Services Cloud

The objects ship with the FSC Insurance package. Configuration focuses on record types, page layouts, and integration with the underlying policy administration system.

  1. Enable Financial Services Cloud Insurance

    Setup, Industries Settings, enable FSC and the Insurance package. The standard objects appear in Object Manager.

  2. Configure record types per line of business

    Create Auto, Home, Life, and Commercial record types on InsurancePolicy with line-specific page layouts and field-level security.

  3. Map fields to the policy administration system

    Coordinate with the carrier''s policy admin system (Guidewire, Duck Creek, custom mainframe). Map each Salesforce field to the source-system equivalent; use MuleSoft or a custom integration to keep the data in sync.

  4. Set up child object workflows

    Configure InsurancePolicyAsset, InsurancePolicyCoverage, and InsurancePolicyParticipant page layouts and validation rules. Test parent-child creation workflows end-to-end.

  5. Build renewal and endorsement flows

    Use Flow Builder or the included FSC Insurance flow templates to automate renewal generation, endorsement processing, and claim creation from a policy.

  6. Train agents and underwriters

    Walk users through the policy creation, renewal, and claim workflows. Cover the most common edge cases per line of business.

Gotchas
  • Insurance policies must stay in sync with the policy admin system. Integration design is critical; out-of-sync data leads to wrong claims handling and regulatory exposure.
  • Personal lines and commercial lines have very different data shapes. Plan separate record types and page layouts; one shared layout serves neither well.
  • Regulatory requirements vary by state and country. Document which fields drive which reports before going live.
  • The FSC Insurance package is a Salesforce Industries product with its own licensing. Confirm the contract covers your use case before building extensively on the data model.
§

Trust & references

Sources

Cross-checked against the following references.

Official documentation

Straight from the source - Salesforce's reference material on Insurance Policy.

Was this entry helpful?
Help us write better definitions. Quick reactions or detailed edit suggestions.

About the Author

Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.

§

Test your knowledge

Q1. What is an Insurance Policy in Salesforce?

Q2. What's part of the broader insurance data model?

Q3. Where are Insurance Policy records used?

§

Discussion

Loading…

Loading discussion…