Key takeaways
- NAV has no native expense module, so every option is an add-on, a partner extension or an upgrade.
- Vergo ranks first for G/L and dimension coding by inference, on existing cards, with direct posting to NAV.
- Many expense tools now target Business Central first; for NAV, confirm how entries reach an on-premise server.
- Upgrading to Business Central brings Microsoft's own expense features, at the cost of an upgrade project.
Where should you go next?
- Vergo's Navision integration
- What expense management software integrates with Navision?
- Get started with Vergo
Which expense management add-ons work best with NAV?
- Vergo: account and dimension coding by inference, text receipts, existing cards, journal lines or purchase invoices posted through NAV's web services.
- Upgrade to Business Central: Microsoft's Expense Management and Expense Agent, released as a preview in NAV's successor.
- SAP Concur: travel and expense suite with bank card feeds.
- Emburse: expense and travel on existing card programs.
- Expensify: receipt scanning and expense reports on existing cards.
- Navan: travel-led expense management.
| 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 |
| Upgrade to Business Central | Any | Microsoft's Expense Management (preview) and Expense Agent | Native, after the upgrade |
| 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 |
What should an expense add-on do for NAV?
- Reach an on-premise server, through the web services NAV already publishes.
- Code dimensions, not only accounts. A blank department or project dimension breaks NAV reporting.
- Survive the upgrade. Pick a tool that also works with Business Central.
- Keep your cards.
Should you upgrade first or add a tool now?
If the Business Central upgrade is close and expense volume is low, waiting can make sense. If card spend is growing now, an add-on returns the time straight away. 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 NAV?
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. Vergo also integrates with Business Central, so the same coding carries on after the upgrade.
Frequently Asked Questions
Is Vergo a NAV extension?
No. Vergo is a separate platform that connects through NAV's published web services; NAV stays your ledger.
Will Vergo still work after we move to Business Central?
Yes. Vergo integrates with Business Central too.
Do we have to switch cards to get a NAV sync?
No. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
Does Vergo handle reimbursements for NAV?
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 Navision integration page.
