TaRMS Essentials Lesson 6.1 The Single Account Concept Conceptual deep-dive into the Single Account architecture — the unified taxpayer wallet that replaced per-tax-head bank accounts. RefNum, Transaction Purpose, allocation priority, and dual-currency handling.
1

Executive summary

Why ZIMRA built the Single Account, and what changed for the taxpayer.

2

Lesson content

The mechanics: one bank account per taxpayer, RefNum + Transaction Purpose for allocation, automatic rebalancing across heads.

3

Assessment & policy notes

Common allocation pitfalls and a 5-step payment-day playbook.

Executive summary
Lesson content
Assessment

A. Lesson Context: One Wallet, All Heads

Under e-Services, every tax head had its own ZIMRA bank account. Taxpayers wired separate amounts to PAYE, VAT, Income Tax, etc., and reconciled separately. The Single Account architecture, introduced with TaRMS, consolidates everything into one nominated bank account per taxpayer. This is more than a workflow change — it is a fundamentally different financial model. Lesson 6.1 explains the architecture; Lessons 6.2 and 6.3 cover the operational workflows.

B. Legislative Framework

1. Section 34B RAA — the Commissioner’s prescription

The same enabling provision that prescribes TaRMS as the channel for filing also prescribes the Single Account as the channel for payment.

2. Section 79A ITA (introduced by Finance Act 2025) — allocation priority

Where a payment to the Single Account is made without specific allocation, ZIMRA applies a priority order: (i) penalties, (ii) interest, (iii) outstanding principal by oldest debt first.

3. Practice Note — RefNum and Transaction Purpose

Taxpayers may direct allocation by populating the RefNum and Transaction Purpose fields at payment time. Without these, the priority rule applies.

4. Dual-currency reporting

Finance Act 2025 codified ZWG and USD as the two reporting currencies; the Single Account holds balances in each separately.

C. Detailed Conceptual Explanation

1. The architectural change

Aspecte-Services (legacy)TaRMS (current)
Number of ZIMRA accounts per taxpayerOne per tax headOne Single Account
ReconciliationPer-head, manualConsolidated, automatic
Cross-head rebalancingManual refund-and-repayAutomatic by allocation rules
Currency handlingSeparate sub-accountsTwo currency balances per Single Account

2. The Single Account’s structure

Under the hood, the Single Account is one ZIMRA-side ledger per TIN. Funds paid in by the taxpayer’s nominated bank are credited to the ledger; ZIMRA debits the ledger to settle assessed liabilities.

3. RefNum and Transaction Purpose

At the moment of bank transfer:

  • RefNum: a system-generated reference linking the payment to a specific assessment or return.
  • Transaction Purpose: a free-text or coded field indicating intent (e.g., “PAYE March 2026”, “VAT April 2026 + interest”).

If both are correctly populated, allocation is exact. If absent, priority rules apply.

4. Allocation priority (s. 79A)

  1. Penalties first.
  2. Interest next.
  3. Principal: oldest debt first.

Implication: a careless payment intended for current PAYE may be allocated against old penalties, leaving current PAYE underpaid.

5. Dual-currency mechanics

Each Single Account holds two balances: ZWG and USD. Each allocation runs in the corresponding currency. A USD payment cannot settle a ZWG liability or vice versa, except via formal currency conversion subject to ZIMRA approval.

6. Visualisation

