Key takeaways
- Invoice and purchasing approvals: Partly. The Purchase Requisition module lets employees raise requisitions that an Approval group approves or rejects before purchase requests are created. However, no configurable multi-level approval engine for supplier invoices or expenses is documented.
- Expense claim approvals: No. No official upstream expense-reimbursement module exists, per the Tryton forum and the module list.
- Vergo approvals are optional and run before coded spend posts into Tryton.
Where should you go next?
- Tryton AP and expense features: what's included and what to add
- Vergo's Tryton integration
- Get started with Vergo
What Tryton includes
Invoice and purchasing approvals
Partly. The Purchase Requisition module lets employees raise requisitions that an Approval group approves or rejects before purchase requests are created. However, no configurable multi-level approval engine for supplier invoices or expenses is documented.
Expense claim approvals
No. No official upstream expense-reimbursement module exists, per the Tryton forum and the module list. Reimbursements have to be handled as supplier invoices to the employee or through custom or third-party modules.
What teams add alongside it
- Expense reimbursement / receipt capture app
- OCR invoice capture service
Where Vergo fits with Tryton
Vergo adds approvals on the spend before it reaches Tryton. 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 Tryton, coded to your account and analytic axes.
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 Tryton, with its receipt.
