Software Details

Processing a Pay Period

What is processing a pay period?

The TimePilot system will collect clock in and clock out data for months at a time if you allow it to. As employees clock in and out, their transactions are placed into a file called "Unprocessed Transactions." But once a pay period is over, it's a good practice to "process" the transactions. There are several good reasons for doing this:

• It keeps all the transactions for one period of time in one place.
• Along with the transactions, it also saves all the software settings—overtime policy, shifts, employee profiles, etc.—that were in effect at the moment you processed the period. This is important because if you later make changes to your company's work policies while working in the Unprocessed Transactions, those changes will not affect any processed periods. For instance, the software will prevent you from deleting an employee until that employee's transactions have been processed from Unprocessed Transactions. If the software didn't do this, and you deleted an employee, you'd create "orphan" transactions—transactions without an owner.

For instructions on how to process a pay period, click here.

Oops! You entered the wrong dates for your pay period, and now you don't have all your employees' clock-ins and clock-outs in the extracted pay period. No problem. Here's how to fix it.