Skip to content
Zentis AI
Request a demo
Zentis AI
Industries
Banking & creditSOUL co-pilot, retail credit, onboarding.InsuranceFNOL, claims triage, underwriting.Finance, risk & voiceForecasting, reserving, voice agents.Insurance BrokerageEvery quote and every renewal, ready before the client starts wondering.
Products
Zentis AnalyticsForecasting, reserving, and regulatory reportingAuditOSBank, e-commerce, Shariah, and claims audit.FAMIend-to-end motor insurance automationZentis BinderDefence file assembly, live as the case runs.
Resources
NewsProduct news and conference write-ups.ArticlesLonger pieces on AI in regulated industry.Events & webinarsWhere to find us in person.UsecasesA library of reusable, editable templates.
Company
AboutWho we are and why the harness is the product.PartnersTechnology, consulting, and reseller partners.ContactTalk to the team, or book a working session.CareersJoin us
Platform
ZaraZara is where a workflow starts, Zara builds the team.Zen StudioZen Studiois where engineering opens it upZen PilotZen Pilot is where it actually runs
Request a demo

Stay Ahead with Zentis AI Insights

Subscribe to receive the latest updates straight to your inbox

Zentis AI

An enterprise-grade agentic platform for banking, insurance, and audit. Incubated by Techvantage.ai.

Platform

ZaraSPARZen StudioZen Pilot

Solutions

Audit & complianceInsuranceBanking & creditFinance, risk & voice

Trust

The defence fileSecurityAssuranceRegulatory packs

Resources

NewsArticlesEvents & webinarsClassic

Company

AboutPartnersContactCareers
© 2026 Zentis AI. All rights reserved.info@zentis.aiLondon, England
Anthropic Partner NetworkNVIDIA InceptionTechvantage.ai, Deloitte Technology Fast 50
← All use cases04 / 20
Insurance · Singapore

Quarterly close and reporting for a life insurer

A nine week scramble across four systems could become a two day, board-ready pack.

Built with a Head of Finance & Actuarial in mindQuarterly close and reporting for a life insurer — workflow screenshot

The kind of team this fits: a Singapore life insurer with a multi product portfolio, roughly USD 2.4bn GWP, 45 FTE across finance and actuarial.

The morning before

Nine weeks of quarterly close spent reconciling four separate systems by hand means the board pack gets built from last quarter's confidence in this quarter's numbers, because there was never time to double check them properly.

Image, the morning before

A photo or illustration of what this looks like today, before any of this runs.

How this could run

Not a feature list. The actual sequence, from the moment the case lands to the moment someone signs it.

  1. 01

    Forecasting and reserving share one core

    Premium forecasting and IBNR reserving run off the same live data all quarter, not four systems reconciled at the end.

  2. 02

    Reconciliation stops being manual

    The numbers agree because they came from the same place, not because someone spent three weeks making them agree.

  3. 03

    The ratio pack builds itself as the quarter closes

    Loss ratio, expense ratio and combined ratio are ready before the board meeting, not the night before it.

Image, inside Zen Studio

Screenshot of a Zen Studio canvas configured for a workflow like this one.

What doesn't change

Finance still owns every number that reaches the board. What changes is how much of the quarter gets spent chasing them instead of using them.

What this could mean

Illustrative, based on the shape of a workflow like this one. The real number depends on the case, the team, and how it's configured.

9 weeks → 2 daysQuarterly board pack turnaround
1 coreForecast, reserve and ratios connected
Image, inside Zen Pilot

Screenshot of the Zen Pilot dashboard or explainability panel for a run of this workflow.

Where this lives in the platform

For a head of finance & actuarial, a workflow like this starts as a conversation with Zara, describing the process in plain language and getting a first draft of the team back in the same session. Zen Studio is where engineering opens that draft, sets the guardrails node by node, and versions it before it goes live. Zen Pilot is where it actually runs, and where anyone can watch a case move through it in real time, node by node, with the reasoning attached.

Scale this is modelled on

Modelled at USD 2.4bn GWP, 4 systems connected

See a workflow like this built and running, live.Request a demo
← Previous use caseAll use casesNext use case →