Copyright © 2009, Escape Technology, Inc. All Rights Reserved.

Labor Distribution Errors

This FYI discusses the procedures for correcting labor distribution errors generated from running the labor distribution process in the Escape Payroll Module.

NOTE: Please contact Escape Customer Care for help in correcting a labor distribution error message.

Labor Distribution Errors

Below are commonly known errors that are generated during the labor distribution process.

AcctBalLink: Deleted account was asked for. Could not read account # for employee (???). Could not read cash account.

• This error indicates that an account number used in the pay day has been deleted.
• On the EPDUPD screen, two things could be done:
  1. Control+End at the account number clears the account link number that references the deleted account. Once the account is cleared, the position account number is used.
  2. A valid account number could be entered.

Blank Account # Was Encountered for ???.

• An add-on (s) does not have any account number entered on the employee's EPDUPD account screen.
• Mark the employee and unlock them on the pay cycle. Enter the appropriate account (s) on the EPDUPD account page.

CASH Entries Do Not Match NET PAY for Employee

• Account(s) may have been ended. Verify that there are valid position accounts for the pay period.
• Retirement code may be missing on the EPDUPD screen. If retirement code is missing, enter a plan code on the EPDUPD retirement page.

Could not locate earnings account to distribute Employer costs of $$$ for employee (employee's name) ER GTN CODE: (GTN code).

• Acounts may not exist or may have been ended in Chart. Verify that the account (s) exist in Chart.
• If the employee has a tracking record, verify that the BNFT flag is set to a Y in the tracking record.
• If the employee has only an add-on record, verify that the BNFT flag is set to a Y in the employee's add-on record.

Could Not Read Account # for Employee

• The account number in question is not setup in the Chart module.

Net Pay Does Not Equal Cash

• Check if the dollar amount is the difference between the cash entry and the net pay.
• If this dollar amount is the amount of the PERS reduction, then check the PERS file (from the main pay menu). The entry may show on this list, even if the key file is broken. The key file may need to be checked; therefore, you should report this error message to Escape Customer Care for further research.

Pay Cycle has not been final computed. Do not post this journal.

• The pay cycle for the specific pay date has NOT been final computed (locked in). Final compute the pay cycle in question before proceeding.

Pay Detail Overflow

• It means that there is not enough room in the pay detail file between records to mark and compute employees. The entire pay cycle list must be recomputed to re-space the records.

Pos #xxxx not assigned to this employee". Add-on REGULAR is not assigned to this employee.

• The software cannot assign an add-on to a position that is not active on the last day of the pay period; therefore, it will report this error message. The employee referenced in the error message usually has a position that has been ended mid-month.
• Here are the steps to fix the error:
  1. Check the employee's tracking record history to see when the position was active. The error message most likely occurred because the tracking record had been ended mid-month.
  2. Wipe out the position # referenced on the employee's EPDUPD earnings screen. The software is complaining because it can not assign the add-on to the position for the entire period (i.e. tracking record ends 8/16, but EPDUPD screen for retro payroll shows 8/31 effective date).
  3. Run a labor snapshot to verify that labor is being charged correctly. It should charge to whatever account that is active for the period. The EPDUPD account screen can be used to manually change where it is being charged.

PSL # Does Not Have any Account #s Defined

• Account number (s) needs to be entered on the position account screen in the Personnel Module.

Warning all Deductions Will Be Coded to Fund ???.

• If the pay cycle is setup to charge out health and welfare benefits, this error message may be acceptable. It should be considered as a warning since there are no earnings on the payroll.
• The error message should be researched if there are earinings on the payroll.

Warning All Earnings Will Be Coded to Account # ???.

• This error message should be researched. This message means that all earnings will be coded to the general fund account.