Skip to content

Insurance: Cross Entity Claims Settlement

Allianz adopts Luthers platform for Deep Process Automation at scale to automate the complex and critical process for motor insurance cross-entity claims settlement.

Insurance: Cross Entity Claims Settlement

1. Executive Summary

Allianz, a leading global financial services company headquartered in Munich, with over 125 million customers globally, is the largest insurer in the world, employing over 157,000 people. Allianz offers a variety of types of insurance, including life, property & casualty, credit, and specialist corporate insurance. As part of the p&c insurance offerings, Allianz provides motor insurance, and serves a large number of cross-department customers. The cross-department claims settlement process is vital to Allianz operations, and involves a handling operating entity (the OE where the incident occurred) processing the customer’s claim, providing settlement to the customer, then invoicing the originating operating entity (the OE that issued the policy) who pays the invoice and closes the claim.

Allianz Annual Stats

However, the process operates across siloed and separate participants, who change their operations as functions and technology change. Consequently, other teams are operating on constantly changing information, resulting in disjointed, inconsistent end-to-end operations which lead to delays and errors. Disjointed process operations require monitoring and reconciliation to correct errors, increasing operating costs. Using Luther’s Deep Process Automation technology to streamline cross-department claims settlement, Allianz was able to reduce the estimated cost of the process by 80%. The estimated settlement process time was reduced from 4 hours to just 0.8 hours.

Allianz Process Results

Allianz operates the cross-department claims settlement process as part of the claims value chain. This process operates across 5 teams & 8 software systems. To operate the process end-to-end, each system performs the same cycle of steps; i) send data & info to the System, ii) receive response from System, iii) compute & validate response, iv) share & store execution of step, v) evaluate & initiate next step. For reliable operations, all teams & systems involved should operate the same end-to-end Process. They often don’t! Enterprises attempt to i) set up local connectors between directly linked systems in the process, ii) Develop local operations scripts to manage the process. Both bespoke connectors and operations scripts require regular updates as teams, process operations, and systems evolve. These updates are reactive and localized, without fully considering the entire process. This leads to operational & technical challenges, which make process operations unreliable. The opportunity is providing a platform to reliably operate the end-to-end process, across all teams & systems involved.

These teams and participants are: the Handling Claims Team, the Originating Claims Team, the Handling Finance Team, the Originating Finance Team, and the Originating Payments Team. These systems are: Oracle Database, Equifax, Guidewire Claimcenter, MySQL, Basware, Microsoft Sharepoint, DocMagic, and Allianz Business System.

Silo cause Ops problems

Traditional solutions to end-to-end process operations are unreliable & expensive. Enterprise Operations are generally function-first, meaning they continue to improve functions & their systems in isolation. Processes are considered secondary. The thinking is that if we have great functions & systems, the business can operate any process! Luther's platform is designed process-first, & primarily focuses on end-to-end processes.

Reliable end-to-end process operations include consistent operation, and great functions & systems. Traditionally enterprises use bespoke connectors & local operations scripts for process operations, which are fragmented, siloed, and change separately, and so are ineffective for reliable process operations. To remedy this, enterprises use automation tools. However they are ineffective at end-to-end process operations, due to their limited scope and scale, and stitching them together also doesn’t solve the problem.

Luther’s unique value for reliable end-to-end Process Operations is providing i) standard connectivity & ii) a common operations script, across all teams & software systems. Luther’s platform vertically integrates; i) distributed system technology ii) optimal resource allocation & management, iii) real time event ordering & streaming, iv) deterministic event processing & execution, for reliable end-to-end process operations. Luther’s platform does this by i) connecting systems to standard platform nodes, rather than to each other, and ii) teams & systems can change the common operations script but all teams & systems have to know & agree to the change, so all teams & systems involved operate the same end-to-end Process all the time!

To implement the platform; i) Luther’s team mapped the Process, ii) identified teams & software systems in the process, iii) allocated nodes (servers) to teams, iv) connected nodes to systems, v) set up the Platform on the nodes, vi) Allianz’s team along with Luther’s team developed the  Common Operations Script (code) for Process Operations, vii) the process went Live. The process can now be completed in less than an hour and operational costs have been reduced by 80%.

Beyond the commercial results, this led to operational benefits in production, i) reliable operations across the end-to-end process & over time, ii) 5X smaller Ops teams, iii) real-time monitoring, iv) enforced compliance checks, v) real-time and consistent updates across all teams, vi) reduction of reconciliation. Also, technical benefits during development, i) standard dev. process so developers can focus on operations, ii) 5X smaller Dev teams, iii) standard process connectors, iv) automated infrastructure and connectors setup, v) real-time and consistent updates with the rest of operations. Ultimately, this leads to reliable end-to-end process operations!

2. The Process

Cross-Department Claims Settlement process

A key aspect of Allianz’s operations is Claims. This value stream involves cross-department claims settlement among other processes.

Value stream figure

For operational reliability, financial efficiency, regulatory reporting, and to avoid delays which adversely impact customer experience, each step of the settlement process must be operated, documented, validated and completed effectively and consistently. To complete the settlement process, Allianz works with customers and other OE’s Allianz teams.

