Payment plans (instalment arrangements) are the most important “middle path” between voluntary immediate payment and coercive enforcement. They preserve revenue where a taxpayer is unable to pay in full now but remains viable and willing to pay over time; they also reduce enforcement costs and can stabilize compliance by aligning payment obligations with cashflow. In Zimbabwe, instalment arrangements are not merely administrative convenience—they are legally recognized in the Income Tax Act (the Commissioner may determine that tax is payable in instalments) and also operate within VAT’s payment-in-full framework through administrative discretion and related mechanisms (including deposits for provisional payment where VAT cannot be accurately calculated). ()

At the enforcement end, the law is designed to prevent “delay by dispute.” For both income tax and VAT, the obligation to pay is generally not suspended by objection/appeal unless the Commissioner directs otherwise; this means payment plans operate against a background of collectability even during dispute and interact with escalating enforcement tools such as agent appointment/garnishee and expedited recovery. ()

TaRMS has changed payment plan practice. ZIMRA explicitly stated that legacy payment plans under SAP TRM did not carry over: they were nullified before migration, and taxpayers in arrears must apply for new payment plans via the TaRMS Self Service Portal under the Debt Management module. () As a result, debt strategists must be fluent in the system lifecycle: application → assessment of viability and risk → approval → automated monitoring and reminders → default handling → revision or cancellation → enforcement.

Case law reinforces the boundaries: ZIMRA v Packers (SC 28/2016) emphasizes that suspension of payment pending appeal is for the Commissioner’s discretion; courts should not usurp that power, and strong collection tools like garnishee/agent appointment can lawfully follow assessment. Murowa Diamonds (HH 1-11) illustrates that asserted set-off or claimed overpayment does not automatically block statutory recovery powers absent proof and proper procedure. These principles support a payment-plan policy that is supportive but firm: arrangements are conditional and must be monitored, and default should trigger rapid escalation. ()

Assumptions and access limits: No internal ZIMRA payment-plan SOPs/templates or detailed TaRMS internal workflow manuals were provided in this chat. The analysis relies on statutory texts and ZIMRA public notices/FAQs. The “uploaded case pack” referenced in earlier prompts was not accessible; case law is cited from public sources. Where Finance Act amendment section numbering is not visible in consolidated texts, it is flagged as unspecified.

Lesson Ten follows “Debt Collection Strategies” and precedes detailed enforcement powers. Payment plans are the primary mechanism debt teams use to convert a soft-collection engagement into an enforceable, monitored compliance pathway without immediate coercive action.

By the end of a 60–90 minute session, learners should be able to:

Identify where payment-plan authority comes from in Zimbabwean law and where it is administrative practice.

Distinguish plan revision from cancellation and understand when to pivot to enforcement.

Income Tax Act [Chapter 23:06]

Installment authority: Income Tax Act s 71 (Appointment of day & place for payment; payment in a sum or instalments). Section 71 provides that tax becomes due and payable on prescribed dates and that, where tax is payable, it shall be paid “in one sum or in instalments and at such times as may be determined by the Commissioner, having regard to the circumstances of the case.” This is the clearest statutory foundation for instalment arrangements for income tax and related debts. ()

Interest interacts with payment time and extensions (Income Tax Act s 71 proviso). Where time is extended “in special circumstances,” the Commissioner may extend time “without charging interest.” That is effectively a statutory relief lever that can support payment arrangements when the taxpayer demonstrates exceptional circumstance and/or credible rehabilitation. ()

Pay-now-argue-later default (Income Tax Act s 69). Payment is not suspended pending objection/appeal unless the Commissioner directs otherwise. This influences plan policy: a taxpayer in dispute may still be required to pay or to enter a plan unless formal suspension is granted. ()

Debt enforceability and recovery posture (Income Tax Act s 77 and s 78). Tax is deemed a debt due to the State when due; recovery proceedings are deemed like recovering a debt acknowledged in writing. This matters because payment plans should be documented and enforceable; once default occurs, the debt remains legally recoverable. ()

VAT Act [Chapter 23:12]

VAT does not present payment plans as explicitly as income tax; however, the statutory architecture still provides hooks:

