Policy administration software, also called a policy administration system or PAS, is the core system an insurer, managing general agent (MGA) or broker with delegated authority uses to set up its insurance products and to record and process each policy from quotation to cancellation or expiry. It holds the record of every policy and of every transaction made to it.
This entry explains what a policy administration system does at each stage of a policy's life, how products are configured in it and the data and regulatory outputs that UK rules, Lloyd's standards and IFRS 17 expect it to supply. It then sets out how the software is deployed, what the PRA and FCA expect when it is outsourced or run in the cloud, the data standards it uses and what published survey evidence shows about legacy systems and their replacement.
What policy administration software is
PAS stands for policy administration system, and the same abbreviation is used for policy administration software. "Policy admin system" and "policy management system" are other names for the same kind of software. Policy administration is also the name of the work itself: issuing, changing, renewing and cancelling policies after the sale.
A policy administration system is one of the core systems of an insurance business, alongside claims and billing systems. Where one supplier provides all three on a shared record, the combination is described as a core insurance platform or suite. Around the policy record sit other systems that exchange data with it: a rating engine that calculates the premium, an underwriting workbench where underwriters review referred and complex risks, customer and broker portals, document services and third-party data services.
This entry concentrates on general insurance, where a policy is written for a period of cover and is then renewed, cancelled or allowed to lapse. Life and annuity contracts stay in force for much longer, which shapes the systems that administer them. The survey evidence cited here comes from North American life insurance.
The policy life cycle in a policy administration system
A policy administration system processes a fixed set of transactions over the life of each policy. The figure sets them out in order, and the table shows what the system records at each stage and how the stage is reported where business is written under a Lloyd's binding authority.
The policy life cycle, as processed by a policy administration system
| Stage | What the system records | Lloyd's risk and premium reporting |
|---|---|---|
| Quotation | The risk details collected, the premium offered and any referral and its outcome | No risk transaction type: the standards cover bound risks, premiums and claims |
| Bind and issue | Inception and expiry dates, sum insured, excess, premium, tax, commission and the documents issued | New business, with the risk inception date (CR0030) and risk expiry date (CR0031) |
| Mid-term adjustment | The change, its effective date and any additional or return premium; a change to the cover is documented as an endorsement | Endorsement where there are financial changes (an amendment where all changes are non-financial), with the effective date of the transaction (CR0057) |
| Renewal | The renewal terms and, for UK consumer home and motor policies, the renewal price and the equivalent new business price | Renewal, for business previously placed under a Lloyd's binding authority |
| Cancellation | The cancellation date, any return premium and the reason | Cancellation, with a reason from recommended values such as "Product cancelled within cooling off period"; the reason is mandatory for some business, including UK Flood Re and South Africa |
| Lapse | Expiry of cover without renewal | No transaction type for expiry; the expiry date (CR0031) is reported at binding |
Billing, claims and reporting draw on the same record. A billing system collects the premium recorded at each transaction, a claims system checks the cover in force on the date of loss when a claim is made at first notification of loss, and management reports and bordereaux are produced from the policy data. Because every transaction carries its own effective date, the record can show the cover, premium and documents that applied on any given day.
Products, configuration and customisation
A product in a policy administration system is the set of questions, rules, rates and documents that apply to one type of cover. A product is set up or changed through configuration, customisation or both. In an agenda decision published in April 2021, the IFRS Interpretations Committee set out the descriptions given in the request it considered: configuration involves setting "flags" or "switches" within the application software, or defining values or parameters, so that the software's existing code functions in a specified way, while customisation involves modifying the software code in the application or writing additional code, and generally changes, or creates additional, functionalities within the software.2
The two differ in who makes the change and how it is released. Adding a question to a proposal form, changing a rate table, setting an excess or editing a document template are examples of changes that a system can allow through configuration, made by business users where the system and the firm's controls permit. A new type of calculation or an integration the software does not support needs customisation, which developers write and test before release. Each product version carries the date from which it applies, so that a mid-term change or a claim is assessed against the version that was in force on the relevant date. How the premium itself is calculated is covered in the entry on rating engines.
Data and regulatory outputs
Much of what a policy administration system must produce is set by rules that apply to the firm rather than to its software. The firm remains responsible for meeting each rule; the policy record holds the data the firm uses to do so. The table lists the main outputs for a UK general insurance business and the rule or standard behind each.
| Output | What it contains | Rule or standard |
|---|---|---|
| Renewal price and equivalent new business price (ENBP) | For each UK consumer home or motor renewal, a renewal price no higher than the ENBP, worked out on the channel the customer first used | ICOBS 6B.2.1R and 6B.2.5R3 |
| Records of pricing by tenure | The assessments and controls showing that ENBPs for longer-standing customers do not systematically exceed those for new customers | ICOBS 6B.2.51R3 |
| Home and motor pricing returns | Information on consumer home and motor contracts (excluding commercial customers and group policies), add-on policies and retail premium finance, in a standard format | SUP 16.28, inserted by instrument FCA 2021/19 (as made in 2021; later amendments not reviewed)4 |
| Consumer outcomes monitoring | Evidence of whether products provide fair value and whether any group of retail customers is getting different outcomes from another group with the same product | PRIN 2A.9.8R to 2A.9.10R5 |
| Records of business | Adequate records of matters and dealings for insurers, managing agents and the Society of Lloyd's; orderly records of all services and transactions for other firms | SYSC 3.2.20R6; SYSC 9.1.1R78 |
| Risk and premium bordereaux for Lloyd's | Risk and paid premium fields, of which those marked red are mandatory and those marked yellow are conditional | Lloyd's Coverholder Reporting Standards, version 5.21 |
| Core Data Record | Transactional data captured at written line for premium validation and settlement, claims matching, tax and regulatory reporting | Core Data Record v3.2, London Market Group Data Council9 |
| IFRS 17 groups of contracts | The portfolio, year of issue and profitability group of each contract | IFRS 17 Insurance Contracts1011 |
Renewal pricing records
For home and motor insurance sold to consumers, chapter 6B of the Insurance Conduct of Business Sourcebook (ICOBS) applies where a firm sets the renewal price, sets the price of an additional product offered at renewal or determines its remuneration at renewal.3 ICOBS 6B.2.1R states that a firm must not set a renewal price higher than the equivalent new business price, and that this applies at the point the renewal notice is prepared.3 In working out the equivalent new business price, ICOBS 6B.2.5R requires the firm to assume that the customer approached it through the same channel they used when they first bought the policy, which depends on the policy record keeping that channel.3
Firms must also make and retain written records. ICOBS 6B.2.51R lists what they cover: the assessment of whether equivalent new business prices for customers of longer tenure systematically exceed those for new customers, the controls on any pricing model used to generate them, the evidence on fair value for longer-standing customers, the assessment of fees and any independent oversight of these.3 Guidance at ICOBS 6B.2.56G gives examples, including minutes of any pricing committee and analysis of whether similar customers face different pricing outcomes, while guidance at ICOBS 6B.2.58G reminds firms of SYSC 3.2.20R and SYSC 9.1.1R and points to the guidance in SYSC 3.2.21G and SYSC 9.1.5G, including the general principle that records should be retained for as long as is relevant for the purposes for which they are made.3
The FCA also collects pricing data. Its instrument FCA 2021/19, published with policy statement PS21/5, inserted SUP 16.28, which requires firms within its scope, including insurers, managing agents and insurance intermediaries, to submit information on their home and motor contracts, add-on policies and retail premium finance in a standard format; policies entered into by commercial customers and group policies are excluded.4 Guidance at SUP 16.2.1G(4), as inserted, states that the purpose of SUP 16.28 is to give the FCA data it can use to assess compliance with ICOBS 6B, identify potential harm to consumers and monitor the effect of the pricing rules on the market.4
Consumer Duty monitoring and records
Under the Consumer Duty, PRIN 2A.9.8R requires a firm to regularly monitor the outcomes retail customers receive from the products it manufactures or distributes, its communications and its customer support.5 The monitoring must enable the firm to determine, among other things, whether the products retail customers buy provide fair value, and to identify whether any group of retail customers is experiencing different outcomes compared with another group of retail customers of the same product.5 Guidance at PRIN 2A.9.4G says the obligation applies proportionately to a firm's role in the distribution chain.5 Policy records of sales, renewals, mid-term changes and cancellations are one source of the data for that comparison.
For non-investment insurance, the test of fair value at product approval sits in PROD 4.2.14AR, which requires the product approval process to identify whether the product provides fair value to customers in the target market, including whether it will continue to do so for a reasonably foreseeable period after renewal.12 Guidance at PRIN 2A.9.15G points firms to the high-level record-keeping requirements in SYSC 3 and SYSC 9 and leaves them to decide which records they need for the Duty.5
Those record-keeping rules differ by type of firm. SYSC 3.2.20R, which applies to insurers, managing agents and the Society of Lloyd's, requires a firm to take reasonable care to make and retain adequate records of matters and dealings which are the subject of requirements and standards under the regulatory system, capable of being reproduced in the English language on paper.6 For other firms, such as insurance intermediaries, SYSC 1 Annex 1 applies SYSC 9.1.1R as a rule: it requires orderly records of the firm's business and internal organisation, including all services and transactions, sufficient for the FCA to monitor compliance.78
Bordereaux and Lloyd's data standards
Under delegated authority, the policy administration system of the coverholder or MGA is the source of the bordereaux sent to each capacity provider. For the Lloyd's market, the Coverholder Reporting Standards state the core set of regulatory, tax, premium and claims information that coverholders and delegated claims administrators are required to report, for all classes of business in all territories.1 Lloyd's mandated that syndicates request and collect data consistent with the standards for risks and claims attached to binding authority agreements incepting or renewing from July 2017 onwards, and has not mandated a particular format.1 Some fields apply only in certain territories or classes: the reason for cancellation, for example, is mandatory for UK Flood Re and South Africa among others.1
For the London open market, the Core Data Record holds the critical transactional data to be captured at written line for four downstream processes: premium validation and settlement; claims matching at first notification of loss; tax validation and reporting; regulatory validation and core reporting.9 The London Market Group Data Council published version 3.2 on 29 March 2023, alongside version 3 of the Market Reform Contract.9 In March 2022 the Data Council agreed that ACORD would be the market's data standards methodology, with the content of the Core Data Record aligned to ACORD's Global Reinsurance and Large Commercial standard.13
IFRS 17 data
IFRS 17 Insurance Contracts is effective for annual reporting periods beginning on or after 1 January 2023.10 It measures insurance contracts in groups. A company first identifies portfolios, each a set of contracts subject to similar risks and managed together, and then divides each portfolio into groups by expected profitability: contracts onerous at initial recognition, contracts with no significant possibility of becoming onerous, and the remainder.11 Only contracts issued within the same year can be included in the same group.11
The product and issue date held in the policy record are the starting points for allocating each contract to a portfolio and an annual group, and the premium and cover data feed the profitability assessment. The IFRS Foundation's project summary notes that a company may have more groups than the minimum, for example where its internal reporting distinguishes the possibility of contracts becoming onerous at a more granular level.11
Deployment models: on-premise, hosted and SaaS
A policy administration system is delivered in one of three broad ways, and the way it is delivered affects how UK regulators' documents classify the arrangement. Software as a service (SaaS) is the model in which the supplier runs one application and each firm uses it over the internet.
| Model | What it is | Who runs the software | How the regulators' documents treat it |
|---|---|---|---|
| On-premise | Licensed software installed on the firm's own servers or in its own data centre | The firm | The PRA lists purchases of software and the design and build of an on-premise IT platform among examples of non-outsourcing third party arrangements, but still expects firms to assess the materiality and risks of all third party arrangements14 |
| Hosted or managed | The firm's own instance of the software, run for it by the supplier or another provider in a data centre or the cloud | The provider, under contract | The FCA says that where a third party delivers services on behalf of a regulated firm, including a cloud provider, this is considered outsourcing; the statement applies equally to SaaS15 |
| Software as a service | One application run by the supplier and used by many firms over the internet | The supplier | The FCA includes SaaS in what it means by cloud, so its statement that delivery by a third party, including a cloud provider, is outsourcing applies here too15; under the shared responsibility model described by the PRA, the firm remains responsible for classifying its data, taking a risk-based approach to where data is located and configuring and monitoring its data in the cloud14 |
SS2/21 applies to insurers and groups in scope of Solvency II, including the Society of Lloyd's and managing agents.14 FG16/5 is relevant to firms authorised under the Financial Services and Markets Act 2000 other than banks, building societies and certain investment, payment and e-money firms, and the FCA describes it as not binding.15
What regulators expect when the software is outsourced
Where a hosted or SaaS policy administration system supports critical or material functions, the outsourcing rules and expectations apply. They are set out differently for insurers and for other FCA-regulated firms.
| Expectation | Insurers and Lloyd's managing agents | Other FCA-regulated firms, such as MGAs and brokers |
|---|---|---|
| Responsibility stays with the firm | The binding outsourcing rules for these firms are in the PRA Rulebook, including Conditions Governing Business 7, which SS2/21 elaborates14; in the FCA Handbook, SYSC 3.2.4G: a firm cannot contract out its regulatory obligations and should take reasonable care to supervise the discharge of outsourced functions6 | SYSC 8.1.6R: a firm that outsources critical or important operational functions remains fully responsible for discharging all of its obligations, applied to these firms as a rule168 |
| What counts as material | SS2/21 paragraph 5.11: generally material where a defect or failure could materially impair, among other things, the firm's ability to meet the Threshold Conditions, its operational resilience or, for insurers only, policyholder protection14 | SYSC 8.1.4R: critical or important where a defect or failure would materially impair continuing compliance, financial performance or the soundness or continuity of the firm's services, applied to these firms as guidance168 |
| Telling the regulator | Notify the PRA before entering into or significantly changing a material outsourcing arrangement (SS2/21 paragraph 5.14)14; from 18 March 2027, notify all material third party arrangements through FCA Connect (PS7/26)17 | SYSC 8.1.11R: make available to the FCA on request all information necessary to supervise the outsourced activities, applied to these firms as guidance168 |
| Planning an exit | For each material outsourcing arrangement, a tested business continuity plan and a documented exit strategy covering both stressed and non-stressed exits (SS2/21 paragraph 10.1)14 | FG16/5: exit plans and termination arrangements that are understood, documented and fully tested, including how data would be removed from the provider's systems15 |
Operational resilience and critical third parties
The FCA's operational resilience rules, set out in policy statement PS21/3, came into force on 31 March 2022 and apply to firms including insurers and enhanced scope senior managers and certification regime firms.18 They require firms to be able to remain within their impact tolerances as soon as reasonably practicable, and no later than 31 March 2025.18 The PRA's supervisory statement SS1/21 sets the same deadline for the firms it regulates, and explains that the PRA's rules require firms to be able to deliver their important business services within impact tolerances in severe but plausible scenarios.19 Where a firm identifies a service such as issuing or renewing policies as an important business service, the policy administration system behind it would be among the resources it maps and tests.
The regulators also oversee some suppliers directly. Under section 312L of the Financial Services and Markets Act 2000, as amended, HM Treasury may designate a third party as critical if a failure in, or disruption to, the services it provides to firms could threaten the stability of, or confidence in, the UK financial system.20 On 10 July 2026 HM Treasury announced that it had designated four major global cloud services and technology providers as critical third parties, whose critical services to the financial sector the Bank of England, PRA and FCA will oversee jointly.21 The regulators state that this oversight regime does not eliminate, reduce nor replace the accountability of firms, their boards and senior management.20
Connections and data standards
A policy administration system exchanges data with rating engines, billing and payment services, claims systems, document services, portals, finance systems and data providers, through an application programming interface (API) or file transfer. Some systems are built as microservices, small services that each handle one function, such as rating or document production, and call one another through APIs. Straight-through processing of a quote or mid-term change depends on connections of this kind.
Common data formats come from ACORD, a non-profit, industry-owned standards body which says it engages more than 36,000 participating organisations in more than 100 countries.22 ACORD describes its Property and Casualty XML and AL3 standards as also relevant for delegated authority, and its Global Reinsurance and Large Commercial standards as covering claims, placing and accounting and settlement.23 Its Next-Generation Digital Standards are intended for fine-grained transactions such as microservices and RESTful APIs.24
Legacy systems and modernisation
Published survey data on legacy policy administration systems is limited and comes mainly from North American life insurance. A 2017 report was based on a survey conducted in summer 2016 by LIMRA, a US-based research and trade association for life insurers and financial services firms, of 58 companies in the United States and Canada; the commentary in the report is Deloitte Consulting's, and Deloitte did not validate the survey data.25 Respondents reported having from one to 26 policy administration systems, with an average of 4.0 and a median of 2.0, and nearly half (46%) had completed changes and updates on at least one legacy system.25
Legacy policy administration systems at North American life and annuity insurers
Product strategy was the highest rated driver, and when asked for the single most influential driver, one in five respondents chose product speed to market or policy volume growth.25 Among companies with more than one legacy system, the report found that about half were attempting to modernise them all at once, while those upgrading separately often started with their smaller systems.25
Asked which approaches they had actually chosen, the 42 companies answering most often named convert and retire (50%) and replace and retire (48%), followed by installing a new system and upgrading the existing one (36% each).25 The report defines retiring a solution as eliminating it through the conversion of policies or the consolidation of software, and replacing as implementing a new solution for future sales, with or without converting existing policies.25 The answers are not mutually exclusive, because companies with several systems may choose different approaches for each.25 The survey covers life and annuity business and does not cover UK general insurance.
Replacing a policy administration system
Replacing a policy administration system involves moving policy, customer and transaction records from the old system, a process covered in the entry on data migration. A replacement can move every product at once, or move products in stages with the old and new systems running side by side until the remaining policies on the old system have expired or renewed onto the new one. In the LIMRA survey, roughly two in five companies (39%) had one legacy system, and one respondent described the migration of current policies and associated agent management data as the single greatest challenge in modernisation.25
For a firm whose current system is hosted or provided as SaaS, a replacement is also a planned exit from an outsourcing arrangement, which the PRA describes as a non-stressed exit for commercial, performance or strategic reasons.14
Show References Hide References
- Lloyd's. Coverholder Reporting Standards User Guide, Version 5.2. 20 August 2019.
- IFRS Interpretations Committee. Configuration or Customisation Costs in a Cloud Computing Arrangement (IAS 38 Intangible Assets). IFRIC Update March 2021, agenda decision published April 2021.
- FCA Handbook. ICOBS 6B: Home insurance and motor insurance pricing (6B.1 and 6B.2). Read 10 November 2026.
- Financial Conduct Authority. PS21/5: General insurance pricing practices market study, Feedback to CP20/19 and final rules. May 2021, including instrument FCA 2021/19.
- FCA Handbook. PRIN 2A.9: Monitoring of consumer outcomes. Read 10 November 2026.
- FCA Handbook. SYSC 3: Systems and controls. Read 10 November 2026.
- FCA Handbook. SYSC 9.1: General rules on record-keeping. Read 10 November 2026.
- FCA Handbook. SYSC 1 Annex 1: Detailed application of SYSC. Read 10 November 2026.
- Lloyd's. Core Data Record. Read 10 November 2026.
- IFRS Foundation. IFRS 17 Insurance Contracts. Read 10 November 2026.
- IFRS Foundation. IFRS 17 Insurance Contracts: Project Summary. May 2017.
- FCA Handbook. PROD 4.2: Manufacture of insurance products. Read 10 November 2026.
- ACORD, courtesy of London Market Group. Data Council Agrees ACORD Standards Adoption and Content for Core Data Record. 31 March 2022.
- Prudential Regulation Authority. SS2/21: Outsourcing and third party risk management. November 2024 update.
- Financial Conduct Authority. FG16/5: Guidance for firms outsourcing to the 'cloud' and other third-party IT services. July 2016, updated September 2019.
- FCA Handbook. SYSC 8.1: General outsourcing requirements. Read 10 November 2026.
- Prudential Regulation Authority. PS7/26: Operational resilience: Operational incident and third-party reporting. 18 March 2026.
- Financial Conduct Authority. PS21/3: Building operational resilience. March 2021.
- Prudential Regulation Authority. SS1/21: Operational resilience: Impact tolerances for important business services. March 2022.
- Bank of England, Prudential Regulation Authority and Financial Conduct Authority. The Regulators' approach to the oversight of critical third parties. November 2024.
- HM Treasury. UK financial system strengthened with new safeguards for major technology providers. Press release, 10 July 2026.
- ACORD. About ACORD. Read 10 November 2026.
- ACORD. ACORD Data Standards. Read 10 November 2026.
- ACORD. Next-Generation Digital Standards. Read 10 November 2026.
- LIMRA and Deloitte. Legacy systems and modernization: Core systems strategy for policy administration systems. 2017. Survey of 58 life and annuity insurers in the United States and Canada, summer 2016.
Frequently Asked Questions
How are the costs of SaaS policy administration software treated in the accounts?
Under IFRS Accounting Standards, the IFRS Interpretations Committee's April 2021 agenda decision considered a SaaS arrangement in which the contract gives the customer a right to receive access to the supplier's software over the contract term. That right does not give the customer a software asset, so the access is a service received over the term. The Committee observed that the customer often would not recognise an intangible asset for configuring or customising the software, because it does not control the software and the work does not create a separate resource it controls. The exception is where the arrangement produces, for example, additional code from which the customer can obtain the economic benefits and restrict others' access; the customer then assesses whether that code is identifiable and meets the recognition criteria in IAS 38.
Where no asset is recognised, the agenda decision explains that the cost is an expense when the configuration or customisation services are received, which is when the supplier performs them under the contract. If the contract for the work is with the software supplier (including where it subcontracts the work to a third party) and the services are distinct, the cost is expensed as the work is done; if they are not distinct from the right of access, it is expensed as access is provided over the contract term. Where the contract is with a third-party supplier, the cost is expensed when that third party performs the work. A payment made before the services are received is recognised as a prepayment asset, and the customer discloses its accounting policy where that is relevant to understanding its financial statements. Firms that report under other frameworks need their own analysis.
What should a contract for a cloud policy administration system cover?
For insurers regulated by the PRA, SS2/21 sets out what a written agreement for material outsourcing should contain at least. The list includes a clear description of the outsourced function, the start, renewal and end dates and notice periods, the governing law and each party's financial obligations. It also covers whether sub-outsourcing of a material function is permitted, and the regions or countries where the service will be provided and data kept, processed or transferred, with a requirement for the supplier to give reasonable notice before changing them. Agreed service levels with qualitative and quantitative performance criteria, the firm's right to monitor performance and the supplier's duty to report developments that could affect its service are also on the list.
Data and access have chapters of their own. Where data is transferred, the PRA expects firms to classify it by confidentiality and sensitivity, identify the risks to it and agree an appropriate level of availability, confidentiality and integrity. Agreements for material outsourcing should give the firm, its auditors and the PRA full access and unrestricted rights for audit and information, and the PRA warns that long chains of sub-outsourced providers spread across jurisdictions can limit a firm's ability to manage the risks. For other firms, the FCA's cloud guidance notes that cloud customers may have less control over the supplier, for example over how far the service can be tailored, and over their data, such as where it is stored.
How long does it take to replace a policy administration system?
Published evidence comes mainly from life insurance. The LIMRA and Deloitte report states that a modernisation, from initial selection to the last policy converted, could take a decade to complete depending on the staffing and capital available, and its authors add that a project as large as replacing a policy administration system could span several financial years and may commit multiples of the business as usual budget in a single year. Asked about the payback period for the benefits of their programmes, 36% of the 42 companies with current or completed transformations estimated more than four but less than seven years, 19% more than two but less than four years, 12% less than two years and 10% more than seven years, while 24% did not know.
The report's Deloitte authors write that these programmes are measured in years rather than months and need a company's most knowledgeable subject matter experts, and one respondent wrote that the speed of a replacement is limited by the number and quality of subject matter experts for each line of business. In general insurance, where a policy is written for a period of cover, an old system can be closed once the last policies on it have expired or renewed elsewhere.
What is the difference between a policy administration system and a broker management system?
A broker management system runs a brokerage: it holds the broker's clients, records the placements it makes with insurers and manages its accounts and commission. A policy administration system runs the products a firm underwrites: it holds the product rules, rates the risk, binds cover, issues documents and processes every change to the policy. Insurers and MGAs use one to write their own products, and brokers with delegated authority use one for the schemes and binders they underwrite and administer for an insurer. The categories overlap, and functions such as customer records and document production appear in both.
Delegated authority is where the two meet. Lloyd's Coverholder Reporting Standards note that some coverholders have been provided with systems by their London brokers or Lloyd's syndicates which already collect the information the standards require. For PRA-regulated insurers, SS2/21 lists delegated underwriting among its examples of third party arrangements that do not fall within the definition of outsourcing, while still expecting insurers to assess the materiality and risks of all third party arrangements. A broker that both places business and underwrites its own schemes can run both kinds of system, each for its own job, and connect them so that a policy written under delegated authority also appears in the client record.
How does a life insurance policy administration system differ from a general insurance one?
In the LIMRA survey, the policy administration systems in scope for modernisation included homegrown systems (3% of respondents), externally developed custom solutions (20%) and commercial off-the-shelf packages (37%), and the report describes them as generally vintage platforms dating from the 1980s and 1990s. It adds that retiring a life insurance system generally means a policy conversion, which is one of the most difficult projects to justify on economic grounds alone. Some respondents described an alternative: putting a new front end on an existing system, so that older contracts are serviced through it without being converted to a new one.
The data standards are also separate. ACORD publishes Life and Annuity XML standards alongside its Property and Casualty XML and AL3 standards. For accounting, the IFRS 17 project summary gives whole-life insurance contracts, annuities and car insurance contracts as examples of three different portfolios, each of which is divided into groups by profitability and year of issue.
We'd rather show you than tell you.
We'll start by getting to know your business. Then we'll show you exactly how Genasys handles it.
Insurance People
Zero Fluff
Tailored to You

