We have made the decision not to invest in transitioning the Russian payroll capabilities in Dynamics AX 2012 R3 over to Dynamics 365.
However, we’ll continue to support existing Russian payroll capabilities for organizations on an Enhancement Plan during the mainstream support and extended support through October 12, 2021 and January 10, 2023, respectively. For more information about Dynamics AX 2012 R3 lifecycle, read this article.
Although we do not recommend it, organizations can continue using Russian payroll capabilities with the knowledge that all regulatory updates and non-security hotfixes for Dynamics AX 2012 R3 will end on October 12, 2021, and security hotfixes will end on January 10, 2023.
Here are answers to some common questions for organizations impacted by this decision.
Why is support of Dynamics AX 2012 R3 Russian payroll capabilities not being continued in future releases?
Payroll is not included in the global strategic focus of the Dynamics 365 portfolio. Partners and ISVs are best positioned to provide payroll functionality that is compliant with local regulations and tax updates.
What Russian payroll solution is recommended when I move to Dynamics 365 Finance?
We recommend that organizations work with their implementation partner to determine the best local payroll solution based on their specific needs.
Does being active on a support or service plan ensure continued support for the Dynamics AX 2012 R3 solution?
Yes. Organizations active on an Enhancement Plan will receive mainstream support and extended support. The mainstream support for Dynamics AX 2012 R3 ends on October 12, 2021. Extended support for Dynamics AX 2012 R3 ends on January 10, 2023. For more information about Dynamics AX 2012 R3 lifecycle, read this article.
Can I continue to use the Russian payroll capabilities included in Dynamics AX 2012 R3?
Yes, but regulatory updates and non-security hotfixes for the Russian Payroll feature for Dynamics AX 2012 R3 will be discontinued on October 12, 2021.
Is support for Dynamics AX 2012 R3 Russian payroll capabilities being retired?
No. Dynamics AX 2021 R3 is included in mainstream support until October 12, 2021, which means Microsoft provides security hotfixes, non-security hotfixes, and regulatory updates. After the end of mainstream support, it will be included in extended support from October 13, 2021 to January 10, 2023. Microsoft will continue to provide security hotfixes only. There won’t be additional support for non-security hotfixes nor will there be regulatory updates. Dynamics AX 2012 R3 will be out-of-support starting on January 11, 2023. For more information about Dynamics AX 2012 R3 lifecycle, read this article.
Will the Russian payroll capabilities of Dynamics AX 2012 R3 be available in Dynamics 365 on-premises deployments?
Russian payroll capabilities of Dynamics AX 2012 R3 won’t be available in Dynamics 365 as a cloud service or for on-premises deployment. We suggest you work with your implementation partner to determine the best option for you.
What if I want to continue to use the Russian payroll capabilities after the end of the mainstream support for Dynamics AX 2012 R3?
Organizations using Russian payroll capabilities in AX 2012 R3 are welcome to use it after it is discontinued. However, we do not recommend doing this, as payroll regulations are continuously changing, and the existing product will not be compliant.
Will out-of-the-box integration be provided with any payroll solution for Russia, similar to integration with some US solutions, such as Ceridian or ADP?
Microsoft works with ISVs on enabling seamless integration with payroll providers for different geographies. Monitor Microsoft AppSource and other communication channels for alternative solutions.
Next steps
We recommend that you contact your implementation partner to determine the best payroll solution to meet your needs and build a plan to migrate to a new solution.
Send email to RUPayrollInquiry@microsoft.com with any questions about these changes. Find more information about the Russian payroll capabilities in the documentation.
