Software for insurance brokers: from quotation to renewal in one management system

1. What insurance-broker software is

Insurance-broker software — also called broker management system, broker back-office, or technically Policy Administration System (PAS) for intermediaries — is the central system of the broker's back-office. It handles everything relating to the policy-customer-insurer relationship: from opening a customer record to issuing the policy, from managing deadlines to renewal, from claim notification to commission collection.

It differs from a generic CRM (which only manages pre-contractual commercial relationship) and from generic accounting software (which has no notion of class, premium, claims reserve). It is a vertical system: it speaks the insurance language and is born to comply with IVASS rules.

Which broker actually needs it

Typically: brokerage firms registered in RUI section B with a portfolio of at least 1,000-2,000 simultaneously managed policies, multiple principal insurers, a sub-broker or collaborator network, and a document volume to sign and preserve that makes Excel + email + shared folders inadequate. Below this threshold, a single-handed broker can still cope with generic tools; above, the absence of a management system generates three types of invisible cost: time lost in manual activities, non-compliance risk in IVASS audits, missed deadlines resulting in customer cancellation.

2. The 12 essential features today

A modern broker management system covers twelve functional areas. Every vendor implements them with varying depth: assessment during vendor selection must verify real coverage, not marketing claims.

2.1 Unified multi-insurer customer master data

A single customer with consolidated view of all policies issued through different insurers. Duplicate control on entry, address normalisation, integration with Italian Revenue Agency master data for VAT and tax-code validation. The customer is the foundation: everything else orbits around it.

2.2 Multi-line policy management

Issuance and management of policies across all lines operated by the firm: motor TPL, home multi-risk, professional liability, surety bonds, business TPL, accident, life classes I-III, credit insurance if handled. For bonds attached to public tenders, native integration with ANAC for CIG validation. For claims-made professional liability, correct modelling of retroactive and run-off — fundamental to avoid cover gaps.

2.3 Automatic renewal management

Integrated scheduler with 90, 60, 30 days deadline visibility. Automatic customer reminders via email/SMS, automatic renewal proposal generation, handling of any variations (sum-insured reduction, cover addition, premium change for tariff evolution). For Italian motor TPL, where automatic renewal has been banned since 2013 (D.L. 1/2012), correctly generating the 30-day notice before expiry is an IVASS obligation.

2.4 Deadline and reminder workflows

Beyond renewals, the scheduler manages all key dates: instalment payments, periodic services, annual reviews, retroactive expiry, run-off end, scheduled ATPs, hearings in pending-claim cases. Every deadline has a configurable reminder workflow (customer, internal operator, principal insurer).

2.5 Multi-level approval workflows

Delegated underwriting with authority rules per profile: collaborator quotes up to X, above X the broker principal, above Y back-office head approval needed. Each step is logged with mandatory motivation, forming a structured audit trail presentable in IVASS audits.

2.6 eIDAS electronic signature (FES, FEA, FEQ)

The three electronic signature families of eIDAS regulation, integrated in the issuance workflow:

• FES (Simple Electronic Signature): SMS/email OTP, for consents and low-probative-risk declarations;
• FEA (Advanced Electronic Signature): SPID/CIE + graphometric signature on tablet, for most retail and SME policies;
• FEQ (Qualified Electronic Signature): remote qualified certificate via CSC API, equivalent to handwritten signature (eIDAS art. 25), for bonds to PA, multi-million-euro policies, delegated underwriting authorisations.

2.7 Bidirectional PEC integration

Sending certified correspondence outbound (policy renewal, claim notice, guarantee call) and automatic ingestion of inbound PEC with classification (insurer PEC, customer PEC, claim counterparty PEC). Automatic match of inbound PEC with the relevant policy or claim. Decade-long compliant CAD preservation.

2.8 Document management and versioning

Unified repository for all policy, contractual, claims and communication documents: contracts, IPID, information booklets, expert reports, claim photos, correspondence. Automatic versioning, metadata classification, decade-long preservation via accredited AgID Preservation Provider. Full-text search powered by OCR for scanned documents.

2.9 Management KPI dashboard

Dashboards for the principal broker: monthly production vs prior year, customer churn rate, consolidated exposure by customer and insurer, top-10 customers by commission, claims ratio by line, portfolio concentration index. Drill-down by date, line, insurer, collaborator.

2.10 Reporting for principal insurers and IVASS

