How can I prove my carbon records were not changed after the fact?
Fingerprint every source file with a hash such as SHA-256, write each calculation to an append-only log where every entry includes the hash of the one before, and share the latest hash with your auditor or lender at each reporting date. Any later edit then shows up. This proves records were not altered, not that they were true.
Step 1: fingerprint the source documents
A SHA-256 hash, defined in NIST FIPS 180-4, turns a file into a 64 character code. Change one character in the invoice PDF and the code changes completely. Store the hash next to every emission line that came from that file, so anyone holding the original can recompute it and compare.
Step 2: chain the calculation records
Write each emission line, correction and approval as a new entry. Never overwrite. Each entry's hash is computed from its own content plus the previous entry's hash. Editing or deleting an old entry breaks every hash after it, so the change is visible to anyone who checks the chain.
Step 3: put the latest hash outside your own control
A chain kept only by you can, in principle, be rebuilt from scratch. Send the latest hash to your auditor, lender or buyer when you report, or include it in the signed report. Later, they recompute the chain and confirm it still ends in the hash they received. You do not need a blockchain for this.
What this does not prove
- That the invoice itself was genuine or the quantity on it was right. A fake bill hashed on day one stays fake.
- That nothing was left out. A hash chain shows what was recorded, not what was never uploaded.
- That the method was correct. Keep the factor source and methodology version with each line so a reviewer can judge that separately.
How a two-entry chain catches an edit
- Entry 1: diesel 500 litres, hash h1 = SHA-256(h0 joined to entry 1)
- Entry 2: electricity 42,000 kWh, hash h2 = SHA-256(h1 joined to entry 2)
- You share h2 with your lender on the reporting date
- Someone later changes entry 1 to 400 litres: h1 changes, so h2 changes, and it no longer matches what the lender holds
What Senseible does here
Senseible gives every uploaded file a SHA-256 fingerprint and keeps an append-only compliance ledger whose entries are hash-chained, so later alteration is detectable. It does not prove that the original documents were truthful, and it does not use blockchain tokens.
Sources: NIST FIPS PUB 180-4, Secure Hash Standard (2015)
Last reviewed 2026-10-15.