Papdis Error Messages
The Papdis process assumes your payroll application can assess your employees and then calculate their pension contributions. Once this is complete, you need to export a compatible file, known as a pre-assessed file or a pre-calculated file, using the Papdis 1.0 standard. This page describes some of the errors that you might face if you have exported a file that is not accepted first time.
Before uploading a file, please make sure that all the columns in your file exactly match the example file on here payroll support.
Having uploaded a file, each file is given a state. The state is a quick way to see if the file imported correctly or not. You can view the details of the import or download the file again. Below are the meanings of each state.
Should all details in the file be correctly imported then the state of the file will be 'Success'. Well done you! If your file includes contributions, you can see successfully imported contributions in the Pending Contributions table in the Payroll section.
If some of the details were imported correctly but others failed the state of the file will be shown as 'Partial success'. For example, this can happen if the employee details were located and updated correctly, but there was a problem with their contribution information. We treat both actions separately for each member meaning this update was partially successful. You can edit the file to correct the issue and then upload it again. This will be treated as a new file and you can see if it is then successful.
If the contents of the file could not be imported the file state will be marked as 'Fail'. Click the view button to see the reported errors. If we couldn't provide an error it is likely the file format is not correct. We can only provide errors for files we can read.
This page describes what may be wrong if the state of your file is Fail.
1. Locating your EmployerID
The Papdis file needs to include your unique EmployerID. This ID is called the Company Slug and can be found in your account under Company Details.
Click here to find your ID: Company Details > Update Company > Company Slug
EmployerID Column C
Company Slug in Company Details
2. Are all required fields filled out correctly?
All rows need to have the same number of fields completed. Certain columns are mandatory so you must make sure that all required fields are completed.
In this example the group field (which is a required field) has been added to the first two rows, but left out on the last row (D4). The same logic applies to the other fields like dates, or contributions, double check your file for any missing fields. Check you have completed each one correctly using the example file on our payroll support page.
Missing fields = D4
No missing fields
3. Are there too many rows in your file?
Much like the point above, having too many fields is also a problem. This example is an obvious one, it makes sense that you might want to double check your contribution total before uploading it and therefore SUM the column first.
If you do this you create a new row and then when we import the file we can't find the other relevant columns for this row and the file is rejected. Remove the extra cell and the file will upload correctly.
Too Many rows = AK5
No missing fields
4. Are you using a correct pay period?
We accept a variety of pay periods and frequencies. Be it a tax month or a calendar month, or weekly or bi-annual pay we don't mind. All we care about is that there are no missing pay periods and importantly you are using the same calendar as us.
As the poem goes; thirty days hath September, April, June and November. All the rest… Get this bit wrong and the file wil be rejected!
This kind of error can happen if your pay runs are near identical so you upload last months file with a few minor changes but forget that the current month has more or fewer days in it.
Invalid Month = G4
Quick check list
Check the list below and make sure your file includes these details or is formatted to suit.
- File type: We support CSV or XML only. If your file is a PDF, XLS or DOC etc it will not be imported and the state of the file will be Fail.
- Headers: Ensure you have copied the header names exactly. Click here to download a sample file to copy the header names.
- Date format: Check you are using one of these date formats YYYY/MM/DD 2016/12/30 or YYYY-MM-DD 2016-12-30.
- PensionProviderId. Always use: smartpension (lowercase). This is a static field and you should be able to add it as a description field in your payroll software.
- EmployerId. This is your Smart Pension Company ID. You can find this number by looking in your account under Company Details > Update Company > Company Slug.
- Group This is a required field. You can create different contribution groups (managers, sales etc) within your Smart Pension account, add the group name per employee to this field. If you don't want to use groups then just add the word default (lowercase) to this field for each employee.
- EmployeeId. This is your internal reference for your employees. Typically this is your payroll reference. This has to be unique to avoid creating duplicate records. If you have existing employees set up in your Smart Pension account, update their employee profile with your payroll reference before you upload your Papdis file.
- AssessmentCode & EventCode. These are numeric values that are produced by your payroll application. If your payroll application does not provide these codes we can accept the equivilant word. i.e. 1 could also be Eligible Jobholder.