Key takeaways
- Invoice and purchasing approvals: Partly. Documented approval steps exist for draft client bills and trust (client) account payment requests with request permissions; supplier invoices have only a Lock/Approve posting status controlled by data permissions.
- Expense claim approvals: not publicly documented; confirm with Actionstep.
- Vergo approvals are optional and run before coded spend posts into Actionstep.
Where should you go next?
- Actionstep AP and expense features: what's included and what to add
- Vergo's Actionstep integration
- Get started with Vergo
What Actionstep includes
Invoice and purchasing approvals
Partly. Documented approval steps exist for draft client bills and trust (client) account payment requests with request permissions; supplier invoices have only a Lock/Approve posting status controlled by data permissions. Configurable approval routing for supplier invoices, POs or expenses is not documented.
Expense claim approvals
Expense claim approvals are not publicly documented for Actionstep. Confirm with Actionstep before you budget.
What teams add alongside it
- AP invoice capture / OCR
- Employee expense management and receipt capture app
Where Vergo fits with Actionstep
Vergo adds approvals on the spend before it reaches Actionstep. 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 Actionstep, coded to your matter, as disbursements.
Frequently Asked Questions
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 Actionstep, with its receipt.
