This lesson connects three things that beginners usually treat as separate: the paper (or electronic) tax invoice a business issues at the till, the Fiscalisation Data Management System (FDMS) that streams every one of those invoices to ZIMRA in real time, and the Invoice Management module inside the TaRMS Self-Service Portal (SSP) where a VAT-registered operator matches the invoices ZIMRA already holds against its own records before lodging the VAT 7 return. Understand how these three interlock and most VAT input-tax problems — denied claims, audit queries, lost credits — disappear.

The governing law is the Value Added Tax Act [Chapter 23:12]. Section 20 is the heart of it: a registered operator making a taxable supply must, within 30 days, provide the recipient with a tax invoice carrying the particulars listed in Section 20(4) — and since the Finance Act 7 of 2021 (gazetted 31 December 2021, effective 1 January 2022) the first of those particulars is literally the phrase "Fiscal Tax Invoice" in a prominent place. The Schedule to the Act defines a "tax invoice" as a fiscal tax invoice provided by a registered operator and printed by a fiscalised electronic register or fiscal memory device — in other words, in Zimbabwe a VAT tax invoice that is not fiscalised is, by definition, not a tax invoice at all. That single definitional move is why fiscalisation is not an optional add-on; it is the form requirement baked into the document.

The compliance teeth are sharp and recent. Section 63A (inserted by the Finance Act 13 of 2023, effective 29 December 2023) makes it a criminal offence to fail to issue or retain a fiscal tax invoice (level 7 / 6 months), to fail to produce one on demand (level 7 / 6 months), to deal in unapproved fiscal memory devices (level 14 / 5 years), or to tamper with a fiscal device (level 14 / 5 years). Running alongside the criminal track is a civil-penalty regime in the Schedule: failing to acquire and install a device, failing to interface with FDMS within 96 hours of being ordered to, tampering, or running a faulty device each attract a fixed penalty of up to US$1,000 plus a cumulative daily penalty of US$25–US$50 for up to 90 days, all preceded by a 48-hour show-cause window and a 96-hour remediation window.

On the practical side, ZIMRA has migrated the whole country onto FDMS, which interfaces with installed hardware fiscal devices and also offers a Virtual Fiscalisation System (the statutory hook is Section 68CC, inserted by the Finance (No. 2) Act 10 of 2022) — an API-based route for taxpayers without dedicated till hardware. Every compliant fiscal tax invoice now carries a QR code and a verification (authentication) code, validatable at the public portal https://fdms.zimra.co.zw, where a clean invoice returns the word "VALID". By Public Notice (most recently Public Notice 30 of 2025, building on PN 80 of 2024 and PN 50 of 2023), every fiscal tax invoice must now also transmit buyer details — the buyer's name, address, TIN, contact details and VAT number where applicable — with a hard compliance date of 31 May 2025, the same cut-off that completed the TaRMS–FDMS integration.

Why does the buyer in TaRMS care? Because input tax under Section 15(2)(a) of the VAT Act can only be deducted if a valid tax invoice under Section 20 (i.e. a fiscalised one) is held — and ZIMRA's stated position is that only compliant invoices bearing buyer details and a verifiable QR code will be accepted for input-tax claims. The Invoice Management module is the SSP page where you confirm that the invoices you intend to claim are the same invoices FDMS already has on file under your TIN — reconciling the two before the VAT 7 goes in rather than discovering a mismatch during an audit. There is a carrot too: Section 15 allows a deduction (input credit) equal to 50% of the cost of acquiring a fiscalised electronic register, softening the hardware bill.

Case law on fiscalisation itself is thin — this is young, statute-driven territory — so this lesson grounds the procedure in the Act, the VAT 7 guide, the SSP External Guide and ZIMRA's public notices, and flags screen-level specifics that only the live SSP help can finally confirm with `.

In a value-added tax, the invoice is the unit of the entire system. Output tax is charged on it; input tax is claimed from it; the whole self-policing logic of VAT — that my output tax is your input tax — only works if the two sides are looking at the same document with the same numbers. For decades the weakness of that logic in Zimbabwe (and everywhere) was that the invoice was a private piece of paper. A seller could issue one invoice to the buyer and record a different (or no) figure in its own VAT return. A buyer could fabricate an invoice and claim input tax on a purchase that never happened. ZIMRA only saw the discrepancy if and when it audited — long after the cash had moved.

