If the employee sees this message on the terminal, the punches have been received by the platform but are not associated with the corresponding shift.

The error occurs because:

• Badge mismatch between punches and shift (e.g., missing leading zero or different formatting)
• The user associated with the punch import has been deleted/terminated/blocked

Badge mismatch

The Administrator user should perform the following checks: 

1. Check the punches that were not associated: go to Attendance > Punches > in the "Last name and first name" field, enter the comparison operator = is empty
2. Reopen the days up to the first day of the shift. See Reopen and close again one or more already processed or closed days
3. Go to Attendance > Shifts > enter the correct badge number > Save
4. Click Actions > Associate punches to badge

5. Reprocess the reopened days so that the punches are correctly linked to the shift/employee

    

The user associated with the punch import has been deleted/terminated/blocked 

The Administrator user should perform the following checks: 

1. Go to Reports > Report list > search for "API: Access log"

2. If the report shows errors such as:

   The lookup view Lookup Badge DipendenteID did not produce any results

   The field Punches.DipendenteID will be set to null

   In most cases, the user used for the import has been blocked/terminated/deleted.

How to fix (change the import user)

1. Go to Settings > Imports

2. Select the import template used for punches

3. Save the template with a different active Admin account than the one that was blocked/terminated/deleted

4. Relaunch the import: go to Other > Data import > select the failed import 

5. Actions > Run again from backup

6. Check again the "API: Access log" report: the errors should no longer appear

Tip: use a dedicated technical account (service account) for integrations to avoid issues in case of turnover.