<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:x="urn:schemas-microsoft-com:office:excel" 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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@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"><span style="font-family:"Tahoma",sans-serif">Dear Colleagues,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif">In recent years, changes in University of California policy and California law have impacted our processes at UC Riverside. Because these changes will alter ways of working for most faculty
and staff in addition to those directly responsible for financial transactions, I want to call your attention to the work of Impact23 and
<a href="https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202320240SB27">
SB 27</a>, a California Senate Bill that was passed into law last year and took effect in 2024.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif">But first, it’s important to highlight the philosophy and organizations that affect our ways of working.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif">Over the last two years, the Impact23 initiative at UCR aimed to replace outdated software and systems for travel, project and grant management, and accounting. Prior to this initiative, the
last major finance software update was in 1999 in preparation for Y2K, long before many technologies we use today had been developed. Additionally, the UC Office of the President has required all campuses to switch to a common accounting system. You may have
heard of the term Chart of Accounts, or COA, which is the type of accounting system we now use. This allows UCOP to standardize reporting practices across the system<span style="color:black">, given that they are responsible for the UC-wide financial audit</span>.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif">Implementing change is a challenge, even when upgrading to systems with greater capability. If you are not yet familiar with Impact23, I encourage you to visit the
<a href="https://impact23.ucr.edu/">website</a> where you can access the objectives, known issues, training, and other support.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif">Within a public entity, procurement’s highest priority is to assure open and fair opportunities<span style="color:black"> for private vendors</span>. We must also abide by strict
<span style="color:black">policy and </span>safety standards. We have both state and UC system requirements that may govern vendor choice; and, when UCR receives federal contracts or grants, we must also comply with requirements set forth by the awarding agency,
such as the National Science Foundation (NSF), the Department of Agriculture (USDA), and National Institutes of Health (NIH), among others.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif">A new law, SB 27, which establishes many requirements on UC vendors as it relates to compensation for the vendors’ employees, will also impact our processes.
<span style="color:black">This new law helps to support fair wage/fair work standards, but does come with some significant overhead for our vendors. Specifically, the law requires vendors to meet salary and benefit parity with UC for their staff, provide vendor
employees with written notices regarding contracted com</span>pensation rates, and pay employees according to the rate listed within the contract or face fines and penalties. Moreover, it requires documentation from the vendors confirming their compliance
with these requirements.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif"><span style="color:red"><o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif">As we continue to implement Impact23 and understand California SB 27, we will distribute more information about how they impact you. While operational changes may cause some frustration as we
work through new processes or update software programming to fit our needs, we will work to keep you informed. In the long run, these changes allow us to align with regulation and policy to carry out our responsibilities and meet our objectives.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif">Please anticipate updates and more information on these topics from Planning, Budget, and Administration.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif">Sincerely, <o:p>
</o:p></span></p>
<p class="MsoNormal"><span style="font-size:4.0pt;font-family:"Tahoma",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif"><img border="0" width="82" height="62" style="width:.8541in;height:.6458in" id="Picture_x0020_1" src="cid:image001.png@01DA64C6.5A6EBD40" alt="cid:image001.png@01D95271.314E2FD0"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:4.0pt;font-family:"Tahoma",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif">Kim A. Wilcox<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif">Chancellor <o:p>
</o:p></span></p>
<p class="MsoNormal"><span style="font-size:2.0pt;font-family:"Tahoma",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif"><img border="0" width="145" height="43" style="width:1.5104in;height:.4479in" id="Picture_x0020_2" src="cid:image002.png@01DA64C6.5A6EBD40" alt="cid:image003.png@01D89DAF.8FA25DD0"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif"><o:p> </o:p></span></p>
</div>
</body>
</html>