01 / 21

ANLAA TECH · NON-MOTOR INSURANCE

Non-Motor Insurance
Mid-Office Solution

Connecting products, distribution, underwriting, policies, claims and analytics

Business & Technology OverviewSeptember 2026English

02 / 21

CONTENTS

Blueprint & Scenarios

First the business breakpoints and the overall blueprint, then the specific solutions for four scenarios.

04 / 21

01 / POSITIONING

Connect workflows. Extend, not replace, the core.

A configurable operating layer connects products, distribution and services across organizational boundaries.

01

Product change

Keep coverage, rates, disclosures and channel rules aligned as products change across sales touchpoints.

02

Partner handoffs

Align status, evidence and ownership when distributors, insurers and service partners handle the same order or claim.

03

Business feedback

Bring policy, claims and channel data together under agreed definitions to inform product and distribution decisions.

System responsibility map

Business touchpointsInsurers · Distribution partners · Enterprises

Non-motor insurance mid-officeProduct configuration · Workflows · Service coordination

Insurer core systemsPolicy, claims and finance records within the insurer’s remit

The mid-office serves surrounding workflows. Core responsibilities, data ownership and interfaces are agreed per project.

05 / 21

02 / BUSINESS BLUEPRINT

Three business domains. Five platform capabilities.

Scenarios define the use case; domains organize workflows; platform capabilities support delivery.

Four scenarios

Group accident & employers’ liability

SME commercial insurance

Employee & flexible benefits

Cargo & logistics insurance

Business domains

Product & distributionProducts · Underwriting rules · Distributors · Orders

Claims & value-added servicesClaims rules · Human / AI review · Service partners

Data analyticsPolicy / Claims data · Product / Channel P&L

Five capabilities

Non-motor insurance mid-office

AI underwriting

AI claims

Data & models

Open platform APIs

Connected foundation

Insurer core systemsExchange business records and status through agreed interfaces

Cloud & AI MaaS servicesDatabase · Logging · Security · Model services

Modules are selected by scope. Scenarios share capabilities, but retain their own risk fields, rules and service journeys.

06 / 21

03 / PRODUCT FACTORY

Turn insurance schemes into manageable components

Define what is covered, how it is priced, who is eligible and where it can be sold.

Coverage & rates

Configure coverage, limits, deductibles and pricing inputs for each product and scheme, keeping policy terms and quotes aligned.

Disclosures & inputs

Organize required fields, disclosures and evidence around the enterprise, insured people or cargo. Each scenario has its own information checklist.

Rules & versions

Associate eligibility and underwriting rules with product versions. Confirm when changes apply and how existing orders should be treated.

Channel release

Map schemes to authorized channels, application journeys and API fields. Validate sales scope and issuance flows during integration testing.

Configuration depends on insurer-supplied wording, rates, underwriting requirements and available core interfaces.

07 / 21

04 / DISTRIBUTION OPERATIONS

Link partner access, orders and reconciliation

Connect downstream sales partners with upstream insurers for policy and service operations.

Access → Orders → Settlement

Partner access: maintain distributor organizations and roles with authorized products and scope; sales access is separate from underwriting authority.

Linked orders: connect channel orders, applications and returned policy records, following acceptance, information requests and issuance status.

Service & settlement: use order and policy context for enquiries, endorsements and claims coordination; reconcile premiums, fees and order differences.

Fees and settlement responsibilities are agreed per project

Channel operations staff handling orders and data

Channel orders and settlement tracked on one chain

08 / 21

05 / GROUP ACCIDENT & EMPLOYERS’ LIABILITY

Manage occupational risk and workforce changes

Group accident and employers’ liability may share workforce data, but retain distinct coverage and underwriting rules.

01

Occupation classes

Capture industry, job roles and occupation classes. Check eligibility against the selected limits and coverage.

02

Member lists

Organize member identity and application data, check required fields and submit evidence required by the product.

03

Changes & renewal

Route additions, removals and updates through insurer endorsement processes. Reconfirm members, occupations and coverage at renewal.

Business objects

Enterprise & occupational riskIndustry · Occupation classes · Coverage needs

Group scheme + member listCoverage and limits sit alongside member information

Policy lifecycleIssue → Endorse members → Review for renewal

Not a product screenshot. Eligibility, endorsement effective dates and renewal terms remain subject to insurer confirmation.

09 / 21

06 / SME & CARGO SCENARIOS

Shared capabilities. Different risk information.

