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.

CanPay ROE issue fixed with January 2015 hotfix

This is a little tardy but I thought I’d share it in case it affects anyone…

For Dynamics GP 2010 users only, there was an issue after installing the year end update where the ROE Generate Batch File window gave an error message and was missing text on the buttons, making it difficult to use (if it worked at all). This issue has been resolved in the GP 2010 January hotfix, released Jan 30, 2015.

Canadian Payroll 2014 Year End Update

Hello folks!

It’s that time of year again… and the tax table updates / year end updates for Dynamics GP2010 and Dynamics GP2013 were just released, for English installs. For French installs, they are hoping for early next week.

Canadian Payroll – Sept 1, 2014 tax update (Ontario only)

Well, the “no mid-year tax update” euphoria didn’t last too long… 🙂

As a result of the June 2014 Ontario election and subsequent budget in July 2014, there are tax changes, affecting Ontario only and only affecting those with incomes > $150,000. The tax changes are effective for September 1, 2014 tax tables, but are retroactive to January 1, 2014.

This update is somewhat optional as you can read below, and organizations need to decide how many of their employees it affects and if the employee(s) affected can authorize manually changing the withholding for the last 4 months of the year to accommodate the change instead of putting a new service pack in now.

Canadian Payroll – No 2014 Mid Year tax update!


This isn’t new news if you have heard this through the grapevine already but for those of you who haven’t heard, there are no tax changes for 2014 mid year in Canadian Payroll for Dynamics GP.

Enjoy your Canada Day free of service pack stress 🙂

(Shortest post ever!)

New Hotfix – many Cdn Payroll fixes

This post is a little late as it came out last week… however, better late than never!

A new hotfix was released for GP2010 and GP2013. Here are the details:

Cdn Payroll – Things that make you go hmmmm

After my last post debacle (if you missed it, you missed it!), I’ll stick to blogging about things I know best!

This is a strange one, one of those things that makes you go “hmmmmmm”.  I never understand how this happens, if it’s been here for years or just never been noticed?

Canadian Payroll ROE changes coming

For those users on Dynamics GP2010 and GP2013, there is a hotfix currently planned for March 2014.

The ROE (Record of Employment) has recently changed to require some fields to be zero filled that Dynamics GP doesn’t zero fill today.  This was a change that Microsoft learned about quite late in the process, hence the need for a hotfix when it’s ready.

So, stay tuned! I’ll post again when the hotfix is released.

Canadian Payroll 2013 Year End Tax Updates

It’s that time of year again! Cue the Christmas/Holiday carols of choice in the background please…

UPDATE #3: Canadian Payroll year end update for GP2010 was released on December 19th, 2013, both English and French.  GP2013 was released December 20th, 2013.

Update on Account Number error in Canadian Payroll

A couple of years ago around this time of year, I got a call from a client of mine with a strange error in Canadian Payroll.  At the time, I ran into other significant issues in trying to help with said error, and at the time, I blogged/ranted about it here.

Fast forward to last month, when I received an email from another customer who was asking me “did you ever find out what the issue was with that error? We are having the same problem now!”.  We exchanged emails and I researched what notes I had taken at the time, and in the end, she confirmed for me that what worked for my client also worked for her.

So, this post is just an update on the issue and at least one resolution, in case it helps someone else out there. Some of this is a repeat of the rant blog, without the rant!