Skip to main content

Errors and warnings

Guidance for resolving error or warning messages

Jessica McLean avatar
Written by Jessica McLean
Updated over 3 weeks ago

We want to make sure we're giving you as much support as possible to complete your pays successfully, so from time to time in PaySauce you may be alerted to an issue.

In PaySauce, we have warnings and errors.

Warnings are yellow messages that highlight something that may need your attention, but they won't prevent you from closing a pay.

Errors are red messages that require you to do something before you can close your pay.

Warnings and errors will both appear in the top of the pay preview window on the right hand side of your screen when you're using PaySauce on a computer.

Warning and error message

Warning message

These are yellow and let you know about something that could impact your pay. You can choose to ignore it or resolve the message if in fact there is an issue. It will not restrict you from closing your pay.

Examples of warnings that may appear:

  • A public holiday has not been accounted for in an employee's pay as expected based on their work pattern (either recorded as taken or worked)

  • An employee's pay rate is set below minimum wage

  • Bank account appears to be invalid

Error message

An error message is shown in red and tells you there's something that will cause an incorrect payment. You will not be able to close the pay until this issue is resolved.

Examples of errors that may appear:

  • Timesheets have been entered for a public holiday, so the correct entry for public holiday worked must be recorded for the employee on the leave view

  • Leave rate could not be determined for payout


Any employees you calculate with error messages unresolved will show in the 'Requires Attention' tab.

Requires attention


You will need to return the employee's pay to data entry by clicking on the return arrow (next to the employees name) to resolve the error.

Warning messages will also show in the finalise screen below the summary on the Banking tab.

Message summary

Company settings for errors and warnings

You have some settings that you can manage in relation to errors and warnings.

For unattended statutory holidays, you can set these to either give you warnings (won't prevent you closing a pay) or an error (will prevent you closing a pay unless addressed).

You can choose to set maximum daily hours for your employees in your company settings. If you have maximum daily hours set and these are exceeded, you will receive an error.

Resolving errors

Multiple transactions error

Duplicate transactions have occurred, and PaySauce Support must resolve this for you. Please send us a message so we can sort it out for you.

This generally occurs because there are multiple users on PaySauce at the same time, or you have multiple instances of PaySauce open. It can also occur if PaySauce has slowed down (for example, due to internet speed) and there was a delay in saving something.

You must apply leave

You'll see this message if your company setting for 'unattended statutory holiday' is set to error.

To resolve this, first check the actual day the warning is for. Check your employee's work pattern, and check the dates of the current pay period.

If the public holiday in the error message actually falls in the pay period prior to the one you are processing or the period after, it may be in relation to a conflict with the work pattern hours. Edit the employee's work pattern for this period to remove the hours from the day the error message refers to (applying the changes to the current pay run only).

You should also ensure that there is no timesheet submitted for the employee on the public holiday. If there is a timesheet entry for the day, remove it and record the public holiday worked from the leave view instead.

Rate could not be determined for leave payout

In every pay period, PaySauce calculates background transactions to keep a record of important leave calculations. This error may appear if the primary payment is not included in the pay run.

You can either resolve this by adding the primary payment back to the pay run (but changing the value to zero) or by going to the employee leave settings and changing the 'current rate' rule to 'Use Primary if set then Override' and set the override rate as the same as the employee's normal pay rate.



Did this answer your question?