Hello U29305,

A pre-submission validation error indicates there might be an issue on the SARS e@syFile database. The issue is not with the data imported from your Sage payroll, as the system would not have accepted the certificate import (passed).

Follow the steps below, and let us know if this resolved the issue: 

1. Access SARS e@syFile 
2. Select the Employer, and Period of Recon (202508)
3. Click Employee Admin
4. Select the impacted employee 
5. Click on the certificate at the top
6. Click Employee ETI
7. Click Save Certificate
8. Retry the submission to SARS

Your feedback will help others with the same issue.

Hi Francois,

I tried this on two employees (there were 32 of them) but as soon as I saved it it shows the certificate as incomplete.

When I tried to submit it gave me the following  Warning:

Please ensure that you complete the following mandatory fields before submitting the form. - Reason is a mandatory field - The ETI calculated reported on the Emp501 does not balance with the IRP5/IT3 (a) certificates.

Please rectify the ETI calculated on the EMP501 or applicable IRP5 /IT3(a) certificates

It has actually reduced my ETI value on the EMP501 which was correct to the value without the two certificates included.

How do i correct this now?

Delene Moolman
 

Hello U29305,

It seems as if the SARS database removes the ETI values (thus not balancing with you declared values).

The error message indicates it sees the midyear certificate as year-end certificate (even though you payroll provides ETI for 6 months only, it sees 12 months in the database

• One option is delete the payroll file you imported, and then to reimport it again - this will ensure the payroll data imported is correct
• Check you Declaration screen that the values for ETI balances on the reports from Payroll Professional (value of electronic certificates)
• If the issue persist, we recommend to get your Business Partner to investigate

Hi Francois,

Just to let you know I have finally managed to submit my EMP501.

I had to go into each one of the certificates with ETI, recapture the ETI of the certificate and save again for it to reflect “created- revised”

Only then did it go through.

Hello U29305 ,

Thank you for letting us know. It seems as if the records in the database corrupted somehow (the file import did not give any indication there was an issue), and seem the "recapture and save" fixed the record. Was the ETI values missing on the certificate, or did you just have to recapture the same information?

We have not seen this before, but will keep an eye out if other clients have the same experience.

No the values was not missing, I just had to recapture them.

Strange indeed.