Core claims systems integration
Ishqkala + Majesco Claims for P&C
Subrogation scoring for Majesco Claims for P&C through scheduled extracts or APIs.
Overview
Majesco Claims for P&C handles FNOL through settlement on a rules-based engine, as part of Majesco's P&C core suite, in the cloud or hosted by the carrier. Because Majesco API access varies by implementation, Ishqkala starts with a customer-scheduled extract of claims, notes and documents over SFTP, and moves to API calls where your implementation exposes them. Findings return as a findings file or, with API access, a claim note and task your Majesco team controls.
Use cases
- Run a 24-month closed-claim sweep for a regional carrier on Majesco without new core development.
- Score new auto collision claims overnight so subrogation units start each day with a ranked list.
- Find water and fire losses where a contractor, landlord or product manufacturer caused the damage.
- Track SOL dates for open opportunities outside the core system until a recovery is booked.
Architecture & data flow
How data moves between Majesco Claims for P&C and Ishqkala.
01
Scheduled extract
Your team schedules a nightly delta extract from the claims database or reporting layer to a Ishqkala SFTP endpoint.
02
Ingestion
Ishqkala validates the file against the agreed layout, decrypts it and loads it into your isolated tenant.
03
NLP and scoring
Notes and documents are read for liability signals, then scored on recoverable dollars, win probability and days to SOL.
04
Findings return
A findings file with claim number, score, rationale and SOL date returns over SFTP, or posts through the API where enabled.
API data flow
Objects read and written.
| Object | Direction | What Ishqkala does with it |
|---|---|---|
| Claim | Read | Loss date, loss state, cause of loss, line of business and status, used to set the limitation clock. |
| Claimants and involved parties | Read | Parties and roles, used to identify the adverse party and any known adverse carrier. |
| Claim notes | Read / write | Adjuster notes parsed in full; with API access, Ishqkala adds a finding note with cited text. |
| Documents | Read | Police reports, estimates, photos and expert reports included in the extract or retrieved by reference. |
| Reserves and payments | Read | Paid and reserved amounts by coverage for the recoverable estimate. |
| Recovery entries | Read | Existing subrogation or salvage entries where your configuration records them, so duplicates are suppressed. |
| Task | Write | A review task for the subrogation queue, through the API or loaded from the findings file. |
Security & data governance
Controls on this connection.
- SFTP with key-based authentication and PGP-encrypted files; landing files removed after ingestion.
- Where APIs are used, a dedicated service account limited to the claim, note, document and task operations Ishqkala needs.
- AES-256 at rest and TLS 1.3 in transit, in US AWS regions only.
- Zero model training on your claim files, with a HIPAA BAA for bodily injury documents.
- Full audit trail of every file received and every finding returned.
Setup timeline
From kickoff to first findings.
Week 1
Extract specification
Agree the extract layout, delta logic and schedule with your Majesco team or systems integrator.
Weeks 2 to 3
First extract and mapping
Load 24 months of history, map loss causes and lines, and run the closed-claim baseline.
Weeks 4 to 5
Findings review
Subrogation leads review scored findings and set thresholds and routing.
Week 6
Production schedule
Nightly deltas go live; API write-back is added later if your implementation exposes it.
FAQ
Majesco Claims for P&C integration FAQ
No. Your team or integrator schedules an extract from data you already hold. Ishqkala claims no Majesco partnership and needs no product change.
Findings are ready the morning after the extract runs. For most subrogation work that is soon enough, and FNOL triggers can move to near real time once API access is available.
Claim number, loss date, loss state, cause of loss, line, paid amounts, adjuster notes and document references. Additional fields such as party roles improve adverse party identification.
No. Ishqkala reads financial data to size the recovery but never writes reserves, payments or recoveries.
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.