Skip to main content

The EMP501 reconciliations

Twice a year SARS wants the monthly EMP201s reconciled against what you actually paid people. E·BIZI Pay tracks those two deadlines on the Processing dashboard and holds the figures you need for them.

For what a reconciliation is and what SARS does with it, see EMP501 reconciliation.

When the cards appear​

Four cards, on the month they are due rather than on every month.

Generate Bi-Annual EMP501 and Submit Bi-Annual EMP501 cover 1 March to 31 August, and appear on the October run. SARS wants that one by 31 October.

Generate Annual EMP501 and Submit Annual EMP501 cover the full tax year, 1 March to 28 February, and appear on the May run. SARS wants that one by 31 May.

You will not see them in any other month. A month's cards are created when you confirm the month before it, so the bi-annual pair appears once September is confirmed and October opens. Looking for them in August will not find them.

Send IRP5s sits alongside the annual pair in May.

Where the figures come from​

Your monthly EMP201s are the input, and E·BIZI Pay keeps every one of them.

Open the Processing dashboard, use Select run to pick a month, and choose Re-execute on that month's Generate EMP201. The report opens with that month's PAYE, UIF and SDL, and CSV downloads it. Do that for each month in the period and you have the totals the reconciliation asks for. See the EMP201.

The figures do not change once a month is confirmed, so a month you pulled in June reads the same in October.

The four cards are yours to confirm​

All four work the way Submit EMP201 and EMP201 Payment do. E·BIZI Pay cannot see eFiling, so marking one complete is you recording that you have done it. Nothing is sent to SARS when you choose Mark complete, and nothing is sent when you re-execute.

Do the reconciliation itself on eFiling, or in e@syFile if you are working from a payroll export, then come back and mark the cards.

The order they unlock in​

Both Generate cards sit behind that month's Submit UIF Declaration, and each Submit card sits behind its own Generate. So the ordinary month-end work for October has to be finished before the bi-annual pair opens up.

A card reading blocked is waiting for the step before it, not for a date. See the Processing dashboard.