Key takeaways
- Invoice and purchasing approvals: Yes. Workflow Groups control who can view, modify or promote (approve, post) purchase invoices, timesheets, expense claims and payments, with five seniority levels and value limits.
- Expense claim approvals: Yes. Expense management is built in.
- Vergo approvals are optional and run before coded spend posts into Aqilla.
Where should you go next?
- Aqilla AP and expense features: what's included and what to add
- Vergo's Aqilla integration
- Get started with Vergo
What Aqilla includes
Invoice and purchasing approvals
Yes. Workflow Groups control who can view, modify or promote (approve, post) purchase invoices, timesheets, expense claims and payments, with five seniority levels and value limits. Marketing pages also say purchase orders use the hierarchical approvals, but the PO processing help page does not describe an approval step.
Expense claim approvals
Yes. Expense management is built in. Released expense claims go to approvers, who can approve or reject whole documents or individual lines, with value limits and seniority rules set in Workflow Groups.
What teams add alongside it
- Expense management with receipt OCR
Where Vergo fits with Aqilla
Keep Aqilla's workflow for the documents it already routes; Vergo approves the spend before it reaches Aqilla. 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 Aqilla, coded to your expense type, VAT treatment and project.
Frequently Asked Questions
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 Aqilla, with its receipt.
