Separate the employer’s obligations before checking status
A PAYE number is one item in an employer’s compliance file. It does not demonstrate that every UIF task has been completed. The useful questions are whether the employer is registered through the appropriate route, whether contributions are calculated correctly, whether payments reach the correct account and whether employee information is declared accurately.
Review those questions separately and then reconcile the results. A registration letter cannot prove that last month’s employee file was submitted. A bank payment cannot show that a new employee’s identity and start date were accepted. Treating all of these as one UIF status makes it difficult to identify a gap until an employee or an official asks for the missing history.
Confirm the contribution-payment registration
SARS’s current guidance says an employer registered for employees’ tax also needs to register to pay UIF contributions. The appropriate payment registration depends on the employer’s position under the rules; it is not simply a choice of whichever portal seems easier. Obtain the actual registration outcome and confirm the relevant employer details and effective information.
If an adviser handled the setup, ask for the official records rather than an invoice saying payroll registration completed. Check that the legal employer is correct, especially where several companies share directors or a payroll administrator. A valid registration belonging to a related business does not establish the position of the entity employing the staff. Resolve mismatches before relying on the account for payments.
Check the UI Commissioner’s employee-information requirements
The SARS UIF guide distinguishes registration for payment from registration and monthly employee information required by the UI Commissioner. Employers paying contributions through SARS still need to address the employee-information side. Confirm the appropriate UIF employer record and declaration route with the current official guidance.
This distinction explains why an EMP201 can be correct while an employee’s detailed UIF history remains incomplete. The EMP201 allocates payment amounts; it is not the same record as the employee declaration information. Ask the payroll provider who submits that information, under which employer reference and how the business receives evidence of the result. Do not assume it happens automatically because the payroll calculation includes UIF.
Use a four-part evidence check
| Part of the process | Evidence to inspect |
|---|---|
| Employer registration | Official records and correct employer identifiers |
| Payroll calculation | Employee-level contribution basis and employer share |
| Employee declarations | Submitted period details and processing feedback |
| Payment | Declaration allocation, bank evidence and account posting |
Use the same period and legal employer when comparing the records. If the figures or people differ, investigate the reason. A simple tick beside UIF paid should not conceal a missing declaration or a payment allocated to the wrong period.
Test employee coverage and payroll settings
Review who is included and the basis on which any employee is excluded. UIF has its own contribution rules and exclusions. An employee with no PAYE deducted is not automatically outside UIF, and a high salary does not mean the employee disappears from the declaration process. Have the relevant rule applied to the actual employment facts.
Check the contribution base and the ceiling applicable to the period. Do not assume every payroll earning has identical treatment for PAYE and UIF. Review new starters, leavers and unusual pay items, and retain the reason for material settings. Payroll software can calculate consistently while using an incorrect employee category or earning-code configuration, so a successful pay run is not proof that the setup is right.
Illustrative example: payment succeeds but a starter is omitted
A company hires an employee and includes the correct UIF amount in its monthly SARS payment. Its payroll provider’s employee declaration export was configured before the new starter was added, so the employee was absent from that submission. The payment does not identify or repair the omitted employee record on its own.
The employer should compare the payroll roster with the declaration detail, confirm the submission feedback and correct the employee information through the appropriate process. It should not make a second contribution payment merely to make the missing name appear. First establish whether the amount was already paid and allocated correctly. The example shows why contribution totals and employee history need separate evidence.
Avoid duplicate payments across channels
Establish which authority receives the employer’s contributions under the applicable registration arrangement. If staff use both SARS and UIF systems for different tasks, document which system is used for payment and which records support employee declarations. Do not interpret the existence of a payment button as an instruction to pay the same liability again.
If a statement appears to show an amount already paid elsewhere, reconcile the period, employer reference and allocation before acting. Obtain clarification where needed and keep the payment evidence. A duplicate transfer can create a separate refund or allocation problem while leaving the original declaration issue unresolved. The correct response begins with the actual transaction history, not a second payment made without review.
Agree the payroll provider’s deliverables
Ask the provider to state whether its service includes registration, payroll calculations, employee declarations, contribution-payment preparation and follow-up on rejected files. Those are related tasks but may not all be included in one fee. Assign a named person inside the business to review the results and handle employee changes.
Require a monthly handover showing what was submitted, the period covered and any unresolved errors. A payroll report prepared locally is different from evidence that an authority received the declaration. If the provider changes, obtain the historical files, references and open queries before the old access is removed. Keep the employer’s records accessible without relying on one individual’s email account.
Maintain changes throughout employment
Record starts, terminations, remuneration changes and other relevant employment details accurately and on time through the applicable process. Check the effective dates instead of replacing all history with the current position. A former employee should not remain active because nobody passed the termination information to the declaration team.
When an employee queries their history, compare the underlying records rather than assuming the system is wrong or the employee is mistaken. Identify the periods involved and distinguish a missing record from a payment issue. Correct factual errors with supporting evidence. Do not change a termination reason or employment date simply to produce a preferred benefit outcome.
Treat employee claims as a separate process
Employer registration and contribution records support the UIF system, but they do not guarantee that an individual benefit claim will be approved. Eligibility and the claim decision belong to the applicable official process. Provide accurate employment evidence and avoid promising a payment amount or processing date on behalf of UIF.
The current uFiling portal notice directs employee benefit applications to UIF Online. Older guides may show a benefit workflow that is no longer the correct route. Use current official entry points when helping employees find information, and keep sensitive employee documents within appropriate access controls. An employer’s administrative support should not become an unauthorised claim submission or a false declaration.
Close the registration gap with evidence
Vatco’s UIF registration support can help organise the employer setup and identify missing records. Where the wider payroll process needs attention, payroll services can assist with the recurring calculations and handover requirements. Bring the PAYE and UIF records, employee list and recent declaration and payment evidence.
The immediate outcome should be a clear statement of what is registered, what has been declared, what has been paid and what still needs correction. Keep those facts separate in the monthly review. That gives the business a stronger basis for compliance than assuming that a PAYE number has resolved every UIF obligation.
Sources and review
Checked on 30 September 2026. Use the linked official guidance for current requirements and forms.
- SARS: Unemployment Insurance Fund
Current overview updated 19 August 2026, covering contribution registration, payment and exclusions. Check the rule applicable to the relevant period.
- SARS employer guide to UIF
Official guide distinguishes contribution-payment registration from employee information submitted to the UI Commissioner. Its older interface references are not used as current screen instructions.
- SARS: registering for PAYE
Official registration guidance explains the additional UIF contribution-registration requirement where applicable.
- Official uFiling employer portal
Current employer registration, declaration and payment entry point. The live notice directs employee benefit applications to UIF Online, not the old uFiling benefit workflow.
Support for UIF registration
Discuss your records and the support your business needs.
Explore UIF registration