Why does the same loss ratio come out 3 different ways?
The management board asks for the fleet portfolio’s loss ratio for the last quarter. Portfolio, claims, and controlling each check their own sources. Every result looks right, and every result can be explained.
The report will go through. The question is whether it survives an audit.
See where the errors — and the discrepancies — come from.
What happens when someone asks: “where does that number come from?”
Where does the data start to change the report?
One month, one product. Data from the policy admin system, broker files and documents read via OCR. At first glance the differences look minor; in a report they can shift the result or make it hard to explain.
| policy_no | client_eid | client_name | inception_date | expiry_date | premium | currency | status | trade_lic |
|---|---|---|---|---|---|---|---|---|
| FL/2023/AE001 | 784-1990-1234567-8 | AL-RASHIDI MOHAMMED | 2023-01-15 | 2024-01-14 | 3600.00 | AED | Active | — |
| FL/2023/AE001 | 784-1990-1234567-8 | Al-Rashidi Mohammed | 15/01/2023 | 14/01/2024 | 3,600.00 | AED | ACT | — |
| FL2024AE001 | 7841990123 | Al Rashidi Mohammed | 15-01-2023 | 2024.01.14 | 3600,00 | — | 1 | — |
| FL/2023/AE002 | 784-1975-9876543-2 | Gulf Logistics LLC | 2023-02-01 | 2024-01-31 | 28500.00 | AED | active | DED-12345 |
| FL/2023/AE003 | 784-1985-5678901-3 | Al-Mansoori Fleet Co. | 2023-03-10 | 2024-03-09 | 45000.00 | SAR | Active | — |
| FL/2023/AE004 | 784-1980-3456789-4 | Mohamed Al-Hamdan | 01/15/2023 | 01/14/2024 | 5100.00 | AED | Active | — |
| FL/2023/AE005 | 784-1988-6789012-5 | Muhammad Al-Hamdan | 2023-04-01 | 2024-03-31 | NULL | AED | N/A | — |
| FL/2023/AE005 | 784-1988-6789012-5 | Mohammed Al-Hamdan | 2023-04-01 | 2024-03-31 | 5100.00 | AED | Active | — |
| FL/2023/AE006 | 784-1992-7890123-6 | Emirates Transport | 2023-05-20 | 2024-05-19 | 1.950,00 | AED | Active | ADNOC-789 |
| FL/2023/AE007 | 784-1970-8901234-7 | Al-Maktoum Holdings | 2023-06-01 | 2024-05-31 | 120000.00 | — | Active | DED-99001 |
The good news: data can be cleaned up before it reaches analysis
A shared data platform joins information from policies, claims, broker files and OCR, then checks it against agreed rules. It detects inconsistencies, labels their type and triggers a fix before the differences reach the report.
Will the data make the board's 8:00 report?
You have a shared reporting layer, but every extra source stretches the nightly data path. Move the slider and see when the morning report starts running late.
There's no time for guesswork. You need a process that shows where the data got stuck before the morning report becomes a problem.
What's the loss ratio? It depends on the definition
The result changes when different teams calculate it on different assumptions. Change the parameters and watch one number become three versions of the report.
This combination is technically possible, but it should not go into an official report.
The system can compute it, but without an approved definition it's hard to explain later why the result looks the way it does.
When a definition has no owner, every team can compute the same metric its own way.
What does your data platform need to carry?
Set the sliders to your real priorities — not just what hurts today, but what the data needs to support over the next 12–18 months.
Data warehouse
When reports, audit and numbers you can explain matter most.
It works well for reporting loss ratios, premium, reserves, portfolio, product profitability and sales results. It helps align definitions, control data quality and show where a result came from — in a board report, an audit or a conversation with the regulator.
It fits less well when your main challenge is raw data, many formats, documents, OCR or fast-moving AI models.
Data lake
When you want to use data that does not fit standard reporting today.
It takes in data from many systems, files, documents, processes and external sources — even when they have different formats and quality levels. It gives room to analyse claims history, segment clients, scoring, anomaly detection, work on documents and prepare AI projects.
Note: without a data catalogue, owners and quality rules it can become yet another place where data has to be explained by hand.
Lakehouse
When reporting, audit and AI need to run on the same data foundation.
It combines the order of a data warehouse with the flexibility of a data lake. It lets you work on raw, trusted and reporting data in one architecture. It fits modernising reporting, data quality control, portfolio analytics, scoring, claims prediction and anomaly detection.
Note: it requires clear data layers, shared definitions, quality rules, data owners and consistent change management.
This is not a finished architecture choice, only a first pointer. To pick the right solution you have to translate this result into real assumptions: what you have today, what to clean up first and what decisions the data platform should support in the coming months.
AI needs to know where its answer comes from, too
If you are thinking about bringing AI into reporting, analytics or work with portfolio data, you first need a solid foundation: tidy sources, shared definitions and quality rules. Without it, AI will not solve the problem of divergent data. It can only reproduce the same chaos faster — in a more convincing form.
|
The same question, an entirely different route to the answer
What is the fleet loss ratio for the last 4 quarters?
Your data doesn't have to look like this
45 minutes with a data architect. No sales pitch — we go straight to your situation.
altkom software · data platforms
Privacy Policy