Implementing an Accounting ERP in an Insurance Entity

This book is about that decision and about carrying it out.

It has three purposes. The first is to explain S/4HANA to a reader with no prior background in information systems: what an integrated business system is, what the HANA database does and does not change, why the Universal Journal is the most substantial change to the organisation of SAP accounting in twenty years. The second is to separate, at every point, what the product makes possible from what the programme achieves. Vendor presentations and market folklore obscure that distinction with equal efficiency. The third is to treat the question from the insurer's own position: inverted production cycle, technical provisions, investment subledger, coexistence with policy and claims systems, the IFRS 17 chain, and the production of regulatory returns.

That last angle is the reason for the book. There is a large body of writing on S/4HANA for manufacturing and retail, and a dense technical literature on IFRS 17 and Solvency II. The junction between them, meaning how a French or European insurer builds its finance core on S/4HANA, with which subledgers, which reconciliations and which responsibilities, remains poorly documented outside vendor and system integrator material, whose role is not to be neutral.

Scope. The book covers concepts and decisions, never configuration: no screen, no transaction and no table is described here to be reproduced. Oracle, Workday, Microsoft and sector solutions appear to situate the market, without being assessed — the reader will find neither a vendor comparison nor an argument for or against the product. The book takes a position on specific points, including the real scope of "real time", the blocking nature of certain prerequisites, and the impossibility for any software to produce compliance. It states explicitly where sources diverge or are missing.

Method and sourcing. Every normative statement refers to the official text: the French Commercial Code, Directive 2009/138/EC and Directive (EU) 2025/2, IFRS standards published by the IFRS Foundation, EIOPA and ACPR publications, and SAP documentation. The figures that circulate abundantly on this subject, meaning average project costs, close cycle reductions, automation rates and market shares, come almost entirely from commercial comparison sites, sponsored studies or licensing advisory firms. They are not repeated here as facts. Where an order of magnitude is useful, it appears as such, with the origin of the source and the reservation it requires. This discipline has a cost: the reader will find fewer striking numbers than in a brochure. It also has a return: what is written here can be defended in an investment committee.

Reading conventions. The book uses ERP for the integrated business system. It distinguishes throughout between SAP ECC, the application core of SAP ERP 6.0 used by most existing installations, and S/4HANA, a distinct product marketed since 2015. HANA is the database; S/4HANA is the ERP that runs on it. The word edition refers to the three forms of S/4HANA, meaning on-premise, Cloud Private Edition and Cloud Public Edition, and never to a software release. The word release refers to the software version. FI is financial accounting in the SAP sense, CO is management accounting. These conventions are restated at the head of each part so that each part can be read on its own.

The book follows a logical progression: understand the object, understand what it does to accounting, understand what you are buying, weigh the benefits against the costs, choose a migration path, address the specifics of insurance, run the programme. Economics first, technique second, organisation and controls last.