Canadian Payroll 2019 YE Update Round 2

Microsoft released a “Round 2” update for Canadian Payroll for Dynamics GP. What is a round 2 update? It’s a change that wasn’t in the first update in December! Typically we don’t see this in Canadian Payroll but the CRA made a relatively last minute change to the federal basic personal amount (BPA for short) that necessitated an update. As it turns out, the update does not address that change from the CRA but it does fix 3 other bugs.

Here’s what you need to know and do if you are a Dynamics GP Canadian Payroll user.

UPDATE: January 20/2020

For whatever reason, there was quite the miscommunication with this update. The long story short is it does not handle the new CRA Basic Personal Amount formula and there are some manual updates required to have properly calculated income tax as a result. The relevant parts of this post are marked with **UPDATE** to clarify.

If you run this install, the GP core build number doesn’t change, but the Canadian Payroll dictionary version does. If you’re not sure if you have the update or not, check the Canadian Payroll control window for the version vs. what I’ve listed below.

Documentation & Downloads

The official blog with all of the details is here. ** UPDATE ** the blog has some updates to reflect the updates I am including here.

GP 2015

  • (Links removed, no longer valid)
  • Dynamics GP build: 14.00.1230
  • Canadian Payroll build: 14.00.1254

GP 2016

  • (Links removed, no longer valid)
  • Dynamics GP build: 16.00.0814
  • Canadian Payroll build: 16.00.0836

Dynamics GP

  • (Links removed, no longer valid)
  • Dynamics GP build: 18.2.1036
  • Canadian Payroll build: 18.2.1058

What’s changed?

There are a total of 3 changes in this service pack: two hot fixes around CPP and EI, and one fix around upgrading. If you were on Dynamics GP 2018 or Dynamics GP (aka 18.2), there is a 4th item: it fixes an error you may have received regarding a “caerr.cnk” file (and this was specific to 18.2).

In this section, I’m going to focus only on the payroll specific fixes.

Fix #1: 2020 CPP Maximums

This one is minor (relatively speaking), and time is on your side if you can’t install this tax update right away. Without this tax update, the CPP maximum will be over the allowed amount by $0.90. For most organizations, it will be a while before employees get to this point. By my math, you’d max out on CPP contributions by the end of February if your annual net income was $350,000. Even a $150,000 net income employee doesn’t max out until sometime in May so it will affect some of your higher earners but not for a while in most cases.

Fix #2: CPP & EI Maximums for 2019 T4

This is an issue that will impact you sooner rather than later because it’s T4-related. Without this tax update, the T4 creation process incorrectly uses 2018 maximums for box 24 (EI) and box 26 (CPP). This is fixable via a SQL script if you have already run the Create T4 process. The script is available on the official blog (re-linked here) to update CPY40101.

Do I need to run this script? It depends…

  1. If you have already run the Create T4 process for 2019, you need to either run this script OR install the tax update and re-run the Create T4 process. Depending on where you are in your T4 preparation process, re-creating may not be a big deal. If you’ve made a lot of edits, I would use the script.
  2. If you have not yet run the Create T4 process, I would install the tax update and don’t worry about any script.

Regulatory change: Federal Basic Personal Amount

This is the “big” change, and it’s a significant departure in how tax credits were used in the past. New for 2020, effective Jan 1, 2020, the federal basic personal amount has changed AND if you earn more than $150,473 in a year, it’s a calculation, not a flat amount.

Long story sort of short: when the initial year end changes were announced, the 2020 Federal BPA amount was $12,298. NOW the Federal BPA is $13,229 for most people and a calculation if you earn more than $150,473. Some details can be found here in the CRA’s Q&A. Here’s a screenshot of the gist of it. It’s now a formula. For income earners between $150,473 and $214,368, the BPA will decrease until you get to the original $12,298 number.

What does this mean? ** UPDATE **

This tax update IS NOT calculating the formula for the Basic Personal Amount. After the update, the Tax Credits window will still show the old value of $12,298 for Federal. You must update that yourself - the tax update will not change that nor is there a pre-built routine to update it.

The Microsoft blog has the script to run to mass update the value for all employees at once to the default amount of $13,229. There is no quick fix for employees who fall into the $150,473 to $214,368 range. For employees who make more than $214,368, the value of the Basic Personal Amount stays the same for 2020 as it was before this update: $12,298. I am going to prepare a separate blog on how to calculate the BPA for those employees with annual net income in the middle range where a calculation is required.

What are my options?

According to Question 7 of the CRA Q&A link above, employers can use $13,229 for all individuals until their payroll systems are updated to fully implement the proposed legislation. Here’s the exact text:

Whether you’ve installed the tax update or not, you could set your employees all to a Federal BPA of $13,229 per the above Q&A, and the system will calculate tax based on that BPA amount. I tested this and can confirm the results match what the new tax amount should be, and if I used a different BPA for those earning in the middle threshold, it calculated that correctly too.

The bad news is there is NO plan to address this that I’m aware of. This will cause a challenge to employers who have employees with variable annual incomes and there will be no easy way to address this, other than updating the BPA amount in the TD1 values > Tax Credits window if and when the net income rises to the amount within the threshold above or climbs above it.


There’s a fair amount to soak in with this but the bottom line is you cannot simply install this update and assume everything is fixed. While that is unfortunate, that is the current situation with this update.

comments powered by Disqus
Built with Hugo
Theme Stack designed by Jimmy