Fiscalisation · Zimbabwe
Fiscalisation means configuring a fiscal device to record each sale and transmit it to ZIMRA servers at the time of sale. It applies to VAT-registered operators under SI 104 of 2010 and, under section 90 of the Income Tax Act, to taxpayers below the US$25,000 VAT threshold too. A virtual fiscal device lets your existing accounting system interface directly rather than adding a till.
Last updated 2026-09-04. Published by Umbra ERP.
ZIMRA defines fiscalisation as the configuring of fiscal devices to enable them to record and transmit sales and other tax information at the time of sale to the ZIMRA servers. Two parts of that definition carry all the weight, and both are easy to skim past.
The first is "at the time of sale". Fiscalisation is not a reporting exercise you complete at month end. It is a requirement that the transaction is captured and transmitted as it happens, which makes it a change to your operating process rather than a change to your bookkeeping. A business that reconciles carefully once a month can still be entirely non-compliant, because the obligation attaches to the moment of the sale, not to the accuracy of the eventual return.
The second is "fiscal device". A fiscal device is not simply software that produces a nicely formatted invoice. It contains what ZIMRA calls fiscal memory: a special read-only memory permanently built into the device to store tax information. The point of that memory is that the record cannot be edited after the fact. This is the conceptual heart of fiscalisation and the reason it cannot be satisfied by a spreadsheet, a Word template or an invoice book, however diligently they are kept.
Once you hold those two ideas together, the practical shape of the obligation becomes clear. You need something that captures every sale as it occurs, writes it somewhere it cannot later be quietly altered, and passes it to ZIMRA. The question for most businesses is not whether to do this but which of the recognised device types is the least disruptive way to do it.
There are two separate legal bases, and businesses routinely know about the first and not the second.
The first is Statutory Instrument 104 of 2010, which requires VAT-registered operators to fiscalise. If you are registered for VAT, this has applied to you for well over a decade and is not news.
The second is section 90 of the Income Tax Act (Chapter 23:06), which ZIMRA cites as extending the requirement to all taxpayers, including those whose turnover falls below the US$25,000 VAT registration threshold. This is the part that surprises people. A small trading company that has correctly concluded it does not need to register for VAT can still fall within the fiscalisation requirement, because the second basis does not depend on VAT registration at all.
The practical consequence is that "we are too small to register for VAT" is not, on its own, an answer to "why are you not fiscalised". The two thresholds are not the same threshold, and they do not come from the same statute. If your position rests on being below the VAT threshold, it is worth confirming with your accountant or with ZIMRA directly how section 90 applies to your specific circumstances, because the exposure sits in exactly that gap.
Registration for VAT itself becomes compulsory once taxable supplies exceed, or are likely to reach, US$25,000 or the ZiG equivalent within a twelve-month period, a threshold effective from 1 January 2024. Note the phrase "likely to reach". The obligation can crystallise on a reasonable forward expectation, not only on a figure you have already banked, which means a business winning a large contract should be thinking about registration when it signs, not when it invoices.
ZIMRA recognises four categories of fiscal device, and the differences between them matter a great deal to how much your operation has to change.
For a business that issues invoices rather than till slips, the first three options all involve bolting hardware onto a process that does not naturally have a counter in it. A consultancy invoicing eight clients a month does not want a till. A wholesaler raising invoices against purchase orders does not want to re-key each one into a separate device just to obtain a fiscal record.
Virtual fiscal devices are what make fiscalisation tractable for those businesses. ZIMRA describes virtual fiscalisation as allowing a direct interface of taxpayer server to ZIMRA server, or a direct connection from an accounting or point-of-sale system. In other words, the system you already raise invoices in can be the thing that fiscalises them, and no one has to re-key anything. ZIMRA publishes the API documentation for this free of charge on its website.
That is a meaningful change in the compliance burden. It moves fiscalisation from "buy and maintain a separate machine, and remember to use it" to "connect the system you already use". It also moves the risk: the failure mode is no longer a broken till, it is a broken integration, which is quieter and therefore easier to miss.
Under the Value Added Tax Act (Chapter 23:12), a registered operator must issue fiscal tax invoices within 30 days of the supply. Two words in that sentence are worth separating.
"Fiscal" means the invoice is the output of a fiscal device and carries the identifiers that prove it. A document that looks like an invoice but was produced outside the fiscal process is not a fiscal tax invoice, no matter how complete its contents are.
"Within 30 days" is a deadline that runs from the supply, not from when you get round to billing. For businesses that invoice in arrears, in batches, or after a job is signed off, this is the requirement most likely to be breached without anyone noticing, because the internal process feels orderly. The invoice run happens reliably every month; it simply happens more than 30 days after some of the supplies it covers.
There is one relief worth knowing. A supplier is not required to provide a fiscal tax invoice where the amount is less than US$10.00 or the ZiG equivalent, effective 1 September 2022. That threshold is low enough that it is genuinely useful only to businesses making a large volume of very small sales, and it is not a general exemption.
On the numbers themselves, the standard rate of VAT is 15.5 per cent. It is worth stating plainly because 15 per cent was the rate for many years and remains lodged in a lot of templates, spreadsheets and memories. A pricing model or an invoice template still calculating 15 per cent is understating the tax, and the difference accrues quietly on every line.
The VAT return itself is the VAT7. You declare total sales and the tax charged on them, which is your output tax, and you subtract the tax on your purchases, both cash and credit, which is your input tax. A positive balance is remitted to ZIMRA. A negative balance generates a refund.
Refunds carry a minimum threshold: US$60.00 or the ZiG equivalent for processing. Below that, the balance is not going to come back to you as cash in that cycle, which is worth building into expectations rather than treating as an error.
The relationship between fiscalisation and the return is straightforward once you see it. Fiscalisation is the mechanism by which ZIMRA already holds your sales data before you file. The return is not the moment of disclosure; it is a reconciliation against something the authority can already see. This is precisely why the integrity of the fiscal record matters more than the tidiness of the return. If the two disagree, the fiscal record is not the version that has to explain itself.
Fiscal devices do not simply post transactions into a void. They operate in fiscal days, which are opened and closed, and they maintain counters that number receipts in an unbroken sequence.
That sequencing is the entire point. An unbroken counter is what makes a missing sale detectable. If receipts run from 1 to 400 and number 273 does not exist, that is visible without anyone needing to audit your bank statements. It is the same logic as a pre-numbered receipt book, implemented so that it cannot be defeated by removing a page.
Operationally this means fiscalisation imposes a rhythm that a plain invoicing system does not have. A fiscal day has to be opened before transactions can be submitted against it, and closed when the trading period ends. A day left open, or a submission attempted against a closed day, is not a cosmetic problem: it breaks the sequence the whole mechanism depends on.
For a business moving from ordinary invoicing to fiscalised invoicing, this is the genuinely new discipline. Everything else has an analogue in what you already do. Opening and closing a fiscal day does not, and it is the step most likely to be forgotten in the first few months.
Umbra ERP supports ZIMRA fiscalisation through a FiscalCloud virtual fiscal device. It is worth being exact about what that does and does not mean, because this is an area where vague marketing does real damage.
What Umbra does: you configure the virtual device against your account and test the connection. You open and close fiscal days from within Umbra. You submit invoices, credit notes and debit notes to the device, either one at a time or as a batch. Every invoice carries a visible fiscal status, so you can see at a glance which documents have been submitted, which are pending and which failed. Tax codes are mapped for you, with the standard rate, zero-rated supplies and exempt supplies each mapped to the code ZIMRA expects.
What Umbra does not do: it does not fiscalise an invoice automatically when you issue or send it. Submission is an action a person takes, per invoice or per batch. It is also not a direct integration with ZIMRA and not a ZIMRA-certified device in its own right; the connection runs through FiscalCloud as the virtual fiscal device. Umbra does not file your VAT7 for you either. The filing obligation stays with the business.
We would rather say that plainly than let you discover it at the wrong moment. If you need every invoice fiscalised the instant it is issued with no human in the loop, that is a workflow you should confirm carefully before committing, wherever you buy your software.
Most of the pain in a fiscalisation project comes from data that was never captured properly in the first place, not from the integration itself. The work below is worth doing before you connect anything.
VAT-registered under SI 104 of 2010, or below the threshold but caught by section 90 of the Income Tax Act. Confirm this with your accountant or ZIMRA rather than assuming, because it determines whether the question is urgent or already overdue.
Fiscal submissions want proper buyer details for the transactions that require them. A customer list full of "Cash Sale" and half-remembered trading names becomes a queue of failed submissions. Fix it while it is a data-tidying job, not a compliance incident.
Every product or service needs a defensible tax treatment: standard-rated, zero-rated or exempt. If your catalogue currently carries a single default rate applied to everything, that is the mapping problem you will hit on day one.
Anything still calculating 15 per cent rather than 15.5 per cent needs updating, including spreadsheets, quotation templates and any pricing model you use to bid work.
The 30-day rule bites hardest on businesses that invoice in arrears. If some supplies are being billed 45 days late today, fiscalising the process will make that visible rather than fix it. Recurring billing schedules and quotations that convert on acceptance both shorten the gap structurally.
Name the person and the time. This is the step with no analogue in your current process, so it needs an owner rather than an assumption.
Umbra helps with several of these directly. Client self-service links let a customer fill in their own legal name, address, TIN and VAT number against a quotation, which is a far more reliable way to get accurate buyer details than typing them from a WhatsApp message. Recurring invoices and recurring quotes shorten the lag between supply and invoice. Prices come from your catalogue rather than being retyped per document, which keeps tax treatment consistent across every line.
Possibly yes. ZIMRA cites two bases: SI 104 of 2010 covers VAT-registered operators, and section 90 of the Income Tax Act (Chapter 23:06) extends the requirement to all taxpayers, including those below the US$25,000 VAT threshold. Being under the VAT threshold does not by itself put you outside the fiscalisation requirement. Confirm your position with your accountant or ZIMRA.
A Virtual Fiscal Device, or VFD, is software that performs the role of a fiscal device without dedicated hardware on your counter. ZIMRA describes virtual fiscalisation as allowing a direct interface of taxpayer server to ZIMRA server, or a direct connection from an accounting or point-of-sale system, so the system you already invoice in can be what fiscalises the sale.
The standard rate is 15.5 per cent. This catches people out because 15 per cent was the rate for a long time and still appears in many invoice templates and pricing spreadsheets. Some supplies are zero-rated and others are exempt, which are different treatments and are mapped to different codes on a fiscal submission.
Within 30 days of the supply, under the Value Added Tax Act (Chapter 23:12). The clock runs from the supply itself, not from your invoice run, which is why businesses that bill in arrears or in monthly batches are the ones most likely to breach it without realising.
Yes. A supplier is not required to provide a fiscal tax invoice where the amount is less than US$10.00 or the ZiG equivalent, effective 1 September 2022. It is a narrow relief aimed at high-volume, low-value sales rather than a general exemption.
No. Umbra supports ZIMRA fiscalisation through a FiscalCloud virtual fiscal device, and you submit invoices, credit notes and debit notes individually or as a batch. Issuing or sending an invoice does not fiscalise it on its own. Each invoice shows its fiscal status so you can see what has been submitted and what has not.
No. Umbra connects to FiscalCloud, which acts as the virtual fiscal device. Umbra is the system you raise and manage the documents in, and it handles device configuration, fiscal days, submission and status tracking, but it is not itself a certified device and it does not file your VAT7 return.
Fiscal devices operate in days that are explicitly opened and closed, maintaining an unbroken counter across receipts. The sequence is what makes a missing sale detectable: if the numbering jumps, that is visible without an audit. Submissions must fall inside an open fiscal day, so opening and closing it needs a named owner.
Regulatory figures on this page are taken from the following primary sources. Tax rates and thresholds change; check the source before relying on a figure.