The Mass Update of PayPath Actions process enables UCPath Initiators to update employee Position, Job, and Additional Pay Data using a comma separated value (CSV) template.
UCLA Department Initiators may use the Mass Update of PayPath Actions CSV template for high-volume data changes. Templates must be submitted to UCLA Central Resource Unit (CRU) for processing. CRU uploads the file to UCPath and valid transactions post to the system with no approval workflow.
The following table outlines the roles and responsibilities related to using the Mass Update of PayPath Actions template.
Responsible Party | Responsibilities |
|---|---|
UCLA Department |
|
UCLA CRU |
|
Future-dated transactions are allowed, however the effective date must not precede the UCPath conversion date or be before the employee's hire date or after their termination date.
The following requirements must be met:
Must be CSV format only
Must use the current template from the UCPath SharePoint site
Must follow the appropriate naming convention:
BusinessUnit_E081_MASSUPDATEPAYPATH_YYYYMMDD
Example: LACMP_E081_MASSUPDATEPAYPATH_20260701
The following items are key components of the data's processing behavior:
Job Data uses effective sequencing, which is important for retroactive changes. If submitting multiple Job Data updates, each line on the template corresponds to an effective sequence number.
When the file is uploaded, the processing order updates Position Data first, then Job Data, then Additional Pay.
Position Data and Job Data updates are posted immediately after successfully completing data validation.
Additional Pay transactions load to a staging table and complete processing during the following payroll cycle.
Once the file is uploaded, the system performs validation and produces the following:
stdlog→ indicates technical success/failure, list of invalid codes
Output Log → provides record-level results, including successes, errors, and warnings
Files with errors will not upload to the system. Files with warnings will upload, but require review.
Refer to both the UCLA CRU Pay Processing Calendar and the UCPath Center Production Processing Schedule to ensure deadlines are met.
The Mass PayPath template bypasses the approval workflow engine (AWE). Files are not reviewed by CRU for accuracy. Data approval and integrity is the responsibility of the Department.
After the file is processed, if data corrections are required, you must create a case with UCPath Center.
Article: How to Find Mass Templates
Process Map: Mass PayPath Updates
Website: UCLA Processing Calendars