The Board Pack That Has to Be Proven: Finance Reporting with Signed Evidence
An illustrative engagement, not a customer story: a finance team whose quarterly figures are challenged after the fact, and how governed metrics, signed execution receipts and a verified build turn a reconstruction into a record.
- Published
- Reading time
- 7 min
This is an illustrative engagement built from the problems finance teams bring to us, not a customer story. Revoluzen publishes no customer names until they agree to be named.
The situation
A finance team at a listed mid-cap company produces a quarterly board pack from a warehouse fed by nightly pipelines. The numbers are usually right. The problem is what happens when someone asks why:
- An external auditor asks which transactions were included in a revenue figure from two quarters ago. The pipeline has been edited twice since. The logs have rotated. The answer is a reconstruction, delivered three weeks later, with a caveat.
- Two dashboards disagree about gross margin by four basis points. Both are "right" by their own definition, which is the problem.
- The CFO wants to know, before signing, that the figures in the pack came from the data as it stood at close, not as it stands today.
The finance systems team is two engineers and an analyst. They are not short of tools; they are short of a record.
What was delivered
Assess, one week. The finding is that the pipelines are sound and the metrics are not: margin is computed in three places with three filters. The plan has three parts: a governed definition of each board-pack metric, signed receipts on every run that feeds the pack, and a reporting layer that shows where a number came from.
Governed metrics. The board-pack metrics are defined once, in the governed model behind Revoluzen Studio: revenue, cost of sales, gross margin, operating expense, each with its filters written down. Every dashboard and every paginated report in the pack reads from those definitions. The four-basis-point disagreement is traced to a filter on intercompany sales that one dashboard applied and the other did not; it becomes one definition, and a documented decision.
Signed receipts. Every run of the pipelines that feed the pack emits a signed execution record through Revoluzen Evidence: the inputs and their hashes, the output and its hash, the code version, the row counts and the result, signed at the moment of execution with a key the company holds. The receipts are retained with the pack.
The verified build. The quarter-close pipeline itself is rebuilt as a verified build: an agreed specification from the finance controller, tests for the edge cases that have bitten before (late journals, restated periods, currency conversion at close rates), one revision round, and documented handover. It runs on Revoluzen Flow with per-step resume, so a failure on the last step does not reprocess the quarter, and with backfills that reproduce a prior period exactly.
The pack. Each figure in the paginated report traces to its metric, its query and the receipt of the run that produced it. The CFO signs a pack whose provenance is a record, not a memory.
The auditor's question, answered
The next time the question comes, the answer is a receipt and a public key. The auditor runs the open-source verifier offline: the signature is valid, the content hash matches, the chain of runs is intact. No access to the company's systems, no access to ours, no three weeks. That is what verifiable evidence means in practice.
What it cost
| Item | Price |
|---|---|
| Assessment | fixed, quoted |
| Verified build, quarter-close pipeline | $149 |
| Verified builds, board-pack dashboards and reports | $149 each |
| Flow Enterprise, Team, one production environment | $99 per month |
| Studio, early access | scoped |
| Production care | $199 per month |
The work took the finance systems team away from their normal duties for the assessment week and the handover day. Evidence is open source; the verifier is a standalone tool, so the proof outlives any subscription.
The limits, stated
A receipt proves what the executing system recorded and signed; it is strong evidence of execution, not a proof that the business logic was correct, which is why the verified build and the governed definitions matter as much as the signature. Key custody is the company's responsibility. Studio is in early access, and the team worked with us on the deployment rather than downloading it and being finished.
See regulated reporting with verifiable evidence and the financial services page.
Frequently asked questions
What is a signed execution receipt?
A record of a pipeline run, covering inputs, outputs, code version and result, signed with Ed25519 at the moment of execution. Anyone with the receipt and the public key can verify it offline, years later, without access to the system that produced it.
How does this differ from keeping logs?
Logs say what a system believes happened, and they rotate. A signed receipt lets a third party confirm it, and it is retained deliberately, as evidence, with the pack it supports.
Does the auditor need our software?
No. The verifier is a standalone open-source tool. It needs the receipt and the public key, nothing else.
How do we stop two dashboards disagreeing?
Define each metric once in a governed model with its filters written down, and have every dashboard and report read from it. Disagreements become modeling decisions, not meetings.
Is this a real customer?
No. It is an illustrative engagement built from the problems finance teams bring to us.
About the author
Revoluzen
The team building Revoluzen Flow, Catalog, Studio, Console, Mobile and Evidence — writing about what they build and what they have learned running it.