When employees clock in and out, Microsoft Dynamics AX checks the registration table for the most recent clock-in or clock-out registration. If the most recent registration is a clock-out, the application will clock in the employee; if the most recent registration is a clock-in, the application will clock out the employee.
In the process of calculating registrations, a supervisor may mistakenly register a clock-in or a clock-out with a future timestamp using by the missing clock-out feature. For related information, see About missing clock-out.
Suppose that on Tuesday, an employee's supervisor registers a clock-out time for Wednesday at 16:00 by using the missing clock-out feature. When that employee clocks in Wednesday morning at 08:00, the employee will get a clock-in message which is correct. But when the employee attempts to clock out at 16:05, Microsoft Dynamics AX will acknowledge the registration as a clock-in because the employee has a clock-out registration time of 16:00.
The employee clicks the same button when clocking in or out. Microsoft Dynamics AX will check for the newest similar registration. For example, if the newest registration was a clock-in, the application will register the next registration as a clock-out.
To prevent problems caused by these types of registrations, you can remove registrations with timestamps set for the future from the registration table.
Remove registrations with timestamps set for the future
You can make batch selections to execute this feature on a regular basis. For more information about batches, see Prepare batch processing on the Batch tab.