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 treats submissions, policy changes, cancellations and reinstatements as separate job types, each with its own API calls. A sender that built a submission connector must map, code and test every other transaction again. Until that build finishes, someone keys each change into PolicyCenter by hand.
One System Shows the Old Policy
A cancellation recorded in the underwriting system does nothing until PolicyCenter receives it. In the gap, the two systems show different status for the same policy. Anyone working from PolicyCenter sees a policy that no longer matches the underwriter’s decision.
Every Upgrade Reopens the Build
Each connector a sender writes depends on PolicyCenter’s APIs and on the carrier’s own endpoints. When Guidewire or the carrier upgrades, the sender reworks and retests the connector. With a separate connector for each transaction, one upgrade means several rounds of rework.
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