Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionaryCClaim
ServiceBeginner

Claim

A Claim in Salesforce is the standard insurance industry object that represents a policyholder's request for payment, repair, or benefit under an active Insurance Policy.

Insurance Claim record for a Wind Damage Claim with status, policy holder, dates, and an activity timeline of adjuster steps.
Illustrative mock of the Claim page in Lightning Experience
§ 01

Definition

A Claim in Salesforce is the standard insurance industry object that represents a policyholder's request for payment, repair, or benefit under an active Insurance Policy. The object lives in Financial Services Cloud Insurance and Salesforce Industries Insurance solutions, with fields for Claim Number, Policy, Claimant (the Person Account or Insured Entity making the claim), Loss Date, Loss Type, Status, Reserve Amount, Paid Amount, and links to associated Claim Items, Claim Participants, and Claim Documents. Claims pass through a lifecycle (Submitted, Acknowledged, Under Review, Approved, Settled, Denied, Closed) tracked through standard status fields plus custom milestone records.

Claims matter because they are the moment of truth for any insurance carrier. The claim experience defines customer perception of the brand; speed, accuracy, and empathy through the claim lifecycle determine renewal rates and word-of-mouth. Salesforce Industries Insurance gives carriers a unified Claim record that ties to the Policy, the policyholder, the adjusters working it, third-party participants (witnesses, body shops, medical providers), and the financial reserves and payouts. The model integrates with policy administration, finance, and customer-service workflows so the claim file is the single source of truth across the carrier's operation.

§ 02

How Claims work in Salesforce Industries Insurance

The Claim data model

The Claim object is the parent record with Claim Number, Loss Date, Loss Type, Status, Reserve, Paid Amount, Cause Of Loss, and Description. Child objects include Claim Item (per damaged item or covered service), Claim Participant (witnesses, third parties), Claim Coverage (which policy coverages apply), and Claim Document (uploaded files like photos, police reports, medical records).

Claim lifecycle and milestones

Claims typically flow through First Notice of Loss (FNOL), Investigation, Coverage Verification, Adjustment, Settlement, and Closure. Each stage has its own SLA, owner, and required documentation. Industries Insurance ships a configurable milestone framework that tracks the lifecycle and surfaces overdue stages on dashboards.

First Notice of Loss (FNOL)

FNOL is the customer's initial submission, often through a digital channel (Experience Cloud claim portal, mobile app, Service Cloud Voice). Salesforce captures the loss details, generates the Claim record, and routes it to the right adjuster team based on loss type, geography, and policy.

Adjusters and Claim Team

The adjuster owns the Claim through investigation and settlement. Industries Insurance supports Claim Team members (similar to Case Team) for cross-functional staffing: investigator, appraiser, supervisor, legal counsel. Each team member has a role and access level.

Reserves, payments, and financial tracking

Reserve Amount captures the adjuster's estimate of total exposure. Paid Amount tracks actual disbursements. The two together drive carrier financial planning. Reserve adjustments require approval workflows; misestimated reserves are a regulatory red flag.

Integration with policy and customer

Claims link back to the Insurance Policy that covers them, the policyholder (Person Account), and any related parties. The 360-degree view lets adjusters see the full customer context, recent service interactions, and policy history when working a claim.

Subrogation and salvage

When a third party caused the loss, the carrier may pursue subrogation (recovery from the at-fault party). The Subrogation object tracks recovery attempts. Salvage applies to damaged property the carrier acquires and disposes of. Both reduce net claim cost.

Compliance and audit

Insurance is highly regulated; claims data feeds state filings, NAIC reports, and audit trails. Salesforce Industries Insurance ships standard compliance fields and reports; mature implementations integrate with regulatory reporting tools to automate the filing process.

§ 03

How to set up Claims in Salesforce Industries Insurance

Standing up Claims is a multi-team project covering data model, claim lifecycle, integrations, and customer-facing intake. The configuration steps below assume the broader Industries Insurance program is in place.

  1. Enable Insurance in Salesforce Industries

    Setup, Salesforce Industries Insurance. Activate Insurance permission sets and assign to adjusters, supervisors, and claim staff.

  2. Configure the Claim data model

    Object Manager, Claim. Add fields per business need (Cause of Loss, Catastrophe Code, Risk Group). Build the Lightning record page with the standard plus org-specific layout.

  3. Build FNOL channels

    Experience Cloud claim portal for self-service, Service Cloud Voice for phone, mobile app for in-field FNOL. Each channel produces a Claim record routed to the right adjuster.

  4. Configure claim lifecycle and milestones

    Define milestone records for each stage (FNOL, Investigation, Settlement, Closure). Configure SLAs and notifications. Build dashboards for in-flight claims by stage.

  5. Integrate with policy admin and finance

    Connect to the policy administration system for coverage verification. Connect to finance for payment disbursement and reserve tracking. Without these integrations, claims work becomes data entry.

Gotchas
  • Reserve estimates that prove wildly off are regulatory red flags. Approval workflows on Reserve changes prevent ad-hoc adjustments.
  • FNOL channel mismatches between digital and call-centre intake produce duplicate claims. Deduplication at intake is critical.
  • Compliance reporting needs structured data. Free-text fields make audit nightmares; standardise picklists for Cause of Loss, Loss Type, Catastrophe Code.
  • Integration with policy admin and finance is not optional at scale. Claims without integrated data become manual reconciliation projects.
§

Trust & references

Sources

Cross-checked against the following references.

Official documentation

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

Keep learning

Hands-on resources to go deeper on Claim.

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 does a Claim represent in Salesforce?

Q2. In which Salesforce product is Claim primarily used?

Q3. What lifecycle stages does a Claim typically pass through?

§

Discussion

Loading…

Loading discussion…