SSP registration is the creation of a user account on the Self-Service Portal at https://mytaxselfservice.zimra.co.zw — the credential a human being uses to log in. It is performed once per person, via the Sign Up function on the portal's landing page. The form first asks whether the applicant is a Zimbabwean resident or a non-resident; residents identify themselves by National Registration ID Number, non-residents by Passport Number. The remaining mandatory fields are Title, First Name, Surname, Gender, Date of Birth, Nationality, a Username unique across the SSP, Phone Number and Email Address (Middle Names optional). After submission ZIMRA verifies the data and emails a password-creation link to the registered address; following the link and setting a password completes the account, and the user can log in.

The critical conceptual point — hammered throughout this course — is that SSP registration is not taxpayer registration. Creating a login registers a person as a user; it does not create a TIN, does not register anyone for any tax head, and does not stop the 30-day clock in Section 25B of the Income Tax Act [Chapter 23:06]. Taxpayer registration is a separate, subsequent application through the Taxpayer Registration module (its own lesson). SSP registration is, however, the unavoidable precondition: no user account, no portal; no portal, no taxpayer registration, no returns, no clearance.

Because every later recovery route (password resets, verification codes) runs through the contact details captured at sign-up, the quality of this five-minute registration determines the resilience of years of subsequent access. The identity captured is also the anchor of the portal's one-person-one-login discipline — the system-level expression of the Section 5 secrecy obligation and of attributable answerability under Sections 53–61 (representative taxpayers and the public officer), as established in Logging In, Dashboard, and Switching TINs.

There is no case law on user-account creation, and this lesson says so honestly. The substance is procedure, field-by-field accuracy, the resident/non-resident branch, the verification handshake, and the error states that strand applicants — typos in the email address, identity-number mismatches, and usernames already taken.

