Yazh (Yaal), our Integration Gateway, already takes sender payloads into your systems. InsOps is building toward sending billing updates, suspense payments and disbursements through it, and wants carriers to help shape it.
The Problem
Billing Changes and Unmatched Payments Reach Your Billing System Out of Step
Payments and billing changes come from policy systems and payment sources, often without the information your billing system needs to post them.
Payments Arrive Before the Policy Does
Payments can arrive before a policy is bound, without account or policy details, so the billing system holds them in suspense.
Applying a Payment Needs Accurate Identification
To apply a payment, it must be open and linked to an existing account or policy, so someone has to identify the correct target.
Unmatched Money Needs a Decision
A suspense payment can be applied, reversed or returned as a disbursement. Each is a separate action.
The Solution
How does InsOps Help?
Yazh (Yaal) Is Building Toward Billing Updates in Your Billing System
Billing Updates Into Your Billing System
Planned: sending billing updates from sources into your billing system in the format it expects.
Suspense Payments
Planned: sending a payment as a suspense payment when its account or policy is unknown.
Applying and Disbursing
Planned: applying a suspense payment once its account or policy is known, and returning unmatched money to the payer as a disbursement.
Mapped Once, Confirmed by a Person
LiLa suggests how a sender's payload maps to your billing system. A person confirms it, and later changes are edited in the portal.
Value Translation, Test Calls and Secured Requests
Yazh (Yaal) maps sender values to your billing system's formats. Senders can test before go-live, and every request passes firewall, authentication, authorization and validation checks.
Every Billing Request on One Dashboard
Teams see each request, response and error in one place.
FAQ
Is this available today?
Who confirms the mapping?
Is this the same as billing migration?