Dynamics NAV Localization Assessment
Your international Dynamics NAV implementation needs to be rolled out to more countries, but you don’t know how the NAV roll-out will be facilitated in the different countries.
Localizations are often underestimated in regards to their functional impact on corporate financial solutions. And in the Dynamics NAV environment it’s even more complex—with Microsoft providing localization in some countries, Partners in the PLLP program providing localization to others and finally there are countries supported by a partner solution.
On top of that is the effort required to stay up to date with changing requirements that are often underestimated. You will find that regulatory requirements vary tremendously from country to country. For example, just within Europe, VAT, taxes, and regulatory requirements can be completely different from one country to the other.
Furthermore, when you are working with ERP solutions across borders, there are surprises hidden in the details: never underestimate local complexity. You may have decided to use one language (English) across borders and streamlined your processes across your subsidiaries, which simplifies, but you’re not yet home safe. Localization is not limited to languages—far from it! PREPARING TO OVERCOME THE CHALLENGES
This paper will briefly introduce you to the sociocultural and
technical challenges of local ERP deployments, which are often
ignored or underestimated by international organizations at
their own peril.
PREPARING TO OVERCOME THE CHALLENGES This paper will briefly introduce you to the sociocultural and technical challenges of local ERP deployments, which are often ignored or underestimated by international organizations at their own peril.
A call with our experts
Deliver a list of countries in scope
Group requirements (business processes, languages, support requirements)
Questionnaire (if needed)
Dynamics NAV Localization
Review countries in Scope and align localization packages
Overview of available localization packages
Drivers for building the approach
Trade- off: localization strategies vs. application architecture
Knowledge sharing: CORE Strategy and Lifecycle