Why do "punch outs" appear at different times in Kronos than in FieldClock

Kronos CSV Export

This article only applies to users who are using the Kronos CSV export and are omitting Non-Productive Time from their payroll export.

Our Kronos CSV exports a "Time In" and "Time Out" for each payout. Generally, this is pretty simple.  If an employee clocks in at 5am, and out at 1:30pm, it's simple enough:

  • Piecework -- In @ 5am; Out @ 1:30pm

Things start getting more complicated as soon as you add a break at that job.  Let's say there's a paid rest break for 10 minutes starting at 7am.  Now our CSV export looks like the following:

  • Piecework -- In @ 5am; Out @ 7am
  • Paid break -- In @ 7am; Out @ 7:10am
  • Piecework -- In @ 7:10am; Out @ 1:30pm

Once you add in an unpaid lunch break, another rest break, and maybe some travel or training periods...  you can have a lot of In and Out times for 1 employee!  

  • Piecework -- In @ 5am; Out @ 7am
  • Paid break -- In @ 7am; Out @ 7:10am
  • Piecework -- In @ 7:10am; Out @ 9am
  • Piecework -- In @ 9:30am; Out @ 11:30am
  • Paid break -- In @  11:30am; Out @ 11:40am
  • Piecework -- In @ 11:40am; Out @ 1:30pm

By default, FieldClock will export all this data to Kronos for you.  However, you may want to have Kronos calculate it rather than using FieldClock's data.  In this case, you can specify "Omit Non-Productive Time" in your Payroll configuration and FieldClock will only export basic time data.

If you omit non-productive time in your Payroll export, It is important to note that the "Out" time you see in FieldClock may not be the same as the "Out" time you see in Kronos.  This is because FieldClock stores the total hours that an employee should expect to be paid for their work.  

In the above scenario, the Employee starts at 5am and ends at 1:30pm.  Once you deduct their 30 minute unpaid lunch break, they should expect to be paid for 8 hours of work.  As a result, FieldClock will export their time as "In @ 5am, Out @ 1:00pm" to capture the full 8 hour work period.  

 

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.