Industries / Finance and business services / Insurance / InsurTech
Policy and claims systems
The software an insurer keeps its policies, bills and claims in, and the shared forms and data standards it uses to swap them with brokers and agents.
7
Milestones achieved, from 1972 to 2026.
2
To watch for: announced, not yet confirmed outside.
2
Open deliverables. Nobody has shipped them.
The road
AchievedWatch forOpen
Achieved
1972
One form for all insurers
ACORD was formed in 1970 for independent insurance agents. Its first standard form, a property loss notice, went into use in 1972, Insurance Journal reported. By 2004 about 530 ACORD standard forms had "eliminated the need for up to 80,000 proprietary forms", by Digital Insurance's account.
Credit
ACORD
1974
Software sold to insurers
Seibels, Bruce & Co., a South Carolina insurer, began in 1966 the computer division whose programs "automated premium calculation and billing procedures". In 1974 it "began selling its programs to the entire property/casualty industry", and the division became Policy Management Systems Corporation (PMSC). By its 1993 annual report, PMSC had "over 3,000 software systems licenses in force", running on IBM computers.
Credit
Seibels, Bruce & Co.; G. Larry Wilson, PMSC's president and chief executive
2002
A $100 million system unused
21st Century Insurance spent "about $100 million" over five years on new policy and claims systems with the contractor CSC, and "took a $24 million write-down". The system was "being used to support less than 2% of 21st Century's business", Computerworld reported in December 2002. In 2024 BCG described a central European insurance group that gave up a cross-country platform project after eight years, "with a write-off of more than $500 million".
LessonA custom core system can use up most of its budget before it carries much business.
Credit
Computerworld and BCG, for the reports
2006
Lloyd's abandons Kinnect
In 2001 Lloyd's of London began a project, later named Kinnect, to build a shared data platform for its market. In January 2006 its Franchise Board "agreed not to fund the Kinnect platform going forward". Business Insurance put the project's cost at an estimated £70 million. Michael Dawson of Lloyd's said its role "going forward should be primarily on standards setting, not building infrastructure".
LessonLloyd's itself concluded that a market body should set standards rather than build the systems.
Credit
Lloyd's (Michael Dawson)
2012
Packaged systems, then cloud
Guidewire, founded in 2001, sells packaged software for policies, billing and claims. It listed in January 2012 at $13 a share, with more than 100 customers, TechCrunch reported. Its annual report for the year to July 2026 gives about 550 customers in 44 countries, served "primarily through a cloud-based offering sold on a subscription basis". Subscription and support made up 66% of its revenue that year.
Credit
Guidewire
2026
Blueprint Two dropped
Lloyd's launched Blueprint Two in 2020 to move the London market's processing onto new digital services. In June 2024 it postponed the first cutover because testing was "running eight weeks behind schedule". In September 2025 it said the re-platforming would not be finished before 2028. On 19 March 2026 its council approved "the decision to sunset the name and original vision of Blueprint Two". Patrick Tiernan of Lloyd's said "the project has not yielded the benefits that were originally envisioned".
LessonLloyd's has now twice dropped a market-wide build, in 2006 and in 2026.
lloyds.cominsurancetimes.co.ukinsurancetimes.co.ukinsurancetimes.co.uk
Credit
Lloyd's; Insurance Times, for the reporting
2026
One setting, 41,564 overcharged
In October 2026 the New South Wales regulator SIRA penalized NRMA Insurance A$479,500 for eight pricing failures in compulsory third party (CTP) car insurance, the cover for injuries a car causes to other people. In one, "an address-data misconfiguration caused incorrect rating districts to be applied to policies" in its HUON system. About 41,564 policies were overcharged by a total of about A$12.2 million.
LessonOne wrong data setting in a policy system can misprice tens of thousands of policies.
Credit
State Insurance Regulatory Authority (SIRA), as reported by Insurance Business
Watch for
COBOL to cloud in months
COBOL is a programming language that many insurers' older mainframe systems are written in. Unum, a US insurer, said "we went from COBOL to cloud with a testable application in 3 months" using AWS Transform and Pega Blueprint, AI tools for rewriting old systems. It said two vendors had quoted "7 years, $25 million dollars".
Achieved whenan outside party reports the new system in production and the old mainframe module switched off.
Claimed by
Unum, December 2025, in a talk reported by Pega
AI translation graded by AI
IBM Research reported translating 20 programs from GenApp, its public sample insurance application, and 10 customer applications from COBOL to Java. It reported "a typical (median) structural quality score of over 80% and a functional score above 75%", both graded by an AI model rather than by running the code.
Achieved whensomeone outside IBM runs the translated programs against the originals and publishes how many give the same results.
Claimed by
IBM Research, April 2026
Open
01
GenApp, run both ways
A public test of AI code translation on GenApp, IBM's sample general insurance application for its CICS transaction system. The whole application is translated from COBOL to Java or Python. Every transaction, such as adding a customer or a policy, is run on the original and on the translation with the same inputs, and the number giving identical results is published.
The briefCredit · unclaimed02
A bordereaux checker for Lloyd's
A free, open-source validator for bordereaux, the spreadsheets of policies, premiums and claims that coverholders must send. Coverholders are firms that sell cover on behalf of Lloyd's insurers. The validator reports each row and field that breaks a rule of Lloyd's Coverholder Reporting Standards before the file is sent.
The briefCredit · unclaimed
Open 01 · the brief
GenApp, run both ways
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A public test of AI code translation on GenApp, IBM's sample general insurance application for its CICS transaction system. The whole application is translated from COBOL to Java or Python. Every transaction, such as adding a customer or a policy, is run on the original and on the translation with the same inputs, and the number giving identical results is published.
Why it is still open
In 2025 IBM researchers tested translated GenApp code paragraph by paragraph on 33 programs from GenApp and a second dataset, and found one program that failed because a loop condition "is incorrectly inverted". IBM's 2026 paper graded translations with an AI model. Neither published a whole-application comparison made by running the code.
Built with what exists
GenApp from IBM's cicsdev GitHub account, under the Eclipse Public License 2.0; a place to run CICS, such as IBM Z Development and Test Environment or AWS Mainframe Modernization; for translation, watsonx Code Assistant for Z, AWS Transform or a coding model such as Claude or Inkling 2 Small (see the Note "Checked without being asked"); Cobol-Check from the Open Mainframe Project for unit tests.
First step
Clone GenApp, list its transactions and the COBOL programs each one calls, and write 20 inputs by hand for adding a customer.
Done looks like
Every GenApp transaction is run with at least 500 generated inputs on both versions, and the share with identical outputs and stored records is published for each transaction. The translated code, inputs and test harness are released under an open license.
Open 02 · the brief
A bordereaux checker for Lloyd's
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A free, open-source validator for bordereaux, the spreadsheets of policies, premiums and claims that coverholders must send. Coverholders are firms that sell cover on behalf of Lloyd's insurers. The validator reports each row and field that breaks a rule of Lloyd's Coverholder Reporting Standards before the file is sent.
Why it is still open
Lloyd's requires the data to "meet the Coverholder Reporting Standards or validations will stop entry into the system", and names only commercial systems for the job. The market's processing platform, DDM, "maps, cleanses, and validates bordereaux data", but its rules are not published. The closest open-source project found shows no license and does not mention the standards.
Built with what exists
the published Coverholder Reporting Standards; Python with pandera or Great Expectations to write the rules; made-up bordereaux for testing.
First step
Get the current Coverholder Reporting Standards and write the mandatory fields for one bordereau type as a machine-readable schema.
Done looks like
Every mandatory field and rule in the current standards for risk and premium bordereaux is written as a check. On 50 made-up files with 500 planted errors, the validator finds at least 490, with no more than 5 false alarms. It is released under an open license.