Key takeaways
- NAV users are established mid-market companies, often on their own servers, many planning a move to Business Central.
- Vergo ranks first because it codes NAV dimensions by inference, posts to NAV directly and keeps your cards.
- SAP Concur, Emburse, Expensify and Navan work with existing cards; Ramp and Brex are built around their own.
- Choose a tool that also works after a Business Central upgrade.
Where should you go next?
- Vergo's Navision integration
- What expense management software integrates with Navision?
- Get started with Vergo
How do the options rank for NAV users?
- Vergo: best overall. G/L and dimension coding by inference, text receipts, existing cards, direct posting to NAV and to Business Central after an upgrade.
- SAP Concur: best for travel-heavy organisations with bank card feeds.
- Emburse: best for expense and travel on existing card programs.
- Expensify: best for simple expense reports on existing cards.
- Navan: best when travel booking drives expenses.
- Ramp: best for companies ready to move to the Ramp Visa card.
- Brex: best for companies ready to move to Brex cards.
| Option | Cards | How coding is proposed | Route into NAV |
|---|---|---|---|
| Vergo | The cards you already have | Inference from your own NAV chart and dimension history, with the reason shown | Journal lines or purchase invoices through NAV's web services |
| SAP Concur | Existing cards through bank card feeds | Categorisation from merchant and transaction data | Ask how entries reach NAV |
| Emburse | Existing Amex, Mastercard or Visa programs, or Emburse Cards | AI categorisation | Ask how entries reach NAV |
| Expensify | Card-agnostic; also offers the Expensify Card | AI categorisation | Ask how entries reach NAV |
| Navan | Navan cards, or existing cards through Navan Connect | Categorises by merchant type and employee role | Ask how entries reach NAV |
| Ramp | Ramp Visa corporate card | Auto-coding trained on customer transaction patterns | Ask how entries reach NAV |
| Brex | Brex Mastercard corporate cards | AI expense management built into the card | Ask how entries reach NAV |
What matters most for NAV users?
- On-premise reach. The tool has to post to a NAV server, not only to a cloud ERP.
- Dimension accuracy. NAV reporting depends on department and project values being right.
- Upgrade safety. The expense tool should not need replacing when you move to Business Central.
- Card continuity. Long-standing NAV companies usually have long-standing bank relationships.
Why does Vergo rank first for NAV?
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. Every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. Vergo connects through the web services Microsoft built into NAV: your IT publishes them once on the NAV server, then Vergo reads your chart of accounts and vendors and posts coded journal lines or purchase invoices.
Do you have to change cards?
No. Vergo does not issue cards; connecting your existing cards involves no card applications, no re-issuing and no banking change. Your statement imports into the Payment Reconciliation Journal keep working as before.
Frequently Asked Questions
Is Vergo only for construction companies on NAV?
No. Vergo codes to whatever accounts and dimensions your NAV database uses, in distribution, manufacturing, services and more.
How is Vergo different from SAP Concur for NAV?
SAP Concur centres on travel and expense reports. Vergo codes each card transaction by inference as it happens and collects the receipt by text.
We are upgrading to Business Central. Should we wait?
No need. Vergo integrates with NAV now and with Business Central after the move.
How do we start?
Get started; your IT publishes NAV's web services once.
Does Vergo handle AP invoices too?
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.
