This guide explains the Alerts you may see when running a Paylink, and what to do about each one.
For the full run-through process, see Paylink - Running a Paylink.
Common Paylink alerts
| Alert text | Icon | What it means | How to fix it |
|---|---|---|---|
| Base Data will be truncated | The Paylink has been set up to accept this data with a set number of characters, and some data in this field exceeds that, so it will be cut off and lost. | Go to Payroll > Paylink Configuration > Paylink Modules and select the payroll type from the dropdown. Click the field to amend, change the length, then click Update. | |
| There is more than one job and pay change in the period for employees | There is more than one job and pay record for an employee in the period selected. | Review the data. If you need both job and pay changes to come through the Paylink, run it twice, or more, by amending the date range. | |
| There are employees on this payroll who do not appear on the previous payroll but whose employee number does appear on the last payroll | This usually only appears during set up. | No action necessary. | |
| There are employees whose employee number exceeds the maximum length in this payroll | The employee number is set to a maximum length in the system, and some numbers exceed it. | Go to Payroll > Paylink Configuration > Numbering Schemes and amend the number of characters allowed. | |
| There are employees with a different pay frequency to that which is currently being run in this payroll | The pay frequency in the job and pay records of employees attached to a payroll must match, for example a monthly payroll must have a pay frequency of monthly for each employee. Affected employees are excluded from the Paylink report until this is corrected. | Click Details to find out which employee's job and pay record does not match, reset the Paylink, then amend the pay frequency on the record. | |
| Allowance started and ended in this payroll period | The date range chosen includes an allowance that started and then ended. | No action necessary. | |
| Column numbers are not consecutive. Missing column numbers will be submitted to payroll as blank columns | This could lead to the payroll import blanking data in the payroll. A gap has been created in the CSV columns when the Paylink was configured. | Review the numbering in Payroll > Paylink Configuration > Paylink Configuration and correct it so the column numbers are consecutive. | |
| The start date entered is before the end date of the previous run | The end date of the last Paylink run was later than the start date chosen for the current run. | No action necessary. | |
| There are employees on this payroll who were on a different payroll on their last run | This appears if an employee has been moved to a different payroll. | No action necessary if this is correct. Note: all data will be output, as this is new data for this payroll. | |
| There are Data Codes that have been used more than once in this payroll | A data code has been used for more than one field when the Paylink was set up. | From the reports area, run the Universal Pay Data Configuration report and check the data code column to find the fields sharing the same code. Then go to Payroll > Paylink Configuration > Paylink Modules, renumber one of the fields, then go to Paylink Configuration and reattach that field to the new number. Repeat for other payrolls if necessary. |
Footer
Comments
0 comments
Article is closed for comments.