Your SAP is only as good as the data going in and out of it
Most insurers connect SAP to the rest of the business with report downloads, spreadsheets, shared folders and scripts nobody owns. We replace them with secure, tested connections your finance, actuarial and operations teams can rely on, built on what we learned delivering integration for a global reinsurer.
What ad-hoc integration looks like in insurance
Month-end by spreadsheet
Finance exports SAP reports, reworks them in Excel and uploads them somewhere else. Every close depends on a few people and a lot of copy and paste.
Shared passwords into SAP
Scripts and tools log into SAP with a shared account. Nobody is quite sure what uses it, so nobody dares change it.
Actuarial runs nobody can see
Actuarial models run overnight, results land in a folder, and someone checks in the morning whether it worked.
Every SAP change breaks something
Point-to-point links grew one project at a time. An upgrade or a new report layout quietly breaks a feed nobody documented.
Three pressures landing at the same time
SAP's support deadline
Standard support for SAP ECC ends at the end of 2027, with paid extended support to 2030. Any move to S/4HANA breaks ad-hoc links. Fix the connections first and the SAP upgrade gets smaller.
IFRS 17 data flows
Actuarial results, cash flows and accounting entries now have to move between teams and systems every period. Manual hand-offs are where the reconciliation pain lives.
Operational resilience
Regulators expect you to know which systems your important services depend on and to test them. Undocumented scripts and shared logins are hard to defend.
Six lessons from a global reinsurance integration programme
SAP at the centre, surrounded by workflow, actuarial, scheduling, data warehouse and market data systems. Here is what worked.
Stop uploading SAP reports. Ask SAP directly.
Found: reinsurance reconciliation relied on staff exporting SAP reports and uploading them into the workflow tool.
Did: put a secure service in front of SAP so the workflow pulls exactly the data it needs, when it needs it.
One connection per system, kept separate
Found: the temptation to build one big connector for every back-office system.
Did: gave SAP, the job scheduler, the actuarial engine and the workflow tool their own connection, so one can change without breaking the rest.
No shared passwords
Found: system-to-system access using stored usernames and passwords.
Did: moved SAP and other systems to modern, expiring access tokens, all tied to the company's single sign-on.
Actuarial runs you can see
Found: actuarial calculations and scheduled jobs started by hand and checked by hand.
Did: let the workflow tool start runs and get status back automatically, so people act on results, not chase them.
Move data, don't copy it
Found: integration layers quietly keeping their own copies of sensitive financial data.
Did: kept connections pass-through only, with a full log of who asked for what, and nothing stored in between.
One way to raise the alarm
Found: each integration failing in its own way, often silently.
Did: built one shared alerting service, so any failure reaches the right team the same way, every time.
SAP at the centre, everything else around it
How ad hoc is your SAP integration?
Tick everything that is true today.
Your integration looks under control. A health check would confirm it before your next SAP upgrade.
Talk it through with usSAP integration health check
Fixed scope, fixed price. You get a clear picture of every way data gets in and out of SAP, and a plan to fix the riskiest parts first.
Find every connection
Reports, file drops, scripts, shared logins and system links, including the ones nobody wrote down.
Score the risk
How much manual effort each one costs, what breaks if it fails, and how hard it is to fix.
Fix in the right order
Quick wins for the next month-end, then a staged plan that also prepares you for any SAP upgrade.
Already paying for MuleSoft or Boomi?
The same patterns work on Apache Camel, without the licence. Fix your SAP links and cut platform cost in one programme.
Questions insurers ask us
Do you replace or reconfigure SAP?
No. We connect to SAP through its standard, supported interfaces. Any change on the SAP side is agreed with your SAP team first.
We are still on ECC. Is this worth doing before S/4HANA?
Yes. Clean, documented connections mean fewer surprises during the upgrade, and most of them carry straight over.
Does our data get stored by the integration?
No. Data passes through on request and every request is logged. Nothing is kept in between unless you decide it should be.
Do we need to buy an integration platform?
No. We can build on what you already own, or on free open-source tools if you would rather not take on another licence.
Who looks after it afterwards?
Your team, with full handover and documentation, or we run it for you under a support agreement.
Find out what is really holding your SAP together.
Book an SAP integration health check. We map every connection, rate the risk and give you a plan, starting with your next month-end.
XAGROSE