Understanding Employer Tax and EMP501 Support

This page explains how Beam Machine supports monthly employer-tax review, where that support stops, and what you still need outside the app for South African payroll compliance.

Product: Beam Machine
Module: Tax -> ITR14 / EMP201 Preparation and Payroll
Role: Payroll Lead, Accountant, Tax Preparer, Reviewer
Difficulty: Intermediate
Time: 10 minutes
Last Updated: 2026-03-10
Version: Current Beam Machine app build in this repo

Before You Start

• You need access to Payroll and Tax.
• Relevant pay runs must already be finalized or the tax worksheet will be empty.
• Treat this page as an interpretation guide, not payroll tax advice for unusual facts.

What is this page?

This is the plain-English explanation of how Beam Machine currently helps with employer tax.

In practice, employer tax work in South Africa usually means:

• monthly EMP201 review and payment support,
• payroll tax component checks for PAYE, SDL, UIF, and ETI,
• and later EMP501 reconciliation between monthly declarations, payments, and employee certificates.

Beam Machine currently exposes the strongest monthly support on the ITR14 / EMP201 Preparation screen and through finalized payroll runs. It does not currently show a full EMP501 reconciliation workspace in the live UI.

When do you use this?

Use this page when:

• the payroll team wants to understand what the BM EMP201 numbers actually mean,
• finance is preparing for monthly SARS payment and declaration work,
• or year-end reconciliation planning is starting and someone assumes Beam Machine already does the whole EMP501 process.

If you skip this distinction, teams start relying on a monthly support screen as if it were a full employer-tax compliance engine.

Where do you find the live BM support?

Primary paths:

• HR -> Payroll -> Pay Runs
• Finance -> Tax -> ITR14 / EMP201

Routes:

• /dashboard/payroll/pay-runs
• /dashboard/tax/itr14-prep

How to use Beam Machine for employer-tax support

1. Finalize the relevant pay runs in Payroll first.
2. Open Tax.
3. Click ITR14 / EMP201.
4. Move to the EMP201 — Monthly Employer Declaration card.
5. Confirm the period shown on screen.
6. Review the payroll-driven totals in this order:
   • PAYE (Employees' Tax)
   • SDL (1%)
   • UIF — Employee (1%)
   • UIF — Employer (1%)
   • UIF Total (2%)
   • Less: ETI (Employment Tax Incentive)
   • Total EMP201 Liability

✅ Checkpoint: You should now be looking at a monthly support worksheet built from finalized payroll data, not a blank planning screen.

7. Compare the BM totals to your payroll working papers before using them in declaration or payment work.
8. Keep the actual filing and proof of payment in your formal SARS payroll file.
9. Build the EMP501 reconciliation outside the current BM UI by tying together:
   • monthly EMP201 totals,
   • SARS payment proof,
   • and certificate totals from the payroll process.

What Beam Machine does and does not do today

• Beam Machine does surface monthly employer-tax totals from finalized pay runs.
• Beam Machine does help you check PAYE, SDL, UIF, and ETI before monthly filing.
• Beam Machine does not currently expose a dedicated EMP501 screen, a certificate-reconciliation workbench, or a visible e@syFile-style import and submission workflow in the live UI.
• Beam Machine does not replace payroll review, certificate control, or SARS submission evidence.

South African employer-tax logic users should know

• EMP201 is the monthly employer declaration for PAYE, SDL, UIF, and applicable ETI.
• SARS generally expects EMP201 declaration and payment by the 7th of the following month, or the last business day before that if the 7th is not a business day.
• EMP501 is the reconciliation process that ties monthly liabilities and payments to employee tax certificates.
• EMP501 is not the same job as EMP201. Monthly figures can look correct and still fail later reconciliation if certificates, periods, or payments are wrong.

Common Questions & Issues

"The EMP201 card is blank"

Why this happens: No finalized pay runs exist for the period BM is checking.

Fix: Finalize the pay run first, then refresh the tax worksheet.

"I can see EMP201 totals, so EMP501 must already be done"

Why this happens: Users confuse monthly declaration support with reconciliation support.

Fix: Treat the EMP201 card as monthly support only. Complete EMP501 reconciliation separately.

"Can I submit the employer declaration directly from this page?"

Why this happens: The screen title sounds operationally complete.

Fix: No direct filing control is exposed on this route in the current BM build. Use the screen as a support worksheet.

"ETI is reducing the liability. Can I trust that blindly?"

Why this happens: Users see the offset and assume SARS qualification was already fully validated.

Fix: Recheck employee eligibility, period qualification, and payroll evidence before relying on the offset.

What's Next

• Read 03-preparing-itr14-and-emp201.md for the route-level worksheet manual.
• Read 02-managing-provisional-tax.md if the next tax job is company provisional tax rather than payroll tax.

Related Pages

• 00-tax-guide-index.md
• ../08-people-and-payroll.md
• ../tasks/07-creating-a-pay-run.md
• ../modules/14-working-in-payroll.md

SA Compliance Reference

• South African employer-tax work normally requires monthly EMP201 control and periodic EMP501 reconciliation.
• Beam Machine currently supports the monthly review side more clearly than the full reconciliation side.
• Keep certificate totals, payment references, and SARS proof outside the app as part of your payroll compliance file.

Still Stuck?

• If monthly totals look wrong, go back to finalized pay runs before blaming the tax card.
• If someone expects a full EMP501 workbench, check 13-mapping-sa-tax-scope-to-live-bm-pages.md.
• Contact support: support@veva.co.za

Was this page helpful?

[Yes] [No]