ClaimFinancialSettings Metadata Type Guide

Architectural Overview#

In property and casualty (P&C), life, and health insurance carriers running on Salesforce Financial Services Cloud / Insurance Cloud, claims adjudication involves strict financial accounting around Loss Reserves, Expense Reserves, and Claim Payment Summaries. The ClaimFinancialSettings metadata type enables and configures the platform’s native claim financials engine.

Storing ClaimFinancial.settings-meta.xml in SFDX version control ensures that scratch orgs, SIT/UAT sandboxes, and production environments enforce identical financial reserve and payment processing rules before deploying dependent Claim, ClaimCoverage, and ClaimPaymentSummary Flow automations.

Directory Location and File Suffix#

In Salesforce DX projects, ClaimFinancialSettings is stored in the settings directory as ClaimFinancial.settings-meta.xml.

Key Metadata Fields#

The following table describes the configuration flags on ClaimFinancialSettings in API version 68.0 (Winter ’27):

Declarative Metadata Example#

The following ClaimFinancial.settings-meta.xml file enables Claim Financial Management in a target Insurance Cloud environment:

<?xml version="1.0" encoding="UTF-8"?>
<ClaimFinancialSettings xmlns="http://soap.sforce.com/2006/04/metadata">
    <enableClaimFinancialSettings>true</enableClaimFinancialSettings>
</ClaimFinancialSettings>

Package Manifest (package.xml)#

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>ClaimFinancial</members>
        <name>Settings</name>
    </types>
    <version>68.0</version>
</Package>

SFDX CLI Retrieval and Deployment#

Use the Salesforce CLI (sf) to retrieve and deploy ClaimFinancialSettings:

# Retrieve ClaimFinancialSettings from an Insurance Cloud org
sf project retrieve start --metadata Settings:ClaimFinancial

# Deploy ClaimFinancialSettings to a target org
sf project deploy start --metadata Settings:ClaimFinancial

Architect Best Practices and Gotchas#

• Scratch Org Definition Alignment: When building automated CI/CD pipelines with scratch orgs, include the corresponding Insurance Claims feature and claimFinancialSettings block inside config/project-scratch-def.json so scratch org creation provisions the underlying standard objects automatically.
• Permission Set Assignment: Enabling ClaimFinancialSettings exposes the feature at the org level, but claims adjusters still require the appropriate Insurance Claims permission set license and PermissionSet CRUD access to create reserve adjustments and payment summaries.

Frequently asked questions

What does ClaimFinancialSettings control in Salesforce Insurance and Financial Services Cloud?

It controls org-wide claim financial management behavior, such as enabling claim financial tracking, reserve calculation modes, and payment authority enforcement on Claim and ClaimCoverage objects.

How is ClaimFinancialSettings referenced in package.xml?

In package.xml, use the Settings metadata type with the member name ClaimFinancial, which maps to force-app/main/default/settings/ClaimFinancial.settings-meta.xml in SFDX source format.

Why does deploying ClaimFinancial.settings-meta.xml fail in a standard Sales Cloud org?

ClaimFinancialSettings requires Insurance Cloud or Financial Services Cloud Claims management licenses to be provisioned in the target org.

Can ClaimFinancialSettings be used alongside Flow and Apex for claim adjudication?

Yes, ClaimFinancialSettings enables the underlying platform financial engine, while Flow and Apex orchestrate custom adjudication rules and external payment gateway callouts.