What's new in Global Content Reference Applications for Palisades

Message processing enhancements

In this release, the following message processing enhancements are added to the London Market Integration Gateway implementation (IPLMG):

• Comprehensive inbound and outbound storage of XML messages in support of Electronic Claim File 2 (ECF2) and London Insurance Market (LM)

• Audit capabilities for inbound and outbound XML messages in support of ECF2 and LM. This feature persists all inbound and outbound ECF2 and London Market XML messages processed via Integration Gateway and links them to the related London Market message records in ClaimCenter.

Message management enhancements

In this release, the following message management enhancements are added to ClaimCenter for London Market cloud:

• Support for negative amounts reported as reserve and/or payment values via London Market claims messages

• Support for out-of-sequence SCM claim creation and enhanced movement sequencing

• Support for loss date editing during manual allocation of suspended EDI claim movements

• Support for multi-currency reserving by settlement currency. ClaimCenter now supports reserve line uniqueness by settlement currency for London Market messages.

• Ability to use ‘claim context’ when applying message data correction rules. The configurable message data correction framework has been enhanced to allow rules to be restricted by claim context (for example, UCR and claim line).

• Support for LIMCLM and LIRMA short messages. ClaimCenter now correctly handles LIRMA short LIMCLM messages (summary, closure, and short response messages with reduced data structures).

• Ability to import reference data correction rules

• Improved management of suspended message flows including:

  • Use of claim line number for Claim Search

  • Re-evaluate and apply previously suspended SCM messages automatically

  • Display a claim history record for manual allocation of suspended messages

• Catastrophe management enhancements added for improved ECF integration

Extensions

In this release, the following configuration and extension options are included for insurer customization:

• Extension point for document mapping for ECF transaction and IMR search. Using the extension point, you can configure out‑of‑the‑box document mappings for London Market documents received via IMR download, Claim Notify, and documents shared via IMR upload.

• Extension point for automatic ECF document download rules. Using the extension point for IMR/ECF document download rules, you can apply custom logic using any data element from ECF Notify/Retrieve messages and optional external systems

Note on terminology:

• ClaimCenter for London Market cloud (Palisades) provides an Electronic Data Interchange (EDI) file processing and management services for Syndicate Claims Message (SCM) and London Insurance Market Claims Message (LIMCLM) messages to support both London International Insurance and Reinsurance Market Association (LIRMA) and Institute of London Underwriters (ILU) message processing.

• Both SCM and LIMCLM are EDI message standards used to transmit claim data between brokers, underwriters, and the Velonetic bureau systems in Lloyd's.

• ECF2 is an enhanced electronic claims processing system used in the London Insurance Market (LM) to streamline the handling of insurance claims.

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

Australian content packaging

Australian content has been restructured into separate packages to enable independent pricing and delivery.

Australia Complaints Gateway

This new feature within the InsuranceSuite package for Australia helps insurers meet regulatory and compliance requirements when managing customer complaints.

Australian localization enhancements

Base configuration has been updated to better align with Australian standards, terminology, and regional requirements.

Code of Practice — Time-Based Obligations enhancements

Code of Practice — Vulnerability enhancements

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

SompoVAN for ClaimCenter

SompoVAN is a messaging standard used by Japanese insurers for exchanging claims-related information. The new SompoVAN replaces the legacy SompoVAN implementation that was part of the Japan Personal Auto (JPPA) accelerator for ClaimCenter.

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

VIN correction

The solution now supports VIN (FIN in German) correction for Change of Insurer (VU_GDV_002) and End of Contract (VU_GDV_004) messages when a VIN correction service is booked with GDV.

Depending on configuration, VIN corrections can be auto‑bound or require user review, with activities created in both cases.

Red license plates (Kennzeichenart R) are explicitly excluded from VIN correction and remain valid without a VIN.

Electronic insurance verification (eVB) message storage and transmission

The solution now supports SOAP‑free eVB queue messages and JMS BytesMessage. These changes align the product with GDV eVB queue requirements while maintaining backward compatibility for existing TextMessage‑based deployments.

Improved eVB message search usability and consistency

The eVB Message Search screen now delivers consistent, more readable search results:

• Improved eVB message search results by filtering out technical messages.

• Refined Message Typefilter.

• Simplified name-based search by introducing unified fields for Policy Holder Name, Vehicle Holder Name, and Association Name.

• Enhanced eVB message persistence so VU_GDV_001 messages are stored after GDV_VU_001 is received, allowing the eVB number to be saved on the outgoing message.

• Protected GDV_VU metadata so updates from incoming messages (for example, license plate changes) are preserved and not overwritten by correlated messages.

• Quick navigation links in results: Holder name now links directly to the Policy Holder’s Account. eVB Number now links directly to the related Policy’s eVB tab.

• Clearer message direction indicator: the former Sent/received column is renamed to Direction with values incoming or outgoing.

• A new eVB Status column has been updated, displaying one of the following values: Not Yet Valid, Valid, Used, or Expired.

• Persistent search filters on the eVB Message Search screen, ensuring that selected filters and search text are retained when users navigate away from and then return to the screen.

Support for German Insurance Association (GDV) eVB procedure version 4.20

The solution now supports GDV eVB version 4.20 validation rules. Outbound eVB messages enforce:

• Plausible insurance start dates (DatumVersicherungsbeginn) between 01.01.1940 and at most two years in the future.

• (Where applicable) Updated handling of VIN‑related change reasons in line with the 4.20 specification.

These checks help prevent implausible dates and ensure conformity with the updated GDV manual.

Associations as vehicle owners/holders in inbound and outbound messages

The solution now fully supports associations (Vereinigungen) as vehicle owners and holders in inbound and outbound GDV messages. You can:

• Use an association organization with either a natural person or legal person as the legal representative.

• Include association details in outbound payloads under policyholder (Versicherungsnehmer) and, when explicitly requested for eVB, under vehicle holder (Halter) with the correct <Vereinigung> structure.

• Rely on the user interface and outbound validations that require a legal representative and ensure that only one of NatuerlichePerson or JuristischePerson is populated, in accordance with the GDV handbook.

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