Payroll Batches are the most complex part of FieldClock, as each is unique to the payroll software. While we do our best to make them as easy as possible to create and understand, sometimes codes/values appear to be missing or incorrect.
This article aims to answer common questions as well as clarify various 'nuances' in order to help avoid confusion.
Can Payroll Batches be deleted?
We don't currently allow payroll batches to be deleted. If a mistake has been made, you have a couple of options:
- Correct the data in the export file: open your export file batch and correct the data prior to uploading to your payroll software
- Correct the data in your payroll software: upload your payroll batch as usual, then correct the data
Although this isn't an ideal solution, we do have some functionality in the works that will allow some modifications to Batches in the semi-near future.
"hh:mm" vs decimal format for time
All downloadable Payroll Batch files (.txt, CSV) use decimal format for time, with the exception of a select few. However, our 'Printer-friendly By-rate' report and "Printer-friendly Details" report uses "hh:mm" format. This may be confusing when comparing data between the two, or when comparing to data in one of our dedicated reports such as the Daily Activity report. As an example, if an employee's calculated time in a Batch file is 7.56, this would be presented as 7:33 in "hh:mm" notation in the Printer-friendly report and the Daily Activity report.
Rounding
Continuing with the above example, if an employee's calculated time is 7.56, this would be presented as 7:33 in "hh:mm" notation -- however, working 33 minutes backwards to decimal would indicate that the decimal value should be is .55.
Programs for examining payroll files
While your system may provide software that allows you to view payroll files (such as Text Edit or Excel), sometimes better programs are needed for better viewing. One such (free) program is VS Code, which runs on both Windows and Mac, and will provide a nice environment for sifting through Payroll Batch data.
Why does the Date column not have a preceding '0' for the month?
When viewing dates in Excel (or attempting to import a Payroll Batch file and getting an error), you may notice that 'June 10th, 2021' is represented as '6102021' rather than '06102021'. This is due to Excel cutting off the preceding '0', and is done automatically due to '6' just being '6' in numerical form - not '06'. This only happens when viewing Dates in Excel, but the actual CSV file does include the preceding '0' if viewed outside of Excel, such as TextEdit or another program that shows 'raw' data.
If you need the preceding '0' for import, do not save the batch file after opening it in Excel - it will cut off the '0'. Please duplicate the file, one for viewing and one for importing, or, simply don't save the file after opening it in Excel; close it and import as you normally would.