Sourcing note: the SSP online help (https://mytaxselfservice.zimra.co.zw/help/ssp/en/default.htm) was unreachable this run; the procedure below is grounded in ZIMRA's Comprehensive Guide to the ZIMRA Self-Service Portal (External Guide). Screen-level specifics carry VERIFY flags where appropriate.

Every actor in the Zimbabwean tax system who touches the portal — the sole trader, the payroll clerk, the public officer, the tax agent with forty clients — begins identically: one Sign Up form, one verified identity, one login. The portal's entire access model (users shifting into taxpayers, assignees granted roles, agents assigned to clients) presupposes that each human node in the network is a registered, identifiable user. That is why this lesson sits this early in the course: lessons 1 and 2 described the building and the keys; this one is the locksmith's appointment.

It matters disproportionately for three audiences. New businesses, because the Section 25B registration clock is usually already running while the founders are still creating logins — delay here cascades into the Section 25C penalty exposure quantified in Introduction to TaRMS and the SSP. Employers and firms, because the one-person-one-login rule means every finance staff member and adviser needs their own sign-up before Assignee Management can grant them anything. Non-residents, because the passport-based branch is their entry point into Zimbabwean compliance (a non-resident landlord, a foreign contractor with Zimbabwean-source income, a regional firm's group accountant).

A user account is a portal construct, not a statutory creature — but four bodies of law shape it:

• Section 25B, Income Tax Act [Chapter 23:06] — the 30-day taxpayer-registration duty is the deadline that SSP registration exists to serve. The portal sequence is rigid: user account → taxpayer registration → TIN. A founder who treats sign-up as something to do "once the business settles down" is spending the Section 25B window on logistics; the Section 25C civil penalty (US$30 + US$30/day, capped at 90 days, as substituted by the Finance (No. 2) Act 7 of 2024 w.e.f. 1 January 2025) prices that delay.
• Section 5, Income Tax Act — secrecy. The verified, individual identity captured at sign-up is what makes every later act in the portal attributable to a specific person, which is the precondition for controlled, lawful access to taxpayer information.
• Sections 53–61, Income Tax Act — representation. Representative taxpayers and the public officer (Section 61) are named humans answerable for a taxpayer's compliance; the portal gives that answerability operational form by requiring those humans to exist as registered users before rights over a taxpayer can be granted to them.
• Identity documents. The National Registration ID (residents) and passport (non-residents) demanded by the form are the same identifiers ZIMRA's registration machinery uses downstream; consistency between this form and the later taxpayer-registration application is what lets ZIMRA's verification pass smoothly.

No provision prescribes the sign-up form itself — its fields are administrative practice under ZIMRA's general administration of the Acts via the Revenue Authority Act [Chapter 23:11].

C.1 What you are creating — and not creating

A person who already has an SSP account never signs up again — a director joining a second company, an accountant changing firms, an agent taking on new clients all keep the same login and acquire new grants through Assignee Management.

C.2 Before you start — what to have at hand

1. Your National Registration ID (residents) or passport (non-residents) — exactly as the document reads; the verification step matches against official records.
2. An email address you control and check — the password-creation link, all reset links and verification codes will go here. For staff registering in a work capacity, a corporate mailbox outlives personal ones.
3. A phone number in service — the second verification channel.
4. A username you intend to keep — it must be unique across the entire SSP, and it is the identity colleagues and ZIMRA support will know you by.

C.3 The procedure, step by step

1. Browse directly to https://mytaxselfservice.zimra.co.zw (never from an emailed link — the phishing discipline from Logging In, Dashboard, and Switching TINs applies from the very first contact).
2. Click Sign Up.
3. Choose the branch: Zimbabwean resident or non-resident. This selection drives the identity field — National Registration ID for residents, Passport Number for non-residents.
4. Complete the mandatory fields: - National Registration ID Number (residents) / Passport Number (non-residents) - Title - First Name - Middle Name(s) — optional - Surname - Gender - Date of Birth - Nationality - Username — unique across the SSP - Phone Number - Email Address
5. Check every field against the source document — especially the ID/passport number and the email address. A transposed digit in the ID stalls verification; a typo in the email sends your password link into the void.
6. Submit. The application goes to ZIMRA for data verification.
7. Watch the registered email inbox (and spam folder). On successful verification ZIMRA emails a password-creation link.
8. Follow the link and set a password — strong, unique, and recorded in whatever password discipline you use; ZIMRA's guidance is rotation at least annually.
9. Log in (username/email + password; complete browser verification if challenged) — you arrive at the welcome dashboard in User mode, ready for taxpayer registration or for receiving assignee rights.

C.4 The verification handshake — what can go wrong

The sign-up is not instantaneous self-service; ZIMRA verifies the submitted data before activating the account. The common failure modes:

• Identity mismatch — the name/ID combination does not match official records (maiden vs married surname, anglicised spellings, old ID formats). Cure: re-submit with the details exactly as the identity document states.
• Email never arrives — usually a typo in the address at sign-up, sometimes spam filtering. Check spam first; if the address was wrong, the application must be redone/corrected with ZIMRA support, since the portal cannot deliver credentials to an unverified alternative address.
• Username taken — choose another; usernames are unique portal-wide.
• Expired link — password-creation links do not live forever; if expired, use Forgot Password against your username/email to trigger a fresh link, or contact support.

C.5 After the account exists

Three immediate housekeeping acts, all from Logging In, Dashboard, and Switching TINs but worth restating as the close of registration:

1. Confirm your profile under Getting Started → SSP User Profile (username, phone, email correct).
2. Bookmark the portal URL — the bookmark, not emails, is how you arrive from now on.
3. Proceed to the purpose the account serves: Taxpayer Registration (if you are the taxpayer or its founder/public officer) or notify the taxpayer's administrator that you are ready to be added as an assignee (if you are staff or an adviser).

D.1 Individuals

Rudo (employee) signs up in ten minutes with her national ID and personal email. Her only real decision is the email address — she picks the one she actually reads, because in three years, when she has forgotten the password, that inbox is her way back in.

A non-resident landlord in Johannesburg with a Harare rental property takes the non-resident branch with her passport. Her sign-up is what makes everything downstream possible remotely: taxpayer registration, returns on the rental income, and payments — without a physical visit to a ZIMRA office.

D.2 SMEs

Mbare Hardware (Pvt) Ltd, newly incorporated. Correct sequence in week one: the public officer signs up (own ID, corporate email); the accountant signs up separately; the public officer completes taxpayer registration for the company (Section 25B clock managed); then Assignee Management grants the accountant her roles. Two sign-ups, two identities, zero shared passwords. The classic failure is one "admin@mbarehardware" account created with a generic mailbox and shared — it works until the first staff departure, then becomes a lockout incident in the middle of a filing month.

D.3 Large corporates, groups and practices

A tax practice onboarding forty clients does not create forty accounts — each professional has one account, and each client-taxpayer grants agent/assignee rights to the professionals who serve it. The practice's onboarding checklist therefore includes "confirm the staff member holds an SSP account" alongside bar-style identity records. Group tax functions mirror this: every member of the team registers individually (corporate emails), and the group's access matrix (lesson 2) maps users to entities. For multinationals, regional staff use the non-resident branch with passports — the portal accommodates a Lusaka-based group accountant without Zimbabwean residence.

D.4 Worked timing illustration — sign-up delay meets the Section 25B clock

Chenai incorporates her company on 1 July. The company becomes a registrable taxpayer and Section 25B gives it until 31 July to register. The founders treat portal logistics casually: sign-up attempted 20 July, fails verification on an ID mismatch, is corrected 28 July, password link followed 30 July, taxpayer registration submitted 5 August — five days late.

Exposure under Section 25C: US$30 + US$30 × 5 days = US$180 — modest here, but the same pattern stretched to the 90-day cap costs US$2,730, plus the Section 80 30% withholding bleeding from every uncleared invoice in the interim. The cure costs nothing: sign up in week one, not week three.

No Zimbabwean court has had occasion to consider SSP user registration, and this lesson does not manufacture authority. The legally proximate material remains what lessons 1 and 2 cited: Afritrade International Network v ZIMRA (2021, SC) on the answerability of the public officer — the person whose sign-up typically anchors a company's portal presence — and the secrecy and representation provisions (Sections 5, 53–61) whose discipline the verified individual identity serves. Should a dispute ever turn on whether a particular person performed an act in the portal, the registered identity behind the login would be the evidentiary starting point; that forensic value is created at sign-up.

1. Confusing sign-up with taxpayer registration — the course's recurring warning, because the consequences are priced by Section 25C. A login is not a TIN.
2. Mistyped email address. The password link, every reset, every code goes there. One character wrong and the account is stillborn — and the cure runs through ZIMRA support, not self-service.
3. Personal email for a work role. When the employee leaves, the recovery channel leaves with them. Staff registering in a professional capacity use corporate mailboxes.
4. Identity details that don't match the document. Verification matches against official records; nicknames, married/maiden inconsistencies and reformatted ID numbers stall it. Transcribe the document exactly.
5. Creating a second account because the first is forgotten. One person, one login — duplicate identities create verification conflicts. Recover the original via Forgot Password or support.
6. Shared "company" accounts. A company cannot sign up; only humans can. The company exists in the portal as a taxpayer, accessed by registered users with granted roles.
7. Signing up from an emailed link. Phishing begins before you even have a password. Type the URL.
8. Letting the password-creation link expire and abandoning the process halfway — finish the handshake the day the email arrives.

Work through the questions one at a time. Choose an answer and it is graded immediately, with an explanation and the provision it comes from. Your progress is saved, so you can stop and resume.

• SSP registration creates a login for a human, once, ever — via Sign Up at https://mytaxselfservice.zimra.co.zw: resident (National ID) or non-resident (passport) branch; mandatory identity, contact and username fields; ZIMRA verifies; password-creation link by email completes the account.
• It is not taxpayer registration. No TIN, no revenue heads, no effect on the Section 25B 30-day clock — but it is the precondition for the application that does discharge Section 25B, so do it in week one.
• The contact details captured at sign-up are the account's lifeline — every reset link and verification code routes through them; use an email you (or the corporation) will still control in five years, and transcribe identity documents exactly.
• One person, one login — companies exist in the portal as taxpayers, never as users; staff and advisers each sign up individually and receive authority through Assignee Management/agent assignment (Sections 5, 53–61 discipline).
• Anticipate the handshake's failure modes — spam folders, typos, identity mismatches, expired links — and their cures, before a deadline makes them expensive.
• No case law exists on sign-up; its legal weight is downstream, in the attributability of everything the account later does.

Resident vs non-resident sign-up

Sign-up to working access

flowchart TD
 A[Go directly to mytaxselfservice.zimra.co.zw] --> B[Click Sign Up]
 B --> C{Resident or non-resident?}
 C -->|Resident| D[National ID + personal details]
 C -->|Non-resident| E[Passport + personal details]
 D --> F[Username, phone, EMAIL - check every character]
 E --> F
 F --> G[Submit - ZIMRA verifies data]
 G --> H{Password email received?}
 H -->|Yes| I[Follow link - set strong password]
 H -->|No| J[Check spam - confirm status with support - correct details]
 J --> G
 I --> K[Log in - User mode dashboard]
 K --> L{Purpose?}
 L -->|Own or company affairs| M[Taxpayer Registration - TIN, Section 25B clock]
 L -->|Staff or adviser| N[Receive assignee or agent rights]
 M --> O[Taxpayer mode - work begins]
 N --> O

Statutes & sections

• Income Tax Act [Chapter 23:06] — Section 25B (30-day taxpayer-registration duty the sign-up enables); Section 25C (civil penalty US$30 + US$30/day, 90-day cap; Finance (No. 2) Act 7 of 2024 w.e.f. 1 Jan 2025); Section 25D (liability independent of registration); Section 5 (secrecy — the rationale for verified individual identities); Sections 53–56, 61 (representative taxpayers; public officer).
• Revenue Authority Act [Chapter 23:11] — ZIMRA's administration, under which the portal and its account practices operate.

Case law

• None on SSP user registration (stated honestly). Context: Afritrade International Network v ZIMRA (2021, SC) — public officer answerability (Income Tax Course).

ZIMRA guidance

• Comprehensive Guide to the ZIMRA Self-Service Portal — ZIMRA External Guide, Getting Started → SSP Registration (field list, resident/non-resident branch, verification and password-link flow; primary procedural source).
• ZIMRA SSP online help — https://mytaxselfservice.zimra.co.zw/help/ssp/en/default.htm (unreachable this run; verification turnaround, link validity and password rules flagged for verification).