ThumaBooks
ENSNNDSWFR
ZIMRA, without the queue

Fiscalisation that catches up with you.

Zimbabwe requires VAT-registered businesses to fiscalise their sales through ZIMRA's Fiscalisation Data Management System (FDMS). Most software makes that your problem. ThumaBooks makes it a background job: register your fiscal device once, and every invoice and credit note is submitted.

How it works

Four steps, one of them yours

01

ZIMRA issues your device

You register for fiscalisation with ZIMRA and receive your fiscal device credentials — a device ID, a serial and a key. That part is between you and the authority; we tell you exactly what to ask for.

02

You register it once

Enter the credentials on the Books Desk. The key is stored and never shown again — not on any screen, not to us in support, not in any export. Registering is itself recorded in your access log, with a name on it.

03

Every sale, from the day it starts

From the moment your device is registered, every invoice and credit note you issue is signed, numbered and sent to ZIMRA in order, within a minute — and if the connection drops, it waits and catches up. Sales from before the device stay as they were: ZIMRA takes a receipt dated inside an open fiscal day, so ThumaBooks never back-dates one.

04

Every document keeps its reference

The fiscal reference and verification detail ZIMRA returns are stored on the invoice itself, permanently. A submission that fails says why, in a sentence, and retries; a submission that succeeded is never sent twice.

The discipline underneath

Rules a tax inspector would recognise

A fiscalised sale cannot be voided
Once an invoice carries a fiscal reference, cancelling it is refused — in a sentence that tells you the lawful alternative: a credit note, which is itself fiscalised as one.
Built
A submitted record is never rewritten
Fiscalisation records are append-only, like the ledger they describe: a submission's identity is frozen at write, and "submitted" is a terminal state nothing can un-set.
Built
Failures are visible, not silent
A rejected submission shows its reason on the Desk's month-end screen and keeps retrying up to a limit. What is queued, what went through and what failed is a list you can read, not a promise.
Built
Checked against ZIMRA's rules before it is signed
Every rule ZIMRA's system marks a receipt against is run on the receipt first. One ZIMRA would mark red — the kind that stops a fiscal day closing — is never signed or sent; the invoice says why, in a sentence, with ZIMRA's own code.
Built
ZIMRA's own signature, verified
When ZIMRA accepts a receipt, and when it closes a day, it signs what it took. ThumaBooks checks that signature against ZIMRA's certificate and keeps the result with the receipt: proof, held by you, that ZIMRA has exactly what you sent.
Built
Your suppliers' receipts, checked with ZIMRA
A supplier's fiscal receipt you photograph is checked on ZIMRA's verification portal. One ZIMRA does not know, holds with a different total, or has since credited is flagged before you claim its VAT — not found at audit.
Built
Go-live with your taxpayer pack
The integration is built and tested against ZIMRA's FDMS interface. Connecting each taxpayer is a configuration step done with your ZIMRA integration pack when your device is issued.
Per taxpayer, at onboarding

Fiscal transmission is a service on your instruction, governed by its own Fiscal Transmission Terms, published before any customer is asked to agree to them. ThumaBooks submits the documents; the return you file, and what you file in it, remain yours.

Fair questions

Asked by people who have met a fiscal printer

No. FDMS is ZIMRA's online interface; your "device" is a registered credential, not a machine on your counter. Your phone rings up the sale, and ThumaBooks submits it.
You keep selling. Submissions queue and go through when the connection returns, in order, each one exactly once. The month-end screen shows anything still waiting, so nothing is silently unfiled.
A credit note. The product will refuse to void a fiscalised sale and say so in plain words, because that is the rule ZIMRA holds you to — the credit note corrects the books and is itself submitted as a fiscal credit note.
No — and ThumaBooks knows it. A business without VAT registration keeps clean books with no VAT accounts and no fiscalisation; when you grow into registration, the machinery is already there.

Be compliant by default

The books, the VAT working totals and the fiscal submissions all come from the same entries — so they cannot disagree with each other.

Ask us about your case