, but this code // executes before the first paint, when

ÃÛÌÒapp

is not yet present. The // classes are added to so styling immediately reflects the current // toolbar state. The classes are removed after the toolbar completes // initialization. const classesToAdd = ['toolbar-loading', 'toolbar-anti-flicker']; if (toolbarState) { const { orientation, hasActiveTab, isFixed, activeTray, activeTabId, isOriented, userButtonMinWidth } = toolbarState; classesToAdd.push( orientation ? `toolbar-` + orientation + `` : 'toolbar-horizontal', ); if (hasActiveTab !== false) { classesToAdd.push('toolbar-tray-open'); } if (isFixed) { classesToAdd.push('toolbar-fixed'); } if (isOriented) { classesToAdd.push('toolbar-oriented'); } if (activeTray) { // These styles are added so the active tab/tray styles are present // immediately instead of "flickering" on as the toolbar initializes. In // instances where a tray is lazy loaded, these styles facilitate the // lazy loaded tray appearing gracefully and without reflow. const styleContent = ` .toolbar-loading #` + activeTabId + ` { background-image: linear-gradient(rgba(255, 255, 255, 0.25) 20%, transparent 200%); } .toolbar-loading #` + activeTabId + `-tray { display: block; box-shadow: -1px 0 5px 2px rgb(0 0 0 / 33%); border-right: 1px solid #aaa; background-color: #f5f5f5; z-index: 0; } .toolbar-loading.toolbar-vertical.toolbar-tray-open #` + activeTabId + `-tray { width: 15rem; height: 100vh; } .toolbar-loading.toolbar-horizontal :not(#` + activeTray + `) > .toolbar-lining {opacity: 0}`; const style = document.createElement('style'); style.textContent = styleContent; style.setAttribute('data-toolbar-anti-flicker-loading', true); document.querySelector('head').appendChild(style); if (userButtonMinWidth) { const userButtonStyle = document.createElement('style'); userButtonStyle.textContent = `#toolbar-item-user {min-width: ` + userButtonMinWidth +`px;}` document.querySelector('head').appendChild(userButtonStyle); } } } document.querySelector('html').classList.add(...classesToAdd); })(); Time Entry Financial Services | ÃÛÌÒapp

ÃÛÌÒapp

Skip to main content

Time Entry

Time entry for hourly employees

All hourly employees and their supervisors submit records of time worked, using . 

All time submissions must be complete and accurate:

  • Time should be entered on a regular basis – accruing with each shift worked.
  • Time recorded as worked must equal actual time worked.
  • Time entries must be submitted by the employee and approved by their supervisor.
  • Time worked (not including paid time off) over 40 hours in one week is paid as overtime.
    • Overtime must be approved in advance.
  • Time off (PTO, holiday, jury duty, etc.) must be requested and approved via Time Off in Workday
  • Premium pay (overtime, holiday time worked and on-call time) must be clearly recorded.
  • Chapel break and Healthy Habits lunch extensions may be recorded as time worked.

Employees must complete and electronically sign off on their time entries by 12:00 p.m. (noon) on the Monday following the end of each pay period.

Supervisors must review their employees’ time submissions carefully, correcting or adding time as-needed, and must electronically approve their employees’ time sheets by 12:00 a.m. (midnight) on the Monday following the current pay period. Payroll will not be processed for an employee until their supervisor approves their time entry. All time must be submitted and approved in Workday. If neither the employee nor their supervisor is able to enter time-worked for a given time period, the hours can still be corrected, submitted, and approved in Workday retroactively. Hours entered for a previous time period will be paid on the next available pay period after approval.

For more information about time entry and approval in Workday, including instructions and video tutorial, please see the .