Dynamics NAV, formerly Navision, is an enterprise resource planning (ERP) software designed by Microsoft for small and medium-sized businesses. It covers accounting, commercial management, logistics, and production within a single database. Its deployment and configuration largely depend on the chosen integration partner, which affects the quality of daily operations.
End of support for NAV 2018: a timeline that requires decisions
The last marketed version, Dynamics NAV 2018, remains under Microsoft extended support until January 2028. After this date, no functional fixes or security updates will be released.
A second deadline falls on April 30, 2031: Microsoft will then end the Annual Service Plans (Enhancement Plan, Advantage Plan) and the possibility of purchasing new perpetual user licenses. Any company still using NAV after 2031 will find itself without extension capabilities or support safety net.
This double cut changes the nature of the decision. It is no longer a question of whether migrating to Dynamics 365 Business Central is relevant, but rather determining when and how to carry it out. To fully understand the stakes before planning this transition, using Dynamics NAV software with ASCI first allows you to make the most of the existing system during the remaining support period.
Accounting management and invoicing in Dynamics NAV: what the standard covers
The financial module of NAV manages general accounting, multi-dimensional analytical accounting, debtor and creditor entries, fixed assets, and cash management. This scope allows for the centralization of all financial flows without resorting to third-party accounting software.
Electronic invoicing relies on structured formats that facilitate validation and automatic bank reconciliation. Customer and supplier invoices follow a configurable validation circuit, with VAT management by regime and by country.
Bank reconciliation and payment
NAV includes a bank reconciliation module that imports statements in standard format, then offers automatic matching of entries. Payment processing, whether it involves SEPA transfers or direct debits, is configured directly in the finance module administration.
This level of automation significantly reduces the time spent on repetitive accounting tasks. Financial data remains consolidated in a single repository, simplifying monthly and annual closings.
Role of a specialized integrator in optimizing NAV processes
An ERP delivered as standard never exactly covers the business processes of a given company. The gap between the default configuration and operational reality is precisely the area of intervention for an integrator.
A specialized integrator adapts NAV to existing processes rather than the other way around. This involves configuring validation flows, creating custom reports, and developing additional modules in C/AL or AL depending on the version.
- Audit of management processes to identify gaps between the NAV standard and the actual needs of the company
- Configuration of analytical dimensions, chart of accounts, and approval circuits tailored to the internal organization
- User training by role (accountant, purchasing manager, inventory manager) to ensure effective adoption
- Corrective and evolutionary maintenance, including monitoring Microsoft support deadlines
Without this support, companies underutilize their ERP. They circumvent the system with parallel spreadsheets, which fragments data and multiplies the risks of error.
Migration to Business Central: preparing the transition from NAV
Dynamics 365 Business Central is the cloud successor to NAV. Microsoft offers migration programs supported by partners, with discounts of up to 30% on the Business Central subscription for NAV customers with an active extension plan.
The migration is not just a technical change of platform. It involves reviewing existing customizations, validating the compatibility of specific developments, and retraining teams on a rethought interface.
What changes concretely
Business Central operates natively in the cloud, eliminating the need for internal server infrastructure management. Updates are automatically deployed by Microsoft twice a year.
- Customizations in C/AL must be rewritten in AL (the development language of Business Central)
- Third-party extensions installed on NAV require compatibility checks with the cloud environment
- Historical data (accounting entries, item records, supplier history) can be migrated via dedicated tools, but the volume and quality of data determine the project’s duration
Planning the migration at least 12 to 18 months before the end of support allows time to correct data, test processes, and train teams without calendar pressure.
Data and administration: maintaining system reliability on a daily basis
The value of an ERP relies on the reliability of its data. A poorly filled field in an item record or an incorrectly assigned accounting account propagates through all downstream entries: invoices, financial statements, VAT declarations.
The daily administration of NAV requires strict data entry rules and regular checks of data consistency. User profile access rights limit modifications to authorized individuals, reducing manipulation errors.
Integrated reporting solutions (role-based views, dashboards, RDLC reports) allow for quick detection of anomalies. An unusual discrepancy on an expense account or an inconsistent supplier balance can be spotted before it turns into an accounting problem during closing.
NAV remains a powerful tool for companies that utilize it correctly during its support period. The combination of appropriate configuration, rigorous administration, and a competent integration partner determines the actual quality of management achieved, much more than the version of the software itself.