For actuarial, risk and finance teams
Spreadsheet logic,
governed in your own database.
Every input, formula and result is a row in your database: versioned, audited per cell, reproducible. Your actuaries keep working the way they work in Excel.
Runs in your environment. Source-code escrow and an exit to .xlsx come with every licence.
Live demo: edit a cell, watch the database
Spreadsheet
| A | B | C | D |
|---|
Select a cell, type a number or a formula such as =B2*B3, press Enter.
Your database
| row | col | formula | value |
|---|
| time | cell | old | new | user |
|---|
The problem
Where the money is calculated, the audit trail stops.
- Field audits of real-world spreadsheets, summarised by Raymond Panko, found errors in roughly 1 in 20 formula cells.[1]
- Under Solvency II and DORA, supervisors expect insurers and pension funds to control the tools that produce regulatory numbers: who changed what, when, and whether a result can be reproduced.[2]
- The usual workflow (export from the database, calculate in Excel, import the result) breaks the audit trail at the exact point where the money is calculated.
- [1] Raymond Panko, spreadsheet error rates, summarised at planguru.com.
- [2] Regulation (EU) 2022/2554 (DORA); Directive 2009/138/EC (Solvency II).
How it works
Import, calculate, govern.
- 01 Import
An existing workbook is read
Formulas, inputs and layout become rows in your database. Target platforms: PostgreSQL, Oracle and SQL Server.
- 02 Calculate
The engine recalculates in the database
Formulas can reference records in your own tables. Results are ordinary data that reports and downstream systems read directly.
- 03 Govern
Every change is logged per cell
Old value, new value, formula, user, time. Any past state can be reproduced. Export back to .xlsx at any moment.
How this differs. Calculation-as-a-service products move your logic into their cloud. Spreadsheetproof keeps logic, data and history in your database, under your controls.
Controls
Control measures in every licence
What we commit to, and in which document it is laid down. These terms come with every licence.
| Measure | What it covers | Where it is laid down |
|---|---|---|
| Runs in your environment | Installed on your infrastructure and your database. No data leaves your organisation, no SaaS dependency. | Installation, licence per environment |
| Source-code escrow | Every licence includes source-code escrow with an independent escrow agent, set up when the contract is signed. | Licence agreement, escrow agreement |
| Exit to Excel | Any sheet exports to a working .xlsx with its formulas intact. You are never locked in. | Product function, exit clause |
| Parity with Excel | Each migration is delivered with a parity test against your Excel workbook; you receive the results. | Migration deliverable |
| Continuity | The contract names a continuity partner who can take over maintenance. | Licence agreement |
| DORA | Contracts include an annex on DORA Article 30, exit strategy and audit rights; we complete your supplier questionnaire. | Contract annex, questionnaire |
We take one existing EUC model of yours and run it in Spreadsheetproof in parallel with Excel, read-only, in your environment.
Deliverable
- A variance report, cell by cell.
- An audit-trail demonstration for your second line.
You keep the report, whatever you decide.
Licence per environment, quoted after the pilot.
For partners
Actuarial and risk consultancies, integrators
You build and maintain the models; we provide the governed platform.
- Implementation work stays with you.
- Your models become auditable assets for your clients.
- Partner pricing and joint pilots.
About
About ELK Solutions
ELK Solutions is a small, specialised software company in the Netherlands. The approach behind Spreadsheetproof was first built for a Dutch publisher of construction cost data, where stacked cost databases and spreadsheet calculations had to become one governed system.
Our continuity does not depend on headcount: escrow, a named continuity partner and installation in your environment are terms of every contract.
FAQ
Questions we expect
What if ELK Solutions stops?
You receive the source code through the escrow agent, and the continuity partner named in the contract can take over maintenance. Because Spreadsheetproof runs in your environment and every sheet exports to .xlsx, your models keep working in the meantime.
Which databases are supported?
Target platforms are PostgreSQL, Oracle and SQL Server. Which one fits your estate is settled when the pilot is scoped.
Does it replace Excel?
No. Your actuaries keep the same grid and the same formulas. What changes is where the model lives: in governed storage in your database instead of a file on a shared drive.
Where is our data?
In your own database, in your own infrastructure. Spreadsheetproof is installed there; no data leaves your organisation and there is no SaaS dependency.
How does this relate to DORA?
Contracts include an annex on DORA Article 30, exit strategy and audit rights, and we complete your supplier questionnaire. Per-cell history supports your own controls on end-user computing; the regulatory assessment stays with you.
What does a pilot require from us?
One model, a database schema or test environment, and one contact person. Plan for about one day per week during the 8 weeks.
Contact
Talk to us
Questions, a pilot or a partnership: info@elk.solutions