How to Prepare Microsoft Dynamics GP for a Multi-National Deployment, Part 2 - Typical Setup Challenges

In the first part of this series we looked at common localisation needs that accompany an international deployment of Microsoft Dynamics GP.  As we saw, there are both regional and country-specific needs that GP can meet, either with built in features, extra modules, add-on solutions, or customizations.

Beyond these very specific needs, a company that is preparing to roll out Dynamics GP to an international team should be aware of the variety of other locale-specific considerations that can determine a GP deployment's success.  These factors range from the mundane to the unexpected, but as any GP professional can attest, getting each one right is critical for a smooth multi-national deployment.


Requires FREE Membership to View

Become a Member Joining gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more, and it’s all FREE. You’ll also receive periodic email newsletters with the latest relevant articles and content updates.
About Ian Stewart

Ian Stewart is a Microsoft Dynamics GP MVP. He is a co-owner of Genesys Financial Systems, an European based International Microsoft Partner. Genesys provides localisation, implementation, support and development services, and out of hours support coverage for organisations with a presence in the US and Europe.

About Ian: 20 years’ experience in finance and IT, 16 with Microsoft Dynamics GP. Following an early career as a management accountant in the finance industry, Ian moved into the area of IT in business with the expansion of technology in the early ‘90’s, and then into Interim Management working with growing companies. He has led the implementation of many large-scale software installations for business in Europe, the USA and Asia.

Read full bio...