Employee time entry and accounting system5459657Abstract A time entry and accounting system permitting employees to clock in and clock out from work at computerized time clocks located adjacent to their workstations using an individually encoded identification card. The time clock is configured to have a normally closed state and an opened state and to move between states in response to a supervisor scanning his identification card. The computerized time clocks are interactively linked to a central computer and, upon an employee clocking in or out, the central computer receives appropriate signals from the time clock, and stores information corresponding to these signals in memory. The information stored in the memory of the computer is subsequently used to develop accounting records and reports, to generate payroll data, and to send signals to the time clocks. The time clock further includes a display screen permitting the time clock to display messages in response to signals sent by the central computer and a plurality of buttons permitting an employee or supervisor to send additional information to the central computer. Claims What is claimed is: Description MICROFICHE APPENDIX
TABLE 1
______________________________________
CLOCK SCAN FILE
______________________________________
Clock Date Job Code
Clock Time Special Event Code
Employee Number Hours Worked
Clock time (In, Out, Meal)
Hours Types
Clock ID Hours Keyed by Supervisor
Supervisor Number No Badge Flag
Division Exceptions and Approval
Department
______________________________________
Referring to Table 1, the information generally includes the date and time, according to the time clock 101, that the employee either logged in or out on the current date, the identification number of the employee, information identifying the time clock 101 where the transaction took place, information identifying the hours worked and the type of hours, and information about whether the hours worked were for a special event. Further, files in the clock scan data structure 192 also contains information about each particular transaction, e.g., the supervisor who logged the employee in, and whether the supervisor used the NO BADGE button 144 (FIG. 2a). The information shown in Table 1 is preferably stored in a manner that is readily accessible to the computer 104. One method of organizing file data used in this preferred embodiment for the files of the clock scan data structure 192, as well as the files in other data structures described below, is the Index Sequential Access Method (ISAM). ISAM is a well known method of organizing file data, enabling the computer 104 to quickly locate information relating to each of the employees within the system. The front end process 190 also receives meal scan information from the dedicated meals time clocks 101. Such clocks 101 (which may be wired or wireless) are positioned within the employee cafeterias located in the workplace. These time clocks 101, in this preferred embodiment, are configured to signal to the front end process 190 each time an employee scan his ID card indicating that he has taken a meal. This information is then recorded by the front end process 190 in a file within a meals data structure 194 corresponding to this particular employee. The operation of the time clocks 101 located within the cafeteria is discussed in greater detail in reference to FIG. 21 below. The information stored in each file of the meals data structure 194 for each employee is summarized in Table 2 below.
TABLE 2
______________________________________
MEALS FILE
______________________________________
Company Department
Date Job Code
Employee Meal Count
Division
______________________________________
Referring to Table 2, an employee's file in the meals data structure 194 contains information about the employee including ID number, assigned company, department, division and job, as well as the number of meals he has consumed in the cafeteria on a given day. This information permits an accounting record to be made of the amount of meals consumed, which can be used for planning purposes. As can be appreciated, the information sent from the time clock 101 located within the cafeteria can be readily expanded in alternative embodiments. For example, a cashier could also be located adjacent to the time clock 101 who would then total the value of the meal taken by the employee and enter this information into the time clock 101. This information could then be used to either generate a more accurate accounting record, or even be deducted from the employee's paycheck depending upon the work rules for this particular employee. The front end process 190 also stores information in an Open/Close file 195. The Open/Close file 195 maintains a record of the number of times each time clock 101 was closed automatically and also records the name of the supervisor who did not close the time clock 101 by scanning his identification badge 170. The Open/Close file 195 is discussed in greater detail in reference to FIG. 8 below. The front end process 190 also retrieves information stored in the memory of the computer 104 which is then used by the time clock 101 when employees are clocking into and out of work. The operation of the time clock 101 during this type of clock processing is described in greater detail in reference to FIGS. 9-20 below. The front end process 190 typically retrieves this information from an employee master data structure 196. The employee master data structure 196 includes a file containing information about each particular employee. The information contained within a file in the employee master data structure 196 for a particular employee is summarized in Table 3 below.
TABLE 3
______________________________________
EMPLOYEE MASTER FILE
______________________________________
Company Standard Shift
Employee Number Start Day of Work Week
Check Digit Clock Zones
Name Pay Type
Division Status
Department Meals Allowed
Job Code Summary of Earnings Data
Base Rate Misc Demographic Data
Pay Rules
______________________________________
Referring to Table 3, an employee's file in the employee master data structure 196 contains information about the employee, including his name, his ID number, his employment status, e.g., whether he has been terminated, or on leave and the pay rates, pay rules and type for this particular employee as well as the standard work shift. Further, the employee's file also contains information about this particular employee's job, including the division, department, clock zone, and job code as well as a summary of earnings the employee has made to date within the current pay period. In the employee master data structure 196, there are also employee master files for each of the supervisors. The supervisor employee master files (not shown) contain similar information as shown in Table 3 above, and it additionally contains information about which time clock zones the supervisor is authorized to open the time clock and approve exceptions. The front end process 190 also retrieves information, in response to signals originated by the time clocks 101 during clock processing, from both a code files structure 200 which include a message/special event code data structure (not shown) and a job code data structure (not shown). The message/special event code data structure contains files for each of the special events for which a separate accounting record is being maintained. These files contain information about each special event as well as messages that should be passed along when a supervisor assigns an employee to a special event. The information within a file of the special event data structure is summarized in Table 4 below.
TABLE 4
______________________________________
CLOCK MESSAGES & SPECIAL EVENTS
______________________________________
Company Date Range
Division Message/Name
Department Event Code
______________________________________
The job code data structure contains a file for each of the various jobs that employees can perform at the workplace. This information in this file includes the job code, the company, division and department in which it is performed, and rules governing worker performance and benefits for the particular job. The contents of a typical job code file, included in the code files 202, is summarized in Table 5 below.
TABLE 5
______________________________________
JOB CODE FILE
______________________________________
Company Portal Time in Minutes
Division Max Meals per Day
Department Max Hours to Search Back to a
Clock In
Job Code Union Code
Round Up Minutes
Rule ID
Round Down Minutes
Report Selections
Shift Start Times
______________________________________
The front end process 190 also has access to other files during clock processing not shown in FIG. 4, which are discussed in reference to FIGS. 9-21 below. Information from the time clocks 101 that is stored by the front end process 190 in the clock scan data structure is then periodically organized, e.g., daily, by a file server 204 and stored in either an Hours A data structure 206, an Hours B data structure 208, or an Hours C data structure 210. The Hours A, Hours B and Hours C data structures 206, 208, and 210 each contain accumulated information pertaining to the hours worked by each employee. The specific contents of these data structures is described in greater detail below. Each of the data structures 206, 208, and 210 are preferably ISAM organized, and each contain a file for each of the employees working in the workplace. The file server 204 updates the Hours data structures 206, 208, and 210 preferably on a continuous basis using the information contained within the clock scan data structure 192, the employee master data structure 196, the codes data structure 202, and the meals data structure 194. Source code implemented by the file server 204 performing the function of updating these files, as well as other functions, is included in the Microfiche Appendix and is entitled $ SYSTEM.TAGNDSRC.TASRV000. The Hours A data structure 206 contains a separate file for each of the hourly employees in the workplace. The information stored in a single employee's file in the Hours A data structure 206 is summarized in Table 6 below.
TABLE 6
______________________________________
HOURS A FILE
______________________________________
Company Department
Worked Date Job Code
Employee Number Base Rate
Name Pay Rules
Division
______________________________________
Referring to Table 6, the file for a particular employee in the Hours A data structure 206 contains information including the employee's name, employee ID number, the job code of the employee's job code, the pay rate and rules for this employee, and the department, division and company to which the employee is assigned. Further, the file also contains the date on which the employee last worked. The Hours B data structure 208 also contains a separate file or data record for each of the hourly employees in the workplace. The information stored in a single employee's file on data record in the Hours B data structure 208 is summarized in Table 7 below.
TABLE 7
______________________________________
HOURS B FILE
______________________________________
Company Worked Pay Rate
Worked Date Hours Worked
Employee Number Type of Pay
Worked Division Exception Codes
Worked Department Approval Codes
Worked Job Code Adjustment Code
______________________________________
Referring to Table 7, the Hours B data structure 208 for a single employee contains the company name, the employee ID number, the dates, divisions, departments, hours, and pay rates for the hours the employee has worked during the preceding pay period. Further, the Hours B data structure also contains the various approval, exception and adjustment codes that apply to this particular employee. The information for each employee contained within the Hours B data structure 208 is downloaded to a payroll system 220 on a regular basis, e.g., at the end of every pay period. The downloading of the contents of Data structure B 208 to the payroll system 220 is described in reference to FIG. 8 below. An Hours B data record for an employee is generated every time the employee works a shift, i.e., clocks into and subsequently out of work. Hence, on any given day, the Hours C data structure 210 also contains a separate file or data record for each of the hourly employees in the workplace. The information contained within a single employee's file in the Hours C data structure 210 is summarized in Table 8 below.
TABLE 8
______________________________________
HOURS C FILE
______________________________________
Company Clock In Supervisor
Worked Date Clock Out Time
Employee Clock Out Supervisor
Clock In Time No Badge Flag
______________________________________
Referring to Table 8, the Hours C data structure contains information about the shifts worked by the employee or the last day worked by the employee. This information includes the date upon which the employee last worked, when he clocked in and out, and who the supervisors were, and whether the employee clocked in or out without his ID badge 170 (FIGS. 3a and 3b). Since an employee may have worked more than one shift on the last day worked, multiple data records containing the information summarized in Table 8 may be created for a single employee. The information contained within the Hours A data structure 206, the Hours B data structure 208, and the Hours C data structure 210 is used to generate accounting and payroll records. Further, the timekeeping department 108, using the timekeeping computers 109 (FIG. 1), can access the information in the Hours data structures 206, 208, 210, as well as the employee master data structure 196 and the code files 202 via an interface process 212 to generate reports, answer inquiries, or update these files. When the timekeeping department 108 is generating a report, the interface process 212 accesses a parameter data structure 214 permitting the operator in the timekeeping department 108 to select the parameters of the report that he intends to generate. Generation of reports is described in greater detail in reference to FIG. 9 below. Also shown in FIG. 4 is an external human resources system 222. The human resources system 222 is a computer system which is also used to create and update files within an employee master data structure 196 and files within a codes data structure 202. Newly created or updated files are then downloaded into an interface or process 224 which uses the information contained in the data structures 196, 202 to update the employee master data structure 196 and the code data structure 202. Hence, in this preferred embodiment, the employee master data structure 196 and the code data structure 202 in the computer 104 can be updated either by the timekeeping department 108 via the personal computers 109 and the interface 212, or by the human resources department downloading files from the human resources system 222 to the interface 224 within the computer 104. FIG. 5 is an operational flow diagram illustrating the basic operation of the time and attendance system 100 when files in the code files structures 202, and the employee master data structure 196 are created and maintained by the timekeeping department 108. An authorized person within the timekeeping department 108, using the timekeeping computers 109, sets up and maintains these files and thereby performs tasks such as creating files for new employees in the employee master data structure 196 or creating new code files for new jobs, etc., in the codes data structure 202. A security data structure 230 contains security files for each authorized employee. The security data structure 230 is used by the computer 104 to deny access to employee master files 196 or to the code files 202 to unauthorized individuals. The contents of a typical file stored in the security data structure 230 is summarized in Table 9 below.
TABLE 9
______________________________________
SECURITY FILE
______________________________________
Company Screen ID
User ID Access Codes
User Initials
______________________________________
FIG. 6 is an operational flow diagram illustrating how the timekeeping department 108 updates information contained within the hours A data structure 206, the hours B data structure 208, and the hours C data structure 210 as well as the employee master data structure 196 using the personal computers 109. Access to these files is preferably limited to authorized personnel and the security file 230 (see, FIG. 5 and Table 9) is used to verify that only authorized personnel have access to these files. The timekeeping department 108 can access an employee's file in the employee master data structure 196 and change such things as, for example, his job title, pay rate and pay rules to reflect a promotion. As another example, if on one shift an employee clocks in to the time clock 101 at the beginning of his shift, but then fails to clock out at the end of his shift, the information in the hours B data structure 208 for this employee will not correctly reflect the number of hours that the employee has worked. Hence, the timekeeping department 108 can step in and update the hours data corresponding to this employee and correct the failure of the employee to log out using the timekeeping computers 109. Changes to either the employee master data structure 196 or the hours data structures 206, 208, 210 typically involve the timekeeping department entering the job code or various other codes to identify the change to be made. These codes are stored within the codes data structure 202 which is used to ensure that the codes entered by the timekeeping system 108 are valid codes. The employee master data structure 196 for each employee is set up when the employee is first hired and it is subsequently updated when the employment status of the employee changes. Changes in status can include a change in job description, a change in the department or division that the employee works for, a change in the hourly rate that the employee is being paid or the rules by which the employee is paid. As mentioned previously, updates to these files can also be made by downloading information from the external human resources system 222 via the interface 224 (FIG. 4). FIG. 7 is an operational flow diagram illustrating the interface between the time and attendance system 100 and the payroll system 220 (FIG. 4) when payroll data is downloaded from the hours B data structure 208 in response to commands from the timekeeping department 108 executed on the computers 109 and received by the interface 212. In this presently preferred embodiment, when downloading the data in the Hours B data structure 208, the time and attendance system 100 generates a computer tape 240 containing information about the number of hours worked by each employee, including hours which have been recorded as overtime hours, and pay rate. In this preferred embodiment, the computer tape 240 is then loaded into a payroll computer (not shown) which generates the payroll checks. Once the Hours B data structure 208 has been downloaded, the individual downloaded files are marked by the computer 104 as interfaced indicating that the employees have been paid for these hours. Of course, the time and attendance system 100 shown in FIG. 4 can be modified in an alternative embodiment so that the computer 104 will use the information contained in the Hours B data structure 208 to generate the payroll checks as opposed to an external payroll system. FIG. 8 is an operational flow diagram illustrating how the time and attendance system 100 generates printed reports for use by department managers and supervisors. These reports can be used, for example, to follow up and finalize an exception approved by a supervisor at a time clock 101, resolve disputes between a supervisor and an employee regarding hours or paycheck amounts, or to adjust an employee's hours. The reports are generated in response to the timekeeping department selecting parameters stored within the parameter files 214 (FIG. 4) via the personal computers 109 and the interface 212. The selected parameters are then used to search for the desired information in the Hours data structures 206, 208,210, the code files 202 and the employee master file 196 as well as other files (not shown), necessary to generate the selected report. One such report is a Clock Open/Close Report which lists all open and close activity at a designated time clock 101 including whether the time clock 101 (FIG. 4) was closed by a supervisor or closed automatically. In this preferred embodiment, the time clock 101 is programmed to automatically close, i.e., not accept any more data, after two minutes of no activity on the time clock 101. The Clock Open/Close report can be used to review either all activity on a selected time clock 101, or simply when the time clock 101 is automatically closed within a range of specific dates. Further, the report can be specific to either a particular supervisor, based on his identification number as encoded on his ID badge 170 or for an entire department which uses a particular time clock 101. The information used to generate this report is stored in a Supervisor Open/Close file 195 in the memory of the computer 104. This file is updated each time a time clock 101 is activated. The information contained within this file for each time clock 101 is summarized in Table 10 shown below.
TABLE 10
______________________________________
SUPERVISOR OPEN/CLOSE FILE
______________________________________
Date Open/Close Time
Division Supervisor Number
Department Record Type
(Open, Close, Autoclose)
Clock ID
______________________________________
Referring to Table 10, the Supervisor Open/Close File 195 keeps a daily record of when each time clock 101 is open and closed, which supervisor opened and closed the time clock 101, and whether the time clock 101 was automatically closed or was closed by the supervisor. The information stored within the file 195 is accessible to the timekeeping department 108 via the computers 109 and the interface 212. A report can also be generated by the computer 104 in response to appropriate parameters selected by the timekeeping department 108 from the parameters file 214 (FIG. 4) showing all of the employees who have used the NO BADGE button 144 (FIG. 2a) to either log in or log out during a set period of time, and the supervisors who have approved the log in or log out with the NO BADGE button 144. The information needed to generate this report is stored in the Hours C data structure 210 (see FIG. 4 and Table 8). This report can then be used to identify particular employees who are habitually forgetting their ID badges 170 as well as supervisors who are not sufficiently diligent in requiring employees to have their ID badges 170. As can be appreciated, the efficiency of logging persons into and out of the time and attendance system 100 is maximized when the employees log in and log out by using their ID badges 170. A report listing employees who have clocked-in or clocked-out outside of their normal time clock zone, as well as the supervisors who approved the zone exceptions can also be generated by the computer 104 in response to appropriate parameters selected by the timekeeping department from the parameters file 214 (FIG. 4). These reports can be generated for a selected date range, a selected Division, Department, or job, and for a specific time clock 101 and these reports can be used to determine employee and supervisor adherence to assigned zones and work areas. The employee's assigned work station is stored within the employee master file 196 (FIG. 4, Table 3), the locations where the employee worked is stored in the Hours B data structure 208 (FIG. 4, Table 7) and the supervisor who logged the employee into a specific work area is stored in the Hours C data structure 210 (FIG. 4, Table 8). Other reports, specific to particular employees or groups of employees, can also be generated by the computer 104 based on the parameters entered into the personal computers 109 by the timekeeping department 108. Specifically, reports showing the hours an employee worked on a given day, including the overtime hours, can be generated by accessing the information stored in the hours B data structure 208 (FIG. 4). Additionally, the computer 104 can also generate a report which prints out a copy of the information contained within the employee master data structure 196 (FIG. 4) for a particular employee. These aforementioned reports are generated by the computer 104 in response to the appropriate inputs from the time-keeping department 108 via the computer 109 (FIG. 1). Computer source code implemented on the computer 104 which generates these reports is included in the Microfiche Appendix attached herewith. III. TIME CLOCK OPERATION Generally referring to FIG. 4, the time clocks 101 of the presently preferred embodiment includes a microprocessor and two 32 k.times.8 bit Random Access Memories (RAMs) and are user programmable. These time clocks 101 are programmed to transmit information, such as the clock in and clock out times of the various employees and number of the supervisor opening and closing the time clock 101, to the computer 104 for storage in memory. Further, these time clocks 101 are also programmed to receive signals from the computer 104 requiring either the supervisor or the employee respond appropriately to specific questions via the time clock 101. The microprocessor of the time clock 101 is programmed in Interactive Reader Language, a language developed by Intermec and commercially available for its Model 9560 time clock. The programming for this preferred embodiment is described in greater detail below with reference to FIGS. 9 through 21. FIG. 9 is a top level flow diagram illustrating the operation of a time clock 101 as it interactively interfaces with the supervisor and employees while the employees are clocking into and out of work. From a start state 270, the time clock 101 proceeds to state 272 wherein the supervisor opens the time clock 101 by scanning his ID card 170 through the slot scanner 130 (FIG. 3). The time clock 101 then sends a signal to the front end process 190 (FIG. 4) in the computer 104 that the time clock 101 has been opened by this supervisor. Once the time clock 101 is opened, the supervisor or an employee depresses either the IN button 140 or the OUT button 142 (FIG. 2a) in state 272 to indicate whether they are clocking into work at the beginning of their shift or clocking out of work at the end of their shift. Once the IN button 140 or the OUT button 142 has been depressed in state 272, the employee then scans his ID badge 170 (FIGS. 3a and 3b) in state 276 or, if the employee does not have his ID badge 170, the supervisor manually enters the employee's number after depressing the NO BADGE button 144 (FIG. 2a). The time clock 101 then sends an appropriate signal to the front end process 190 identifying the employee and the time he scanned his card. The front end process 190 (FIG. 4) then stores this information in the employee's file in the Clock Scan data structure 192 (FIG. 4). After the employee has either clocked in or out in states 274 and 276, the supervisor then responds to exceptions pertaining to this employee in state 280. In state 280, the supervisor can assign the employee to work in a job other than the employee's normally assigned job, or work for a specific special event. In either case, the time clock 101 sends an appropriate signal to the front end process 190 resulting in the changed job assignment or assignment to a special event to be stored in an appropriate memory file. Further, in state 280, the computer 104 may determine that a specific exception applies to the employee, e.g., the employee is entitled to overtime for this shift requiring supervisor approval. In this case, the front end process 190 sends a signal to the time clock 101 causing it to display a message on the LCD display 126 (FIG. 2) requiring the supervisor or the employee to respond to the message using the buttons mounted on the face of the time clock 101. The response is then sent back to the computer 104 and stored in an appropriate memory file. From state 280, the time clock 101 moves to decision state 282 where the supervisor determines whether there are additional employee's waiting to clock in or out of the time clock 101. If there are additional employees, the supervisor or next employee depresses the IN button 140 or the OUT button 142 (FIG. 2a) in state 274. The time clock 101 then proceeds to loop through states 274, 276, 280 as previously described until there are no more employees to clock in or out in decision state 282. When there are no more employees to clock in or out, the supervisor closes the time clock 101, in state 284, by scanning his ID card 170 (FIGS. 3a and 3b) in the slot scanner 130 (FIG. 2). As described previously, in this embodiment the time clock 101 is also programmed to automatically close if there has been more than two minutes in which there has been no activity on the time clock 101. The supervisor is thus required to be present at the time clock 101 when the employees are clocking in and out permitting the supervisor to contemporaneously verify the clock in and clock out times of each of the employees. Further, the supervisor can also make new job assignments and approve exceptions, and have these new job assignments and exceptions automatically recorded in the memory of the computer 104 at the time when the assignment or exception is made. After the supervisor closes the time clock 101 in state 204, the time clock 101 proceeds to a return state 226. The operation of the time clock 101 illustrated in FIG. 9 will now be described in greater detail with reference to FIGS. 10-20 below. FIG. 10 is a flow diagram illustrating the time clock 101 performing the function of clocking in an employee. From a start state 270, called by the time clock from state 274 (FIG. 9), the time clock 101 displays, in state 302, the company name, e.g., The "Company Name", and the current date and time on the LCD display 126 (FIG. 2). The time clock 101 (FIG. 1) then proceeds, in state 304, to scan for a supervisor's ID card 170 (FIGS. 3a and 3b) opening the time clock 101. Once an individual has scanned or swiped his card 170 in state 304, the time clock 101 verifies, in decision state 306, whether the ID card is valid and authorized to open this particular time clock 101. This verification is made by the time clock 101 communicating to the front end process 190 of the computer 104 (FIG. 4) a code identifying the time clock 101, the identification number encoded in the bar code 186 of the individual's ID badge 170 (FIG. 3b) and a requesting the front end process 190 to verify whether this individual is authorized to open this particular time clock 101. Upon receipt of this communication, the front end process 190 verifies whether the individual is a supervisor authorized to open this particular time clock 101 by reviewing the file employee master data structure 196 (FIG. 4) for this particular supervisor. If the individual is not authorized to open the time clock 101, then the front end process 190 so signals the time clock 101 causing it to display the message "YOU ARE NOT AUTHORIZED TO OPEN THIS CLOCK" on the LCD display 126 (FIG. 2) in state 308. From state 308, the time clock 101 returns to state 306 where company name, date, and time are redisplayed. If the ID card 170 is found to be valid for opening the time clock 101 in decision state 306, the time clock 101 is then opened for employee processing permitting employees to clock in and out of work. Note, if at any time after a time clock 101 has been opened for processing, the CANCEL button 158 (FIG. 2a) is pressed, the time clock 101 returns to state 310. After the time clock 101 is opened for processing, the microprocessor (not shown) contained within time clock 101 initiates the previously described function where it detects whether there has been no activity on the time clock 101 for more than two minutes necessitating an automatic closing of the time clock 101. This function minimizes the problem of a supervisor opening a time clock 101 and then forgetting to close it thereby permitting employees to scan in or out at some later time when the supervisor was not at the time clock 101. Hence, the supervisor must be present during clock processing of the employees, which permits him to verify the clock in and clock out times for each employee as they occur. After the time clock 101 is opened, the employee or the supervisor is prompted, in state 310, to press either the IN button 140 or the OUT button 142 (FIG. 2a) to either clock in or out. Further, in state 310 other custom messages to the supervisor can be displayed on the LCD display 126 (FIG. 2). Custom messages are entered by the timekeeping department 108 via the timekeeping personal computers 109 (FIG. 1) and are stored in the supervisor's file in the employee master data structure 196 (FIG. 4). When the computer 104 is searching for the supervisor's file in the employee master data structure 196 in decision state 306, it also searches for any messages stored therein. In this way, messages to the supervisor, e.g., asking the supervisor to perform a specific task can be sent directly to the supervisor at the time clock 101. Note, the time clock 101 can also enter state 310 from a transition state 312, labelled B, which is described below in reference to FIGS. 15, 17 and 20 respectively. The supervisor then determines in decision state 282 whether all of the employees have been processed. If all the employees have been processed, the supervisor scans his ID badge 170 through the slot scanner 130 to close the time clock 101 in state 284 as previously described in reference to FIG. 9. After the time clock 101 has been closed in state 284, it returns to state 302 where the company name, time and date are displayed on the LCD display 126 (FIG. 2). If the supervisor determines, in decision state 282, that not all of the employees have been processed, either the next employee to clock in or the supervisor depresses the IN button 140 (FIG. 2a) in state 318 thereby initiating a flag, indicating that the time at which the next employee scans his ID card 170 is the time at which this employee is clocking in or beginning his shift. Once the IN button 140 is depressed, the time clock 101 displays, in state 320, the message "PRESS FUNCTION KEY OR SCAN EMPLOYEE BADGE" on the LCD display 126 (FIG. 2). Note, the time clock 101 can also move to state 320 from a transition state 322, labelled C, as discussed with reference to FIGS. 12, 13 and 14 below. The supervisor then determines, in decision state 324, whether this employee is changing from his usually assigned job to a new job necessitating the recording of a job change for the hours worked by this particular employee in the memory of the computer 104. If a job change is necessary, the supervisor depresses the JOB CHANGE button 152 (FIG. 2), in state 325, causing the time clock 101 to move to a transition state 326, labelled D, which is discussed with reference to FIG. 12 below. If a job change is not necessary, the supervisor then determines, in decision state 328, whether the work the employee will do on this shift is for a special event. If the work to be performed by this employee is for a special event, the supervisor depresses the SPECIAL EVENT button 154 (FIG. 2a) in state 331 causing the time clock 101 to move to a transition state 332, labelled E, which is discussed with reference to FIG. 13 below. If the work is not for a special event, the time clock 101 moves to a transition state 330, labelled F, which is discussed with reference to FIG. 14 below. FIG. 11 is a flow diagram illustrating the operation of the time clock 101 performing the function of clocking an employee out. This function is almost identical to the clock-in function described in FIG. 10 with the exception that in state 318 the OUT button 142 (FIG. 2a) is depressed thereby initiating a flag indicating that the time at which the next employee scans his ID card 170 is the time at which this employee is clocking out or ending his shift. FIG. 12 is a flow diagram of the function performed by the time clock 101 when the supervisor depresses the JOB CHANGE button 152 in state 324 (FIGS. 10 and 11). The Job Change function is used when the employee will be or has been working at a different job than his normally assigned job, thereby necessitating different accounting procedures or different pay for the employee. From transition state 326, labelled D (FIGS. 10 and 11), the time clock 101 moves to decision state 352 where a determination is made as to whether the time clock 101 has been allocated to a specific department or division of the workplace. This determination is made by sending a signal to the front end process 190, causing it to search a terminal clock file (not shown) to determine if the time clock 101 is allocated or nonallocated. As previously described, in this preferred embodiment, a time clock 101 can either be programmed to either be allocated or non-allocated. If the time clock 101 is non-allocated, the front end process 190 sends an appropriate signal in state 354 causing the time clock 101 to display, in state 356, the message "JOB CHANGE ACCEPTED. PLEASE SUBMIT FORM." on the LCD display 125 (FIG. 2). The supervisor is then informed he should fill out the appropriate form for the timekeeping department 108 (FIG. 1) so that they can update their records to account for this job change. As previously discussed, the file server 204 (FIG. 4) uses the information in the clock scan data structure 192 to periodically update the files in the Hours A data structure 206, the Hours B data structure 208, and the Hours C data structure 210. If the time clock 101 is non-allocated, the records in these data structures will not accurately reflect the job assignment to a different department or division. Thus, upon receipt of the appropriate form from the supervisor, the timekeeping department updates the information contained within the Hours B data structure 208 for this employee to reflect the correct department, division and job the employee performed on this work shift. From state 356 the time clock 101 moves to the transition state 322, labelled C, discussed previously in relation to FIGS. 10 and 11. If, however, the time clock 101 is allocated, then a signal is sent in state 358 by the front end process 190 causing the time clock 101 to display in state 360 the message "DO YOU WISH TO ENTER A JOB CODE>YES OR NO" on the LCD display 126 (FIG. 2). The supervisor then determines, in decision state 362, whether he wants to enter the job code corresponding to the job the employee will be performing. If the supervisor does not want to enter a job code, or does not know it, he depresses the NO button 160 (FIG. 2a) in state 364. From the state 364 the time clock 101 then proceeds to display in state 366, the message "JOB CHANGE ACCEPTED. PLEASE SUBMIT FORM." on the LCD display 126 (FIG. 2). The supervisor then knows that the job change has been accepted, but that he should inform the timekeeping department 108 (FIG. 1) of the job change so that they can update their records, including the hours data structures 206, 208, 210 (FIG. 4), accordingly. The time clock 101 then moves to the transition state 322, labelled C, discussed previously in relation to FIGS. 10 and 11. If, in decision state 362 the supervisor knows the appropriate job code, he then depresses the YES button 156 (FIG. 2a) in state 368. From state 368 the time clock 101 then displays, in state 370, the message "TYPE JOB CODE NUMBER. PRESS [ENTER]" on the LCD display 176 (FIG. 2). The supervisor then types the job code number of the new job in state 372 using the numerical buttons 146 and the enter button 150 (FIG. 2a). The time clock 101 then determines, in decision state 374, whether the job code entered is a valid job code number. This determination is made by sending the job code entered in state 372 to the front end process 190 of the computer 104 which validated the number by verifying that it is a valid job code stored in the codes files structure 202 (FIG. 6). If the job code entered in state 372 is invalid, the front end process 190 returns an invalid signal causing the time clock 101 to display, in state 376, the message "INVALID JOB CODE. PLEASE TRY AGAIN" on the LCD display 126 (FIG. 2). From state 376, the time clock 101 then returns to state 370 where the supervisor is again prompted to enter the new job code. If the front end process 190 determines in decision state 347 that the job code entered in state 372 is valid, it sends a signal to the time clock 101 causing the time clock 101 to display the name of the job e.g., chef or host, that corresponds to the job number entered by the supervisor, and asks the supervisor "CORRECT JOB ? YES OR NO" on the LCD display 176 (FIG. 2) in state 378. The supervisor then determines in state 380 whether the job title displayed in state 378 corresponds to the job he is assigning or has assigned to this particular employee. If the supervisor determines that the job title does not correspond to the job he is assigning or has assigned, he then depresses the NO button 160 (FIG. 2a) in state 381 causing the time clock 101 to return to state 370 where the supervisor is asked to re-enter the job code. If the supervisor determines, in decision state 380, that the job title corresponds to the job he is assigning or has assigned to this employee, he then depresses the YES button 156 (FIG. 2a) in state 382. The time clock 101 then displays, in state 384, the message "JOB CHANGE ACCEPTED" on the LCD display 126 (FIG. 2). Further, in state 384, the time clock 101 also signals the front end process 190 (FIG. 4) that the hours logged by this employee for this work shift shall be logged in the file for this employee in the clock scan file 192 (FIG. 4) as having been worked in the new job classification. Subsequently, the file server 204 uses the information in the clock scan data structure 192 to update the information in the Hours data structures 206, 208, and 210 (FIG. 4). The information for this particular employee working this particular shift in the Hours B data structure 208, then reflects that the employee worked the shift in a different job classification, possibly necessitating higher pay. Consequently, accounting changes and pay roll changes resulting from the job change are automatically made by the time and attendance system 100 as the employee is processed without requiring any additional paper work by either the supervisor or the timekeeping department 108. FIG. 13 is a flow diagram illustrating the operation of a time clock 101 as it performs the special events function called in state 331 (FIGS. 10 and 11). This function permits certain employees to be designated as working on a special event, e.g., an event for which a separate accounting record is desired such as a specific contract or project. From the transition state 332, labelled E, (FIG. 10 and 11) the time clock 101 proceeds to display, in state 402, the message "TYPE EVENT CODE #. THEN PRESS ENTER>" on the LCD display 126 (FIG. 2). The supervisor then types the special event code number using the numerical buttons 146 and the ENTER button 150 (FIG. 2a) in state 404, to identify the particular special event that the employee is working on. The validity of the number entered in state 404 is then checked in decision state 406. This determination is made by sending a signal to the front end process 190 causing it to compare the number entered in state 404 to numbers of special events stored in the codes data structure 202 (FIG. 4). If the special event number entered by the supervisor in state 404 is found by the front end process 190 to be invalid, the front-end process 190 sends a signal to the time clock 101 causing it to display, in state 408, the message "INVALID SPECIAL EVENT" on the LCD display 126 (FIG. 2). After displaying this message, the time clock returns to state 402 where the supervisor is prompted to re-enter the event code number. If a valid special event number has been entered by the supervisor in state 404, the front end process 190 then sends a valid signal, along with the name of the special event corresponding to the number entered in state 404, to the time clock 101 which in turn displays in state 410 the name of the special event and the prompt "CORRECT ? YES OR NO ? " on the LCD display 126. The name of the special event is retrieved by the front-end process 190 (FIG. 4) from the code data structure 202 (FIG. 6). This ensures that the supervisor is assigning the employees to the correct special event. The time clock 101 then moves to decision state 412 where the supervisor determines whether he has entered the correct special event in state 404. If the supervisor incorrectly entered the special event code in state 404, he then presses the NO button 160 in state 414 causing the time clock 101 to return to state 402 where the supervisor is prompted to retype the special event code number. If the supervisor entered the correct special event code number in state 404, he then presses the YES button 156 (FIG. 2a) in state 416. The time clock 101 then proceeds to display, in state 418, a message that the special event has been accepted by the supervisor as the correct event to assign the hours worked by this employee on the LCD display 126. In state 418, the time clock 101 also sends a signal to the front end process 190 (FIG. 4) to record the hours logged by this employee in the clock scan data structure 192 as having been worked for the special event corresponding to the number entered in state 404. As discussed previously, the file server 204 (FIG. 4) updates the Hours data structures 206, 208, and 210 as well as additional accounting records with the information in the clock scan data structure 192. Hence, the file server 204 updates files in the memory of the computer 104 containing accounting records for the a special event as including the work performed by this particular employee. From state 418, the time clock moves to the transition state 322 previously described with references to FIGS. 10 and 11. FIG. 14 illustrates the operation of the time clock 101 as it performs a badge/no badge function. This is the function performed by the time clock 101 when the employee is actually clocking in or out of work by either scanning his ID badge 170 (FIG. 3a and 3b) through the slot scanner 130 (FIG. 2) or by the supervisor manually entering the employee's ID number using the numerical buttons 146 (FIG. 2a). From the transition state 330, labelled F, described previously in reference to FIGS. 10 and 11, the time clock 101 moves to decision state 430 where it is determined whether the employee presently clocking in or out has an ID badge 170. If the employee has an ID badge 170, the employee slides it through the slot scanner 130 (FIG. 1) in state 432. Hence, in state 432, the bar code 167 of the badge 170 (FIG. 3b) is scanned by the slot scanner 130 (FIG. 2) of the time clock 101 causing the time clock 101 to record the current time. After the ID badge 170 has been scanned, determined in decision state 434, whether the scanned ID badge 170 is valid. This determination is made by sending a signal to the front end process 190 including the ID number encoded in the bar code 186 (FIG. 3b) of the employee's ID badge 170 which then compares this ID number, to numbers stored in the employee master data structure 196 (FIG. 4). If the ID badge 170 scanned in state 432 is valid, the front end process sends an appropriate signal to the time clock 101 causing the time clock 101 to signal the front end process 190 to store the time recorded in state 432 as the time the employee either clocked in or out. Whether the employee is clocking in or out is dependent upon which flag was initiated in state 318 when either IN button 140 or the OUT button 142 (FIG. 2a) was depressed. If the employee is clocking in (FIG. 10), then the current time is recorded in the file for this employee in the clock scans data structure 192 (FIG. 4) as the time the employee began his shift. If the employee is clocking out (FIG. 11), then the time at which the employee scanned his ID card 170 is recorded by the front-end process 190 in the employee's file in the clock scans data structure 192 as the time the employee clocked out or ended his shift. Once a clock-in and clock-out time is stored for a particular employee in the clock scan file 192, the file server 204 (FIG. 4) transfers the information for this employee in the clock scan data structure 192 into the files for this employee in the Hours data structures 206, 208 and 210. The time clock 101 then proceeds to transition state 436, labelled H, discussed with reference to FIG. 15 below. If ID badge 170 is invalid in state 434, i.e., the identification number encoded on the card 170 does not correspond to a current employee, the front end process 190 sends an appropriate signal to the time clock 101 causing it to then display the message "INVALID BADGE TRY NO BADGE", in state 438, on the LCD display screen 126 (FIG. 2). Preferably, the supervisor should then try to input the employee's identification number directly using the numerical buttons 146 (FIG. 2a). From state 438, the time clock 101 moves to a transition state 322, labelled C, discussed previously in reference to FIGS. 10 and 11. If, in decision state 430, the employee does not have an ID badge 170 that can be scanned into the time clock 101, the supervisor then depresses the NO BADGE button 144 (FIG. 2a) in state 440 causing the time clock 101 to then display on the LCD display 126 (FIG. 2) the message "TYPE EMPLOYEE NUMBER. PRESS [ENTER]," in state 442. The supervisor then types in the employee's ID number using the numerical buttons 146 and the enter button 150 (FIG. 2) in state 444. The time clock 101 then determines, in decision state 446, whether the number entered in the state 444 is a valid employee number by ensuring that the number entered in the state 494 has the correct number of digits and is in the correct sequence. If the employee number is invalid, then the time clock 101 displays in state 448 the message "INVALID EMPLOYEE NUMBER" on the LCD display 126 (FIG. 2). The time clock 101 then returns from state 448 back to state 442 where the supervisor is prompted to re-enter the employee's identification number. If, in decision state 446, the employee number is valid, the time clock 101 then proceeds to decision state 450 where it is determined whether there is a currently employed employee assigned to the ID number entered in state 444 in the memory of the computer 104. This determination is made, via the front end process 190, by searching the employee master data structure 196 (FIG. 4) for the employee corresponding to this ID number. If there is no corresponding employee, the front end process 190 sends a signal to the time clock 101 causing it to display the message "**UNKNOWN EMPLOYEE ** INVALID NO BADGE" on the LCD display 126 (FIG. 2) in state 452. From state 452 the time clock 101 then returns to state 442 where the supervisor is prompted again to enter the employee's number. If, in decision state 450, there is an employee on file corresponding to the ID number the front end process 190 sends a signal to the time clock 101 causing it to display the name of the employee having the employee number that the supervisor entered in state 444 as well as the message "CORRECT EMPLOYEE ? YES OR NO" on the LCD display 126 (FIG. 2) in state 454. The front end process 190 also sends a signal indicating the name of the corresponding employee found in the decision state 450 to the time clock 101. The supervisor then determines in decision state 456 whether the name of the employee displayed on the LCD display 126 in state 454 corresponds to the name of the employee who is currently at the time clock 101. If the displayed name is not the name of the employee, the supervisor presses the NO button 160 (FIG. 2a) in state 458 which returns the time clock 101 to state 442 where the supervisor is prompted to enter the employee ID number again. If the name displayed on the LCD display 126 corresponds to the name of the employee at the time clock 101, the supervisor then presses the YES button 156 on the time clock 101 (FIG. 2a) in state 460 causing the time clock 101 to move to the transition state 436, labelled H, which is discussed with reference to FIG. 15 below. Further in state 460, the time clock 101 sends a signal to the front end process 190 causing the front end process 190 to record the current time as the clock in or out time for this employee in the employee's file in the clock scan data structure 192. The signal also causes the front end process 190 to trigger the no badge flag (Table 1) in the employee's file in the clock scan data structure 197. As can be appreciated, the supervisor must be present at the time clock 101 when the employee is either logging into or out of their work shift. Hence, the supervisor is verifying the presence of the employee contemporaneously with the employee arriving and leaving their work station, thereby eliminating the need for the supervisor to later verify the accuracy of the timekeeping records. FIG. 15 is a flow diagram illustrating the operation of the time clock 101 as it executes a function which displays stored messages on the LCD display 126 (FIG. 2) about the employee whose ID number has been entered in either states 432 or 444. Further, this function also determines whether certain exceptions, requiring supervisor approval, apply to this particular employee. From the transition state 436, labelled H, (FIG. 14), the time clock 101 first determines if one of four status messages apply to the particular employee whose ID number was entered in either states 432 or 444. The timekeeping department 108 (FIG. 1) programs these status messages into the employee file in the employee master data structure 196 and the front-end process 190 (FIG. 4) checks this file in response to a signal generated by the time clock 101 indicating that the employee has either logged in or out in states 434 or 460 (FIG. 14). If a status message has been inserted into the employee's file in the employee master data structure 196 (FIG. 4) then the front end process 190 sends to the time clock 101. In this embodiment there are four possible status messages, the employee is on leave, the employee salaried, there is no corresponding employee on file, and the employee has been terminated. The time clock 101 then evaluates the signal provided by the front end process 190 in decision states 472, 476, 480 and 484 to determine which message to display on the LCD display 126. If the time clock 101 interprets the signal sent from the front end process 190 as indicating that there is no corresponding employee on file in decision state 472, the time clock 101 then displays a message indicating that there is no employee on file corresponding to the ID number entered in state 432 or 444 on the LCD display 126 in state 474. The time clock 101 displays this message for several seconds and then proceeds to decision state 488. If there is an employee on file in decision state 472, the time clock 101 then moves from decision state 472 to decision state 476. If, in decision state 476, the time clock 101 interprets the signal sent from the front end process 190 as indicating that the employee corresponding to the number entered in state 432 or 444 (FIG. 14) is on leave, the time clock 101 displays a message indicating that the employee is on leave on the LCD display 126 (FIG. 2) in state 478. The time clock 101 displays this message in state 478 for several seconds and then proceeds to decision state 488. If the employee is not on leave in decision state 476, the time clock proceeds to decision state 480. If, in decision state 480, the time clock 101 interprets the signal sent from the front end process 190 as indicating that the employee corresponding to the number entered in state 432 or 444 (FIG. 14) is salaried, the time clock 101 then displays a message indicating that the employee is salaried on the LCD display 126 in state 482. The time clock 101 continues to display this message in state 478 for several seconds and then proceeds to decision state 488. If the employee is not on salary in decision state 480, the time clock proceeds to decision state 484. If, in decision state 484, the time clock 101 interprets the signal send from the front end process 190 as indicating that the employee corresponding to the number entered in state 432 or 444 (FIG. 14) has been terminated, the time clock 101 then displays a message indicating that the employee has been terminated on the LCD display 126 in state 486. The time clock 101 continues to display this message in state 486 for several seconds and then proceeds to decision state 488. In this fashion, the supervisor can be told whether the employee who is logging into the time clock 101 is not on file, on leave, salaried or has been terminated at the time the employee is actually logging in. Hence, the supervisor is then aware of any important changes in status of employees while the employees are standing in front of him at the time clock 101. As can be appreciated, additional messages can also be programmed about particular employees, e.g., the employee is on probation etc., which are then displayed by the time clock 101 in a similar fashion as described above. If, in decision state 470, it is determined that no status messages apply to this particular employee, the time clock 101 then determines, in a decision state 488, whether the employee is attempting to clock out when he has not clocked in. If the OUT button 142 (FIG. 2a) was pressed in the state 318 (FIG. 11) without the IN button 140 having been previously depressed during the past pre-selected number of hours which, in this case is 17, then the employee's file in clock scan data structure 192 (FIG. 4) is incomplete as it lacks a clock in time. In decision state 488, the time clock signals to the front end process 190 to check if the employee's file in the clock scan data structure 192 has a clock in time. If the clock scan data structure 192 does not have a clock in time, then the time clock 101 moves to a transition state 490, labelled K, described below in reference to FIG. 16. The time clock 101 then moves from decision state 488 to decision state 492 where it is determined whether the employee corresponding to the identification number entered in either states 432 or 444 (FIG. 14) is authorized to work in the time clock zone corresponding to this particular time clock 101. This determination is made by reviewing the employee's file in the employee master data structure 196, via the front end process 190 (FIG. 4), to determine which time clock zone the employee is authorized to work in, and then comparing this zone to the zone corresponding to this particular time clock 101. If the employee is not authorized to work in this time clock zone, then the time clock 101 moves to a transition state 494, labelled M, discussed below with reference to FIG. 17. Note, the time clock 101 can also enter the decision state 492 from a transition state 496, labelled L, discussed below with reference to FIG. 16. If it is determined in the decision state 492 that the employee is authorized to work in the time clock zone, then the time clock 101 moves to decision state 498, where it is determined whether the employee is entitled to any overtime pay. This determination is preferably made by the front end process 190 reviewing the summary of earning data and the pay rules for this employee stored within the employee master data structure 196. The employee master data structure 196 is updated periodically, e.g., once a day by the timekeeping department 108, via the interface 212 (FIG. 4) to reflect the current work status of the employees. Typically, overtime is awarded for working more than a standard number of hours for a work shift, working more than a standard number of hours for a work week, or working on holidays. Further, overtime pay is typically higher than the employee's base pay, e.g., one and a half times the employee's typical hourly rate, however, the hourly rate paid for overtime rate may be increased to double or even triple the employee's hourly rate for given circumstances, e.g., working on a holiday etc. The payment of overtime is governed by the aforementioned work rules which may further require the supervisor to authorize the employee to work the overtime hours. If it is determined in decision state 498 that the employee is entitled to overtime and that supervisor approval is required, then the time clock 101 moves to a transition state 500, labelled M, discussed further in reference to FIG. 18 below. Note, the time clock 101 can also enter decision state 498 from a transition state 502, labelled N, discussed further in reference to FIG. 17 below. If, in decision state 498, the employee is not entitled to overtime, the time clock 101 proceeds to determine, in decision state 504, whether the employee is subject to being on an early out. At some workstations, the workload for a particular employee varies tremendously from day to day, some employees have to work long hours one day, but on the next day, their workload may not be sufficient to keep the employee busy. As a consequence, the employee's supervisor may wish to send the employee home prior to the scheduled end of the employee's shift. The time clock 101 determines in decision state 504, whether the employee (FIG. 14) who is logging out in state 318 (FIG. 11), is subject to being dismissed from work early. The time clock 101 makes this determination by sending a signal to the front end process 190 (FIG. 4) to check to see if the employee's file in the employee master data structure 196 lists the status of this employee as being an employee subject to being dismissed from work early. If the time clock 101 determines that he is subject to an early out, then the time clock 101 moves to a transition state 506, labelled Q, discussed further in reference to FIG. 19 below. Note, the time clock 101 can also enter decision state 504 from a transition state 508, labelled P, described further in reference to FIG. 18 below. If, in decision state 504, the time clock 101 determines that the employee is not subject to being dismissed from work early, the time clock 101 then proceeds to determine, in decision state 510, whether an exception requiring supervisor approval applies to the employee who is logging in or out in states 437 or 444 (FIG. 14). Exceptions requiring approval of the supervisor include approving the number of overtime hours an employee has worked, and approving the employee leaving work early. Additional exceptions can be programmed by the timekeeping department 109 or Information Systems 106 (FIG. 1). The time clock 101 determines if an exception applies by reviewing the employee master data structure 196 as well as the clock scans data structure 192 stored, via the front end process 190 (FIG. 4). If supervisor approval is required, the time clock 101 then moves to a transition state 512, labelled S, which is further described in reference to FIG. 20 below. Note, the time clock 101 can also enter decision state 510 from a transition state 514, labelled R, discussed with reference to FIG. 19 below. If, in decision state 510, supervisor approval is not required for this particular employee, the time clock 101 ascertains whether the employee is logging in or out in decision state 516. This determination is made based upon whether the IN button 140 or the OUT button 142 (FIG. 2a) was depressed in state 318 (FIGS. 10 and 11). If the employee is logging in, the time clock 101 moves to state 518 where it displays a message on the LCD display 126 (FIG. 2) welcoming the employee by name to work. The time clock in state 518 also scans the employee master file 196 corresponding to this employee, via the front end process 190 (FIG. 4), to determine if it is the employee's birthday or anniversary. If the current day happens to be a special day such as the employee's birthday or anniversary the time clock 101 then displays an appropriate message on the video display 126 (FIG. 2). The time clock 101 then proceeds from state 518 to the transition state 312, labelled B, discussed previously in reference to FIG. 10 above. If, the employee is logging out in decision state 516, then the time clock 101 moves to state 520 where it displays a message thanking this particular employee by name as well as displaying the number of hours the employee has worked since logging in on the LCD display 126 (FIG. 2). The number of hours the employee has worked is determined from the file the clock scan data structure 192 for this employee accessed by the front end process 190. From state 520, the time clock 101 moves to a transition state 312, labelled B, discussed previously in reference to FIG. 11 above. FIG. 16 illustrates the flow diagram of the time clock 101 as it executes the function called from decision state 488 (FIG. 15) where the time clock 101 determined that the employee logging out in either states 432 or 444 (FIG. 14) failed to log in. From the transition state 490, the time clock 101 determines in decision state 540, whether the employee has already logged hours, i.e., has a completed clock scan, for this particular clock day. This determination is made by sending a signal to the front end process 190 (FIG. 4) to search the clock scan data structure 192 to determine if the employee has previously logged hours on the current day. If the employee has previously worked on the current day, the front end process 190 sends a signal to the time clock 101 that hours have previously been worked on this particular day, as well as indication of the number of hours previously worked. The time clock 101 proceeds to display, in state 542, a message on the LCD display 126 (FIG. 2) indicating the number of hours that the employee has previously worked on this day and a prompt asking the supervisor to enter any additional hours the employee has worked on this day. The supervisor then types the additional hours the employee has worked in state 546. If there are no hours already recorded for this employee on this particular clock day, then the front end process 80 sends an appropriate signal to the time clock 101 causing it to display the message: "CLOCK-OUT. NO CLOCK-IN. TYPE HRS. THEN PRESS ENTER" on the LCD display 126 in state 540. This informs the supervisor that he should now manually enter the time that the employee has worked that day using the numerical buttons 146 and the enter button 150 (FIG. 2a) in state 546. Once the supervisor has depressed the enter button 150 in state 546, the time clock 101 proceeds to determine, in decision state 548, whether the hours entered by the supervisor in state 546 are valid. The hours are invalid if the supervisor has entered more than 24 hours, entered more than 2 digits of hours, or typed an invalid number using a non-numerical button in state 546. If an invalid number of hours was entered, then the time clock 101 returns to transition state 490 from which the time clock 101 permits the supervisor to re-enter the hours. If, in decision state 548, the number of hours entered by the supervisor in state 546 is valid, the time clock 101 then displays in state 550 the message "NOW TYPE MINUTES, THEN PRESS ENTER" on the LCD display 126 (FIG. 2). The supervisor then enters, in state 552, the number of minutes, after the last complete hour, that the employee has worked using the numerical buttons 146 and the enter button 150 (FIG. 2a). If the supervisor does not know the exact number of minutes the employee has worked, then the supervisor simply presses the enter button 150 in the state 552 in which case no minutes after the last full hour are recorded for this employee. From state 552, the time clock 101 proceeds to verify, in decision state 554, that the number of minutes entered by the supervisor in state 552 is a valid number of minutes. Invalid number of minutes occur when the supervisor has entered more than 59 minutes, more than two digits for minutes or has typed an invalid number using a non-numerical button. If the number of minutes entered by the supervisor in state 552 is invalid, the time clock 101 returns to state 550 where the supervisor is again prompted to enter the number of minutes the employee has worked. If, the number of minutes entered in state 552 is valid, the time clock 101 then proceeds to a transition state 496, labelled L, discussed previously in reference to FIG. 15. Once valid hours and minutes are entered by the supervisor in states 546 and 552, the time clock 10, sends a signal to the front end process 190 indicative the number of hours and minutes and the front end process proceeds to record them in the file for this employee in the clock scan data structure 192. The above-described function permits the supervisor to correct the problem of an employee failing to log in to the time clock 101 at the beginning of their shift when he has completed his workshift by entering the amount of time the employee has worked via the numerical buttons 146 (FIG. 2). Consequently, this function minimizes the need for additional paper work by either the supervisor or the employee to correct this failure to log in. FIG. 17 illustrates the flow diagram of the time clock 101 as it executes the function called from decision state 492 where it was determined that the employee is logging into a time clock 101 in a zone where the employee is not authorized to work. From the transition state 494, the time clock 101 displays, in state 560, a message that the supervisor must approve this p | ||||||
