If your accountant is the only person who can press Post on a vendor bill, month-end queues up behind them. The AP team keys in bills all month, the drafts pile up, and the week before the VAT return turns into a posting marathon. Odoo 19 changes the options you have here, and the change deserves its own decision during your upgrade. Leave it alone and the default access rights decide for you.
What Odoo 19 changed about posting rights
According to the Odoo 19 release notes, published in September 2025, users who have only the Invoicing or Invoicing & Banks access level can now post journal entries. When they do, the posted entry is flagged "To review" for an accountant, meaning a user with Bookkeeper or Administrator rights. Once an accountant has reviewed the entry, the Invoicing user can no longer reset it to draft.
This article describes Odoo 19 Enterprise with the Accounting app installed. The access level names come from the release notes.
In practice, the clerk who entered the bill can finish it, and the accountant moves from approving every bill one by one to working through a review list. The lock after review matters too: a reviewed bill cannot be quietly pulled back to draft and edited by the person who entered it.
A bill waiting for review is already in your VAT figures
The review happens after the bill is posted. While it waits in the To review list, it is already in your payables, your aged balances and the tax figures that feed your VAT return. If a clerk posts a bill with the wrong tax or the wrong vendor and nobody reviews it before the return is prepared, the error reaches the return.
So the review flag is a control only if someone works the list on a fixed schedule. Without that, you have moved the bottleneck from posting to correcting, and corrections after posting are slower: a credit note or a reset to draft, followed by posting again.
The duplicate checks that make clerk posting safer
The second part of the Odoo 19 change is better duplicate detection on invoices and bills. Warnings now come in two levels. A red warning marks a likely duplicate that should be corrected; a yellow warning marks a possible duplicate to check before posting. After posting, only red warnings remain, and on bills the warning banner stays visible after posting instead of disappearing. The Reference field of affected bills is highlighted in the list view, so a reviewer can spot them without opening each bill.
Bills flagged as possible duplicates are also excluded from automatic posting. If some of your vendors are set to post their bills automatically, a suspected duplicate stays out of the ledger until a person posts it.
One more change helps the matching side. When a vendor bill is imported from an XML file or through OCR, Odoo 19 searches the whole bill, including the line descriptions, for a purchase order reference. Bills where the vendor wrote the PO number in an odd place are more likely to land against the right order, which leaves the clerk less to fix by hand.
How much of a trail you need
The release notes also say a light, non-restrictive audit trail is now on by default for everyone. That gives you a record of changes without blocking anyone from editing.
If your auditors or your own policy require posted entries that cannot be changed at all, the journal setting Secure Posted Entries with Hash does that. Odoo's documentation is clear that it is one-way: once an entry is posted in a journal with this setting on, you cannot disable it, and secured entries cannot be edited. Turn it on for the purchase journal only after your team is comfortable with how corrections will work, because every mistake will then need a reversing entry.
When we would let AP staff post
Our view is that clerk posting works well when three conditions hold. Payments are approved by someone other than the person who posts the bill, so a wrong bill cannot also be paid by the same hand. An accountant clears the To review list before each payment run and before each VAT return, on dates written into the closing calendar. And bill volume is high enough that posting is a real queue.
We would keep posting with accountants when one person both posts and pays, when volume is low enough that the accountant posts in an hour a week, or when nobody can name who owns the review list. In that last case, the To review flag turns into a backlog that grows quietly until the year-end audit finds it.
Decide this as part of your Odoo 19 rollout plan, alongside the rest of the access rights, and test it on a copy of your data with real bills before you switch it on. If you are planning the move now, our Odoo version upgrade service covers this kind of access review as part of testing.
Changing a user's access level takes a minute. Before you do it, put three things in writing: who works the To review list, on which day of the month, and who corrects a bill that fails review.
