Key takeaways
- Xledger is cloud finance built for multi-entity organisations, from small businesses to enterprise groups.
- Its Expenses module includes mobile receipts with OCR, card feeds, mileage, per diem and approval workflows.
- Spend is coded to customer-defined dimensions, such as department, project and fund.
- Vergo proposes account and dimensions from your history, texts for receipts and posts GL import items through Xledger's GraphQL API.
Where should you go next?
- Vergo's Xledger integration
- What expense management software integrates with Xledger?
- Get started with Vergo
How do you automate expense management in Xledger, step by step?
- Connect Xledger. Vergo connects directly through Xledger's GraphQL API, reads your accounts and dimensions, and posts coded card spend as GL import items. It is self-serve.
- Keep the cards you have. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
- Get receipts by text. Employees handle everything by text message — no app to download, no portal login — and Vergo chases missing receipts itself instead of waiting for a report.
- Propose account and dimensions. Vergo suggests the account, department, project and any other dimension your entity uses, with the reason.
- Post to Xledger. Confirmed spend lands in the general ledger with its coding intact, entity by entity.
What does Xledger need on each card transaction?
- Account: from the entity's chart.
- Dimensions: the ones you defined, such as department, project or fund.
- Entity: the right company in a multi-entity group.
- Receipt: kept for audit and VAT.
Where does Xledger stop and automation start?
Xledger describes automated coding to dimensions and projects inside its Expenses module, alongside OCR on receipts. That is a real step forward from typing. The hard part in a multi-entity group is the decision behind the coding: which fund a conference fee belongs to, or which project absorbs a software seat bought by a shared-services team. Vergo reads the receipt itself, line by line, and predicts the coding from what was actually bought, not just the vendor name on the header. Vergo proposes the dimensions from how your group coded similar purchases before.
A practical example
A charity group running three entities on Xledger gives cards to programme managers. One buys training materials and travel for a volunteer session. Vergo texts for the receipt, proposes the programmes entity, the training account and the restricted fund that paid for the last session, and a finance officer confirms. The GL import item posts to Xledger with the fund dimension set.
How Vergo handles this
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. In Xledger that means your own dimension values, per entity. 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.
Frequently Asked Questions
Does Vergo replace Xledger Expenses?
It can sit alongside it. Some teams keep Xledger Expenses for mileage and per diem claims and use Vergo for card spend.
Which dimensions can Vergo code?
Whichever your Xledger entities use. Vergo reads them and proposes values from history.
How does Vergo write to Xledger?
Through Xledger's GraphQL API, as GL import items. It is self-serve.
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.
Do we need new cards?
No. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
