Just over a month ago, on July 5th, the core Impact23 systems deployed. Since then, our campus community has diligently reported concerns and the team has been actively addressing inquiries and coordinating solutions. While working to stabilize the new systems with competing priorities, the program team is prioritizing issues impacting payments and/or reimbursements. Through initiatives such as Office Hours, ongoing training, and communication, our aim is to keep the campus informed about known issues, interim solutions, and resolution progress. Your collaboration, patience and support are sincerely appreciated.

The process for establishing Guest Travelers is as follows:

1. Confirm the supplier/payee is "Spend Authorized" in the Oracle Supplier portal. Learn how to request a Supplier. 
2. Concur Delegates then associate the non-employee traveler with the appropriate accountability structure in Guest Traveler Routing - view guide.
3. Confirm with your Dept. SAA that the department has established an "ALL" record for Concur Routing in EACS.

The university occasionally provides reimbursements for moving expenses as part of our commitment to attracting and retaining top talent. These reimbursements are considered taxable benefits, imputed income, impacting eligible employees' net pay. 

While moving and relocation reimbursements information is being actively collected in Concur, the process of reporting the imputed income and processing reimbursement in UCPath is under review. As a result of this review, the reporting of taxable benefits on eligible employees' net pay and issuing reimbursement will be deferred until October. 

For inquiries regarding the Concur moving and relocation process and department approvals, submit a ticket to Travel and Expense. For payroll inquiries, submit a ticket to Payroll Coordination & Analysis. Note that questions regarding the timing of moving and relocation reimbursements, inputted income amounts/rates, etc., cannot be answered during the review process. Additional information will be communicated in October.

• Red! circle icons are errors that require correction
  by the user before a Request or Expense Report
  can be submitted. 
• Yellow! triangle icons are warnings or important information which users should take note of and action if appropriate, but will not prevent a Request
  or Expense Report from being submitted.

Inter-Org Transfer

Corrected

The valid intersections to transfer financial aid funding using the Inter-Org transfer have been corrected. This means that departments can transfer funds to Financial Aid/Grad Division OR Financial Aid/Grad Division can transfer funds from departments (with a negative amount) for student awards. Please continue to follow the processes established by Financial Aid/Grad Division to communicate the awards, but now funding should be easier to move within the system.

If you have experienced auto-rejection while using Oracle Procurement, try the following troubleshooting scenarios:

1. Punchout Catalog Purchases over $10,000: Ensure that purchases made in punchout catalogs greater than $10,000 (excluding restricted catalogs: Sysco, Amerisource Bergen, ePlus, and McKesson) are processed correctly.
2. Missing Approver Setup in EACS: Verify that the appropriate approver has been configured through EACS. If no approver is set up, the requisition will automatically be rejected.
3. Project # for Contract & Grant, Capital Project Purchases: For Contract & Grant, and Capital Project purchases, ensure that the Project # is correctly entered in the Project Number field. Avoid entering any Project # (except 0000000000 DEFAULT) in the Charge Account field to prevent auto-rejection. This ensures proper entry of POETAF values. See How to Correctly Charge a Project.

4. Request Form Orders over $10,000: Requisitions were being modified by Transactors to include their names in the buyer field, and they were generating POs exceeding $10K without involving central procurement. To prevent such orders from being processed, an "auto-reject" rule has been implemented. To avoid auto-rejection, users must refrain from altering the buyer field for orders exceeding $10K.

Important Update: For all PCard requisitions, please use "PCard" as the supplier name, irrespective of whether the actual supplier names are in the system.