Skip to content
PERINGER Service Informatique, back to home

Back

Enterprise

Banking and insurance

Data-platform, application and AI-system design for banking and insurance. Integration of banking operations, market data or policies and claims, with historical models, APIs and deployment on cloud or private infrastructure.

Banking, payments and market data

Account movements, securities positions and market prices carry different dates and statuses. A pipeline preserves value dates, booking dates and data provenance. Instrument reference data and correction history support reconstruction of a position or valuation as of the selected date.

Examples of data processed in this sector

  • Accounts and payments

    Balances, entries, payment references and processing statuses feed cash-management services and accounting reconciliation.

  • Securities and portfolios

    Positions, transactions, ISIN identifiers, prices, currencies and corporate actions connect portfolios with vendor data.

  • Reporting and checks

    Aggregated data is reconciled with its sources and prepared using each report’s periods, definitions and formats.

Documented practices and systems in Switzerland

Public sources describing organisational practices and software interfaces. PERINGER project references appear separately below.

Insurance, policies and claims processing

An insurance policy changes through renewals or endorsements. A claim connects the relevant cover, notifications, supporting documents and benefits paid. Modelling preserves coverage periods and distinguishes paid amounts from reserves, preparing data for portfolio analysis and actuarial work.

Examples of data processed in this sector

  • Policies and coverage

    Policyholders, insured people or assets, coverage, premiums and endorsements form the contractual history.

  • Claims and benefits

    Occurrence and notification dates, supporting documents, assessments and payments describe the handling of a claim.

  • Portfolios and partners

    Premiums, claims costs and reserves feed analysis. Broker exchanges cover policies, documents and commissions.

Documented practices and systems in Switzerland

Public sources describing organisational practices and software interfaces. PERINGER project references appear separately below.

Engineering services

  • Data warehouses and historical models

    Relational and dimensional models for positions, transactions, policies or claims. Preservation of effective dates, corrections and calculation rules to supply applications, analysis and reporting with traceable data.

    Data platforms and warehouses →
  • Market feeds and financial reference data

    Ingestion pipelines for prices, instrument reference data and corporate actions. Identifier mapping, update processing and validation of units, currencies and dates before distribution to databases and calculation services.

    APIs and systems integration →
  • Banking APIs and data applications

    Development of services accessing accounts, transactions and positions through available interfaces and granted permissions. Portals and analytical applications preserve processing statuses and transaction references.

    Custom software and applications →
  • Policy and claims applications

    Web or mobile interfaces for viewing policies, submitting claim documents and tracking processing. Connectors link policy administration, case files, payments and broker exchanges, with access controls and change history.

    Custom software and applications →
  • Document AI and analytical services

    Data extraction and classification from financial or insurance documents, with source-passage references and field validation. Document search and API-connected agents operate within defined action and access permissions.

    Intelligent document processing →
  • Platform deployment and operations

    Infrastructure as Code, CI/CD pipelines and deployment of databases, APIs and processing services. Job monitoring, load checks and recovery procedures support replaying a feed without duplicating operations already integrated.

    Infrastructure automation →

Traceability, security and supervisory requirements

Technical controls follow the institution’s scope, the data processed and the functions outsourced. Engineering covers transformation traceability, access separation and recovery testing, with verifiable evidence for control and audit teams.

  • Data history, calculation-rule versions and reconciliation between sources, models and outputs
  • Application and portfolio permissions, restricted service accounts, encryption and operation logs
  • Controlled deployments, processing monitoring, restore tests and recovery of data pipelines
Applicable frameworks by institution

Banks and operational resilience

FINMA Circular 2023/1 covers ICT risks, cyber risks, critical data and continuity for institutions within its scope. It connects critical functions with their supporting resources and dependencies, applying the principle of proportionality.

View the source

Insurers and data controls

FINMA-supervised insurers have their own framework for governance, risk management and technical reserves. Software prepares and reconciles the policy, claim and payment data used in this work. Actuarial assumptions and approvals remain with the relevant specialist functions.

View the source

Cloud and outsourcing

FINMA Circular 2018/3 sets requirements for significant functions outsourced by the institutions concerned. The assessment includes the function inventory, responsibilities, provider monitoring, audit rights and options for bringing functions back in-house or transferring them.

View the source

Personal data and confidentiality

The revised Swiss FADP applies to data about identifiable individuals. Banks also account for banking secrecy. Service configuration examines purposes, retention, processor access and international transfers. Hosting location is one part of this assessment.

View the source

Incidents and notifications

The incident procedure provides for assessment of duties towards FINMA, the FDPIC and, where applicable, the NCSC. These notifications have different thresholds, deadlines and channels. Logs and provider information support documentation of the event and its consequences.

View the source

Related projects

2 projects

All my projects by sector →

Discuss your project

A discussion of your project’s design, development and production deployment.