1. Save these files as your example templates.  Save them as MS Excel workbook (with the extension of .XLSX) and name them based on the type of transactions they are used for:
   • EXAMPLE 1 File Name:  PSHUP Template for EARNINGS
     (This example has one row of data which is for the earnings type: STP)
   • EXAMPLE 2 File Name:  PSHUP Template for DEDUCTIONS
     (This example has one row of data which is for deduction code: 000040)
   • EXAMPLE 3 File Name: PSHUP Template for TAXES
     (This example has one row of data which is for federal tax: State: $U)
2. You can use your template for the actual PSHUP file you want to create.  Start entering your data on row 3 of the example template so you can utilize the example row to be sure you are populating the data fields correctly.  After you have populated your template with the required data rows, delete the example row (row 2) and Save the file as your current period file.  Save the file so that it’s clear which pay period it is for, example: 010_PSHUP_05B_2023_EARNINGS.

1. The columns that are highlighted in GREEN are mandatory depending on the type of transaction entry (earnings vs. deductions vs. taxes).  Be sure to populate your file with current period data, DO NOT copy any data in the GREEN columns from your example row.

2. The following are key fields (that can uniquely identify rows in a table):

Key          Field Name               Description
Y          PU_SOURCE               Paysheet Update Source
Y          CREATION_DT           Creation Date
Y          COMPANY                 Company
Y          PAYGROUP                 Pay Group
Y          PAY_END_DT              Pay Period End Date
Y          OFF_CYCLE                 Off Cycle ?
Y          EARNS_BEGIN_DT      Earnings Begin Date
Y          EARNS_END_DT         Earnings End Date
Y          EMPLID                       Employee ID
Y          EMPL_RCD                  Employee Record
Y          SEQNO                       Sequence Number

3. Column A (PU_SOURCE) is a required field. It must be set to 'OT' (Other Sources),
   so the Load Paysheet Transactions (PYLOAD) can recognize the data source for paysheet update.
4. Column F (OFF_CYCLE) is a required field. It must be set to 'N'.
   If left blank, the Load Paysheet Transactions process (PYLOAD) would not be able to process the data.
5. Column G and H (EARNS_BEGIN_DT and EARNS_END_DT -
   Leave blank for Deductions and Taxes transactions. When left blank, the Load Paysheet Transactions process (PYLOAD) will set these dates to the current pay period begin/end date. For Earnings type of transactions, you can enter dates to override the default payline values (pay period begin and end date).
6. Column K (SEQNO) is a required field. The sequence number needs to be unique based on other key data: Pay End Date, Empl ID, Empl Rcd and Pay Group.
   For data entry simplicity and efficiencies, you can simply number each row in the spreadsheet sequentially, i.e.: row 2 = 1, row 3 = 2, row 4 = 3, etc. all the way down to the last row.
7. Columns R, S, T & U (DEPTID, JOBCODE, POSITION_NBR & ACCT_CD) are NOT required fields, however, the data should be populated if it’s an “override” to the employee’s job data or if different from the CTC Earnings Distribution.
8. Column AB (OTH_HRS) - Set to 0.00 for Deductions and Taxes transactions.
   For Earnings type of transactions, enter the number of hours paid via the Earnings Code.
9. Column AD (OK_TO_PAY) - Normally, set to 'Y'.
10. Columns AF, AG & AP (STATE, LOCALITY, TAX_CLASS) are for Taxes type of transactions. Otherwise, leave blank.
11. Column AQ (ONE_TIME_CD) is a required field for Deductions and Taxes transactions. Be sure to use the correct code ie: A=Addition, O=Override, or R=Refund.  When entering an amount for a One-Time Code of R (Refund), use a positive amount. The system will utilize the one-time code of R to process the refund. If you use a negative amount for a refund, the amount will be deducted from the employee's pay, not refunded.
12. Columns AS, AT, AU, AV & AW (PLAN_TYPE, BENEFIT_PLAN, DEDCD, DED_CLASS, & DED_CALC) are required for Deductions transactions. It is important to note that for the Deductions transactions, the PLAN_TYPE (column AS) is populated with a 2-character plan code, and the DEDCD (column AU) is populated with a 6-character deduction code. For example, for Medical Plan, PLAN_TYPE: 10, DEDCD: 000040. DO NOT change the formatting of these cells, both should already be formatted as "General" or "Text".
13. The columns that are highlighted in ORANGE are mandatory as well, but you will need to copy them down as they are entered in the example row on the template (unless you need to use those fields in your transactions).