Payment-in-full and the “deposit” mechanism (VAT Act s 38). VAT must be paid “in full” within the timelines allowed; however, where tax due cannot be accurately calculated within time due to circumstances beyond a person’s control, the Commissioner may accept a deposit equal to estimated liability, which is treated as provisional payment; excess is refundable and short payment recoverable. This is not a general payment plan, but it demonstrates that VAT law recognizes managed payment timing under Commissioner satisfaction, which can be operationally adjacent to arrangements. ()

Pay-now-argue-later (VAT Act s 36). The obligation to pay tax/additional tax/penalty/interest is not suspended pending objection/appeal unless the Commissioner directs otherwise. This is critical: payment arrangements are often sought during disputes. The VAT Act indicates s 36 was substituted by Finance Act 8/2022 (Finance Act section number unspecified in the consolidated excerpt). ()

Penalty/interest consequences (VAT Act s 39). Late payment triggers penalty and interest which continue unless remission applies; payment plans must therefore be designed with awareness that debt can inflate. ()

Revenue Authority Act [Chapter 23:11]

The Revenue Authority Act does not spell out payment plans in detail, but it shapes the plan environment because it defines sharper enforcement pathways:

Expedited recovery (s 33A). Where conditions are met (served assessment; no objection or no appeal pursued; unpaid tax), ZIMRA can pursue expedited recovery procedures including attachments. This is the “backstop” that gives leverage to payment arrangement negotiations—plans are an alternative to immediate enforcement, not a replacement for it. ()

Partial-payment ordering (s 33A(10)). Where payment is less than the total (principal + penalty/fine + interest), it is deemed to settle principal first, then penalty/fine, then interest. Plans should expect that partial payments will reduce principal first, leaving penalties/interest visible until later stages; communications must manage taxpayer expectations accordingly. ()

Finance Act amendments

For payment plans specifically, Finance Act references are mostly indirect (adjusting due dates, interest rates, or administrative provisions). Where Finance Acts are referenced in the consolidated laws but section numbers are not shown, this lesson flags them as unspecified.

Payment arrangements exist in a triangle of authority:

Express statutory discretion (income tax) – Income Tax Act s 71 expressly allows instalment times “determined by the Commissioner.” ()

Administrative practice within statutory payment/recovery systems (VAT) – VAT’s “full payment” structure is rigid, but s 38 deposit logic shows controlled flexibility when the Commissioner is satisfied; this supports a practical approach where arrangements must still manage interest/penalty consequences and maintain compliance. ()

Enforcement backstop – The existence of strong enforcement options (agent appointment, s 33A expedited recovery) means an arrangement is accepted because it is expected to maximize recovery versus immediate enforcement, not because debt becomes non-collectable. ()

A robust professional framework uses four eligibility lenses:

Ability to pay (affordability) Assess credible cashflow, existing obligations, and realistic surplus. In TaRMS, account statements reflect current liabilities, but viability requires taxpayer-provided evidence (bank statements, management accounts, cashflow forecasts).

Willingness to pay (behavioral compliance) Past compliance history: filing timeliness, responsiveness, prior defaults, history of estimated assessments due to non-filing (a strong negative signal in TaRMS contexts). ZIMRA warns that lack of returns can result in estimated assessments, which suggests teams should treat chronic non-filing as high risk. ()

Debt characteristics Debt amount, age, compounding rate (VAT penalties/interest can escalate quickly), currency mix (USD/ZWL), and whether debt is disputed (collectible unless suspended). ()

Risk and enforceability Availability of assets/third-party funds (if garnishee is possible), flight risk, and whether s 33A is available. Plans should not be offered where the better outcome is immediate enforcement due to high asset availability and low cooperation.

Negotiation of payment plan terms

A professional plan is not “a schedule”; it is a control mechanism. Standard term components include:

Schedule (weekly/monthly) aligned to cashflow; avoid end-loaded plans.

Scope: does the plan cover only principal tax or also penalties/interest? Under many statutory regimes, penalties/interest continue unless remission applies, so plans should disclose that debt can still grow if new periods are missed. ()

Conditions precedent: taxpayer must remain current on all new filing and payments (current returns must be filed), otherwise the plan is in immediate default.

