EMP501 Interim Reconciliation 2026: Deadlines and Checks

The interim EMP501 is the mid-year check that your monthly EMP201s, the money that left the bank, and the IRP5 / IT3(a) certificates all tell the same story. It is not a formality you squeeze in after October payroll.

SARS lists the 2026 interim window as 21 September to 31 October 2026. The return covers 1 March 2026 to 31 August 2026. If you run payroll for a company of 50 to 250 employees, this is your filing. It is not a year-end problem you can leave until May.

This is for the FD, HR lead, or ops owner who has to sign off that the file is clean. The next EMP201 (August payroll) is due Monday 7 September 2026. The listed interim window opens two weeks later. You have work to do before then.

EMP501 vs EMP201, in plain language

The EMP201 is the monthly employer declaration. You tell SARS what PAYE, UIF, and SDL you deducted for that month, and you pay it. Submission and payment sit inside seven days after month-end. If the 7th is a weekend or a public holiday, the deadline is the last business day before the 7th, not the next working day.

The EMP501 is the reconciliation. Twice a year you add up those monthly declarations, match them to the payments SARS allocated, and support the totals with a certificate for every person who was paid in the period. IRP5 for employees. IT3(a) for contractors you remunerated.

Monthly is the running total. Interim and annual are the audit of that running total.

If the monthly file is sloppy, the EMP501 does not fix it. It exposes it. The errors that trigger SARS trouble on the EMP201 (wrong period, uncleared payment, figures that do not tie back to the payroll journal) are the same errors that stall the recon. We unpacked those in EMP201 errors that trigger SARS penalties.

What the interim 2026 return actually covers

Period: 1 March 2026 to 31 August 2026. That is the first six months of the 2026/2027 tax year.

SARS Business Requirements Specification (BRS) dates for this cycle:

Return	Period	Listed window
Interim EMP501	1 March 2026 to 31 August 2026	21 September to 31 October 2026
Annual EMP501	Full year to 28 February 2027	1 April to 31 May 2027

SARS caveats those windows. Final dates depend on readiness. Confirm the live window when September arrives. Do not treat a blog date as a substitute for the SARS notice.

What you are reconciling:

Six EMP201s (March through August)
Six payments against those EMP201s
An IRP5 or IT3(a) for every person paid in that window, including people who left

Interim certificates go to SARS only. They do not go to employees. If someone in HR is planning to email "interim IRP5s" in October, stop that. Staff do not receive an interim certificate.

If the six months do not balance, SARS attributes the shortfall to the last month of the period. For this interim, that is August 2026. A quiet under-declaration in May does not stay in May. It lands on August and sits there until you unwind it.

The annual return later covers the full year to 28 February 2027. Get the interim right and May is a continuation, not a reconstruction. The rest of the year's payroll dates sit on the SA payroll compliance calendar 2026/2027.

The three-way balance

Three totals have to agree:

The sum of the EMP201s for March to August
The sum of the payments SARS allocated to those months
The sum of the IRP5 / IT3(a) certificates for the same period

If any one of those is off, the return is not ready. Do not file and correct later. Later is how a six-month problem becomes a twelve-month problem.

The breaks we see before a file is ready are ordinary, not exotic:

An EMP201 was submitted for the right amount, but the payment reference pointed at another month
A leaver sat on the March to June EMP201s and is missing from the certificate file
A contractor was paid (or should have been declared) and has no IT3(a)
UIF was calculated without the ceiling. The current ceiling is R17,712 per month. If you ignored it for six months, the certificates will not match the EMP201s

Declared is not the same as paid and allocated. A payment that cleared after the EMP201 deadline, or that used the wrong period reference, leaves a month looking unpaid even when the cash left your account. Reconcile bank, EMP201, and the SARS allocation for each of the six months before you build certificates.

e@syFile for 50 or more employees

If you have 50 or more employees, this return is an e@syFile Employer (Thin Client) job. eFiling on its own is not the channel for a 50 to 250 headcount file.

That means, in practice:

The current e@syFile Employer / Thin Client build is installed and tested before 21 September
You have a payroll extract that e@syFile will accept, not a spreadsheet you hope to retype
You have time inside the window to validate, reject, and resubmit

Do not leave the install for the week the window opens. That is how you spend 21 to 25 September fighting a client update instead of the recon.

