Does Navision have built-in expense management?

Key takeaways

• No native expense module: NAV records expenses through general journals and purchase documents.
• In later NAV releases, employees have their own ledger, so out-of-pocket expenses post to the employee's account and are paid through a payment journal.
• Microsoft's new Expense Management features belong to Business Central, NAV's successor, not NAV.
• Vergo codes card spend to G/L accounts and dimensions by inference and posts through NAV's web services.

Where should you go next?

• Vergo's Navision integration
• What expense management software integrates with Navision?
• Get started with Vergo

How does NAV handle expenses today?

• Employee expenses: a general journal line with the employee as the account, then a payment to the employee's bank account, applied like a vendor payment.
• Company card spend: journal lines or purchase invoices keyed from the card statement.
• Bank statements: imported into the Payment Reconciliation Journal, which matches payments by statement text.
• Coding: a G/L account plus dimension values on every line.

Where does that leave work for finance?

• Receipts arrive late, by email or envelope, and someone matches them to statement lines.
• Dimensions are chosen by hand, so department and project reporting depends on whoever keyed the line.
• Bank feeds are limited on premise: Microsoft's Yodlee feed extension is online-only, so on-premise sites import files instead.

When is a separate tool worth it?

When more than a handful of people carry company cards, or when close waits on receipts. 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. 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.

How Vergo works alongside NAV

NAV stays your ledger and your posting rules still apply. 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. Every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. 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.

Should you wait for Business Central?

Business Central is adding its own expense features, but upgrading from NAV is a project measured in months. Vergo integrates with NAV now and with Business Central after the move, so expense automation does not have to wait for the upgrade.