The activity log behind every reported figure is append-only at database level. Below is a real reporting cycle in a demonstration tenant, read live from our production database. Try to change it.
| Recorded | Actor | Action | Detail | Digest |
|---|---|---|---|---|
| Reading the log… | ||||
Digest is a SHA-256 over each row's stored fields, computed when the page loaded. It is not a hash chain — it lets you check a row reads identically on every reload, nothing more.
Each test runs a real statement against the live database and shows you exactly what comes back. To be precise about what is being demonstrated: our server can add entries — that is how the log gets written, and how your attempt gets recorded. What nobody can do, ourselves included, is change or remove one that already exists.
Once a sign-off is recorded against a figure, it stays recorded and attributed. It cannot be re-pointed at someone else after the fact — not by a preparer, not by an administrator, and not by us.
When a figure is restated, the original value stays visible beside the new one, with the reason and the person who made the change. A correction reads as a correction rather than disappearing into a later version.
Your auditor does not have to accept a control description on trust. They can attempt the same operations against the same table and read the same refusal you just did.
Twenty-five questions on governance, evidence, controls and assurance readiness. You get a scored report with the gaps named.
Score your readiness in 6 minutesNo account needed.