Lesson 9.1: Employee Management — Employees and Earnings

If your organisation employs anyone — even one part-time worker — you’ll need TaRMS’s Employee Management module before you can lodge a clean PAYE return. This lesson takes you through it screen by screen.

If your organisation employs anyone: even one part-time worker — you’ ll need TaRMS’ s Employee Management module before you can lodge a clean PAYE return. This is where you register each employee on your firm’ s TIN, capture their earnings, and generate the PAYE-ready data that feeds the monthly PAYE return. Get the registration wrong (wrong TIN, wrong status, wrong tax credit) and the PAYE return errors cascade for the rest of the tax year. This lesson takes you through the module screen by screen, with the most common errors flagged.

Modules 1–8 of TaRMS Essentials taught the taxpayer’s view of TaRMS. turns to the specialised modules of the Self-Service Portal — the modules that exist for taxpayers with specific operational responsibilities. Lesson 9.1 deals with Employee Management, the SSP module that any organisation employing one or more workers must master before it can lodge a clean PAYE return.

The Employee Management module is, in ZIMRA’s own description, the place where the SSP user "registers employees of the organization you represent, manages registration details of employees regardless of the current employment statuses (active, inactive, former employee, temporary employee, contractor, etc.) and generates or uploads the employee incomes for further submission of PAYE tax reports". In one sentence, that is the entire purpose: keep an authoritative employee register at ZIMRA, and feed earnings data from that register into the PAYE return.

Why does this matter? Because Lesson 4.2 taught the PAYE return as if the data were captured ex-novo every month. In practice, the PAYE template can be auto-populated from the Employee Management module’s register, and ZIMRA can cross-check what the employer declares on the P2 against what the employer registered as employees. Employers who keep the two in sync sail through PAYE compliance; employers who do not, generate audit-trigger discrepancies that the year-end ITF 16 reconciliation surfaces ruthlessly.

By the end of this lesson the learner will: (i) be able to navigate to the Employee Management module from any Profile’s context; (ii) register a new employee with the correct status (active, inactive, contractor, etc.); (iii) capture earnings either via direct entry or template upload; (iv) generate the assessment of employee earnings that feeds into the PAYE return; (v) understand the legal duties that attach to the employer-as-PAYE-agent under sections 73–79 of the Income Tax Act; and (vi) reconcile the Employee Management register against the year-end ITF 16.

1. Sections 73–79 Income Tax Act — the PAYE system

The PAYE system in the Income Tax Act [Chapter 23:06] imposes a chain of duties on every employer:

• section 73 — the duty to deduct PAYE from each employee’s remuneration on each pay day, calculated using the rates and tables in force, and to remit within 10 days of month-end.
• section 73A — the obligation to keep employee records for the section 51 six-year retention window.
• section 75 — the certificate of tax deducted (P6) issued to each employee at year-end.
• section 76 — year-end reconciliation via ITF 16 (employer’s annual return).
• section 79 — the employer’s personal liability where deducted PAYE is not remitted.

2. Aids Levy

The Aids Levy is 3% of PAYE deducted (effectively a surcharge). The Employee Management module’s earnings calculation includes it automatically.

3. Finance Act No. 7 of 2025 — dual-currency PAYE

For organisations paying in mixed currencies (some employees USD, others ZWG, or some employees in both), the Employee Management module captures the currency of remuneration on each row. The PAYE return then reports two parallel liability totals.

4. The data-protection layer

Employee personal data captured in the SSP (national IDs, addresses, banking details for some salary components, dependents data for tax-relief calculations) is personal data within the meaning of the Cyber and Data Protection Act [Chapter 12:07]. The employer is the data controller; ZIMRA is a downstream data controller of the data shared via the module. Section 7 (data-protection by design) and section 8 (lawful basis) both apply.

5. Statutory Instruments and Practice Notes

The PAYE rates and tables are set in the Finance Act in force. The Employee Management module’s calculation engine pulls the current tables from a back-end configuration which ZIMRA updates centrally. Employers do not need to update tables locally.

