Skip to content
Ishqkala

Core claims systems integration

Sapiens International logoIshqkala + Sapiens ClaimsPro

Subrogation scoring for Sapiens ClaimsPro within CoreSuite for Property & Casualty.

Vendor: Sapiens InternationalSync: Real-time + batchMethods: 3

Overview

Sapiens ClaimsPro is the claims component of Sapiens CoreSuite for Property & Casualty, alongside PolicyPro and BillingPro. Ishqkala reads claim, note and document data from the ClaimsPro reporting tables Sapiens provides for near real-time reporting, through a read-only connection your team provisions, or from a scheduled extract. Findings return as a findings file or through the interfaces your CoreSuite implementation exposes, so your adjusters see a note and task without changes to ClaimsPro configuration.

Use cases

  • Score commercial lines claims for contractor, landlord and product liability without changing ClaimsPro.
  • Run the Closed-Claim Sweeper against ClaimsPro history from the reporting tables.
  • Give subrogation managers a daily ranked list with SOL dates across lines.
  • Catch water losses where the notes name a plumber, a supply line brand or a building owner.

Architecture & data flow

How data moves between Sapiens ClaimsPro and Ishqkala.

  1. 01

    Read reporting tables

    Ishqkala queries the ClaimsPro reporting tables on a schedule you set, typically every 15 minutes, through a read-only database user.

  2. 02

    Fetch documents

    Document references are resolved against your repository and retrieved for OCR.

  3. 03

    NLP and scoring

    Notes and documents are read for liability signals and scored on recoverable dollars, win probability and days to SOL.

  4. 04

    Return findings

    Findings post through a CoreSuite interface or return as a file your integration team loads.

API data flow

Objects read and written.

Write-back is limited to the objects listed here and can be switched off entirely for read-only deployments.
ObjectDirectionWhat Ishqkala does with it
ClaimReadLoss date, jurisdiction, loss cause, line and status from the reporting tables.
Claimants and partiesReadInvolved parties and roles, used to name the adverse party.
Claim notesRead / writeAdjuster notes parsed for liability signals; a finding note is written back where an interface is available.
DocumentsReadPolice reports, estimates and expert reports, retrieved from your document repository by reference.
Reserves, payments and recoveriesReadPaid amounts for the recoverable estimate, and recoveries already booked so they are not flagged twice.
TaskWriteA review task for the subrogation unit, through an interface or loaded from the findings file.

Security & data governance

Controls on this connection.

  • Read-only database user restricted to the reporting tables Ishqkala needs, connected over a private network link or IP-allowlisted TLS 1.3.
  • No write access to ClaimsPro transactional tables.
  • AES-256 at rest in US AWS regions only, with AWS GovCloud available.
  • Zero model training on your claim files, and a HIPAA BAA for bodily injury records.
  • Every query and finding logged for SOC 2 Type II evidence and internal audit.

Setup timeline

From kickoff to first findings.

  1. Week 1

    Access

    Your DBA provisions the read-only user and network path; agree which CoreSuite interface, if any, handles write-back.

  2. Weeks 2 to 3

    Mapping and baseline

    Map reporting table fields and codes; run a 24-month closed-claim baseline.

  3. Weeks 4 to 5

    UAT

    Subrogation leads review findings and set thresholds and routing.

  4. Week 6

    Production

    Scheduled reads and write-back go live.

FAQ

Sapiens ClaimsPro integration FAQ

The reporting tables exist for this kind of access. Ishqkala reads only changed rows on each run, and you set the schedule.

No formal partnership is implied. Ishqkala connects through data access your team provisions under your Sapiens agreement.

Any version that includes the ClaimsPro reporting tables. Earlier versions can use a scheduled extract instead.

No. Your adjusters open and manage recoveries. Ishqkala supplies the evidence, score and deadline.

Find the millions hiding in your closed claim files before the Statute of Limitations expires.

We'll scan a batch of 500 closed claims for free and deliver an itemized recovery manifest within 5 business days.