Roundcube is a software provider that provides a cloud-enabled, modular policy, billing and claims management solution designed specifically for the insurance industry that:

Provides a state-of-the-art customer centric portal to be used by any party that wants to interact with insurers.

Offers personalized portal pages and dash boards:

View, compare and purchase or change policies, claims, personal details

Ask questions and/or “contact us”

Allows real-time changes with high degree of Straight-Through-Processing, Configurable by regular business people Platform independent and can be layered on top of any currently implemented core insurance system;

Powered by Software AG's DBP


Policy and Claims Management Solution for Insurance

Roundcube is a cloud-enabled, modular policy, claims, and billing management solution designed specifically for the insurance industry. It promotes customer centricity by providing a personalized experience to any and all users, whether end-customers, employees or third parties. Claims and Policy Management solution for Insurance

Features and Benefits

Provide omni-channel seamless user experience
  • Reach users anytime, anywhere, on any device 
  • Increased customer 24/7 self-servicing with new offering
  • Reduced response time to match expectations
Improve productivity
  • Maximize STP and reduce human error 
  • Enable real-time insights and proactive business intelligence 
  • Reduce operational costs through self-service
Introduce maximum flexibility
  • Get true control of distribution channels, product design, business processes and business rules 
  • Accelerate time-to-market significantly with ability to make instant changes 
  • Get best practices that can be used unchanged or easily modified yourself
Multi-user, omni-channel portal
Powerful online self-service solution for customers, employees, partners, body shops, experts, appraisers and opposite parties. This digital solution supports pre-sale, sale, and post-sale service to customers and help insurers regain more direct control of the customer relationship.
Every user, whether internal or external, has access to the same portal, insuring consistency and simplicity. The solution will select the right information to provide and layout to use, based on the user's profile.

The Roundcube Portal allows insurers to communicate with customers, create access to appropriate products and promote an effortless experience at every touch point.
Best-Practice Processes
Roundcube comes standard with out-of-the-box best-practices for Policy, Claims and Billing Management Processes which are easy to adjust.
Best-Practice Processes
Best-Practice BPM process
The solution provides a set of best practice processes for claims handling, policy management and billing to be deployed and executed on the BPM layer.
Master Data Tables
In Roundcube, insurers can build insurance product(s). In an insurance product an administrator is able to configure questions and create a drop down lists so a customer can choose from a list of predefined answers.
For instance, a question that could be asked when applying for a home content insurance is the type of house. Possible answers could be: normal, villa, apartment etc. The possible answers that are presented to the user originate from a master data table. In a master data table all possible values that Roundcube accepts for type of house are stored. When "type of house" is selected as a relevant question for the application of an insurance product this is done in the product configurator. The possible answers for this product will be selected out of a subset of the corresponding master data table. This means there is a dependency between master data table and the product configurator.
Roundcube comes with a lot of pre-configured master data tables out-of-the-box. These master data tables are linked to an attribute from the Roundcube data model. Next to the predefined Roundcube master data tables, an administrator can create new master data tables and link them to a specific attribute from the Roundcube data model. A record in the master data table can be linked to a system type to perform programmed behavior, for instance, an automated fraud check.
In Roundcube the business rules engine plays an important role to make decisions to for example to determine if a task has to be created, or to calculate the premium with the information that is entered by the customer. Inside a set of business rules the administrator will check the content that is set for specific fields in the Roundcube data model.
Task Based Workflow
Roundcube is an application in which business processes play an important role. Business processes ensure as much automation as possible for major insurance processes such as applying a policy or handling a claim. If such a process cannot be handled entirely automatically, tasks are created for human intervention after which the automated process can resume.
In Roundcube a task consists of one or more actions. These actions are optional or mandatory and can or should be completed in order to complete the task. After completing a task, the process is resumed, the next steps are automatically performed again until a step in the process again requires manual action. If a task is created from a step in the process, a business rules determines which type of task must be created and another business rule determines to whom the task must be assigned. So there is a dependency on the availability of the business rules engine. Tasks can be assigned to users, groups or roles that are known within Roundcube.
An administrator can define various tasks templates, each with their own actions. For each task type defined, the administrator can determine what is the default priority, assignee and deadline. There is also the possibility to add a work instruction and a detailed description. When defining a task the administrator has the option for certain characteristics to make choices from a master data table.
The administrator can indicate if a task template can be assigned to a third party. Third parties must be notified via an email of the presence of the task and how this task has to be reminded if it is not completed before the specified deadline. The user will see the tasks assigned to him in a task list (Task inbox). Here are the tasks visible to him, his role(s) or to the group(s) to which he belongs. In the task list, tasks with different priority or status are displayed with a different color.
Task Based Workflow
Authentication and Authorization
Roundcube authentication and authorization features are intended to give people access to the system and to make sure they only can perform the functions within the system for which they are authorized.
Persons that need to gain access to the system must be known within Roundcube. This can be achieved when the individuals have been registered in the internal Roundcube system or a linked LDAP. A person who wants to get access to the system must be authenticated. This can be done using a password which is validated by Roundcube or by the LDAP system or authentication can be done using a SAML ticket obtained from an external identity provider that allows single sign-on when Roundcube is used in combination with other applications.
Persons with access to Roundcube can only perform functions if they are authorized for. The authorization system of Roundcube is role based. Functions that can be performed are coupled by an administrator in roles. The administrator can attach thereto the following Roundcube assets to a role:
  • Services
  • Tasks
  • Processes
  • Menu options and actions
