Key takeaways
- Invoice and purchasing approvals: Yes. The Books+ workflow automation engine includes an 'approval condition' action for routing documents such as bills, POs and invoices.
- Expense claim approvals: Partly. Employee expense claims with manager approve/reject and journal posting configuration are in Deskera People/People+ (the HR product), not Books itself.
- Vergo approvals are optional and run before coded spend posts into Deskera Books.
Where should you go next?
- Deskera Books AP and expense features: what's included and what to add
- Vergo's Deskera Books integration
- Get started with Vergo
What Deskera Books includes
Invoice and purchasing approvals
Yes. The Books+ workflow automation engine includes an 'approval condition' action for routing documents such as bills, POs and invoices. Deskera ERP markets approval workflows for POs, invoices and expense changes.
Expense claim approvals
Partly. Employee expense claims with manager approve/reject and journal posting configuration are in Deskera People/People+ (the HR product), not Books itself.
What teams add alongside it
- AP automation / invoice capture (OCR)
- Expense management app (if not using Deskera People)
Where Vergo fits with Deskera Books
Keep Deskera Books's workflow for the documents it already routes; Vergo approves the spend before it reaches Deskera Books. 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 Deskera Books, coded to your expense account and tax.
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 Deskera Books, with its receipt.
