Key takeaways
- Invoice and purchasing approvals: Partly. Purchase documents can be held in draft and then approved (posted), with access controlled by roles: predefined roles from the Standard plan and custom roles from the Advanced plan. However, no configurable multi-step approval workflow for purchase invoices or POs is documented.
- Expense claim approvals: Partly. Employee expense reports can be sent into the Inbox and converted to purchase documents that an accounting user reviews and approves, but no dedicated employee expense-claim, approver-routing or reimbursement workflow is documented (HR approval flows cover absences and time records).
- Vergo approvals are optional and run before coded spend posts into Holded.
Where should you go next?
- Holded AP and expense features: what's included and what to add
- Vergo's Holded integration
- Get started with Vergo
What Holded includes
Invoice and purchasing approvals
Partly. Purchase documents can be held in draft and then approved (posted), with access controlled by roles: predefined roles from the Standard plan and custom roles from the Advanced plan. However, no configurable multi-step approval workflow for purchase invoices or POs is documented.
Expense claim approvals
Partly. Employee expense reports can be sent into the Inbox and converted to purchase documents that an accounting user reviews and approves, but no dedicated employee expense-claim, approver-routing or reimbursement workflow is documented (HR approval flows cover absences and time records). Holded Card spending is controlled with per-card limits and permissions.
What teams add alongside it
- Employee expense report and reimbursement app
- Invoice approval workflow tool
Where Vergo fits with Holded
Vergo adds approvals on the spend before it reaches Holded. Approval workflows are optional and fit how you already control spend: route by GL account, by amount, or by project — or skip approval flows entirely and let policy flags catch only what breaks a rule. Approved card spend posts into Holded, coded to your account, project and tags.
Frequently Asked Questions
Does it depend on the Holded edition or add-ons?
Purchase documents can be held in draft and then approved (posted), with access controlled by roles: predefined roles from the Standard plan and custom roles from the Advanced plan.
Can Vergo route approvals by project?
Yes. Route by GL account, by amount or by project, or skip approval flows and let policy flags catch only what breaks a rule.
What happens after approval in Vergo?
The coded card spend posts into Holded, with its receipt.
