Amendments, cancellations and reinstatements made in your underwriting system reach PolicyCenter through Yazh (Yaal), our Integration Gateway, the same route that carries submissions, so no sender builds a separate integration for each.
The Problem
Policy Changes Fall Behind in PolicyCenter
Underwriting teams change policies after issuance, often in a workbench or policy system outside PolicyCenter. PolicyCenter has to receive each change to stay accurate.
Each Transaction Is Its Own Build
PolicyCenter requires separate connectors for policy changes, cancellations and reinstatements, forcing staff to enter updates manually until integrations are ready.
One System Shows the Old Policy
Until PolicyCenter receives a cancellation, systems show conflicting policy statuses, leaving staff with outdated information that contradicts the underwriter’s decision.
Every Upgrade Reopens the Build
Guidewire or carrier upgrades force senders to rework and retest connectors. Separate transaction connectors multiply the effort with every upgrade.
The Solution
How does InsOps Help?
How Yazh (Yaal) Moves Submissions Into PolicyCenter
Bring Your Change Payload
Send amendments, cancellations and reinstatements in your own format. LiLa suggests how each field maps to PolicyCenter.
Review Every Mapping
A person on the sender’s side edits, adds or removes mapped fields before the mapping goes live.
Policy Changes
Send a mid-term amendment against the policy it changes.
Cancellations
Send a cancellation against an active policy.
Reinstatements
Send a reinstatement against a cancelled policy.
Logged and Monitored
Every request is authenticated, validated and recorded, with audit entries on the dashboard.
FAQ