Your core system stays

Claim360 connects to the system that is already there and writes back. No rip-and-replace, no two-year programme. The core system stays in the lead.

The agents do the paperwork. The people do the contact.

Book a technical walkthrough
App visualApp visualApp visual
Market

Income protection insurers

Core systems for income protection and disability.

  • NL · BE

    Vendor: Keylane

    Connects via the Claim360 API

  • NL · BE

    Vendor: Novulo

    Connects via the Claim360 API

  • NL · BE

    Connects via the Claim360 API

  • NL · BE

    Connects via the Claim360 API

  • NL · BE

    Vendor: Guidewire

    Connects via the Claim360 API

  • NL · BE

    Vendor: Anva

    Connects via the Claim360 API

Is your system not listed? Claim360 is API-first and also connects to in-house and other core systems.

Get in touch

Platform or chain partner? This is how you connect.

Platforms and core systems Chain partners

Three layers, the core system at the bottom

Claim360 is the layer directly above your core system: orchestration and workflow automation in one. The self-service portal runs on it, and AI on top. The core system remains the system of record.

The build

AI

  • the user's permissions
  • every question logged

Your model, a partner's or our Claimassistent, through Claim360 as the gateway. Reads, checks and prepares; the handler decides.

Self-service portal

  • fields instead of attachments
  • per role

Azori, in your brand. Claimant, solicitor, chain partners and handler in the same file; everyone sees what their role needs. Runs on Claim360.

Claim360: orchestration and workflow automation

  • deadlines, tasks, payments
  • roles and permissions
  • direct API per chain partner
  • writing back to the core

This is where the intelligence sits. Deadlines, tasks, documents and payments run by themselves; roles, permissions and triggers across the core system; what has to go back, goes back to the core.

Your core system

Keylane Axon, Novulo, CCS, UBench, Guidewire and Anva or another: it stays. Claim360 connects to it and writes back.

API-first. Every chain partner connects through a direct API on Claim360, or Claim360 connects to that party.

Four flows between Claim360 and the core system

In Claim360 the file is the same truth for all parties; what the core system needs goes back without retyping.

  • File and parties

    The file with its heads of damage and the parties around it, with permissions per role. The core system remains the system of record.

  • Documents

    Every document on the head of damage it belongs to, with version history. Reports from chain partners land straight in the right file.

  • Payments and reserves

    Interim payments, balance and reserve per item go back to the core system. Nothing entered twice.

  • Status and deadlines

    Status, deadlines and tasks are in Claim360 and are the same truth for handler, chain partner and claimant.

How the integration works

  • Direct API

    Every chain partner connects through a direct API on Claim360, or Claim360 connects to that party.

  • Permissions and logging

    Permissions per role and per person. Access is logged, traceable and revocable at once.

  • Writing back to the core

    Claim360 writes back to the core system. Nothing entered twice.

  • Hybrid working

    Work fully in Claim360, or hybrid next to the core system. The core system stays.

Frequently asked questions from IT and architecture

Is your question not here?

Ask your question through the contact page

Do we have to replace our core system?

No. Claim360 is an orchestration layer that runs on existing systems. We connect through APIs to legacy policy systems, claims administrations and others. Work fully in Claim360, or hybrid next to it: the core system stays.

How do chain partners connect?

Every chain partner connects through a direct API on Claim360, or Claim360 connects to that party. Connecting once applies to every insurer that runs Claim360; see the page for chain partners.

How does an AI model get access?

Through Claim360 as the gateway, with the user's permissions: a headless API that gives exactly what someone may also see in the portal, and every question logged. The model changes, the layer underneath stays; suppliers of AI models can reach us through the contact page.

Where is the data and who sees what?

In the Netherlands, within the EU: data sovereignty under European law. Permissions per role and per person, access logged and revocable at once, audit trail per file and per automated action.

See how Claim360 connects to your core system?

Book a demo or a strategy session with our team. We usually respond within one working day.

Request a demo