Automatic generation of periodic reporting to each principal insurer (policies issued, premiums collected, commissions earned, claims open). Standard reports for IVASS inspections: policies register, complaints register, AML register, training register, required audit trail.

2.11 REST APIs for external ecosystem

Exposure of documented REST endpoints for integration with online comparators, bancassurance partners, external CRMs, accounting systems of the firm, payment gateways. The ability to integrate without developing custom middleware is a decisive differentiating factor.

2.12 Multi-tenant cloud SaaS

System accessible via browser from any device, no local installation, with continuous updates without upgrade projects. Multi-tenant architecture: the broker doesn't manage servers, backups, IT security because everything is included in the service. Crucial for DORA compliance (see section 9).

3. Comparison: Excel vs CRM vs traditional management systems vs NewPicass

4. Multi-principal insurer handling

The typical Italian broker operates with 5-20 principal insurers simultaneously. Multi-principal handling is the most impactful factor on back-office operational efficiency.

A well-designed vertical management system natively handles: principal insurers master data with mandate conditions (commissions, underwriting authority, ceilings), per-insurer tariffs automatically imported or configured, bidirectional policy sync to each principal via API or file exchange, periodic reporting BDX in the format required by each, automatic reconciliation of commission movements with insurer statements, portfolio reassignments when the broker changes conditions with a principal.

Without this native feature, the broker ends up manually duplicating each policy entry in the individual insurer portals — a huge time cost growing linearly with volume.

5. IVASS compliance (Reg. 40/2018, RUI, AML)

The IVASS regulatory framework for the Italian broker articulates on five main axes:

• RUI section B registration: the broker must be registered in the Italian Insurance Intermediaries Register. The management system verifies via IVASS API its own and section-E collaborators' registration during onboarding.
• IVASS Reg. 40/2018 (distribution): pre-contractual information duties, IPID and information booklet, conflict of interest management, registration of distribution activity.
• IVASS Reg. 44/2019 (AML): customer due diligence, sanctions/PEP screening, UIF reporting for suspicious operations on life and investment classes.
• IVASS Reg. 24/2016 and subsequent (training): register of continuous professional training hours for each RUI registrant.
• Document preservation: all documents subject to preservation obligation (policies, communications, IPID delivery proofs) are sent to the accredited AgID Preservation Provider for compliant decade-long preservation.

An IVASS-ready management system embeds these requirements in its operational workflows, automatically generating the evidence and outputs that IVASS will require during inspection: typically six months before a formal inspection, an IVASS alert activates the broker to produce evidence — those with the management system have them ready, those without enter emergency mode.

6. eIDAS electronic signature and PEC integration

Digital signature and PEC are the two document-digitalisation tools of the broker. Their native integration in the management system eliminates manual steps, transmission errors and loss of delivery evidence.

eIDAS electronic signature articulates on three levels: FES for low-importance acts (consents, declarations), FEA for most retail and SME policies with SPID or CIE identification + graphometric signature on tablet, FEQ for high-probative-risk acts (bonds to PA, multi-million-euro policies, delegated authorisations). The signature workflow is embedded in the issuance process: at a click, the system generates the document, sends to the signer, awaits signature, time-stamps with AgID TSA, sends for decade-long preservation.

For PEC, preservation of acceptance and delivery receipts is mandatory. The management system natively handles sending and receiving, automatically classifies inbound PEC by sender and subject, matches with relevant case file. No more manual copy-paste between certified mail clients and local folders.

7. Deadlines, renewals and automatic workflows

The real ROI of the management system, from a business perspective, lies in reducing missed deadlines. A policy not renewed due to oversight is a cancelling customer — potentially moving to competitors.

The typical 90/60/30/15/7-day deadline workflow includes:

• T-90 days: internal alert to reference collaborator, renewal-condition check, possible re-quotation with principal insurer for tariff changes;
• T-60 days: first customer communication with renewal proposal and link for online acceptance/modification;
• T-30 days: IVASS-mandatory notice, renewal-document generation, possible re-signing;
• T-15 days: second customer reminder, internal escalation if no response yet;
• T-7 days: last reminder, possible direct call by collaborator;
• Post-expiry: grace-period handling (for policies that provide one), cancellation workflow if customer hasn't renewed.

8. KPI dashboards and reporting

For the broker principal, the KPI dashboard is the firm's pilot tool. Typical KPIs a modern management system must expose in real time include:

