Skip to main content
Pending validationOdoo 20.0Community and Enterprise

I cannot post in a locked period or a closed fiscal year

Symptom​

You type a date from a period that is already closed on a journal entry. Warnings appear at the top and, when you click Post, an Invalid Operation window opens. The entry stays in Draft and is not saved.

Message​

On a manual journal entry dated 15/12/2025, in a company with the 2025 fiscal year closed (Accountant profile), two warnings appear first:

“The date is being set prior to: Global lock date (31/12/2025). The journal entry will be accounted on 29/10/2026 upon posting.”

“302 days since the end of the month this entry refers to (limit of CIRC art. 123.º n.º 3). Post it or review its date; nothing is blocked.”

When you click Post:

“The fiscal year 2025 (01/01/2025 to 31/12/2025) is closed: you cannot create the entry account.move dated 15/12/2025. Why: a closed fiscal year is locked so that accounts already approved do not change. How to fix it: post it in an open fiscal year or, if it is really necessary, ask Fiscal administration for an exception with a reason (Accounting › Close › Year-end closing › Lock dates and exceptions). (To see it, turn on developer mode.)”

The messages were triggered in the demo database. The first warning says the entry “will be accounted on” today, but it is not: posting is refused and the date does not change. The final message has two parts that are not meant for you: “account.move” is a technical name for the journal entry, and developer mode is not needed (the path is below).

Verified causes​

  • The fiscal year is closed. When the fiscal year is closed, the Global Lock Date moves to its last day (in the demo, 31/12/2025). No entry dated up to that day can be posted.
  • There are other lock dates. Besides the global one, the company may have a Tax Return Lock Date, Sales Lock Date, Purchase Lock Date and Hard Lock Date. Each one closes its type of entry up to that date.
  • “Fiscal administration” is a fiscaldoo access right, not the Tax and Customs Authority, nor a value of the Profile field. It is the access that can open exceptions: the administrator has it.

What to check​

  1. The date of the entry: is it really from a closed period, or is it a mistake?
  2. The company's lock dates, in Accounting › Close › Year-end closing panel › Lock dates and exceptions. The list shows each date in force, who set it, the reason and the state (in the demo, “Global lock date”, 31/12/2025, “Closing of fiscal year 2025 (01/01/2025 to 31/12/2025)”, In force). The Accountant does not have this panel.
  3. Whether the entry can go to the open period. A forgotten expense from a closed year, for example, may have to be treated as a correction of prior years, not posted in the closed year. Pending validation by a certified accountant: treatment of an expense or income of a fiscal year already closed (NCRF 4, errors and changes in estimates) and the effect on Corporate Income Tax (IRC).

How to fix it​

The date was wrong (Accountant profile)​

  1. Click Close.
  2. Type a date in the open period and click Post.

The entry has to go to the closed period​

Only with an exception to the lock date, and only with the certified accountant's decision. The administrator (or whoever has the extra access Fiscal administration) opens and revokes the exception; the entry is posted by whoever the exception covers.

  1. In Accounting › Close › Year-end closing panel, open Lock dates and exceptions › Exceptions and revoking. This list shows the active exceptions and has the link Open the lock dates.
  2. Click Open the lock dates: Lock dates opens, with the Company and the current dates. In Global Lock Date, type a date earlier than the entry's (in the example, 30/11/2025, for an entry dated 15/12/2025). The screen warns “Global lock date moved back from 31/12/2025 to 30/11/2025: this opens an exception (only for you, until revoked); the date of the company is kept.” and shows The exception applies to (Only for me or For everyone) and Exception valid until.
  3. Choose For everyone if someone else is going to post (for example, the Accountant). In Exception valid until, set a near date and time, and type the Reason. Click Apply. The message confirms: “Exception opened. Global lock date moved back to 30/11/2025 (for everyone, until 29/10/2026 23:00:00); the company date is still 31/12/2025.”
  4. Whoever the exception covers posts the entry with the date in the closed period. The lock date warning no longer appears; the warning about days since the end of the month remains.
  5. As soon as the entry is posted, close the exception. In Exceptions and revoking, open the exception's line and click Revoke with reason. In the Revoke lock date exceptions window (“The reason you give is stored on the exception and in the audit log, with who revoked it and when.”), type the Reason and click Revoke. The exception becomes Revoked and leaves the list of active exceptions. If you do not revoke it, it ends by itself on the Exception valid until date.

With the Certified accountant profile, step 2 shows a different warning: “Your profile cannot open it: it needs the group "Fiscal administration". Ask a user with that profile; nothing will be saved if you press Apply.”

In the demo, on a copy of the database: the administrator opened the exception for everyone until 29/10/2026 23:00, with a reason; the Accountant posted the entry MISC/2025/00060, dated 15/12/2025, with the lines 6241 Electricity debit 100.00 € and 2722 Creditors for accrued expenses credit 100.00 € (checked on the posted entry); the administrator revoked the exception with a reason. After the revocation, Back to draft on that entry was refused with the closed fiscal year message: the period was closed again. So that the example would not stay in the 2025 accounts, the entry was reversed on the same date before the revocation (MISC/2025/00061, with the lines swapped).

Who does it: the administrator (opens and revokes the exception) and the profile that posts the entry.

The Hard Lock Date only moves forward and cannot be undone: a period with a hard lock does not accept exceptions.

Expected result​

  • With the date corrected, the entry is posted in the open period and gets a number (for example MISC/2026/…).
  • With the exception, the entry is posted with the date in the closed period. After the revocation, the period is closed again and the exception is recorded as Revoked, with the reason, who opened it and who revoked it.

When to contact support​

  • The message appears with a date later than every lock date in the list.
  • The exception is active, for you, and posting is still refused.
  • You need to correct a period with a Hard Lock Date.

Information to send​

  • The company, the date of the entry and the journal.
  • The full text of the message, copied from the screen.
  • The lines of the Lock dates and exceptions list (a screenshot will do).
  • The profile you logged in with.
Versions: Odoo 20.0Community and Enterprisefiscaldoo 20.0 (master d88933a51)ID DOC-0345
Was this page helpful?