The Claim Financials lighting web component (LWC) is the central workspace where claim
adjusters manage all financial aspects of a claim. This process starts after the First Notice of
Loss (FNOL), after the system has created the foundational claim records, such as coverages,
participants, and involved items. This component provides the capabilities needed to evaluate
and then settle the claim.
The Claim Financials LWC features a hierarchical data grid that empowers adjusters to
efficiently organize loss and expense data grouped by coverages and claim items. This grid
offers robust search, sort, and filtering capabilities, making it easy to find and manage
specific information. Adjusters can also perform critical in-context actions directly from the
grid, such as initiating payments or managing coverages, streamlining their workflow. The LWC
supports comprehensive claim coverage management, enabling users to create and manage loss and
expense items under open coverages.
To aid in informed decision-making, the Financial Dashboard provides real-time financial
intelligence through visual summaries. This dashboard presents critical data, including
insights into policy limits, payment progress, and the overall financial health of claims.
Administrators have the flexibility to configure the entire experience, tailoring the layout,
data views, and available actions to align with specific business processes.
Claim Financials Setup and Runtime Experience Use the configuration-driven framework for Claim Coverage Payment Detail (CCPD) forms to tailor the payment details data capture process as per your business needs. Define both the user interface layout and the underlying calculation logic without requiring custom code. The result is a dynamic system that ensures data is captured accurately and efficiently, adapting automatically to the context of the claim.
Claim Financials Setup Claims admins manage the entire setup process to operationalize the claims financials system.
Configurable Status to Action Mapping for Claim Payments Claim admins manage business-specific claim workflows by mapping org specific dynamic Claim Coverage Payment Detail (CCPD) statuses to non-configurable CCPD static enums and configuring allowed actions accordingly.
Customize Data Entry with Payment Detail Configuration When a claim adjuster adds a financial item such as a loss or expense, the system needs to identify the form to present and the calculation logic to use. Claim admins can specify this behavior for each product.
First Notice of Loss When policyholders, brokers, or insurance reps first report a loss to an insurance carrier, they use the First Notice of Loss (FNOL) flow. Insurance carriers set up this FNOL flow by using Omniscripts. Omniscripts provide the interface that policyholders, insurance carrier brokers, or insurance reps use to file a claim. This FNOL flow starts the claims processing and supports the submission of documents to support the claim. On the backend, the flow uses the verifyPolicyCoverage API to confirm if the policyholder has an active coverage on the date of the loss. Then, it uses the createClaim API to create the initial claim record and the updateClaim API to update the claim details with additional information.
Work with Claim Financials Claims adjusters can get a quick overview of claims and related tasks, and then dive into the management of individual claims.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.