Child pages
  • UPDCAL_FUT-Future Payroll Data Maintenance1
Skip to end of metadata
Go to start of metadata

overview

UPDCAL_FUT allows a user to enter payroll exceptions before starting a payroll. In fact, exceptions can be entered days, even months ahead of time.

UPDCAL_FUT works in the same manner as UPDCAL_CUR. The only difference is that an effective date field appears in UPDCAL_FUT. This field allows the user to direct an UPDCAL_FUT record into a specific payroll. The effective date must be inclusive of payroll period begin and end dates in which the payment needs to be made.

Future pay records included in the current payroll will be marked with an "I" in USPSCN/UPDCAL_FUT. The "I" stands for, "Transaction included with payroll in progress." Once the payroll is completed the "I" will be changed to a "P" and the record will be deleted from the USPSCN/UPDCAL_FUT screen the next time the INICAL program is run. The "P" stands for, "Transaction has been posted."

It is important to not enter regular pay amounts that will be processed with the normal payroll run in the UPDCAL_FUT option as these regular amounts will then be doubled when the payroll is run and counted toward the contract amount paid.

accessing the program

The program may be executed by typing:

  $ RUN OECN$PAY:USPSCN

at the $ prompt or in the menu system type:

  Menu>USPSCN

Then select the UPDCAL_FUT module.

updcal_fut option

 

 --------------------------------------------------------------------------------------
| Find:                                                                                 |
|       SSN/ID    Job             Last Name           First Name                        |
| ID:  111111111   Job: 01  Name: JOHN            DOE                                   |
|                                                                                       |
|                   Daily Rate:45.00       Position: SUBSTITUTE TEACHER                 |
| Work days:  __                                     Tax         Retire Reg/  Effective |
| Type   Units     Rate     Amount   Description     Opt Retire  Hours  Spec    Date    |
|P MIS       1       20      20.00      02-11-96      1     Y    _____   R   __/__/____ |
|  MIS       1       45      45.00      02-13-96      1     Y    _____   S   02/22/1996 |
|  ___   _____     ____     ______   ___________      _     _    _____   _   __/__/____ |
|  ___   _____     ____     ______   ___________      _     _    _____   _   __/__/____ |
|  ___   _____     ____     ______   ___________      _     _    _____   _   __/__/____ |
|  ___   _____     ____     ______   ___________      _     _    _____   _   __/__/____ |
|  ___   _____     ____     ______   ___________      _     _    _____   _   __/__/____ |
|  ___   _____     ____     ______   ___________      _     _    _____   _   __/__/____ |
|                                                                                       |
|         Gross wages:       45.00    Pay per period: ______                            |
|  P = Transaction has been posted.                                                     |
|                                                                                       |
|  UPDCAL - Update FUTURE payroll data                                                  |
|   XX  Top            XX  Add            XX  Switch                                    |
|   XX  Help           XX  Delete                                                       |
|   XX  Exit           XX  Modify                                                       |
|   XX  Next                              XX  Work/Srv Days                             |
|   XX  Find           XX  Pay Report     XX  Set Defaults                              |
 ---------------------------------------------------------------------------------------


Field Definitions

  • Work days are the number of work days this pay period. This is a non-modifiable field. The number of work days is calculated by taking the period beginning and ending dates entered in INICAL and finding how many W's, C's, and H's are entered on the employee's job calendar for that period.
  • There are many different pay *Type*s which can be used in UPDCAL_FUT. When entering the pay type only the first letter of the pay type is required.

Pay Types Available in UPDCAL_FUT

 
Pay Type Description

REG*

Regular wages for contracted employees. These count toward the fulfillment of the contract. When adding regular wages to an employee leaving the rate blank will cause the system to default to the employee's regular rate. Regular pay types are charged according to how they are set-up in USPSCN/PAYSCN.

OT

Overtime wages. These do not update the contract amount paid. If the rate field is left blank the system will enter a rate of 1 1/2. Overtime wages are charged to an overtime account based on the employee's regular pay account.

BCK*

Retro pay. Retro pay updates the contract amount paid.

MIS

Miscellaneous pay. Does not update the contract amount paid. Miscellaneous pays can be taxed at different rates and charged to different accounts.

