Skip to content
Integration

Sapiens Integration

Move products and claims operations off Sapiens onto Regure, one product or claim cohort at a time. The integration keeps data in step while each scope moves, then Sapiens is retired for it.

Move insurance operations from Sapiens onto Regure in controlled phases

Sapiens provides enterprise-grade policy administration, claims management, billing, and reinsurance platforms for P&C, life, and pension carriers globally. Sapiens CoreSuite and IDC deliver scalable, configurable core systems for insurers processing millions of policies and claims annually.

But like most core platforms, Sapiens wasn't designed for document-heavy operations — broker submission intake, ACORD form processing, claims document automation, or multi-party collaboration workflows. Most Sapiens customers build custom document handling within Sapiens (expensive to maintain) or use standalone document management systems that don't integrate cleanly.

Regure replaces that arrangement, Sapiens included, product by product or claim cohort by cohort. Through Sapiens' REST APIs, the policy and claim data each scope needs is exchanged while it is in transition, and documents are classified and extracted in Regure from day one. Each scope becomes Regure's once its acceptance criteria are met, and Sapiens is retired for it.

The integration is transition plumbing with an end date, not a permanent split of responsibilities. The destination is one platform for underwriters, adjusters and operations teams. See how switching to Regure works.

REST APINative integration with Sapiens IDC/CoreSuite REST APIs
Real-Time SyncWebhooks for instant document and status updates between systems
2-3 Week SetupAPI configuration, field mapping, and go-live in 2-3 weeks

What syncs between Regure and Sapiens

Ownership moves with each scope. Until a product or claim cohort is accepted on Regure, Sapiens holds its policy and claim lifecycle; after that, Regure does, and the sync for that scope stops.

From Regure to Sapiens

  • Documents from all channels (broker portals, email, upload, mobile, API)
  • AI classification results (document type, confidence scores, metadata)
  • Extracted structured data (ACORD fields, loss details, submission data, claim information)
  • Document content (PDFs, images, forms) attached to policy and claim records
  • Workflow completion events (submission complete, FNOL intake complete, underwriting review ready)

When a broker submits a new business application or a claimant files an FNOL for a scope not yet moved, Regure's AI extracts the relevant fields and pushes them into the corresponding Sapiens module, so nothing is transcribed by hand while both systems are in play.

From Sapiens to Regure

  • Policy data (policy numbers, effective dates, coverage details, insured information)
  • Claim data (claim numbers, status, loss dates, assignment, reserves)
  • Underwriting decisions (quote approved, bound, declined, pending additional info)
  • Status updates (policy issued, claim approved, payment authorized)
  • Assignment and routing changes (underwriter reassignments, adjuster changes)

For records not yet moved, Sapiens still holds policy and claim decisions during the transition. When an underwriter binds or an adjuster approves there, the status syncs to Regure immediately, so brokers, field teams and claimants see accurate status without needing Sapiens licences or portal access.

How to connect Regure to Sapiens platforms

Regure's implementation team configures the API integration. Your Sapiens administrator provides credentials and approves data mappings.

1

API Authentication

Your Sapiens administrator creates an API service account with read/write permissions for policy and claims modules (IDC, CoreSuite, Decision, or Reinsurance). Regure connects via Sapiens REST APIs using OAuth 2.0 or API key authentication depending on your Sapiens version.

2

Field Mapping

Map Regure document fields to Sapiens entity fields. For example, extracted loss date maps to claim loss date, extracted named insured maps to policy holder name. Sapiens custom fields and complex entity structures (multi-location commercial risks) are fully supported. Field mappings are configurable without Sapiens changes.

3

Webhook Configuration

Configure Sapiens webhooks to notify Regure when policy status changes, claims update, or underwriting decisions occur. Real-time webhooks eliminate polling delays. Regure provides webhook endpoints and handles authentication and retry logic for failed deliveries.

4

Testing & Go-Live

Test in Sapiens staging environment with sample policies and claims. Upload documents to Regure, verify data flows to Sapiens, confirm document attachments appear in Sapiens records. Validate webhooks trigger correctly. Production rollout after UAT approval. Regure monitors integration health post-launch.

How carriers move off Sapiens

Three phases, repeated per product or claim cohort. Each one ends with Sapiens retired for that scope.

Phase 1: Submissions and FNOL

Intake moves first. Broker submissions arrive via email, broker portal or API, and Regure's AI classifies them by line of business and extracts ACORD or proprietary form data. FNOL from any channel is extracted the same way. For products and claim cohorts not yet moved, the extracted data populates Sapiens so nothing is re-keyed during the transition.

Missing information is flagged automatically, and routing rules (for example, high-value accounts to senior underwriters) apply on arrival, so the intake workflow is already running on Regure when the product itself moves.

No re-keying from ACORD 125, 126, 130 or 140 forms

Phase 2: Products and claims move

Product by product, rating, quoting, binding, issuance, endorsements and renewals move onto Regure, renewal-led or with the in-force book. Claim cohorts follow: the claim record, reserves, payments and approvals move onto Regure, with assignment rules routing claims by line of business, complexity or geography.

Documents (photos, police reports, initial estimates) sit on the same claim record, so adjusters start investigating immediately. Data mapping, reconciliation checks and the cutover date for each scope are part of the configuration scope.

Policy, claims and documents on one record for each scope that moves

Phase 3: Retire Sapiens for it

Once a scope's acceptance criteria are met and signed, the sync for that scope is switched off and Sapiens is retired for it. From then on, immutable audit logs on Regure capture every action, with user identity, timestamp, IP address and action taken, exportable for regulatory reviews or litigation discovery.