SME schemes address enterprise exposures; cargo and logistics journeys follow goods, transport and shipment orders.

SME enterprise property and engineering risk

SME COMMERCIAL INSURANCE

Multi-line schemes around the enterprise and its premises

Risk inputs: industry, address, assets and liability needs.
Coverage mix: property, liability and people cover, line by line.
Workflow: scheme selection, evidence and underwriting to issuance.

CARGO & LOGISTICS INSURANCE

Applications organized around goods and transport

Risk inputs: goods type, route, transport mode and sum insured.
Order linkage: waybills or transport orders with field mappings.
Service handoff: shipment data linked to policies and claims.

Final fields and coverage combinations depend on policy terms and available interfaces.

10 / 21

02

Operations & Integration

Application, underwriting and claims through to data and the open platform: AI and professional judgement on one chain.

11 / 21

07 / APPLICATION TO POLICY

Make each handoff explicit, from quote to policy

This is a business workflow, not a product screen. Payment and underwriting order varies by product and insurer process.

01 / CHANNEL

Select a scheme

Confirm the available product, coverage and version, then open the relevant application journey.

02 / APPLICANT

Submit inputs

Provide disclosures, risk fields, member or asset details and required supporting documents.

03 / REVIEW

Check & assess

Apply checks, request missing information and refer decisions requiring judgment to authorized reviewers.

04 / HANDOFF

Confirm & send

Confirm terms and follow the agreed payment flow and core interface to request policy issuance.

05 / INSURER

Return the policy

Receive policy records and status, link the channel order and connect subsequent policy servicing.

An exception is not completion

Missing documents, manual referrals and unconfirmed interface responses need follow-up. Submission alone does not establish cover.

12 / 21

08 / AI-ASSISTED UNDERWRITING

AI assists. Rules and underwriters retain control.

Extracted information and model prompts are not binding decisions. Review authority remains part of the workflow.

01 / INPUT

Extract

Read enterprise, member and asset details from application documents.
Return missing or uncertain inputs for follow-up.

→

02 / RULES

Validate

Check occupation, eligibility, limits and coverage conditions.
Associate the applicable product and rule version.

→

03 / ASSIST

Highlight

Bring together key evidence, rule results and open questions.
Support information requests or referral to an underwriter.

→

04 / REVIEW

Review & record

Authorized staff verify evidence and decide the next action.
Retain inputs, rule results and reviewer comments.

Document types, rule coverage and model integration are validated per project. Automation is not assumed for every line or application.

13 / 21

09 / CLAIMS OPERATIONS

Connect evidence, rules and partners around a claim

Notification, AI assistance, third-party coordination and human assessment form one service journey.

01

Intake & evidence

Link policy and incident information, collect required evidence, extract key fields and check document completeness.

02

Claims rules

Check coverage, limits and evidence requirements. Present open issues and assisted assessments to the reviewer.

03

Human review

Assess documents and partner feedback, record the decision and case status, and return results through agreed channels.

Third-party administration / TPA

Service requestsFurther evidence · Medical services · Loss surveys

Case coordinationRequest scope · Required documents · Status

Service resultsPartner findings support the claims reviewer

TPAs and service partners deliver agreed services; insurer claims authority is unchanged. Integration and data use are confirmed per project.

14 / 21

10 / VALUE-ADDED SERVICES

Connect third-party services to insurance journeys

Coordinate requests, partner delivery and status under agreed terms. External services are not presented as in-house delivery.

01 / PEOPLE & HEALTH

Occupational health & care

Optional connections include health screening, education, online medical services and care navigation. Scope depends on providers and local availability.

02 / RISK MANAGEMENT

Enterprise risk services

Connect safety training and disaster or severe-weather alerts where included in the scheme. Agree how services are triggered and who receives them.

03 / SCHEME LINKAGE

Services alongside cover

Associate services and eligible users with product schemes. Employee and flexible benefits are application scenarios, not an additional platform layer.

Confirm entitlement

Submit a request

Partner accepts & delivers

Track status & feedback

Services, geography, responsibilities and status updates depend on partner agreements and available interfaces.

15 / 21

11 / OPERATING ANALYTICS

Agree definitions before comparing performance

Connect policy, claims and distribution data. This view defines analysis scope, not projected financial results.

01

Portfolio views

Organize policy and claims data by product, scheme and distributor. Align observation periods and business status before making comparisons.

02

P&L definitions