SHP

Shift premium. Shift premiums can be defined in USPSDAT/USPCON as a percent or fixed amount.

IRR*

Irregular pay. Irregular pays update the contract amount paid, but do not update pays paid and days worked. This can be used to pay retro amount on a separate check.

DCK*

Dock pay. Dock amounts are subtracted from gross wages. DCK entries are assumed to be negative

TRM

Termination pay. Pays an employee a specific amount as termination pay, for example severence pay. You must supply the tax and retirement options. The Job Status field will be changed to a 9 once CHKUPD is run.

POF*

Pay off of total accrued wages. This pay type updates the contract amount paid. This amount is calculated by the system.

NC1

Life Insurance Premium. This pay type is used in the processing of the taxable amount of life insurance premiums on W2's for coverage in excess of $50,000. More on that process can be found in the "Useful Procedures Section" of the
USPS User Guide. Any NC1 amounts are taxed by Medicare and Social Security, as applicable. No Federal, state, or OSDI tax is deducted from this amount. The software provides the ability to withhold city tax on non-cash earnings. This can be activated by setting the "Tax non-cash earnings" flag to Y (yes) on the city tax record in the USPSDAT/DEDNAM program.

NC2

Adoption Assistance.

NC3

Non-cash taxable benefit. This pay type will represent the non-cash taxable benefit amount.

Note Pay types marked with an asterisk (star) affect the contact amount paid
  • The Units field contains the number of units that the employee should be paid by. This could be the number of hours/days the employee worked.
  • The Rate for the job is the amount an employee earns per unit they work. This amount could be for a day, hour, etc.
  • The Amount field is calculated by the program. The amount is equal to the units multiplied by the rate. This field is unmodifiable.
  • Enter a brief Description indicating the purpose of the pay. By default, the description for a regular pay type is taken from the check stub description field found on the job record.
  • Miscellaneous (MIS) and Termination (TRM) Pay Types require a Tax Opt. for the payment. If using a supplemental pay taxing option for an employee, all MIS or TRM pays must be taxed using the same supplemental option.

The CALCPAY program will issue a fatal error if it encounters an employee with multiple jobs with
different supplemental taxing options. The options must be modified for
the employee so they correspond to each other.

All supplemental payments are taxed at 22.00% for Federal and 3.5% for Ohio.

The options are:

  1. - Supplemental payment with annuities applied to regular wages.
  2. - Payment taxed as part of regular wages.
  3. - Supplemental payment with annuities applied to supplemental wages.

If Option 1 is selected and the regular wages are less than the total annuities, the remaining annuity amount will be subtracted from the gross amount being taxed at the supplemental rate.

Option 2 may be used along with either supplemental taxing option.

If Option 3 is selected and the supplemental wages are less than the total annuities, the remaining annuity amount will be subtracted from the gross amount being taxed at the regular rate.

For more information, see Supplemental Payments and Taxing Options in the Miscellaneous Notes
section of UPDCAL_CUR chapter. A "Set defaults" function key is available with the tax option. See the Miscellaneous Notes section of this chapter.

When entering a Miscellaneous or a Termination Pay Type, a Retirement option must be chosen. The options are:

  • Y - to have retirement deducted.
  • N - to not have retirement deducted.

A "Set defaults" function key is available with the retirement option. See the Miscellaneous Notes section of this chapter.

  • The Retire hours field allows the user to enter retirement hours for all pay types, except ACC, LPA, and LPE. If no retirement hours are entered for the pay type, then zero is assumed.One exception is that only the "REG" and "OT" (Overtime) pay types will automatically calculate the retirement hours based on the retire hours field on JOBSCN if greater than 0. If retire hours = 0, then hours in hours per day field are used. If hours per day = 0, then 0 is moved to retire hours. If the calculated retirement hours are not correct, the user has the ability to override the calculated hours.
  • The Reg/Spec field is unmodifiable. The program will determine whether a miscellaneous pay is regular or specific based on whether a specific account was charged by the user. This field will be filled in with an "R", unless a miscellaneous pay is chargd to an account through the Misc. Info screen in UPDCAL_*.
  • The Effective Date is the date when the record should be paid. When this date is included within the run of the current payroll beginning and ending dates, the record will be included in the payroll. If no date is entered in the Effective Date field, the record will be included in the next payroll run.

