UIF Registration and Declarations Checklist

UIF compliance breaks down when employers think payment alone is enough. The employee declaration record also matters.

If employee details are missing or stale, a maternity, illness, unemployment, or retrenchment claim can become difficult even where deductions were made.

UIF setup checklist

1. Confirm the employer registration position.
2. Activate or update the uFiling profile.
3. Load employer details correctly.
4. Add employee identity and employment details.
5. Confirm remuneration and contribution treatment.
6. Save proof of registration and declarations.
7. Link the process to payroll and EMP201 review.

This supports UIF registration services and payroll services.

Monthly declaration checks

Check each month:

• new employees
• terminations
• salary changes
• unpaid leave
• maternity leave
• retrenchments
• corrections to ID or passport numbers
• payroll period and remuneration values

The UIF declaration should agree to the payroll file for the month.

Payroll and SARS link

Employers often handle UIF through both payroll and SARS EMP201. That makes reconciliation important. The business should know whether the UIF amount deducted, the employer contribution, the EMP201 value, and the Labour declaration all tell the same story.

This is why UIF belongs inside the employer compliance checklist.

Records to keep

These records reduce pressure when an employee needs documents urgently.

UIF monthly control table

The table is useful because UIF is not only a monthly amount. It is also an employee record system. If the employee record is wrong, the employee may struggle when trying to claim benefits even if contributions were deducted.

Employer registration review

Start by confirming whether the employer is registered and which platform or process is being used for declarations. Some employers have SARS payroll tax records, Labour records, and uFiling access that do not fully align. The employer should know which reference numbers apply, who controls access, and where proof of registration is stored.

The registration file should include employer details, representative details, company registration information where relevant, address information, banking details where required, and proof of the UIF setup. If the business has changed name, address, representative, or payroll provider, the file should be reviewed.

For new employers, UIF setup should happen with the first payroll planning, not after employees ask for claim documents. The same onboarding data used for payroll should support UIF declarations: employee identity details, employment start date, remuneration, occupation or role, and contact information where required.

If a business has historic employees but weak UIF records, separate the current month from the cleanup. Current declarations should be brought under control while older gaps are reviewed. That prevents the file from continuing to deteriorate while historic corrections are being prepared.

Employee declaration accuracy

UIF declarations depend on accurate employee-level data. Review employee names, ID or passport numbers, start dates, termination dates, remuneration, contribution status, and payroll period. A small typo can become a major problem when an employee needs to claim.

New employees should be added promptly. Terminated employees should not remain active indefinitely. Salary changes should be reflected. If an employee has unpaid leave, maternity leave, illness leave, or reduced hours, the payroll file should explain the remuneration value used for the declaration.

The declaration record should agree to the payroll report. If the payroll system says one value and uFiling or Labour records show another, keep a reconciliation note. This is especially important when corrections are made after payroll has already been finalised.

UIF, EMP201, and payment reconciliation

Many employers pay UIF contributions through SARS as part of EMP201. That can create a false sense that UIF compliance is complete. The payment may be made, but employee declarations still need to be current.

Each month, compare the employee UIF deductions, employer UIF contributions, EMP201 UIF value, payment proof, and declaration records. The totals should agree or the difference should be explained. If the employer pays through a separate Labour process rather than SARS, the same principle applies: payment and declaration evidence should sit together.

The accounting records should also make sense. UIF liability should be posted, paid, and cleared. If the accounting team only receives a combined EMP201 payment amount, it may not know whether PAYE, UIF, SDL, and ETI were recorded correctly. A clean payroll journal prevents confusion later.

Employee claims and document readiness

UIF records usually become urgent when an employee needs to claim. That may be after unemployment, maternity leave, illness, adoption, or a dependent claim. At that point, the employee needs accurate employment and remuneration records quickly.

The employer should be able to provide termination or leave records, payslips, payroll summaries, and declaration proof without reconstructing the employee history. Where UI-19 or other movement records are needed, the details should match the payroll file.

This is why monthly declaration discipline matters. A business that updates records only when a claim arises may discover missing start dates, incorrect ID numbers, old salary values, or employees who were never properly loaded. Those gaps are harder to fix under pressure.

Payroll provider handover

If payroll is moved between providers, UIF records should be part of the handover. The new provider needs employee master data, declaration history, reference numbers, access status, prior payroll reports, and any known corrections. Without that, the new payroll may be processed correctly while UIF records remain stale.

The handover should also confirm who is responsible for declarations. Do not assume the bookkeeper, payroll provider, accountant, or business owner is handling UIF unless the responsibility is stated. A simple monthly checklist prevents the task from falling between roles.

Common UIF mistakes

The first mistake is assuming EMP201 payment is the same as employee declaration compliance. It is not. Payment and declaration records both matter.

The second mistake is not updating terminations. Employees who left months ago should not remain active in the declaration record, and their final payroll details should be supported.

The third mistake is poor employee identifiers. ID and passport errors can block or slow claims. These should be checked during onboarding and again before certificates or claim documents are prepared.

The fourth mistake is waiting for employee pressure. UIF should be current before someone needs benefits. That is both a compliance issue and a staff trust issue.

Review cadence

UIF should be checked at three points: onboarding, monthly payroll close, and termination or leave events. Onboarding confirms the employee record is usable. Monthly close confirms remuneration and contributions are current. Termination or leave review confirms that claim-related records are accurate before the employee needs them.

For SMEs, this cadence does not need to be complicated. Add UIF to the same payroll checklist used for payslips, EMP201, payroll journals, and employee changes. The important part is that the review happens while the information is still fresh.

If a month has no employee changes, still save the declaration proof or review note. A consistent record is easier to defend than a file that only contains documents for problem months.

Practical takeaway

UIF should be kept current monthly. Waiting until an employee needs to claim is usually too late.