The short answer
An insurer, health maintenance organisation (HMO) or benefits administrator runs on two kinds of systems:
- Core insurance systems handle products, policies or plan members, underwriting, premiums, claims adjudication and payments to members or providers.
- An ERP handles the organisation itself: general ledger, accounts payable and receivable, procurement, fixed assets, budgeting, human resources and management reporting.
"Next-generation ERP" in this sector rarely means replacing claims or policy systems with an ERP. It means a finance and operations platform that receives clean, detailed data from those core systems, closes the books faster, supports regulatory and management reporting, and can change as products and regulations change.
Where older setups struggle
Many insurers and benefits providers have grown through new products, acquisitions or new plan sponsors, and their finance systems show it:
- Summary-only postings. Core systems send one journal entry a day or a month, so finance cannot trace a figure back to policies or claims without asking another team.
- Spreadsheet reconciliations between the claims system, the bank and the ledger.
- Commission and fee calculations for brokers, agents or third-party administrators done outside any system.
- Several ledgers from acquired businesses, consolidated manually.
- Reporting changes (such as those required when IFRS 17 changed how insurance contracts are measured and reported) handled with add-on spreadsheets instead of structured data.
What a modern ERP should provide
A finance data model that fits insurance
Use accounting dimensions (such as line of business, product, plan sponsor, region and distribution channel) so that results can be analysed without creating thousands of ledger accounts. Agree these dimensions with finance and actuarial teams before configuration.
Clean integration with core systems
Define exactly what flows from policy and claims systems into the ERP: premiums written and earned, claims paid and reserved, refunds, commissions and fees, with enough reference detail to trace each entry. Automate the flow, log every transfer, and reconcile totals on both sides.
Payments and bank reconciliation
Claims and provider payments are high-volume and time-sensitive. Plan for bulk bank transfer files, payment approval rules, and automated bank reconciliation against statements and instant-transfer (NIP) credits.
Procure-to-pay and vendor management
Insurers rely heavily on vendors: technology providers, loss adjusters, medical and dental reviewers, print and mail services. The ERP should support approvals, contracts, vendor onboarding and spend reporting, including withholding tax and VAT treatment on vendor invoices.
Controls and audit trail
Role-based access, segregation of duties, approval workflows and a complete audit trail are basic requirements, not extras.
The Nigerian regulatory context
This is general information, not legal or regulatory advice.
- Insurers are licensed and supervised by the National Insurance Commission (NAICOM), which issues rules on reporting, solvency and market conduct (NAICOM). Check the current requirements with your regulator and your legal adviser, including how IFRS 17 reporting is to be applied.
- HMOs and health benefits administrators also operate within the health insurance framework for their sector, so confirm which health-sector regulators apply to your plans in addition to NAICOM-style conduct expectations where relevant.
- Banks and payment service providers you work with are supervised by the Central Bank of Nigeria (CBN), whose cybersecurity framework and guidelines apply to them and can flow down into your contracts and integrations (CBN).
- Privacy. Benefits and health plan data includes personal and often health information, which the Nigeria Data Protection Act 2023 (NDPA) treats as sensitive personal data. The Act is enforced by the Nigeria Data Protection Commission, and covers lawful basis and consent, data subject rights, data protection impact assessments for high-risk processing, registration of controllers and processors of major importance, and transfers outside Nigeria (NDPC). A breach likely to risk individuals' rights must be notified to the Commission within 72 hours of becoming aware of it.
- Data location. There is no major public cloud region in Nigeria, so hosting is either a local data centre or a region abroad. The choice has to fit the NDPA's transfer rules and any sector rules, and contracts, backups and support access need to be checked as well.
Choosing the next platform
Evaluate ERP options against your own scenarios, not a generic demo:
- a month-end close using realistic volumes of premium and claims postings;
- a new line of business or plan sponsor added without new ledger accounts;
- a commission run with clawbacks or adjustments;
- an auditor request to trace a reported figure back to source transactions;
- a user access review showing who can post, approve and pay.
Open-source platforms such as ERPNext can be a good fit for smaller insurers, benefits administrators and agencies that want to own their data and control costs. Larger carriers may need platforms with specific insurance accounting capabilities. The right choice depends on volumes, reporting requirements and the core systems already in place. Include power and connectivity in the evaluation too: an on-premises deployment needs reliable backup power and a failover link, while a hosted one depends on the quality of your internet connection at every branch.
Hypothetical example. A regional dental benefits administrator adjudicates claims for several employer plans in a specialist claims system. Finance receives one summary file a day, reconciles it to the bank in a spreadsheet, and bills each plan sponsor manually each month.
A modernisation plan could: define dimensions for plan sponsor and benefit type; automate a daily detailed feed from the claims system into the ERP; match provider payments to bank transactions automatically; generate sponsor invoices from the posted claims data; and restrict access to member-level information to the roles that need it. The claims system itself stays in place.
Readiness worksheet
Scope
- Which functions will the ERP own, and which stay in policy and claims systems?
- Which reporting requirements (regulatory, management, sponsor) must it support?
Data and integration
- What detail must flow from core systems to the ledger, and how often?
- How will each transfer be reconciled and logged?
- Which dimensions will we use for analysis?
Controls and risk
- Which regulator's expectations apply to us, and to our vendors?
- How will segregation of duties and access reviews work?
- Where will data be hosted, backed up and supported from?
People
- Who owns the chart of accounts and the integration mappings after go-live?
Limitations
An ERP does not replace actuarial models, policy administration or claims adjudication, and it does not by itself make an organisation compliant with any regulation. Integration with core systems is usually the largest and riskiest part of the project, and it deserves most of the testing time.
Next step
Our ERP implementation service starts by mapping finance processes and core-system interfaces before configuration. See also our work with banks and insurers, our privacy and compliance readiness service, and our guide to planning a large data migration.
Sources and further reading
Product capabilities and guidance change. These are the primary sources this article relies on, checked on the review date above.
- National Insurance Commission (NAICOM), NAICOM
- Nigeria Data Protection Commission, NDPC
- Central Bank of Nigeria, CBN
This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.