Duck Creek Integration
Move products and claims operations off Duck Creek onto Regure, one product or claim cohort at a time. The integration keeps data in step while each scope moves, then Duck Creek is retired for it.
Move insurance operations from Duck Creek onto Regure in controlled phases
Duck Creek's cloud-native platform delivers policy administration, billing, and claims management in a unified SaaS environment. But like most core platforms, Duck Creek wasn't designed for document-heavy workflows — FNOL intake from multiple channels, ACORD form processing, field adjuster collaboration, or vendor document management.
Most Duck Creek customers build custom workflows within Duck Creek for document routing, or they bolt on separate document management systems that don't integrate cleanly. Adjusters switch between Duck Creek for claim data and external systems for documents, creating fragmented workflows and duplicate data entry.
Regure replaces that arrangement, Duck Creek included, product by product or claim cohort by cohort. Through Duck Creek's APIs, the policy and claim data each scope needs is exchanged while it is in transition, and documents arriving by email, upload or API are classified and extracted in Regure from day one.
Ownership is explicit for every phase. Duck Creek holds only the records not yet moved; each scope becomes Regure's once its acceptance criteria are met, and Duck Creek is retired for it. The integration is transition plumbing with an end date. See how switching to Regure works.
What syncs between Regure and Duck Creek
The integration supports the transition, nothing more. Ownership moves with each scope: until a product or claim cohort is accepted on Regure, Duck Creek holds it; after that, Regure does, and the sync for that scope stops.
From Regure to Duck Creek
- Documents from all sources (email, fax, upload, mobile, API)
- AI classification results (document type, confidence score, source)
- Extracted field data (ACORD form fields, FNOL details, loss amounts, claimant info)
- Document content (PDFs, images, forms) attached to policy and claim records
- Workflow completion events (submission review complete, FNOL intake complete)
When a broker submits an ACORD application or a claimant files an FNOL for a scope not yet moved, Regure's AI extracts the relevant fields and pushes them to the corresponding Duck Creek record, with the documents attached. No manual data entry while both systems are in play.
From Duck Creek to Regure
- Policy data (policy numbers, effective dates, coverage details, insured info)
- Claim data (claim numbers, status, loss dates, assignment info)
- Billing and payment status (premium due, payment received, settlement issued)
- Status updates (policy issued, claim approved, payment sent)
- Assignment changes (underwriter assignments, adjuster reassignments)
For records not yet moved, Duck Creek still holds policy and claim status during the transition. When an underwriter binds or an adjuster approves there, the status syncs to Regure immediately via webhooks, so field teams, vendors and policyholders see accurate status without needing Duck Creek access.
How to connect Regure to Duck Creek OnDemand
Regure's implementation team configures the integration. Your Duck Creek admin provides API credentials and approves field mappings.
API Connection
Your Duck Creek administrator creates an API service account with permissions for policy and claims modules. Regure connects via Duck Creek's OnDemand API using OAuth 2.0 authentication. API tokens refresh automatically to maintain continuous connectivity.
Field Mapping
Map extracted document fields to Duck Creek policy and claims fields. For example, ACORD 125 named insured maps to Duck Creek's insured name field, loss location maps to Duck Creek's loss address field. Support for custom fields and multi-entity structures (umbrella policies, complex commercial risks).
Webhook Subscriptions
Subscribe to Duck Creek events for real-time synchronization. When claim status changes or a policy is issued in Duck Creek, webhooks notify Regure instantly. No polling delays. Regure provides webhook endpoints and handles authentication.
Testing & Go-Live
Test with sample policies and claims in Duck Creek's staging environment. Upload documents to Regure, verify data flows to Duck Creek, and confirm webhooks trigger correctly. Move to production after UAT sign-off. Regure monitors integration health post-launch.
How carriers move off Duck Creek
Three phases, repeated per product or claim cohort. Each one ends with Duck Creek retired for that scope.
Phase 1: Submissions and documents
Submission and document intake move first. Brokers submit ACORD 125, 126, 130 and 140 applications via email or upload; Regure's AI extracts the fields (named insured, coverage limits, locations, loss history). For products not yet moved, the data is pushed to Duck Creek underwriting queues so nobody re-keys an ACORD form during the transition.
Certificate of insurance (ACORD 25) requests are processed automatically: insured details are taken from the policy record, the certificate is generated from Regure's template engine and delivered to the broker electronically, with issuance tracked for audit.
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, and email attachments sent to claims@ route to the correct claim on Regure automatically.
FNOL forms submitted through policyholder portals extract loss details (date, location, description, parties involved) and create the claim on Regure, with assignment rules applied immediately. For claim cohorts not yet moved, the claim is created in Duck Creek instead until they do.
Phase 3: Retire Duck Creek for it
Once a scope's acceptance criteria are met and signed, the sync for that scope is switched off and Duck Creek is retired for it. Field adjusters capture photos, statements and damage assessments on the same record, with GPS coordinates and timestamps, without Duck Creek mobile licences.
Secure messaging between field teams and office staff replaces unsecured SMS and email, and vendors (contractors, appraisers, medical providers) upload documents to Regure portals, all on one record with a complete audit trail.
Common questions about the Duck Creek integration
Is Duck Creek required to use Regure?
No. Regure runs as the operating platform without Duck Creek. This integration exists for organisations moving products or claims operations off Duck Creek: it keeps policy and claim data in step during the transition, and is switched off for each scope once Duck Creek is retired for it.
What gets automated with the Duck Creek integration?
During the transition: document classification (police reports, ACORD forms, estimates, photos), data extraction into Duck Creek fields for records not yet moved, document routing to the correct policy or claim, and workflow triggers. As each product or claim cohort moves, that work runs on Regure end to end and the Duck Creek side of it is retired.
Can we customize workflows in Regure that trigger Duck Creek actions?
Yes, for scopes still in transition. Regure's workflow engine can trigger Duck Creek API actions when a workflow completes, for example creating a quote in Duck Creek for a product that has not moved yet. Once the product moves, quoting, rating and binding run on Regure and the trigger is retired. Workflow rules are configurable without coding.
How does this integrate with Duck Creek's cloud updates?
Regure uses Duck Creek's published OnDemand API, which is version-stable across Duck Creek's quarterly cloud releases. When Duck Creek releases new API versions, Regure's engineering team tests compatibility and updates the integration if needed — typically with zero downtime. You don't need to update Regure when Duck Creek releases new features.
Learn more about Regure and Duck Creek
Regure vs. Duck Creek
Where Regure replaces Duck Creek, how the platforms differ, and what a phased move looks like.
Solutions for Carriers
How insurance carriers use Regure for submission automation, claims intake, and team collaboration across all lines of business.
How Switching Works
The steps from first working session to a retired legacy workflow, one product at a time.
Related Integrations
Five things Duck Creek was never built to do
Duck Creek handles Claims management, Policy administration, Rating 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.
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 statementsAI 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 reportCompliance 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 correspondenceRenewal 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 reportsClaims 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 Duck Creek 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 Duck Creek?
Book a session with your Duck Creek environment. We'll map the first product or claim cohort to move, and show the transition integration and field mapping.