Chapter 5 Journals

Journal Sequence Rules

When Odoo enables accounting inalterability, especially for EU compliance or audit-chain scenarios, it requires every posted journal entry to uniquely identify the previous posted journal entry.

This is used for:

• Hash or sequence chains.
• Audit traceability.
• Preventing deletion, insertion, or disorderly modification.

In other words, journal entry numbers must remain continuous and should not have gaps.

Different Odoo versions implement this rule differently. In Odoo 15, it was handled through a secure sequence number. From Odoo 17, the implementation changed and no longer relies on the old sequence object in the same way. Instead, it calculates from existing database records.

Therefore, when encountering this error, the troubleshooting strategy depends on the Odoo version:

An error occurred when computing the inalterability. Impossible to get the unique previous posted journal entry

The error means the journal contains a missing or inconsistent sequence. Possible causes include accidental deletion of journal entries or database inconsistency.

Implementation Advice

For production accounting databases:

• Do not delete posted journal entries manually.
• Avoid direct database changes to accounting records.
• Restrict who can reset posted entries to draft.
• Test invoice numbering and journal sequence behavior before go-live.
• When a sequence issue appears, diagnose against the exact Odoo version.

Journal sequence rules are part of accounting auditability. Treat them as compliance-sensitive configuration, not only as a numbering preference.

This chapter explained journal sequence continuity and inalterability errors. With this, the accounting part has introduced core accounting concepts, invoicing, payments, customer statements, and journals. The next part moves into project or related operational modules according to the manual structure.