A user who is assigned a role, can perform all the functions that are associated with the role. A user of Roundcube can be assigned multiple roles. In order to simplify user management, it is also possible to make a user member of a group. Roles can also be assigned to a group. All users who are a member of the group are then given all the functions associated with the role. A user can be member of multiple groups. Roundcube is next to employees of the carrier also used by external parties. For an external party it should be possible to appoint an administrator. This external administrator must have the ability to do the user administration for all employees of the external party. To do this he must be able to add users and assign roles to these users.
Authentication and Authorization
E-forms policies and claims
The purpose of the E-forms is to provide electronic transaction forms to any other front-end application for applying:
  • New business for insurance products
  • Existing policies
  • Making proposals for new policy
  • Package products
  • Make an notification of loss
E-forms support both personal lines insurance products and commercial lines insurance products. In the E-forms interfaces with external data providers is supported for already a few markets (e.g. Audascan, Infofolio, Postal code, Fynergy) and web analytics through Google Analytics/Tag Manager.
It comprises of the following functionality: 
  • More flexibility in designing forms (e.g. no fixed funnel steps, composing use and placeholder for content components instead of programmed behavior)
  • Better integration in existing E-commerce websites (leads to better integrated analytics, one technology, thin UI)
  • Better onboarding experience (better usability, focus on conversion, more use of commercial content)
  • Mobile friendly support (responsive E-forms, E-forms on any device)
  • International support (multi lingual, multi-currency)
E-forms policies and claims
Accelerate time to market
  • Leverage best-practice processes, or easily modify them at need 
  • Fast deployment of new processes or changes to existing ones 
  • Intuitive web-based UI to configure business rules
Wrap and extend legacy systems
  • Add on top of any insurance core system without risk 
  • Extend life of legacy systems 
  • Redeploy to a flexible, more cost-effective platform without introducing significant risk
Create sales opportunities
  • Support of pre-sale, sale, and post-sale service to customers 
  • Generate up-sell and cross-sell opportunities 
  • More direct control of customer relationship
Product Configuration
Roundcube Product configuration allows you to make any change to your insurance product portfolio and deploy it to production in minutes instead of weeks or months.This process is made even more efficient with the help of templates.
Purpose of the product configurator is to have an efficient, user-friendly and structured tool to create and manage commercial products and forms that are offered online. The product configurator combines configuration scripts for E-forms and forms in the Connect portals. The configuration scripts offer a lot of flexibility to optimize the customer journey to the expectations of the insurance company.
The product configurator contains:
  • Creating new insurance products
  • Creating a package product
  • Adding and managing attributes that are used in a product (visual and hidden)
  • Add and manage master data tables for each individual attribute
  • Create and manage a custom list on an attribute
  • Add and manage default value on an attribute
  • Setting the display behavior of attributes
  • Add and manage coverages to the product
  • Composing coverage combinations for optimal presentation in E-forms
  • Add and manage acceptance questions (assuming an existing repository with acceptance issues is available)
  • Add and manage product parameters for validation and functional behavior in the E-form
  • Add and managing forms for premium comparison, NOL and party details (customer and agent)
  • Add and manage product themes
  • Link coverages and coverage combinations to back office products and coverages
