A tender deadline can expose a tax administration problem that has been sitting quietly in the background for months. A director logs into TaRMS expecting a certificate, then finds no ITF263 in the inbox and assumes ZIMRA has rejected an application.

When an ITF263 is refused, the first judgement call matters: since 1 January 2024, ZIMRA ordinarily generates the certificate automatically for compliant taxpayers. There is usually no manual application for an officer to approve or decline. Start with our ZIMRA tax clearance certificate (ITF263) guidance, then use TaRMS to identify the outstanding condition.

As of September 2026, ZIMRA’s published process points to five practical causes: missing returns, unpaid obligations, VAT fiscalisation failures, incomplete TaRMS access or outdated master data. Each has a different remedy. Paying money without identifying the matching obligation often makes the position worse, not better.

First, understand what “refused” means in TaRMS

The ITF263 is ZIMRA’s tax clearance certificate. ZIMRA issues it through the TaRMS Self-Service Portal and emails it to the address held in the taxpayer’s master data when the taxpayer meets the system’s compliance conditions.

That distinction changes how we investigate. Do not submit duplicate requests or wait for an approval email if the system shows an outstanding return, a debt, or a fiscalisation exception. Clear the specific exception, then check TaRMS again.

ZIMRA made the TaRMS process effective from 1 January 2024. Certificates from the former SAP and e-services environment that overlapped beyond December 2023 ceased to be valid on 1 January 2024, so an old BP-number certificate cannot solve a current tender or supplier-onboarding requirement.

Step 1: Claim your TIN and confirm portal access

Existing ZIMRA taxpayers need to claim their TIN and register on the TaRMS Self-Service Portal. A business without a historic Business Partner number needs to register in TaRMS before it can manage its tax profile.

This is the first item we check because directors often retain an old registration number but have not completed the TaRMS account setup. The tax position may be sound, yet the business cannot see its certificate or compliance exceptions until it has the correct account access.

Check that the entity name, TIN and authorised user correspond to the legal taxpayer. If your company changed its name, directors or registered address through the Companies Registry, now operating as the Corporate and Intellectual Property Zimbabwe office, confirm that your ZIMRA records also reflect the current position. A Companies Registry update does not automatically update ZIMRA’s tax master data.

The common reasons an ITF263 is not issued

1. Outstanding tax returns

ZIMRA identifies outstanding returns as a primary reason for non-issuance. The missing return may relate to a period with no tax due, which is exactly why it is often overlooked. A nil return can still be a required compliance filing.

ZIMRA’s October 2024 notice confirmed that the system automatically charges penalties on outstanding returns. The official material reviewed does not confirm one standard ITF263-specific penalty amount, so verify the amount shown against the taxpayer’s actual TaRMS profile before paying.

The practical step is simple but exact: list every outstanding return by tax type and period, prepare the returns from the accounting records, submit them in TaRMS, and retain the submission acknowledgements. Do not assume that filing the most recent return cures older open periods.

2. Tax due or a payment that has not been allocated

An unpaid tax obligation can prevent automatic issuance. More commonly, a taxpayer has paid into the ZIMRA Single Account but has not submitted the corresponding return, so TaRMS cannot post that payment against the correct obligation.

This is the step businesses skip. A bank payment reference proves that money left the business account. It does not, by itself, prove that TaRMS has settled the return liability. Until the return exists and the payment posts to it, the obligation can remain open and continue to attract penalties and interest.

Take an illustrative Harare wholesaler with twelve staff and a US$40,000 monthly payroll. The finance manager paid US$6,000 toward an older payroll obligation but filed the related return late, leaving TaRMS to show the period as unsettled when the business bid for a supply contract. The immediate cash cost was not the US$6,000 payment, which the business had already made, but the additional interest and penalty exposure while the payment remained unallocated. Next time, the team should file first, confirm the period and tax head, then reconcile the TaRMS account after payment.

Before you pay a second time, reconcile the tax period, tax type, return status and payment allocation in TaRMS. If the records do not align, prepare the evidence for a targeted query rather than making a speculative payment.

3. An expired or migrated payment arrangement

A taxpayer with arrears may apply for a new payment plan through TaRMS Debt Management. This gives a viable route where the business cannot settle the full amount at once, subject to ZIMRA’s consideration of the arrangement.

Do not rely on a payment plan agreed under SAP TRM before the TaRMS migration. ZIMRA stated in February 2024 that old SAP TRM payment plans were nullified before migration. A director may honestly believe an arrangement remains active while TaRMS shows the full debt as overdue.

A payment plan is not a substitute for ongoing compliance. Continue filing current returns while addressing historic arrears, because new unfiled returns can create a fresh block even where Debt Management considers an arrangement.

4. VAT fiscalisation exceptions

For VAT-registered taxpayers, ZIMRA identifies failure to interface with the Fiscalisation Data Management System as a reason the ITF263 may not issue. This issue affects businesses that have filed and paid correctly but have not met the applicable fiscalisation requirement.

Check the VAT profile before treating the matter as a debt issue. Ask whether the taxpayer’s fiscal devices or systems are interfacing as required and whether TaRMS records an exception. A generic tax payment will not correct a fiscalisation block because the system is testing a different compliance condition.

