Dynamics GP – Error Message PERIOD_KEY_INVALID when submitting VAT Return to HMRC

I had a client report this issue recently which was preventing them submitting the VAT return to HMRC via the government gateway. The exact error is below

After some digging it seems the period key is passed down from HMRC when the obligations are retrieved therefore its strange that the error is produced when submitting the VAT return as it should be using the same period key.

I looked at the TX00300 table (VAT Return Header) and I can see the PeriodKey was blank for the VAT Return ID in question

I then checked a clients system who I know has managed to process their VAT return successfully and this showed a PeriodKey in the TX00300 as per below

Therefore I can only assume that after pulling down the obligations either the PeriodKey wasn’t written to the TX00300 table correctly or the client accidentally changed a date in the VAT Return window which blanked the PeriodKey. Then, when they then tried to submit the VAT return they received the “PERIOD_KEY_INVALID” error.

To resolve the issue I had the client delete and recreate the VAT return ensuring no dates were altered after selecting the obligation and this then worked fine. (I did want to work through the whole process with them so I could check the PeriodKey in the TX00300 at every stage however unfortunately they processed everything before I had chance i.e. I wanted to check the PeriodKey value after getting the obligations, and then check it again after calculating and then prior to submitting)

In was a simple fix in the end but it was interesting piecing things together.

Thanks for reading.

Dynamics GP – The remittance reprint is including a remittance for a different vendor

A client reported that when reprinting a remittance via the “Recreate Check Stub” option it was correctly reprinting the remittance however another remittance for a totally different vendor was also printing at the same time?

The option being used for the remittance reprint is below

To troubleshoot I looked at the main table used on the “Reprint Check Remittance” layout in report writer.

As you can see from the image above this is the “PM Remittance Temp” table which on investigation is the PM80950 table.

When I queried this table in SQL I found a single row and the Vendor ID matched that of the remittance that was being tagged onto the reprint.

I therefore removed this row from the table by running a DELETE statement in SQL and now when I reprint the remittance it prints correctly.

I hope this helps someone else in the future if they come across the same issue.

Thanks for reading!

Thinking of making the move to Business Central? We can help

Dynamics GP – Error “Install Microsoft Word” when emailing a large number of Customer Statements

A client was experiencing the error “Install Microsoft Word” on the exception report for lots of statements when emailing a high volume of customer statements when running Dynamics GP 2013.

After searching online I found the following thread in the community forum https://community.dynamics.com/gp/f/32/t/137272

This mentioned the exact same issue and a user named Pam Robertson posted to advise of a fix in later versions of Dynamics GP.

I was curious to find this in the Microsoft documentation so I tracked down the fix list for Dynamics GP 2013 and a fix is indeed listed as per below for version 12.00.1920

I’ve since installed this at the client and can confirm it fixed the issue!

Therefore if you are on Dynamics GP 2013 (version 12.00.1920) or earlier and running into this issue applying this service will fix the issue.

A very quick post but I thought it worth putting out there in case anyone else encounters this issue and needs the evidence to show this is fixed in a later version of Dynamics GP.

Thanks for reading.