onboarding

This commit is contained in:
2025-07-11 19:59:51 -04:00
parent f53b4911e7
commit a3b2da9ab5
4 changed files with 91 additions and 29 deletions

File diff suppressed because one or more lines are too long

View File

@@ -1,4 +1,4 @@
# Sphinx build info version 1 # Sphinx build info version 1
# This file records the configuration used when building these files. When it is not found, a full rebuild will be done. # This file records the configuration used when building these files. When it is not found, a full rebuild will be done.
config: 568f480c232e819a9c6a7fb4f9382074 config: d31dc42d0cc8030fa3819858665f4bb0
tags: 62a1e7829a13fc7881b6498c52484ec0 tags: 62a1e7829a13fc7881b6498c52484ec0

View File

@@ -143,24 +143,19 @@
5.3. Required Federal and Provincial/Territorial Forms 5.3. Required Federal and Provincial/Territorial Forms
</a> </a>
</li> </li>
<li class="toctree-l2">
<a class="reference internal" href="#entering-employee-information-into-sage50">
5.4. Entering Employee Information into Sage50
</a>
</li>
<li class="toctree-l2"> <li class="toctree-l2">
<a class="reference internal" href="#content-review-highlights"> <a class="reference internal" href="#content-review-highlights">
5.5. Content Review Highlights 5.4. Content Review Highlights
</a> </a>
</li> </li>
<li class="toctree-l2"> <li class="toctree-l2">
<a class="reference internal" href="#review-questions-sample"> <a class="reference internal" href="#review-questions-sample">
5.6. Review Questions (Sample) 5.5. Review Questions (Sample)
</a> </a>
</li> </li>
<li class="toctree-l2"> <li class="toctree-l2">
<a class="reference internal" href="#example-evaluations"> <a class="reference internal" href="#example-evaluations">
5.7. Example Evaluations 5.6. Example Evaluations
</a> </a>
</li> </li>
</ul> </ul>
@@ -1162,14 +1157,13 @@ accurately and on time.
</li> </li>
</ul> </ul>
</section> </section>
</section>
<section id="entering-employee-information-into-sage50"> <section id="entering-employee-information-into-sage50">
<h3> <h4>
Entering Employee Information into Sage50 Entering Employee Information into Sage50
<a class="headerlink" href="#entering-employee-information-into-sage50" title="Link to this heading"> <a class="headerlink" href="#entering-employee-information-into-sage50" title="Link to this heading">
&para; &para;
</a> </a>
</h3> </h4>
<p> <p>
To enter a new employee into the Sage 50 Payroll module (Canada edition), start by navigating to the Employees &amp; Payroll section in the To enter a new employee into the Sage 50 Payroll module (Canada edition), start by navigating to the Employees &amp; Payroll section in the
Home window. Right-click the Employees icon and choose &ldquo;Add Employee&rdquo; to begin creating employee&rsquo;s record. Input the employee&rsquo;s full legal Home window. Right-click the Employees icon and choose &ldquo;Add Employee&rdquo; to begin creating employee&rsquo;s record. Input the employee&rsquo;s full legal
@@ -1180,6 +1174,13 @@ separately, as Sage50 does not automatically generate these. You&rsquo;ll also n
information is reviewed for accuracy, save and close the record to finalize setup. If you prefer a guided approach, Sage50 also offers information is reviewed for accuracy, save and close the record to finalize setup. If you prefer a guided approach, Sage50 also offers
an Employee Wizard to walk you through these steps. an Employee Wizard to walk you through these steps.
</p> </p>
<section id="entering-perdonal-information">
<h5>
Entering Perdonal Information
<a class="headerlink" href="#entering-perdonal-information" title="Link to this heading">
&para;
</a>
</h5>
<div class="admonition important"> <div class="admonition important">
<p class="admonition-title"> <p class="admonition-title">
Important Important
@@ -1193,6 +1194,8 @@ regulatory standards.
</p> </p>
</div> </div>
<img alt="_images/onboarding-employee_001.png" src="_images/onboarding-employee_001.png"/> <img alt="_images/onboarding-employee_001.png" src="_images/onboarding-employee_001.png"/>
</section>
</section>
<section id="review-questions"> <section id="review-questions">
<h4> <h4>
Review Questions Review Questions
@@ -1216,6 +1219,65 @@ Record of Employment (ROE), as it establishes the starting point for the employe
</p> </p>
</li> </li>
</ol> </ol>
<p>
#. Within the scope of Payroll Administration, how should the department ethically and legally respond when a supervisor requests access
to an employee&rsquo;s date of birth for the purpose of workplace recognition, given that this personal information is already held by payroll?
Additionally, what procedures or company-wide practices should be implemented to ensure that the sharing of such sensitive data complies
with privacy regulations and maintains proper standards for handling employee information?
</p>
<blockquote>
<div>
<p>
<a href="#id1">
<span class="problematic" id="id2">
*
</span>
</a>
Under Canadian payroll administration and the Personal Information Protection and Electronic Documents Act (PIPEDA), sharing an employee&rsquo;s date of birth&mdash;even for positive intentions like workplace recognition&mdash;is not legally or ethically appropriate without the employee&rsquo;s explicit consent.
</p>
</div>
</blockquote>
<p>
PIPEDA requires employers to:
</p>
<blockquote>
<div>
<ul class="simple">
<li>
<p>
Limit the collection, use, and disclosure of personal information to what is necessary for clearly identified business purposes.
</p>
</li>
<li>
<p>
Obtain meaningful consent before using personal data for any purpose beyond what it was originally collected for&mdash;such as payroll or benefits administration.
</p>
</li>
<li>
<p>
Protect employee privacy by restricting access to personal information on a strict need-to-know basis.
</p>
</li>
</ul>
</div>
</blockquote>
<p>
In this case, using the date of birth for celebrations or acknowledgments is outside the scope of payroll processing. Even if the Payroll
department holds this information, it cannot be disclosed to supervisors or other staff unless the employee has formally agreed to such use.
</p>
<p>
To make the practice of sharing employee birth dates for recognition purposes both appropriate and compliant, the Payroll department must
establish a structured framework aligned with Canadian privacy legislation, particularly PIPEDA. This begins with creating a formal
consent process, allowing employees to voluntarily authorize the use of their birth date for non-payroll purposes, such as birthday
celebrations. Consent must be clearly informed, specifying the intended use, who will access the information, and how long it will be
retained. Employees should also retain the right to withdraw consent at any time. The company&rsquo;s privacy policy should be revised to
include provisions for using personal information in recognition programs, and any updates must be effectively communicated to all staff,
including supervisors. Access to birth date data should remain restricted to authorized personnel, and the information must only be used
for its approved purpose. Payroll should maintain secure documentation of all employee consents and conduct periodic audits to ensure
proper data usage. In addition, training programs should be provided to supervisors and managers to reinforce privacy obligations and
encourage a culture of respect for personal data. By implementing these measures, the Payroll department can support positive workplace
initiatives while safeguarding employee privacy and meeting legal standards.*
</p>
</section> </section>
</section> </section>
<section id="content-review-highlights"> <section id="content-review-highlights">