Document retention policies apply jurisdictional requirements (7-year retention for most P&C, longer for certain lines), with automated deletion after retention expires and version history on every document. Archive-only history from Sapiens can sit in a governed, searchable retention store.

One platform, and one fewer core to license and maintain

Common questions about the Sapiens integration

Which Sapiens products does Regure integrate with?

Regure integrates with Sapiens CoreSuite (policy administration and claims), IDC (Intelligent Underwriting and Claims), Decision (underwriting decision engine), and Reinsurance platforms. The integration uses Sapiens REST APIs available across these products. Specific field mappings are customized based on which Sapiens modules you're using and your configuration.

Is this a certified Sapiens integration?

No — and we will say so plainly rather than imply otherwise. The integration is built on Sapiens' published REST APIs, which are version-stable and documented, so it does not depend on a partner agreement to work. Formal listing through Sapiens' partner programme is something we intend to pursue; until it is granted, treat this as an API integration rather than a certified one.

What's the setup timeline for the Sapiens integration?

Standard configurations (policy admin and claims with common field mappings) typically go live in 2-3 weeks. Complex configurations with extensive custom fields, multi-entity structures, or multiple Sapiens modules may take 4-6 weeks. Regure's professional services team handles the heavy lifting — your IT team provides credentials and approves mappings.

Can we use Regure with Sapiens cloud or on-premise deployments?

Both. Regure integrates with Sapiens cloud (SaaS) deployments via public APIs and with on-premise Sapiens installations via VPN or API gateway. For on-premise deployments, your network team provides secure API access (typically via VPN tunnel or reverse proxy). Cloud deployments connect directly via HTTPS with OAuth authentication.

Where the gap is

Five things Sapiens was never built to do

Sapiens handles Policy management, Claims handling, Reinsurance and does it well. These are the workflows that fall outside that scope — the ones that end up in inboxes and spreadsheets beside it. They are usually the first work to move onto Regure, and the rest of the operation follows, one scope at a time.

  1. AI Subrogation Detection Agent

    The gap. Adjusters handling high claim volumes miss subrogation opportunities because manual review of every police report, incident narrative, and medical record for third-party fault indicators is impossible at scale. Industry estimates suggest 10-15% of subrogation opportunities are not pursued due to identification failures.

    What Regure does. Regure's AI reads every incoming claim document — police reports, FNOL narratives, witness statements, and incident photos — and flags subrogation indicators automatically. The agent identifies third-party involvement, potential product liability, and Workers' Comp employer negligence, routing identified opportunities to the subrogation unit with supporting evidence.

    ReadsPolice reportFNOL narrativeMedical examination reportContractor inspection reportWitness statements
  2. AI Fraud Triage Agent

    The gap. Claims fraud costs the US insurance industry $80B annually. SIU teams cannot review every claim — manual referral rates of 1-3% mean the majority of fraudulent claims are paid without investigation. Document-level fraud signals (staged accident indicators, provider billing anomalies, claim inflation patterns) are invisible without AI analysis.

    What Regure does. Regure analyzes every claim document against a fraud signal library: medical provider billing history, accident scenario consistency, claimant claim frequency, contractor pricing benchmarks, and document metadata anomalies. Claims exceeding configurable risk thresholds are automatically routed to SIU with an evidence package.

    ReadsCMS-1500UB-04Police reportContractor invoiceFNOLIME report
  3. Compliance Automation

    The gap. Core insurance platforms generate transaction records but not the structured evidence that regulators require. FCA Consumer Duty evidence, DORA ICT incident logs, SAMA Cyber Framework controls, and US state market conduct examination responses require additional compilation effort that falls on compliance teams.

    What Regure does. Regure turns the operation's transaction data into the evidence regulators require. Every document processed and decision made is automatically logged with cryptographic tamper-evidence. Regure generates structured evidence packages — FCA Consumer Duty outcome reports, DORA incident response logs, state examination responses — from operational data, eliminating manual compilation.

    ReadsClaims decision recordsCustomer communication logsFNOL to settlement timelinePricing justification documentsRegulatory correspondence
  4. Renewal Intelligence

    The gap. Renewal teams in core systems see transaction history but lack the unstructured signal in claim narratives, broker communications, and loss survey reports that predict renewal outcomes. At-risk accounts are identified too late — typically at the 30-day mark when competitors have already presented alternatives.

    What Regure does. Regure enriches renewal data with signals extracted from document workflows: claim frequency patterns, broker communication sentiment, loss control recommendation compliance, and market submission activity. Accounts with early deterioration signals are flagged 90+ days out for proactive retention actions.

    ReadsLoss run reportsLoss control surveyRenewal applicationBroker correspondenceClaims development reports
  5. Claims Leakage Prevention

    The gap. Claims leakage — overpayment, coverage misapplication, missed recoveries, and process failures — costs insurers 4-10% of total claims spend. Core systems track payments but can't identify where and why leakage occurs across the document-heavy claims process.

    What Regure does. Regure monitors every document touchpoint in the claims lifecycle against carrier-specific leakage indicators: contractor invoice vs. benchmark pricing, medical billing code consistency, reserve adequacy vs. document evidence, settlement authority adherence, and subrogation opportunity compliance. Leakage alerts are surfaced in real-time to supervisors.

    ReadsContractor invoiceProperty damage estimateMedical bills (CMS-1500, UB-04)Reserve documentationSettlement authorization

How the connection to Sapiens is actually configured is decided in implementation against the version you run — see how configuration works. For the document machinery underneath all five, see document processing.

Ready to move off Sapiens?

Book a technical session with your Sapiens environment. We'll map the first product or claim cohort to move, and show the transition integration and field mapping.

Book a working session