Allianz Process
Cross-Department Claims Settlement process, teams & systems involved
Process Stats

The cross-department claims settlement process has these steps: i) the Handling Claims Team retrieve the claim from the claims database, ii) the Handling Claims Team processes the claim and sends it to the Originating Claims Team for review and approval, iii) the Originating Claims Team reviews the invoice, iv) the Originating Claims Team approves the invoice, v) the Handling Finance Team generate an invoice for the OE, to cover costs that were incurred by the handling entity while processing the claim, along with a fee for the handling of the claim, vi) the Originating Finance Team review and approves the invoice, vii) the Originating Finance Team sends the invoice to the Originating Payments Team to make the payment, viii) the Originating Payments Team makes the payment and completes the claims settlement process.

Process Operations

Different teams have different operations, rules and governance and they also utilize and operate a variety of  software systems in different ways. Each system operates a specific function for the process. To operate the process end to end, each function performs the same cycle of steps: i) send data & information to the System, ii) receive response from the System, iii) compute & validate response, iv) share & store execution of step, v) evaluate & initiate next steps.

Operations Cycle
Process with Operations cycle
Operations Cycle must repeat for each software system in the end-to-end process.

3. Opportunity

Opportunity: platform to reliably operate

Enterprises are complex organizations operating many processes. Enterprises operate Processes across fragmented and siloed teams and software systems resulting in disjointed, inconsistent  and inefficient end to end operations, leading to high costs, delays and errors.

All teams Operate the same process

Specifically, operating processes across fragmented and siloed teams and software systems affect process operations both technically during the development phase & operationally once they go live in production.

Process problems

Allianz’s cross-department claims settlement process encompasses multiple participants, who are fragmented and siloed throughout the process. Due to the siloed nature of the participants, teams will often change their operations without the knowledge of other teams operating the process. This often requires monitoring and reconciliation by Allianz to correct errors and ensure the process functions correctly, increasing operational costs of the process. Delays impact settlement for customers, which decreases customer satisfaction. The siloed process also increases the risk of fraud and makes audits more difficult.

4. Traditional Solutions to end to end process operations are unreliable

Enterprises have great individual functions & teams & software systems. However, for efficient process operations, effective end-to-end operations are as important as effective functions & teams & systems.

Process First

To operate an end to end process enterprises traditionally set up projects, with i) dedicated  large teams,  & ii) infrastructure set up, to iii) develop application (end to end process) code, & iv) set up maintenance systems. This bespoke approach results in high operations cost & multiple technical & operational problems.

Traditional approach

Bespoke connectors and local operations scripts & why they are unreliable

Traditional solutions for operating enterprise processes are inefficient. They have disjointed local operations that are modified and maintained by teams that own specific parts of the process. As the process changes and evolves, local operations are often modified without fully considering its impact on the rest of the end to end process operations. They also deploy local and non-standard connectors between teams directly interacting with each other in the process. For more details please visit the Full Case Study.

Automation tools & why stitching them together is unreliable

RPA & Workflow not great

To attempt to remedy the inefficiencies of this approach, enterprises use automation tools such as RPA and workflow automation tools to operate the process. These tools are effective at operating local task and workflow operations, usually for 1-2 teams - but do not scale to end-to-end process operations across multiple teams and software systems. This approach does not solve the problems of operational friction, inefficiencies, delays and errors. For more details please visit the Full Case Study.

5. Solution

Luther’s platform was used by the Allianz’s development team to build a world-class cross-department claims settlement process. The platform provides standard connectivity across all teams & systems, and  consistent common operations script.

Platform USP
How Luther does it

Implementation

The automated cross-department claims settlement process is a product built on the Luther platform using Deep Process Automation Technology to automate the process of settling claims. The implementation steps included:

  • Discover Phase (4 weeks):
  • Platform Set-up (1 day): Luther's team deployed the platform on all nodes.
  • Common Operations Script for Process Operations (8 weeks): Allianz development team, in collaboration with Luther, developed the application code to operate the end-to-end process.
  • Go Live (Production)
Implementation times

How it all comes together reliably, with the Luther Platform

Luther’s platform reliably operates the end-to-end cross-department claims settlement process by providing standard connectivity and common operations scripts.

Luther Platform for Allianz ICS
Luther Platform Reliable

6. Results

Estimated Commercial Results

Allianz Results

Operational and Technical Results

The Luther Platform streamlines operations across enterprise processes, reducing process time and cost while maintaining transparency and flexibility.

Ford Benefits

Luther Systems

What we do and why

Luther nutshell

Luther platform Links

Find more information about Luther’s Platform Core Features here.

For a more detailed introduction to the Luther platform please visit Luther Deep Process Automation Primer

For a detailed introduction and documentation examples please see the Luther Platform website.

For more information about Luther’s platform please visit Luther Systems website.

We use cookies to give you the best experience of using this website. By continuing to use this site, you accept our use of cookies. Please read our Cookie Policy for more information.