Key takeaways
- Invoice and purchasing approvals: Yes. Studio approval rules add one or more ordered approval steps (named approvers or groups, optional conditions) to any button, such as confirming a PO or posting a bill, and the separate Approvals app handles request types like procurement and payments; both Studio and Approvals are Enterprise-only.
- Expense claim approvals: Yes. Employees group expenses into expense reports that users with at least Team Approver rights approve or refuse (individually or in bulk), after which reports are posted and reimbursed individually, in bulk, or through payslips. However, the documentation describes a single manager approval step rather than multi-level routing.
- Vergo approvals are optional and run before coded spend posts into Odoo.
Where should you go next?
- Odoo AP and expense features: what's included and what to add
- Vergo's Odoo integration
- Get started with Vergo
What Odoo includes
Invoice and purchasing approvals
Yes. Studio approval rules add one or more ordered approval steps (named approvers or groups, optional conditions) to any button, such as confirming a PO or posting a bill, and the separate Approvals app handles request types like procurement and payments; both Studio and Approvals are Enterprise-only. Purchase also has an Order Approval setting that sends POs above a minimum amount to a manager (documented in older Odoo versions).
Expense claim approvals
Yes. Employees group expenses into expense reports that users with at least Team Approver rights approve or refuse (individually or in bulk), after which reports are posted and reimbursed individually, in bulk, or through payslips. However, the documentation describes a single manager approval step rather than multi-level routing.
What teams add alongside it
- Expense management app
- AP automation / invoice capture
- Multi-level purchase approval modules (Odoo Apps Store)
Where Vergo fits with Odoo
Odoo's own workflow can keep governing the documents listed above. Vergo's approvals sit on the spend before it reaches Odoo. Approval workflows are optional and fit how you already control spend: route by GL account or by amount — or skip approval flows entirely and let policy flags catch only what breaks a rule. Approved card spend posts into Odoo, coded to your account and analytic distribution.
Frequently Asked Questions
Does it depend on the Odoo edition or add-ons?
Studio approval rules add one or more ordered approval steps (named approvers or groups, optional conditions) to any button, such as confirming a PO or posting a bill, and the separate Approvals app handles request types like procurement and payments; both Studio and Approvals are Enterprise-only.
How does Vergo route approvals?
By GL account or by amount, or skip approval flows entirely and let policy flags catch only what breaks a rule.
What happens after approval in Vergo?
The coded card spend posts into Odoo, with its receipt.
