The form has been successfully submitted.
Please find further information in your mailbox.
Hire us Select language
About us Technologies Industries Portfolio 
Insurers aren’t known for underinvesting in technology. Still, McKinsey notes that insurance cost ratios are 10% higher globally than in 2005, even though the industry put heavy money into automation and digital tooling. Meanwhile, telecom, automotive, and airlines cut theirs considerably. The same analysis says technology did raise labor productivity, by 14% in P&C (property and casualty) and 24% in life insurance. So the tools worked in individual processes, but the overall bill didn’t shrink. My reading is that the problem sits between systems.
Closing that gap is what an ERP system is supposed to do. In this guide, I go through what insurance ERP software is and is not, what it gives you, which modules matter, how I would approach implementation, and how the major vendors compare. I also point out where the marketing around this topic stretches the truth, starting with the industry habit of calling any finance package an insurance solution.
ERP stands for enterprise resource planning. One system and one database for the functions every company has, such as finance, procurement, HR, and reporting. Insurance adds complications that make a generic setup awkward. You collect premiums before you know what the product will cost. Revenue arrives over months or years. Part of the risk goes to reinsurers, so money flows in both directions. Intermediaries earn commissions that depend on what happens to the policy later. And regulators want to see all of it.
Insurance ERP may mean three things. The first is a general ERP that handles finance, procurement, and HR and connects to the insurer’s core systems. The second is a general ERP extended with insurance-specific modules for policies, commissions, or claims, which is common among agencies and smaller carriers. The third is an insurance core suite marketed as ERP because the word sounds better in a pitch deck.
The difference from classic insurance software comes down to ownership. A PAS owns the policy lifecycle: quote, bind, endorse, renew, cancel. A claims system owns the claim process. The ERP owns what the business does around them: the ledger, the suppliers, the people, the reporting. Think of the PAS as the production line, and the ERP as the building’s wiring and the accounts office. A line can run for a while on bad wiring, and you will notice at quarter end when the lights flicker.
Most insurers aren’t starting from a blank page anyway. In Adacta’s 2025 survey of 110 European insurance professionals, obsolete systems were the top trigger for core modernization, cited by 48.2% of respondents. In a similar survey, 65% of UK and Irish insurers reported that their organizations had already started modernizing core systems. That subgroup made up 18.2% of the sample, roughly 20 people, so treat it as a mood, not a census. It’s also worth remembering that Adacta sells core insurance systems, so it has a horse in this race.
| Insurance ERP | PAS | Standalone point tools | |
|---|---|---|---|
| Main job | Runs finance, procurement, HR, and reporting, and ties the business together | Runs the policy lifecycle from quote to renewal | Handle one task, such as a commission spreadsheet or a billing app |
| Owns data on | Ledger, suppliers, employees, consolidated reports | Policies, coverages, rating, endorsements | Whatever the team typed into them |
| Typical weakness | No deep policy or claims logic out of the box | Thin finance and back-office functions | Manual reconciliation and duplicate records |
| Works best when | Finance and operations have outgrown spreadsheets and separate apps | Product and underwriting complexity is the main problem | The team is small, and the process is simple |
This module holds policies, coverages, endorsements, renewals, and the underwriting rules that decide what you accept and on what terms. Most general ERPs don’t include it, so either the insurer keeps its existing PAS and the ERP reads from it, or the ERP is extended with a policy module. Either way, the integration matters more than the screen design. A PAS typically exposes REST or SOAP APIs, while older installations may rely on file exports and database views. Middleware then translates policy events (bound, endorsed, cancelled) into postings the ledger understands. Get that event list right early, and the rest gets easier. This is the major part of ERP integration work in insurance.
Here you define products, coverage options, tariffs, and the rules that turn risk data into a price. The question to ask is how much of this can change without a developer. If launching a new tariff takes a release cycle, you have a rating engine in name only. General ERPs rarely include one. Rating usually lives in the PAS or a dedicated rating service, and the ERP needs only the financial outcomes: premiums, taxes, fees, and commission amounts. Keep the engine where pricing specialists can reach it.
This covers producer records, licenses, appointment terms, commission schedules, overrides, statements, and payments. The complexity is in the rules. Rates vary by product, channel, and volume, and they change after the fact through cancellations and endorsements. The feature I would test first is the clawback. Feed the system a policy sold in January, cancelled in April, with a bonus tier crossed in March, and see whether the statement comes out right. If a person has to fix it, you have just found your real requirements.
The claims system decides coverage, sets reserves and manages the file. The ERP handles what follows: posting reserves, paying claimants and repairers, recording recoveries and subrogation. The link is usually an API or a message queue, with payment instructions going one way and confirmations coming back.
Where the time goes is instructive. McKinsey describes Aviva rolling out more than 80 AI models in claims, which cut liability assessment time for complex cases by 23 days, improved routing accuracy by 30% and reduced complaints by 65%. That’s not an ERP result, to be clear. But look at what it targeted: assessment and routing, the handoffs, rather than payment processing. An ERP that pays quickly after a slow claims decision hasn’t fixed much.
CRM holds leads, policyholders, interactions, renewals, and cross-sell opportunities. Inside an ERP suite, it shares customer and policy data with finance, so a service agent sees that a premium is overdue before promising anything. A standalone CRM is often stronger on sales features, and then the integration question comes back: the customer ID has to match across CRM, PAS, and ERP, or you end up with three Mr. Smiths. I wrote about that in our piece on CRM and ERP integration, and my colleague compared tools in our guide to the best CRM for insurance. For the “where is my claim?” calls, an ERP-connected chatbot can answer from payment and claim data without a human in the loop.
This is the core: general ledger, payables and receivables, premium and commission accounting, reinsurance accounting, multi-entity consolidation, budgeting, tax and regulatory reporting, plus procurement and HR. Insurance asks for things a standard ledger may not handle well, such as earned versus unearned premiums, reserves, and reinsurance recoveries. Check these with real data in the demo, not with slides. If the vendor needs to “get back to you” on unearned premium, that’s an answer. AI features are now appearing in finance modules, such as automated matching and forecasting, and our overview of ERP trends tracks which ones are real.
Innowise looks at your current PAS, claims, and CRM tools and shows which functions an ERP should have.
Most of the work in an insurance ERP project sits in the connections to existing systems and in the data you carry over. Here’s how we approach it at Innowise.
List which system owns policy, claim, payee, commission, and ledger data, and where the handoffs break. ERP consulting usually starts here.
Decide whether to buy, extend, or build, then shortlist platforms against your real scenarios.
Define the data model, the policy and claim events that trigger postings, and every integration point.
Tidy up formats, fill gaps, standardize IDs, then load in test runs. See ERP data migration and our migration services.
Set up ledger, commissions, and workflows, and connect PAS, claims, and CRM. Start read-only, add write paths once numbers reconcile.
Run ugly scenarios: mid-term cancellations, backdated endorsements, reinsurance recoveries, and month-end close with open claims.
Go live in steps: finance first, then commissions, then claims postings. Train people by role. ERP implementation support helps here.
Fix what real usage exposes, then add the next flow.
List which system owns policy, claim, payee, commission, and ledger data, and where the handoffs break. ERP consulting usually starts here.
Decide whether to buy, extend, or build, then shortlist platforms against your real scenarios.
Define the data model, the policy and claim events that trigger postings, and every integration point.
Tidy up formats, fill gaps, standardize IDs, then load in test runs. See ERP data migration and our migration services.
Set up ledger, commissions, and workflows, and connect PAS, claims, and CRM. Start read-only, add write paths once numbers reconcile.
Run ugly scenarios: mid-term cancellations, backdated endorsements, reinsurance recoveries, and month-end close with open claims.
Go live in steps: finance first, then commissions, then claims postings. Train people by role. ERP implementation support helps here.
Fix what real usage exposes, then add the next flow.
So, what is the best insurance ERP system? The one that fits your size, your existing systems, and your appetite for customization, which is an unsatisfying answer I’ll try to make less so. Two caveats first. None of the six products below is a policy administration or claims system. If that’s what you need, look at core insurance platforms such as Guidewire, Duck Creek, or Sapiens, and read this section as a finance and operations comparison. Second, this is my reading of each product’s position, not a benchmark. Features and licensing change, so verify with the vendor.
| Key features | Best for | Limitations | |
|---|---|---|---|
| SAP S/4HANA | Finance, procurement, analytics and insurance components such as FS-CD (collections and disbursements) and FS-RI (reinsurance) | Large, multi-entity insurance groups | Long, costly implementations that depend heavily on partners |
| Microsoft Dynamics 365 Business Central | Finance, purchasing and reporting with tight Microsoft 365 and Power BI links | Small and mid-sized insurers, agencies, and brokers | No policy or claims engine; complex group structures need extensions |
| Microsoft Dynamics 365 Finance & SCM | Advanced finance, multi-entity accounting, procurement and Power Platform options | Mid-size to large insurers already on Microsoft | Supply chain features may go largely unused; insurance logic comes from partners |
| Odoo | Modular platform with an open-source Community edition, accounting, CRM, and customizable modules | Agencies, brokers, and smaller carriers looking for flexibility | Insurance logic is built, not bought; quality depends on the partner |
| Oracle NetSuite | Cloud financials, multi-subsidiary accounting, billing, and built-in reporting | Growing insurers, MGAs, and insurtechs with multiple entities | Insurance-specific functionality requires customization or add-ons; costs increase with users and modules |
| Sage Intacct | Cloud financial management, multi-entity consolidation, and flexible reporting dimensions | Finance-focused brokers, MGAs, and mid-sized insurers | Finance first; operations, policy, and claims need other systems |
Start with three questions. Where does your PAS end, and where must the ERP begin? How many entities, currencies, and regulators do you deal with? And who will maintain the customization in year three?
Answering them alone is harder than it sounds, because every vendor will tell you their product fits. A partner who has worked with different ERPs across different industries can lay out the pros and cons of each against your actual use case, including the awkward ones. We work across SAP, Microsoft, and Odoo, so we have no single product to push. If you are moving from an older SAP system to S/4HANA, our SAP migration team plans the move. If Odoo looks like the better fit, our Odoo implementation services cover the build. With 3,500+ employees, Innowise can also cover whatever else the project needs, from integration and testing to support after go-live.
You can also use our guide to choosing an ERP system as a checklist.
Let me start with a number I distrust. You’ll see claims that 55% to 75% of ERP projects fail, usually without a clear definition of failure. Better data exists. Panorama Consulting’s 2026 ERP report found that more than a quarter of organizations exceeded their project budgets, with additional technology needs cited as the leading cause. The causes below are all fairly ordinary, which makes them easier to deal with.
Among organizations that did overrun their budgets, NetSuite’s roundup of the data lists underestimated staffing (38%), expanded scope (35%), and technical issues (34%) as the main reasons. Name an owner for every process, budget for your own people’s time on top of the partner’s invoice, and freeze scope after design with a written change process. The pattern is dull, which is the good news, because dull problems have dull fixes.
Panorama’s own assessment is that organizations often discover fatal misfits late, then reach for extra technology, scope expansion, and custom builds. Run the ugly scenarios in a proof of concept before signing the full contract, while walking away is still cheap.
Old policy systems may have no usable API, and nobody who wrote them still works there. McKinsey notes that insurers facing big replacements often choose incremental paths, such as progressively modernizing and hollowing out legacy systems. I like that approach for ERP too: put middleware in front, move one flow at a time, and retire old components only when the numbers reconcile.
Since 17 January 2025, the EU’s Digital Operational Resilience Act has applied to insurance companies, among other financial entities. It requires them to maintain a register of contractual arrangements with ICT third-party service providers, including ERP vendors and cloud hosting providers. Micro, small, and medium-sized insurance intermediaries are exempt, but larger ones are covered. Check audit rights, exit plans, and incident reporting obligations in the ERP contract before you sign. During the audit is too late. Other regulated industries face similar requirements. Pharma ERP projects, for example, involve validation and audit trails.
A system nobody trusts grows shadow spreadsheets within a month. In the same NetSuite roundup, 77% of companies that completed an ERP implementation named leadership support as the most critical success factor. Give claims supervisors and finance leads ownership of the rollout. IT can’t do it for them.
Bring us your toughest ERP challenges, and we’ll work through them together.
Innowise holds ISO 9001, ISO 27001, and ISO 27017 certifications and is a certified Microsoft Solutions Partner, an AWS Partner, and an Odoo Implementation & Development Partner. We also have SAP expertise covering SAP Activate, S/4HANA, SAP HANA, SAP Analytics Cloud, SAP Fiori, and ABAP Cloud. The full list is on our certifications page.
Certificates don’t build ERP systems, so the better evidence is the work. We have implemented ERP systems for many industries, including insurance, and you can see the projects below.
The most useful question in this whole topic is not which ERP to buy. It is where your policy and claims systems end, where the ERP begins, and who owns each handoff. Get that map right, and most vendor decisions become obvious. Get it wrong, and the best software on the market will reproduce your spreadsheet chaos in a nicer interface. Start small: one flow, one entity, real data. If you want a second opinion on the map, our ERP consulting team can give you one.
A PAS manages the life of a policy: quoting, issuing, endorsing, renewing, and cancelling it. An insurance ERP manages the business around it: ledger, payables, commissions, procurement, HR, and reporting. Most insurers need both, connected by events such as "policy bound" or "claim paid".
Yes, though the method depends on what the legacy system offers. Modern APIs are the easy case. Older systems may need middleware, scheduled file exchange, or database-level connectors. Start read-only and add write paths later. Our ERP integration service covers this.
Because much of their revenue comes from commissions, and commissions depend on policy events, carrier statements, and client money rules. A general accounting package may struggle to reconcile carrier statements against expected commissions without additional tools or manual work. Many jurisdictions also require client money to be held separately and reconciled. Brokers don’t need an exotic product so much as a setup that handles these two things properly.
Off-the-shelf fits when your processes are close to standard and finance is the main pain. Custom fits when your products or commission logic are a competitive edge, or legacy integration is heavy. Many companies end up with a platform plus custom modules. The cost that surprises people is maintenance, not the build.
Cloud ERP vendors typically provide encryption, access control, and logging, but the contract and configuration decide whether you can prove it. Ask for ISO 27001 and ISO 27017 certification evidence, data residency terms, audit rights, and an exit plan. For EU insurers, DORA adds the third-party register duties described above.
Indirectly. The claims system decides, and the ERP speeds up what comes after: payment processing, reserve posting, payee checks, and status visibility for customer service. The larger gains in cycle time usually come from better routing and assessment, so pair the ERP with claims workflow changes instead of expecting it to fix a slow adjuster queue.
Client review
