Software for insurance companies: from policy portfolio to Solvency II

1. What a core system for an insurance company is

The core system of an insurance company — technically Policy Administration System (PAS) — is the central software that manages the end-to-end product lifecycle. It is the insurer's "system of record": the point through which every issued policy, every reported claim, every reinsurance cession, every premium and commission movement passes. Its quality directly determines operational efficiency, regulatory compliance and market response speed.

For mid-sized Italian insurers, the typical 2026 dilemma is replacing a legacy on-premise PAS (developed between 1995 and 2010) with a modern cloud SaaS PAS. Drivers are recurrent: DORA in force since 17 January 2025, wave of modern API integration demands (ANAC, AgID, Lloyd's, FatturaPA, SEPA ISO 20022), skill scarcity on the old platform, rising maintenance costs. The cloud transition is the dominant trajectory.

Which insurer needs it

Typically: Italian or European insurers authorised by IVASS or EU host authorities, with a policy portfolio above 30,000 active positions, one or more specialty lines (surety bonds, professional liability, credit insurance, Lloyd's specialty), structured reinsurance exposure (treaties + facultatives), a back-office team of 50-200 operational users. Below this threshold, even a well-configured vertical PAS may be over-engineering; above it, system criticality grows exponentially — it is the "core" system not figuratively, but because without it the insurer stops functioning within two weeks.

2. Multi-line policy issuance

Policy issuance is the first contact point between the core system and the real business. The maturity of the issuance engine is measured by its ability to handle multiple lines with native logic, not with custom configurations.

2.1 Surety bonds (CIG, L210, AGEA, joint ventures, customs)

For the surety line, NewPicass 14.Net is the historical domain: automatic CIG validation against the ANAC BDNCP at issuance time, templates for bid bonds, performance bonds, L210 VAT-refund policies, AGEA CAP agricultural-measure policies, ADM customs bonds, joint-venture management with shares and joint liability. Differentiated call workflow between first-demand and prior-execution, regress management and post-payment recoveries.

2.2 Professional liability (claims-made, retroactive, run-off)

For professional liability claims-made — almost universal in the Italian market — correct modelling of claims-made, retroactive and run-off is the critical point. A PAS that mismodels these extensions creates cover gaps (challengeable by the damaged party) or undue covers (paid claims that should not have been). NewPicass 14.Net natively handles: retroactive continuity in renewals, premium calculation for retroactive extension with IVASS-approved factors, mandatory 10-year run-off (L. 24/2017 Gelli-Bianco for doctors, L. 247/2012 for lawyers), insurer-change handling with retroactive recognition.

2.3 Credit insurance (per-buyer limits, recoveries)

For credit insurance the system handles per-buyer credit limits (individual cap on each commercial debtor of the insured), real-time integration with credit bureaus (Cerved, CRIF, Dun & Bradstreet), continuous rating monitoring with downgrade alerts, default-management workflow when the buyer doesn't pay, indemnification to the insured + subrogated recovery activation on the original debtor.

2.4 Standard P&C (motor TPL, kasko, home, accident)

For standard P&C in configuration: Italian motor TPL with ANIA BCM (Claims Database) integration and bonus-malus classes, kasko and ancillary covers, home multi-risk, individual and group accident. CARD/CID workflow for motor-claim direct settlement, ANIA SIC Clearing House reconciliation for inter-insurer flows. The platform is sized for high-concentration surety portfolios; for ultra-massive motor TPL portfolios (millions of policies) we recommend a dedicated PoC to validate performance.

2.5 Lloyd's specialty (marine, aviation, bilingual MRC)

For Italian coverholders operating under Lloyd's of London binders, the system handles bilingual Italian/English MRC (Market Reform Contract), Lloyd's class mapping to IVASS lines, premium and claims BDX in ACORD format for syndicates, coverholder and binder Atlas register. See the operational guide to MRC → local certificate workflow for the 6-step flow detail.

3. Premium handling and technical accounting

Insurance technical accounting is a specific sub-discipline, distinct from the general accounting handled by the ERP.

3.1 Per-line tariffs with customer overrides

Configurable rating engine per line with multiple parameters (master data, duration, sum insured, ancillary covers). IVASS-approved tariffs for your catalogue, with possibility of customer override within underwriting authorities. Every override is logged with motivation and applying profile.

3.2 Written, earned, ceded, retroceded premiums

Technical accounting distinguishes concepts that general accounting doesn't know: written premium (at policy issuance), earned premium (pro-rata temporis of the risk period already elapsed), ceded premium to the reinsurer (for the cession share), retroceded premium in retrocession programmes. Automatic reconciliation via SEPA pain.001 and camt.053 for collections and bank payments.

3.3 Premium and claims reserves

Premium reserve calculation (portion of premium not yet earned on in-force policies), claims reserve RBNS (Reported But Not Settled) and IBNR (Incurred But Not Reported). For formal actuarial reserves, data is periodically exported to the actuarial system (Prophet, ResQ) which applies chain-ladder, Bornhuetter-Ferguson or other actuarial methods on development triangles.

4. End-to-end claims management

The claims module covers the full cycle from notice to closure.

4.1 FNOL (First Notice of Loss) and classification

Claim opening via web portal, mobile app, PEC from principal or beneficiary. Automatic classification by type (motor TPL, professional liability, surety call, etc.) and severity with configurable rules. Automatic allocation to claims handler based on competence and workload.

4.2 Reserve, expert assessment, litigation

Initial reserve calculation with line-standard methodologies, periodic revisions with audit trail, expert or lawyer appointment by amount and complexity. For professional liability, management of ATP (pre-litigation expert assessment under art. 696-bis Italian c.p.c.) mandatory for healthcare PI. For surety, differentiated call workflow between prior-execution and first-demand.

4.3 Payment and recovery/regress activation

Payment via SEPA SCT with pain.001 to the beneficiary. For surety, automatic activation of the regress workflow on the guaranteed principal post-payment: demand letter, possible repayment plan, judicial litigation, recoveries tracking. For credit insurance, activation of subrogated recovery workflow on the original debtor.

4.4 IBNR reserves and development triangles

Generation of development triangles by occurrence year × reporting year × payment year, exported to the actuarial system for formal IBNR calculation. For long-tail lines (claims-made professional liability), retroactive and run-off recognition in reserve calculation.

5. Reinsurance: treaties and facultatives

The reinsurance module is central for surety insurers, where structured cession is the norm. NewPicass 14.Net natively handles:

• Proportional treaties: quota share with automatic fixed-share allocation, surplus with configurable retention and progressive cession above retention;
• Non-proportional treaties: excess of loss with calculation of the share exceeding retention, CAT XL for catastrophic-event protection;
• Facultatives: single cession with reinsurer consultation workflow before issuance (for large or atypical risks above treaty capacity);
• Retrocession: reinsurance of the reinsurer for those accepting inbound cessions.

Quarterly generation of ACORD-standard bordereaux for reinsurers (Munich Re, Swiss Re, Hannover Re, SCOR) and Lloyd's market. Automatic reconciliation of technical accounts (ceded premiums, ceded claims, ceding commission, profit commission). Recoveries tracking on both cedent and reinsurer side.

6. Multi-level approval workflows with delegations

Delegated underwriting with decision-authority rules per user profile: agent quotes up to limit X, above X the in-house underwriter, above Y the head of underwriting, above Z technical management. Each step is logged with mandatory motivation, forming a structured audit trail presentable in IVASS audits. For complex-underwriting lines (specialty, marine, aviation, high-exposure surety) integration of reinsurer or Lloyd's syndicate-leader consultation workflow before issuance.

7. Solvency II readiness (Pillars 1, 2, 3)

Solvency II (Directive 2009/138/EC) mainly touches the PAS on Pillars 1 and 3. Read the Solvency II compliance guide.

7.1 Pillar 1 — capital requirement (SCR/MCR)

Solvency Capital Requirement (SCR) and Minimum Capital Requirement (MCR) calculation is performed by the actuarial system from data provided by the PAS: earned premiums by line, claims paid by occurrence year, claims reserves (RBNS + IBNR) with development triangles, reinsurance cession data, exposure by business line and geographic area. The PAS provides structured inputs in standard formats required by the actuarial system.

7.2 Pillar 2 — governance and ORSA

Pillar 2 (governance and Own Risk and Solvency Assessment) requires organisational processes more than software functionality. The PAS contributes with: immutable audit trail of every operation, data quality and traceability to support ORSA, documented evidence for the four key functions (risk management, actuarial, compliance, internal audit).

7.3 Pillar 3 — transparency and reporting

Generation of standardised extracts for periodic QRT (Quantitative Reporting Templates) transmitted to IVASS in XBRL format, annual RSR (Regular Supervisory Report) complete, public SFCR (Solvency and Financial Condition Report). For Italian surety insurers, integration with IVASS statistical reporting of premiums and claims by line.

8. IVASS audit trail and DORA compliance

DORA (EU Reg. 2022/2554, applicable since 17 January 2025) reorganised the ICT resilience framework for the financial sector. For insurers, evidence required during inspection is five-fold:

1. Documented ICT risk management framework with clear governance;
2. Asset inventory and business impact analysis with process and criticality (RTO/RPO) mapping;
3. Up-to-date third-party register in RT ESA format, with focus on critical providers (including cloud PAS);
4. Incident log with applied classification and IVASS-notification evidence;
5. Annual test plan with results of the latest executed test (penetration test, BCP test, DR test).

NewPicass 14.Net directly contributes to items 2 (PAS vendor asset inventory), 4 (security log exposure), 5 (quarterly DR-test evidence). For other elements (governance, documented framework) the PAS contributes with audit trail and data quality.

For IVASS Reg. 38/2018 (corporate governance): immutable audit trail, segregation of duties, operational delegation register, product-approval log.

9. Multi-data-center EU architecture

NewPicass 14.Net operates on two EU data centers in active-active mode:

• Strasbourg (France) — primary;
• Roubaix (France) — secondary.

Both within the European Economic Area to ensure EU data residency compliant with GDPR. Synchronous replication of the transactional database, geographic load balancer for web farms, automatic failover on primary degradation with documented RPO ≤ 15 minutes and RTO ≤ 1 hour. Quarterly failover tests with tabletop exercises + annual live night-time switch exercise with post-test sign-off. SQL Server 2022 cluster with automatic failover, nightly backups and hourly transaction logs.

10. Comparison: legacy on-premise vs modern SaaS vs NewPicass

11. Implementation and migration

For a mid-sized surety insurer (50,000-150,000 policies, 50-100 users) average contract-to-go-live time is 12-18 months:

• Assessment + fit-gap (2-3 months): mapping existing processes, functional gap analysis, historical data quality assessment;
• Implementation + configuration + integrations (5-9 months): tenant setup, tariff configuration, document templates, approval workflows, integration with actuarial system, ERP, peripheral systems;
• Integrated testing + UAT (2-3 months): end-to-end testing on real scenarios, key-user training, iterative fixes;
• Controlled parallel run + cutover (2-3 months): dual system for new issuances with accounting reconciliation, final cutover managed in a controlled window.

The dominant pattern for migration is the strangler pattern: the new PAS handles new products and new renewals, the legacy continues for natural run-off of the historical portfolio over 2-5 years, then is decommissioned. This approach minimises big-bang risk and enables progressive process migration.

12. Vendor selection — 10 criteria for technical leadership

For those tasked with leading a new PAS selection, recommended criteria:

1. Functional fit to your lines with referenced customer examples in your niche;
2. Cloud SaaS multi-tenant architecture with EU-exclusive data residency and documented DORA-readiness;
3. Documented OpenAPI REST APIs with real integration examples (CRM, ERP, banks, actuarial);
4. Built-in compliance: IVASS Reg. 38/40/44, IDD, eIDAS, AgID preservation, Solvency II, ISO 27001:2023;
5. Complete reinsurance module: proportional + non-proportional + facultatives + retrocession, ACORD BDX;
6. End-to-end claims module: FNOL, reserve, expert assessment, regress/recoveries, development triangles;
7. Immutable audit trail: every operation tracked, applicable segregation of duties, exportable logs;
8. Public roadmap: visibility on evolutions in the next 12-24 months;
9. Vendor sustainability: years on market, referenced customers in your line, financial standing;
10. Exit strategy: contractual clauses for data extraction, termination, portability (mandatory per DORA art. 30).

13. Real use cases (3 anonymised mini-cases)

Case A — Italian surety insurer, 80,000 policies/year, 90 users: driver = replacement of legacy PAS at original vendor's end-of-life. 14-month migration with strangler pattern: NewPicass 14.Net in production for new products and renewals from month 8; legacy in run-off for historical portfolio until month 36. Result at 24 months: bid bond issuance time dropped from 14 min to 3 min with automatic ANAC CIG; DORA compliance passed in 2025 IVASS inspection without observations; on-premise infrastructure costs eliminated.

Case B — Italian Lloyd's coverholder, 5 active binders, 40 users: driver = syndicate-leader request to expose monthly premium BDX within the 10th working day of the following month. 9-month NewPicass 14.Net implementation with focus on ACORD BDX and bilingual MRC. Result at 12 months: 100% BDX timeliness (zero delays over 60 binder-months); exception rate dropped from 7% to 0.8%; annual Lloyd's audit closed without findings.

Case C — European insurer operating under FoS from Italy in 3 EU countries, 35,000 policies, 60 users: driver = unification of three different national PASs into a single multi-currency, multi-language PAS, compliant with each host country's information requirements. 18-month implementation with progressive country-by-country migration. Result at 24 months: 60% reduction in administrative back-office staff, consolidated cross-country supervision, automatic local POG compliance per country.

14. Frequently asked questions