ETI Checklist for South African Employers

ETI can reduce monthly employees' tax, but it should not be treated as a casual payroll discount.

The employer needs a monthly record showing which employees qualified, how the amount was calculated, and how the claim was included on EMP201.

Monthly ETI checklist

1. Confirm the employer is eligible to claim.
2. Review employee-level eligibility.
3. Confirm employment start dates and qualifying periods.
4. Check remuneration values for the month.
5. Calculate the ETI amount per qualifying employee.
6. Include the claim correctly on EMP201.
7. Save the employee-level schedule.
8. Reconcile ETI again during EMP501.

This supports EMP501 reconciliations and monthly payroll services.

Employee-level records

Keep a schedule that shows:

• employee name and ID/passport number
• tax number where available
• employment start date
• age or qualifying basis
• monthly remuneration
• qualifying month
• ETI amount claimed
• reason for exclusion where not claimed

The schedule should agree to payroll reports and EMP201.

EMP201 and EMP501 link

ETI is claimed monthly, but it is tested again when payroll is reconciled. If the employer cannot explain the monthly claims, EMP501 becomes slower and more exposed to validation errors.

This is why ETI should be part of the employer compliance checklist, not a separate spreadsheet that only one person understands.

Validation risk

SARS provides ETI validation guidance because incorrect data can block or reduce claims. Employers should review employee identifiers, certificate periods, remuneration, and claim months before submissions become urgent.

If a claim is reversed or corrected, keep the reason visible in the payroll file.

ETI control table

This table is useful because ETI is usually not tested only once. The employer makes a monthly decision, but the same decision can be questioned again at EMP501, during a SARS validation process, or when historical payroll data is reviewed.

Employer eligibility review

Start with the employer before checking each employee. ETI should not be claimed simply because an employee appears to be young enough. The employer must first be comfortable that the business is permitted to claim the incentive, that the payroll period is within the relevant rules, and that no obvious disqualifying issue exists.

The review should be documented in simple terms. Record who checked the ETI position, which payroll month was reviewed, and what data was used. This is especially useful where payroll is outsourced, because the business owner, payroll processor, and accountant may each assume the other party has checked the claim.

If the employer is behind on payroll compliance, the ETI review should be cautious. Late EMP201 submissions, unresolved PAYE balances, missing employee certificates, or weak payroll records can turn a useful incentive into a messy reconciliation issue. ETI should support compliance, not hide weak controls.

For growing SMEs, the cleanest process is to include ETI in the monthly payroll approval pack. The owner or finance lead should see the gross payroll, PAYE, UIF, SDL if applicable, ETI amount, net EMP201 amount, and the employee-level ETI schedule before the declaration is submitted.

Employee eligibility review

Employee-level support is the part that usually decides whether the claim can be defended. A payroll report that shows one total ETI value is not enough. The business should be able to explain which employees were included, which were excluded, and what changed from the prior month.

Check employee identity details first. If an ID number, passport number, date of birth, employment start date, or tax number is wrong, the claim may calculate incorrectly or fail validation later. Also check whether the employee was employed for the full month, started during the month, left during the month, or had unpaid time that affects remuneration.

Then review remuneration. ETI calculations depend on the monthly payroll value used for the employee. Bonuses, overtime, unpaid leave, deductions, commissions, or backdated adjustments can all change the number. If payroll values are changed after EMP201 submission, keep a note showing whether ETI was reviewed again.

Where an employee does not qualify, do not just leave the line blank. Record the exclusion reason. Examples include age, remuneration, employment date, missing information, or the fact that the employee has already reached the relevant claim period. Exclusion notes make the schedule more useful when a reviewer compares several months.

EMP201 approval workflow

Before EMP201 is submitted, the ETI schedule should be checked against the final payroll. The payroll processor should not calculate ETI from a draft payroll and then submit the final EMP201 after salary changes are made. That is how differences creep in.

A practical approval pack includes the final payroll summary, employee-level ETI schedule, PAYE calculation, UIF and SDL values, and the EMP201 amount to be declared. The reviewer should confirm that the ETI claim has been deducted correctly and that the resulting PAYE amount still agrees to the payroll records.

The payment step also matters. ETI reduces the amount payable to SARS, but it does not remove the need for clean proof of submission and payment. Keep the EMP201, payment proof, SARS statement where available, and ETI schedule in the same monthly folder. When the file is organised this way, EMP501 is much easier because each month has already been tied back to its evidence.

If an error is found after submission, decide whether it needs correction in the current cycle, a later adjustment, or further payroll advice. Do not overwrite the original ETI schedule without saving the correction trail. The correction trail should show what changed, who approved it, and how the adjustment was reflected in SARS or payroll records.

EMP501 reconciliation checks

ETI should be reviewed again before EMP501 is finalised. The monthly claim schedule should agree to the certificate data and payroll reconciliation reports. If monthly schedules are missing, the team may need to rebuild the claim from employee master data, payslips, payroll journals, and EMP201 submissions.

This is also the point where validation errors become visible. Employee identifiers, employment dates, certificate periods, remuneration values, and ETI amounts must align. A claim that seemed acceptable in one month can create a year-end problem if the employee record is incomplete or if a payroll adjustment was handled outside the normal process.

For stronger control, create a year-to-date ETI summary before EMP501 starts. The summary should show ETI claimed per month, number of employees claimed, total claim value, changes from prior months, and any reversals or corrections. This gives the reviewer a quick way to spot unusual movements before the reconciliation file is submitted.

Common ETI mistakes

The first common mistake is claiming from incomplete onboarding data. If employee details are still being collected, the employer should be careful about submitting a claim that depends on those details. It is better to delay or document the basis than to create a validation problem later.

The second mistake is treating ETI as a set-and-forget payroll setting. Employee eligibility changes over time. Remuneration changes, qualifying months run out, employees leave, and corrections are made. ETI should be recalculated from current payroll information each month.

The third mistake is leaving ETI outside the accounting records. The EMP201 payment, payroll journal, and SARS liability should still make sense after the incentive is applied. If the accounting team only sees the payment amount and not the ETI schedule, PAYE balances can become harder to reconcile.

The fourth mistake is waiting for EMP501 to review the claim. By then, the team may be working across many months of records. A small monthly schedule is much easier to maintain than a full year reconstruction.

Practical takeaway

ETI is useful only when the claim is traceable. A monthly employee-level schedule is the simplest way to keep the incentive defensible.