We are experiencing two issues with timekeeping via DC-C:
 
1) The start (CLOCK IN) and stop (REPORT LABOR) times do not agree with the system (computer) time. For example, in experiments we have done, the time stamp in EVO (at the moment we answer Y to CLOCK IN? or REPORT LABOR?) lags the system time by a random amount ranging for 7 seconds to 45 seconds. This becomes critical at the end of the day, as it gives the appearance that the employee is punching out early.  
 
So questions #1 - from where does EVO get it's time stamp, and how do we make it agree with the system time right down to the second?  
 
2) This may be related to #1 - We have seen several, random cases where an employee's total time for the day does not add up to 8 hours, even though the start and stop times would indicate that it should. This has only happened on days where the person was in two or more consecutive jobs, but it does not happen consistently. For example, the time stamps show a clock in to the first job at exactly 06:00:00, no time lag between jobs, and a clock out of the last job at precisely 14:00:00. However, EVO then calculates that total time for the day to be 7.99 hours, not 8.  
 
The only work-around we've found is to edit the Pending Labor Transactions, and manually change the start or finish time of one of the jobs so that two jobs overlap by 30 seconds. EVO then shows 8 hours for the day.
 
Question #2 - how can we look at the actual math as EVO converts minutes and seconds to hundredths of hours?

Thanks for the help, but we don't currently use the feature that allows multiple jobs to be open at one time. All our people work the jobs in linear fashion  - out of one, into the next.