misc. info option

Screen 1 of 1

When entering a miscellaneous pay, an additional screen is available to charge the miscellaneous pay amounts to specific pay accounts. While on the miscellaneous pay line, press the [Misc.Info] key to display the additional screen. Each miscellaneous pay has its own specific account screen. If your district uses the XREF codes, simply enter the code (case sensitive) in this field and the account it represents will be entered for you. The BRDDIS and LEVPRO charging flags will default based on the first active matching PAYSCN record. If your district does not use XREF codes, this field will not be available.

 -------------------------------------------------------------------------------
|ID:  ________   Job: __  Name: ____________________________                    |
|                       Pos: ________________________________                   |
| Total:    50.00      Brd Lev                                                  |
|     Amount   XREF    Dis Pro  Fnd Func Obj SCC  Subj   OPU IL Job             |
|      50.00  ______    Y   Y   200 4134 143 9440 000000 002 00 000             |
|  __________ ______    _   _   ___ ____ ___ ____ ______ ___ __ ___             |
|  __________ ______    _   _   ___ ____ ___ ____ ______ ___ __ ___             |
|  __________ ______    _   _   ___ ____ ___ ____ ______ ___ __ ___             |
|  __________ ______    _   _   ___ ____ ___ ____ ______ ___ __ ___             |
|  __________ ______    _   _   ___ ____ ___ ____ ______ ___ __ ___             |
|  __________ ______    _   _   ___ ____ ___ ____ ______ ___ __ ___             |
|  __________ ______    _   _   ___ ____ ___ ____ ______ ___ __ ___             |
|  __________ ______    _   _   ___ ____ ___ ____ ______ ___ __ ___             |
|  __________ ______    _   _   ___ ____ ___ ____ ______ ___ __ ___             |
|  __________ ______    _   _   ___ ____ ___ ____ ______ ___ __ ___             |
|  __________ ______    _   _   ___ ____ ___ ____ ______ ___ __ ___             |
|                                                                               |
| UPDCAL - Update FUTURE payroll data                                           |
|  XX  Return                                                                   |
|  XX  Help           XX  Scroll down                                           |
|  XX  Cancel                                                                   |
|  XX  Pay Accounts                                                             |
 -------------------------------------------------------------------------------


Field Definitions

  • Amount is the amount that is to be charged to this account. The amounts charged to various accounts must balance with the total amount of the miscellaneous pay.
  • The XREF code refers to a cross reference option available in the USAS software which allows a short cut to be established for the full USAS account dimension. If your district uses the XREF codes, simply enter the code (case sensitive) in this field and the account it represents will be entered for you. The BRDDIS and LEVPRO charging flags will default based on the first active matching PAYSCN record. If your district does not use XREF codes, this field will not be available.
  • Is this a Brd Dis(Board Distributed Account)?
    • Y - Yes, this is a board distributed account.
    • N - No, this is not a board distributed account.
  • Should this account be used for Leave Proj? This flag determines whether or not an account can be used by LEVPRO to charge out leave entered in USPSCN/ATDSCN and the job calendars to the corresponding leave accounts.
    • Y - Yes, this account should be used for leave projection?
    • N - No, this account should not be used for leave projection?
  • The Fnd, Func, Obj, SCC, Subj, OPU, IL and Job fields contain the USAS account code that the amount is to be charged.

The miscellaneous pay amount can be charged to various accounts. The accounts can be either manually entered or you can press the [Pay Accounts] key while the cursor is on the account line to see a pop-up window of accounts already used for this employee and job. Highlighting the desired account and pressing the [Return] key will place the account code on the line.

Field Definitions

  • Amount is the amount that is to be charged to this account. The amounts charged to various accounts must balance with the total amount of the miscellaneous pay.
  • The Fnd, Func, Obj, SCC, Subj, OPU, IL and Job fields contain the USAS account code that the amount is to be charged.

