A record that cannot quietly change.

Specific engineering controls, in plain language. No badges we have not earned. No guarantee that software can make a source document true.

Controls you can ask us to explain.

Append-only, hash-chained ledger

Each entry carries the previous entry’s hash. Append-only access is enforced by database grants, not only application code. The chain can be verified independently using a trusted-owner operation outside the served application; there is no one-click verification action for every user.

Workspace isolation

Row-level security separates workspaces at the database level. Production cross-workspace probes have been recorded. This is an isolation control, not a claim that every security property has been independently audited.

Evidence keys and data region

The infrastructure provisions per-organisation KMS keys for evidence storage. The estate runs in London, eu-west-2. A provisioned key and an adapter are not, by themselves, proof of an observed encrypted-object round trip.

Authentication and approval

MFA is mandatory for Admin and Approver roles; TOTP replay is refused. A submitter cannot approve their own request. SSO and passkeys are not available.

Security history

The security log records identifiers, an email digest rather than an email address, and a network prefix rather than precise location. Workspace-attributed history can be exported by an Admin. This is not a record of every evidence-document view.

Factor provenance

Publisher, edition, licence and file hash travel with a factor set. Once used, the set is locked. The documented example is DESNZ · 2026 v1.2 · OGL-UK-3.0.

Clear limits are part of trust.

No external security certification is held. No independent assurance opinion, penetration-test claim or availability commitment is made here. The security questionnaire is not publicly released.

Ask about specific controls during a walkthrough. Published source procedures and local test results must not be mistaken for live estate receipts.

Read the recorded service-provider inventory

Product capability wording is bounded by the EmitIQ claims register and the website brief verified against the running product on 25 October 2026. Illustrations are not customer records. The software does not submit a filing, provide legal advice or replace independent assurance.

Start with the number
you need to explain.

Bring one site and one month of bills. Explore the record, the workflow and its limitations.

Book a walkthrough