Fiscalisation closes that gap by making the invoice announce itself to the tax authority at the moment it is created. A fiscalised device — whether a dedicated electronic till (a Fiscalised Electronic Register, "FER") or a virtual software solution talking to ZIMRA over an API — records the sale in tamper-evident memory and transmits the transaction to ZIMRA's back-end, the Fiscalisation Data Management System (FDMS), in real time. The printed invoice then carries a QR code and a verification code that anyone can check against ZIMRA's record. The invoice is no longer a private claim; it is a co-signed record held simultaneously by seller, buyer and ZIMRA.

For the TaRMS user, this changes daily life in two directions:

• As a seller, your obligation is no longer just "issue an invoice." It is "issue a fiscalised invoice, on an approved device, interfaced with FDMS, carrying buyer details, and keep the copy." Each of those four adjectives is independently enforced (see section B).
• As a buyer, your input-tax claim is only as good as the seller's fiscalisation. If the seller hands you a hand-written or non-fiscalised invoice, you are holding a document that is not a tax invoice in law — and the Invoice Management module in TaRMS will not have it on file, so the claim is exposed.

This is exactly the area where ZIMRA audit interest is highest, because FDMS gives auditors a complete, queryable record of every fiscal invoice in the economy. Mismatches between a taxpayer's VAT 7 and the FDMS data are now trivially easy for ZIMRA to surface. That is why this lesson sits at the centre of the TaRMS course: it is where the documents you issue and receive meet the system that watches them.

Where this lesson fits in the chapter: it builds directly on End-to-End VAT Workflow in TaRMS (tarmsvatworkflow), where the VAT 7's input-tax side, Part III, was shown to require a valid fiscal tax invoice; it complements Common TaRMS Pitfalls (tarmspitfalls), which flagged the "imported services" and "invalid input tax" traps; and it feeds the audit thread (tarmsaudit, forthcoming), because fiscal data is the auditor's first port of call.

Fiscalisation is not in one tidy section — it is woven through the definitions, the invoice section, the input-tax section, the offences, and a dedicated penalty Schedule. Take them in order.

B1. What a "tax invoice" is — the definition that requires fiscalisation

The Schedule to the VAT Act defines:

• "tax invoice" means "a fiscal tax invoice provided by a registered operator, and printed by a fiscalised electronic register or fiscal memory device used by a registered operator for the purpose of section twenty."
• "fiscal tax invoice or receipt" means "a tax invoice or receipt printed from an approved fiscal device used by a registered operator."
• "fiscalised electronic register" means "an electronic sales register having such features as may be prescribed."
• "approved fiscal memory device" means "an approved electronic device used to record sales of taxable supplies", and "approved" means a device whose use is approved by the Authority, having been sold … by or on behalf of a supplier approved by the Authority.

Read together, these definitions do something subtle but decisive: they collapse "tax invoice" and "fiscal tax invoice" into the same thing. For VAT purposes there is no longer a category of valid, non-fiscalised tax invoice. A document that is not printed by an approved fiscalised device is not a tax invoice in law, whatever it says at the top.

B2. Section 20 — the content and timing of a tax invoice

Section 20(1): a registered operator making a taxable supply (other than a Section 7(9) deemed supply) shall provide the recipient, within 30 days from the date of supply, with a tax invoice containing the Section 20 particulars. The two provisos: (a) it is not lawful to issue more than one tax invoice per taxable supply (the source of the "one invoice rule" — duplicates create double-claim risk); (b) a lost original may be replaced with a copy clearly marked "copy."

Section 20(4) — the mandatory particulars, "except as the Commissioner may otherwise allow":

