Yazh (Yaal), our Integration Gateway, brings a single billing record from your legacy system or archive into BillingCenter on demand. Older billing history stays in the archive until it is needed.
The Problem
Old Billing Records Are Either in the Way or Out of Reach
Carriers moving to BillingCenter have to decide what happens to years of billing history. Moving all of it is costly, and leaving it behind makes it hard to reach.
Billing History Stays in the Legacy System
Guidewire’s Open Balance approach transfers only open balances as single transactions, leaving historical transactions in the legacy system and requiring staff to access it for records and statements.
Payment Plans Have to Match
Guidewire requires matching payment plans in both systems before legacy billing records can be created in BillingCenter.
Billing Logic Differs Between Systems
Each system calculates the same premium, commission or discount in its own way. Teams decode that logic by hand before a record can be reconciled and loaded.
The Solution
How does InsOps Help?
Yazh (Yaal) Brings Legacy Billing Records Into BillingCenter When They Are Needed
Pull one billing record when it is needed.
Your team or system sends a single legacy billing record, only when someone needs it in BillingCenter.
Understands billing data
LiLa recognizes the same premium, commission or discount across systems, even when fields or calculations differ. It works with inconsistent billing data without an upfront cleanup.
Mapped once, confirmed by a person
LiLa suggests the mapping the first time a payload arrives. A person confirms it, and later payload changes are edited in the portal.
Value translation
Yazh (Yaal) translates your legacy codes into the values BillingCenter expects.
Test calls and secured requests
Test the route before go-live. Every request passes a firewall, authentication, authorization and validation.
Every record on one dashboard.
Your team sees each request, response and error in one place.
FAQ