Keep your core.
Add a connection.
Use API-based integration to connect selected workflows to your existing information systems, including systems outside the Zhibao Cloud platform.
Build on the systems
you already use.
Connect a specific workflow or introduce a broader operating platform. WiseFin’s approach starts with your existing technology and the connections your business needs.
Your operating environment
Existing systems
Core insurance · CRM · finance · digital channelsWiseFin
Connect & coordinate
Selected modules · API adapters · workflow configurationExternal connections
Insurers & partners
Approved product, application, policy and status interfacesConceptual model. The interfaces, data flows and responsibilities are defined for each project.
Choose the right
starting point.
The integration approach follows your priorities and the interfaces available.
Keep your core.
Connect a sales
and service workspace.
Introduce a Broker Portal and the agreed back-office connections for a more consistent client-facing workflow.
Bring more of the
operation together.
Scope a wider set of modules across policies, commission, reporting and organisational management, with a planned migration approach.
Define the connection.
Then prove it works.
Clear data ownership and interface expectations are as important as the connection itself.
Product & application data
Agree the product fields, application flow and validation expected by the insurer or partner. Online issuance depends on approved insurer API access.
Policy & status return
Map policy identifiers, documents, status changes and exception handling to the operational record.
Finance & reconciliation
Define the records, settlement rules and exchange format needed by finance and existing accounting workflows.
Access & operating controls
Agree interface authentication, permitted access, monitoring, failure handling and responsibility for changes.
The approach builds on Zhibao Cloud’s documented OpenAPI and existing-system integration capabilities. Connections in each international market are scoped individually.
Kenya / Insurer finance & operations
Your core system works.
Make the next improvement count.
Strengthen commission reconciliation and operational controls alongside existing systems. Start where manual checks, scattered records and reporting effort slow your team down.
Cross-check records
Bring commission records, comparison rules and mismatch review into one agreed workflow, so finance can work across fragmented sources with clearer context.
Make exceptions visible
Give finance and operations a shared view of discrepancies and the follow-through needed to resolve them. Make management reviews easier to prepare.
Fit your business rules
Configure commission structures around your operating model, then agree how the required records connect with your existing systems.
Support sales and service
Use AI assistance for proposals, policy enquiries and customer follow-ups within the agreed scope. Your team reviews the output and makes the decisions.
A focused first step
Start with one
reconciliation workflow.
Agree a paid pilot with a fixed scope, named business owners and a baseline. Review the required data, interfaces and controls before delivery, then compare the agreed measures before deciding whether to expand.
Success measures to agree
- Reconciliation hours
- Time spent preparing, checking and reconciling records.
- Unmatched records
- Outstanding mismatches at an agreed point in the process.
- Resolution time
- Time from identifying a discrepancy to its agreed resolution.
Use comparable record volumes and time periods. These are proposed pilot measures; results are established with your team.
The product tour shows commission rule configuration. An end-to-end reconciliation demonstration is scoped around your records, rules and interfaces. Integration feasibility, authorised data access and local requirements are agreed for the project.
A useful first
technical conversation.
Bring your system map, the workflows you want to connect and any available interface documentation. We can then identify the data mapping, ownership and testing questions.
Plan an integration discussionDo we need to replace our current platform?
Not necessarily. The documented integration approach supports connecting to existing systems. Whether a particular workflow can be added depends on the available interfaces and agreed project design.
Are all insurer connections already available overseas?
No. The China integration history is experience, not a claim that every connection is available in another market. We confirm insurer participation, API access and the required workflow before committing to scope.
Is online policy issuance included automatically?
Issuance requires an approved insurer interface, the relevant product and operating permissions, and a tested integration. The product tour does not issue policies.
How are migration and interface changes handled?
Data mapping, trial imports, exception resolution and acceptance checks are planned during delivery. Responsibilities for interface changes and ongoing maintenance are agreed in the service scope.
Let’s build your
next chapter.
Tell us where you want to take your insurance business. Let’s explore how the right technology can help.
Talk to our team