Key takeaways
- Invoice and purchasing approvals: Partly. Approval steps are documented only for expense claims (Expense Claims app) and customer approval of estimates.
- Expense claim approvals: Partly. The Expense Claims app (from $5/month, included in the Premium cloud plan and above) lets employees submit claims marked paid by employee, assigns an approver who approves or refuses, and tracks reimbursement status.
- Vergo approvals are optional and run before coded spend posts into Akaunting.
Where should you go next?
- Akaunting AP and expense features: what's included and what to add
- Vergo's Akaunting integration
- Get started with Vergo
What Akaunting includes
Invoice and purchasing approvals
Partly. Approval steps are documented only for expense claims (Expense Claims app) and customer approval of estimates. A review of the bills help docs and the Sales/Purchase Orders app page (Draft, Sent, Confirmed, Issued statuses) shows no approval workflow for bills or purchase orders.
Expense claim approvals
Partly. The Expense Claims app (from $5/month, included in the Premium cloud plan and above) lets employees submit claims marked paid by employee, assigns an approver who approves or refuses, and tracks reimbursement status. It is a marketplace app rather than part of the free core.
What teams add alongside it
- AP automation / invoice capture
- Expense management app
- Approval workflow tool
Where Vergo fits with Akaunting
Vergo adds approvals on the spend before it reaches Akaunting. 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 Akaunting, coded to your category.
Frequently Asked Questions
Does it depend on the Akaunting edition or add-ons?
The Expense Claims app (from $5/month, included in the Premium cloud plan and above) lets employees submit claims marked paid by employee, assigns an approver who approves or refuses, and tracks reimbursement status.
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 Akaunting, with its receipt.



