Key takeaways
- xTuple has time and expense sheets, so an add-on should win on card spend.
- Vergo ranks first for voucher distributions by inference and vouchers through the API.
- SAP Concur and Expensify work from expense reports; Ramp requires its own card.
- None lists an xTuple integration on its site, so ask how entries would reach it.
Where should you go next?
- Vergo's xTuple integration
- What expense management software integrates with xTuple?
- Get started with Vergo
Which expense management add-ons work best with xTuple?
- Vergo: G/L account, profit center and project by inference, text receipts, existing cards, vouchers created and posted through the API.
- xTuple time and expense: native sheets with approval, vouchered to AP.
- SAP Concur: expense suite with bank card feeds and 300+ connectors; best for travel-heavy companies.
- Expensify: receipt scanning and expense reports on existing cards.
- Ramp: best for companies moving to the Ramp Visa card.
What should an add-on do for xTuple?
- Produce vouchers, the object xTuple AP runs on.
- Fill every G/L segment you use.
- Reimburse employees as vendors, matching xTuple's pattern.
- Keep your cards.
Should you use time and expense sheets or an add-on?
Sheets suit project staff logging billable costs. For company cards, a sheet is an extra step nobody wants, and the voucher still has to be coded. The add-on should go straight from card transaction to coded voucher. Vergo proposes the coding by inference from your own accounting structure and history — no rule library to build, no keyword lists to maintain, and new vendors are coded on first sight.
How does Vergo connect to xTuple?
Vergo connects through xTuple's public API, reads G/L accounts and projects, and creates and posts vouchers with coded distributions. Reimbursements go to the employee as a vendor. Transactions are ready to code the moment they happen — no waiting for clearing — and once they clear, they sync into xTuple.
What should you ask each vendor?
Ask whether it produces xTuple vouchers or only an export file, whether it fills profit center and subaccount segments, and how it handles employees who must be set up as vendors to be reimbursed.
Frequently Asked Questions
Is Vergo an xTuple extension?
No extension is needed. Vergo connects through xTuple's public API.
Can Vergo and xTuple sheets run together?
Yes. Keep sheets for project time and let Vergo handle card spend.
Do we need new cards?
No. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
Does Vergo handle supplier invoices?
Yes. Card spend, employee reimbursements and AP invoices run through one coding model — same coding, same review, one reconciliation — and payment stays on the rails you already use.
Where are the integration details?
On the xTuple integration page.



