What's new in Global Content Reference Applications for Qusar

Message management enhancements in ClaimCenter for London Market Cloud

This release adds the following message management enhancements to ClaimCenter for London Market Cloud:

• Electronic Claim File (ECF) Response screen updates to remove Volume Claims Service (VCS) related response codes
  • This release updates the Lloyd’s ECF response screen in ClaimCenter to remove VCS-specific options. This update is in response to changes made by Velonetic (Central Services) where VCS support is discontinued.
  • VCS-related response codes (such as SERVICE-ACTION and VCS-ENTRY/EXIT variants) and VCS triage categories (for example, VCS-XCS and VCS-Crawford) are no longer available in the Lloyd’s Lead Response and Triage Category drop-downs.
  • The Triage Category field now defaults to the standard CTP-Standard option, ensuring consistent, non-VCS processing for all Lloyd’s responses and preventing you from selecting unsupported VCS response types.
• Adapt bureau/non-bureau claim identification behaviours to London Insurance Market Claims Message (LIMCLM) scenarios
  • This feature extends existing bureau/non-bureau claim identification to support LIMCLM messages in London Market ClaimCenter.
  • This enhancement lets claim handlers capture the ReceiverPartyID during FNOL for bureau claims. It then uses the LIMCLM-specific composite key: Unique Claim Reference (UCR), Unique Market Reference (UMR), and Receiver Party ID (UCR+UMR+ReceiverPartyID) to automatically match incoming LIMCLM messages, both Institute of London Underwriters (ILU) and London International Insurance and Reinsurance Market Association (LIRMA) variants, to the correct claim.
  • When a LIMCLM message is linked, it is displayed under the London Market location group in the claim’s navigation.
• LIRMA multi-currency SDC/MAM matching per currency (CUX)
  • This change corrects multi-currency handling for LIRMA messages (Claim Notification for LIRMA or CLMLRC). For each currency (CUX) block, the Signing Details Corresponding (SDC) and Insuring Market Amount (MAM) segments are matched by currency code instead of treated as shared message-level data.
  • For each currency slice, the processor now derives signing details and claimAmountsIndicator independently, based on that slice’s SDC/MAM entries, ensuring accurate financial and signing information across all currencies without changing existing single-currency behaviour.
• Message-scoped correction revert for outbound Electronic Claim File (ECF) and Insurers' Market Repository (IMR) messages
  • Outbound ECF and IMR messages now return the original (pre-correction) field values received from external systems, even when internal data-correction rules have normalised those values in ClaimCenter.
  • This message-scoped revert behaviour ensures brokers and market systems can reliably match responses to their original transactions, including in scenarios where multiple “incorrect” values map to the same corrected value.
• Configure recovery reserve creation and seeding
  • New extension points in the London Market financials processing allow you to control when and how recovery reserves are created and seeded from settlement messages such as LIRMA.
  • Customers can decide whether to create a recovery reserve for a given message, adjust the initial reserve seed (for example, include or exclude the recovery amount), and customise how recovery transactions are created and integrated with approval workflows.
  • The originating settlement message is now available to Gosu rules at save time, enabling approval logic based on insurer response codes and other message data.
  • Default behaviour remains unchanged if you do not configure these hooks.

  For more information, see the London Market Configuration Guide.

Message processing enhancements in ClaimCenter for London Market Cloud

For more details, see the latest London Market Release Notes.

Enhancements to Code of Practice time-based obligations

Enhancements to Code of Practice vulnerability

Enhancements to Complaint Gateway

Contact-level complaint summary in InsuranceSuite applications

This release introduces a contact-level complaint summary in InsuranceSuite applications. This summary provides a consolidated view of all complaints associated with a selected contact across claims, policies, and accounts.

Key benefits:

• Provides a single view of all complaints related to a contact across multiple business records.
• Improves visibility into customer complaint history without navigating between claims, policies, or accounts.
• Delivers a consistent user experience by reusing the existing Complaint Gateway summary view.
• Supports faster customer service and more informed decision-making through enhanced complaint visibility.

For more details, see the InsuranceSuite Packages for Australia and New Zealand Release Notes.