• (a) the words "Fiscal Tax Invoice" in a prominent place — substituted by Act 4 of 2012, then amended by the Finance Act 7/2021 (gazetted 31 December 2021, w.e.f. 1 January 2022) to its present fiscalised wording;
• (b) the name, address and registration number of the supplier;
• (c) the name and address of the recipient, and the recipient's registration number if it is a registered operator — this is the statutory root of the "buyer details" mandate now enforced through FDMS;
• (d) an individual serialised number and the date of issue;
• (e) a description of the goods or services (annotated in the Act to IAB Company v ZIMRA 22-HH-032);
• (f) the quantity or volume;
• (g) either (i) the value of the supply, the tax charged, and the consideration; or (ii) where tax is the tax fraction of the consideration, the consideration plus either the tax amount or a statement that tax is included and the rate.

Section 20(2) — recipient-created tax invoices ("RCTIs"/self-billing): a registered-operator recipient may create the document and it is deemed the supplier's tax invoice, but only with prior Commissioner approval, a supplier-recipient agreement that the supplier will not also invoice, and copy-retention. Section 20(3) handles the Section 7(9) deemed supply mirror (recipient creates the document within 30 days).

Section 20(5) — the de minimis: no tax invoice need be provided where the total consideration is in money and does not exceed US$10 / ZW$5,000 (increased to ZWL 25 million by Finance Act 8/2022 w.e.f. 24 October 2022) or the prescribed amount. Below this threshold a fiscalised receipt still issues, but the full Section 20(4) invoice is not compelled.

Section 20(6) — the Commissioner may, where records are sufficient and a full invoice impractical, dispense with particulars or with the invoice. Section 20(7) governs second-hand goods and Section 7(9) supplies — the recipient keeps prescribed records (supplier identity, ID verification, date, description, quantity, consideration) instead of a tax invoice; this underpins the "notional input tax" on second-hand goods.

Section 20A is a transitional rule: VAT invoices generated before 31 December 2021 could be used to claim input tax up to 31 March 2022, disapplying the 12-month limit for that legacy stock (inserted by Finance Act 7/2021).

B3. Section 15(2)(a) — no fiscal invoice, no input tax

Section 15 calculates the tax payable; Section 15(2) states that no deduction of input tax shall be made unless — (a) a tax invoice (or debit/credit note) under Section 20 or Section 21 has been provided within the return period or 12 months, whichever is longer, and is held when the return is furnished; (b) an invoice is not required under Section 20(5)/(6); (c) Section 20(7) records are kept for second-hand goods; (d) a bill of entry under the Customs Act is held for imports; or (e) a Section 13(2) invoice is held and Section 13(1) tax on imported services paid. The 12-month maximum was litigated in PIL (Pvt) Ltd v ZIMRA 17-HH-213. Because Section 15(2)(a) routes through the Section 20 definition — and Section 20's definition requires fiscalisation — the input-tax gate is a fiscalisation gate. ZIMRA's administrative overlay tightens it further: per the 2024–2025 public notices, only invoices bearing buyer details and a verifiable QR code are accepted for input-tax claims.

B4. Section 21 — credit and debit notes

When a supply is cancelled, varied, re-priced, or goods returned, Section 21 governs the credit note (CN) or debit note (DN) that corrects the original tax. Under FDMS these are themselves fiscal documents — a fiscalised CN/DN, validatable on the portal — and they flow into the VAT 7 adjustment lines (carried in tarmsvatworkflow). The "one invoice per supply" rule (Section 20(1) proviso (a)) plus the CN/DN machinery is how the system corrects without issuing a second invoice.

B5. The Section 15 acquisition allowance — the 50% sweetener

Among the Section 15 deductions the Act lists "an amount equivalent to 50% of the cost of the acquisition of fiscalised electronic registers by a registered operator" (originally inserted by Act 3 of 2010 w.e.f. 17 September 2010; re-substituted by Act 1/2014). This is a deliberate subsidy: the State wanted operators to buy the hardware, so it let them recover half the cost as an input credit. It matters in the worked examples below.

B6. Section 63A — the criminal offences (Finance Act 13/2023, w.e.f. 29 December 2023)

Newly inserted Section 63A makes it an offence for any person registered or required to be registered who:

