We had a client report the error “No Obligations found for the Year 2020” when trying to retrieve the obligations when doing the VAT return. They were running Dynamics GP 2018 version 18.00.0704.
The exact error is below
We checked all the usual things like company VAT number, and also tried when logged in as “sa” even though the relevant service pack has been applied, however the error persisted. (more details on troubleshooting can be found in this Microsoft link)
I then had a colleague run a fiddler trace and he noticed that on the tunnel to the HRMC API there were calls using TLS 1.0 and on further investigation the message “The function requested is not supported”
My colleague suspected a change on the HRMC side which was preventing TLS 1.0 from working.
We suspected the file VAT100ElectronicSubmission.DLL located in the GP client folder was responsible for this functionality so I checked the version currently installed which was 18.0.705.0
I then copied the VAT100ElectronicSubmission.dll file from my Dynamics GP 18.3 local install which is version 18.3.1181.0 to the users PC. (i.e. the latest version)
Now when we tried again this all worked! The obligations were retrieved successfully and we are now presented with the “Select Obligations” window
We also tried another PC which had previously had the same issue and this also worked!
Therefore we can only surmise that something has changed at HMRC’s side and there are now issues with certain versions of the VAT100ElectronicSubmission.dll files on older versions of GP.
We now plan on rolling out Dynamics GP 18.3 to all PCs at this site and are waiting to see if this affects other users on the older version.
Again we can only guess, however it seems something may have changed at the HMRC side which is preventing making tax digital submissions when you have an older version of the VAT100ElectronicSubmission.dll file. We found the solution is to replace this file with the most recent copy available with Dynamics GP 18.3.
Fingers crossed this helps others who may encounter this issue.
I came across a situation where a user needed to post a credit card payment via a payment journal with a VAT element so I thought I’d document on my blog 🙂
In order to do this first create a Payment Journal batch with the relevant balancing account, in my case a credit card, and also select the highlighted VAT options below:
** Please note you may have to go to the General Journal Template for Payments and tick these ON before you can select them for the batch.
With the option “Copy VAT Setup to Jnl. Lines” selected, the VAT posting groups will be copied from the GL code and VAT will be calculated.
With the option “Allow VAT Difference” selected, changes can be made to the calculated VAT amounts.
If you only have one G/L expense code to record VAT its fairly simple. You can pickup the relevant G/L code, which should default the “VAT Bus Posting Group” and “VAT Prod. Posting Group”, and the system will calculate the VAT for you. You can then just leave the “Bal Account No.” as the bank account.
Now when you post the entry you will get VAT entries as well as G/L and Bank Account Ledger Entries:
If you wish to record VAT for more than one G/L code you can list the expense codes and blank off the “Bal. Account No” on each line and then have the final line entry as the balancing credit card bank account as per below. (again the VAT posting groups have defaulted from the G/L code)
Now when you post the batch you’ll get the relevant VAT entries as well as G/L and Bank Account Ledger Entries:
If you have the “VAT Difference” option ticked on the batch you can change the “VAT Amount” at any time if this differs from the actual VAT you need to post.
I hope you find this useful if you ever need to post payments with VAT.