Fair Insurance Code for New Zealand

The Fair Insurance Code (FIC) feature helps New Zealand insurers meet obligations under the Fair Insurance Code. This feature ensures insurers provide a minimum level of service to policyholders and claimants, especially when responding to inquiries and handling claims.

• Time-based claim obligations: Enables insurers to manage and fulfill time-based claim obligations by completing required actions within defined time frames, improving claims processing efficiency and compliance.
• Past-due reviews: Provides comprehensive reporting to identify overdue obligations and monitor compliance with code-related requirements, helping insurers address non-compliance proactively.
• Vulnerability support: Helps insurers identify and support claimants and policyholders experiencing vulnerabilities, ensuring appropriate assistance is provided throughout the claims journey.
• Interpreter assistance: Supports policyholders and claimants with language barriers by facilitating interpreter services for more effective communication.
• Manage vulnerabilities through APIs: Introduces enhanced APIs that allow insurers to create, update, or delete individual vulnerabilities for a contact without replacing the entire list, enabling more efficient vulnerability management.
• FIC reporting: Delivers insights into time-based obligation compliance, workflow progress, and vulnerability tracking through Guidewire Explore and Guidewire Data Studio, providing greater operational visibility and reporting capabilities.

For more details, see the InsuranceSuite Packages for Australia and New Zealand Release Notes.

Japan policy capabilities

• SompoVAN 1st Messaging integration with PolicyCenter

  The SompoVAN 1st Messaging integration enables Guidewire PolicyCenter on Guidewire Cloud to generate policy-related report data in the format required for the SompoVAN Network Center, the centralized data exchange network for Japanese non-life insurers.

  Key capabilities of SompoVAN 1st Messaging integration

  • Automatic generation of SompoVAN 1st messages based on personal auto policy lifecycle events.
  • Support for outbound requests and inbound responses for SompoVAN messaging.
  • Support for the following six SompoVAN 1st message types:

    1. Accident History

    2. Duplicate Policy Check

    3. Grade 6 Contract Data

    4. Maturity Data

    5. Suspended Policy

    6. Multiple Vehicle Ownership

  • Automatic creation of underwriting review activities in PolicyCenter whenever an inbound SompoVAN response identifies discrepancies, enabling underwriters to review and resolve issues promptly.

• Japan Personal Auto (JPPA) support for policy start and end times

  PolicyCenter supports configurable policy start and end times for the Japan Personal Auto (JPPA) line of business. This enhancement enables insurers to define policy effective times that align with Japanese market practices, where policies typically begin and end at a specific time of day (commonly 16:00) instead of midnight.

• GIROJ outbound file recreation capability

  The General Insurance Rating Organization of Japan (GIROJ) integration now supports outbound file recreation, allowing insurers to regenerate GIROJ submission files when updates or corrections are needed before submission. This capability simplifies recreating outbound files after data corrections, accidental file loss, or system updates, ensuring accurate and timely submissions without manual reconstruction of file contents.

• Japan Rating integration for PolicyCenter

  The Japan Rating release introduces a major enhancement to premium calculation for the Japanese market in Guidewire PolicyCenter on Guidewire Cloud.

  This release replaces the legacy JPPA Rating implementation with the new Stacked Cost Rating Engine. The new engine provides more accurate and flexible premium calculations and addresses key limitations of the standard Guidewire rating model. The new architecture supports Japan-specific business rules, including direction-based premium proration, multiple policy changes on the same day, customer-specific rounding requirements, and complex policy transaction scenarios

Japan claims capabilities

• Search for policies by license plate number in ClaimCenter

  The Search for policies by license plate number feature streamlines the First Notice of Loss (FNOL) workflow by introducing structured search fields for Japanese license plates.

• Police Reports integration for ClaimCenter

  The new Police Reports release introduces a modern, Guidewire Cloud Platform (GWCP)–ready integration for requesting and receiving Traffic Accident Certificates (交通事故証明書) from the Japan Safe Driving Center (JSDC).

For more details, see the InsuranceSuite Package for Japan Release Notes.

Insurance license plate policies in PolicyCenter