• (2)(a) fails to issue a fiscal tax invoice or receipt to a buyer (or, if the buyer refuses it, fails to retain a copy for at least 24 months) — fine up to level 7 / imprisonment up to 6 months / both;
• (2)(b) fails to produce a fiscal tax invoice or receipt to an officer on demand within 12 months of the demand — level 7 / 6 months / both;
• (2)(c) manufactures, sells, offers or distributes fiscal memory devices while not an Authority-approved supplier — level 14 / 5 years / both;
• (2)(d) deliberately tampers with an electronic fiscal device so it fails to record taxable transactions — level 14 / 5 years / both.

Note the two tiers: housekeeping failures (issue/retain/produce) sit at level 7; attacks on the integrity of the device or the device market sit at level 14.

B7. The Schedule — civil-penalty orders (the parallel, faster track)

Independently of the criminal route, paragraph 2 of the Schedule lets the Commissioner serve civil-penalty orders for four fiscalisation defaults. Each order carries a 48-hour show-cause suspension (to prove it was issued in error) and a 96-hour remediation window, then bites:

The civil and criminal tracks are expressly cumulative — para 2(1) lets the Commissioner impose the civil penalty "in addition to, and without derogating from" any criminal penalty. A designated officer may, where tampering cannot be proved, downgrade a para 2(6) order to a para 2(8) "faulty device" order (para 2(7) proviso (iii)).

B8. Sections 68CC / 68D — the Virtual Fiscalisation System

Section 68CC (inserted by Finance (No. 2) Act 10 of 2022, gazetted 30 December 2022) authorises the Minister to make regulations creating the Virtual Fiscalisation System — "an electronic platform to enable the electronic recording by taxpayers of transactions that may be liable to tax." Section 68D lets the Commissioner prescribe a user agreement for communication through the system. This is the statutory door through which FDMS's API / virtual route enters: a taxpayer without a hardware till can fiscalise through software interfaced to ZIMRA under a user agreement.

Think of invoicing-under-TaRMS as three layers that must agree.

Layer 1 — The device (where the invoice is born)

Every taxable sale must run through an approved fiscal device. Two species exist:

1. Hardware fiscal device / FER — a physical fiscalised till or printer bought from a ZIMRA-approved supplier. The device has tamper-evident fiscal memory, prints the QR-coded invoice, and pushes the transaction to FDMS. Onboarding runs through a test environment (the supplier configures the device, generates sample outputs — a Fiscal Tax Invoice and a CN/DN — for ZIMRA approval) and then registration in the FDMS live environment.
2. Virtual fiscalisation (API-based) — software that talks to FDMS directly under Section 68CC. The taxpayer downloads the API specification, has a developer build to it, tests on the FDMS test platform, and on approval goes live. This suits e-commerce, ERP-based invoicing, and businesses without a traditional point of sale.

Either way the output is the same: a fiscal tax invoice carrying a QR code and a verification/authentication code.

Layer 2 — FDMS (where ZIMRA holds the record)

The Fiscalisation Data Management System is ZIMRA's back-end. It receives the transaction stream from every interfaced device, stores each fiscal tax invoice, CN and DN, and exposes a public validation portal at https://fdms.zimra.co.zw. Anyone — buyer, auditor, the public — can enter the invoice's verification code or scan its QR code; a clean invoice returns "VALID" and shows that the printed details match what was transmitted. Since the 31 May 2025 buyer-detail mandate, the transmitted record must include the buyer's name, address, TIN, contact details and VAT number (if applicable), so the validation also confirms the buyer was correctly captured.

Layer 3 — TaRMS Invoice Management (where you reconcile before filing)

Inside the SSP, the Invoice Management module (the SSP External Guide lists it as one of the 16 modules) has two pages:

• Invoices — "search, identify and claim invoices for the given taxpayer." This is where a VAT operator views the input-tax invoices FDMS holds under its TIN for a tax period and confirms which it intends to claim — reconciling ZIMRA's record against its own purchase ledger before lodging the VAT 7.
• Diplomatic Missions and Development Partners Invoices — "submit invoices for refund claims by diplomatic missions and development partners," the special zero-rate/refund channel for privileged buyers.

The guide is explicit that the module "integrates with the Fiscalised Electronic Register (FER) ecosystem so VAT-registered operators can match the input-tax invoices on file at ZIMRA against their internal records before lodging the VAT 7." That sentence is the whole point of the module: match first, file second.

How the layers must agree