Acceleration clause: default triggers immediate enforcement escalation.

Critical Zimbabwe nuance: Because pay-now-argue-later applies, a taxpayer in dispute may still have to adhere to a plan unless collection is formally suspended. Packers explains hardship relief/suspension is a Commissioner discretion and requires taxpayer-supplied facts; that logic supports requiring proactive disclosure and evidence in plan applications, particularly where the taxpayer seeks suspension or special terms. ()

Monitoring taxpayer compliance with payment plans

Monitoring is the difference between a plan and a delay tactic. Monitoring should include:

Payment verification: confirm each instalment posts in TaRMS ledger to the correct currency and obligations; TaRMS allows payments to sit in the Single Account until returns are submitted, so monitoring must include return submission compliance. ()

New obligations: taxpayer must not accrue new arrears (especially VAT/PAYE).

Trigger thresholds: if one payment missed → immediate contact; two missed → default/cancellation; deterioration in compliance → escalate.

TaRMS is designed to support monitoring by showing statements, balances, and debt module workflow tasks (as indicated in ZIMRA’s TaRMS operational notices and go-live communications). ()

falsified financial disclosure.

Default consequences should be immediate and credible: reclassify debt as enforcement-ready and consider agent appointment, garnishee, or s 33A expedited recovery (if finality conditions exist). ()

Murowa Diamonds illustrates why default also interacts with contested credits: asserted set-offs do not neutralize collection powers absent proof; therefore, default plus unproven credit claims should not freeze enforcement. ()

Revision of instalment agreements

Plan revision should be permitted only with evidence of a material change:

Cancellation triggers enforcement escalation.

ZIMRA’s Public Notice 87 of 2023 states:

payment plans under SAP TRM were nullified prior to migration, and

taxpayers in arrears must settle the outstanding amounts or apply for new payment plans through the TaRMS Self Service Portal under the Debt Management module. ()

This is operationally significant: it means plan requests are now an auditable workflow, with system-based tracking, approval, and monitoring.

Approval workflow and monitoring signals

While ZIMRA does not publish internal approval matrices, TaRMS publicly lists modules including “Debt Management,” and operational statements suggest it can support the end-to-end lifecycle: applications, monitoring, and indicators of default via aging and ledger status. ()

Automated reminders and ledger posting constraints

A plan is only effective if payments are recognized and posted. ZIMRA’s Single Account concept warns:

payments require returns for recognition and posting; otherwise payments remain in Single Account until return submission. ()

Therefore, a TaRMS-era plan must include compliance conditions:

taxpayer must submit returns on time, otherwise their instalments may not settle obligations properly and may trigger estimated assessments.

TaRMS FAQ indicates the system raises estimates after a grace period (9 days after due date), reinforcing that missing returns during a plan can quickly create new debts. ()

Refund offsets and impact on plan balances

VAT Act s 44(6) authorizes set-off of VAT refunds against unpaid VAT and other domestic tax debts; TaRMS FAQ confirms refund offsets are possible, but cross-currency offsets are not allowed (ZWL refund cannot offset USD obligation). ()

plan schedules must be crafted per currency ledger,

predicted refunds should not be treated as cash until set-off rules and return compliance are satisfied.

Relevance to payment plans:

VAT collection is “pay now, argue later”; suspension pending appeal is for the Commissioner’s discretion and must be based on facts the taxpayer provides. ()

Strong recovery tools (garnishee/agent) can lawfully follow assessment where there is non-payment. ()

Practical plan implication: payment plans are not substitutes for statutory obligations; they are a managed compliance pathway. A taxpayer seeking a plan during dispute must still respect pay-now logic unless suspension is granted.

Relevance:

The taxpayer admitted withholding tax was due but argued for set-off based on alleged overpayment; ZIMRA emphasized its statutory recovery and agent appointment powers; the court refused to restrain recovery absent proof and proper basis. ()

Practical plan implication: debt teams must not accept unproven set-off “promises” in lieu of payments; plan eligibility should require clear proof of credits/refunds and posted ledger positions.

Relevance:

The court reaffirmed strict statutory interpretation principles (“no equity about a tax”), meaning payment plan discretion must operate within legal authority and cannot be purely equitable. ()

