Canadian Payroll 2014 Year End Update for GP2015

//Canadian Payroll 2014 Year End Update for GP2015

Canadian Payroll 2014 Year End Update for GP2015

When GP 2015 was released, the code did not include the year end tax tables for Canadian Payroll and it was announced they would be released in the first patch/MSP for GP2015 in early 2015.

Well, late last week the fix was released for GP 2015 and now includes the 2014 year end update and any 2015 tax changes (plus other bug fixes unrelated to this).

If you were waiting to install GP2015, due to being a payroll user, now you can proceed with this update. If you had previously installed GP2010 or GP2013’s year end update, this patch is what you were waiting for to successfully upgrade to GP2015 as well.

The patch can be found here and more information can be found on the official support blog here.

By | 2017-08-13T11:46:28+00:00 February 11th, 2015|Canadian Payroll|2 Comments

2 Comments

  1. Shawn Arsenault February 27, 2015 at 9:51 am - Reply

    Do you know where I can get a complete Fix List concerning the Canadian Payroll Module we are on GP2010 and have reported many issues we have found, and have been told from Microsoft that some of them should be fixed with GP2015, I have only been able to find very limited info on the fix list

  2. Jen Kuntz February 27, 2015 at 10:49 am - Reply

    Hi Shawn,

    The fix lists on a given service pack or tax update, as far as I know, *are* the fix list. If there are things they fixed in GP2015 itself, as product improvements, there isn’t an obvious place to see that, since it’s something that typically isn’t provided with the core install of a new build, only with service packs. Obviously larger new features are highlighted everywhere on GP2015 but often smaller things are not.

    My recommendation would be to go to the official blog for Microsoft Dynamics support and post a question on there as you’re more likely to get a Microsoft support engineer’s response on it. The link to the support blog is in my post above if you don’t have it handy.

    Many times you only can verify if something is resolved by testing yourself to see that the issue you identified is working differently now.

Leave A Comment