The discipline is simple to state and easy to fail: the invoice you issue (Layer 1) → the record ZIMRA holds (Layer 2) → the figure you put on the VAT 7 (Layer 3) must be identical. A buyer who claims input tax on an invoice that FDMS does not show under its TIN is claiming on a document that, from ZIMRA's side, does not exist as a valid fiscal invoice — the classic audit flag. A seller whose VAT 7 output tax is lower than the FDMS total of its issued invoices has under-declared — equally visible. Reconciliation in the Invoice Management module is how you catch your own mismatches before ZIMRA's system catches them for you.

Step-by-step: registering and going live on a fiscal device

The following is the practical onboarding sequence drawn from ZIMRA's FDMS guidance; exact button labels in the live FDMS environment may differ — .

1. Confirm you must fiscalise. Any person registered or required to be registered as a VAT operator must fiscalise all taxable supplies (Schedule para 2(2)).
2. Choose the route — hardware FER from an approved supplier, or virtual/API fiscalisation under Section 68CC.
3. Test. Configure on the FDMS test environment with dummy data; generate sample outputs (Fiscal Tax Invoice, CN/DN) for ZIMRA approval.
4. Register the device in the FDMS live environment once the test outputs are approved.
5. Interface with FDMS — establish the live data link. (Failure to interface within 96 hours of an order is a Schedule para 2(4) civil default.)
6. Issue compliant invoices — every invoice now prints with a QR code, verification code and buyer details.
7. Validate sample live invoices at https://fdms.zimra.co.zw — confirm they read "VALID" and that printed details equal transmitted details.

Step-by-step: reconciling input-tax invoices in TaRMS before the VAT 7

1. Log in to the SSP and select the correct taxpayer (TIN) — see tarmslogin/tarmsprofile.
2. Open Invoice Management → Invoices.
3. Search by tax period for the input-tax invoices FDMS holds under your TIN.
4. Match each against your purchase ledger — confirm supplier, date, value, tax, and that buyer details (yours, as the recipient) are correctly captured.
5. Identify/claim the invoices you will include — resolve any missing or mismatched ones with the supplier before filing (the supplier may need to re-issue a fiscal invoice or a CN/DN).
6. Carry the reconciled input-tax total into VAT 7 Part III (Tax Return Management → the pending VAT 7), keeping the per-currency input-tax schedule (tarmsvatworkflow).
7. Submit the VAT 7 and pay each currency stream by the 15th (VAT Act Section 28(1), as shortened by Finance (No. 2) Act 7/2024).

Individuals and micro-traders

A sole trader below the US$25,000 VAT-registration threshold (Finance Act 13/2023) is not a registered operator and so has no fiscalisation obligation and no input-tax claim — VAT is simply a cost. But the moment turnover crosses the threshold (or a voluntary registration is taken), the trader becomes "required to be registered," and Section 63A plus the Schedule penalties attach immediately — even before formal registration paperwork is complete, because the Act uses "registered or required to be registered." The first compliance act of a newly-liable trader is therefore to acquire and install a fiscal device (or onboard virtual fiscalisation) — failing which a single Schedule para 2(2) order can cost US$1,000 + US$25/day.

Worked example — register-acquisition allowance. Tendai's Hardware, a newly-VAT-registered Mutare retailer, buys a fiscalised electronic register for US$1,200. Under the Section 15 deduction the business may claim input credit of 50% × US$1,200 = US$600, recovered on its next VAT 7 (subject to holding the supplier's fiscal tax invoice). Net hardware cost after the allowance: US$600.

SMEs and partnerships

This is where the daily friction lives. Consider Acme Cables (Pvt) Ltd, the Harare SME used across the workflow lessons, filing its VAT 7 for a tax period.

Worked example — input-tax reconciliation. Acme's purchase ledger shows input tax of US$3,000 across 40 supplier invoices. In Invoice Management → Invoices, Acme searches the period and finds FDMS holds only 38 of those invoices under its TIN, totalling US$2,820. Two suppliers issued non-fiscalised invoices (a hand-written one and one from a till that was not interfaced with FDMS). Those two, worth US$180 of input tax, are not valid tax invoices under Section 20 and Section 15(2)(a) denies the deduction.

