Yazh (Yaal), our Integration Gateway, creates a single policy in PolicyCenter from your legacy system or archive when a claim or request calls for it, so years of old history stay out of PolicyCenter until they matter.
The Problem
Old Policy Terms Are Missing When Someone Needs Them
Most carriers bring only current terms into PolicyCenter at go-live. Older terms stay behind, and the need for them shows up one request at a time.
A Claim Arrives on a Term That Isn’t There
Claims tied to old policy terms require manual retrieval and recreation in PolicyCenter, delaying claim creation and keeping the legacy system active.
Loading All History Slows the New System
Loading all historical terms into PolicyCenter requires extensive cleansing and may degrade performance, despite most records rarely being accessed.
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 the Term From Legacy or Archive
Send the policy term in the format your legacy system or archive already holds it.
LiLa-Suggested Mapping
LiLa maps each source field to PolicyCenter. You set the mapping once for a line of business and reuse it for every policy you send.
Review Every Mapping
A person edits, adds or removes mapped fields before the mapping goes live.
Policy First, Then the Claim
PolicyCenter receives the policy, and the claim is created against it.
Self-Service
Your team sends a policy whenever it is needed, with no InsOps step inside each transaction.
Logged and Monitored
Every request is authenticated, validated and recorded, with audit entries on the dashboard.
FAQ