Mass Load
- Former user (Deleted)
- Andrea Boehm
- Lori Miller
The user would need the MODULE_IMPORT and both CREATE and UPDATE for a given entity in order to use mass load. To check or add, go to SYSTEM/ROLE.
The Mass Load program allows a district to import data into the USPS Redesign from an outside source. This may include, but is not limited to, Excel, Access, Lotus and other third party software's that have the option to export data in a CSV (Comma Separated Values) format. The Mass Load program reads the data, imports and validates it, then writes it to the USPS file structures, thus eliminating manual entry. This might be useful for a district converting to USPS or for a district processing mass updates to varying fields.
All possible field values are outlined in the Miscellaneous notes section, under the Mass Load Criteria. Any records with fields not meeting the USPS possible values validity checks are rejected. A message is written to the reports indicating what record included invalid data.
The CSV being read by the Mass Load options can include the fields in any order. The file must contain a header record which includes all the pre-defined field names (Req Column Desc) as the first record in the import file. The pre-defined field names are included in the Mass Load Criteria found in the Miscellaneous notes section of this chapter. The remaining records in the file represent the data values being loaded.
The Custom Report Creator option under Reports can be used to create a report containing current data. Example-Payroll Items-you are wanting to create a file to use for loading a new rate. (If need more help with creating Detail Reports, Click 'Custom Report Creator') The Custom Report Creator can be used to create a file with the appropriate headers that are required to be used when processing Mass Load to import data. To do so, Select the Object you wish to import. Once the object is selected, choose the Identifying fields under the appropriate Properties that will be needed to make the changes desired. (Below are lists of header definitions for each Object)
Once you have selected the correct identifying fields (view table below), desired.
The detail report writer will also allow you to select and filter current identifying fields under the Configure Filters tab.
The Generate Report tab allows you to create the report.
Under the Format option Select the Excel-FieldNames. Enter in a file name and click generate report. This will create an Excel file you can now edit and then Save As a csv file and then can be used to import data using the Utilities/Mass Load option.
Example of Excel-FieldNames:
Using the Mass Load Feature
Go to Utilities and Select Mass Load
- USPS Load File-Click
and locate the file you wish to load. The USPS Load File can be an import file supplied by a third party software as well as a custom created report. The file must be in comma separated values (CSV) format. - Importable Entities-Select from the drop down
the Entity you wish to load the data into. - Click
MASS LOAD CRITERIA
Each Object to be imported, has to be created on a separate .CSV file. The Identifying Fields below have to entered exactly how they are written. For more Identifying and Optional fields, please use the Custom Report Writer to find the field names. 'Select Object' to open up the Property names and hover over the name with your mouse pointer: example. ('RegularItemConfig' Object - Employer Health Coverage identifying field would be employerHealthCoverage.
Mass Load will always attempt to change the value in the database with the value (blank or not) in the import file. So, therefore, any blank/empty values in a column in the import file will result in setting the value in the database to empty. In the case of numeric values, empty equates to zero, for strings, it will either be null or an empty string. There is no defaulting, it will set the value to what the user specifies.
If a new record is being created in the database, and a field that is NOT in the import file would normally be defaulted (as when adding via the UI), then it will end up with default values for certain fields.
USPS-R always use 'true'/'false' (lowercase) for all boolean fields (flags). Example-Employee--odjfReportable, reportToEMIS
| Object to be imported | Identifying fields that must be included in the file | Optional fields |
|---|---|---|
CompensationAllows all Compensations (Non Contract, Contract and Legacy Compensations to be updated Contract and Non Contract Compensations can be added (created) but Legacy CANNOT be added | To Update Compensation record: code (this replaces the id of the compensation) Has to match what the employee's code is exactly. position.number position.employee.number type
To Add a new Compensation record: code - (enter unique code: Example 1234-33. cannot be left blank) position.number position.employee.number type
payUnit
payPlan
| Compensation: type jobCalendar.description jobCalendar.type jobCalendar.archived description (compensation) label (No apostrophe is allowed in the label name) dateRange.startDate (compensation) dateRange.stopDate (compensation) payPlan
payUnit
unitAmount retirementHours strsAdvance
supplementalTaxOption
archived
contractDaysWorked hoursInDay primaryCompensation
Contract: payPerPeriod contractAmount (No comma in the amount - 2000.00) contractObligation (No comma in the amount - 2000.00) paysInContract retroNextPay stretchPay
Salary Schedule: salaryScheduleColumn - Only Numeric salaryScheduleId - Alpha and Numeric salaryScheduleStep - Only Numeric State Reporting: customFields.reportableToEMIS.value customFields.localContractCode.value Historical Context: calendarDate.startDate calendarDate.stopDate Legacy Compensations Headers:
|
Adjustment JournalKeep in mind if the adjustment should apply to a specific payroll item you will need to supply the Payroll Item Code and Position Number(if position level payroll item) to correctly create adjustments Adjustments can only be created via mass load. You will not be able to update existing adjustments via mass load. | employee.number payrollItem.code amount transactionDate type - The Type column must contain one of the following values:
| payrollItem.position.number (if applicable) description imported
monthToDate *(See note below) quarterToDate *(See note below) yearToDate *(See note below) fiscalYearToDate *(See note below) *The 'default' value for all 4 to date flags is TRUE, so if there are no columns listed specifying the load for to date data to be FALSE, it will always be TRUE. Even if the columns are not listed on the report. Example- you are needing to change just YTD data. You would make sure that each record for YTD is set to TRUE. You would also need to have the MTD, FYTD and QTD columns on the spreadsheet with FALSE listed so that only the YTD data is updated. |
Employee**Note** Enter dates as MM/DD/YYYY For dollar amounts, omit the $ sign
INFO: If updating Employee ID to SSN, the Old History attached to the Employee ID will remain | id = the database id
number name.lastName (to add) name.firstName (to add) | Identification: ssn
customFields.credentialID.value customFields.emisId.value Name: name.lastName name.firstName name.middleName name.suffix Legal Name: legalName.lastName legalName.firstName legalName.middleName legalName.suffix Address: address.street1 address.street2 address.city address.state address.postalCode address.foreignAddress address.province address.country Contact: customFields.workPhone.value customFields.homePhone.value customFields.homePhoneUnlisted.value primaryEmailAddress secondaryEmailAddress otherEmailAddress **SERS New Hire report uses this field for reporting** General: maritalStatus archived
customFields.eligibleForRetirement.value
emailDirectDeposit
customFields.gender.value
newHireReportedODJFS
odjfsReportable
osdiCode customFields.partTime.value
reportToEmis
customFields.spouseFirstName.value customFields.subDays.value Dates: birthDate hireDate lastPaidDate odjfsHireDate terminationDate Evaluation: customFields.lastEvaluation.value customFields.nextEvaluation.value Experience: customFields.accredDistrictExperience.value customFields.authorizedExperience.value customFields.buildingExperience.value customFields.districtExperience.value customFields.militaryExperience.value customFields.nonOhioPrivateExperience.value customFields.nonOhioPublicExperience.value customFields.ohioPrivateExperience.value customFields.ohioPublicExperience.value customFields.principalExperience.value customFields.purchasedExperience.value customFields.retireSystemExperience.value customFields.totalExperience.value customFields.tradeExperience.value Race: customFields.primaryRace.value **required if adding new Employee**
race.americanIndianAlaskaNative
race.asian
race.black
race.nativeHawaiianPacificIslander
race.white
race.hispanicLatinoOption
Standard Payroll: checkDistribution customFields.payrollCode1.value customFields.payrollCode2.value customFields.payrollDate1.value customFields.payrollDate2.value customFields.payrollText1.value State Reporting: customFields.ECEQualification.value
customFields.degreeType.value
customFields.handicapStatus.value customFields.longTermIllness.value customFields.nonCertificateEmployeeID.value customFields.otherCredentials.value
customFields.semesterHours.value |
Date CodeCore>Date Code>Date Text Field | name propertyName | group |
Employee -Custom Date Fields | number customFields.testDate.date (Date to be imported) customFields.testDate.dateText (Description) In this example 'testDate' is the property name of the Date Detail to be loaded. This part of the header will be different for each Date. This can be found on the Date Codes view. Example a Date Code called "Fingerprinting" is created Example of date header- customFields.fingerprinting.date. Example of text header-customFields.fingerprinting.dateText Multiple dates can be imported per employee per file as long as each date has the correct header. | |
Position | employee.number - Employee Number number - Pos # retirementCode (only when adding a new position) - Retirement Code
| archived
positionDescription jobStatus
payGroup.code appointmentType
buildingCode.code departmentCode.code customFields.extendedService.value fte hireDate positionDate.startDate positionDate.stopDate customFields.raiseDate.value terminationDate supervisor.number timesheetRequired
Eligibility Flags: eligibleForPersonLeave
eligibleForSickLeave
eligibleForVacation
EMIS Related Information: customFields.reportableToEMIS.value
customFields.positionCode.value - Position Code customFields.stateReportingAppointmentType.value (only use the numbers)
customFields.positionType.value (only use the letters)
customFields.positionStatus.value (only use the letters)
customFields.fullTimeEquivalence.value
customFields.specialEducationFullTimeEquivalence.value
customFields.lowGrade.value (only use the numbers, letters, or two asterisks for Not Applicable.)
customFields.separationReason.value (only use the numbers)
customFields.paraprofessional.value
customFields.contractAmount.value customFields.contractWorkDays.value customFields.hoursInTheDay.value customFields.highGrade.value (only use the numbers, letters, or two asterisks for Not Applicable.)
customFields.separationDate.value customFields.paraprofessionalHireDate.value customFields.buildingIRN.value customFields.experienceCurrentClass.value Funding Source: customFields.assignmentArea.value (only use the numbers)
customFields.fundingSourceCode1.value (only use the letters)
customFields.percent1.value customFields.fundingSourceCode2.value (only use the letters)
customFields.percent2.value customFields.fundingSourceCode3.value (only use the letters)
customFields.percent3.value |
Position-Custom Date field | employee.number number customFields.testingDate.value | |
Payroll Item Configuration (Select PayrollItemConfiguration Entity)The import file can contain multiple payroll item configuration types in one import. Click here for a sample load file. Adopt Assistance Item Config Annuity Item Config Child Support Item Config City Tax Item Config Dependent Care Item Config Employer Sers Item Config Employer Strs Item Config Federal Tax Item Config Health Savings Account Item Config Medical Saving Item Config Medicare Tax Item Config Ohio State Tax Item Config Osdi Tax Item Config Regular Item Config Savings Bond Item Config Sers Annuity Item Config Sers Buy Back Annuity Item Config Sers Item Config Social Security Tax Item Config State Tax Item Config Strs Annuity Item Config Strs Buy Back Annuity Item Config Strs Item Config | Add a new Payroll Item Configuration: payee.id OR payee.number (one of these) code type
paymentCycle
Modifying existing Payroll Items Configurations: code
| addGrossToPayablesReport Adoption Assistance Item: name abbrev w2abbrev paymentCycle suppressSsnId employerHealthCoverage voluntary required showOnCreateWizard Annuity Item: achSource annuityType cca ccaDescription certifiedObj city classifiedObj designatedRoth employerHealthCoverage jobLevel medicarePickup name nonWages125 osdiCode otherObject postalCode printEmployerAmount rita ritaDescription reportToCCA required showOnCreateWizard state stateId payee.address.street1 payee.address.street2 payee.address.city payee.address.state payee.address.postalCode payee.address.foreignAddress payee.address.province payee.address.country payee.phone.internationalCode payee.phone.number payee.phone.extension payee.phone.unlisted payee.fax.internationalCode payee.fax.number payee.fax.unlisted suppressSsnId taxEmployerAmounts taxEntityCode taxNonCashEarn voluntary w2abbrev |
Payroll Item (Select the PayrollItem Importable Entities)The import file can contain multiple payroll items and employee's in one import. Example of a Payroll Item Mass Load csv: payItemMultipleCreateTest (1).csv Adopt Assistance Item Annuity Item Child Support Item City Tax Item Dependent Care Item Employer Sers Item Employer Strs Item Federal Tax Item Health Savings Account Item Medical Saving Item Medicare Tax Item Ohio State Tax Item Osdi Tax Item Regular Item Savings Bond Item Sers Annuity Item Sers Buy Back Annuity Item Sers Item Social Security Tax Item State Tax Item Strs Annuity Item Strs Buy Back Annuity Item Strs Item Payroll Item Error AdjustmentUse Importable Entities: payrollItemErrorAdjustment Payroll Item Employer Error AdjustmentUse Importable Entities: payrollItemEmployerErrorAdjustment | configuration.code employee.number position.number - only needed if payroll item is deduction by job code employeeNumber positionNumber amount date description code employeeNumber positionNumber amount date description | employee.ssn accountNumber archived
For ACH fields - use the following below: Dependent Care and HSA
additionalWithHolding advanceErrorAdjustment Covid19 Fields
deductionType (for City Tax Item)
effectiveRetirmentDate Employee Deduct Max Amount-use the following below:
Employer Deduct Max Amount-use the following below:
-Annual employerRate - (No comma in the amount Ex. 2000.00) New W4 fields useNewW4
filingStatus
twoLikeJobs dependentAmount otherIncome deductionAmount fullOrPartTime
increasedCompensation
lastModifiedDate maritalStatus
newEmployee
numberOfExemptions osdiCode PayrollItemType payCycle
pensionPlan
percentOfGross position.number - only needed if payroll item is deduction by job rate - (No comma in the amount Ex. 2000.00) rateType
rehiredDate rehiredRetiree
activeDateRange.startDate (not specific on how date is entered) activeDateRange.stopDate (not specific on how date is entered) surchargeExempt
type
typeOfBenefit Retire Rehired Reporting - 450 Payroll Item
|
Attendance JournalLoad files may contain only Attendance, only Absences, or a combination of both Absences and Attendances. Example of Attendance and Absence Journal Modify Template | employee.number id (only if modifying a current record) position.number compensation.code type
category (Absence)
category (Attendance)
activityDate
length unit
| appliedToBalance appointmentType
dayOfWeek id (Compensation) payDate subCategory substituteFor - (enter employee number of the substitute) type usasPostingIndicator |
LeavesSick Leave Personal Leave Vacation Leave If wanting to zero out the balances, use Mass Load Accumulation Transaction: employeeNumber leaveType length (enter a negative figure to zero out balance) | employee.number type
The leaves will load if they are not eligible but will not display in the Leaves grid until the Eligibility for the leave is checked in Position grid. Warnings will be given: Warning: Employee XXXXXXXX is not eligible for XXXXXXX leave. XXXXXXX leave entry was loaded but will not be displayed when viewing leaves for the employee. Warning: Employee XXXXXXXX is not eligible for any leave. Leave entries were loaded for this employee, but this employee will not be displayed when viewing leaves. You must provide employee.number and type in your load file. If Leaves do not exist for a given employee during the load, then the leaves will be added. If the employee already has Leaves, then they will be updated. For any fields that apply to sick leave only, you will have to provide the header name in the header row, and then supply a value for the sick leave record. Vacation and personal should contain commas as placeholders for the sick leave only fields. For example:
If during a modify load you change the leave unit for an employee's existing leave, from daily to hourly or vice versa, you will need to provide an additional field in your load file with a header value of hoursInDay. This is a decimal value that will be used to convert the leave balance. If converting from daily to hourly, the existing leave balance will be multiplied by the hoursInDay value to get the new balance. If converting from hourly to daily, the existing leave balance will be divided by the hoursInDay value to get the new balance. The hoursInDay must be between 1 and 8 and contain no more than 2 decimals. To convert the balance, all leave types must have the same leave unit and hoursInDay in the load file. | If header column field is not included, then data is not changed or defaulted and all other fields are correct. **NOTE**If a field is in the header and no value given for employee, then it defaults to a default value such as 0 if numeric (ex. accumPerMonth, maxLeaveAmount). accumPerMonth accumulateBasedOnHours
advancedUnitsUsed currentServiceHours employee.name.lastName employee.name.firstName leaveUnit
maxAdvanceLeave maxLeaveAmount personalLeaveAccum resetValue serviceHoursAccumulator FOR SICK LEAVE ONLY: accumulateBasedOnHours
currentServiceHours maxAdvanceLeave serviceHoursAccumulator |
Compensation JournalCompensation | Headers that are required for compensation journal entry:
Once the Excel spreadsheet has been created, you must manually add in all the following headers:
In the spreadsheet file, you need to manually enter in the amount fields, days Worked and description. The amount fields and days worked cannot be blank. Enter zeros if no amount is needed.-Note: Adding zeros to these fields will not change the current value if one exists. **NOTE**Once the spreadsheet file has been created and data has been filled in, go to Mass Load and select the CompensationJournal entity. | |
Payroll AccountsThe following will be checked on import:
**NOTE** If you get a SEVERE Error, no data will be updated for anyone on the file If wanting to create a spreadsheet to update current Payroll Accounts, use Custom Report Creator and select the Object, Payroll Account (No 's' at the end) Below are the Properties that can be selected using Payroll Account and Report Options, Excel-FieldNames:
Once spreadsheet is created, column headers may need to be updated to match the correct field names to the right | positionNumber employeeNumber id -
rateType
status
Rate (once .csv is created, change the header to be 'chargeAmountOrPercent' fund func obj scc subj opu il job | startDate
stopDate
leaveProjection
employerDistribution
maximum
sortOrder
|
Accumulation TransactionUse Accumulation Transaction to clear out Balances, use a negative length. | employeeNumber leaveType
length | positionNumber transactionDate
description employee.name.lastName employee.name.firstName leaveUnit
|
Pay Distributions**NOTE** If employee fails for 1 transaction, they will fail for all transactions for that employee. It will likely give same error message for all transactions for that employee | employeeNumber code (this field cannot be updated to be something different in Mass Load or using Mass Change, has to be manually updated) type
rateType
rate | startDate
stopDate
priority Direct Deposit Specific Headers
**NOTE** The transferType and transferCode are used together to find the ACH Source for a direct deposit.
|
User Adjustment Payables Ledger(Process Outstanding Payables/Payables Adjustments) | Headers (all required) - This mass load will only CREATE new items, you cannot use this to update existing payables:
| |
Future Pay Amount**NOTE** If wanting to update different fields for different employees on the same load, you will need to put the old (current) values wherever you don’t want it updated. You must supply a value for most fields because null value does not work for most fields. To add and update Future Pay transactions in one upload, you would have to supply all the values in the current because null values (,,) will give errors for most fields such as true, false. Some have default values if not supplied. | Add Future Pay Amount
Update Future Pay Amount
| effectiveDate - in YYYYMMDD format supplementalTaxOption
rate - if rate is not supplied in csv file, it uses the compensation rate for that employee/position retireHours description appliesForRetirement
supplemental
specificPayAccount.rateType - (Must include in file if using Specific Pay Accounts)
specificPayAccount.amountCharged - (Must include in file if using Specific Pay Accounts) specificPayAccount.accountOrXrefCode
specificPayAccount.leaveProjection - (Must include in file if using Specific Pay Accounts)
specificPayAccount.employerDistribution - (Must include in file if using Specific Pay Accounts)
When adding specific accounts, you have to provide either the xref code of the expenditure account OR the full account code (no hyphens between account dimensions). If you are updating a future pay and including a specific account, if the account you provide in the load file already exists on the future pay, then the specific account will be updated with the account values you provide in the load file. If the account does not exist on the future pay, it will be added as a new specific account. |
ACH DestinationCore>ACH Destination | routingNumber (Must be 9 characters) description | |
PayeeExample of Payee Mass Load Headers | id
| number name secondName electronicPayment archived adress.street1 address.street2 address.city address.state address.postalCode address.foreignAddress address.province address.country phone.number phone.internationalCode phone.extension phone.unlisted fax.number fax.internationalCode fax.extension fax.unlisted |
Warnings and Errors
No Position found for # , Employee #XXXXXXXXX
'For input string: "" - error given when load values for employee id or position number are not supplied
Missing required headers
- Standard mass load error that reports missing required headers
Length cannot equal zero
No Leaves found for Employee#$(employeeNumber)
No Position found for #$positionNumber, Employee#$employeeNumber
No Leave found for type $leaveType for Employee#$employeeNumber
Absence
Cannot calculate absence length - no active compensations found for Employee XXXXXXXXX - Position Null- check they have an active compensation or a Leave Unit (Daily or Hourly) selected in the employee's Leaves
Can not find entity reference - Make sure Employee ID is correct
Compensation is advanced. New earnings (REG) may not be added to the compensation.
Irregular pay type affects contract amount paid for advanced compensation, can not be used.
Unable to convert '2022408' to Calendar for property activityDate
- date should be '20220408'
Payroll Account Errors
- Error: Payroll Account percentages must total 100% from Rule 'Ensure Payroll Accounts with rate type percent add up to 100% in org.ssdt_ohio.usps.model.payrollaccounts'
- Payroll Account must equal 100%. Update in Payroll Account for employee
- If updating a Payroll Account, same Position Number, for an employee in a file. for example, adding a stop date, but also adding a new Payroll Account, same Position number, for this same employee, old account has to be Inactive, and the new account needs to be Active.
- Position with number XX not found for Employee #XXXXXXXXX - No Position# number found for this employee. Verify for correct Position# or add new position
- Employee with number NOACCT not found - Employee has not Payroll Account associated with Position #
- No expenditure account found for account codes null-null-null-null-null-null - payroll account missing in spreadsheet
- If loading more than one Payroll account for an Employee on the same Position#, the mass Load will fail for ALL Lines for this employee only. Correct and reload.
Pay Distributions Errors
- DirectDepositDistribution.directDepositType: may not be null (Value: 'null') -If one line fails for an employee, then all transactions for that employee will fail. Research and correct wrong transaction
- Missing Identifying Properties for Pay Distributions. Headers should contain the following [ employeeNumber, code, type, rateType, rate ] - verify all header names are entered
- Employee with number XXXXXXXXX not found-Verify employee number is correct
- Rate Type is required to load Pay Distributions - Verify Rate Type is entered correctly as False or True (case sensitive)
- Cannot convert Rate Type - Verify Rate Type is entered correctly as False or True (case sensitive)
Payroll Item
- Payroll Item type Regular does not equal Payroll Item Configuration type Annuity for code XXX - error means there is a mismatch of the Payroll Item Configuration 'Type' to the Payroll Item 'Type'. Verify which it should be and correct in Payroll Item Configuration or Payroll Item 'Type'
Payroll Item Configuration
- Payroll Item Configuration Type is required for add
- Payee ID or Payee Number is required for add
- No enum constant org.ssdt_ohio.usps.model.constants.PayrollItemType.XXXXXX
- wrong 'Type' name has been entered
Leaves
Warning: Employee XXXXXXXX is not eligible for XXXXXXX leave. XXXXXXX leave entry was loaded but will not be displayed when viewing leaves for the employee.
Warning: Employee XXXXXXXX is not eligible for any leave. Leave entries were loaded for this employee, but this employee will not be displayed when viewing leaves.
- Cannot Load Leaves:
- Employer Number is required to load Leaves
- Type is required to load Leaves
- Leave units for sick, vacation, and personal are not the same
- Leave Unit for employee must be the same for all Leave types, either all Hourly or all Daily
- Leave type unsupported: Vacation or Sick or Personal
- All need to be in CAPS VACATION or SICK or PERSONAL
- Missing Identifying Properties for Leaves. headers should contain the following (employee.number, type)
- Add employee.number and type to spreadsheet
Compensation
- Position #null for Employee #null not found
- Legacy Compensations can not be created in USPS. Legacy type is only valid when updating an existing Legacy Compensation
- ContractCompensation.payPlan: may not be null (Value: 'null'), Contractcompensation.payUnit: may not be null (Value: 'null')
- NonContractCompensation.payPlan: may not be null (Value: 'null'), NoncontractCompensation.payUnit: may not be null (Value: 'null')
Future Pay Amount
- Boolean value must contain true or false: value provided
- Compensation is advanced. New earnings (REG) may not be added to the compensation.
- Employee with XXXXXXXXX not found - No employee is found
- Employee with # not found - If no employeeNumber is given, then get error that Employee with # is not found
- FuturePayAmount.supplementalTaxOptionValid: Supplemental Tax Type must be false (Value:
- Irregular pay type affects contract amount paid for advanced compensation, can not be used.
- No Future Pay Amount record found for id (xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)
- No Position found for #99, Employee #XXXXXXXXX - No Position 99 for employee #XXXXXXXXX
- Pay Type 'Regular' must apply for retirement - If appliesforRetirement is set to null and if Regular Pay type, it must be 'True'
- Pay Type 'Irregular' must apply for retirement.
- Pay Type 'Shift Premium' must apply for retirement
- Specific Pay Account: Missing Amount Charged for new specific pay account with code XXXXXXXXXXXXXXXX for employee: XXXXXXXXX, position #
- Specific Pay Account: Missing Rate Type for new specific pay account with code XXXXXXXXXXXXXXXXXXX for employee: XXXXXXXXX, position #
- Specific Pay Account: Missing Leave Projection & Employer Distribution for new specific pay account with code XXXXXXXXXXXXXXXXXX for employee: XXXXXXXXX, position #
- Specific Pay Account: Missing Leave Projection for new specific pay account with code XXXXXXXXXXXXXXXXX for employee: XXXXXXXXX, position #
- Specific Pay Account: No expenditure account found (XXXXXXXXXXXXXXXXXXXXX) for employee: XXXXXXXXX, position #
- Warning: Specific pay account properties exist in load file with no specific account code for employee. XXXXXXXX, position: X, compensation code: xxxxxx-A. specific pay account not loaded - A Account code is needed in order to update any Specific Pay Account fields. The 'Specific pay Account' fields did not update, verify Amount Charged, Leave Projection, Employer Distribution fields are correct. Correct and reload.
Position
- Position saved with no retirement code - if adding new Position, retirementCode is required