The miscellaneous pay amount can be charged to various accounts. The accounts can be entered in 2 ways. The first it to manually enter the account code. The second is to press the [Pay Accounts] key while the cursor is on the account line to see a pop-up window of accounts already used for this employee and job. Highlighting the desired account and pressing the [Return] key will place the account code on the line.

  • Is this a Brd Dis(Board Distributed Account)?
    • Y - Yes, this is a board distributed account.
    • N - No, this is not a board distributed account.
  • Should this account be used for Leave Proj? This flag determines whether or not an account can be used by LEVPRO to charge out leave entered in USPSCN/ATDSCN and the job calendars to the corresponding leave accounts.
    • Y - Yes, this account should be used for leave projection?
    • N - No, this account should not be used for leave projection?

miscellaneous notes

Creation of New PAYSCN's

Once the payroll has been completed a pay screen will be created for any new accounts that have been used for specific miscellaneous pays. On this pay screen the account status will be set to "S" for specific miscellaneous.

Adding Jobs to UPDCAL_FUT

When adding jobs through UPDCAL_FUT using the [Add] key, a pop-up window is displayed listing the job, position, rate, and pay accounts. Please note that some of the position description may be truncated in order to allow the rest of the information to display properly on the screen.

Highlighting and selecting the applicable information will automatically bring it into the UPDCAL_FUT screen to be included using the [Add] key.

Set Defaults Function

The Set Defaults function key allows defaults to be set for the taxing and retirement options which are required for MIS and TRM Pay Types.

When MIS or TRM pay types are being entered in add or modify mode, pressing the Set Defaults function key displays a pop-up box on the screen that allows you to select either the taxing or retirement option. Once either of these is selected, the options for each one are displayed on your screen so a default value can be selected. Refer to the available options listed in the field definitions above. The default is then retained as long as you are in the UPDCAL_FUT module. You may override the default values prior to pressing the Accept key if you wish.

This function works differently from other set default options in the USPS software. If the defaults are selected and set, the default values will not appear on the screen until the [Accept] key is pressed. Then the default values will appear. Other set default options automatically place the default values in the appropriate fields as soon as the screen is called up.