• If Acme claims the full US$3,000 anyway, the VAT 7 will exceed the FDMS record by US$180 — an automatic audit flag, and on audit the US$180 is disallowed, with Section 39 penalty and Section 71/SI 212-2022 interest on the resulting shortfall.
• The correct move: claim US$2,820 now, and chase the two suppliers to re-issue fiscal invoices (or a fiscal CN then a fresh fiscal invoice). Once the fiscalised invoices appear under Acme's TIN in FDMS, the US$180 can be claimed in a later period (within the 12-month Section 15(2)(a) window).

The lesson for SMEs: a supplier's fiscalisation failure becomes your lost input tax. The Invoice Management reconciliation is the early-warning system.

Large corporates and multinationals

Large operators run virtual fiscalisation via API integrated into their ERP, so that every system-generated invoice fiscalises automatically and streams to FDMS. Their exposures are scale exposures:

• Volume reconciliation. With thousands of invoices a period, a corporate cannot eyeball the Invoice Management page; it bulk-exports the FDMS-held data and reconciles programmatically against the sales/purchase ledgers. A 0.5% mismatch on a large base is a material VAT 7 variance.
• Buyer-detail completeness. Post-31 May 2025, B2B customers expect their TIN and VAT number on every invoice so they can claim input tax; a corporate seller whose API does not transmit buyer details damages its customers' claims and its own relationships.
• Device-market discipline. A group that develops or on-sells fiscalisation software to other entities must ensure it is an Authority-approved supplier — dealing in unapproved fiscal devices is a level-14 / 5-year offence under Section 63A(2)(c).
• CN/DN governance. High volumes of returns and price adjustments mean disciplined fiscal credit/debit note issuance under Section 21, because every correction must itself be fiscalised and validatable.

Fiscalisation and FDMS are recent statutory creations — Section 63A dates only to December 2023, Section 68CC to December 2022, and the buyer-detail mandate to 2025 — so there is, candidly, almost no decided case law directly on fiscalisation. It would be dishonest to manufacture authority where the courts have not yet spoken. The relevant decisions are the invoice-and-input-tax cases that the fiscalisation regime now operates through:

• PIL (Pvt) Ltd v ZIMRA 17-HH-213 — established the 12-month maximum window for holding a tax invoice to support an input-tax claim under Section 15(2)(a), and (in the records context carried in earlier lessons) that ZIMRA may inspect but not seize computer hardware. It anchors the timing limb of the input-tax gate that fiscalisation now feeds.
• IAB Company v ZIMRA 22-HH-032 — annotated in the Act at Section 20(4)(e) (the "description of the goods or services" particular), it illustrates that the content requirements of a tax invoice are litigable: a deficient description can undermine the document.

Beyond these, the area is governed by statute and ZIMRA practice notes/public notices rather than case law, and this lesson says so rather than padding. As disputes over denied input tax for non-fiscalised or non-validating invoices, and over civil-penalty orders under the Schedule, work their way through the Fiscal Appeal/High Court, that gap will fill — but as at this writing it is genuinely sparse.

