Skip to content
English
Submit a Ticket Customer portal Sign in
Home
  • There are no suggestions because the search field is empty.

What do the error codes mean when clock events don't get sent into Yourpayroll?

This article addresses what the error codes mean when using any yourpayroll product, and how to resolve them

 

Error

Code

Meaning

Resolution

400

An attempt is being made to clock in/out for a shift when a later shift has already been started. This is usually caused by a shift being completed in Employment Hero Payroll manually or a timesheet being created in Employment Hero Payroll manually (before this event was sent through to Employment Hero Payroll).

Verify that the shift has been properly recorded in the employee’s timesheet.

Assuming it has, the error can be ignored. You can also (optionally) delete the event in NoahFace.

403

User does not have permission to clock on/off. This is usually caused by an employee not being granted kiosk access.

Grant kiosk access to the user in Employment Hero Payroll, then retry the Notification.

404

The business or the kiosk was not found in Employment Hero Payroll. This is usually caused by either:

  1. Incorrect configuration
  2. Manually deleting kiosks in Employment Hero Payroll.

Verify that the business name in Employment Hero Payroll matches the business name in NoahFace exactly.

Edit and re-save your Notifications in NoahFace so that they are re-created in Employment Hero Payroll.

500

Attempting to send an event to Employment Hero Payroll for a user that was not synchronised from Employment Hero Payroll (usually a user than was manually created in NoahFace).

Either:

  1. Delete the user that was created manually in NoahFace, synchronise the user from Employment Hero Payroll, and have the user re-register.
    1. Have this user clock in/out on a dedicated iPad that is used only by non-Employment Hero Payroll users

1001

Tried to send a clock out event to Employment Hero Payroll but the user is not currently clocked in.

There are two possiblee causes:

  1. The user forgot to clock in at the start of their shift and then tried to clock out at the end of their shift
  2. The user clocked out twice

The resolution depends on the cause:

  1. Manually create the timesheet for the day in Employment Hero Payroll
  2. Ignore the error

In both cases, you can optionally delete the event in NoahFace

1002

The mapped location value was invalid for that user. This is usually caused by incorrect configuration.

Verify the names of the locations in Employment Hero Payroll match the details of the event, then retry the Notification

1003

The mapped work type value was invalid for that user. This is usually caused by incorrect configuration.

Verify the names of the work types in Employment Hero Payroll match the details of the event, then retry the Notification

1004

Tried to send a clock in or clock out event to Employment Hero Payroll when the user is already clocked into Employment Hero Payroll at a later time.
This is caused by two different
sources of events for a user (eg:
NoahFace + WorkZone), when the
event has been delayed (eg: if an
access point is temporarily offline
due to a network issue).

NoahFace will automatically retry this
event when the user has clocked out.
This will either succeed or it will fail
with a different error. You can therefore
ignore these errors.