Take an illustrative Bulawayo hardware retailer with annual VAT sales and several tills. The business had no arrears, but its accountant focused on VAT returns while an interface issue prevented the expected tax clearance certificate from generating before a procurement submission. It spent about US$1,200 on technical support and record reconciliation to identify the fault and regularise the connection. The better approach would have been a monthly fiscalisation status check, not a last-week tender check.

If your enterprise is not VAT registered, do not spend time investigating fiscalisation first. Start with returns, liabilities, portal access and master data, because ZIMRA’s published fiscalisation condition specifically concerns VAT-registered taxpayers.

5. Incorrect email address or incomplete master data

ZIMRA sends the certificate to the email address in its records. A compliant taxpayer can therefore conclude that an ITF263 was refused when the certificate went to a former accountant, a departed employee or an inbox nobody monitors.

Confirm the physical address, email address, telephone number, bank account details and industry classification in the taxpayer’s master data. ZIMRA identifies Rev 2 for an email-address change. Check the current form and process in TaRMS before submission because administrative requirements can change.

This issue needs careful handling where a group uses one finance email for several entities. Each legal entity must have accurate master data. Do not assume that a holding company’s contact update flows to its subsidiary’s tax account.

A practical TaRMS recovery sequence

Use this sequence before escalating a missing certificate. It keeps the finance team focused on the condition that is actually blocking issuance.

1. Check the tax profile, not only the inbox

Log into the TaRMS Self-Service Portal under the correct taxpayer account. Review outstanding returns, balances, correspondence and any status messages before asking whether ZIMRA has “refused” the certificate.

Take dated screenshots or export account statements for your internal file. A tender team, auditor or board member will need a clear record of what the tax system showed on the day.

2. Clear every outstanding return

Match the listed period to the general ledger, payroll records, VAT records and prior submissions. File the return even where the amount due is nil, because the filing obligation and the payment obligation are separate.

For employers, review payroll taxes alongside your PAYE calculations. A payroll reconciliation that identifies an omitted period early gives management a better basis for deciding whether to pay immediately or approach Debt Management about arrears.

3. Reconcile each payment to each obligation

Confirm that every payment has a submitted matching return and that TaRMS has posted the amount to the intended period. This is particularly important for payments made into the ZIMRA Single Account.

If the system still shows an unpaid balance, investigate the allocation before paying again. Double payment can create a credit in one place while the actual compliance block remains elsewhere.

4. Check VAT fiscalisation where applicable

A VAT-registered enterprise should test whether it interfaces with ZIMRA’s Fiscalisation Data Management System and whether the system shows any unresolved exception. Give your technical provider a precise exception reference where TaRMS provides one.

Do not infer that a POS system is compliant merely because it prints receipts. The relevant question is whether the taxpayer meets ZIMRA’s required fiscalisation interface condition.

5. Update master data and wait for the system result

Confirm the email address in the ZIMRA record and make the appropriate update where necessary. Once returns, payments, fiscalisation and master-data issues are corrected, check TaRMS again for automatic issuance.

If the certificate arrives, validate it through TaRMS using its QR code or the TIN and authentication code. This protects the enterprise and its counterparties from relying on an invalid or altered document.

Keep other regulators in the right place

A business can need several clearances at once, especially when bidding, importing, restructuring or entering a regulated sector. That does not make each regulator’s approval a stated ITF263 issuance condition.

PRAZ registration may matter for government suppliers, and your PRAZ registration position should be managed alongside your tender timetable. However, ZIMRA’s published ITF263 conditions focus on ZIMRA registration, returns, payments, master data and VAT fiscalisation. Do not assume PRAZ status automatically unlocks an ITF263.

The same discipline applies to Companies Registry annual returns, NSSA obligations and Zimbabwe Investment and Development Agency approvals. These may be material to the enterprise’s broader compliance, governance or investment position, but the official ZIMRA material reviewed does not state that CIPZ, PRAZ, NSSA or ZIDA compliance automatically triggers ITF263 issuance.

For a transaction or public tender, build one compliance calendar with separate owners for ZIMRA, PRAZ, NSSA, Companies Registry and any ZIDA requirement. That gives the board a reliable view of exposure without confusing one regulator’s process with another’s.

Frequently Asked Questions

Can I submit a new ITF263 application if the certificate is missing?

Usually, start in TaRMS rather than submitting a new manual application. Since 1 January 2024, ZIMRA ordinarily auto-generates and emails the certificate when the taxpayer meets the compliance conditions.

I paid ZIMRA. Why does TaRMS still show an outstanding balance?

The matching return may be missing, which can prevent TaRMS from posting a Single Account payment to the relevant obligation. File the correct return, reconcile the payment allocation, then review the balance again.

Does an old SAP payment plan still protect my tax clearance position?

Do not assume so. ZIMRA stated that SAP TRM payment plans were nullified before the TaRMS migration, and taxpayers with arrears should consider a new TaRMS Debt Management payment plan.

Will PRAZ registration or NSSA clearance make ZIMRA issue an ITF263?

Not automatically, based on the ZIMRA conditions reviewed. Manage PRAZ registration and NSSA compliance separately, while resolving the ZIMRA returns, payments, master-data and VAT fiscalisation issues that TaRMS identifies.

An ITF263 issue becomes manageable when the finance team stops treating it as a vague rejection and starts tracing the exact TaRMS condition behind it. For a step-by-step view of the certificate process and the documents your enterprise should retain, visit our ZIMRA tax clearance certificate (ITF263) hub page.