Why Are the Logs from the Approved Certificate of Attendance (COA) Not Reflecting in the Attendance Report?

 

As we all know, logs on Sprout HR come from either of the following sources:

1.  Logs from the biometric device (synced via fetcher or auto-push)

2. Logs from the Desktop Bundy

3. Logs from the Web Bundy (or Virtual Log In)

4. Logs from an approved Official Business (OB) application

5. Logs from an approved Certificate of Attendance (COA) application

 

If there is an approved Certificate of Attendance (COA) application but the logs indicated there are not reflecting in the attendance report, here are the possible reasons as to why this may be happening:

1. Are the logs from the approved COA within the threshold?

- If you're not familiar with this, you may read this article: How Do Pre-Shift & Post-Shift Thresholds Work?

- In case your logs are really beyond the set threshold, here's a guide you can refer to: Resolving logs beyond threshold by adjusting unrecognized logs in Payroll

2. Has there been a change in the Biometric ID of the affected employee?

- If the employee's Biometric ID at the time he filed the COA was, for instance, 1001, and his current Biometric ID as of now is already 1011, then the logs from the approved COA will not reflect. This is because of the fact that the approved COA logs were tagged on the original Biometric ID.
- To resolve this, the approved COA should be updated by either the manager or the admin so that the COA logs will be tagged to the new Biometric ID. (How to Edit an Approved Certificate of Attendance (COA) Application)

 

These are the possible reasons why the logs from an approved Certificate of Attendance aren't reflecting in the attendance report. For any further questions or concerns you may have regarding this, feel free to message us at [e-mail]. We look forward to hearing from you.