Key takeaways
- Dolibarr's own module handles claims and approval; an add-on helps with coding and receipts.
- Vergo leads because it posts entries through Dolibarr's own API on the cards you have.
- General tools like Expensify, Zoho Expense and BILL need checking for how they would reach a self-hosted instance.
- Open source users should favour add-ons that do not require moving banks.
Where should you go next?
- Vergo's Dolibarr integration
- What expense management software integrates with Dolibarr?
- Get started with Vergo
Which expense management add-ons work best with Dolibarr?
- Vergo: suggests type and account; texts for receipts; keeps your cards; posts supplier invoices through the REST API and prepares expense reports for it.
- Dolibarr Expense Reports: the built-in module for claims and approval.
- Expensify: receipt photos grouped into reports, for teams used to that pattern.
- Zoho Expense: technical teams can script against its API themselves.
- BILL: payables with BILL's own card, a larger change for a small office.
| Option | Cards | How coding is proposed | Route into Dolibarr |
|---|---|---|---|
| Vergo | The cards you already have | Inference from your own Dolibarr structure and history, with the reason shown | Supplier invoices posted through the REST API; expense reports prepared for it |
| Expensify | Card-agnostic; also offers the Expensify Card | AI categorisation | Ask how entries reach Dolibarr |
| Zoho Expense | Existing corporate card program | Zia reads receipts for merchant, date, amount and tax | Ask how entries reach Dolibarr |
| BILL | BILL's own corporate card | BILL AI auto-categorisation | Ask how entries reach Dolibarr |
What should an add-on do for Dolibarr?
- Map to expense types so accounting accounts follow.
- Attach receipts to the entry.
- Leave approval and payment in Dolibarr.
Why the API matters for Dolibarr
Dolibarr instances are often self-hosted and customised. An add-on that works through the REST API module, with a key you issue and can revoke, fits that model better than exports and imports. 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 Dolibarr?
You enable Dolibarr's REST API module on your instance and issue Vergo a key; Vergo then reads your third parties and posts card purchases as coded supplier invoices through Dolibarr's API, with expense reports posted through the same API. Transactions are ready to code the moment they happen, so the office is not waiting for statements.
Frequently Asked Questions
Is Vergo a Dolibarr module?
No. Vergo reaches Dolibarr from outside, through the REST API module.
Can we revoke Vergo's access?
Yes. Access uses a key you issue on your instance.
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 details?
On the Dolibarr integration page.