Agree sources and allocation for premiums, claims and channel fees in product and distributor P&L analysis. Operating reports do not replace accounting records.

03

Reporting inputs

Connect the report center to policy and claims records. Analysis depends on the completeness and update arrangements of core and channel data.

04

Decision feedback

Take findings back to product, distribution and underwriting teams. Inform scheme, rule and operating changes without assuming automatic financial gains.

16 / 21

12 / OPEN INTEGRATION

Select integrations around the business journey

Open platform APIs connect core and surrounding systems. Identity, payments and third-party services are scoped per project.

Insurer core systems

Connect application, issuance, endorsement, claims and finance records using insurer-provided interfaces and status definitions.

Channels & identity

Connect distributor front ends, enterprise journeys and existing identity systems. Agree organizations, roles and business access.

Open platform APIs

Field & reference mapping
Requests & status updates
Access & call logs

Payments & settlement

Connect payment and reconciliation flows as agreed. Define the payee, payment timing and ownership of discrepancies.

Partners & models

Select TPA, service, risk-data or AI MaaS connections. Agree transmitted fields, permitted use and expected responses.

Confirm interface scope, data authorization, exception handling and acceptance tests. This map does not imply every integration is already in place.

17 / 21

13 / DEPLOYMENT & SECURITY

Design deployment and data boundaries together

Client environments, regulatory requirements and service scope shape the design. Technology choices do not establish compliance.

Runtime & integration

Plan deployment around business applications, data services and core connectivity. Confirm the pattern during solution design.

Environments: define runtime locations, network reach and production / test boundaries.
Observability: agree logging, monitoring and alerts, including who receives and acts on exceptions.
Continuity: agree backup, recovery and capacity arrangements, then include them in project validation.

Data & access

Bring permissions, data locations and key management into design, rather than checking them only before launch.

Identity: define access by organization, role and interface purpose.
Data & keys: agree storage locations, protection in transit and at rest, and local key-management boundaries.
Audit: agree operational records, third-party data use and retention requirements.

These are design and acceptance topics, not claims of certification, a fixed cloud stack, guaranteed availability or absolute security.

18 / 21

14 / OPTIONAL MULTI-MARKET REFERENCE

Shared governance. Market-specific runtime.

Optional design reference, not a list of delivered markets. Regulation, data flows and operating boundaries require local review.

Shared control plane

Singapore regional center / referenceConfiguration governance · Routing · Key policy · Monitoring · Report aggregation

Policy & insight flows

Governance policies sent to market nodes

Approved anonymized metrics returned for aggregation

Local runtime nodes

Korea / Country nodeLocal application runtime · Data · KMS boundary

Thailand / Region-native nodeLocal application runtime · Data · KMS boundary

Country X / Rollout templateReassess runtime and data boundaries for each new market

Central governance does not imply pooled transaction data

Design residency, key policy and access separately. Review aggregation fields, re-identification exposure and cross-border conditions; no absolute isolation is implied.

19 / 21

15 / IMPLEMENTATION

Start with one complete business journey

Select initial products and channels, then agree application, issuance and service scope. Timelines are project-specific.

01 · Scope

Map products, channels, roles and exception paths
Build the process, data and interface inventory
Agree the first business loop and acceptance criteria

02 · Configure

Configure coverage, application inputs and rules
Confirm channel access and scheme versions
Prepare test cases and integration environments

03 · Validate

Integrate the insurer core and selected partners
Check normal and exception state transitions
Verify evidence flows and business results

04 · Launch

Agree acceptance scope and cutover arrangements
Complete training and operations handover
Transfer open items to the operating teams

Delivery depends on joint preparation

Client inputs include wording, rules, test data, interfaces and approval owners. Scope, schedule and acceptance criteria are agreed together.

20 / 21

16 / OPERATION SUPPORT

Support product and channel operations after launch

Connect business teams, technology teams and partners. Responsibilities and service arrangements are agreed per project.

Product setup

Assist with configuration and checks on product inputs and rules. Prepare business validation for launches and subsequent changes.

API coordination

Support integration testing and issue investigation. Align business fields and processing status across insurers, channels and selected partners.

Channel support

Coordinate available schemes, application journeys and service handoffs. Follow up on business issues raised by distribution partners.

Service operations

Support enquiries, document follow-up and claims or value-added service coordination. Feed issues into product, channel and service reviews.

Support does not replace insurer or partner service responsibilities. Service hours, response arrangements and staffing are separately agreed.

21 / 21

ANLAA TECH