1. Treating a non-fiscalised invoice as a tax invoice. A hand-written, Word, or pre-fiscal till invoice is not a tax invoice (Schedule definition + Section 20), so the buyer's input-tax claim fails under Section 15(2)(a). Fix: refuse non-fiscal invoices; insist on a fiscal tax invoice with a QR code; validate at fdms.zimra.co.zw before claiming.
2. Claiming input tax on invoices not held by FDMS under your TIN. If the Invoice Management module does not show it, ZIMRA's record does not have it — claiming anyway creates a VAT 7-vs-FDMS variance and an audit flag. Fix: reconcile in Invoice Management before filing; only claim what matches.
3. Ignoring the buyer-details mandate (post-31 May 2025). Invoices missing the buyer's name, address, TIN, contact and VAT number may be rejected for input-tax purposes. Fix: upgrade devices/API to transmit buyer details; give your TIN/VAT number to every supplier.
4. Issuing duplicate invoices. Section 20(1) proviso (a) forbids more than one tax invoice per supply; a second one invites double-claiming and is itself unlawful. Fix: correct via a Section 21 fiscal CN/DN, not a re-issued invoice; replace a genuinely lost original only with a copy marked "copy."
5. Missing the device deadlines and triggering Schedule penalties. Failing to acquire/install (para 2(2)), to interface with FDMS within 96 hours of an order (para 2(4)), or to fix a faulty device (para 2(8)) each runs US$25/day after a 96-hour grace; tampering (para 2(6)) runs US$1,000 + US$50/day. The 48-hour show-cause window is the only chance to prove an order was issued in error. Fix: treat any civil-penalty order as a 48-hour emergency; remediate within 96 hours.
6. Buying or selling unapproved devices. Dealing in fiscal memory devices without Authority approval is a level-14 / 5-year offence (Section 63A(2)(c)). Fix: buy only from approved suppliers; never on-sell devices without approval.
7. Tampering or running a knowingly faulty device. Deliberate tampering is level 14 / 5 years (Section 63A(2)(d)) and a US$1,000 + US$50/day civil order. A faulty device must be rectified/replaced within 96 hours. Fix: report faults immediately; keep the supplier's service record.
8. Not retaining copies. Failing to retain a fiscal tax invoice/receipt for 24 months (where the buyer refused it) or to produce one within 12 months of demand is a level-7 offence (Section 63A(2)(a)/(b)). This sits on top of the general 6-year record-keeping rule (Section 57). Fix: archive fiscal copies; the FDMS record is a backstop, not a substitute for your own retention.
9. Forgetting the 50% acquisition allowance. Operators routinely expense the whole device cost and miss the 50% input credit in Section 15. Fix: claim it on the VAT 7 against the supplier's fiscal invoice.
10. Confusing the de minimis. Below US$10 / the prescribed ZWL-ZiG figure a full invoice is not compelled (Section 20(5)) — but a fiscal receipt still issues and the sale still streams to FDMS. Fix: never read "no invoice required" as "no fiscalisation required."

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.

