CPP issue at age 70

SOLVED

We have an employee that turned 70 in August. An ever since then Businessvision wants to pay back his CPP that has been deducted so far this year. We have checked the CPP exempt and it won't let us zero it out in the batch. Any assistant would be appreciated.

Top Replies

  • Hi  ,

    Thanks for reaching out about the CPP deductions for your employee who turned 70. I see you've encountered an issue where Sage Businessvision is attempting to refund CPP deductions. This…

  • +1
    verified answer

    Hi  ,

    Thanks for reaching out about the CPP deductions for your employee who turned 70. I see you've encountered an issue where Sage Businessvision is attempting to refund CPP deductions. This was a known issue with the January 2023 payroll updates 7.92.13 and 7.92.14, but it has been resolved in update 7.92.15.

    To correct this for your employee, please ensure you have applied the latest update 7.92.15. After updating, follow these steps:

    1. Review the original cheque and note the CPP amount that was underpaid.
    2. Adjust the employee's Date of Birth under the Details tab, or uncheck the CPP exempt option under the Amounts tab to allow the program to recalculate CPP.
    3. Issue a supplementary timecard for the same period. Enter Regular pay with $1 and then with -$1, and total it.
    4. In the CPP field, enter the previously noted CPP amount as a negative figure. This should make the net pay equal to the CPP amount.
    5. Print the cheque, then revert the Date of Birth or reapply the CPP exempt as needed.

    Please note, if the employee was paid through direct deposit, you'll need to issue a manual cheque as corrections can't be made through the batch.

    For any assistance during this process or if further issues arise, feel free to reach out. Our support team, including Hugh who recently set up the 7.92.18 install, is here to ensure everything runs smoothly for you.

    Warm Regards,
    Erzsi

  • 0 in reply to Erzsi_I

    Thanks for your assistance. We found out we missed the last update 7.92.15. After running the update. The issue was fixed. 

  • 0 in reply to Todd Sales

    That's a relief! Thanks for the update on this Slight smile