Tax debt management in Zimbabwe is now conducted inside software. The assessment that creates the debt, the ledger that records it, the statement that proves it, the demand that follows it, the instalment plan that restructures it and the garnishee that collects it all originate in ZIMRA's Tax and Revenue Management System (TaRMS) and its public face, the Self-Service Portal (SSP) at https://mytaxselfservice.zimra.co.zw. This lesson teaches the legal infrastructure beneath that technology and the practical operation of its debt-facing modules. The statutory spine is Part VIIIA of the Income Tax Act [Chapter 23:06] (Sections 80B–80L, inserted by the Finance Act 12/2006 w.e.f. 1 January 2007) and its mirror, Part XA of the VAT Act [Chapter 23:12] (Sections 68A–68I): together they authorise the Commissioner to establish computer systems for tax administration (Section 80D; VAT Section 68C), regulate registered users, user agreements and digital signatures (Sections 80E–80G), make electronic data admissible evidence with "due evidential weight" (Section 80C; VAT Section 68B, applied in PIL (Pvt) Ltd v ZIMRA 17-HH-213), deem electronic retention to satisfy statutory record-keeping (Section 80H), fix when electronic communications are sent and received (Section 80I), and criminalise misuse of digital signatures and falsification of electronic records (Section 80L — fines up to level 12 or 10 years' imprisonment).

Two later insertions complete the statutory platform. Section 80DD (Finance Act 1/2018) mandates the Virtual Tax Management System — the legislative name for what taxpayers experience as TaRMS — with rules to be prescribed by the Minister under Section 90; the VAT twin, Section 68CC (Finance (No. 2) Act 10/2022), mandates the Virtual Fiscalisation System. Section 80FF (Finance Act 2/2017, backdated to 1 January 2017) lets the Commissioner compel any self-assessment taxpayer to become a registered user, on pain of a civil penalty of US$1,000 per day (capped at 181 days) and, for continued default, a criminal offence — digital onboarding is not optional for the modern taxpayer.

On the VAT side, technology is also how the debt is detected. The fiscalisation regime — the requirement that every registered operator use a fiscalised electronic register or fiscal memory device — is anchored in the Section 2 definition, the substituted definition of "tax invoice" as a fiscal tax invoice printed by such a device (Finance Act 7/2021, w.e.f. 1 January 2022), the Section 63A offences (Finance Act 13/2023: failure to issue or retain fiscal invoices, dealing in unapproved devices, and tampering with an electronic fiscal device — up to level 14 or 5 years), the VAT (General) Regulations SI 273/2003 Sections 22A and 23 (compulsory cash registers and their functional specifications, including a six-year English-language record), and the 50% input-tax-style deduction for the cost of acquiring a fiscalised register under the renumbered paragraph (j) of Section 15(3). The devices stream transaction data to ZIMRA — the operational system known publicly as the Fiscalisation Data Management System (FDMS) — so output tax debts are computed from data ZIMRA already holds.

The money-movement layer is regulated too: Section 4B of the Finance Act [Chapter 23:04] (Finance (No. 2) Act 10/2022, tightened by Act 7/2024 w.e.f. 1 January 2025) obliges an approved financial intermediary to credit the Consolidated Revenue Fund within 24 hours of a taxpayer's payment, on pain of interest of 15% (USD amounts) or bank policy rate + 5% (local currency). And the price of being a debtor in the system is interest: for income tax, at the rate fixed by the Income Tax (Rate of Interest) Notice SI 212/2022; for VAT, at the rates in the Fifth Schedule to SI 273/2003 as substituted by SI 25/2025 (gazetted 19 March 2025) — bank policy rate + 5% for local-currency amounts and 10% for foreign-currency amounts.

Practically, the lesson maps the SSP's sixteen modules onto the debt lifecycle, concentrating on the five that matter most to debt work: Taxpayer Accounting (assessment notices, the Summary Report and Tax Type Report — the automated statements), Payments (the Single Account, ZIMRA's unified multi-head USD/ZiG ledger whose oldest-debt-first allocation rules routinely surprise taxpayers; currencies never net against each other), Debt Management (Overdue Debts, Instalment Plan applications — lodge them before the due date), Case Management (electronic objections under Section 62) and Notifications. Worked USD computations cover VAT interest at the confirmed rates, the Section 80FF civil-penalty exposure, the 50% fiscalised-register deduction, and a Single Account misallocation scenario. The continuity anchors are the TaRMS Essentials lessons (tarmsintroduction, tarmslogin) for portal mechanics, and the debt lessons already completed — this lesson supplies the technology layer that those lessons assumed.

Until the TaRMS go-live, Zimbabwean tax debt lived in fragmented ledgers: a legacy e-services platform, manual Business Partner Number accounts, paper assessments, physical queues at regional offices. The practical consequences for debt management were predictable — taxpayers learned of arrears late, payments were misposted, statements took weeks to obtain, and ZIMRA's collectors worked from incomplete pictures. The Tax and Revenue Management System replaced that landscape with a single back-end ledger per taxpayer, surfaced through the Self-Service Portal. As the Introduction to TaRMS & the Self-Service Portal lesson established, the SSP user (a natural person with login credentials) is distinct from the taxpayer (the legal person whose affairs are managed); a user "shifts" into a taxpayer to act, and the portal's sixteen modules then expose everything from registration to refunds.

Why does a debt course need a technology lesson? Because every stage of the debt lifecycle taught in this course now has a digital form, and the digital form changes the legal and practical analysis:

• Debt creation is digital: the self-assessment return filed through the SSP is the assessment (Section 37A(10)–(11)), so the moment of upload is the moment a debt exists.
• Debt recording is digital: the Single Account is the authoritative ledger, and its allocation rules — not the taxpayer's intentions — decide which liability a payment extinguishes.
• Debt notification is digital: assessment notices, demand letters and debt-management alerts arrive in the Notifications module (and by configured email forwarding), which reframes every "I never received the notice" argument.
• Debt restructuring is digital: instalment plans are applied for, granted and monitored in the Debt Management module — the electronic expression of the Section 71(1) instalment power examined in Attachment and Sale of Property and the queued Payment Plans and Instalments lesson.
• Debt enforcement is digital: garnishee targets are identified from disclosure notices and account data (Sections 60–60B, extending to crypto wallets and professional custodians since the Finance Act 13/2023), the ITF 263 compliance check that strangles a debtor's commerce runs as an automated real-time query, and the Section 79 certificate that wins the recovery case is generated from the electronic ledger, with Section 80C / VAT Section 68B guaranteeing the admissibility of the underlying data.
• Debt detection is digital: fiscal devices stream sales data to ZIMRA, and the VAT debt is increasingly computed from ZIMRA's own data rather than the taxpayer's say-so.

