Is it possible to use standard non-localized W1 version of Dynamics NAV for roll-out to Russia?

One of the most frequent questions I’m asked is whether it is possible to use W1 version for the implementation of Dynamics NAV in Russia, or is it obligatory to use only Russian localized version. Those who ask this question are hoping that they can take their existing solution, based on W1 version or any other country localization and apply it to Russian entity just by doing regular company settings and perhaps switch on Russian language on the server.

The answer to this question depends on the scope of the implementation and what processes it aims to cover. Obviously, in terms of the business processes Russia is very close to all the other countries, and ERP functionality for Sales, Purchases, Planning, Production, Warehouse and Logistics of W1 version can be also applied and used in Russia. Thus, to some extent, it is possible to use W1 Dynamics NAV version in Russia.

However, it is possible only to some extent.

1. If you are planning to use only Dynamics NAV for all processes, including Financials for accounting and taxation, it is inevitable to use Russian localized version, otherwise it will be not possible to fulfill both statutory requirements and local business practice. You can refer more here for learning the financials differences of Russian NAV version. It is not possible to use W1 version for doing full Russian accounting, otherwise it would be not better than handling the accounting just in Microsoft Excel.
2. If you plan to limit corporate solution for handling just the core corporate business processes, and leave finance to some other (local) software for statutory reporting purposes, you would need either to make double-booking or make the integration to feed the postings from corporate NAV to local accounting software. Both are additional costs, and you would also face many issues to resolve. Couple of samples:
   
   • First, you would most likely need to have the print forms of documents which should support your basic processes, as they need to be provided to customers mainly realtime together with shipping of items or provisioning of services. So to make sales, it is necessary to provide to your customers with a set of documents, e.g. Proforma Invoice (or Prepayment Invoice, used for indicating the banking payment details), Way-Bill or Act of acceptance of services (which is by nature is an “Invoice” in European terms) and a VAT invoice – a document, showing how much VAT is in the transaction, so customers would be able to deduct it further. I’ve blogged about those documents some time ago here). W1 version of Dynamics NAV does not have these documents in Russian language, and you would need to create them for your database, used in Russia.
   • Then, the other example can be the document numbers. When booking certain purchase invoice, the external document number of the invoice, provided by the vendor, needs to be input to the system. For that, you have the standard “External Document No.” field, available in W1 version. However, you also inevitably need to register VAT invoice number and VAT invoice date, which most likely you will receive from your vendor. Those fields are present in localized Russian version of Dynamics NAV, but not in the W1 version. Those numbers you need to feed to your accounting system, or input them there manually, which neglects your integration efforts.

SUMMARY: To some extent, it is possible to use W1 non-localized version of Dynamics NAV in Russia, however it is much more handy to use the localized version, officially supported by Microsoft, in order to satisfy at least basic requirements of sales business process for print forms of sales documents. If you aim to respond to full set of requirements for local financials – accounting and taxation – it is inevitable to operate with a localized Russian version, as the amount of differences is huge. There can be many aspects, affecting your implementation process. Remember to consult with trusted local Microsoft Partner for gaining support of your roll-out and processes design when going to Russia.