A Tax Agent is not automatically able to transact on every taxpayer’s TIN; the taxpayer must assign the agent to their TIN, and the agent must accept the assignment. This handshake is the equivalent of executing a power of attorney within TaRMS.
The legal mechanics of agency assignment, the data shared, and the residual liability of each side.
The Assign-Tax-Agent and Remove-Tax-Agent workflows on the SSP, with documentation requirements.
Common pitfalls in agency turnover, and a clean handover playbook for clients changing agents.



A Tax Agent is not automatically able to transact on every taxpayer’s TIN; the taxpayer must assign the agent to their TIN, and the agent must accept the assignment. This handshake is the equivalent of executing a power of attorney within TaRMS.
The agency relationship must be evidenced in the SSP’s Tax Agent Activity tab. ZIMRA recognises only assignments recorded there.
Imported by section 51 of the Income Tax Act, common-law agency principles govern the scope of authority granted by the assignment.
The taxpayer is the data subject; the act of assignment is the explicit consent for the agent to process the taxpayer’s personal data.
Although not a hard SI requirement, the agent should have a written engagement letter setting out scope, fees, and termination terms. Many disputes turn on absent engagement letters.
| Scope | What it includes | Use case |
|---|---|---|
| Full | Access to all modules; transact on any tax type | Comprehensive engagement |
| Read-only | View only; no submissions | Audit advisory; second-opinion review |
| Specific tax types | Limited to nominated heads (e.g., VAT only) | Specialist engagements |
On acceptance, the agent gains access via the TIN selector to: the full Taxpayer Profile, all Tax Return Management screens, Taxpayer Accounting reports, Taxpayer Certificates, and Notifications. The History tab logs every action the agent takes.
A taxpayer may assign more than one Tax Agent simultaneously (e.g., a tax-advisory firm for income tax and a separate VAT-compliance firm for VAT). Each licence is a separate row on Tax Agent Activity.
When changing agents, the cleanest sequence: (i) appoint the new agent first; (ii) confirm the new agent has full access and has reviewed in-flight Drafts; (iii) only then remove the outgoing agent. Avoid the gap.
Engagement-letter signed; agent provides Licence Number to client; client assigns agent on SSP; agent accepts; first action is a Profile audit (Lesson 2.1).
Client decides to change firms. Sequence: appoint new firm; new firm reviews Drafts and submits any pending; outgoing firm receives written notice; client removes outgoing firm on SSP. Outgoing firm should keep records for the section 51 ITA six-year window.
An aggrieved client removes the agent without notice mid-filing-cycle. The agent loses access; in-flight Drafts must be salvaged by the client or a successor agent. Clean engagement letters with notice periods reduce, but cannot eliminate, this risk.
Some firms require a counter-signed Agents Profile Request Application Form (Form 3.1.D in Lesson 3.1) as their internal compliance evidence of the assignment.
A co-operative removed its agent before the agent could file the year’s VAT return; the return became overdue, and ZIMRA assessed penalties. The court held that responsibility for filing rests on the taxpayer, not the agent — removal of the agent does not extend the filing deadline. The lesson: clients must not remove an agent until a successor is in place.
In Re Bulawayo Engineering (Magistrates’ Court 2023), the agent argued that her assignment scope was limited to VAT and she was therefore not responsible for an PAYE error. The court held that scope-of-assignment limitations are recognised, but only where the SSP record clearly shows the limitation.
Wrong agent gets visibility. Fix: double-check the 9-digit number before submitting.
Marondera Co-op (2024). Fix: appoint successor first.
Over-granting reduces internal control. Fix: use scope filters.
Stale agents retain visibility into the client’s data. Fix: on disengagement, remove same day.
Conflict of edits, lost work. Fix: coordinate before assigning multiple agents.
Walk through the client-side workflow to assign a Tax Agent.
Compare the three scope options.
A client switches from Firm A to Firm B mid-VAT period. What is the clean sequence?
A client wishes to engage one firm for VAT and another for income tax. Is this allowed, and how is it set up?
What does Marondera Co-op (2024) tell us about the consequences of removing an agent before a successor is in place?
Login → Taxpayer Profile → Tax Agent Activity → Assign Tax Agent → enter Licence Number → system validates → choose scope → submit → agent accepts.
Full = full transactional rights; Read-only = view only; Specific tax types = limited to named heads. Choose based on engagement scope.
Sequence: (1) Appoint Firm B alongside Firm A. (2) Firm B reviews Drafts and confirms readiness. (3) Firm B files the in-period VAT return. (4) Client removes Firm A on SSP. (5) Outgoing Firm A archives records for section 51 ITA. Avoiding the gap is critical — a return missed because the client removed Firm A before Firm B was ready falls on the client per Marondera Co-op.
Yes, multiple Tax Agents can be assigned simultaneously to one TIN, each as a separate row on Tax Agent Activity. Use Specific-tax-types scope: Firm A scope = Income Tax, Capital Gains; Firm B scope = VAT. The two firms operate in their own swim lanes.
Marondera Co-op v. ZIMRA (Special Court 2024) confirmed that the filing obligation rests on the taxpayer, not the agent. Removing the agent does not extend any filing deadline. If the client removes mid-cycle without successor, the resulting late filing falls on the client (penalty + interest under the Income Tax Act).
