Payroll

How long are paychecks kept in UCPath Online?

Paychecks are available in UCPath Online for a rolling 18 months.

What should I do if I believe there is an error in my pay?

If you believe there is an error in your pay, use your Berkeley Regional Services channel to report the issue right away. The sooner you report an issue, the more quickly it can be resolved.

If you are unsure which service region your unit belongs to, you can Find Your Region here. BAMPFA, Cal Performances, and International House (I-House) employees should contact their local HR team.

BEST, ProS, SHARE, BEARS, ChaMPS Regions

ERSO Region

Call the First Contact Team...

What transactions have to be stopped (not approved)?

Position Management Update transactions for the current or previous pay cycles cannot be entered during this period, when there is an incumbent in the position.

PayPath transactions for the current or previous pay cycles cannot be entered during this period.

Note: the problem is when transactions are initiated and approved because then they will write to the UCPath system and cause issues with the Payroll Processing for that pay period. It is okay to initiate the transaction and ...

What is a “pay-impacting” transaction?

A pay-impacting transaction is any transaction in UCPath that updates Job Data in such a way that impacts the frequency in which an employee is paid, amount owed, or the funding for an employee in the current pay cycle or prior pay cycle (i.e., retroactive transaction) during the Payroll production process. This also includes position management changes for positions which are currently assigned to employees. Any job data change, such as a retro-active lower rate change, that will cause an overpayment.

A pay-impacting transaction includes...

What transactions can be initiated and approved during the Payroll Processing Schedule stop dates (“blackout period”)?

PayPath transactions outside of the current on-cycle pay period; e.g., if the current pay period being processed corresponds to biweekly employees, you may enter monthly transactions.

Non-PayPath transactions, e.g., HR templates and leaves.

Transactions with effective dates beyond the current pay period (including PayPath transactions).

Employee data changes that affect payroll must be submitted and approved in UCPath by 3:00 PM. Changes submitted after 3:00...

Are the blackout dates specific to a pay cycle, i.e., can transactions for MO employees be completed during a hold on transactions for BW employee transactions?

Yes, the hold dates are pay cycle specific. If the current pay period corresponds to biweekly employees, monthly transactions can be entered and vice versa. See page 10 on the Job Aid: Review the Payroll Processing Schedule

Can Smart HR templates continue to be submitted during the “blackout period” listed on the Payroll Processing Schedule?

Yes, HR Templates can continue to be processed during this window, since they require processing at the UCPath Center before writing to the system. However, anything submitted after 3:00 PM of the cutoff date will not be processed for current pay cycle. The UCPath Team team will hold work on these until the “resume” date listed on the Payroll Processing schedule. Refer to the Payroll Processing document section for “What does this mean for...

Can Position Management transactions be entered during the blackout dates if there is no incumbent in the position?

Yes, vacant and new positions are okay to transact as long as there is no incumbent in the position- vacant position changes are not pay impacting Other Position management changes (especially those with incumbents in the position) should be held until the “Resume” date on the Payroll Processing Schedule.

Is it okay to enter future dated PayPath and Position Management transactions during the blackout dates?

Only if the PayPath and Position Management transactions have an effective date beyond the payroll cycle resume date is it okay to submit these future dated transactions.

There seemed to be a discrepancy in the payroll processing schedule in that accrual transactions need to be entered by the Inbound Files date, but are included in the transactions that should not be processed. Can someone please clarify this?

There seemed to be a discrepancy in the payroll processing schedule in that accrual transactions need to be entered by the Inbound Files date, but are included in the transactions that should not be processed (often a day before the deadline for inbound files). Can someone please clarify this?

The Employee Data Change Deadline, the first column in the location section of the Payroll Processing schedule, is actually for deadline purposes, rather than for hold dates. For this reason, you can continue to focus on the outlined Inbound Files date so long as the transaction is being processed as a mass file. See page 3-4 on the Job Aid: Review the Payroll Processing Schedule.

Note:...