Repeated employee IDs in a Kenyan recruitment agency’s payroll file need investigation before removal. One worker may have several approved assignments or earning codes in the same pay period. Establish what each row represents, reconcile the approved total and check how the payslip output handles that structure.
All worker records in this example are fictional.
Separate a repeated identifier from a duplicated payment
Consider a Kenyan staffing agency whose employee works at two client sites during one approved pay period. The client assignment references differ, but the employee ID is the same. Payroll has approved separate earning lines in Kenyan shillings (KSh). HR must preserve the valid items while confirming that they belong to the same employee.
Deleting the second row solely because the ID repeats could remove valid pay information. Equally, two identical rows may be an accidental duplication. The repeated identifier is a review signal, not a conclusion.
Ask the payroll owner to identify the meaning of each line and confirm the authorised total. A delivery administrator should not decide which earnings are legitimate from formatting alone.
Build a small review record
Use a working note separate from the import file:
| Item | Fictional example | Review purpose |
|---|---|---|
| Worker | AG-204 | Confirm a stable identity |
| Period | One approved pay period | Avoid combining unrelated periods |
| Line A | Assignment A: KSh 4,200 | Preserve the first approved item |
| Line B | Assignment B: KSh 1,800 | Explain why the ID repeats |
| Total earnings | KSh 6,000 | Reconcile with the approved payroll |
These amounts illustrate reconciliation only. They do not prescribe wage rates, deductions or a legal pay calculation.
Test the actual output before sending
Ant Payslip accepts the payroll spreadsheet the business already uses and provides employee previews. Include a multi-line worker in the test. Check whether the output correctly represents the approved earnings and intended recipient.
Do not assume that recognising fields automatically proves that every multi-row arrangement is supported. If the preview produces separate unintended statements, omits a line or gives an unclear total, pause that record and resolve its treatment with the product team and payroll owner. A new import template should not be invented as a substitute for understanding the data.
Review a second employee with a similar name to ensure that grouping follows the correct identity. Then compare the number of intended employee statements with the output, investigating differences rather than assuming one source row must equal one worker.
Keep the check when assignments change
Agency workloads change as clients and earning codes change. Add new structures to the review sample when they first appear. Retain the explanation of valid repeated IDs so the next administrator does not “clean” them away.
Frequently asked questions
Should HR use Excel’s remove-duplicates command first?
Only after the payroll owner has defined what makes a record an actual duplicate. Employee ID alone may be insufficient.
Does automatic recognition guarantee correct grouping?
No. Inspect representative output using the agency’s actual approved structure before release.
Discuss your agency’s spreadsheet structure with Ant Payslip and include a fictional multi-assignment record in the demonstration.