• A VAT "tax invoice" is a fiscal tax invoice. The Schedule definition + Section 20 fuse the two; a non-fiscalised document is not a tax invoice, full stop.
• No fiscal invoice → no input tax. Section 15(2)(a) gates every input claim on a valid Section 20 invoice held within 12 months; ZIMRA's overlay adds a verifiable QR code and buyer details (Public Notices 50/2023, 80/2024, 30/2025).
• Three layers must agree: the device (FER or virtual/API), FDMS (ZIMRA's record + the https://fdms.zimra.co.zw validation portal), and TaRMS Invoice Management (where you match before you file the VAT 7).
• Buyer details are now mandatory on every fiscal tax invoice (name, address, TIN, contact, VAT number) — hard date 31 May 2025, the same cut-off that completed TaRMS–FDMS integration.
• Section 63A criminal track (Finance Act 13/2023): fail to issue/retain/produce = level 7 / 6 months; deal in unapproved devices or tamper = level 14 / 5 years.
• Schedule civil-penalty track runs in parallel: US$1,000 fixed + US$25–US$50/day for up to 90 days for failure to acquire/install, interface with FDMS, fix a faulty device, or tamper — with a 48-hour show-cause and 96-hour remediation window.
• Virtual fiscalisation is statutory (Section 68CC, Finance (No. 2) Act 10/2022) — an API route for taxpayers without till hardware, under a Section 68D user agreement.
• Claim the 50% acquisition allowance for buying a fiscalised electronic register (Section 15) — half the hardware cost comes back as input credit.
• Reconcile, then file. The Invoice Management module exists so a buyer's VAT 7 never diverges from the FDMS record; that single habit defuses most input-tax audit risk.
• Case law is genuinely thin on fiscalisation (the regime is new) — PIL 17-HH-213 (12-month window) and IAB 22-HH-032 (invoice content) are the nearest authorities; the field is governed by statute and public notice, and this lesson says so rather than inventing precedent.

Table 1 — The three layers of an invoice in TaRMS

Table 2 — Fiscalisation penalties at a glance

All civil orders carry a 48-hour show-cause window and a 96-hour remediation window; civil and criminal penalties are cumulative (para 2(1)).

Diagram — Should I claim this input-tax invoice?

flowchart TD
 A[Supplier hands me an invoice] --> B{Is it a fiscal tax invoice with a QR code?}
 B -->|No| X[Not a tax invoice Section 20 / Schedule def - input tax DENIED Section 15 2 a]
 B -->|Yes| C{Scan QR at fdms.zimra.co.zw - returns VALID?}
 C -->|No| D[Ask supplier to fix / re-issue via Section 21 CN+new invoice]
 D --> C
 C -->|Yes| E{Shown under my TIN in Invoice Management?}
 E -->|No| D
 E -->|Yes| F{Buyer details + my TIN correct?}
 F -->|No| D
 F -->|Yes| G[Claim input tax on VAT 7 Part III within 12 months]

Statutes & sections — VAT Act [Chapter 23:12]

• Section 15(2)(a) — input tax deductible only if a Section 20/Section 21 tax invoice (or Section 20(7) records / customs bill of entry / Section 13 invoice) is held within the return period or 12 months; the fiscalisation gate for input tax. (PIL 17-HH-213 on the 12-month limit.)
• Section 15 deduction — input credit of 50% of the cost of acquiring a fiscalised electronic register (Act 3/2010; re-substituted Act 1/2014).
• Section 20 — tax invoices: 30-day provision (1); recipient-created invoices (2); Section 7(9) deemed-supply documents (3); mandatory particulars incl. "Fiscal Tax Invoice" (4) (amended Finance Act 7/2021 w.e.f. 1 Jan 2022); de minimis US$10 / prescribed amount (5); Commissioner dispensation (6); second-hand-goods records (7).
• Section 20A — transitional use of pre-31 Dec 2021 invoices to 31 Mar 2022 (Finance Act 7/2021).
• Section 21 — credit and debit notes (cancellation, variation, returns).
• Section 63A — fiscalisation offences (inserted Finance Act 13/2023, w.e.f. 29 Dec 2023): issue/retain/produce (level 7); unapproved devices and tampering (level 14).
• Section 68CC / 68D — Virtual Fiscalisation System and user agreements (Finance (No. 2) Act 10/2022, gazetted 30 Dec 2022).
• Schedule (defs + para 2) — "tax invoice," "fiscal tax invoice or receipt," "fiscalised electronic register," "approved fiscal memory device"; civil-penalty orders for failure to acquire/install, interface with FDMS, tamper, or fix a faulty device (US$1,000 fixed + US$25–US$50/day, 48-hr show-cause, 96-hr remediation).
• Section 28(1) — VAT 7 + payment due by the 15th (shortened 25th→15th by Finance (No. 2) Act 7/2024 Section 33, w.e.f. 1 Jan 2025) — carried from tarmsvatworkflow for filing context.

Case law

• PIL (Pvt) Ltd v ZIMRA 17-HH-213 — 12-month maximum for holding a tax invoice to claim input tax (Section 15(2)(a)); inspection-not-seizure of records.
• IAB Company v ZIMRA 22-HH-032 — annotated at Section 20(4)(e); the "description" particular of a tax invoice is litigable.
• Honest note: there is, as yet, no decided Zimbabwean case directly on FDMS, Section 63A, or the buyer-detail mandate — the area is governed by statute and public notice.

ZIMRA guidance

• Comprehensive Guide to the ZIMRA Self-Service Portal — ZIMRA External Guide (§13 Invoice Management: Invoices; Diplomatic Missions and Development Partners Invoices; integration with the FER/FDMS ecosystem; glossary "FER").
• Comprehensive Guide to the VAT 7 — ZIMRA External Guide (Part III input tax requires a valid fiscal tax invoice; input-tax schedule).
• ZIMRA FDMS guidance & validation portal — https://fdms.zimra.co.zw ("VALID" on clean invoices); device test/live registration; hardware vs virtual (API) routes; Fiscal Device Gateway API Specification.
• ZIMRA Public Notices — 50 of 2023 (FDMS compliance), 80 of 2024 (fiscal tax invoice & FDMS compliance), 30 of 2025 (buyer details on FDMS fiscal tax invoice; 31 May 2025 cut-off and TaRMS–FDMS integration).