SARS interim EMP501: what to file before 31 October 2026

What the interim reconciliation actually is

The EMP501 interim reconciliation isn't a new return. It's a check that three numbers agree: the EMP201s you filed monthly from March to August, the money that actually left your bank account for SARS, and the IRP5/IT3(a) certificates you generate for every employee who worked in that six-month period. You already declared all of this. The reconciliation is where you prove it adds up.

If you're the employer who thinks "I did this already, every month" — you're half right. You declared it. Now you're showing your working, and it's exactly where small mismatches surface: a payment that landed a day late and rolled into the wrong month, an ETI claim on an employee who no longer qualifies, a certificate generated for someone who left in April but is still on the run. None of these are dramatic on their own. They're the reason the reconciliation exists as its own step instead of being assumed from the six EMP201s.

The two dates, and the one people get wrong

Two dates matter, and they're not the same date. The period you're reconciling — 1 March to 31 August 2026 — closed already. The window to actually submit that reconciliation runs 21 September to 31 October 2026.

That gap is worth sitting with. For three weeks after the period ends, you can't file yet — the submission channel isn't open. Employers who treat 1 September as go-time find the door shut. Employers who treat 31 October as the real deadline find their data still broken with no runway left to fix it. Use the gap for what it's for: checking your numbers, not relaxing because "there's still time."

Miss the 31 October close and it's not just interest. SARS applies an administrative penalty equal to 1% of your annual PAYE liability for the month you're late, rising 1% for every further month the return stays outstanding, up to a maximum of 10%. For an employer with a meaningful payroll, that's a real number — worth building the runway to avoid rather than a vague "costs you money."

The rule that bounces submissions this cycle: every employee needs a tax number

This is the one that catches employers who file exactly the way they filed in May. SARS has confirmed that income tax numbers "have been strictly enforced in e@syFile™ Employer and eFiling since the February 2026 employer Filing Season," and that "missing or invalid income tax numbers may delay processing and may result in EMP501 submissions being rejected."

In practice, that's the casual you took on for two months over winter, the new hire who started in June and hasn't registered yet, or the domestic worker whose registration got put off because "there's time." Each one is a certificate that can hold up your whole reconciliation, not just theirs. If any employee on your books for March–August doesn't have a valid tax reference number, that's the first thing to fix — before you touch the software.

If an employee has a number but has just forgotten it, that's a self-service request, not a project — the employee can look it up themselves, from their own registered cell number, through SARS's own channels: SMS "TRN" plus their ID number to 47277, WhatsApp "Hi" to 0800 11 7277, or dial *134*7277# and select the tax reference number option. Registering an employee who has never had a tax number at all is the different, slower job — that goes through eFiling or a SARS branch and takes real processing time, more if several employees need it at once. That's the practical reason this comes first on the list below, not last: first-time registration is the one item on the checklist you can't compress into the last week of October.

The tool changed too — don't file from the build on your machine

e@syFile Employer gets a new build ahead of each filing season, and the copy sitting on your PC from the May filing is not the one you file this reconciliation with. Two things follow from that.

First: download the current build before 21 September, not on the day you sit down to file. Second, and more easily skipped — back up your local e@syFile database before you upgrade. That database lives on one machine. It isn't backed up to the cloud on its own. An upgrade that goes wrong on a machine with no backup doesn't cost you an afternoon; it costs you the filing season, because you're rebuilding certificates from scratch instead of reconciling them.

If your backup routine is "I'll get to it," this is the managed backup conversation to have before 21 September, not after something breaks. And if the machine holding e@syFile is the only machine that can file — no fallback if it's down that week — that's a conversation about IT support you can have now, cheaply, instead of during the last week of October.

What to do before 21 September

Six things, each with an owner:

1. Pull the employee list for 1 March–31 August, including everyone who left partway through — they still need a certificate.
2. Check every employee has a valid income tax reference number. Register the ones who don't. This takes days, not minutes — do it now while you have the runway.
3. Reconcile the six EMP201s against what actually left your bank account. Differences here are what the interim reconciliation is built to catch.
4. Confirm any ETI claims still tie back to employees who actually qualify.
5. Back up the e@syFile database, then install the current build.
6. Book the filing itself for the week of 21 September, not the last week of October, so a rejected certificate still has time to be fixed and resubmitted.

If your payroll software already flags missing tax numbers and reconciles against your EMP201s as you go, most of this list is a five-minute check instead of a two-week scramble. If it doesn't, this cycle is telling you why that matters.

Payroll data is POPIA data

An IRP5 run for your whole staff is ID numbers, tax numbers, banking details and salaries in one file. Wherever that file sits while you prepare this reconciliation — a shared drive, a laptop that isn't backed up, a WhatsApp thread to your bookkeeper — is a decision about how you're processing personal information, and October is exactly when that data moves around the most. Treat the staging as seriously as the filing. If you're not sure your current setup would hold up to a question about it, that's worth a look at POPIA compliance before, not after, this year's certificates go out.

Getting your payroll data reconciliation-ready before 21 September — tax numbers checked, EMP201s tied out, certificates clean — is exactly the kind of prep our payroll support exists for. If you'd rather hand off the checklist above than run it yourself, get in touch before the window opens.

General information, not legal or tax advice.