Core claims systems integration
Ishqkala + Duck Creek Claims
Subrogation scoring for Duck Creek Claims through Anywhere APIs or scheduled extracts.
Overview
Ishqkala works with Duck Creek Claims whether you run it as Duck Creek OnDemand SaaS or self-hosted. Claim, party, file note and document data arrive through the Duck Creek Anywhere REST APIs your license exposes, or through a scheduled extract from your Duck Creek data store. Findings return as a File Note and a Task routed to your subrogation queue. Your team provisions access under your existing Duck Creek agreement; Ishqkala does not need partner-level credentials.
Use cases
- Catch commercial auto claims where a file note records the other fleet driver's admission of fault.
- Sweep closed property claims for contractor and appliance manufacturer liability before limitation dates run.
- Add subrogation scoring to Duck Creek Claims without waiting for a core configuration release.
- Feed a daily prioritized worklist to recovery units that work outside the claim system.
Architecture & data flow
How data moves between Duck Creek Claims and Ishqkala.
01
Change detection
Ishqkala polls the licensed claim APIs, or receives your extract, for claims with new notes, documents or status changes.
02
Claim retrieval
Claim detail, parties, file notes and documents are pulled with a read-scoped service account.
03
NLP and evidence extraction
Documents are OCR'd and liability signals are tied to the source note or page.
04
Scoring
Win probability, recoverable dollars and days to SOL combine into one priority score.
05
Return to Duck Creek
A File Note and Task post through the API, or arrive as a findings file your integration layer loads.
API data flow
Objects read and written.
| Object | Direction | What Ishqkala does with it |
|---|---|---|
| Claim | Read | Loss date, jurisdiction, loss cause, line of business and status. Jurisdiction and loss date set the limitation clock. |
| Parties | Read | Claimants, other drivers, property owners and vendors with their roles, used to identify the adverse party. |
| Coverage, reserves and payments | Read | Paid and reserved amounts by coverage, used to estimate recoverable dollars net of the deductible. |
| File Note | Read / write | Adjuster file notes are parsed in full. Ishqkala adds one File Note per finding with the liability rationale and quoted source text. |
| Document | Read | Police reports, estimates, photos and expert reports attached to the claim, retrieved for OCR and NLP. |
| Task | Write | A review Task for the subrogation queue, due ahead of the earliest SOL or notice-of-claim date. |
| Recoveries | Read | Existing subrogation or salvage recoveries, so claims with a booked recovery are suppressed. |
Security & data governance
Controls on this connection.
- Service account issued by your Duck Creek administrators, scoped to the operations Ishqkala uses.
- SFTP extracts with key-based authentication and PGP encryption, removed after ingestion.
- AES-256 at rest and TLS 1.3 in transit, in US AWS regions only.
- Zero model training on your claim files.
- Audit log of every read and write, available to your security and internal audit teams.
Setup timeline
From kickoff to first findings.
Week 1
Access and scope
Confirm OnDemand or self-hosted deployment, which Anywhere API services are licensed, and how write-back will run.
Weeks 2 to 3
Mapping and baseline
Map loss cause and line codes; run a closed-claim baseline from a historical extract.
Weeks 4 to 6
Write-back and UAT
Configure File Note and Task templates, routing and thresholds; test in non-production with your claims team.
Week 7
Production
Enable change detection and review the first two weeks of findings with subrogation leads.
FAQ
Duck Creek Claims integration FAQ
No. Ishqkala is not a certified Duck Creek partner integration. It uses the Anywhere API services and extracts already available under your license, with credentials your team issues and can revoke.
Both OnDemand and self-hosted Duck Creek Claims. OnDemand customers usually start with API change detection; self-hosted customers often begin with a nightly extract.
With API change detection, typically within 15 minutes of the note being saved. With nightly extracts, findings are ready at the start of the next business day.
No. Ishqkala reads financial data to estimate recoverable dollars but has no write access to reserves, payments or recoveries. Booking a recovery stays with your claim professionals.
More core claims systems
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.