Key takeaways
- Invoice and purchasing approvals: Partly. Approvals are built into specific modules rather than a configurable engine: purchase orders need a separate approver, with an optional second approval above a set amount, and expense reports have supervisor approval.
- Expense claim approvals: Yes. The core Expense Reports module runs Draft, Validated (email to the supervisor), Approved or Refused, then Paid, with separate approve and pay permissions and receipts attached to each report.
- Vergo approvals are optional and run before coded spend posts into Dolibarr.
Where should you go next?
- Dolibarr AP and expense features: what's included and what to add
- Vergo's Dolibarr integration
- Get started with Vergo
What Dolibarr includes
Invoice and purchasing approvals
Partly. Approvals are built into specific modules rather than a configurable engine: purchase orders need a separate approver, with an optional second approval above a set amount, and expense reports have supervisor approval. Supplier invoices only have a validate step; multi-level approval across documents comes from third-party modules.
Expense claim approvals
Yes. The core Expense Reports module runs Draft, Validated (email to the supervisor), Approved or Refused, then Paid, with separate approve and pay permissions and receipts attached to each report.
What teams add alongside it
- AP automation / invoice OCR
- Expense management with card feeds and mobile receipt capture
- Multi-level approval workflow
Where Vergo fits with Dolibarr
Vergo adds approvals on the spend before it reaches Dolibarr. 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 Dolibarr, coded to your accounting account.
Frequently Asked Questions
Does it depend on the Dolibarr edition or add-ons?
Approvals are built into specific modules rather than a configurable engine: purchase orders need a separate approver, with an optional second approval above a set amount, and expense reports have supervisor approval. The core Expense Reports module runs Draft, Validated (email to the supervisor), Approved or Refused, then Paid, with separate approve and pay permissions and receipts attached to each report.
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 Dolibarr, with its receipt.
