The single largest practical change TaRMS made to the life of a compliant Zimbabwean taxpayer is this: the Tax Clearance Certificate (ITF 263) is no longer something a human officer decides to give you — it is something the system computes you have earned. On the Self-Service Portal, the ITF 263 application is, in the local guide's words, "automated to a large extent: the SSP runs a real-time compliance check across every revenue head and either approves immediately or surfaces the gaps to be closed first." The dedicated ITF 263 guide confirms the flow end to end: navigate Taxpayer Certificates → Tax Clearance Certificate, select New Application or Renewal, verify the pre-populated identity fields, confirm the revenue-head registration ticks, update bank details, and Submit — whereupon the SSP checks ZIMRA's own records of returns and payments for each registered head. If everything is up to date, the certificate is issued immediately; if not, a Compliance Status panel lists each missing return or payment, the taxpayer cures the gaps from Tax Return Management and Payments, and re-runs the application.

The legal engine has not changed and was established in the Certificates lesson: Section 80 of the Income Tax Act [Chapter 23:06] obliges every paying officer of the State, a statutory body, a quasi-Governmental institution or a registered taxpayer to withhold 30% of payments under contracts totalling US$1,000 or more in the year of assessment (Finance Act 13/2023) unless the payee produces a valid ITF 263. The withheld 30% is a provisional credit, not a penalty — but the working-capital damage of receiving 70 cents in the dollar for months is the real sanction. Around that core, Section 80A conditions trade, professional and vehicle licensing on a clearance "valid no earlier than 30 days before its production" (FA 2024), and Section 60B bars credit above US$20,000 to corporates and trustees without one (FA(No.2) 7/2024). The certificate, normally valid to 31 December, is applied for in the October–November renewal window and can be revoked mid-year the moment compliance lapses — which is why the ITF 263 guide instructs paying customers to verify the certificate's current status before each payment through the portal's verification facility, not merely file the PDF at onboarding.

