Organization suspense accounts (OSA) are non-funded accounts set up for every organization (org) to account for payroll transactions that fail to post.

Payroll transactions that fail to post successfully to valid project-task-awards (PTAs) are instead posted to clearing awards created to capture these failures for their org. Departments are required to clear OSA transactions soon after the payroll is posted in Oracle.

Every time a new org is created, as part of the Organization Code Hierarchy administered by the University Budget Office, the department must supply a PTA, with award type “Clearing,” to be mapped as the designated OSA for payroll transactions.

  • Additionally the department must provide a sweep PTA (typically operating budgets) where charges on the clearing awards will be moved by central administrative staff in Financial Management Services (FMS) if departments fail to move charges to appropriate PTAs in a timely manner.
    Subsequent PTA changes must be emailed to the Systems and Reporting Operations (S&RO) team to ensure orgs are mapped accordingly.
  • All payroll transactions posted to the OSA reflect the 51610 expenditure type and are burdened at the highest rate.
  • An employee's payroll transactions are charged to the OSA associated with the department (org) of the employee work assignment (job) in PeopleSoft.
  • The Labor Distribution system is used to create labor distribution adjustments (LDAs) to clear OSA transactions.
  • All transactions remaining in the OSA are swept quarterly by the Systems and Reporting Operations (S&RO) team to the sweep PTA provided by the department. Refer to Policy: Clearing of Organization Suspense Accounts for details.
  • To learn the OSA PTA or sweep PTA for an org, contact the Systems and Reporting Operations (S&RO) team at
  • A labor schedule does not exist for an employee that should have one. This excludes students in the graduate financial support (GFS) systems and employees submitting timesheets.
  • Labor schedule lines total less than 100 percent. The remaining earnings are charged to the suspense account.
  • The PTA listed on the labor schedule was not valid when payroll was posted.
  • The PTA assigned in Axess Timecard, Payroll or GFS was not valid.

Changes made to the PTA setup after the transaction was entered but prior to approval may cause the PTA to become invalid and the transaction to be rejected. This may include changes to:

  • Close Date. Last date award will accept transactions (regardless of expenditure item date).
  • End Date. The last expenditure item date the system will allow an expense to be entered on the PTA. For example, an award has an end date of December 31, 2019 (31-DEC-19) and a close date of March 31, 2020 (31-MAR-20).
    A distribution adjustment was entered and approved on March 1, 2020 (01-MAR-20) for payroll earnings reflecting the December 15, 2019 (15-DEC-19) (the expenditure item date) pay period. The adjustment will be processed and posted because the adjustment was entered before the close date (31-MAR-20) and the date the expense was incurred (15-DEC-19) was before the end date.
  • Changes on the P, T and/or A status - If the status is on hold or closed, then charges cannot be posted.
  • Installment Not Activated. The central office has not enabled the award to receive expenses.

Identify Transactions

Using the At A Glance page in the Labor Schedules system, Labor Schedulers can easily view employees who require action in the current pay period due to a missing a Labor Schedule or incomplete Labor Schedules under 100%. 

Additionally, department labor schedulers receive proactive email notifications for the current pay period, informing them of labor schedules requiring action for employees within their authority. 

The notification includes the employee labor schedule information and reason for the notification (e.g., missing labor schedule, explanation of why the PTA lines are invalid, etc.). When there are multiple labor schedulers per department, the email notifications will be sent to each individual in the department with the labor scheduler responsibility.

Taking action before the end of the pay period will prevent expenditures from posting to the department OSA.  For a listing of Labor Schedule notifications, refer to Labor Schedule Notifications.

Use the OBI Payroll and Labor Management (PLM) Dashboard to review all transactions that have been posted to the department OSA. 

For information about OBI, refer to OBI Financial Reporting.

Refer to How to: Clear Organization Suspense Accounts for step-by-step instructions. Based on the transaction detail, you can process the labor distribution adjustment to clear the balance accordingly.

When reviewing the earnings in the Oracle labor adjustment module, clear all transactions posted to the suspense expenditure type 51610 (including Salary on Vacation SOV and Vacation Credit VCR entries).

Clear Transactions

The OSA policy includes a sweep process to periodically move suspense transactions to the sweep account provided by the department. Each payroll transaction included in the sweep incurs a $25 fee. This includes SOV and VCR entries that have not been cleared from suspense accounts.

To clear a transaction, determine what PTA(s) the transaction should have posted to. If you have access to the Oracle labor distribution adjustment module, enter a distribution adjustment(s). Refer to How to: Clear Organization Suspense Accounts for more information. If you do not have access to this module, notify the appropriate person to enter the distribution adjustment(s). To find an LD adjuster in your school or department, refer to Oracle Financials Inquiry Tools: Labor Distribution User Query.

Prevent Future Postings

Following are some of the most common actions a user may take to prevent future payroll transaction errors:


Back to Top