The problem: reconciliations that end in disputes
In most exchange systems, every entry is stored in a mutable database table. When two parties diverge, each searches for “the truth” in its own copy, and an edit window opens — the ledger itself becomes suspect. The dispute is not about the transfer, but about who holds the correct version.
The principle: signed, chained, immutable entry
On TEQ, every financial entry is written once, signed with a hash, and linked to the previous entry via prev_hash. The result is an accounting chain that differs from a classic ledger in only one way: no one — not even the system administrator — can modify an entry without breaking the chain.
Any modification attempt changes the entry’s hash and instantly breaks every subsequent entry. Tampering is not hidden — it is detected automatically, with a clear trace.
Correcting without destroying
Errors happen. But correcting on TEQ does not mean “delete the wrong entry”; it means adding a referencing reversing entry:
- The original entry stays intact (forever).
- A new entry is added, pointing back to the original via
reverses_entry_id. - The running balance corrects itself, and the full impact stays visible for audit.
This is the essence of respectable accounting: correct through transparency, not erasure.
What ends for companies?
- “Whose copy is right” disputes: one ledger, accepted by both parties.
- Audits that stretch for days: the auditor sees the full chain in a single glance.
- Fear of retroactive edits: impossible — every change is visible and signed.
The result for the company
Instant reconciliation, one-click review, and disputes that stop at the start. This is not an extra security layer — it is the correct way to build a financial ledger from the ground up.
Try the immutable ledger on your data with a free trial.