• Monthly production vs prior month vs prior year, in policy count and collected premiums;
• Churn rate monthly and annual (lost customers / total customers);
• Concentration: % of premiums on top-10 customers, top-20, etc. (to measure concentration risk);
• Production by collaborator, to identify top performers and under-performers;
• Claims ratio by line and by principal insurer (broker's loss ratio seen by the insurer);
• Renewal rate: % of policies renewed out of period expirations;
• Commercial pipeline: leads in progress, quotations sent, accepted, lost.

9. Enterprise security: ISO 27001, DORA, GDPR

The Italian broker is technically outside DORA's direct perimeter (EU Reg. 2022/2554), which formally applies to insurance and reinsurance undertakings. But it is indirectly involved because principal insurers — subject to DORA — must include the broker in their third-party register and perform IT-system due diligence on it.

For the broker, this translates into: ISO/IEC 27001:2023 certification of the management-system vendor, backup and disaster recovery evidence, proof of periodic penetration tests, exposure of traceable security logs. Full GDPR compliance: EU data residency contractually guaranteed, audit of data-subject rights exercisable from the customer portal, published sub-processors, contractual DPA per art. 28.

10. Cloud SaaS architecture and REST APIs

The modern broker management system is cloud-native multi-tenant. For the broker this means: access from any computer's browser, mobile included; no server to maintain, no backup to perform, no operating system patch to apply; continuous updates released by the vendor monthly or bi-monthly, no heavy upgrade projects; ISO 27001 certified European data centers included in the service.

Exposure of documented REST APIs (with OpenAPI/Swagger specification) enables integration with the broker's external ecosystem: comparators, bancassurance partners, possible commercial CRMs, payment gateways, firm's accounting. Integration capability is today a differentiating factor: an "island" management system requiring manual import/export is a time cost growing exponentially with portfolio.

11. Mobile app for the sub-broker network

For brokers with a sub-broker network or external collaborators operating in mobility, a native iOS + Android mobile app is now indispensable. Typical features: real-time quotation on enabled lines with limited offline availability, customer signing in mobility via graphometric or FEA, photo attachments for claims (with automatic recognition via OCR for standard documents), push notifications for portfolio deadlines, summary dashboard. Policies quoted on the app sync in real time with the principal broker's back-office for supervision and approval.

12. Implementation: timeframes, costs, legacy integration

A new broker management system adoption project averages 8-14 weeks from contract to go-live, broken into:

• Tenant setup + configuration (2-3 weeks): user and profile master creation, principal-insurer master loading, tariff configuration, document templates, roles and workflow;
• Historical data migration (3-4 weeks): export from current system (Excel too if applicable), data transformation with cleaning rules, import in two or three cycles with control reconciliation;
• Training + UAT (2-3 weeks): per-profile training sessions, guided testing on real flows with test data, fix of discrepancies surfaced;
• Controlled parallel + go-live (1-3 weeks): for a limited period old and new system coexist for new issuances, with final cutover managed over weekend or holiday.

The critical factor is almost never technical: it is the quality of historical data to migrate. Duplicate customer records, in-force policies with incomplete fields, pending claims never closed in the system are what slows real projects. An initial assessment on the firm's historical data is the first thing to do before choosing the vendor.

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

Three recurring scenarios among Italian brokers that have adopted a vertical management system (data anonymised by confidentiality agreements):

Case A — Independent broker Lombardy, 6,500 policies, 14 collaborators: the driver was an IVASS inspection concluded with observations on document traceability. In 12 weeks completed the transition from legacy system + Excel to SaaS management system. Result at 12 months: halved average renewal time, eliminated deadline losses, structured document compliance, subsequent IVASS audit passed without observations.

Case B — Broker specialised in surety bonds, Central Italy, 4,200 policies, 8 collaborators: the driver was the request from a large principal surety insurer to expose real-time policy sync via API. Migration from generic management system to vertical surety management system with native CIG/ANAC integration. Average time to issue a bid bond dropped from 18 minutes to 4 minutes, with automatic CIG validation eliminating the "non-existent CIG" error as the main source of contestations.

Case C — Multi-principal broker, Southern Italy, 11,000 policies, 22 collaborators, network of 35 sub-brokers: the driver was opening an external sub-broker network requiring mobile app + consolidated supervision. SaaS management system implementation with native iOS/Android app. Result: real-time visibility on the entire network production, supervision of cases opened by sub-brokers, 40% reduction in central back-office administrative time.

14. Frequently asked questions