flowchart TD BANK["Taxpayer bank"] --> SA["Single Account ledger"] SA --> ZWG["ZWG balance"] SA --> USD["USD balance"] ZWG --> ZA["ZIMRA assessments ZWG"] USD --> UA["ZIMRA assessments USD"] REFNUM["RefNum"] --> SA PURPOSE["Transaction Purpose"] --> SA PRIORITY["s. 79A priority
penalty, interest, principal"] --> SA

7. Single Account operations

OperationLesson
Concept (this lesson)6.1
Change Single Account bank6.2
Search transactions6.3
Reading the resulting balance7.1, 7.2

D. Real-World Applicability

1. The payment-day playbook

  • Identify the assessment to be settled (Tax Type Report, Lesson 7.2).
  • Note the RefNum from the assessment.
  • Initiate bank transfer to the nominated Single Account bank.
  • Populate RefNum and Transaction Purpose at the bank.
  • Confirm receipt within 24 hours via Single Account Transactions (Lesson 6.3).

2. The cross-head allocation case

Cairns Foods owes USD 5,000 PAYE and is owed USD 3,000 VAT refund. Under the legacy model, Cairns would wait for the refund and then pay PAYE. Under the Single Account, the VAT refund is credited and the PAYE liability is debited automatically — net cash flow is the difference.

3. The dual-currency case

Lily pays PAYE in USD (her staff are USD-paid) but holds VAT liability in ZWG (her domestic sales generate ZWG VAT). The two settle separately within the Single Account; no cross-currency netting.

E. Case Law Integration

1. Mukoko Industries v. Commissioner-General (Special Court 2024)

A taxpayer paid a lump sum without RefNum; ZIMRA applied priority rules and the payment landed against an old penalty rather than the intended current PAYE. The court upheld the allocation: the taxpayer’s remedy is to populate RefNum/Purpose at payment time. Mukoko is the leading domestic authority on Single Account allocation.

2. The currency-conversion question

An emerging question: can a USD over-payment offset a ZWG under-payment? Per Re Triangle Sugar (Special Court 2025, unreported), no — cross-currency offset requires formal Commissioner approval. The currency balances are notionally separate.

F. Common Pitfalls

1. Paying without RefNum

Mukoko Industries (2024). Fix: always include RefNum.

2. Misunderstanding priority rule

Penalties before principal. Plan accordingly.

3. Cross-currency confusion

USD ne ZWG. Pay each in correct currency.

4. Treating Single Account as a savings account

It is a tax-payment account, not a holding facility.

5. Ignoring the bank-side reference fields

The reference fields populate the ZIMRA-side allocation. Bank tellers often skip them; the taxpayer must insist.

G. Knowledge Check

Question 1

What changed in the move from per-tax-head accounts to the Single Account?

Question 2

State the s. 79A allocation priority order.

Question 3 — Scenario

You pay USD 5,000 to settle PAYE March 2026. The taxpayer has an old penalty of USD 800 and outstanding interest of USD 200. RefNum is omitted. Where does the USD 5,000 land?

Question 4

Why can a USD payment not settle a ZWG liability?

H. Quiz Answers with Explanations

Answer 1

Per-head accounts replaced by one consolidated Single Account ledger; manual reconciliation replaced by automatic; cross-head rebalancing automated; dual-currency capability added.

Answer 2

(1) Penalties; (2) Interest; (3) Principal — oldest debt first.

Answer 3

USD 800 settles the penalty; USD 200 settles interest; the remaining USD 4,000 is applied against the oldest principal debt — not necessarily PAYE March 2026. PAYE March may remain unpaid, accruing fresh interest. The fix is to populate RefNum at payment time directing the entire USD 5,000 to PAYE March 2026.

Answer 4

Each currency is a notionally separate balance under the Single Account. Cross-currency offset requires formal Commissioner approval (per Re Triangle Sugar 2025, unreported). The architecture deliberately preserves currency separation to honour the dual-currency reporting framework introduced by Finance Act 2025.

I. Key Takeaways
  • One Single Account per TIN; two currency balances (ZWG, USD).
  • RefNum + Transaction Purpose direct allocation.
  • Section 79A allocation priority: penalties → interest → principal (oldest first).
  • Mukoko Industries (2024) — the burden is on taxpayer to populate RefNum.
  • Cross-currency offset requires Commissioner approval.
  • Continuity: Lesson 6.2 covers changing the Single Account bank; 6.3 covers the transaction-search workflow.