The mistakes that blow the interim

Four errors stop a 2026 interim in its tracks.

Wrong tax year figures. The 2026/2027 tax year started on 1 March. If any of the six months still used last year's PAYE tables, rebates, or medical credits, those EMP201s are already wrong. The interim will not average that out. Fix the months before you build certificates. The figures that should have been in the system from March are in 2026/2027 tax year payroll changes.

Missing income tax reference numbers. From the 2026 reconciliation, SARS will not accept an EMP501 that is missing the required income tax reference numbers. That is a hard reject, not a warning you can park until May. If an employee or contractor has no IT number on file, start that chase now. How to obtain a number is a separate process. Do not hold the whole recon while you read a TRN guide. Get the list of blanks out this week.

EMP201 and payment mismatch. The declaration and the payment have to land on the same month. A late clearance or a wrong period reference leaves SARS showing an outstanding month. The certificate file can be clean and the recon still fails because the payment ledger does not match the EMP201s. Line up all six months before you import.

Issuing interim certificates to staff. Interim IRP5 / IT3(a) certificates are for SARS. They are not employee documents. Sending them out creates version confusion (staff keep an interim file and later see a different annual one) and it is not what the recon asks you to do.

What to do in the next four weeks

Today is Saturday 15 August 2026. The listed window opens on 21 September. Use the next four weeks as prep, not as slack.

This week and next (to 28 August). Lock August payroll on 2026/2027 figures. Pull a list of every person paid since 1 March, including leavers and contractors. Mark every missing income tax reference number. Confirm UIF is using the R17,712 monthly ceiling.

Week of 1 September. File the August EMP201 and make the payment in time for Monday 7 September 2026. Then sit with the six EMP201s and the six payments. Note every variance. Do not wait for e@syFile to tell you.

Week of 8 September. Build the draft IRP5 / IT3(a) file. Run the three-way balance. If there is a shortfall, expect it to be attributed to August. Decide how you will correct it before you import.

Week of 15 September. Confirm e@syFile Employer is current. Import a test file. Fix rejects. On 21 September you should be filing, not starting.

Inside the window you still have the September payroll EMP201 on Wednesday 7 October 2026. That return is not part of the interim period (the interim ends 31 August), but it sits in the same stretch as your EMP501 deadline. Do not let one crowd out the other.

A late EMP501 attracts 1% of annual PAYE per month, capped at 10%. On a 50 to 250 payroll that is not a rounding error. File inside the window.

How a managed payroll run handles this

On a managed PaySpace (Deel Local Payroll) run, the interim is not a separate project. Monthly EMP201s are already tied to the payroll journal and the payment. Certificates are generated from the same record. The recon is a check of work you have already done, not a reconstruction from six folders of spreadsheets.

What that looks like in practice:

Tax year updates sit in the platform before March payroll, so you are not discovering wrong tables in September
EMP201, payment, and certificate data come off one system
e@syFile submission is a scheduled step, not an after-hours install
Missing IT numbers are flagged as a data issue during the year, not in week one of the window

Talentide's payroll service runs that process for 50 to 250 employee teams. If your current setup only holds together while one person is in the office, the interim is where it shows. If you want a straight read on whether your file will balance, talk to us.

Key takeaways

Interim EMP501 covers 1 March 2026 to 31 August 2026. SARS BRS window: 21 September to 31 October 2026. Confirm the live dates when it opens.
Annual EMP501 (year to 28 February 2027): 1 April to 31 May 2027.
EMP201 is the monthly declaration and payment. EMP501 is the reconciliation of those months against payments and certificates.
EMP201s, payments, and IRP5 / IT3(a) totals must three-way balance.
Shortfalls are attributed to the last month of the period. For this interim, that is August 2026.
Employers with 50 or more employees file through e@syFile Employer / Thin Client, not eFiling alone.
From the 2026 recon, an EMP501 without the required income tax reference numbers is not accepted.
Interim certificates go to SARS only, not to employees.
Next EMP201: August payroll due Monday 7 September 2026. September payroll EMP201: Wednesday 7 October 2026.
Late EMP501: 1% of annual PAYE per month, capped at 10%.

EMP501 Interim Reconciliation 2026: What to File Before 31 October