Practical implication: plan approvals, extensions without interest, and remissions must be justified under statutory criteria and documented accordingly.

Overly lenient plans that function as delay tactics If instalments are too small relative to ongoing liabilities and accruing interest/penalties, debt grows even while the taxpayer “pays,” and the plan fails. VAT penalty/interest regimes make this especially dangerous. ()

Failure to require return compliance during the plan Because TaRMS posting depends on returns, a taxpayer can pay into the Single Account but remain delinquent if returns aren’t filed. This can trigger estimated assessments and new debt, collapsing the plan. ()

Insufficient security for high-risk debtors Where assets exist and flight risk is high, a plan without safeguards can lead to revenue loss; the strategic alternative is agent appointment or expedited recovery. Packers illustrates that garnishee is a lawful possibility post‑assessment. ()

Incorrect allocation expectations in short-payment contexts Revenue Authority Act s 33A(10) deems payments to settle principal first, then penalties, then interest, which can surprise taxpayers (“why is interest still there?”). Plans should incorporate clear messaging about how payments reduce components. ()

Currency mismatch and cross-currency offset assumptions TaRMS does not allow a ZWL refund to offset a USD obligation. Plans must therefore be currency-structured. ()

Reputational risk Granting plans to “connected” taxpayers without objective criteria undermines fairness and increases compliance resistance. Strict statutory interpretation principles support transparent, criteria-based decisions. ()

This table presents a training-grade “best practice” framework aligned to Zimbabwe legal constraints and TaRMS realities (not a published ZIMRA SOP). Statutory anchors listed are where the Act provides relevant discretion, not necessarily a “payment plan program” clause.

Key statutory anchors referenced for the table: Income Tax Act s 71 (instalments; interest-free extension), Income Tax Act s 69 (payment not suspended), VAT Act s 36 (payment not suspended), VAT Act s 39(5) remission in principle, and Revenue Authority Act s 33A (enforcement backdrop and allocation ordering). ()

Which statutory provision provides the clearest basis for instalment arrangements for income tax liabilities?

Under Zimbabwe’s pay-now-argue-later rules, does lodging an appeal automatically suspend the obligation to pay, and who has discretion to suspend?

What did ZIMRA’s Public Notice 87 of 2023 say about legacy payment plans during migration to TaRMS?

Name three eligibility criteria you would use to decide whether to approve a payment plan.

Why must a TaRMS-era payment plan include “return filing compliance” as a condition?

What are two “default” triggers that should lead to cancellation and enforcement escalation?

Under Revenue Authority Act s 33A(10), how are short payments applied across principal, penalties, and interest?

Income Tax Act s 71, which allows payment in one sum or in instalments “as may be determined by the Commissioner.” ()

No. Income tax: s 69; VAT: s 36. Payment is not suspended unless the Commissioner directs otherwise (subject to terms/conditions). ()

ZIMRA stated that payment plans under SAP TRM were nullified before migration; taxpayers must apply for new payment plans via the TaRMS Self Service Portal under the Debt Management module. ()

Ability to pay (cashflow), willingness to pay (compliance history/responsiveness), and debt characteristics/risk (amount, age, repeated default, currency profile, dispute status).

Because ZIMRA’s Single Account model requires returns to be submitted for payments to be recognized and posted; without return filing, payments may remain unapplied and liabilities remain outstanding or estimates triggered. ()

Example default triggers: missed instalment beyond grace period; failure to file current returns; incurring new arrears; dishonored payments; material misrepresentation in the application.

Principal first, then penalties/fines, then interest. ()

Payment plans are legally grounded for income tax via s 71, and operationally implemented for broader domestic taxes through TaRMS debt management workflows. They should be treated as conditional compliance contracts, not simple schedules. ()

Zimbabwe’s overall administration is pay-now-argue-later: disputes do not automatically suspend payment; therefore, plans may run even while disputes are processed unless a suspension directive exists. This principle is reinforced by Packers. ()

TaRMS introduces a new failure mode: “cash paid but not posted” due to missing returns. Plans must require return compliance and include reconciliation checks. ()

Default management must be strict: weak monitoring converts plans into delay tactics and increases loss, especially because interest/penalties continue unless remitted. ()