Welcome to the Dynamics GP Support and Services Blog. This new blog is designed to provide you the insights, knowledge and challenges that our support engineers tackle every day.
Hello Canadian Payroll Enthusiasts!
Recently, Service Canada has sent out a notice to Canadian Payroll employers advising that you should provide Records of Employment in a weekly format for 53 weeks, no matter what the employees actual pay schedule is (bi-weekly, semi-monthly, etc.)
Microsoft Dynamics GP back in 2007 (yes, I'm aging myself) added ROE 53 week capability for versions 9.0 and beyond.In my testing as well as speaking with Service Canada, what our system currently does is acceptable to them.I also made sure the ROE did not stop at my current pay period per year.Example, if my current pay period per year is 24, and I have worked for more than 24 pay periods, the ROE will create with additional periods.At this point, Service Canada is only encouraging customers to report in this fashion.I think this recent change was more for the paper ROE’s that are still the “older” way of reporting ROE.
Here is a bit more detail about how the ROE calculates in general:
The ROE amounts and hours will pull from the Payroll Employee Summary Expand – Canada window (click Cards, click Payroll – Canada, click Employee, and then click Calculated). The data needs to be listed in the Summary Expand window to generate the ROE. When the ROE is created it will also look at the Calculated field under the LY Calculated window as well (Inquiry | Payroll - Canada | Employee Last Year Information, and then click Calculated) to collect any LY information it needs to complete the ROE.
The following tables are used: CPY30250 (Payroll Calculation MSTR File) CPY50250 (Payroll Calculation MSTR File LY)
The ROE Total Insurable Earnings information will pull from the PEIInsEarnings24 field in the CPY30250/CPY50250.The ROE Total Insurable Hours information will pull from the PEIInsHours field in the CPY30250/CPY50250.Microsoft Dynamics GP will find all of the calculated records for the employee (one record per employee per batch). It finds the newest (by date) record that is not marked off (PMarkOff = 0). It then finds all of the transactions that made up this batch and grabs the transactions with the highest date. If this was unsuccessful, and the employee did not get paid in the current year or did not have enough pay periods in the current year, it will repeat this process with the history table (CPY50250).
Be careful of the mark off........ you can check the CPY30250 and CPY50250 to see if the transactions have been marked off (PMarkedOff=1). The CPY30250 table holds current year information and the PMarkedOff column will be a '0' up until the ROE is generated. The CPY50250 holds the historical information. When the ROE is generated, the PMarkedOff column will flip to a '1'. So if this is marked, it prevents the information from pulling onto another ROE.
If the transactions are marked off (PMarkedoff = 1) then they will not pull on the ROE and should be reset to 0 if you need them to pull.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Follow Microsoft Dynamics