Key takeaways
- Aqilla has built-in expenses, so an add-on should remove line coding, not replace approval.
- Vergo leads on type, VAT and project suggestions for existing cards.
- Established names such as SAP Concur, Expensify and Emburse should each be asked how they reach Aqilla.
- VAT reclaim accuracy is worth testing on real receipts.
Where should you go next?
- Vergo's Aqilla integration
- What expense management software integrates with Aqilla?
- Get started with Vergo
Which expense management add-ons work best with Aqilla?
- Vergo: suggests type, VAT and project; receipts by text; existing cards; documents posted through the API.
- Aqilla expense management: the native submission and approval flow.
- SAP Concur: for groups that standardise on it for travel.
- Expensify: a report flow many employees already know.
- Emburse: for companies keeping a major-network card program.
| Option | Cards | How coding is proposed | Route into Aqilla |
|---|---|---|---|
| Vergo | The cards you already have | Inference from your own Aqilla structure and history, with the reason shown | Journal or Purchase Invoice documents posted through the API; Expense documents prepared for it |
| SAP Concur | Existing cards through bank card feeds | Categorisation from merchant and transaction data | Ask how entries reach Aqilla |
| Expensify | Card-agnostic; also offers the Expensify Card | AI categorisation | Ask how entries reach Aqilla |
| Emburse | Existing Amex, Mastercard or Visa programs, or Emburse Cards | AI categorisation | Ask how entries reach Aqilla |
What should an add-on do for Aqilla?
- Pick the expense type correctly.
- Get VAT right.
- Keep Aqilla's approval in the loop.
Native or add-on?
For a team that submits a few claims a month, Aqilla's own feature is enough. For card programs with many purchases, the cost is in choosing types and projects line by line. 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 Aqilla?
Vergo connects to Aqilla's API, reads your accounts and suppliers, and posts card spend as coded Journal or Purchase Invoice documents through the API, with claims posted as Expense documents through the same API. Coding begins when the purchase happens rather than when someone sits down to submit.
Frequently Asked Questions
Is Vergo an Aqilla partner?
It is independent of Aqilla and exchanges documents through Aqilla's API.
Can Vergo and Aqilla expenses run together?
Yes. Documents Vergo posts go through Aqilla approval.
Do we need new cards?
No. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
Does Vergo handle purchase 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 details?
On the Aqilla integration page.
