Millennium Error Messages

  • Employee Failed Validations: Employee missing Federal Tax Information; Employee missing State Tax Information. The EE record was created in HR but the taxes were not completed in payroll. Either a value is missing in payroll or the employee's tax information may not have been entered correctly in HR to match the tax record in payroll.
  • Employee Failed Validations: Employee missing State Tax Active Filing Record. The EE record was created in HR but the taxes were not completed in payroll. Either a value is missing in payroll or the employee's tax information may not have been entered correctly in HR to match the tax record in payroll.
  • No current Federal withholding taxes in payroll as of [DATE] See Taxes comment above.
  • Error Updating Deductions - Operator '=' is not defined for type 'DBNull' and type 'Date'. May be code related and need technical intervention.
  • Error Updating Direct Deposits - Object reference not set to an instance of an object. The EE record was created in HR but the DD was not completed in payroll. Either a value is missing in payroll or the employee's DD information may not have been entered correctly in HR to match the DD record in payroll.
  • Employee Failed Validations: Fringe Benefit earning code not found in payroll [Code]. In payroll, the Employer Cost of benefits goes to the Fringe tab. In order for an Employer Contribution to sync, both an Earnings (Fringe) code and Deduction code must be tied to the benefit, even if the employee cost is zero. Both codes must exist in payroll and HR, and both codes must be in the HR code group. In this type of instance, most likely the earning codes do not exist in payroll. If the [Code] does not belong to a fringe benefit, then verify that the earning deduction code configured at the benefit level in HRIS is not populated with a value.
    • Note: If the [Code] does not belong to a fringe benefit, then verify that the earning deduction code configured at the benefit level in the HCM is not populated with a value.
  • Employee Failed Validations: Termination Reason not found on company. In payroll, the Company Setup > Miscellaneous Tab > Term Reasons does not include the same ‘Termination Reason’ value being sent from HR. Also, the sync is based on the payroll code (not the description). The client may have added this value in HR but not in payroll.
  • Employee Failed Validations: More than one 100% direct deposit for this employee. This is most likely due to the DD records for this EE includes more than one percentage election. Election must add up to 100% in HR before syncing to payroll.
  • Employee Failed Validations: Workers Compensation Code not found on [Company ID]: In payroll, the Company Setup > Workers Comp Tab does not include the "Company ID" value. The client may have added this value in HR but not in payroll. Any changes at the Company Setup level (list values) need to be updated in both systems.
  • Employee Failed Validations: Cost Center 1 not found on Company: [Department Value]. In payroll, the Company Setup > Departments Tab does not include the "Department" value. The client may have added this value in HR but not in payroll. Any changes at the Company Setup level (list values) need to be updated in both systems.
    • Note: Any changes at the Company Setup level (list values) need to be updated in both systems.
  • Employee Failed Validations: Benefit Range dates overlap in HR: This usually happens when an Admin manually changes dates for a benefit, and/or adds a mid-year plan change, and the End Date of the previous coverage occurs after the Start Date of the new coverage. For troubleshooting, make sure that the plan code for the benefit in the error message is not used across other benefits. In other words, the plan code can only be used on ONE benefit in a benefit package.
    • Note: For troubleshooting, make sure that the plan code for the benefit in the error message is not used across other benefits. In other words, the plan code can only be used on ONE benefit in a benefit package.
  • Employee Failed Validations: Employee Type not found on company: In payroll, the Company Setup > Miscellaneous Tab > Employee Type does not include the same value being passed from HR. The client may have added this value in HR but not in payroll. Any changes at the Company Setup level (list values) need to be updated in both systems.
  • Error Creating New Employee: The employee ID cannot exceed six characters. This is a Millennium limitation on Employee ID specs. In HR, you have more flexibility but it must comply with this specs for the sync to be successful.
  • Error Updating Employee: Index was outside the bounds of the array. This often indicates that the Supervisor for the employee in HR does not exist in Millennium or is not included in the Sync.
  • Employee has changed pay schedules to Semi-Monthly. Pay frequency must be updated in payroll first. This error pops up often. When a company has multiple pay schedules set up, an employee is assigned Pay Schedule ‘A’ in HR, it syncs with payroll, but when the employee's pay schedule is changed to Pay Schedule ‘B’ in HR, you must manually update the frequency in payroll at the same time. Otherwise, we get this error. It won't automatically sync the change because it "figures" that this type of change may also impact rates, tax withholding, deductions, etc., so the sync alert gives you a heads up.
  • General Company Error: An item with the same key has already been added. If this error occurs on sync, the error will have been caused by a functionally duplicate value in the Millennium payroll Company or Master Company Configuration in one of the following tables: Company Code Groups; Company Tax States; Company Accrual Codes; Company Supervisors. Because Millennium prevents duplicates in most of these tables, the likely culprit will be taxes, where multiple SITW records can be added for the same State and with overlapping dates. Millennium will produce a warning when this occurs.
    • Note: Tax records are active if the check date is between the tax record's start and end date. A yellow warning will indicate a problematic record in Millennium (but will not prevent SAVE).
  • There was an error encountered. This error is typically code related and may need technical intervention. Reach out to your Support Representative.

  • There was an error encountered. Please report this to Product Support. Object Reference not set to an instance of an object. This is a general error that is seen in the view screen within the middleware. A connection could not be made between HR and the middleware. Best-practice is to log out of the middleware and LOG BACK IN to clear the error.
Was this article helpful?
0 out of 0 found this helpful