Concur Is Currently Unavailable

Friday, May 30th | The CMiC team has officially gotten POs working in the system! The Accounting team also worked hard yesterday to push through roughly 1,000 invoices into users’ queues! However, any PO invoices entered yesterday were not able to be tied to a PO due to the issues we were previously experiencing. There are roughly another 3,000 invoices remaining to be entered and assigned to users. With the PO issue fixed, these 3,000 should now be able to be entered into the system properly. WHAT THIS MEANS FOR USERS:  There will be some PO invoices in your queue in CMiC (the ones entered yesterday) that will need to be coded & approved following the temporary process put in place on Wednesday – code the invoice and enter the PO number as a comment on the invoice. This process will ensure the Accounting team can properly tie that invoice to the PO on the back-end. If your PO invoice comes over without any automatic coding, this is the process you will follow. For any PO invoices entered beginning today, the invoice should already be automatically coded according to the PO. For these invoices, you’ll just check for accuracy and then approve. For additional training resources regarding how to code & approve invoices, visit the Keeley’n Hub. If you have any questions or need direct support on AP coding & approval, please contact the Project Controls team via your CMiC Teams Chats, or the Project Accountants for your Business Unit. Wednesday May 28th | , CMiC is still not working as intended as it relates to quantities on PO invoices. This has resulted in a delay in getting PO invoices uploaded into CMiC and into users’ queues – which impacts both AP and T&M billings. In order to get vendors & partners paid in a timely manner (according to our terms & contracts), as well as get T&M bills out as soon as possible, we are going to move forward with uploading PO invoices into CMiC without tying them directly to a PO – essentially turning them into Misc invoices. WHAT THIS MEANS FOR USERS: There will be a slight temporary change to our process. Effective immediately, all PO invoices should be treated as Misc invoices. We are working diligently to get CMiC working properly and begin the normal process ASAP, but in the interim users should follow the same coding & approval process for PO invoices as you do for Misc invoices – with the additional step of adding the PO number as a comment on the invoice. As of Wednesday evening May 28th, users will start seeing more invoices hit your queues to code and approve. Over the next week, please make sure you are coding & approving invoices as quickly as possible while we get caught up on AP & AR in CMiC. You can follow the below steps to complete this. Your first step is to code the invoice appropriately – this will be the case whether your invoice is for a PO or not. If your invoice IS for a PO – you should enter the associated PO number as a comment on the invoice. Once coded and the PO number entered in the comments, you can approve your invoice. If you have any questions or need direct support on AP coding & approval, please contact the Project Controls team via your CMiC Teams Chats, or the Project Accountants for your Business Unit. We appreciate your patience and flexibility as we ensure we are continuing to take care of our people and our partners throughout this massive change.

(UPDATED ON 5/23 AT 12pm) We value the helpful feedback many Keeley’ns have provided so far regarding CMiC – including about the new pay stub format. Our Payroll team has worked hard to make adjustments to the initial format to provide Keeley’ns with the information they are looking for on their pay stubs. Currently live, Keeley’ns will see a new pay stub format when viewing pay stubs in UKG. Please see below for a sample of this new format. The following changes were made to address team members’ feedback: Added more detail regarding the deductions and fringe benefits. Added more detail regarding the earnings & benefits. Cleaned up the format as much as possible to make it slightly easier to understand. The following change is still being worked on to roll out soon: Adding the pay rate for any team members earning overscale wages. (The amount and YTD total are included, but do not currently show the hourly overscale rate.)