Key takeaways
- Invoice and purchasing approvals: Partly. Purchase orders go through a separate Release step, payables need approval for payment, and T&E worksheets need manager approval.
- Expense claim approvals: Yes. Time & Expense worksheets are approved by a manager before vouchering.
- Vergo approvals are optional and run before coded spend posts into xTuple.
Where should you go next?
- xTuple AP and expense features: what's included and what to add
- Vergo's xTuple integration
- Get started with Vergo
What xTuple includes
Invoice and purchasing approvals
Partly. Purchase orders go through a separate Release step, payables need approval for payment, and T&E worksheets need manager approval. Workflow (a package on the desktop client) chains assigned activities across modules, but no amount-based approval routing for POs or vouchers is documented.
Expense claim approvals
Yes. Time & Expense worksheets are approved by a manager before vouchering. Employees and contractors are set up as vendors, and processing creates an unposted AP voucher to reimburse them. The project guide places project accounting in the Enterprise edition, with an extension for other editions.
What teams add alongside it
- AP automation / invoice capture
- Expense management app
Where Vergo fits with xTuple
Vergo adds approvals on the spend before it reaches xTuple. 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 xTuple, coded to your G/L account, profit center and project.
Frequently Asked Questions
Does it depend on the xTuple edition or add-ons?
Purchase orders go through a separate Release step, payables need approval for payment, and T&E worksheets need manager approval. The project guide places project accounting in the Enterprise edition, with an extension for other editions.
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 xTuple, with its receipt.



