Microsoft’s Jodi Christiansen has, on the Inside Microsoft Dynamics GP blog, announced the release of the January hotfix which includes the Making Tax Digital (MTD) updates required for VAT submissions to HMRC from April.
The Microsoft Docs site has been updated with setup instructions; I need to get it downloaded and installed to confirm the functionality, as all of the setup is around the VAT 100 and not VAT Daybook. Clients with more complex VAT often need VAT Daybook which allows them to define which tax codes appear in which boxes on the VAT Return. We’ve previously been assured by Microsoft that the MTD update would include both VAT 100 and VAT Daybook so I need to check that this is in fact the case.
The hotfix can be downloaded from CustomerSource (login required):
- Microsoft Dynamics GP 2016
- Microsoft Dynamics GP 2018
The MTD changes are only available for Microsoft Dynamics GP 2016 and 2018; applying the hotfix will update you to the latest version of the R2 release of these versions. If you’re on a prior version you will need to either upgrade to 2016 or 2018 or source an alternative way of submitting to MTD, such as ISC Software’s Making Tax Digital add-in.
Sr. Technical Support Engineer Cheryl Waswick did a post yesterday on the Dynamics GP Support and Services Blog about the upcoming Making Tax Digital changes for VAT submission in the UK.
Microsoft have been fielding a lot of questions from partners about the VAT 100 Report in relation to Making Tax Digital and have put together some information on VAT 100 in a Q&A format.
As Cheyrl notes, that post should not be your sole source of information, but the information there may be useful.
Cheryl also says that a post is due soon with details on how Microsoft Dynamics GP will be meting the requirements of Making Tax Digital.
One of the problems with the standard Tax Reports ( ) in Microsoft Dynamics GP is that they will include only items requested for the date range, but the VAT 100 Return itself will select everything in the specified date range and also anything dated before this period which has not been included in previous VAT Returns.
This is a problem as it means you can not run a report before generating the VAT Return to see what would be picked up. However, a little thought and consideration of how the SmartList wildcards work and a workable solution presented itself.
In SmartList select the Tax Detail Transactions SmartList Favourite under Company and click on the Search button:
Under Search Definition 1 enter Tax Return ID in the Column Name. Set the Filter to begins with and enter [^2] in the Value.
This search definition will return all transactions which do not have a Tax Return ID beginning with a 2; this assumes you name your VAT Returns along the lines of 2014-08 to have them sorted by date. If, as some clients I have seen, you create your VAT Returns with the month’s long, or short, name first then replace the 2 with JFMASOND and all items not starting with one of those letters will be returned.
After upgrading a client from Microsoft Dynamics GP 10 to 2013 they started getting a problem when creating, or editing, creditors. The error only came up when they had loaded the options window:
Microsoft Dynamics GP – Please enter a valid tax registration number.
I did some testing and found that this error was produced when the Country Code field was set. Microsoft Dynamics GP 10 didn’t exhibit this behaviour, but there is a difference in the installation of version 10 and 2010. And that difference is the VAT Daybook.
In Microsoft Dynamics GP 2010, and later, the VAT Daybook module needs to be installed to use the VAT 100 report which I had installed during the upgrade process.
In this case, the client operates only in the UK and doesn’t need to have Tax Registrations recorded in GP, so they were able to just stop setting the Country Code field on the addresses.
We upgraded a client from Microsoft Dynamics GP 9 to Microsoft Dynamics GP 2010 recently, and the first time they tried to run the VAT 100 report they received a number of errors:
Microsoft Dynamics GP – An error occurred executing SQL statements.
Continue reading “Collation Conflict Printing The Tax Detail Report”