Considerations for Claims Financials

• Full multi-currency functionality including calculations for adjustments and limits isn't supported.
• If multi-currency is enabled, you'll see a currency dropdown, but backend processing defaults to the org's primary currency. For example, the primary currency is USD.
• Creating or editing claim coverages may fail if the parent Claim record lacks a properly set Loss Date and a link to an Insurance Policy.
• Use APIs to create a claim coverage without a mandatory participant, but these records may cause errors when viewed in the Claim Financials component due to validation.

Bulk Payment

Before you run a bulk payment, review these considerations for processing limits, locking behavior, and failure handling. To pay multiple claim coverage payment details (CCPDs) at once, see Pay Claim Coverage Payment Details in Bulk.

• A single bulk payment request accepts a maximum of 10,000 CCPD records.
• Only CCPDs in Draft status qualify for bulk payment.
• Bulk payment groups CCPDs by original policy for processing, and groups run in parallel. Bulk payment processes records within a group sequentially to ensure accurate limit tracking.
• Bulk payment locks the CCPD records during processing. You can't make edits, individual payments, or cancellations on those records until processing completes.
• If a CCPD record within a policy group fails to process, bulk payment skips subsequent records in that group. Other policy groups in the same request continue processing independently.