| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 794 |
| Technical Name |
de_gobd_unveraenderbarkeit_hash_chain_lock |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 794 |
| Technical Name |
de_gobd_unveraenderbarkeit_hash_chain_lock |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
| Versions | 18.0 19.0 |
DE GoBD Hash-Chain
Tamper-evident SHA-256 hash chain over posted journal entries with exportable Unveraenderbarkeit (immutability) evidence
DE GoBD Unveraenderbarkeit Hash-Chain & Lock Proof
Key Features
GoBD Daily Merkle Anchor
GoBD Daily Merkle Anchor. Tracks Day, Sealed Entries, Merkle Root, Previous Day Root, Combined Root. One-click mark published, verify day.
GoBD Immutability Seal (Hash-Chain Link)
GoBD Immutability Seal (Hash-Chain Link). Tracks Reference, Journal Entry, Entry Number, Entry Date, Chain Sequence. One-click verify.
GoBD Seal & Evidence Export
GoBD Seal & Evidence Export. Tracks Seal pending entries first. One-click run.
DE GoBD Unveraenderbarkeit Hash-Chain &
DE GoBD Unveraenderbarkeit Hash-Chain & Lock Proof
Auditors regularly challenge the Unveraenderbarkeit
Auditors regularly challenge the Unveraenderbarkeit (immutability) of digital books.
Odoo's native period lock is
Odoo's native period lock is thin - it stops editing but produces no cryptographic proof that the posted records have not changed since posting.
This module builds a tamper-evident
This module builds a tamper-evident hash chain over posted journal entries:
When an entry is posted
When an entry is posted it is sealed - a SHA-256 hash is computed over its canonical content (date, journal, partner, amounts and every move line) and chained to the previous sealed entry's hash (block-chain style: each link contains the prior link's hash).
Use Cases
Screenshots
Daily Merkle Anchors
Gobd Seals Hash Chain
Seal Export Evidence
Verification Log
Why Choose This Module
When an entry is posted it is sealed - a SHA-256 hash is computed over its canonical content (date, journal, partner, amounts and every move line) and chained to the previous sealed entry's hash (block-chain style: each link contains the prior link's hash). A daily cron seals any still-unsealed posted entries automatically. Any later change to a sealed entry breaks the chain; a verification routine re-hashes the whole chain and reports the first broken link. You can export a signed-style immutability evidence pack (CSV of sequence, entry, content-hash, chain-hash, seal time + a summary PDF/HTML) to hand to the Betriebspruefer as proof of Unveraenderbarkeit.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: 35+
- Author: Pokutsoft
- Dependencies: account
- Support: support@pokutsoft.com
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module