Back office
The only surface with the whole picture and the power to write. Every route checks a named permission before it checks the session.
KAIROS · ROAD ACCIDENT CLAIMS
They manage the file. We produce the proof and govern the time.
Every photograph is captured inside the app, hashed and chained. Every statutory deadline is known from the moment of impact and pushed at whoever has to act. Underneath sits a real ERP — electronic invoicing, payables, a receivables ledger — not a bookkeeping impression.
Measured, not asserted
- Surfaces
- Four, one database
- Data models
- 21 in the claims schema
- Statutory clocks
- Three, wired in
- Evidence
- sha256, chained
- Certified mail
- In and out
- Where the data sits
- European Union
Pillar one · the evidence file
A photograph nobody can argue with.
The injured party photographs inside the app: the gallery is disabled, so there is no picture taken three days later. The server hashes the bytes it received — never a hash the client hands it — and links each item to the one before. Alter a file and the link its successor recorded breaks. Remove one and the sequence has a hole.
- Capture in the app carries time of capture, device model and device attestation
- An upload from the back office is still accepted, and marked as worth less
- The seal folds the hashes into one root and freezes the count it covers
- Sealing a broken chain is refused, not repaired
Break one link and see what happens
Drag to tamper with an item. The chain is checked by recomputing it, not by trusting a flag.
- Item 1 altered
Scene photograph
- sha256
- 9f2c41ae…
- previous
- —
- Item 2 altered
Damage photograph
- sha256
- 3b70d8c5…
- previous
- 9f2c41ae…
- Item 3 altered
Accident statement form
- sha256
- c1a94f02…
- previous
- 3b70d8c5…
- Item 4 altered
Insurance certificate
- sha256
- 7d5e0b63…
- previous
- c1a94f02…
Chain intact — the file can be sealed Every item still matches the fingerprint its successor recorded.
Pillar two · the clock
A time-barred claim is money gone.
The competitor has a passive list of expiries. Here the deadlines are generated from the facts of the claim and pushed: a reminder to the file owner seven days out, an escalation the moment a blocking term runs out. The reminder timestamp is written before the notification goes out, so two overlapping runs never remind twice.
- Notice of loss — three days, art. 1913 of the civil code
- Offer window — 60 days, 90 where there are injuries, art. 148 of the insurance code
- Limitation period — two years, art. 2947(2) of the civil code, blocking
- The offer window only exists once the claim letter has actually gone out
Move the day of the crash
The same table the product uses. Calendar arithmetic, dates in UTC.
-
Notice of loss
art. 1913 c.c. · +3 days
-
Offer window
art. 148 ins. code · +60 days from the claim letter
-
Injury offer window
art. 148 ins. code · +90 days where there are injuries
-
Limitation period
art. 2947(2) c.c. · +2 years · blocking
In the example the claim letter goes out on the tenth day: the offer window is counted from there, not from the crash.
A blocking term that runs out raises the claim to urgent, writes a timeline entry and notifies the owner. It does not close the claim on its own.
Pillar three · the ledger underneath
Claims inside real accounting, not accounting inside a claims tool.
The tools this vertical competes with bolted an invoice table onto a claims database. KAIROS is the other way round: the claims live inside an ERP that already issues electronic invoices through the national exchange, runs the payables cycle towards body shops and tow operators, keeps a receivables ledger, a document archive and payroll.
- Electronic invoicing through the national exchange system
- Payables towards body shops, appraisers and tow trucks
- Receivables ledger, document archive, calendar, field service
- One tenant boundary: your data is scoped by company, not by convention
The commercial name of that ERP is EQUINOX. KAIROS is the vertical you buy on top of it, and it can be bought on its own.
Architecture
Four surfaces, one database.
The injured party must never see a screen that looks like an admin console, and the public internet must never touch the one that does.
The app for the injured party
A separate mobile application. A one-time code on the phone, not a workstation login: the person filing the claim is not, and must not become, a user of your management system.
The public bridge
A separate process on its own address with its own rate limits. It writes to the intake queue and nothing else, so abusing it costs you the queue, not the claims.
Signed-link portals
The lawyer, the appraiser and the body shop get a link, not an account. The token is the credential and it carries no server state.
Without its signing key the public bridge answers 503 on every versioned route. It fails closed by design.
The supply chain
Everyone sees their own claim, and only that.
The filter is applied inside the query, not by trimming the answer afterwards. Release the assignment and the links die with it, even the ones that had not expired.
Pick a role
Sees
Parties, vehicles, damages, timeline, deadlines, evidence, documents, messages
Does not see
The certified mailbox credentials
Sees
Vehicles, damages, evidence, appraisal deadlines
Does not see
Parties, legal documents, correspondence
Sees
Vehicles, damages, photographs
Does not see
Parties, amounts, deadlines, correspondence
Link lifetime: seven days by default.
The portal interface is English-only today. It is on the list.
The product
Real screens, demo data.
Every screenshot below comes from the product running against the demo dataset the product itself seeds: twelve claims, twenty-eight chained items of evidence, thirty-five deadlines, three roadside jobs.
The application ships in five languages. In the other five the screenshots show the English interface.
Who it is for
Three buyers, one product.
Claims firms
You take the mandate, you run the claim against the insurer, you get paid on what you recover. Losing a file to an incomplete bundle or a missed limitation period is the most expensive thing that happens to you.
For claims firmsRoadside operators
You are next to the driver while they are still shaken, before the insurer, before the lawyer, before the body shop. Dispatch, proof of the job and the invoice draft, sold on its own.
For roadside operatorsInsurers
You do not buy a claims system from us. You get counterparties who open claims cleanly, with receipts you can verify and a bundle you cannot dismiss as undatable photographs.
For insurersHonesty
What it does not do is written down.
A capability we cannot demonstrate is not on this site. The electronic signature is a simple one, the qualified timestamp is optional and currently switched off, there is no automatic damage estimate from photographs and there is no round-the-clock operations desk. All of it, with the reasons, is on one page.
Bring us a real claim and we will run it end to end.
Half an hour is enough to see a claim opened from the app, the evidence sealed and the legal clock start ticking.