EMP201 Submission Checklist
Check PAYE, UIF, SDL, payroll reports, payment timing, and support before submitting the monthly EMP201 employer declaration.
- EMP201 should be checked against the payroll run before submission, not treated as a separate SARS entry.
- PAYE, UIF, SDL where applicable, ETI where relevant, and payments should agree to current payroll support.
- SARS states that EMP201 and payment, if applicable, must be submitted within 7 days after month-end.
- A monthly checklist reduces the risk of EMP501 differences later because the return is supported while the payroll run is still current.
EMP201 submission is one of the clearest tests of payroll discipline. The business has already processed salaries, but the monthly employer declaration now asks whether the payroll figures, statutory deductions, and payment amount are reliable enough to submit to SARS.
The danger is treating EMP201 as a form completed after payroll instead of a control that sits inside the payroll month-end process. When the return is prepared from unsupported totals, the business may only discover the mismatch during EMP501 reconciliation, tax clearance pressure, or a later SARS query.
This checklist is for the monthly review before submission. It works with Payroll Services, Payroll Reconciliation Checklist, and the broader accounting handoff.
Quick Answer
Before submitting EMP201, the employer should confirm:
- the payroll run is final
- PAYE agrees to payroll support
- UIF agrees to payroll support
- SDL is included where applicable
- ETI is checked where relevant
- the payment amount and deadline are visible
- the accounting ledger can explain the liability
The submission should not depend on a number copied from one system without review.
Key Numbers
| Item | Number / threshold | Notes |
|---|---|---|
| EMP201 submission and payment | Within 7 days after month-end | SARS states this timing for EMP201 and payment, if applicable. |
| Weekend or public holiday timing | Last business day before | SARS notes this when the 7th falls on a weekend or public holiday. |
| Main payroll taxes on EMP201 | 3 | PAYE, UIF, and SDL where applicable. |
| Minimum monthly ties | 4 | Payroll report, EMP201, payment proof, and ledger liability. |
These are practical control points, not only compliance facts. They tell the team when the return should be ready and what it should agree to.
1. Freeze the payroll run before preparing EMP201
EMP201 should be prepared from a final payroll run. If starter changes, leaver payments, overtime, commission, leave without pay, or salary corrections are still moving, the return is not ready.
Check that:
- the final payroll summary has been approved
- payslip totals agree to the payroll summary
- late changes are listed as exceptions
- any off-cycle payment has been included or clearly separated
- the payroll period is correct
This step prevents the most common problem: submitting a return from a payroll file that changed after the return was prepared.
2. Tie PAYE, UIF, and SDL to payroll reports
The EMP201 values should tie back to payroll support. PAYE should not be a rough estimate. UIF should not be assumed from last month. SDL should not be ignored where it applies.
Review the monthly statutory summary and compare it to the EMP201 entry. The person approving the submission should be able to see the payroll report behind the numbers. If the amount has changed from the previous month, the file should explain why. Normal reasons include new employees, terminations, salary changes, bonuses, commission, overtime, unpaid leave, benefits, or corrected employee information.
If the explanation is not visible now, it will be harder to rebuild later.
3. Check ETI separately where relevant
Employment Tax Incentive claims, where relevant, should be reviewed before submission because they reduce the monthly employees' tax liability. The EMP201 completion process includes ETI fields, and employers should not treat those fields as a casual month-end adjustment.
The monthly file should show:
- which employees were considered
- which periods and remuneration values were used
- which amount was claimed
- whether any compliance issue blocks or affects the claim
If the business does not claim ETI, the file should still show that the field was considered and not simply missed.
Requirements Table
| Requirement | Why it matters | Owner |
|---|---|---|
| Approved payroll summary | Confirms the return is based on the final run | Payroll |
| Statutory deduction report | Supports PAYE, UIF, and SDL figures | Payroll |
| EMP201 draft | Shows the values before submission | Payroll or tax adviser |
| Payment proof or payment plan | Confirms the liability was dealt with on time | Finance |
| Ledger liability check | Keeps payroll and accounting aligned | Accounting |
The table is useful because EMP201 touches more than one person. Payroll calculates, finance pays, and accounting has to support the result later.
Numbered Checklist
- Approve the final payroll run and lock the period before preparing the EMP201.
- Compare PAYE, UIF, and SDL where applicable to the payroll statutory report.
- Review ETI separately where the employer intends to claim it.
- Confirm the submission deadline and payment timing before the 7-day window closes.
- Save the EMP201, payroll support, payment proof, and ledger journal in the same monthly file.
4. Confirm payment timing before the deadline
SARS states that the EMP201 and payment, if applicable, must be submitted within 7 days after the end of the month. If the 7th falls on a weekend or public holiday, SARS notes that submission and payment should happen by the last business day before that weekend or public holiday.
That timing means the payment process cannot be left for the final morning. The business should know who releases the payment, what bank approval is required, and where proof of payment will be stored.
When payment proof is missing from the payroll file, the return may be submitted but the accounting and reconciliation trail remains incomplete.
5. Keep the ledger aligned with the return
EMP201 does not live outside accounting. The payroll journal should create liability balances that explain what was declared and paid. If the ledger says one thing and the EMP201 says another, the business has created a reconciliation problem even if the return was submitted on time.
The accounting review should check:
- PAYE liability
- UIF liability
- SDL liability where applicable
- net salaries payable
- any ETI treatment
- payment allocation after submission
This is where Payroll Month-End Checklist and EMP201 review connect. One controls the payroll close. The other controls the monthly employer declaration.
6. Preserve the support while the month is still fresh
The monthly EMP201 file should be easy to open later. It should contain the payroll summary, statutory deduction report, EMP201 confirmation, payment proof, payroll journal, and notes on any exception.
That evidence is useful during EMP501 work because the reconciliation relies on monthly declarations, payments, and employee certificate information. A monthly file that explains each submission makes the later review less dependent on memory and more dependent on actual records.
7. Manager takeaway
The best EMP201 process is not dramatic. Payroll is approved, the statutory values are checked, the return is submitted on time, payment proof is saved, and the ledger agrees. That routine protects the employer from recurring monthly uncertainty and makes the later reconciliation season more manageable.
If the business cannot explain this month's EMP201 while the month is still current, it will be slower and more expensive to explain it later.
Related Resources
- Payroll Setup Checklist South Africa for the employer setup controls before payroll starts
- EMP501 and IRP5 Reconciliation Checklist for the later employer reconciliation cycle
- Payroll in Accounting for the ledger and reporting side of payroll