The lesson therefore proceeds in two movements: first the law of the platform (Part VIIIA and its VAT mirror, fiscalisation, payment-rail regulation, interest instruments), then the operation of the platform (the SSP modules mapped to the debt lifecycle). The examiner's interest lies in both: candidates are routinely asked where the legal authority for electronic assessments and signatures comes from, what evidential status a TaRMS print-out enjoys, and how a payment made "for VAT" can lawfully end up settling old PAYE.

B.1 Part VIIIA — "Application of Information Technology to Act" (Sections 80B–80L)

Part VIIIA was inserted by the Finance Act 12/2006 w.e.f. 1 January 2007 — Zimbabwe legislated for electronic tax administration well before the systems existed to exploit it. Walk the sections in order:

Section 80B (interpretation). The definitions are broad by design: "computer" covers any electronic, magnetic or optical data-processing device including connected input/output, storage and communication facilities; "electronic data" covers information "stored internally in the memory of the computer or represented in any form (including computer printouts, magnetic optical storage media, punched cards or punched tapes)"; "electronic record or communication" includes microfilm and computer-generated microfiche. Two definitions carry operational weight: "registered user" (a person registered under Section 80F) and "digital signature" (an electronic signature created by computer, intended by the registered user and accepted by the Commissioner to have the same effect as a manual signature, complying with Section 80G(1)). Note the housekeeping quirk: a duplicate "80B" inserted by the Finance Act 1/2014 was renumbered by the editor as Section 80A1 (payments to non-resident artistes), which sits in Part VIII — do not confuse the two.

Section 80C (electronic data as evidence). Admissibility of electronic data "shall not be denied — (a) on the sole ground that it is electronic data; or (b) if it is the best evidence that the person adducing it can reasonably be expected to obtain, on the grounds that it is not in original form" (Section 80C(1)), and such data "shall be given due evidential weight" (Section 80C(2)). Weight is assessed against the reliability of generation, storage and communication, the integrity-maintenance of the data, and the identification of the originator (Section 80C(3)). For debt work this is the provision that lets ZIMRA prove a debt from the TaRMS ledger and lets a taxpayer prove payment from electronic records — it cuts both ways. The VAT mirror, Section 68B, was applied in PIL (Pvt) Ltd v ZIMRA 17-HH-213, where electronically derived information was held admissible.

Section 80D (establishment of computer systems). The Commissioner "may, notwithstanding anything to the contrary in this Act, establish and maintain a computer system for the purpose of applying information technology to any process or procedure under this Act", expressly including the despatch, receipt and processing of "any return, record, assessment, declaration, form, notice, statement or other document relating to any amount liable to tax" and "the electronic processing of any register, book, account, record, return, paper, assessment or other document". This is the umbrella authority for TaRMS and the SSP. The "notwithstanding" formula matters: wherever an older provision assumes paper, Section 80D overrides it.

Section 80DD (Virtual Tax Management System). Inserted by the Finance Act 1/2018 w.e.f. 14 March 2018: "For the purposes of creating an electronic platform to enable the electronic recording by taxpayers of transactions that may be liable to tax under this Act (to be known as the Tax Management System), the Minister shall in regulations made under section ninety prescribe the rules to be followed by taxpayers using the Tax Management System." The section is the statutory naming of the platform taxpayers now know as TaRMS, and the mandate ("shall … prescribe") for its operating rules.

Section 80E (user agreements). The Commissioner may prescribe the user agreement between ZIMRA and registered users, which must set out the terms of communication (approved equipment classes; the allocation of digital signatures; the user's duty to secure them), the manner of affixing a digital signature, the Commissioner's reasonable access to the user's computer system for verification and audit, and the manner and period of electronic record-keeping. The agreement is contractual scaffolding around the statute — and clause (c) (audit access to the user's own system) is routinely overlooked by taxpayers who sign it.

Section 80F (registration of users; suspension and cancellation). No person may communicate with the Commissioner through a Section 80D system unless a registered user (Section 80F(1)). The Commissioner approves applicants who will make regular use, will protect their digital signature, will safeguard data integrity and will maintain reliable systems (Section 80F(3)). Registration may be suspended or cancelled on listed grounds — breach of the user agreement, false statements, failure to make regular use, contravention of the Act, conviction of a tax or dishonesty offence, sequestration or liquidation, or cessation of the relevant business (Section 80F(4)) — but only after notice, reasons, and a reasonable opportunity to respond (Section 80F(5)): a statutory audi alteram partem that supports review of arbitrary lock-outs. For a debtor, the liquidation ground matters: insolvency can sever the company's own digital access just as the liquidator (as representative under Section 53(1)(b)) needs it.

Section 80FF (compulsory registration). Inserted by the Finance Act 2/2017 (backdated to 1 January 2017): the Commissioner may by written notice require any taxpayer who renders a self-assessment return to become a registered user (Section 80FF(1)–(2)). Default attracts a civil penalty of US$1,000 (or the level-four maximum, whichever is the lesser) for each day of default, capped at 181 days, waivable where the contravention was not wilful or negligent (Section 80FF(3)(a), figures as amended by Acts 13/2019, 10/2020, 7/2021 and 13/2023); continued default thereafter is a criminal offence (fine up to level 10 or 6 months) (Section 80FF(3)(b)). Critically for this course, the civil penalty order is itself "a debt due by the infringer to the Zimbabwe Revenue Authority", recoverable "in a court of competent jurisdiction by proceedings in the name of the Authority" (Section 80FF(4)) and is paid into ZIMRA's own funds (Section 80FF(5)) — a tax-adjacent debt created purely by refusing to digitise.

Section 80G (digital signatures). A valid digital signature must be unique to the registered user and under his sole control, capable of verification, linked to the data such that compromised integrity invalidates the signature, and conformant with the Commissioner's prescribed requirements (Section 80G(1)). The Commissioner allocates signatures on registration — for natural persons, to the user and nominated employees; for entities, to each nominated employee (Section 80G(2)). In SSP practice the "signature" is experienced as credentials plus the submission act; the legal analysis still runs through Section 80G.

Section 80H (electronic retention). Any statutory record-retention requirement — most importantly the six-year, English-language books-and-records rule in Section 37B — is deemed satisfied by electronic retention if the information remains accessible and usable, is kept in (or demonstrably faithful to) its original format, and preserves origin, destination and timestamp details. Read with VAT Regulations Section 23(b) (cash registers must store entries in English for at least 6 years), the retention rules are format-neutral but integrity-strict.