What this lesson adds to the Certificates lesson is the anatomy of the automatic pathway itself: what the real-time check actually tests (the compliance grid, head by head — ITF 16, monthly P2 returns and PAYE payments, VAT 7 returns and payments, withholding-tax returns and payments, PT4, QPDs, ITF 12B and the prior year's income tax return and payment); how the Compliance Status panel converts a refusal into a worklist; how immediate issuance changes renewal strategy (apply early — the check is free and repeatable); and how automation re-allocates risk — the certificate now tracks the truth of the ledger in near-real time, so the only durable clearance strategy is continuous month-by-month compliance, with the certificate as a by-product. The companion lesson that follows covers the manual clearance route — the exception path where automation cannot decide.

For decades the tax clearance was a paper ritual. The taxpayer completed the ITF 263 form, a ZIMRA Checking Officer worked through Section 4 of the form — the "For office use" grid — ticking off every return filed and every payment made in the look-back period, handed the form back if anything was missing, and a Supervisor countersigned the approval that authorised issue. The ITF 263 guide preserves this architecture in its walkthrough of the form because the form still exists — but it records the decisive shift: hard-copy submission is now accepted "only by exception, at the ZIMRA office where the taxpayer is registered," and on the SSP the process "is largely automated — ZIMRA's system checks each revenue head against its own records and either approves the certificate immediately or surfaces the outstanding items that need to be resolved first."

This lesson is about that automated pathway — automatic tax clearance — as a process you can plan around. Three framing points:

1. The decision criteria did not change; the decision-maker did. "Up to date on every registered revenue head" was always the test. What automation changed is latency (an immediate answer instead of a queue), consistency (the grid is applied identically every time), and transparency (the system tells you exactly which item blocks you, via the Compliance Status panel).
2. The certificate is now downstream of the ledger. The real-time check reads the same records you see in Taxpayer Accounting (Summary Report, Tax Type Report) and Tax Return Management (Pending Tax Returns). If those modules show you clean, clearance follows mechanically; if they show a gap, no application technique will help — only curing the gap will.
3. Automation cuts both ways. The same real-time machinery that issues in seconds also supports mid-year revocation when compliance lapses during the validity period, and supports counterparty verification of current status. A certificate is no longer a year-long talisman; it is a continuously testable claim.

Where this sits in the course: the Certificates lesson introduced the Taxpayer Certificates module (two pages — Certificates and Certificate Requests), walked Section 80 clause by clause and established the compliance grid. This lesson deep-dives the automatic issuance pathway; the next lesson covers the manual clearance exception route. The returns lessons (Return Submission, PAYE Return, Back-Filing) supply the cure mechanics the Compliance Status panel will send you to.

No section of either Act prescribes "automatic" issuance — the automation is administrative. What the statutes supply is (1) the withholding mechanism that makes the certificate valuable, (2) the gateway provisions that consume it, and (3) the compliance obligations the real-time check tests. The first two were walked in earlier lessons and are summarised, not re-taught.

B.1 Section 80 — the 30% engine (established in the Certificates lesson)

Section 80 of the Income Tax Act defines a "contract" as any agreement under which the State, a statutory body, a quasi-Governmental institution or a registered taxpayer is obliged to pay one or more persons US$1,000 or more in a year of assessment (threshold per Finance Act 13/2023), excluding employment contracts, sales effected in shops in the ordinary course of business, and specified agricultural deliveries (GMB; small-scale gold deliveries). Where a contract falls within the definition, the paying officer must withhold 30% of the gross payment unless the payee produces a valid ITF 263; the withheld amount is remitted to ZIMRA and stands as a provisional credit against the payee's eventual income tax. The paying officer who fails to withhold is personally exposed. Production of a valid certificate switches the payment to gross — which is why the ITF 263 guide calls the certificate "the only routine way to receive payments at gross."

B.2 The gateway companions: Section 80A and Section 60B

As walked verbatim in the Agent Licence lesson, Section 80A conscripts other regulators: operators' licences, mining locations, shop and tourist-facility licences (Section 80A(2)), company incorporation (Section 80A(3)), and — since FA 2024 (gazetted 28 October 2024) — nine professions (architects, engineers, land surveyors, legal practitioners, auditors/accountants, health professions, veterinarians, estate agents, quantity surveyors) cannot be certified, registered, licensed or renewed without a tax clearance "valid no earlier than 30 days before its production" (Section 80A(4)), plus the ZINARA/vehicle-insurance gate (Section 80A(5)). Section 60B (FA(No.2) 7/2024, w.e.f. 1 January 2025) bars credit above US$20,000 in any 12 months to corporates and trustees without clearance, on pain of a 5% civil default and a level-14 fine for the lender. The practical meaning for this lesson: the output of the automatic check is consumed not only by paying customers but by licensing authorities, professional bodies, banks and the vehicle-licensing system. A failed automatic check now propagates much further than one withheld invoice.

B.3 The compliance grid — the obligations the check tests

The ITF 263 guide's Section 4 walkthrough lists exactly what is tested over the look-back period (described as "typically the past 12 to 24 months"):

The guide's rule is categorical: "If any of these is outstanding, ZIMRA will not issue the ITF 263 until the gap is closed. The remedy is to file the missing return and pay any amount due, together with any penalty and interest, before the ITF 263 application proceeds." As the Certificates lesson put it, the compliance grid is the compliance calendar restated — every deadline taught in the returns lessons reappears here as an issuance condition.

B.4 Validity, renewal and revocation

Confirmed from the ITF 263 guide: the certificate is issued by the Commissioner-General to a taxpayer "in good standing with all tax obligations," is normally valid for one calendar year expiring 31 December — "though shorter periods may be issued where compliance has been irregular or where a renewal is conditional on outstanding items" — and renewal should be applied for before expiry, the historical window running from October. Mid-year revocation is express: ZIMRA may revoke during the validity period on triggers including failure to file a P2 or VAT 7 due during the year, failure to pay a QPD, or a material under-declaration discovered on audit; revocation takes effect from the date of the revocation notice, and "customers are expected to verify the certificate's status before each payment, not just rely on the original issue."

C.1 The application flow, step by step

The ITF 263 guide's SSP procedure (its Section 8), confirmed:

1. Log in to https://mytaxselfservice.zimra.co.zw (and shift into the correct taxpayer — the User/Taxpayer mode discipline from the login lesson).
2. Navigate to Taxpayer Certificates → Tax Clearance Certificate.
3. Select New Application (first ITF 263) or Renewal (subsequent years).
4. Verify the pre-populated header fields: registered legal name (not the trade name — the guide flags using the trade name as a classic error), trade name, company registration number (or National ID for a sole trader), date of incorporation/registration/birth, and the TIN (the SSP will not accept the application without it; the TIN replaces the legacy BPN shown on older printed forms). The header is drawn from the taxpayer profile — and as the Taxpayer Profile lesson established, ZIMRA cross-checks the application against that profile, so stale profile data delays clearance. Fix the profile first, by application, then apply.
5. Confirm the revenue-head registration ticks — Yes/No against VAT (registered under VAT Section 23? threshold currently US$25,000), PAYE (employees → 13th Schedule employer), income tax (every business taxpayer), presumptive tax (26th Schedule regimes), withholding taxes (the taxpayer's role as withholding agent, not its own subject-to-WHT receipts — a distinction the guide flags expressly). Ticking "Yes" for a head you are not registered on triggers a query; the system cross-checks against ZIMRA's records.
6. Bank details: the refund account — bank, branch and code, account type, account number; where the taxpayer holds both USD and ZiG accounts, list both, because refunds are made in the currency of the overpayment (the never-net doctrine again). For a company the application is signed by the public officer (Section 61); for a trust, the trustee or representative; for a sole trader, the taxpayer in person.

7. Submit — and the system takes over: "The SSP runs an automated check against ZIMRA's records of returns and payments for each revenue head."

8. Branch A — immediate issue: "If everything is up-to-date, the certificate is issued immediately" and appears in the module; download the PDF and share with customers. The certificate carries the TIN and registered name, a unique certificate number, the validity period start and end dates, and a QR/verification code for portal verification.

9. Branch B — the Compliance Status panel: "If something is outstanding, the SSP shows a Compliance Status panel listing each missing return or payment. Resolve each item from the relevant module (Tax Return Management, Payments) and re-run the application."

C.2 What "real-time" means — and what it does not

The check is real-time against ZIMRA's records, which produces four planning consequences:

• The check is repeatable and effectively free. Unlike the paper era — where each resubmission meant another queue — a failed automatic check costs nothing but the time to cure. The rational strategy is to apply early (October, per the renewal window) precisely because a failure in October leaves two months of cure time before the 31 December expiry, while a failure discovered on 5 January is already bleeding 30%.
• The check tests ZIMRA's ledger, not your in-house records. A payment made but mis-allocated (the Single Account misallocation cascade from the Taxpayer Account Management lesson), or a return submitted but still in Waiting for Approval, may or may not register as compliant at the moment of the check. The safe sequence: reconcile the Summary Report before applying, so the check confirms what you already know.
• Processing lag is no longer an excuse — or a shield. In the paper era, a certificate issued in January might rest on a December snapshot. The automated check's currency means a gap that arises today can block — or revoke — today. The certificate has become a rolling attestation.
• Automation decides only what it can read. Where the records are genuinely in dispute — a contested assessment under objection, an instalment plan in good standing, a migration gap from the old-period lesson — the binary check may refuse even though the taxpayer's position is defensible. That borderland is the territory of manual clearance, the next lesson; for now, note that the existence of an exception route is implied by the guide's own statement that hard-copy submission survives "by exception."

C.3 The cure loop: converting the Compliance Status panel into a worklist

The Compliance Status panel is the automated successor to the Checking Officer "handing the application back with a note identifying the gap." Operationally it is a triage list, and the returns arc supplies the cure for each entry type:

1. Missing return, liability nil → file the nil return now (Section 28(2)/Packers; Section 37A(2)) — the cheapest cure on the panel, always first.
2. Missing return, liability owed → back-filing discipline (one period, one return, oldest first), then pay with penalty and interest — the guide is explicit that the gap is closed only when the return is filed and the amount due "together with any penalty and interest" is paid.
3. Missing payment on a filed return → Payments module, New Payment, correct currency (per-currency P2 discipline from the PAYE lesson; allocation will go oldest-first).
4. Disputed item → do not pay blind: an assessment you contest belongs in Case Management (30-day objection clock) — but recall pay-now-argue-later (Section 69; VAT Section 36) means disputing does not, of itself, clean the grid. An instalment plan lodged via Debt Management in good standing preserved clearance in the Debt Engagement lesson's framework — the interaction between a live plan and the automatic check is exactly the sort of nuance routed to the manual lesson.
5. Re-run the application after each tranche of cures; repeat until Branch A.

C.4 Verification and revocation: the certificate as a live object

Two design features close the loop:

• Counterparty verification. The ITF 263 guide describes a verification facility — "a verification module under Public Verification → Tax Clearance Certificate that takes the certificate number and returns Valid / Invalid" — and instructs the paying officer to verify before paying without withholding, and to withhold 30% if the certificate is expired, revoked, or the taxpayer "has subsequently fallen out of compliance." For your own receipts, the mirror discipline: assume sophisticated customers re-verify at every payment run, so a mid-year lapse is discovered by your customers in real time, not at renewal.
• Mid-year revocation, effective from the notice. Because revocation operates from the date of the revocation notice, there is no retroactive unwinding of gross payments already received — but every payment after notice reverts to the 70% regime. The notification lands in Notifications (configure email forwarding — the Notifications doctrine from the introduction lesson), so an unwatched mailbox can mean weeks of unwitting non-coverage while customers' verifications fail.

C.5 The strategic inversion: clearance as a by-product

Pre-automation, taxpayers "applied for" clearance as an annual event and cleaned up beforehand. Automation inverts this: since the check reads the live ledger, the only strategy that reliably produces a certificate on demand — and keeps it alive all year — is the monthly compliance routine (the rhythm lesson later in this course): P2 by the 10th, VAT 7 by the 15th, QPDs on their dates, monthly Summary Report reconciliation. The certificate stops being a project and becomes a by-product. The corollary for advisers: an ITF 263 problem is never really an ITF 263 problem — it is a returns problem, a payments problem or a profile problem wearing the certificate's clothes, and it is cured in those modules, not in the Certificates module.

D.1 Individual / sole trader: the consultant's October ritual

Rudo, a self-employed engineering consultant (income tax + QPDs only, no employees, below the VAT threshold), bills corporate clients — all registered taxpayers, all above the US$1,000 annual contract threshold, so all obliged to withhold 30% absent her ITF 263.

• Early October she reconciles: ITF 12C for the prior year filed in April (Section 37A, 4 months), QPDs 1–3 paid (10%, 25%, 30% on 25 March/June/September). She applies — Renewal — and the check passes: immediate issue, validity to 31 December of the coming year.
• Compare her colleague Tafara, who applies on 6 January having missed QPD 4 (20 December). The panel lists the QPD; he pays it (with interest from the due date) on 10 January and re-runs to issue. But two clients ran their January payment cycles on the 8th: on invoices of USD 9,000, USD 2,700 was withheld. Recoverable as a credit at year-end — but gone from cash flow for over a year. Fourteen days of delay, priced.

D.2 SME: the Compliance Status panel as a worklist

Pamberi Hardware (Pvt) Ltd (VAT, PAYE, income tax, withholding-agent head) applies for renewal on 15 October. The panel returns three items: the September P2 (USD payroll) unfiled; the August VAT 7 filed but USD 1,950 unpaid; the prior-year ITF 16 bundle not generated.

• Cure order: nil-cost items first is the back-filing doctrine, but here all three cost something. The P2: file (13th Sched para 3(1) — the 10th has passed, so the remittance carries exposure to the para 10 tax-plus-equal-further-amount regime and interest; remission under para 11 needs the no-intent narrative minuted). The VAT: pay USD 1,950 + interest (Fifth Schedule rates, SI 25/2025 — 10% on foreign currency). The ITF 16s: generate from Employee Management and reconcile ΣP2 = ΣITF 16 (the year-end identity from the PAYE lesson).
• Re-run on 22 October: issue. Total cost: the principal it always owed, plus interest, plus penalty exposure managed through remission — versus the counterfactual of a January lapse on roughly USD 60,000 of monthly receipts: USD 18,000 per month locked at 30%. The panel, treated as a worklist, is the cheapest audit Pamberi will ever get.

D.3 Large corporate: clearance as a continuous control

Mukonde Holdings (multiple entities, treasury function) treats clearance as a control, not an application: each entity's ITF 263 validity is on the compliance dashboard; the monthly close includes a Summary Report reconciliation per entity before the 10th/15th deadlines; October renewal is diarised with a two-week cure buffer; accounts payable verifies every supplier's certificate at each payment run (the verification module — and Section 80 personal exposure for paying officers makes this non-optional); and the group's bank-facility covenants now interact with Section 60B, so a lapsed certificate can technically freeze drawdowns above US$20,000. One subsidiary's missed VAT 7 in June triggers mid-year revocation; because Notifications forward to the tax manager's mailbox, the revocation is caught the same day, the return filed, and re-issue sought before the month-end payment cycles — the difference between a one-day and a one-month 30% bleed across the group's debtor book.

Stated honestly: there is no reported Zimbabwean case on the SSP's automated issuance, the Compliance Status panel, or mid-year revocation mechanics. The certificate's case-law hinterland is thin and contextual:

• Sabeta v Post & Telecommunications Corporation 12-HH-079 and Sibanda v Masanga 24-SC-090 — cited in the Certificates lesson as contextual authority on clearance-certificate principles in the CGT sphere (Section 30A capital-gains clearance): a statutory clearance is a precondition with real third-party effects, and parties transact around its absence at their peril. Persuasive context only for ITF 263 work.
• The Section 80 engine itself has produced little reported litigation in the sources; the enforcement pressure operates commercially (withholding) rather than forensically. Where disputes do crystallise, they surface as objection/appeal matters on the underlying returns and assessments — the Packers International 16-SC-028 nil-return principle and the Section 37A line (CF, DNS, IAB, Nestlé) therefore do the indirect work, because the grid items the automatic check tests are precisely those obligations.

That sparseness is itself a teaching point: by the time a clearance problem could become litigation, the taxpayer has usually already paid the practical price in withheld cash. The remedy economics favour cure over contest.

1. Applying in January. The renewal window opens in October for a reason: a failed check in October costs nothing; a failed check in January costs 30% of every receipt until cured. Diarise October; treat 31 December as a cliff, not a deadline.
2. Treating the certificate as annual armour. Mid-year revocation (missed P2, missed VAT 7, missed QPD, audit findings) operates from the notice date, and customers verify continuously. The certificate is a live attestation of a live ledger — the only armour is the monthly routine.
3. Applying over a dirty profile. The header pre-populates from the taxpayer profile, and ZIMRA cross-checks the application against it. Stale addresses, wrong registered name (trade name in the legal-name field is the guide's flagged error), or unrecorded revenue-head changes delay or derail clearance. Profile first (by application, with its 14-day/21-day notice duties — Section 25B(4); VAT Section 25), certificate second.
4. Mis-ticking the withholding-taxes head. The tick asks whether you are a withholding agent, not whether your receipts suffer withholding. Wrong ticks trigger queries and stall the automated path.
5. Curing the return but not the money. The guide is explicit: file the missing return and pay the amount due "together with any penalty and interest." A filed-but-unpaid period still blocks; budget the cure, not just the paperwork.
6. Paying officers filing the PDF and forgetting it. For the customer side: Section 80 liability for failing to withhold is personal to the paying officer, the guide instructs verification before each payment, and a certificate can be invalid tomorrow that was valid yesterday. Verification at every payment run is the only safe routine.
7. Assuming a dispute suspends the grid. Objecting to an assessment does not clean the ledger (pay-now-argue-later, Section 69/VAT Section 36), and the automatic check is binary. Where the blocking item is genuinely contested or under an instalment plan, escalate to the manual-clearance route (next lesson) rather than letting the months bleed — and.

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.

• On the SSP the ITF 263 is computed, not granted: Submit → real-time check across every registered revenue head → immediate issue or a Compliance Status panel listing each missing return or payment (local guide + ITF 263 guide, confirmed). Hard copy survives only by exception.
• The engine is unchanged: Section 80 — 30% withholding on contract payments (≥ US$1,000/YA, FA 13/2023) absent a valid certificate; the 30% is a provisional credit with savage working-capital effect; Section 80A (licences and the nine professions; 30-day-fresh certificate) and Section 60B (credit > US$20,000) widen the blast radius of a failed check.
• The compliance grid is the calendar restated: ITF 16, monthly P2 + PAYE payment, VAT 7 + payment (15th — FA(No.2) 7/2024), WHT returns, PT4, QPDs, ITF 12B, prior-year ITF 12C. Cure = return and money, "together with any penalty and interest."
• Validity normally to 31 December (shorter conditional periods possible); renew from October — the check is free and repeatable, so apply early and use failures as a worklist.
• The certificate is a live object: mid-year revocation from the notice date; counterparty verification before each payment (Public Verification facility —); Notifications forwarding is the early-warning system.
• Strategic inversion: under automation the only durable clearance strategy is the monthly compliance routine — the certificate is a by-product of a clean ledger, and every ITF 263 problem is really a returns, payments or profile problem in disguise.
• No case law on the automated pathway (stated honestly); Sabeta and Sibanda v Masanga offer only contextual clearance-certificate principles.

Automatic clearance at a glance

The automatic clearance cycle

flowchart TD
 A[Monthly routine: P2 by 10th, VAT 7 by 15th, QPDs, payments] --> B[Ledger clean in Taxpayer Accounting]
 B --> C[October: apply - Taxpayer Certificates, Renewal]
 C --> D{Real-time check: every registered head up to date?}
 D -->|Yes| E[Immediate issue - download PDF, share with customers]
 D -->|No| F[Compliance Status panel lists gaps]
 F --> G[Cure: file returns + pay with penalty and interest]
 G --> C
 E --> H{Stay compliant during the year?}
 H -->|Yes| I[Certificate live to 31 Dec - customers verify Valid]
 H -->|No| J[Mid-year revocation from notice date]
 J --> K[Customers' verification fails - 30 percent withholding resumes]
 K --> G

Statutes & sections

• Income Tax Act [Chapter 23:06] — Section 80 (contract definition ≥ US$1,000/YA per FA 13/2023; paying-officer 30% withholding; provisional credit; exclusions) as walked in the Certificates lesson; Section 80A licensing/professional/ZINARA gates incl. the 30-day-fresh rule (FA 2024) as walked in the Agent Licence lesson; Section 60B credit gate (FA(No.2) 7/2024); Section 37A self-assessment (4 months); Section 72 QPDs (10/25/30/35%); Section 46(1)(a) additional tax and Section 46(6) remission; 13th Schedule paras 3(1), 10, 11, 14 (PAYE machinery); Section 25B(4) profile-change notices; Section 61 public officer.
• VAT Act [Chapter 23:12] — Section 23 registration (US$25,000 threshold); Section 28(1)–(2) furnish-calculate-pay, 15th-day deadline (FA(No.2) 7/2024) and nil-return duty; Fifth Schedule interest (SI 25/2025: policy + 5% local; 10% foreign currency); Section 36 pay-now-argue-later; Section 25 change notices.

Case law

• Packers International 16-SC-028 — a nil return is a return (grid-item obligation). Sabeta 12-HH-079; Sibanda v Masanga 24-SC-090 — contextual clearance-certificate principles (CGT Section 30A sphere; persuasive context only). No reported authority on the automated issuance pathway itself (stated honestly).

ZIMRA guidance

• Comprehensive Guide to the ITF 263 — ZIMRA External Guide (local source): application/renewal flow, compliance grid, validity and renewal window, mid-year revocation, verification facility, worked lapse example.
• Comprehensive Guide to the ZIMRA Self-Service Portal (local source): Taxpayer Certificates module; real-time compliance check description.
• Official SSP online help (https://mytaxselfservice.zimra.co.zw/help/ssp/en/default.htm) unreachable this run — screen labels, in-flight-item treatment, instalment-plan treatment and the public-verification path flagged in the public notice.