Guidewire Integration
Move claims operations off Guidewire ClaimCenter onto Regure, line by line or claim cohort by cohort. The integration keeps claims data in step while each scope moves, then ClaimCenter is retired for it.
Move claims operations from Guidewire onto Regure in controlled phases
Guidewire ClaimCenter is the industry-leading core claims platform for managing policy data, reserves, payments, and regulatory reporting. But ClaimCenter wasn't designed for document-heavy workflows or real-time team collaboration across field adjusters, desk examiners, and third-party vendors.
Most Guidewire customers bolt on third-party document management systems, email plugins, and collaboration tools — creating fragmented workflows where adjusters switch between 4-5 systems to process a single claim. Documents live in one system, claim data lives in Guidewire, and team communication happens over email.
Regure replaces that stack, ClaimCenter included, in phases. Intake, documents and triage usually move first; then the claim record, reserves, payments and approvals move line by line or cohort by cohort. While a scope is in transition, the integration exchanges the data ClaimCenter still needs for the claims not yet moved. When the scope is accepted, ClaimCenter is retired for it and that part of the integration is switched off.
The integration is transition plumbing with an end date, not a permanent split of responsibilities. See how switching to Regure works for the steps and acceptance criteria.
What data flows between Regure and Guidewire ClaimCenter
Integration architecture, configured and validated during your implementation. Ownership moves with each scope: until a line is accepted on Regure, ClaimCenter still holds its claim lifecycle and financials; after that, Regure does, and the sync for that line stops.
Data flowing from Regure to ClaimCenter
- Documents uploaded to Regure (emails, faxes, mobile uploads, API submissions)
- Document metadata (type, source, timestamp, confidence score)
- Extracted field data (claimant names, policy numbers, loss dates, amounts, vehicle VINs, injury descriptions)
- Document content (PDFs, images, forms) attached to claim records in ClaimCenter
- Workflow status and completion notifications (e.g., FNOL workflow completed, all required docs received)
When a document arrives in Regure via email or upload, the AI classification engine identifies the document type (police report, medical record, repair estimate, etc.) and extracts key fields. This extracted data pushes directly to the corresponding fields in ClaimCenter — no manual data entry required. The full document attaches to the claim record so adjusters can review source documents without leaving ClaimCenter.
Data flowing from ClaimCenter to Regure
- Claim status updates (opened, pending review, approved, closed)
- Policy data (policy number, effective dates, coverage limits, deductibles)
- Reserve and payment data (reserve amounts, payment status, settlement amounts)
- Assignment changes (adjuster reassignments, vendor assignments)
- Claim notes and activity logs (adjusters' notes, diary entries, status changes)
For claims not yet moved, ClaimCenter still holds claim status and policy data during the transition. When an adjuster updates a claim status or changes a reserve there, the change syncs to Regure so field teams, vendors and claimants see accurate status. Webhooks notify Regure immediately when claim data changes in ClaimCenter, eliminating sync delays.
How to configure the Guidewire ClaimCenter integration
Regure's professional services team handles the initial setup. Your IT team provides API credentials and approves field mappings. Most integrations go live in 1-2 weeks.
API Authentication
Your Guidewire administrator creates a service account in ClaimCenter with API access permissions. Regure connects via OAuth 2.0 authentication with token refresh for continuous access. No custom ClaimCenter plugins or code required.
Field Mapping
Map Regure document fields to ClaimCenter claim fields (e.g., extracted loss date maps to ClaimCenter's LossDate field, extracted claimant name maps to ClaimContact). Custom fields in ClaimCenter are fully supported. Mapping configuration is stored in Regure and can be updated without ClaimCenter changes.
Webhook Configuration
Configure ClaimCenter webhooks to notify Regure when claim status changes, assignments update, or notes are added. Webhooks ensure real-time synchronization — no polling delays. Regure provides webhook endpoints and authentication credentials during setup.
Testing & Validation
Test the integration with sample claims in ClaimCenter's test environment. Upload documents to Regure, verify data populates in ClaimCenter fields, and confirm document attachments appear in claim records. Validate webhooks fire correctly when claim status changes. Move to production after testing sign-off.
How carriers move claims off ClaimCenter
Three phases, repeated per line or claim cohort. Each one ends with ClaimCenter retired for that scope.
Phase 1: Intake and documents
Intake moves first. Emails sent to claims@ file to the correct claim by claim number or policy number. FNOL documents submitted through agent portals are extracted (claimant details, loss location, injury descriptions) without manual data entry, and for claims still in ClaimCenter the extracted data is pushed into its fields.
Search across all documents by claim number, policy number, claimant name, or document type. While both systems are in play, adjusters reach the same documents from ClaimCenter through links to Regure's document viewer.
Phase 2: The claim itself
Line by line, the claim record, reserves, payments, approvals and authority limits move onto Regure. Field adjusters capture photos, record statements and message desk examiners on the same record, and secure messaging between adjusters, vendors and claimants replaces unsecured email threads and SMS.
Vendors (body shops, contractors, medical providers) access a secure portal to upload estimates, invoices and progress photos without needing ClaimCenter licences, with audit trails of who uploaded what and when.
Phase 3: Retire ClaimCenter for it
Once a line's acceptance criteria are met and signed, the sync for that line is switched off and ClaimCenter 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 version history tracks all changes to claim documents with rollback capability. Retention policies ensure documents are preserved for regulatory timelines (7 years for most states) with automated deletion after retention expires.
Common questions about the Guidewire integration
Does Regure replace Guidewire ClaimCenter?
Yes, in phases. Claims operations move onto Regure line by line or claim cohort by cohort. During the transition, ClaimCenter holds the claims not yet moved and exchanges policy, reserve or payment data with Regure as required. Once each scope is accepted, ClaimCenter is retired for it.
What data syncs between Regure and ClaimCenter?
Documents and extracted data flow from Regure to ClaimCenter (police reports, medical records, photos, repair estimates with extracted fields). Claim status, policy data, and assignment changes flow from ClaimCenter to Regure. The integration is bi-directional with real-time sync via webhooks. You control which fields map between systems during configuration.
How long does it take to set up the integration?
Most Guidewire integrations go live in 1-2 weeks. Regure's professional services team handles API configuration, field mapping, webhook setup, and testing. Your IT team provides ClaimCenter API credentials and approves field mappings. Complex custom field mappings or multi-environment rollouts may take 3-4 weeks.
Who manages the integration after it's set up?
Regure handles the initial setup and configuration. Your IT team maintains ClaimCenter API credentials and can update field mappings as needed. Regure's support team monitors integration health, handles API version updates, and provides troubleshooting. No ongoing developer resources required on your side after go-live.
Learn more about Regure and Guidewire
Regure vs. Guidewire
Where Regure replaces ClaimCenter, how the platforms differ, and what a phased move looks like.
Solutions for Carriers
See how insurance carriers use Regure for claims automation, FNOL processing, and team collaboration across personal and commercial lines.
How Switching Works
The steps from first working session to a retired legacy workflow, one line at a time.
Related Integrations
Five things Guidewire was never built to do
Guidewire handles Policy administration, Claims management, Billing 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 Guidewire 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 claims off Guidewire ClaimCenter?
Book a technical session with your ClaimCenter environment. We'll walk through the first line to move, the transition integration and field mapping, and answer your IT team's questions.