This error indicates that there is an incorrect data in a field in the batch. It will often give you more information in the brackets below. This is a clue to the problem and where it might be.
Incorrect Transactions
e.g. The value specified for an item does not match the item type (value = "-158.4", item type = Decimal, uniqueID = http://www.sbr.gov.au/ato/payevntemp:EmployerContributionsYearToDateA)
You can see in this example that it shows a negative value and then mentions the Employer Contribution YTD field.
Download the Income Statement report from the batch and check the field/column to find the negative value. Negative values should always be entered in the year they relate to and where there is a positive amount to offset against. If it relates to a previous year then it needs to be entered in that year. The negative entry would need to be reversed out of the current year and entered in the prior financial year.
See: Reverse a processed pay.
Masterfile Issues
Other errors may relate to values in the employee Masterfile. From Single Touch Payroll, you can use the Employee Details page of the Income Statement Report to find these.
An example of this error in relation to a Masterfile issue:
The value specified for an item does not match the item type (value ="His legal name is Johnny in Australia. He has no surname.*, item type=String, uniqueID = http:/www.sbr.gov.au/ato/payevntemp:FamilyNameT) Hint: The actual length is greater than the MaxLength value.
In this example, the person that was getting the error did not have a surname, so the error was occurring because the Family Name field was blank. The ATO requires a surname to be entered. To resolve this particular error:
In Attaché Payroll, go to Payroll, Masterfiles, Employee Details, Maintain.
From the Details tab, move the name from the First Name field to the Surname.
Click Accept (F9) to save the changes.
In Single Touch Payroll, go to the erroring STP batch.
Click Options, Refresh Batch, and Run update. This will sync the updated information through to the batch after you've updated the employee Masterfile and should resolve the error.