Product Configuration
Easy to use product configuration
With the help of Roundcube’s Product Configurator, business users can rapidly create or change products and deploy them immediately - without the intervention of the IT department. This process is made even more efficient with the help of templates. This means the best lead time in the market and more commercial opportunities.
Customizable Dashboard

Roundcube offers a set of predefined dashboards for Business Intelligence and real-time analytic capabilities.

Customizable Dashboard

Multi Language - Multi Currency
Roundcube can be used by people in different capacities or roles, both internal (company) and external (customer). Because of this, functionality is needed to define profiles that will determine in which way the application will be presented to the user. The presentation of the application consists of a number of layers, each with a specific purpose:
  • The settings profile contains a set of functional parameters 
  • Style elements for the ‘look and feel’ are determined based on different (combinations of) characteristics
  • Text elements for ‘tone of voice’ are determined based on different (combinations of) characteristics
  • Language can depend on personal characteristics of the user, insurance company or product, and menu choice
  • Currency can be a policy property, default currency and number format may be derived from environment settings
  • Available functions, menus and options, and access to the related data are based on an authorization profile
Multi Language - Multi Currency
Business rule engine

Processes like risk acceptance, premium rating and claim handling requires a true business rule engine (BRE). The business processes in Roundcube will interact with its BRE. It will use data from E-forms as input for the BRE, and will also determine by which rule (set) the data will be handled. The output from the BRE will be picked up by the business process to trigger the next step(s).

Business rule engine

Memorisk is a web application that is used to make a risk analysis for insuring business risks. This analysis is used to give an advice to commercial lines customers regarding the risks against which insurance should be closed. The making of the risk analysis and the provision of the product advice is done in a number of steps:
1) Based on the Chamber of Commerce number and a number of additional questions Memorisk shows to the user which insurances are relevant. The relevance of each type of insurance is determined based on averages of the customer's industry. The answers to the questions are also used in determining the relevance of an insurance type. The overview of the relevant and less relevant types of insurances in Memorisk is called the quick scan.
2) The user must fill in a questionnaire with questions that relate to the business, location of the business, sales, operations, claim history etc. It is an intelligent questionnaire in which only questions that are relevant are presented to the user. This is determined on the basis of the sector in which the customer is operating, and the answers to previous questions.
3) Based on the answers given in answering the questionnaire, the following items are determined:
  • An extensive advice on the risks against which the customer would need to be insured
  • An advisory report on risk reduction measures to be taken by the customer. For example, the placement of smoke detectors.
  • A risk factor. This risk factor can be used by the insurer or agent as premium or determining factor in the underwriting rules to determine whether an application to be processed manually or STP.
Data entered by the customer Memorisk will be transferred to the forms in Roundcube used for product comparison, policy application or quote. The data must be displayed to the user in the Roundcube forms.



All support is delivered through Roundcube's customer portal.


Webinar Digitizing Insurance with Software AG and Roundcube
Video Roundcube by Software AG
Solution Brief DBP & Roundcube - A flexible, future-proofed mid-office solution for the insurance industry
White paper Insurance Solutions - Transforming customer interactions for the insurance industry

Portal page

Roundcube Screenshot 1


Insurance Products

Roundcube Screenshot 2


Solution Capabilities

Roundcube Screenshot 3

Contact Us

Fico/Blaze - webMethods connector

Blaze/webMethods bridge

Roundcube is based on webMethods BPMS suite and Blaze Advisor for the rule engine. Although webMethods has a built in integration with Blaze rules, Roundcube has taken a step further to integrate Blaze complex rules and complex argument processing aligned with the reality of the insurance market. Most insurers have complex data and models to work with, as well as complex rules to determine coverage, premium and so on. With the built-in webMethods integration only simple rules with basic type arguments could be used in the business processes. The Blaze/webMethods bridge is developed especially for more complex rules.
 Blaze/webMethods bridge

Features and Benefits

Make changes faster
With Roundcube's Blaze/webMethods bridge, the business can modify the business rules associated with switches in the BP, making changes faster and reliable without changing the logic.
The core function is the wrapper around the Blaze rule engine to call a deployed rule. Mainly this function provides an automated conversion between IS and Blaze types and configures the rule invocation call.


Phone +31348486848


Manual BlazeBridge description

webMethods flow rule wrapper

Fico Blaze Screenshot 1

Contact Us

Support login