DataLynx Compensation Data Quality

Avoiding/Resolving Common DataLynx Compensation Data Issues

Payroll/Compensation is a critical operations component and requires quality data every run. The DataLynx Compensation module relies heavily on good data entry at the store point-of-sale (POS) system as well as initial setup and ongoing maintenance to facilitate a smooth and accurate payroll cycle, especially for organizations with 10's or 100's of store locations.

The following details common causes of inaccurate data in the DataLynx Compensation module and how to resolve and/or avoid each issue:
  1. Missing Tech-to-Employee Maps -  This scenario is common. Every time a new Technician Number is added to a store POS, the technician will need to be mapped to the associated Employee in DataLynx using "Tech Maintenance" in the DataLynx Admin system. This is primarily for commissioned technicians to flow the technician-specific sales to the Employee.
    1. RESOLVE: There is a report called "Missing Tech-to-Employee Maps" to which the Compensation Admin may subscribe for daily alerts of any missing maps. Keeping on top of this process is also a method for AVOIDing this issue in Compensation.
  2. Switching Techs on RO's - This scenario is also common. Sometimes, a manager will switch techs on an RO after submitting the date to DataLynx.
    1. RESOLVE: Managers should immediately resubmit DataLynx for any date a "tech swap" is performed for a prior date. To do this, open the DLClient application on the store server=>Click Tools=>Resubmit Dates. Enter Username, password and start/end dates=>Submit:
    2. NOTE: DataLynx is working on a refresh process that auto-detects this scenario and auto-refreshes.
  3. Split Tickets (ROWriter only) - This feature is not supported by DataLynx for the ROWriter POS system. This feature in ROWriter causes DataLynx to overstate technician sales for the technicians split on the RO. This scenario can be easily identified by subscribing to the "Invoice Mismatch" report as a daily alert. Not all items that show up on this alert report are due to a Split Ticket, but it is the most common cause. Bottom line, this alert will include any Split Tix.
    1. AVOID: We strongly recommend locking down this function in ROWriter to avoid its accidental use. A common method for locking down this feature is to assign a security level in ROWriter for this feature that is higher than the store manager's security level.
    2. RESOLVE: To unsplit a split ticket, the invoice needs to be re-written in ROWriter. 2 methods include:
      1. Allocate all jobs on the RO to 1 technician only
      2. Create 2 separate jobs for each of the split jobs. Split the amounts between the 2 jobs (on both labor and parts) and assign 1 tech to job 1 and the other tech to job 2.
IMPORTANT: For weekly payroll cycles, the payroll is locked in DataLynx on the following Monday night. Any changes thereafter will not be automatically reflected without manually “unlocking” the payroll on both the Technician and Manager screens on DataLynx and clicking “Save”. The payroll period will relock automatically at night again.

    • Related Articles

    • ROWriter Instructions for Employee Setup

      Your shop is now utilizing DataLynx Online as an add-on to ROWriter for managing its employee compensation program. As part of this setup, the employee number of all employees must be standardized across all shops where they may currently record time ...