With this release, you can create, change and cancel insurance license plate policies in PolicyCenter. This release provides the following features:

• Introduces Insurance Plate Policy as a dedicated policy type within Personal Auto Policy (DE) for moped and plate-based products.
• Supports both standard insurance license plates and red plates, with built-in date logic, format, and uniqueness validation, quota-based auto-assignment, and low/no-quota warnings.
• Blocks policy actions such as renewal, rewrite, reinstatement, suspension, and unsuspension.
• Keeps the policy type aligned with German regulatory and business rules.

You can now change and cancel insurance license plate policies. This release provides the following features:

• Enables PolicyCenter to register, change, and cancel German insurance license plate policies via the VU_GDV_005 outbound message.
• Reuses existing policy workflows and eVB Message screens.
• Drives the correct operation type from VuMitteilungsart (issue, change, cancel), and sends messages that track status from "Sent" to "Acknowledged".
• Adds validations to ensure VU_GDV_005 payloads comply with Federal Motor Transport Authority (KBA) rules from 1 July 2026.
• Reduces rejections by enforcing constraints such as a mandatory date of birth for natural-person holders and suppression of prohibited name and association-representative data.

This release provides enhanced handling of insurance license plate errors and warnings.

• Extends the insurance plate messaging flow to handle functional rejections and warnings from the authorities, received as GDV_VU_007 messages.
• When a registration, change, or cancellation is rejected, the system records the message, creates an urgent Insurance license plate rejected activity, and allows users to correct the policy and resend VU_GDV_005.
• Warning responses generate a low-priority Additional notes activity.
• The system validates, stores, and indexes all GDV_VU_007 messages so users can troubleshoot issues, including KBA rule breaches effective 1 July 2026, and ensure that corrected notifications are accepted.

This release provides Quota Administration enhancements for insurance license plates. Use the Quota Administration screen to configure three-letter license plate suffix quotas for normal and red plates.

• The system enforces strict suffix-format validation to ensure uniqueness.
• Available plate counts are decremented as numbers are assigned.
• Deletion is blocked once a suffix is in use.
• A warning message is displayed when a suffix falls below a configurable warning threshold.

APD model modernization for Guidewire for Germany

Integration Gateway license plate validation for eVB requests

This release uses Integration Gateway (IG) to harmonize license plate validation for eVB requests (VU_GDV_001). IG now aligns German eVB license plate validation with GDV rules and with the existing self-managed and Guidewire for Germany on Cloud user interface behavior. This enhancement ensures that:

• Normal black (including "H" and "E" plates and umlauts), green, authority, short-term (RK), red, and diplomat plates that are valid in the self-managed solution are now accepted consistently in IG, and mapped correctly into VU_GDV_001.
• Kennzeichen.001, Kennzeichen.018, and VU_GDV_001.055 messages are generated when there are errors. Errors are generated when there are malformed plates, missing short-term expiry days, invalid Wechselkennzeichen combinations, or impermissible oldtimer or red plates.

eVB registration flows for changes of residence and vehicle owner

In this release, eVB registration flows now support changes of residence and changes of vehicle ownership. Where a vehicle owner moves to a new registration district, and presents proof of insurance from a different insurer, Guidewire for Germany on Cloud now supports the corresponding German registration flows with a new eVB number.

• When your insurer is the new insurer, PolicyCenter can request a new eVB number and consume GDV_VU_003.2 updates from the authorities to keep holder and registration data in sync.
• When your insurer is the old insurer, inbound GDV_VU_005 loss of business notifications are handled without unintended policy changes. The successor insurer date is updated only where required.

Association contact handling for GDV_VU_003 messages

In this release, when the system receives a GDV_VU_003 (Vereinigung) message for a policy whose vehicle holder is an association, it links the message to the existing association contact instead of creating a duplicate.

The system detects changes to the association’s legal representative (for individuals: name and date of birth; for companies: company name) and applies those changes to the account-level contact.

This enhancement ensures that contact data remains consistent between GDV messages and the account while avoiding unnecessary new contacts.

For more details, see the Guidewire for Germany Cloud Release Notes.