1. Workflow to access the module

The Employee Management module is taxpayer-context-bound: it appears only when the SSP user has shifted to a TIN that holds a PAYE registration. Workflow:

1. Login to the SSP.
2. Switch to the employer’s TIN at the top right.
3. Click Employee Management on the left-hand rail.
4. Two sub-menus appear: Employees and Earnings. (A third operational page, Assessment of Employee Earnings, is accessed via the Employees page.)

2. The Employees page

This is the master register. Every individual the organisation employs in any capacity must appear here. Each row carries:

3. The Earnings page

The Earnings page captures pay-period income for each employee. Two routes:

• Direct entry: Open Earnings, select the period, enter gross remuneration, allowable deductions and any non-cash benefits per row. Suitable for very small employers (1–5 staff).
• Template upload: Download the earnings template, populate it from payroll software, upload it back. Same exact-match-headings discipline as the PAYE template (Lesson 4.2). Suitable for every employer with more than 5 staff.

4. The Assessment of Employee Earnings

Once Earnings are captured for a period, the system computes the PAYE liability per employee using the rates and tables. The Assessment of Employee Earnings page presents this computation. The employer reviews the figures, accepts them, and the data is then made available to the PAYE return (Lesson 4.2) for one-click population.

5. Status changes

Employees move between statuses over time. The module supports:

• Active → Inactive: e.g., maternity leave, sabbatical.
• Active → Former Employee: resignation, dismissal, retirement.
• Temporary → Active: conversion to permanent.
• Contractor → Active: conversion of independent contractor to employee.

Each status change has knock-on effects on the PAYE computation. Inactive employees draw zero remuneration and zero PAYE. Former Employees should not appear on PAYE returns for periods after cessation.

6. The integration with PAYE return submission

The Employee Management module is upstream of the PAYE return. The recommended flow:

1. End-of-month payroll closes in the employer’s payroll system.
2. Earnings template is exported from payroll.
3. Template is uploaded to the SSP’s Earnings page.
4. Assessment of Employee Earnings is reviewed and accepted.
5. PAYE return is opened (Lesson 4.2); data is auto-populated from the assessment.
6. Return is reviewed, submitted, paid via Single Account.

1. The 5-employee SME (Lily, post-PAYE)

Lily registers two staff in the Employees page on day-one of their engagement; updates the third when she hires later in the year. Each month her routine: open Earnings, enter five rows, accept assessment, switch to PAYE return, submit. End-to-end on the SSP: 25 minutes.

2. The 1,200-employee corporate (Cairns Foods)

The HR system exports the Employee register weekly. The Tax Manager runs a reconciliation against the SSP register monthly. Earnings data flows from the payroll system through a CSV pipeline. Status changes are processed in the SSP within 48 hours of HR confirming.

3. The contractor question

Independent contractors (paid for services, not employed under contract of service) are not employees for PAYE purposes. The module’s "Contractor" status exists for organisations that wish to keep contractor records inside the SSP for completeness, but PAYE is not deducted from contractor payments. (Withholding tax under different provisions may apply — see the parallel Withholding Tax course.)

4. The cessation discipline

An employee leaves on 25 April. Workflow:

1. HR notifies finance of cessation date.
2. Within 48 hours: status changed to Former Employee; cessation date set to 25 April.
3. April PAYE: employee’s pay-to-date is included.
4. May PAYE onwards: employee does not appear.
5. P6 certificate generated at year-end covering Jan–25 April only.

1. Section 79 ITA — employer’s personal liability

Where an employer has deducted PAYE but failed to remit, section 79 imposes personal liability on the employer (and, in serious cases, on directors). Numerous unreported Special Court matters have applied section 79 to wind up corporate veil arguments. The Employee Management register is the documentary anchor: it shows what the employer told ZIMRA they should be deducting; the gap between register and remittance is the section 79 quantum.

