Audit trail & data integrity: data auditors can believe.
A battery passport is only worth as much as the trust in its data. The EU Battery Regulation therefore demands protection against manipulation and traceability of every change (Art. 78). This guide explains what an audit-proof audit trail must deliver, how a SHA-256 hash chain works - and why none of it requires a blockchain.
- An audit trail records every change to model and passport data: who, what, when. It is audit-proof only if entries can never be deleted or overwritten.
- A SHA-256 hash chain makes tampering visible: every version contains the hash of its predecessor. A retroactively changed value breaks the chain - immediately and provably.
- No blockchain required. The regulation demands the protection goal, not a technology. A hash chain delivers the same evidence without energy, cost and GDPR problems.
- Chain of custody counts twice: OEM buyers and market surveillance don't just ask "is the value correct?" but "where does it come from, and who changed it when?".
What is an audit trail - and what makes it audit-proof?
An audit trail (also change log or audit log) is the chronological record of all changes to a data set. For the battery passport that means: every creation, correction, import and deletion is captured with actor, action, timestamp and target - from the first model draft to the last status change.
A log only becomes audit-proof through four properties:
Every change is captured - automatically in the system core, not via voluntary app logging that can be bypassed or forgotten.
Entries can only be appended (append-only). Deleting or overwriting them later is technically impossible - for every role.
Who, what, when, to what: the entry names actor and affected object so that an auditor understands the event without knowing the system.
The integrity of the log itself can be verified cryptographically at any time - which is exactly where the hash chain comes in.
Why the battery passport demands it
Art. 78 of EU Battery Regulation 2023/1542 defines the technical requirements for the passport. Two points concern data integrity directly: (g) requires the data stored in the passport to be protected against manipulation and misuse, (h) demands that the authenticity, reliability and integrity of the data can be demonstrated. On top of that, the passport must remain available for ten years after the last unit of a model is placed on the market - including a defensible history.
In practice, three parties check exactly these points: market surveillance during inspections and complaints, OEM buyers in supplier audits (passport-readiness clauses have appeared in framework contracts since 2026) and certifiers for Annex X due diligence. An Excel export without a change history fails all three - not because the values are wrong, but because nobody can prove they aren't.
Related: non-compliance risks
The guide What happens without compliance? works through the fines and market consequences of missing or indefensible passport documentation.
The hash chain: tamper evidence without blockchain
A SHA-256 hash is a cryptographic fingerprint: every data state maps to a unique 64-character value - change a single bit and the entire hash changes. A hash chain uses this as follows:
Every substantive change to a model or passport stores the new data state as a version and hashes it.
The hash of version N includes the hash of version N−1. Every version thereby "signs" its entire history.
An auditor simply recomputes the chain: if all stored hashes match the recomputed ones, the history is intact.
If an old value is "corrected" retroactively, the hash no longer matches - the chain breaks at exactly the manipulated point. Tampering isn't prevented, it becomes inevitably visible.
This is the same principle that makes blockchains trustworthy. The difference: a blockchain distributes the chain across many participants to solve mutual distrust between strangers. The battery passport, however, has a clearly named responsible party (the economic operator) and clearly named auditors - the distribution problem doesn't exist. What remains are only the drawbacks:
| Criterion | SHA-256 hash chain | Blockchain |
|---|---|---|
| Tampering provable | Yes | Yes |
| GDPR deletion duties satisfiable | Yes - chain can exclude personal data | Conflict - immutable by design |
| Operating cost & energy | Minimal | High |
| Required by EU 2023/1542 | Neither - the regulation mandates the protection goal (Art. 78 g/h), not the technology | |
Chain of custody: provenance beats assertion
Data integrity doesn't end at your own system boundary. Most passport values - cell chemistry, carbon footprint, recycled content, due-diligence evidence - come from suppliers across multiple tiers. Auditors therefore ask in two steps: Is the value correct? And: where does it come from, who entered it when, which certificate backs it? This documented custody record is the chain of custody.
A defensible chain of custody in the battery supply chain requires:
Every delivered value stays attributed to its supplier - even once it appears consolidated in the passport.
Certificates and test reports are attached to the record with upload time and validity date - expiring evidence triggers notifications.
Even reading sensitive data is recorded: which recycler or authority retrieved which passport when - including the approval decision.
How Batteriepasswerk implements this
In Batteriepasswerk, audit trail and integrity protection are enforced in the database core, not in the application layer: every change to models and passports automatically triggers a log entry, the log is append-only and cannot be deleted or modified by any role. In parallel, every substantive change is sealed as a version in a SHA-256 hash chain - per model and per passport.
The result is publicly verifiable: every passport page carries its integrity proof (short hash + version number), and an open verification endpoint validates the full chain on demand - auditors don't need an account. Supplier data enters the system via self-service links with source attribution, and professional access by recyclers and authorities is approved individually and logged without gaps.
Frequently asked questions
What is an audit trail?
Why does the battery passport need an audit trail?
Does the battery passport require a blockchain?
How can you tell whether battery passport data was tampered with?
What does chain of custody mean in the battery supply chain?
Sources & further reading
Tamper-evident passport data - from the first passport.
Every Batteriepasswerk passport is automatically sealed in a SHA-256 hash chain and logged audit-proof - included in the free Pilot plan.