In short: Odoo 19 has no single switch that sends every vendor bill and payment through two people. You build it from parts: separate access rights, a review step on posted entries, trusted bank accounts and, where needed, Studio approval rules on the buttons that post or pay. Purchase orders do have a standard approval setting. First agree who prepares and who approves, then choose the lightest setup that enforces it.

One colleague enters a vendor bill, someone else checks it, and a third person releases the payment. That is what many growing companies expect from their ERP, and it is a question we regularly get at our helpdesk. For Odoo 19 the answer is more nuanced than yes or no.
This article sets out who should do what, what Odoo offers as standard, where Studio comes in and when custom work makes sense. We use the labels of the English interface. In a Dutch interface some labels read differently.
Why two steps are worth the effort
Two-step approval is not about distrust. It catches ordinary mistakes: a wrong amount, a bill entered twice, costs on the wrong project. It also helps against invoice fraud. The help text on bank accounts in Odoo itself warns about fake invoices with a fraudulent account number, and advises verifying new account numbers, preferably by calling the vendor.
Your accountant will probably ask how you have arranged this as well. Whether a specific control is required for your company is a question for your accountant, not for this article.
Start with who may prepare and who may approve
Decide this before you touch a setting. Odoo can only enforce a division of tasks that you have agreed on. A common division, which you can adapt to your own company, looks like this:
- Prepare the bill: an administrator enters the bill or checks the scanned version, links it to the purchase order and leaves it in draft.
- Approve the bill: the budget holder confirms that the goods or services were received and that the amount is correct.
- Post the bill: the bookkeeper or the approver confirms it, so that it enters the books.
- Prepare the payment: the bookkeeper selects the bills that are due and creates the payment or payment file.
- Approve the payment: someone other than the preparer, often a director, releases the payment in Odoo or at the bank.
- Trust new bank accounts: preferably someone who does not also prepare payments.
Are you a small team? Then not every role can be separated. At the very least, keep changing bank details and paying apart, and ask your accountant whether that is enough for your situation.
What Odoo 19 offers as standard
Draft, confirm and automatic posting
A vendor bill stays in draft until someone clicks Confirm. Only then does it get a journal entry and a number. After that it can no longer be edited without Reset to draft. Anyone with invoicing rights can confirm, so by default there is no separate step between entering and confirming.
Also check the Auto-post bills setting on the vendor. The options are Always, Ask after 3 validations without edits, and Never. For vendors whose bills need approval, Never is the logical choice.
Review of posted entries
Odoo has a To Review filter and a Reviewed button on journal entries. That gives a bookkeeper or accountant a work list of posted entries that still need a look. Note that this is a check after posting, not a block on payment. Test in your own environment which users may set this status.
Approval of purchase orders
Here Odoo does have a real standard setting. Under Purchase app, Configuration, Settings you enable Purchase Order Approval and set a Minimum Amount. Orders above that amount get the status To Approve, unless the person confirming has administrator rights in Purchase.
That is approval before the purchase. If bills follow purchase orders, much of the decision has already been taken by the time the bill arrives. Control policies and 3-way matching add a check on received quantities: the bill shows a Should Be Paid field. According to the documentation, that field flags changes but does not block them.
Trusted bank accounts
Each vendor bank account has a Send Money toggle that shows Trusted or Untrusted. Only users in the Validate bank account group and system administrators can switch it on. For payment methods that need a vendor bank account, the payment wizard does not create payments to accounts that are not trusted. The number of a trusted account can no longer simply be changed.
In our view this is one of the most useful controls in this list, because it tackles the fraud risk directly and needs no extra development.
Payment files and the bank as second step
With a payment file, such as SEPA through batch payments, Odoo creates the file and the bank executes it. The documentation on batch payments describes a Validate button, but no approval step. So the second signature often sits at the bank. Ask your bank whether it can require a second authorisation.
In Odoo 20 you can pay bills from Odoo through a payment connection, where your bank supports it. You can read more in Accounting in Odoo 20. That makes clear agreements on who may prepare and approve payments even more important.
Audit trail
The Audit Trail report, under Accounting and Review, logs changes to accounting fields with date, user, and old and new values. An optional restrictive mode protects these records against deletion. This is not an approval, but it does show afterwards who did what.
What requires Studio
Do you want Odoo to actually hold back the Confirm or Validate button until someone has approved? Then you use approval rules in Studio. Studio is an Enterprise app, so check whether your subscription includes it. The steps from the documentation:
- Open Studio on the view with the button and select the button.
- In the Properties tab, click Add an approval step.
- Choose Approvers, an Approver Group or both. Approvers receive an activity when approval is requested.
- Optionally use the filter icon to limit when the step applies, for example only above a certain amount.
- Add a second step if needed, with an Approval Order. Exclusive Approval prevents one person from approving two steps on the same record.
Approvers can delegate their rights, optionally until an end date. Decisions appear in the chatter. A user without authorisation who clicks the button gets an error, and the approvers receive an activity.
Remember that the rule sits on a button. So test whether other routes, such as list view actions, automatic posting, imports and integrations, also pass through your rule. Treat Studio changes as customisation and test them again at every upgrade. Our upgrade checklist helps with that.
When custom work makes sense
Standard features and Studio cover a lot. Custom work starts to make sense when:
- approval depends on a matrix of amount, department and cost centre that changes regularly;
- approvers should be able to approve outside the back end, for example on a portal page;
- the rule must hold on every route to posting, not just on one button;
- you want an overview of what is waiting with whom, including reminders;
- several companies in one database follow different rules.
Custom work needs maintenance, so try the lightest route first. At DAADit, AI builds and a consultant checks, at a fixed price of €1,000 per app. See how that works.
A practical route in five steps
- Write the division of tasks on one page and discuss it with your accountant.
- Clean up access rights so that people only have what they need. See adding a user without too many permissions.
- Turn on the standard controls: Auto-post bills on Never for the relevant vendors, trusted bank accounts and purchase order approval.
- Add Studio rules only where standard falls short, and try them first in a test environment.
- Test with real users, not with an administrator. Can the preparer skip the approval step anywhere?
Common pitfalls
- Testing as administrator. A Purchase administrator is not stopped by the minimum amount, so your test says nothing about ordinary users.
- Too many administrators. Separation of tasks means little if half the company has every right.
- The approver is away. Arrange delegation or a substitute before the holidays, otherwise bills get stuck.
- Changes after approval. Test what happens when an approved bill goes back to draft and is changed.
- A new account number from an email. Verify it through a phone number you already know, not the one in the email.
- Splitting orders. A minimum amount can be avoided with several small orders.
What this means for you
You usually do not need a big project. We generally advise this order: agree on the roles, clean up rights, use trusted bank accounts and purchase order approval, and only then add Studio or custom work. You can stop as soon as the risk fits what your company and your accountant accept.
Frequently asked questions
Can Odoo approve vendor bills in two steps as standard?
Not with one setting. Odoo 19 does offer draft bills, a review step on posted entries, trusted bank accounts and purchase order approval. If the button must really be blocked until someone approves, use Studio approval rules or custom work.
Who may mark a vendor bank account as trusted?
Users in the Validate bank account group and system administrators. Preferably give this right to someone who does not also prepare payments, and verify new account numbers by phone with the vendor where possible.
Do I need Studio for an approval flow in Odoo?
Not always. Much of the control comes from access rights, trusted bank accounts and purchase order approval. Studio comes into view when a button may only work after someone has approved. Studio is an Enterprise app, so check whether your subscription includes it.
Finally
Would you like to know which approval setup fits your company? Contact DAADit Group or take the free Business Scan.