- Business Intelligence Center (BIC)
- BI Query Transition
- Grant Reporting
- OSUF Systems
- Contact IAR
- Institutional Research (IR)
- Login to Core
Default Pay is a custom calculation designed to help departments predict how much salary expense will be charged to each accounting distribution (FOAPAL) for each employee for each pay period remaining in the current fiscal year. It does not attempt to predict OPE expenses.
Employees with jobs that are active or on leave at some point during the current fiscal year, who have a default earn code, plus those in employee class CD, classified full-time hourly, will be included. That’s typically everyone except hourly paid employees and unpaid appointments, including classified part-time hourly, temporary support staff, academic wage hourly appointments, student workers, and courtesy and emeritus appointments (employee classes CE, TS, UW, XA, and XX). Student positions with a job suffix of 55 will display because these jobs are salaried.
Default pay is not the same as an encumbrance. Any changes made to a job or its labor distribution in HR will be reflected in the calculated default pay the next workday, but won't affect encumbrances until they are recalculated near the end of the month.
In addition, encumbrances are calculated somewhat differently from the default pay. Both are calculated using the job detail records, default earn codes, and default labor distributions from the jobs records, but the encumbrance process uses the first day of the next month to start encumbering, while the default pay process uses the actual personnel effective date. Because of this, you may see some differences between default pay amounts and encumbrance amounts for employees whose job begins mid-month. This will really be apparent for those employees who begin work on September 16. Their encumbrances posted in FIS will not include the time period between September 16 and October 1.
Default pay can only be loaded based on what has been entered into Banner. If the information you are looking for is not there, either it was not in Banner as of the time the warehouse loaded, or it could be due to a data entry error. Look in NYIJOBS to see if the changes you requested have been entered. Inputting paperwork for the current month takes priority over future-dated actions. Future-dated actions are input as soon as possible after that, however system limitations restrict data entry to about two weeks per month.
Pay increases are generally entered by payroll at the beginning of the month in which they became effective. They will not show up as default pay until that month.
Sabbatical will display on the employee position, with an "11" suffix, unless the employee has also signed up for the 9-12-month option. In these cases, it will display on the "00" suffix. In both cases, it should display with a 10123 account code.
The pay is charged to departments across the same 9 month period that the appointment covers, so those are the months where default pay will be projected.
Past months (which are only visible in Jaspersoft) should be ignored. The Default Pay Object is not a record of actual gross wages paid in prior months. The default pay looks at the job record (viewable in NYIJOBS) that was in effect for the month in question. Once a month has passed, the pay can be redistributed, but the job record cannot be changed and the default pay cannot be corrected.