<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
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;}
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.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.normaltextrun
{mso-style-name:normaltextrun;}
span.eop
{mso-style-name:eop;}
span.scxw199578860
{mso-style-name:scxw199578860;}
span.ui-provider
{mso-style-name:ui-provider;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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">
<div class="WordSection1">
<p class="MsoNormal">Dear Colleagues, <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Due to the conversion from the old Chart of Account structure (aka FAU) to the new Chart of Accounts, payroll transactions associated with the dates prior to July 1st are being redirected to the Suspense fund 69993. Any leave and biweekly
pay reported with earning dates prior to July 2023 will be assigned suspense funding due to the new Chart of Accounts (COA) effective date of 07/01/2023. Prior to the new COA effective date, funding was based on the FY23 and FAU. Since the FAU accounting became
inactive on 07/01/2023, previous FAU funding cannot be used for July payroll processing. Therefore, the UCPath process will assign suspense funding for leave taken prior to July 1st, 2023. <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Additionally, inactive FAU funding sources will impact any payroll adjustments to previous pay periods or previous earnings before 07/01/2023. A reduction in the assignment of payroll to suspense accounts will
naturally occur with future pay periods. However, it is important for units to validate position funding iReports and update UCPath with valid Chart of Accounts (COAs) using the Position Funding application.<br>
<br>
<b><span style="color:#0070C0">Upcoming Action</span></b><span style="color:#0070C0"> </span><o:p></o:p></p>
<p class="MsoNormal">To assist units with corrections, a file will soon be shared with CFAOs, indicating the proposed COA for processing transfers of July payroll expenses out of the suspense account; the information in the file will be based on current position
funding. CFAOs should coordinate the review of the file with their unit’s Financial Managers. Additional instructions will be provided once the file is distributed. <b><u>Note</u>:</b> Once the new SCT is available to campus users, it is not possible to process
SCTs on these impacted lines due to the same limitation described above. <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Thank you for your patience and cooperation as we work through these changes. If you have any questions, please
<a href="https://ucrsupport.service-now.com/finadmin_portal" target="_blank">submit a ticket</a> and select
<b>Payroll Coordination & Analysis </b>as the Service/Business Process. <br>
<br>
Sincerely, <o:p></o:p></p>
<p class="MsoNormal"><b><i>Asirra Suguitan </i></b><br>
Controller and Impact23 Functional Lead <b><i><o:p></o:p></i></b></p>
<p class="MsoNormal" style="margin-bottom:3.0pt"><span style="font-family:"Arial",sans-serif"><br>
<img border="0" width="250" height="77" style="width:2.6041in;height:.802in" id="_x0000_i1025" src="cid:image001.png@01D9E232.C175B820" alt="ucr-logo-email"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>