<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
{font-family:"Calisto MT";
panose-1:2 4 6 3 5 5 5 3 3 4;}
@font-face
{font-family:Roboto;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.paragraph, li.paragraph, div.paragraph
{mso-style-name:paragraph;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.normaltextrun
{mso-style-name:normaltextrun;}
span.spellingerror
{mso-style-name:spellingerror;}
span.eop
{mso-style-name:eop;}
span.contextualspellingandgrammarerror
{mso-style-name:contextualspellingandgrammarerror;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Good morning,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This is a follow up regarding PERS Pension Employer contributions going to object code 3210. PLEASE NOTE:
<b>employees were NOT directly impacted by this issue.</b><o:p></o:p></p>
<p class="paragraph" style="margin:0in;vertical-align:baseline"><span class="normaltextrun"><span lang="EN" style="font-family:Roboto;color:#212121"><o:p> </o:p></span></span></p>
<p class="paragraph" style="margin:0in;vertical-align:baseline">DAS Workday Payroll has identified a solution to the January 2023 payroll PERS Pension overcharges and made reversing entries that were part of the March run 1 payroll. Those entries reversed the
overcharged January PERS Pension costs charged to agencies. The original issue was caused by an error in the configuration for the original PERS Pension employer costs and unfortunately the resolution (creating a new PERS Pension code) caused the PERS Pension
costs to be duplicated in January 2023. This will not occur going forward. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="paragraph" style="margin:0in;vertical-align:baseline"><span class="normaltextrun"><span style="color:black">PERS Pension is an employer paid cost that funds the retirement benefit for all employees and is not specifically tied to that employee’s retirement
account. This adjustment is an accounting entry that corrects the PERS Pension amounts overcharged to agencies in January. </span></span><span class="eop"><span style="color:black"> </span></span><span style="font-size:9.0pt;font-family:"Segoe UI",sans-serif"><o:p></o:p></span></p>
<p class="paragraph" style="margin:0in;vertical-align:baseline"><span class="normaltextrun"><span style="color:black">For employees who are PERS members, below is an example of the PERS Pension correction displayed on March 31,
</span></span><span class="contextualspellingandgrammarerror"><span style="color:black">2023</span></span><span class="normaltextrun"><span style="color:black">
</span></span><span class="spellingerror"><span style="color:black">payslips</span></span><span class="normaltextrun"><span style="color:black">:</span></span><span class="eop"><span style="color:black"> </span></span><span style="font-size:9.0pt;font-family:"Segoe UI",sans-serif"><o:p></o:p></span></p>
<p class="paragraph" style="margin:0in;vertical-align:baseline"><img width="626" height="45" style="width:6.5208in;height:.4652in" id="Picture_x0020_1" src="cid:image002.jpg@01D96C5E.734A38F0"><span class="eop"><span style="color:black"> </span></span><span style="font-size:9.0pt;font-family:"Segoe UI",sans-serif"><o:p></o:p></span></p>
<p class="paragraph" style="margin:0in;vertical-align:baseline"><span class="eop"><span style="font-family:Roboto;color:#212121"> </span><o:p></o:p></span></p>
<p class="paragraph" style="margin:0in;vertical-align:baseline"><span class="normaltextrun"><span style="color:black">Agencies looking to search for these entries in Workday you can use the following report...<o:p></o:p></span></span></p>
<p class="paragraph" style="margin:0in;vertical-align:baseline"><span class="normaltextrun"><b><span style="color:black">PAY | Detailed Cost Allocation by Worker Deductions</span></b><span style="color:black">. You’ll want to search under ‘Deduction(s)’ for
‘PERS Pension Correction (Central Payroll Use ONLY)’. This deduction code was created specifically for those correcting entries. You’ll want to use the March pay period and it will show as a retro entry under the February pay period (02/01/2023 – 02/28/2023).
Those entries were done in February to help make them stand out more but also allow for as many entries to flow through to SFMA. There will be another batch of reversing entries, much smaller, coming over on March run 2.<o:p></o:p></span></span></p>
<p class="paragraph" style="margin:0in;vertical-align:baseline"><span class="normaltextrun"><span style="color:black"><o:p> </o:p></span></span></p>
<p class="paragraph" style="margin:0in;vertical-align:baseline"><img width="430" height="613" style="width:4.4791in;height:6.3819in" id="Picture_x0020_6" src="cid:image003.jpg@01D96C5E.734A38F0" alt="Graphical user interface, text, application, email
Description automatically generated"><span class="normaltextrun"><span style="color:black"><o:p></o:p></span></span></p>
<p class="paragraph" style="margin:0in;vertical-align:baseline"><span class="normaltextrun"><span style="color:black"><o:p> </o:p></span></span></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">DAS Workday Payroll Project Team<o:p></o:p></p>
<p class="MsoNormal">Project webpage: <a href="https://www.oregon.gov/das/HR/Pages/Payroll-time-tracking.aspx">
https://www.oregon.gov/das/HR/Pages/Payroll-time-tracking.aspx</a><o:p></o:p></p>
<p class="MsoNormal"><img border="0" width="274" height="138" style="width:2.8541in;height:1.4375in" id="Picture_x0020_2" src="cid:image004.png@01D96C5E.734A38F0" alt="PTT logo for email sig (2)"><span style="font-family:"Calisto MT",serif"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> OSPS-News <osps-news-bounces@omls.oregon.gov> <b>
On Behalf Of </b>Announcements from OSPS to the users of the Oregon State Payroll Application<br>
<b>Sent:</b> Thursday, March 23, 2023 1:42 PM<br>
<b>To:</b> OSPS-News (osps-news@omls.oregon.gov) <osps-news@omls.oregon.gov><br>
<b>Subject:</b> OSPS E-News ~ Workday Payroll PERS Overcharges<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Payroll partners,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">DAS Workday Payroll discovered an issue related to PERS pension employer costs for object code 3210 (PERS). The PERS pension employer costs were not properly handling mid-month transfers. This was corrected but this change duplicated
the PERS pension costs for the month of January 2023. These costs came through in the January run 2 and February run 1 payroll runs.
<b>Employees were NOT directly impacted by the issue.</b><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The Workday Payroll team is currently testing a fix to reverse these overcharges with the goal of implementing this fix by March run 1. We are partnering with DAS SFMS to help provide feedback and analysis for these corrections. These
reversals should come through the SFMA integration and not require manual adjustments in SFMA.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We understand what caused these overcharges and this will not happen again moving forward. We will provide an update on March 28 on this effort.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We apologize for any inconvenience these overcharges caused.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">DAS Workday Payroll Project Team<o:p></o:p></p>
<p class="MsoNormal">Project webpage: <a href="https://www.oregon.gov/das/HR/Pages/Payroll-time-tracking.aspx">
https://www.oregon.gov/das/HR/Pages/Payroll-time-tracking.aspx</a><o:p></o:p></p>
<p class="MsoNormal"><img border="0" width="274" height="138" style="width:2.8541in;height:1.4375in" id="Picture_x0020_3" src="cid:image004.png@01D96C5E.734A38F0" alt="PTT logo for email sig (2)"><span style="font-family:"Calisto MT",serif"><o:p></o:p></span></p>
</div>
</div>
</body>
</html>