A TaRMS payroll workflow contains several related records: the employee’s registration details, the earnings declared for a period, the PAYE return and the payment against the resulting liability. Treating them as a single upload makes it harder to identify what has actually been completed.
A more useful question is: which stage is complete, what evidence confirms it, and what remains to be checked?
ZIMRA’s published Employee Management guide describes registration and earnings processing feeding into the pending PAYE return. The detailed employee earnings and the employer-level return therefore need to be understood together, while remaining distinguishable. [S34]
Prepare the payroll evidence before opening the portal
Start with the approved employee list and period results. Confirm the employer, tax year, tax period and currencies. Keep the source payroll version identifiable so that a later comparison is made against the correct figures.
Resolve missing or inconsistent identity details before attempting a bulk submission. Registration references should identify the person reliably, not depend on a name that can be misspelt or formatted differently. ZIMRA’s FAQ explains that an existing employee TIN is retained rather than replaced when the employee is registered with another employer. [S08]
This preparation is especially important when a client sends a spreadsheet containing only names and payment amounts. Those figures may be sufficient for a payment discussion but insufficient for an employee earnings declaration.
Check access at the right level
Someone being able to sign into the employer’s profile does not necessarily mean they have every permission needed for employee information and return submission. ZIMRA’s guide distinguishes access to detailed earnings from access to the employer-level return and describes the Public Officer’s role in assigning permissions. [S34]
Agree who should see employee-level information, who prepares the submission and who authorises the return. Use named, authorised access rather than sharing one person’s credentials as an informal workaround. Where a permission is missing, investigate the role configuration before changing payroll data to solve an access problem.
The precise interface may change. Use the current official guide and the live portal for menu labels; a screenshot in an older article should not override what the authorised user is seeing today.
Keep registration and earnings changes separate
Registration establishes or updates the employee record. Earnings describe the relevant period. A changed allowance does not normally mean the employee needs to be registered again, and a corrected identity record does not by itself explain a change in taxable earnings.
For a departure, preserve the employee’s history and update the relevant end date rather than deleting the person from the record. That distinction is expressly addressed in ZIMRA’s FAQ. [S08]
A useful local change log records what was updated in the payroll record, what was updated in TaRMS and whether the two now agree. This is a suggested reconciliation aid, not an additional official return.
Use the current template for the correct classification
Download the current template through the appropriate official workflow. Do not rely indefinitely on a file saved several months earlier, especially after a change to employee categories or validation requirements.
ZIMRA’s Non-FDS implementation provides separate FDS and Non-FDS earnings templates, while the employer submits one consolidated PAYE return for the period. Separate earnings files should not be mistaken for two independent PAYE returns. [S07]
Before importing, check the column meanings, required identifiers, period, currency and number formats. Preserve leading zeros where a field requires them. Do not assume that a field accepting a value confirms the underlying tax treatment.
A practical pre-upload check is to compare employee counts and key totals by classification. If the approved payroll has 35 employees but the upload contains 34, explain the difference before submission. The missing person could be a leaver, a duplicate removed correctly or an omission; the count alone does not determine which.
Investigate differences instead of forcing agreement
After earnings are generated or uploaded, compare the resulting calculations with the approved payroll. Start with the employee records that differ, not only the overall total.
Possible areas to investigate include the period, method, earnings classification, prior amounts, credits and currency treatment. A balanced aggregate can conceal offsetting differences between employees. Equally, a small difference may be a documented rounding effect rather than a substantive error.
Do not change an earnings figure simply to make the tax match an expected total. Establish whether the source payroll, the uploaded data, the method or the interpretation requires correction. Where the difference remains unexplained, obtain clarification before proceeding.
Retain a note of the resolution. “Updated method after review of employee circumstances” is more useful than “adjusted to agree”.
Submit the return and retain its acknowledgement
Completing employee earnings is not the same as completing the employer’s return. ZIMRA’s published workflow takes the user from generated earnings to the pending PAYE return, where the relevant amounts are reviewed and submitted. [S34]
The distinction from older terminology matters too. ZIMRA introduced a replacement for the old P2 return from January 2024. “P2” may still appear in conversation or legacy material, but instructions should identify the actual return and process in use. [S10]
Retain the submitted return, acknowledgement and a link to the underlying earnings files. If a submission fails, preserve the validation messages and identify the affected records. Avoid creating a succession of indistinguishable files called “final”, “final2” and “newfinal”.
Reconcile payment separately
For October 2026, the published deadlines are 5 November for the return and 10 November for payment. Although this article is scheduled after the return deadline, that distinction remains useful when investigating an incomplete October submission. Do not read the payment date as an extension of the filing date. [S06]
After payment, compare the bank evidence and taxpayer account allocation with the declared liability. A payment reference or allocation issue needs a different response from an incorrect return. Keep those cases separate in the follow-up log.
A well-preserved period record should make four questions answerable: which employees were declared, which earnings and methods were used, which return was submitted, and which payment settled the liability. That is the connection the workflow needs to maintain from start to finish.
References
- S06 · ZIMRA — Public Notice 61 of 2026: returns and payments due November 2026. 2026-10-27.
- S07 · ZIMRA — Non-FDS calculation method. 2025-11-25; system effective 2025-11-01.
- S08 · ZIMRA — PAYE return: Employee Management Module FAQs. 2025 guidance.
- S10 · ZIMRA — Public Notice 12 of 2024: submission of new PAYE return. 2024.
- S34 · ZIMRA — Submission of PAYE return through Employee Management Module. 2025 guidance.