Insurance companies — back-office, network supervision, compliance
Core system for surety insurers: multi-line portfolio management, coverholder-network supervision, claims, reinsurance, IVASS-ready audit trail, two-DC failover.
The 5 headaches of the surety insurer
Coverholder network out of control
20+ coverholders issuing policies on different systems, reporting via Excel at month-end, aggregating the consolidated position takes 3 analyst days.
Invisible exposure concentration
Customer with 10 policies issued by 4 different coverholders: without consolidated view the total exposure is invisible until a big claim happens.
Quarterly Solvency II reporting
QRT QRT QRT. Actuarial team reconstructs S.05/S.17/S.19 starting from SQL extracts, Excel, historical data. Always under stress.
Imminent IVASS audit
Scheduled IVASS inspection: process documentation, controls, big-claim audit trail, copies of policies issued 5 years ago. Without unified system: panic.
AS/400 migration
Legacy AS/400 still in production, expensive to maintain, missing know-how. Migrating = replacing the insurer's vital system. Perceived risk very high.
From \"surviving\" to \"governing\" the portfolio
| Insurer activity | Status quo | With NewPicass 14.Net |
|---|---|---|
| Consolidated coverholder-network view | 3 analyst-days in Excel | Real-time dashboard, drill-down to policy |
| Consolidated customer exposure | Invisible cross-coverholder | Automatic consolidation by tax code/VAT |
| Solvency II QRT | Manual quarterly reconstruction | Auto-populated, EIOPA-ready XBRL |
| IVASS audit | Weeks of preparation | Generated audit package + 10-year retention |
| AS/400 legacy | Expensive, no know-how | 6-12 month migration with parallel run |
| SLA / DR / BC | Internal best effort | 99.9% contractual, two active-active DC |
How the platform fits your role
Regulated insurer compliance
On a surety insurer with coverholder network
Frequently asked questions from insurers
Can insurers already running NewPicass 14.Net adopt it as PAS?
9+ European surety insurers already use NewPicass 14.Net as their core Policy Administration System (v14.0). "Company" configurations have stricter requirements vs coverholder configuration: contractual SLA, two active data centers, consolidated supervision of the entire delegated coverholder/broker network, legacy integration if the insurer has pre-existing systems.
How does it integrate with existing legacy systems?
Three configurable approaches: (A) REST/SOAP adapter wrapping the legacy and exposing it as API to NewPicass — useful when legacy remains source of truth for a specific module; (B) Bidirectional ETL via SQL Server SSIS or message broker — when both systems maintain their own source of truth; (C) Full migration with cutover — when legacy is to be retired. Typical insurer project: 6-12 months end-to-end.
How does coverholder-network consolidated supervision work?
The insurer sees in real-time the aggregated portfolio of all coverholders and MGAs reporting to them: consolidated exposure per customer/sector/geography, loss ratio per coverholder, performance vs SLA. Drill-down from total to individual policy issued by a broker in the sub-network. Configurable alerts (e.g. coverholder with loss ratio > 85% for 2 consecutive months).
Solvency II Pillar I for insurers: how?
The Analytics module automatically produces the QRT required by Pillar I: S.02 balance sheet, S.05 premiums/claims by LoB, S.17 technical reserves, S.19 claims by underwriting year, S.23 own funds. SCR (Solvency Capital Requirement) and MCR (Minimum Capital Requirement) computable via standard formula or partial internal model (with actuarial configuration). Ready for EIOPA submission via XBRL.
What contractual SLAs do you offer insurers?
For "Company" configuration standard SLA is: 99.9% monthly uptime (contractual penalties on miss), severity-1 24/7 support with response time < 1 hour, RPO ≤ 15 minutes, RTO ≤ 1 hour for disaster recovery, scheduled maintenance in night window with 7-day prior notice. For listed or regulated insurers with specific requirements 99.99% addendum with extended DR architecture is available.
Can we request SOC 2 reports?
Yes under NDA. We provide a public ISO 27001:2023 certificate + annual SOC 2 Type II report (on request). For regulated insurers the due-diligence package includes: ISMS policy, asset register, BIA (Business Impact Analysis), annual DR test report, incident response procedures, penetration test results. Typical for insurer CISO review during contractual onboarding.
See NewPicass 14.Net as it would work for a compagnia
45 minutes with one of our engineers. We show you concretely how the platform fits the specific workflows of your role — not a generic product demo.