Section 80I (sending and receipt). The attribution and timing code: an electronic communication is attributed to the originator if sent by him, by his authorised agent, or by a system programmed on his behalf to operate automatically (Section 80I(1)); acknowledgment rules (Section 80I(2)–(3)) include the trap that where the parties agreed communications bind only on acknowledgment, an unacknowledged communication is deemed not to have been sent; lodgement occurs when the communication enters a system outside the originator's control (Section 80I(4)); receipt occurs when it enters ZIMRA's computer (taxpayer→ZIMRA) or the stipulated place (ZIMRA→user) (Section 80I(5)); an electronic signature on a return or notice has effect as if affixed in manuscript (Section 80I(6)); and the Commissioner may permit Internet submission generally (Section 80I(7)) — the subsection under which browser-based SSP filing operates. For deadline disputes (was the return filed by midnight on the due date?), Section 80I(4)–(5) supplies the legal answer: the timestamp of entry into ZIMRA's system.

Section 80J (obligations, indemnities, presumptions). The user must report a compromised signature without delay (Section 80J(1)); ZIMRA bears no liability for the user's security failures and may treat pre-notification communications as authorised (Section 80J(2)); and in any proceedings it is presumed, absent contrary proof, that a digital signature was used with the consent and authority of the registered user (Section 80J(3)). This presumption is the legal reason the password-hygiene sermons in the SSP guide matter: the employee who shares credentials is, presumptively, bound by whatever was filed with them.

Section 80K (alternatives). When the system is inoperative, the user and Commissioner revert to written communication "in the manner prescribed in this Act" (Section 80K(1)), and the Commissioner may at any time require original documents (Section 80K(2)). Downtime is thus not an excuse for silence — the paper route revives.

Section 80L (offences). Unauthorised use of another's digital signature: fine up to level 12 or 10 years' imprisonment or both (Section 80L(1)); making or falsifying electronic records, or dishonestly/fraudulently making, affixing signatures to, transmitting or executing electronic records (or causing another to do so): the same maxima (Section 80L(2)). These sit alongside the general offences in Sections 81–83 and the fiscal-device offences in VAT Section 63A.

B.2 Part XA of the VAT Act (Sections 68A–68I) and Section 68CC

Part XA, inserted by the same Act 12/2006, replicates the income-tax provisions for VAT: Section 68A definitions, Section 68B electronic evidence (PIL 17-HH-213), Section 68C computer systems (the list expressly adds "receipt, invoice, bill of entry, credit or debit note" — the VAT paper-trail), Section 68D user agreements, Section 68E registered users, Section 68F digital signatures, and the sending/receipt, presumption and offence provisions completing the Part. Section 68CC (Finance (No. 2) Act 10/2022) mandates the Virtual Fiscalisation System — the statutory platform for electronic recording of VAT-able transactions, with rules to be prescribed under Section 78. The parallelism is deliberate: one taxpayer, one portal, two mirrored statutory regimes.

B.3 The fiscalisation regime: detecting the VAT debt at source

Fiscalisation converts the point of sale into a reporting node, with this statutory architecture:

• Section 2 definition: a "fiscalised electronic register" is "an electronic sales register having such features as may be prescribed" (substituted by Finance (No. 2) Act 8/2014).
• The "tax invoice" definition (substituted by Finance Act 7/2021 w.e.f. 1 January 2022): a tax invoice means a fiscal tax invoice provided by a registered operator "and printed by a fiscalised electronic register or fiscal memory device used by a registered operator for the purpose of section twenty". Input tax claims under Section 15(2) hinge on holding a tax invoice — so since 2022, a non-fiscal invoice is not a tax invoice, and the buyer's input deduction is at risk. This single definitional change made fiscal compliance a commercial requirement between traders, not merely a ZIMRA obligation.
• VAT (General) Regulations SI 273/2003, Section 22A (inserted by SI 106/2004): all registered operators "shall be required to use cash registers for the purposes of accounting for value added tax", subject to Gazette exemptions; and Section 23: the register must print sales slips with a back-up master audit roll, store all entries in English for at least 6 years, produce daily readings, split sales by tax category (exempt / zero-rated / standard-rated), display entries to the customer, and print slips carrying date/time, the operator's names and VAT registration number, and the values before and after tax. (The commencement controversy around SI 40/2017's purported amendment of the regulations was among the arguments ventilated in VSL (Pvt) Ltd & 3 Ors v ZIMRA 19-HH-023.)
• Section 63A (inserted by Finance Act 13/2023 w.e.f. 29 December 2023) — the offences: (a) failing to issue a fiscal tax invoice/receipt or to retain a copy for 24 months (level 7 or 6 months); (b) failing to produce a fiscal invoice to an officer on demand within 12 months (level 7 or 6 months); (c) manufacturing, selling or distributing fiscal memory devices without Authority approval under Section 78 regulations (level 14 or 5 years); (d) a registered (or registrable) operator who "deliberately tampers with an electronic fiscal device with the result that it fails faithfully to record any transactions" (level 14 or 5 years).
• Section 15(3), renumbered paragraph (j): a deduction of 50% of the cost of acquisition of fiscalised electronic registers — the legislature splitting the hardware cost with the operator.
• Objection rights: Section 32 includes, among objectable decisions, "any decision of the Commissioner implementing or interpreting regulations made under section seventy-eight in connection with fiscalised electronic registers, and any assessments of amounts of tax due arising from the operation of such registers" (inserted by Act 1/2014) — taxpayer protection for device-generated assessments.
• The devices transmit data to ZIMRA's fiscal data platform (operationally branded FDMS), enabling invoice-matching in the SSP's Invoice Management module and pre-population/verification of VAT 7 figures.

For debt management the significance is upstream: fiscalisation moves VAT debt detection from audit (years later) to data (real time). The under-declared output tax that once surfaced in a Section 31 estimated assessment after an audit now surfaces as a discrepancy between FDMS data and the VAT 7 — and ripens into an assessment, penalty (Section 39(2): 100%) and interest with far shorter lag.

B.4 The payment rails and the price of delay

Finance Act Section 4B (inserted by Finance (No. 2) Act 10/2022; tightened by Act 7/2024 w.e.f. 1 January 2025): a taxpayer may pay any revenue debt through an approved financial intermediary (a bank holding a Commissioner-General account); the intermediary must credit the Consolidated Revenue Fund within 24 hours (shortened from 48), failing which it owes interest of 15% (USD amounts) or bank policy rate + 5% (local currency) on the unremitted amount. The provision protects the taxpayer's position: the payment date for the taxpayer is when he pays the intermediary, and the float risk is the bank's.

Interest on the taxpayer's own arrears is rate-set by statutory instrument:

The Fifth Schedule's history is itself a lesson in rate volatility: SI 53/2021 had pegged the local-currency rate at 25% before the current policy-rate-plus-5% formula — always read the current instrument.

B.5 The digital-asset enforcement provisions (Sections 60–60B)

Covered in depth in Representative Taxpayers and Attachment and Sale of Property, but note their technology character here: the Finance Act 13/2023 rewrote Section 60 to reach professional custodians, safety-deposit receptacles and — through the Section 53 definitions — digital assets and crypto wallets; Section 60(3) plugs ZIMRA into the Financial Intelligence Unit's temporary freezing orders under Section 41A of the Bank Use Promotion Act [Chapter 24:24]; Section 60A warrants compel decryption; and Section 60B (Finance (No. 2) Act 7/2024, w.e.f. 1 January 2025) bars credit above US$20,000 in 12 months to juristic persons or trustees without a valid ITF 263 — conscripting the credit-information system into tax enforcement. Tax debt enforcement now assumes the debtor's wealth may be digital, and legislates accordingly.

This section maps the debt lifecycle onto the technology, module by module, defining each artefact a practitioner will actually touch.

C.1 Identity: SSP user, taxpayer, TIN and assignees

Recall from tarmsintroduction: an SSP user registers personally (national ID or passport, unique username, verified email); a taxpayer is separately registered through the Taxpayer Registration module and receives a Taxpayer Identification Number (TIN) — the successor to the legacy Business Partner Number — used on every return, certificate and ledger entry. One user may represent many taxpayers, "shifting" between them; Assignee Management lets the taxpayer grant other users defined roles (read-only viewer, return preparer, return submitter, payment authoriser) and is the governance perimeter the Section 80J(3) presumption enforces: whatever is submitted under a user's credentials is presumed authorised. The debt-management corollary: when arrears litigation looms, who had submission rights and when becomes an evidential question, answerable from the assignee audit trail.

C.2 Debt creation: e-filing and the return-as-assessment

Returns are filed in Tax Return Management: Pending Tax Returns lists every expected return with its deadline; forms open pre-populated, compute subtotals automatically, accept attachments (input-tax schedules for the VAT 7, capital-allowance schedules for the ITF 12C), and move on submission to Waiting for Approval status (amendable while there). The legal consequence is the one this course keeps returning to: under Section 37A(10)–(11), the self-assessment return is the assessment, deemed served on the later of due date and filing date. The SSP submission timestamp — legally fixed by Section 80I(4)–(5) — is therefore the birth certificate of the debt. Returns the system expected but never received surface as outstanding-return flags that block the ITF 263 and invite estimated assessments under Section 45 / VAT Section 31.

C.3 Debt recording: the Single Account and its allocation rules

The Single Account is the conceptual heart of TaRMS debt management: one unified ledger per taxpayer across all revenue heads, in both USD and ZiG, recording every assessment and every payment. Two rules drive most practical disputes:

1. Payments are allocated, not directed. A payment lands in the Single Account and is then applied by ZIMRA's allocation rules — typically oldest debt first within a tax type, then by tax-type priority — not by the taxpayer's intention. The SSP guide's own warning bears repeating: a payment intended for VAT can be absorbed by an old PAYE shortfall, leaving the VAT unpaid and accruing the Section 39 penalty (100%) and interest. The defence is hygiene: keep all heads current, reconcile monthly, and raise allocation queries through E-Messaging immediately.
2. Currencies never net. USD and ZiG balances are segregated; a USD liability cannot be settled from a ZiG credit. This is the ledger expression of the dual-currency return regime (Section 37AA; VAT Section 38(4)–(4a): tax collected in foreign currency is payable in foreign currency — Delta Beverages 23-HH-577; Inamo Investments 23-SC-096). A taxpayer can simultaneously be in credit (ZiG) and in enforceable arrears (USD).

C.4 Automated statements: Taxpayer Accounting

The Taxpayer Accounting module is the statement engine: Assessment Notices (every liability assessment in a date range), Audit Assessment Notices (post-audit assessments, separately sequenced), the Summary Report (net balance per tax type for the range) and the Tax Type Report (drill-down of every assessment, payment and adjustment). These are the "automated statements" of this lesson's title, and three professional uses follow: (a) monthly reconciliation of the Summary Report to the client's ledger — discrepancies signal either an unallocated payment or an un-noticed assessment whose 30-day objection clock may already be running; (b) debt due diligence — the Tax Type Report is the factual record for negotiating instalment plans or contesting interest runs; (c) evidence — under Section 80C/68B these system outputs are admissible, and the Section 79 / VAT Section 42 certificate that wins ZIMRA's recovery case is distilled from exactly this ledger. The taxpayer who keeps contemporaneous exports of these reports holds the same evidential raw material.

C.5 Overdue debt and instalment plans: the Debt Management module

