Case study · Insurance

ČSOB Pojišťovna

Context

ČSOB Pojišťovna decided to replace its core insurance software with a new Guidewire solution — ClaimCenter, PolicyCenter, and BillingCenter. Our goal was to deliver the new FNOL (First Notice of Loss) portal in close cooperation with the insurer's own teams: a portal that integrates with the Guidewire platform and with every other system participating in the FNOL process.

JavaReactSpring

FNOL portal · system map

Our part · FNOL portal
React frontendFNOL portal
Clustered environment
  • High availability
  • Load distribution
  • Smooth scaling
FNOL backend
CMS module
Java Spring / Spring Boot
Integration layer
GuidewireDelivered by another company
  • ClaimCenter
  • PolicyCenter
  • BillingCenter
Internal customer systems
OAuth serverAuthentication · authorization · role-based access
0204
Problem definition and goal

The original FNOL portal was built on Liferay and tightly integrated with the legacy core insurance system. Once the customer decided to replace the core with Guidewire — delivered by another company — the FNOL portal had to be replaced as well. The new portal needed to integrate with the Guidewire solution and with the other systems that participate in the First Notice of Loss process, while meeting the strict quality and security expectations of an insurance environment.

Industry
Insurance
Competencies
Application integrationAgile developmentHigh availabilitySecurity & access control
Technologies
JavaReactSpringSpring BootREST/SOAP

Challenges

Delivering a portal into the middle of a running core-system replacement brought a specific set of challenges:

  1. Many participants

    The project involved a large number of stakeholders from multiple external companies and internal teams and departments, which significantly increased the complexity of communication and coordination.

  2. Integrations to unfinished systems

    Several integrations had to be built against a backend that was still under development — shifting specifications, unstable interfaces, and frequent changes in behavior. We implemented flexible integration logic, maintained close cooperation with the backend teams, and continuously adapted to the evolving APIs.

  3. High quality requirements

    The customer set very high expectations for usability, performance, and overall product quality. We invested heavily in automated tests and code reviews to make sure the solution met them.

  4. High security requirements

    Because the system handles sensitive insurance data, it had to meet strict security standards: secure communication, strict authentication rules, and proper role-based access control.

Solutions

A modern, scalable architecture

The solution combines a React frontend with a Java Spring / Spring Boot backend. The application runs in a clustered environment for high availability, load distribution, and smooth scaling under increased traffic.

  • React frontend
  • FNOL backend
  • Clustered environment

Two components, one platform

The portal consists of two main components — the FNOL backend and a CMS module — working together as a unified, flexible platform for managing the entire First Notice of Loss process.

  • FNOL backend
  • CMS module

A robust integration layer

The system integrates with the Guidewire platform, multiple internal customer systems, and the OAuth server used for authentication and authorization. Thanks to the modular design, the solution handles complex business workflows while remaining secure, maintainable, and ready for further expansion.

  • Guidewire
  • Internal customer systems
  • OAuth server

Key features

  • FNOL process management
  • Guidewire integration
  • CMS module
  • High-availability clustering
  • OAuth authentication and role-based access
Is this for you?

Your core system is changing. Your customer channels can’t stop.

We delivered ČSOB Pojišťovna’s new FNOL portal while its core insurance system moved to Guidewire. The same challenge appears wherever a customer-facing channel has to keep working on top of a core system that is being replaced.

  • Insurance
  • Banking
  • Utilities and telecom billing
  • Any core-system replacement
Sounds familiar?

0 of 5 sound familiar

How we would start

  1. Map every integrationThe core platform, internal systems and authentication, and who owns each one.
  2. Build for changeFlexible integration logic and close work with the backend teams while their interfaces evolve.
  3. Guard quality and securityAutomated tests, code reviews, OAuth and role-based access from day one.
Replacing your core system?

Tell us
about your project

Describe what you want to build. We’ll get back to you within 24 hours with a proposal for next steps.

Need more info?

Reach out directly to our project managers, who will be happy to tell you more.

Romana Kovalová