2. Innscor Africa revisited

The 2019 Special Court case on PAYE template formatting (Lesson 4.2) implicitly turns on the Employee Management register: if the register shows 1,200 employees and the PAYE template uploads only 1,180 rows, the 20-row gap is a discrepancy ZIMRA can investigate. The discipline is to keep both in sync.

3. Misclassification of contractors

South African analogue (persuasive): in ITC 1858, an "independent contractor" was held by the Tax Court to be an employee in substance. The factual matrix — control, integration, economic dependence — trumped the label. Zimbabwean practitioners should perform the same substance test before classifying a worker as Contractor in the Employee Management module.

1. Stale Employee register

HR forgets to update the SSP register after a hiring or cessation. Fix: monthly HR-finance reconciliation.

2. Wrong employment status

Inactive recorded as Active, or a contractor recorded as Active. Fix: apply the substance test; document classification reasoning.

3. Missing TIN for new joiners

Each employee should have a TIN. Without it, the PAYE return validation may fail. Fix: add "obtain TIN" to the new-joiner HR checklist.

4. Altered Earnings template headings

Same parser as the PAYE template; same prohibition on heading changes.

5. Year-end mismatch with ITF 16

Monthly earnings totals must equal ITF 16 totals. Fix: reconcile each month.

6. Treating contractor payments as PAYE

Generates over-paid PAYE and contractor confusion. Fix: classify contractors as Contractor; do not deduct PAYE.

7. Failing to capture branch

Branch attribution affects audit-trail and section 79 directors’ liability allocation. Fix: capture branch on every employee row.

Question 1

What is the relationship between the Employee Management module and the PAYE return submission workflow taught in Lesson 4.2?

Question 2

List the employment statuses recognised by the SSP and explain when each applies.

Question 3 — Scenario

Cairns Foods hires 50 graduate trainees on 1 March, 30 of whom convert to permanent on 1 September. Walk through the Employee Management workflow for this cohort across the year.

Question 4

What is the legal authority for the employer’s personal liability for deducted-but-not-remitted PAYE?

Answer 1

Employee Management is upstream. The register holds the authoritative list of employees and their attributes; the Earnings page captures pay-period income; the Assessment of Employee Earnings computes PAYE per employee; the data flows into the PAYE return on the Pending Returns screen. A clean register makes the PAYE return a one-click population.

Answer 2

Active (currently employed and paid). Inactive (employed but not currently paid — e.g., unpaid leave). Former Employee (relationship ended). Temporary (fixed-term assignment). Contractor (paid for services, not under employment contract; no PAYE deducted). Casual (irregular work).

Answer 3

1. March: register all 50 graduates as Temporary with engagement date 1 March. Generate March earnings.
2. Apr–Aug: continue capturing monthly earnings.
3. 1 September: change status of 30 to Active; the 20 not converted remain Temporary or have status changed to Former Employee per HR direction.
4. From September: Active 30 carry full PAYE; the 20 either continue under Temporary or, if departed, appear with cessation date in their final earnings record.
5. Year-end: ITF 16 reconciliation must show all 50 across appropriate periods.

Answer 4

Section 79 of the Income Tax Act [Chapter 23:06] imposes personal liability on the employer for PAYE deducted but not remitted. The Employee Management register is the documentary anchor for quantifying section 79 liability.

☑ Employee Management is the master register feeding PAYE returns.

☑ Three pages: Employees (register), Earnings (income), Assessment of Employee Earnings (computation).

☑ Workflow: register → earnings → assessment → PAYE return submission (Lesson 4.2).

☑ section 79 ITA = employer personal liability for unremitted PAYE.

☑ Status changes (Active / Inactive / Former / Temporary / Contractor) drive the PAYE engine.

☑ Reconcile register against ITF 16 monthly to catch drift.

☑ Continuity: Lesson 9.2 next covers Refund Management.

──────────

TaxTami — Zimbabwe Tax Training

www.taxtami.com · info@taxtami.com