This “Future Date” issue will be occurred if the system never poll transaction data from the controller for a long time.

For Example:

If the user poll the transactions on 01.06.2021, but the previous polling date is on 01.07.2020. In this case, E.Win will poll and process all the offline transactions from the controller, from 01.07.2020 till 01.06.2021.

The system will be confused and recognize the downloaded transactions (From 01.07.2020 till 31.12.2020) as year 2021 data.

Hence, the user will obtained “Future Date” from 01.07.2021 till 31.12.2021, since the current date is just 01.06.2021.

The easiest way to fix this messy transaction database is to use Raw2Tran.Exe (Download Here).

By referring to the previous example, the steps are as below:

1. Move out all those TR20*,TR21* files to a temp folder.

2. Separate the *.raw file according to the contents of the files – 2020 folder / 2021 folder

3. Use Raw2Tran.Exe to recover *.raw with 2020 trans from 2020 folder

4. Use Raw2Tran.Exe to recover *.raw with 2021 trans from 2021 folder

5. Now, you have a clean/correct TR20* / TR21* files.

If Chronos TMS is integrated with E.Win, then the Time Attendance Data also have “Future Date” issue.

Please kindly refer to the link for Chronos solution: Chronos TMS(Chronos TMS)

In order to prevent this “Future Date” issue, The user just need to make sure transactions are polled at least once a month.