This lesson is the capstone of the VAT thread running through the TaRMS Essentials course. Every earlier VAT lesson taught one organ of the system in isolation — registration in VAT Registration Application via TaRMS, the return mechanics in Return Submission, the payment screens in Making a New Payment, the clearance engine in Automatic Tax Clearance, the refund pipe in Withdrawals / Refund Requests. Here we connect them into the single living cycle that a registered operator actually runs month after month: register → keep records → charge and account for VAT → file the VAT 7 → pay (or claim) the net → stay cleared → respond to assessments. The point of the lesson is not to re-teach each screen but to show how the screens chain, where one step's output becomes the next step's input, and where the cycle most often breaks.
The governing statute throughout is the Value Added Tax Act [Chapter 23:12], read with the VAT (General) Regulations, SI 273 of 2003 (as amended) and the Finance Act [Chapter 23:04] (which fixes the standard rate of 15%). The charging section is Section 6(1)(a) — VAT is levied on the supply of goods and services made by a registered operator in the course of a trade. Liability to be in the system at all comes from Section 23 (compulsory registration once taxable supplies exceed US$25,000 in any 12-month period — the threshold set by Finance Act 13 of 2023 w.e.f. 1 January 2024, as established in the registration lesson). The return itself is the VAT 7, the single merged form that declares output tax (Part II), claims input tax (Part III), nets the two and credits VAT withheld at source (Part IV), and splits everything between the USD and ZiG currency streams (Part V).
The deadline is the load-bearing date of the whole cycle, and it has changed. Under Section 28(1) the VAT 7 and the payment for the period are now due within the period ending on the 15th day of the first month after the end of the tax period — for example, the January monthly period is due by 15 February. This is the current law: the deadline was shortened from the 25th day to the 15th day by Section 33 of the Finance (No. 2) Act 7 of 2024, with effect from 1 January 2025. Many printed aids — including ZIMRA's own VAT 7 external guide and the Compliance Calendar — still say the 25th; that figure is outdated and following it now produces a late return. This old-vs-new contrast is the single most important practical fact in the lesson.
The cycle's arithmetic is simple and unforgiving: net VAT = output tax (Section 6, valued under Section 9) − input tax (Section 16, only on valid fiscal tax invoices and only to the extent inputs make taxable supplies) − VAT withheld (Section 50A credit). A positive result is paid; a negative result is a refund or carry-forward under Section 44. Payment is governed by Section 38, whose defining rule is currency pairing: USD-stream VAT is paid in USD, ZiG-stream VAT is paid in ZiG, and the two are never netted — a discipline backed by the Section 38A civil penalty for paying in the wrong currency. A nil period is still a filing period (Section 28 requires a return "whether or not any tax is payable"), confirmed by Packers International (Pvt) Ltd v ZIMRA 16-SC-028.
Two failure-modes close the loop. If you don't file or under-declare, ZIMRA raises an assessment under Section 31 (with estimation power under Section 31(4)) and may add additional tax of up to twice the tax under-declared under Section 66, plus penalty and interest under Section 39; you contest it by objection under Section 32 within 30 days. If you over-pay, you claim a refund under Section 44 (six-year window), and interest on a delayed refund under Section 45 is discretionary ("the Minister may direct"), in sharp contrast to the mandatory 60-day refund interest on the income-tax side under ITA Section 48. Holding the whole structure up is Section 57: every record behind every line must be kept six years. Master the chain — deadline, currency pairing, fiscal-invoice discipline, the nil-return rule, and the six-year file — and you have mastered VAT compliance in TaRMS.