UPDCAL_FUT Errors and Warnings
The following list describes messages that may appear after UPDCAL_FUT runs.

  • Job is already being used in another payroll.
    Only applies to districts using multiple simultaneous payrolls. The job has already been included in a current payroll for a different payroll code. The same job can not be in multiple payrolls at the same time.
  • Job is processed for 'Refund of Deduction'.
    The job can not be added to the current payroll because it was added as a refund of deduction thru REFSCN. The employee may be deleted from REFSCN which will allow it to be added to UPDCAL_FUT.
  • Employee is concealed.
    Indicates the job is assigned to a concealed employee and will not be included in the payroll. In order to add jobs for concealed employees, the conceal flag in BIOSCN must first be cleared.
  • Employee is Non Direct Deposit and this payroll is only Direct Deposit.
    When INICAL was processed, the option to process only direct deposits was used. The employee selected to add is not flagged as a direct deposit employee in BIOSCN.
  • Employee is Direct Deposit and this payroll is only Non Direct Deposit.
    When INICAL was processed, the option to process only non direct deposit employees was selected. The employee selected is flagged as being a direct deposit employee in BIOSCN and can not be added to the current payroll.
  • Job has been terminated, can not be added.
    The job selected has been set to terminated (job status field) in JOBSCN. Terminated jobs can not be added to UPDCAL_FUT.
  • Employee is deceased, job can not be added.
    The job selected has been set to deceased (job status field) in JOBSCN. Deceased jobs can not be added to UPDCAL_FUT.
  • Job does not have selected pay plan, can not be added.
    The pay plan defined in JOBSCN for the job selected does not coincide with the pay plan selected to pay when INICAL was processed.
  • Pays paid = number of pays, job can not be added.
    The numbers of pays paid equals the number of pays to be paid as defined in JOBSCN. The job appears to be fulfilled and can not be added.
  • Days worked = work days in contract, job can not be added.
    For a non-stretch paid job (equal pays = N), if the work days in contract is greater than zero, the days worked in contract has to be less that the work days in contract. If the days worked equal the works days in contract, the contract is assumed to be fulfilled and the job can not be added to the payroll.
  • Days worked exceeds work days in contract, job can not be added.
  • Deferred posts + current will cause leave to go negative.
  • Job is already being used in another payroll.
    Applies to districts using multiple simultaneous payrolls. The job has already bee included in another payroll that is currently in process.
  • Contract start/stop dates do not fall within period begin/end dates.
    The job has a contract start and/or stop date defined in JOBSCN that is causing the job to be considered inactive. The contract start date is after the period ending date or the contract stop date is before the period begin date.
  • Pay accounts for the job do not equal 100%, job can not be added.
  • No pay accounts on file for job.
    Pay account(s) information has not been added to USPSCN/PAYSCN for the job. Add the pay account information for proper charging of the employees gross.
  • Units must be specified in order to calculate an amount.
    A unit of at least 1 needs to be entered in UPDCAL in order to allow the pay amount to be calculated. Units times rate equal amount paid.
  • Units times Rate does not equal amount charged to specific pay accounts.
    The pay amount is being charged to specific pay accounts. The amounts entered for the specific pay account charging does not equal the total amount to be charged for the pay line. The amounts to be charged to the pay accounts should be adjusted to total the amount to be paid.
  • This job is in STRS Advance.
    If attempting to pay a BCK (retro) payment on a job that is flagged as being in STRS advance, this warning will be issued.
    If the BCK pay type was originated by NEWCNT or was in JOBSCN before running the actual option of STRSAD, the warning can be ignored. The software would have taken the retro amount into consideration when the advance calculations were done.
    If the BCK pay type is being added in UPDCAL after running the actual option of STRSAD, doing so may cause the advance calculations to be out of balance when all jobs are out of the advance mode. In this instance, if the district wishes the BCK amount to be applied to the current contract, the warning can be ignored and corrections will need to be filed with STRS for this employee or employees as needed. If the BCK amount should not be applied to the current contract, the BCK type should be removed from UPDCAL.
  • Calendar xx/xxxx type xxx not found for xxxxxxxxx.
  • Calendar type xxx has no calendars on file for date range.
  • No calendar type was found for employee xxxxxxxxx, Job xx.
  • Gross pay would exceed contract obligation.
  • Contract amount paid exceeds contract amount.
  • Total carry over dock is greater than remaining contract obligation.
  • All pays must tax using 1 or 3, can not use both for employee.
    An employee may be taxed using Supplemental tacing option 1 or 3. Both taxing options may not be used at the same time for the employee.
  • No UPDCAL posting occured; No payroll selected.
    Applies to multiple simultaneous payrolls only. If using the USPSCN/ATDSCN posting feature to post into UPDCAL, the payroll code to process to must be selected in order to allow for proper posting.
  • Negative units unacceptable, use a negative rate instead.
    If attempting to reverse out a previous payment that was made erroneously, use a negative rate. The units field must be a positive value.
  • Pay type affects contract amount paid for advanced job, can not be used.
    An IRR pay type can not be used for a job in STRS advance. This pay type affects the contract amount paid and would cause a balancing problem with the STRS advance payback.
  • Job is advanced. New earnings (REG) may not be added to the job.
    The REG pay type affects the contract amount paid. Using this pay type with a job in STRS advance would cause the STRS advance balancing to be off. The job may be paid a MIS pay during STRS advance as this pay type does not affect the contract amounts.
  • Warning: DCK pay for an STRS advanced job will affect the payback.
    Docked wages affect the contract amount paid. Using this pay type will cause the STRS advance balancing to be off.
  • Warning: Job is in STRS advance. POF may cause pay back to be off by pennies.
    If the contract is being paid off early using the POF pay type, it may cause the STRS advance balancing to be off by pennies due to rounding issues. The STRS advance amount is calculated on a per pay basis. By paying off the contract early, it may cause some rounding differences in the calculation.
  • Warning: Misc. pay accounts are GENERALLY 1xx object codes.
    When specifying specific miscellaneous pay accounts, the object code normally begins with a 1 unless the fund begins with a 2, but other object codes will be accepted.
  • Warning; Budget account does not currently exist on account master file. Account will be added during AUTOPOST.
    The pay account entered does not currently exist in USAS at the budgetary level. The budget account will be added when AUTOPOST is run to post the payroll batch file.
  • No labels