Skip to main content

Error: 'No allowance scale rate exists' for pay codes with an earlier transaction date

An employee can be held back from payroll with the exception message 'PAY CODE: XXXX NO ALLOWANCE SCALE RATE EXISTS'.

Written by James Pardy

An employee can be held back from payroll with the exception message 'PAY CODE: XXXX NO ALLOWANCE SCALE RATE EXISTS'. The employee's other hours aren't paid either, while other employees on the same pay code are paid as normal.


Why it happens

Payroll uses the date of each timesheet entry to look up the rate from the pay code's rate table. If an entry is dated before the rate's Date Effective, no rate exists for it. For example, a rate that starts on 1 September has no rate for hours dated in August.

Other causes are:

  • No allowance is set up for the employee for that pay code.

  • The first pay point on the scaled rates is set to a number greater than 1.

⚠️Important: An exception message surrounded by asterisks on the Validation report means the employee isn't being processed and won't be paid.


Fix the error

  • If the rate also applies to the earlier dates, change the Date Effective of the rate to an earlier date on each affected pay code:

    1. Go to Settings, then click Pay Codes.

    2. Select the pay code and edit the scale rate.

    3. Change the Date Effective to the earlier date.

    4. Re-run validation.

  • If the rate only applies from the later date, remove the earlier hours or enter them against the correct pay code for that period, then re-run validation.

  • If the cause is a missing allowance, record the allowance at employee level against the pay code, then re-run the Generate Salaries and Allowances job.

  • If the first pay point is greater than 1, enter the scale rate again with a pay point of 1, then re-run the job.


​

Did this answer your question?