<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 12 (filtered medium)">
<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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoNormalCxSpFirst, li.MsoNormalCxSpFirst, div.MsoNormalCxSpFirst
{mso-style-type:export-only;
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoNormalCxSpMiddle, li.MsoNormalCxSpMiddle, div.MsoNormalCxSpMiddle
{mso-style-type:export-only;
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoNormalCxSpLast, li.MsoNormalCxSpLast, div.MsoNormalCxSpLast
{mso-style-type:export-only;
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Tahoma","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Tahoma","sans-serif";}
p.Style1, li.Style1, div.Style1
{mso-style-name:Style1;
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Tahoma","sans-serif";}
p.Style1CxSpFirst, li.Style1CxSpFirst, div.Style1CxSpFirst
{mso-style-name:Style1CxSpFirst;
mso-style-type:export-only;
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Tahoma","sans-serif";}
p.Style1CxSpMiddle, li.Style1CxSpMiddle, div.Style1CxSpMiddle
{mso-style-name:Style1CxSpMiddle;
mso-style-type:export-only;
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Tahoma","sans-serif";}
p.Style1CxSpLast, li.Style1CxSpLast, div.Style1CxSpLast
{mso-style-name:Style1CxSpLast;
mso-style-type:export-only;
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Tahoma","sans-serif";
color:windowtext;
font-weight:normal;
font-style:normal;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoPlainText" align="center" style="text-align:center"><b>Posting Personal Actions to PPDB Timely<o:p></o:p></b></p>
<p class="MsoPlainText" align="center" style="text-align:center"><b><o:p> </o:p></b></p>
<p class="MsoPlainText">As the DAS Centralized PERS Services Team strives to post all employee retirement benefit records timely, we see an opportunity for agency improvement regarding posting Personnel Actions in PPDB. For PERS reporting purposes certain
actions have more critical "timeliness" then others. Actions such as new hires (PA Codes in the 100's), terminations (PA Codes in the 500’s) and PERS Wages Job Class codes (PA Codes 238 and 268) have consequences if not posted prior to payroll's Run 2 for
the month they are effective. The consequences of not posting these actions timely can cost your agency money, as well as impact employee retirement accounts and benefits.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Since 1/1/2004, PERS' electronic reporting system has been capturing state employees’ demographic and payroll data on a monthly basis instead of on an annual basis, as it did in years prior to 2004. This is not a simple or perfect process.
DAS is able to capture and report personnel actions that are required by PERS statute which happen within the current payroll cycle. For example, a new hire (PA Code 141) with an effective date of 6/5/2014, which falls within the 6/1/2014 to 6/30/2014 payroll
cycle needs to be entered by June payroll cutoff Run 2. If it is enter after June payroll run 2, DAS is unable to automatically pick up the code and report it to PERS. After Run 2, it becomes a manual entry into the PERS system for the DAS Centralized PERS
Services Team. The only way the DAS team knows to do so is if the agency contacts us letting us know the code was entered late.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Here are some of the consequences of not entering these personnel actions timely:
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.25in;text-indent:-.25in">• Inaccurate or no reporting of employee demographic data to PERS.
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.25in;text-indent:-.25in">• Inaccurate demographic data can cause the payroll data for the affected month and possibly for months after, not to post to the PERS system. This delay’s crediting employee contributions
to the employee's IAP account. <o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.25in;text-indent:-.25in">• If the salary does not post within the same tax year, the agency can be responsible for prior year earnings the employee's account should have earned on the contributions.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.25in;text-indent:-.25in">• If a new hire is not reported timely for an employee new to PERS, the employee's waiting time could be affected and it could affect when contributions should begin. This can negatively
impact other PERS participating employers. <o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.25in;text-indent:-.25in">• If other state agencies or PERS participating employers do not report timely, it can impact when your agency should begin remitting contributions. Your agency could have to pay employee,
employer and prior year earnings for months or years that were not expected.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.25in;text-indent:-.25in">• If a termination is not posted, PERS may believe the employee is entitled to more retirement service credits then they actually are and the employee's estimate for benefits could be
incorrect.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.25in;text-indent:-.25in">• If a termination is not posted, future employers may receive an inaccurate status check<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.25in;text-indent:-.25in">• If a termination is not posted and the employee request a benefit, it delays the processing of the payment.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.25in;text-indent:-.25in">• If a PERS Wage Job Class Code is not reported timely, it could mean the agency is paying too much or too little in employer "match" dollars if the employee is moving from a general service
to police and fire, or vice versus, position.<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.25in;text-indent:-.25in">• All of these could affect employees’ PERS account accuracy and employees’ ability to have all the information about their plan available timely to make decisions about retirement and
to retire successfully.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Other consequences include manual work for your agency, the DAS Centralized PERS Services Team, and PERS staff to ensure PERS has the correct data.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">The goal is to enter all personnel actions into PPDB by payroll cutoff Run 2 for the month they are effective. Please remember that all new hire or terminations are reported to PERS, as well as PERS Wage Job Class Code and Name/Address
changes. <o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">A "best practice" is to not process any payroll until the appropriate personnel actions are entered into PPDB.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">If you have questions about how entering personal actions into PPDB affect PERS reporting, please contact your DAS Centralized PERS Services Team analyst. They will be glad to provide more detailed information.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
</div>
</body>
</html>