What makes reimbursements AI-native?
AI-native reimbursement removes the expense report rather than speeding it up. An employee texts a photo of the receipt; Vergo reads it line by line, infers the Xero coding from what was bought and from how your team codes similar spend, and chases anything missing itself. There is no form for the employee to fill in, no code for them to get wrong, and no app to download or portal to log into — the finance team in Xero reviews a proposal with its reason instead of fixing a report.
How does Vergo work with Xero?
Vergo connects directly through Xero's public API — self-serve, with nothing needed from your team or from Xero — and reads your chart of accounts, contacts and tracking categories. Confirmed claims are created in Xero as a bill to the employee as a contact, with the receipts attached — the same shape Xero's own expense claims produce once approved — and the employee is repaid in your usual payment run. New accounts and tracking values appear in Vergo as they are created in Xero, so nobody codes against a stale list. The full specification lives on the Xero integration page.
What does Xero need on each employee claim?
- Contact: the employee who is owed the money.
- Account and tracking: for every receipt line.
- Receipt: attached, so the approver never has to ask for it.
- Mileage: coded through the same model as receipts.
What does this look like day to day?
A salesperson pays for a client lunch and a train ticket on her own card. She texts both receipts. Vergo reads them, proposes entertainment and travel with her region and department as the tracking values, and her manager confirms. A bill to her contact with both receipts attached lands in Xero.
What does the employee have to do?
Text a photo of the receipt. Employees handle everything by text message — no app to download, no portal login — and Vergo chases a missing receipt itself instead of waiting for someone to submit a report. Mileage runs through the same coding model, so a drive and a receipt from the same trip are coded the same way and reach Xero together. The people least likely to install an expense app will still reply to a text, which is why claims stop sitting in wallets until month end.
What changes at month end in Xero?
The work moves from the end of the month to the moment of spend. Because coding happens when the receipt or invoice arrives, close in Xero becomes a review of exceptions rather than a pile of late expense reports. Card spend, employee reimbursements and AP invoices run through one coding model — same coding, same review, one reconciliation against the Xero structure — and payment stays on the rails you already use.
Where should you go next?
- Vergo's Xero integration
- Reimbursements for landscape companies on Xero
- See Vergo run employee reimbursements with Xero
Who runs Xero?
Xero is cloud accounting software run by small and growing businesses and the advisers who keep their books. It codes spend to an account plus tracking categories — up to four can exist, two active at a time — so choosing the right two values is most of the coding work. If your finance team lives in Xero, the employee reimbursements layer should adapt to it, not the other way round.
Does Vergo do employee reimbursements for Xero?
Yes. Employees text their receipts, Vergo codes each line against the structure it reads from Xero, and the approved claim reaches Xero ready for repayment through your usual process.
Does Vergo replace Xero?
No. Xero stays the system of record. Vergo sits in front of it, capturing, coding and reviewing spend before it reaches the ledger.
How is Xero connected?
Vergo connects directly through Xero's public API — self-serve, with nothing needed from your team or from Xero — and reads your chart of accounts, contacts and tracking categories.
Does it handle mileage?
Yes. Mileage runs through the same coding model as receipts, so both reach Xero together.