The Debt Management module has four pages: Overdue Debts (every liability assessment in arrears for the period), Instalment Plan (plans agreed with ZIMRA), Instalment Applications (pending/approved applications) and Drafts. The legal substrate is Section 71(1) (tax payable "in 1 sum or in instalments of equal or varying amounts as may be determined by the Commissioner, having regard to the circumstances of the case" — Mayor Logistics 14-CC-007 noting instalments as the system's relief valve) and, for interest relief in special circumstances, the Section 71(2) proviso (MR Bank 19-HH-779; MAN 20-HH-078). The SSP guide's tactical advice deserves statutory framing: lodge the instalment application before the due date. ZIMRA is more receptive to restructuring tax not yet overdue; pre-due-date engagement also strengthens any later argument for the interest-free extension and forestalls the automated escalations (garnishee selection, clearance denial) that trigger on overdue status. The full law of payment plans is the queued Payment Plans and Instalments lesson; here, note simply that the application channel is electronic and time-stamped — the practitioner's diligence is verifiable, and so is its absence.

C.6 Disputes and engagement: Case Management, E-Messaging, Notifications

Three communication modules complete the debt picture, and confusing them has legal consequences:

• Case Management is where formal Section 62 objections (and VAT Section 32 objections — including, since Act 1/2014, objections to fiscalised-register decisions and device-generated assessments) are created, submitted and tracked. The 30-day window runs from the assessment notice; the SSP objection is the "writing" with "grounds specified in detail" that Section 62(3) demands (GC 15-HH-759).
• E-Messaging is correspondence — allocation queries, instalment follow-ups, clarification requests. It is not the objection channel; a detailed grievance sent by e-message does not stop the Section 62 clock.
• Notifications is where TaRMS pushes assessment notices, refund approvals, certificate availability, audit findings, debt-management alerts and payment confirmations, in both User and Taxpayer modes. Because receipt rules (Section 80I(5)) and the practicalities of deadline-running attach to these notices, the guide's instruction to configure email forwarding is risk management, not convenience.

And around all of it sits pay now, argue later: the electronic objection no more suspends the electronic debt than its paper ancestor did (Section 69(1); VAT Section 36; Mayor Logistics 14-CC-007).

C.7 Enforcement automation: clearance, garnishee, recovery

The enforcement instruments taught in earlier lessons run on this same data:

• The ITF 263 application (Taxpayer Certificates module) triggers an automated real-time compliance check across every revenue head — outstanding returns or unpaid balances surface as gaps to close. The certificate's denial is the system's first economic sanction on a debtor (Section 80: counterparties withhold 30%; Section 80A: licensing gates; Section 60B: credit bar).
• Garnishee selection (Section 58; VAT Section 48) is informed by the disclosure infrastructure (Sections 60–60A) and executed against accounts the system already knows; the appointment needs no prior notice (CARS 17-HH-110) and is a collection mechanism, not an objectable decision (Packers International 16-SC-028).
• Recovery litigation is fed by the ledger: the Section 79 / VAT Section 42 certificate is conclusive (Trek Petroleum 17-SC-056), the underlying electronic data admissible (Section 80C; PIL 17-HH-213), and the merits barred (Section 78(2)). The only door — validity review (Paperhole 24-HH-149, itself a TaRMS-era assessment struck down for taxing gross income) — is unaffected by the medium.
• One boundary on digital evidence-gathering: under Section 44(8), officers inspecting business premises without a warrant may take print-outs or copies of information, but Hilmax Enterprises 22-HH-832 held this does not authorise carting away the laptop itself — the power is over information, not hardware.

C.8 Confidentiality and security in the digital ledger

A debt ledger this centralised raises the mirror-image concern: who may see it? The answer remains Section 5 of the Income Tax Act — the preservation of secrecy provision examined in Administration of Income Tax — which binds every officer to confidentiality regarding taxpayer affairs, subject to the statutory gateways (the Minister under Section 5(3); the Financial Intelligence Unit under Section 5(3a)), with criminal sanctions for breach (Section 5(5)/(5a)). The technology provisions integrate with rather than dilute this: the Section 80E user agreement obliges the user to protect credentials; Section 80J(2) immunises ZIMRA against losses flowing from the user's own security failures; and the Section 60 custodian-disclosure machinery overrides private secrecy obligations (banking confidentiality, custody contracts) while immunising the complying custodian — a one-way valve that lets data flow toward ZIMRA but not outward. On the taxpayer's side of the screen, the SSP guide's security-housekeeping rules are the practical implementation: individual logins, strong rotated passwords, quarterly assignee reviews, deliberate logout on shared devices, and — most relevant to debt practice — scepticism toward emails purporting to be ZIMRA. Phishing campaigns mimic ZIMRA correspondence; genuine system messages surface inside the Notifications module, so the practitioner's verification habit ("does this alert also appear in the portal?") is both a fraud control and a record. A debtor whose bank-account details were fraudulently altered before a refund withdrawal faces an uphill battle if his own credential hygiene enabled the change — confirm the banking details visible under Taxpayer Information before every withdrawal request.

C.9 Old regime, new regime: what actually changed for the debtor

Because TAXTAMI lessons always contrast prior and current law, close the conceptual treatment with the before/after that matters to a debtor and his adviser:

Two things did not change, and candidates should say so crisply: the substantive law of the debt (charge, assessment, due date, interest, penalty, objection, pay-now, recovery — every provision this course has taught), and the discretions (instalments, extensions, remissions) that humans at ZIMRA still exercise. The technology compresses timelines and perfects ZIMRA's record; it neither enlarges nor shrinks the taxpayer's substantive rights. That is precisely why the practitioner's value has migrated toward speed and hygiene: deadlines arrive electronically and run mercilessly, but the remedies are unchanged for the adviser quick enough to use them.

C.10 The design logic

Why legislate the platform at all, rather than simply build it? Three reasons emerge from the text. Evidence: Sections 80C/68B pre-empt best-evidence objections that would otherwise dog every ledger print-out. Attribution: Sections 80G–80J make filings and signatures bind the taxpayer with manuscript force, presumptively authorised — without which every e-return invites repudiation. Compulsion: Sections 80FF and 25C-type civil penalties, the fiscal-invoice definition, and the Section 60B credit bar make participation in the digital system commercially unavoidable. The debt-management payoff is a ledger that is simultaneously the operational record, the demand engine and the trial bundle.

D.1 The individual: the consultant who ignored her Notifications

Scenario. Rudo, a self-employed consultant, filed her 2024 ITF 12C through the SSP but underpaid her fourth QPD. TaRMS flagged the shortfall; a debt-management alert and an assessment notice landed in Notifications → Taxpayer Notifications in February 2025. Rudo had not configured email forwarding and did not log in until August 2025, by which time interest had run for six months and the balance had been selected for garnishee.

Teaching points. (1) The notice was received when it entered the stipulated electronic place (Section 80I(5)); non-reading is not non-receipt. (2) Her 30-day objection window (Section 62) ran from the assessment notice — by August it was long closed, leaving only a late-objection plea on "reasonable grounds" (Section 62(2)) — and the garnishee needed no warning at all (CARS 17-HH-110). (3) Had she logged in in February, the Debt Management module would have accepted an instalment application against a not-yet-escalated debt. The technology did not change her rights; it changed the speed at which inaction consumes them.

Interest exposure (structure; income-tax rate flagged). Shortfall USD 4,000; Section 71(2) interest from due date at the SI 212/2022 rate (); at any illustrative rate the lesson is that interest accrues daily on a ledger she could see at any time — the Summary Report is date-parameterised precisely so a taxpayer can quantify arrears as at today.

D.2 The SME: fiscalisation, the 50% deduction, and a misallocation story

Scenario A — fiscalising the shop. Tariro Retail (Pvt) Ltd, newly VAT-registered, buys an approved fiscalised electronic register for USD 1,200.

Failure to fiscalise at all is no longer a paperwork lapse: since 1 January 2022 Tariro's customers cannot claim input tax on non-fiscal invoices (the "tax invoice" definition), business buyers will refuse to trade, and Section 63A adds criminal exposure — including 5 years for device tampering.

Scenario B — the misallocated payment. Tariro owes June 2025 VAT of USD 6,000 (due 25 July) and has an old, forgotten PAYE shortfall of USD 3,500. On 24 July it pays USD 6,000 "for VAT" via e-banking.

The remission door (Section 39(5)) may open — the State suffered no net loss if the PAYE was equally due — but remission is discretionary (VSL 19-HH-023); prevention (reconcile the Summary Report monthly; clear all heads) is cheaper than cure. Note the rate discipline: a ZiG VAT debt would instead bear bank policy rate + 5% (Fifth Schedule para 1, as substituted by SI 25/2025).

Scenario C — the digital refusenik. Tariro's sister company, served with a Section 80FF notice to become a registered user, ignores it for 60 days beyond the grace period:

Waiver is available where default was neither wilful nor negligent (Section 80FF(3)(a) proviso) — but sixty days of ignored written notice is a hard waiver case. The computation shows why "we prefer paper" is now among the most expensive sentences in Zimbabwean tax practice.

D.3 The large corporate: governance of the digital tax function

For a group, the technology issues are governance issues. Assignee Management must mirror the delegation-of-authority matrix: preparers cannot submit, submitters cannot authorise payments, leavers are removed the day they exit (quarterly review at minimum, per the SSP guide) — because Section 80J(3) presumes that whatever was filed under live credentials was authorised. Dual-currency reconciliation is a monthly board-pack item: USD and ZiG ledgers per entity, no netting, with VAT collected in foreign currency payable in foreign currency (VAT Section 38(4); Delta Beverages 23-HH-577). Fiscal data consistency is an audit-defence item: the FDMS stream, the VAT 7 and the financial statements must tell one story, because ZIMRA's case begins from its own data. And the ITF 263 renewal cycle (apply October–November through Taxpayer Certificates) is a treasury-critical path: a lapsed clearance triggers 30% withholding across the contract base (Section 80) and, since 1 January 2025, the Section 60B credit bar above US$20,000 — for a leveraged group, a covenant event. The multinational's incremental burden is integration: aligning group ERP tax engines with SSP filing formats and retaining records to the Section 80H integrity standard across systems.

D.4 The payment rail: who bears the float? — a Section 4B computation

Scenario. On 25 June 2026 (the VAT due date), Nyasha Foods (Pvt) Ltd pays its June VAT of USD 20,000 through its bank, an approved financial intermediary holding a Commissioner-General account (Finance Act Section 4B(2)). A processing failure at the bank delays the credit to the Consolidated Revenue Fund by 12 days.

The practice point: keep the proof of payment to the intermediary (the e-banking confirmation, itself admissible electronic data under Section 80C). If the Single Account shows the liability still open days later, the Section 4B analysis — not a penalty concession — is the answer, raised through E-Messaging with the proof attached.

D.5 The e-objection deadline: a timing scenario

Scenario. An audit assessment notice for USD 35,000 lands in Chiedza Mining's Taxpayer Notifications on Friday 6 March 2026 at 16:45. The finance manager is on leave; the notice is read on 30 March. The objection is drafted and submitted through Case Management on Saturday 4 April at 22:10; ZIMRA's server logs entry at 22:11.

The analysis assembles the whole lesson: receipt of the notice occurred on 6 March when it entered the stipulated electronic place (Section 80I(5)) — the leave roster is irrelevant; the 30-day objection window (Section 62, as taught in Tax Disputes and Debt Collection) therefore ran from that notice; the submission lodged when it left the taxpayer's control and was received on entry into ZIMRA's system on 4 April (Section 80I(4)–(5)) — within the window, and the weekend filing is effective because the electronic channel does not close; the electronic submission with detailed grounds satisfies the Section 62(3) writing requirement, the credentials operating as the manuscript-equivalent signature (Section 80I(6)); and throughout, the USD 35,000 remains payable (Section 69(1)), so the parallel move is an instalment application in Debt Management lodged the same evening. One habit — same-day attention to Notifications — would have bought 24 extra drafting days.

Technology-specific authority is thin — the platform is young — but the source Acts annotate these directly relevant decisions:

• PIL (Pvt) Ltd v ZIMRA 17-HH-213 (High Court). Annotated at VAT Section 68B: electronically derived information is admissible; the section means what it says. Significance: the evidential foundation for ledger print-outs, fiscal-device data and system records in assessment and recovery proceedings.
• VSL (Pvt) Ltd & 3 Ors v ZIMRA 19-HH-023 (High Court). Among the issues: arguments on the validity of SI 40/2017's purported amendment to the commencement of the VAT (General) Regulations (the fiscalisation-adjacent Part), alongside the Section 39 penalty jurisprudence. Significance: subsidiary instruments implementing the technology regime are themselves contestable — practitioners should check the vires of the SI before conceding a device-era penalty.
• Hilmax Enterprises (Pvt) Ltd v ZIMRA 22-HH-832 (High Court). The warrantless Section 44(8) premises power authorises taking information (print-outs, copies) — not seizure of the computer itself. Significance: the physical/digital boundary of ZIMRA's search powers; hardware seizure needs the warrant route (Section 44(7); Section 60A for decryption).
• Central African Road Services (Pvt) Ltd v ZIMRA 17-HH-110 and ZIMRA v Packers International (Pvt) Ltd 16-SC-028. The garnishee — now selected and executed through system data — requires no prior notice and is not objectable as if an assessment. Significance: automation has made the remedy faster, but its legal character was settled before TaRMS existed.
• Trek Petroleum (Pvt) Ltd v ZIMRA 17-SC-056 and Paperhole Investments (Pvt) Ltd v ZIMRA & 2 Ors 24-HH-149. The conclusive Section 79 certificate, and its limit: an invalid assessment (there, tax on gross income) supports nothing built on it. Significance for the digital era: garbage in, conclusive garbage out is not the law — system-generated assessments must still be assessments in law, and review remains available.
• Delta Beverages (Pvt) Ltd v ZIMRA 23-HH-577; Inamo Investments (Pvt) Ltd v ZIMRA 22-HH-672, on appeal 23-SC-096; Prosperous Days Investments v ZIMRA 21-HH-024 (VAT Section 38(4)). The foreign-currency payment obligation that the Single Account's currency segregation operationalises. Significance: the ledger's refusal to net USD and ZiG is statute, not software preference.
• Mayor Logistics (Pvt) Ltd v ZIMRA 14-CC-007; MR Bank Ltd v ZIMRA 19-HH-779; MAN Ltd v ZIMRA 20-HH-078. Pay-now-argue-later and the Section 71 instalment/extension discretions — the legal content behind the Debt Management module's screens.

No reported Zimbabwean decision in the source materials yet construes Part VIIIA's signature presumptions (Section 80J(3)) or the Section 80FF penalty; until one does, the statutory text governs and the practitioner argues from it directly. Foreign electronic-evidence authority exists but is non-binding and is not relied on here.

1. Treating Notifications as optional. Assessment notices and debt alerts are received when they enter the system (Section 80I(5)); the 30-day objection clock and interest run regardless of login frequency. Configure email forwarding; diarise deadlines outside the portal.

2. Sharing SSP credentials. One login per human, always. Section 80J(3) presumes filings under your signature were authorised by you; the shared password converts a rogue submission into your return. Assignee Management exists precisely so delegation is granted, scoped and revocable.

3. Paying without reconciling. Directing a payment "to VAT" does not bind the Single Account's allocation rules; old debts in any head absorb new money (oldest first). Reconcile the Summary Report monthly and clear all heads — or watch a fresh 100% Section 39 penalty grow on a liability you thought you had paid.

4. Netting currencies in your head. A ZiG credit does not pay a USD debt. Treasury must fund each currency stream; the dual-ledger discipline traces to Section 37AA and VAT Section 38(4), not to ZIMRA stubbornness.

5. Objecting in the wrong module. E-Messaging correspondence — however detailed — is not a Section 62 objection. Formal objections go through Case Management, in writing, with detailed grounds, within 30 days. The deadline analysis is unchanged from the paper era (debtdisputes).

6. Assuming downtime suspends obligations. Section 80K revives the written channel when the system is inoperative; it does not suspend due dates. Document the outage (screenshots, helpdesk references) to support any special-circumstances plea, and file on paper if the deadline cannot wait.

7. Fiscalisation as an afterthought. Trading on non-fiscal invoices destroys your customers' input claims (the 2022 "tax invoice" definition), invites Section 63A prosecution, and guarantees a data mismatch when FDMS-derived figures meet your VAT 7. Conversely, claim the 50% acquisition deduction (Section 15(3)(j)) — it is routinely forgotten.

8. Ignoring a Section 80FF notice. At up to US$1,000/day for 181 days, refusal to digitise is a self-inflicted debt — and one recoverable by ZIMRA in its own name (Section 80FF(4)).

9. Waiting until arrears to seek instalments. The Debt Management module accepts applications before due date; ZIMRA's receptiveness, the interest-free-extension argument (Section 71(2) proviso) and the avoidance of automated escalation all favour the early application.

10. Forgetting the audit-access clause. The Section 80E user agreement gives the Commissioner reasonable access to your computer system for verification. Records retention to the Section 80H integrity standard (accessible, format-faithful, origin/timestamp preserved) is a live contractual and statutory duty — six years, in English (Section 37B; VAT Regs Section 23(b)).

11. Trusting the screen over the statute. The SSP displays balances, deadlines and statuses, but the law fixes liabilities and time limits. If the portal erroneously shows a return as not due, the Section 37/37A obligation still exists; if it understates a balance, Section 79 conclusiveness will eventually attach to the corrected ledger, not the screenshot. Conversely, where the system's output is wrong in the taxpayer's favour and ZIMRA later corrects it, the Section 47 reopening limits (6 years; unlimited on fraud/misrepresentation/wilful non-disclosure) govern — the medium changes nothing. Export and retain dated copies of what the portal showed: under Section 80C they are admissible evidence of the state of the ledger at the time, which is exactly what a "practice generally prevailing" or estoppel-flavoured argument needs as its factual base.

12. Letting the tax agent's access outlive the mandate. Taxpayers who change advisers frequently forget the Tax Agent Assignment page. A former agent with live permissions can still see the ledger (a confidentiality breach waiting to happen) and, worse, filings made under their credentials bind the taxpayer through the Section 80J(3) presumption. Termination of the engagement letter must be accompanied, the same day, by revocation in Assignee Management — and the revocation timestamp is itself the taxpayer's protection in any later dispute about who filed what.

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.

• The platform is legislated, not just built: Part VIIIA ITA (Sections 80B–80L, FA 12/2006) and Part XA VAT (Sections 68A–68I) supply the authority (Section 80D/68C), the identity layer (users, agreements, digital signatures, Sections 80E–80G), the evidence rules (Section 80C/68B; PIL 17-HH-213), the timing code (Section 80I) and the offences (Section 80L); Section 80DD names the Virtual Tax Management System (TaRMS) and Section 68CC the Virtual Fiscalisation System.
• Digital participation is compulsory in practice: Section 80FF notices carry US$1,000/day civil penalties (cap 181 days) that are themselves recoverable debts; the 2022 fiscal-invoice definition makes non-fiscalised trading commercially toxic; Section 60B conscripts the credit system.
• The Single Account is the debt: one multi-head, dual-currency ledger; payments allocated oldest-first, never directed; USD and ZiG never net. Reconcile the Summary/Tax Type Reports monthly — they are both your statement and ZIMRA's trial bundle (Section 79; Section 80C).
• Debt-facing modules map to statutory powers: Debt Management = Section 71(1) instalments (apply before due date); Case Management = Section 62/VAT Section 32 objections (not E-Messaging); Notifications = Section 80I receipt; Taxpayer Certificates = the automated ITF 263 gate behind Section 80/80A/60B.
• Interest is instrument-specific: income tax per SI 212/2022; VAT per the Fifth Schedule to SI 273/2003 as substituted by SI 25/2025 — bank policy rate + 5% (local), 10% (foreign currency); intermediaries owe 15% USD / policy+5% on remittance delay (FA Section 4B).
• Fiscalisation moves detection upstream: regs 22A/23 compel the devices; Section 63A criminalises evasion of them (tampering: 5 years); Section 15(3)(j) funds half the hardware; objection rights protect against device-generated assessments.
• Old doctrines survive the new medium: pay-now-argue-later (Mayor Logistics), no-notice garnishees (CARS), conclusive certificates (Trek), validity review (Paperhole), and the information-not-hardware limit on warrantless digital seizure (Hilmax).
• Policy insight: legislating evidence, attribution and compulsion — rather than merely deploying software — is what converts a taxpayer portal into an enforcement architecture; the debtor's ledger, demand and proof are now the same artefact.

Comparison table 1 — the mirrored IT provisions

Comparison table 2 — SSP modules mapped to the debt lifecycle

Diagram — the electronic debt lifecycle

flowchart TD
 A[SSP user registers Section 80F
user agreement Section 80E
digital signature Section 80G] --> B[Taxpayer registered - TIN issued]
 B --> C[E-filing via Tax Return Mgmt
return = assessment Section 37A]
 C --> D[Single Account ledger
USD and ZiG - no netting]
 D --> E{Paid in full by due date?}
 E -->|Yes| F[Balance clear - ITF 263 auto-approved]
 E -->|No| G[Interest runs
SI 212/2022 / Fifth Sched SI 25/2025]
 G --> H[Notifications: debt alert
received on entry Section 80I-5]
 H --> I{Taxpayer engages?}
 I -->|Instalment application
Debt Management module| J[Plan per Section 71-1
possible interest-free extension]
 I -->|Objection via Case Management| K[Section 62 within 30 days
pay now argue later Section 69]
 I -->|Silence| L[Escalation: ITF 263 denied
Section 80 30% WHT - Section 60B credit bar]
 L --> M[Garnishee Section 58 / VAT Section 48
no prior notice]
 M --> N[Recovery action
Section 79 certificate + Section 80C e-evidence]
 N --> O[Judgment - writ - attachment
see debtattachment lesson]
 J --> F
 K --> E2{Objection outcome}
 E2 -->|Allowed| F
 E2 -->|Disallowed| E

flowchart TD
 P[Sale rung up at till] --> Q[Fiscalised electronic register
regs 22A and 23 - fiscal tax invoice Section 2 def]
 Q --> R[Data streamed to ZIMRA fiscal platform
operationally FDMS - VERIFY name]
 R --> S[Invoice Management matching
buyer input tax depends on fiscal invoice]
 S --> T{VAT 7 figures match device data?}
 T -->|Yes| U[Return accepted - debt as declared]
 T -->|No| V[Discrepancy - Section 31 assessment
Section 39 100% penalty + interest]
 V --> W[Objection Section 32 incl device decisions
or debt enters Single Account lifecycle]

Statutes & sections

• Income Tax Act [Chapter 23:06] — Part VIIIA Sections 80B (definitions), 80C (electronic evidence), 80D (computer systems), 80DD (Virtual Tax Management System, FA 1/2018), 80E (user agreements), 80F (registered users; suspension with audi), 80FF (compulsory registration; US$1,000/day civil penalty cap 181 days; debt due to the Authority — FA 2/2017 as amended), 80G (digital signatures), 80H (electronic retention), 80I (sending/receipt/attribution; Internet filing), 80J (indemnities; authority presumption), 80K (fallback to writing), 80L (offences — level 12/10 years); Sections 37A (return as assessment), 37AA (dual-currency returns), 37B (6-year English records), 44(7)–(8) (search powers; Hilmax limit), 51 (notice), 58 (garnishee), 60–60B (custodian disclosure; crypto receptacles; FIU freezing; special warrant; US$20,000 credit bar), 62 (objections), 69 (pay now), 71 (due dates; instalments; SI interest), 79 (conclusive evidence).
• Value Added Tax Act [Chapter 23:12] — Section 2 (definitions: "fiscalised electronic register"; "tax invoice" = fiscal tax invoice, sub FA 7/2021 w.e.f. 1 Jan 2022); Section 6 (charge), Section 15(3) renumbered para (j) (50% fiscal-register deduction); Section 28–29 (returns/payment), Section 31 (assessments), Section 32 (objections incl. fiscalised-register decisions, Act 1/2014), Section 36 (pay now), Section 38–38A (payment; foreign currency; double-tax civil penalty), Section 39 (100% penalty; interest; remission), Section 42 (conclusive evidence), Section 48 (agent), Section 63A (fiscalisation offences, FA 13/2023), Part XA Sections 68A–68I (IT application), Section 68CC (Virtual Fiscalisation System, FA(No.2) 10/2022).
• Finance Act [Chapter 23:04] — Section 4B (24-hour intermediary remittance; 15% USD / bank policy + 5% interest; FA(No.2) 10/2022, amended Act 7/2024 w.e.f. 1 Jan 2025).
• Value Added Tax (General) Regulations, SI 273/2003 — Section 22A (compulsory cash registers, SI 106/2004); Section 23 (register requirements: master audit roll; 6-year English storage; daily readings; tax-category split; slip contents); Fifth Schedule (rates of interest — substituted SI 75/2010, SI 283/2019, SI 53/2021, SI 25/2025: local currency = bank policy rate + 5%; foreign currency = 10%).
• Income Tax (Rate of Interest) Notice, SI 212/2022 — interest on unpaid income tax (percentage to be verified).

Case law

• PIL (Pvt) Ltd v ZIMRA 17-HH-213 — electronic data admissible under VAT Section 68B.
• VSL (Pvt) Ltd & 3 Ors v ZIMRA 19-HH-023 — Section 39 penalties; validity arguments on SI 40/2017 (regulations commencement).
• Hilmax Enterprises (Pvt) Ltd v ZIMRA 22-HH-832 — Section 44(8) reaches information (print-outs), not the hardware.
• Central African Road Services (Pvt) Ltd v ZIMRA 17-HH-110 — garnishee without prior notice.
• ZIMRA v Packers International (Pvt) Ltd 16-SC-028 — garnishee a collection mechanism, not objectable.
• Trek Petroleum (Pvt) Ltd v ZIMRA 17-SC-056 — Section 79 certificate conclusive.
• Paperhole Investments (Pvt) Ltd v ZIMRA & 2 Ors 24-HH-149 — invalid assessment supports nothing; validity review survives the digital era.
• Delta Beverages (Pvt) Ltd v ZIMRA 23-HH-577; Inamo Investments (Pvt) Ltd v ZIMRA 22-HH-672 / 23-SC-096; Prosperous Days Investments v ZIMRA 21-HH-024 — foreign-currency VAT payment (Section 38(4)).
• Mayor Logistics (Pvt) Ltd v ZIMRA 14-CC-007 — pay-now-argue-later constitutional; instalments the relief valve.
• MR Bank Ltd v ZIMRA 19-HH-779; MAN Ltd v ZIMRA 20-HH-078 — Section 71(2) proviso extension discretion.
• GC (Pvt) Ltd v ZIMRA 15-HH-759 — detailed grounds requirement for objections (Section 62(3)).

ZIMRA guidance

• Comprehensive Guide to the ZIMRA Self-Service Portal (TaRMS/SSP, https://mytaxselfservice.zimra.co.zw) — the 16 modules; Single Account allocation rules; Debt Management, Taxpayer Accounting, Payments, Case Management, Notifications workflows; security housekeeping.
• Comprehensive Guide to the ITF 263 — the automated clearance compliance check.
• Comprehensive Guide to the VDA01 Voluntary Disclosure Application — e-filed through Audit Management.
• Zimbabwe Tax Compliance Calendar — the due-date grid the SSP's Pending Tax Returns page operationalises.

Outstanding verification flags

• SI 212/2022 income-tax interest percentage(s); the Section 90 regulations prescribing TaRMS rules (Section 80DD); the current level-4 standard-scale maximum (Section 80FF alternative cap).
• "FDMS" as the operational name of the fiscal data platform (ZIMRA publications; not in the source Acts).
• Current Gazette exemptions, device-approval lists and interface specifications under VAT Section 78 regulations.