What should I check if an employee is missing from UIF declarations?

Define what is missing and where

Ask which record or period shows the problem. Is the employee absent from the employer’s local payroll export, the submitted declaration detail or the UIF record being viewed? Those are different stages. Write down the employer reference, employee identifier and affected months before deciding what needs correction.

Capture the visible result and any error message without exposing unrelated employees’ personal data. A statement that UIF is missing is too broad to diagnose. It may refer to a name not found, a gap in employment history, an incorrect salary period or a payment that has not been allocated. Keeping the symptom precise prevents the business from changing records that were already correct.

Confirm the legal employer and account

Check that the declaration belongs to the entity that employed the person during the period. Businesses with several companies, branches or historical payroll providers can easily inspect the wrong reference. Compare the employment agreement and payslips with the official employer record and the account used for the submission.

If the employee transferred between legal employers, establish the actual dates and records for each relationship. Do not create one continuous history under the latest company merely because the trading name stayed the same. Seek advice where the employment arrangement is complex. The correction must reflect the facts and applicable process, rather than using the most convenient available account.

Match identity details without creating duplicates

Compare the employee’s name and identity details with the supporting documents and the original payroll record. Look for typing errors, transposed digits or an outdated identifier where a lawful change occurred. Use the current official requirements for the employee’s documentation rather than assuming every person has the same type of identifier.

Search existing records carefully before adding another employee profile. A duplicate can split history and make later reconciliation harder. If two records appear to concern the same person, ask the current support channel how to resolve them. Do not delete historical records blindly or use another person’s identifier to force an upload through validation. Preserve the evidence explaining the correction.

Check employment dates and contributor status

Review the actual commencement date, relevant termination information and the status used in each affected month. An accidental future start date or premature termination can remove an employee from a period’s declaration. Compare the declaration data with the contract, attendance records and approved payroll changes rather than relying only on the current employee screen.

If the employee was marked as excluded, verify the basis under the applicable UIF rules. A lack of PAYE deduction or a casual label does not by itself settle UIF treatment. Retain the factual and legal basis for the decision. Do not alter an employment date or status simply to make a benefits claim easier; correct it only where the supporting facts justify the change.

Compare preparation with actual submission

Obtain the file or declaration that was actually sent, not only a report regenerated from today’s corrected payroll. The earlier export may have omitted the employee even though the current screen now includes them. Record the submission date, period and channel, and inspect any receipt, validation feedback or rejected-record report.

A payroll provider’s message saying the monthly run is complete may mean salaries were calculated, not that the UIF declaration succeeded. Ask for the specific submission evidence. If the file failed, determine whether the whole declaration or only particular records were affected. That distinction helps target the correction without unnecessarily duplicating data that was already accepted.

Use a symptom and evidence table

The table suggests where to look; it does not establish the cause. Record the evidence and conclusion for the actual employee before changing the history.

Illustrative example: a payroll migration omission

An employer changes payroll providers in July. The new provider loads current staff, but one employee’s start date is accidentally captured in August. The employee receives July pay and a UIF deduction, yet the July declaration export does not include the person. The current payroll balance alone cannot prove that July’s employee information was supplied.

The employer should preserve the July payroll and original export, verify the true start date and identify the appropriate correction process. It should also check the other migrated employees for the same pattern. If the July contributions were already paid, that payment must be reconciled rather than repeated automatically. The example illustrates a data handover error, not a universal explanation for every missing record.

Separate declaration repair from payment repair

Reconcile the employee-level contribution calculations with the total declared and paid for the period. Determine whether the missing employee information also caused a financial shortfall or whether the money was already included. A correction can affect data, money or both, and each part needs the correct treatment.

Do not pay a second amount solely because a name is absent from a screen. Equally, do not assume that fixing the name settles an unpaid contribution. Keep payment references and account evidence alongside the declaration correction. Where the amounts or allocation remain unclear, obtain advice before making a refund claim, offset or further transfer.

Follow the current correction route

Use the current official portal instructions or UIF support for the affected record and period. Older user guides show how employee data feeds declarations, but interface paths and available correction functions can change. If the period is locked or the required history is not available, ask how to submit the supporting correction instead of forcing it into an unrelated current month.

Provide a concise explanation of the error, the original and correct details, affected periods and supporting evidence. Keep the case reference and response. A support enquiry being logged is not proof that the employee history has been corrected. Review the outcome and follow up where the displayed or confirmed record still differs from the supported facts.

Communicate accurately with the employee

Explain which period is being checked and what action has been taken, using plain language. Share appropriate evidence concerning that employee without exposing the rest of the payroll. If a correction is pending, say so. Do not promise that the UIF will approve a claim or pay by a particular date as a result.

If the employee disputes the underlying employment dates, earnings or termination reason, resolve that factual disagreement through the appropriate employment process and evidence. A payroll administrator should not invent a reason to close the query. Keep the employee’s correspondence with the case file and protect identity, bank and earnings information throughout the review.

Check submissions made through a different provider

Before resubmitting a whole period, ask whether a former provider or another authorised person sent the declaration through a different channel. The records visible in one system may not be a complete history of every submission. Obtain the original receipt and ask UIF to clarify the status if the evidence conflicts with the current view.

Keep the enquiry limited to the relevant employer, employee and periods. This avoids creating duplicate submissions while trying to repair a display or retrieval issue. Once the position is confirmed, document which record is authoritative and what, if anything, still requires correction.

Prevent the same omission next month

Add a monthly comparison between the payroll roster and the submitted employee declaration detail. Review starters, leavers and changed identifiers explicitly, and retain processing feedback. After a payroll migration, reconcile the opening employee list and historical information before treating the handover as complete.

Vatco’s UIF support and payroll services can help organise the records and identify the gap. Bring the actual submitted files, employer references, affected employee details and payment evidence. A focused evidence pack makes it easier to distinguish an omitted declaration from an identity mismatch or contribution problem and to verify the eventual correction.