Fiscalisation, yakaitwa nyore

Risiti yega yega inosvika kuZIMRA — kunyange magetsi akadzima.

Shandisa ThumaBooks, batanidza system yako yemabhuku, kana kuti shandisa API yedu. Mudziyo wefiscal uri mugore: hapana kuisa, hapana kiyi yekuchengeta, hapana injiniya anouya.

Built on ZIMRA's Fiscal Device Gateway API v7.2 Every receipt signed, chained and checked against ZIMRA's signature Records kept seven years on every plan

1 live · 104 countries tracked. Greyed countries open once the code is done and the tax authority has certified it.

One fiscal device, three doors

Nzira nhatu dzekuita fiscalisation

The same signing, the same queue, the same ZIMRA — whichever door the invoice comes through. A $5 customer's receipt is as compliant as an enterprise's: plans sell reach and support, never compliance.

ThumaBooks package

Your books and your fiscal device, together

For a shop, a salon, a consultant, a growing business. Sell from the phone app or the Books Desk; every invoice is fiscalised the moment it is issued.

  • Register with the device ID and activation key ZIMRA gives you — about a minute
  • A4 invoices, 80 mm and 58 mm slips over Bluetooth, PDF by email
  • Fiscal day opened and closed for you; Z and X reports
  • Credit and debit notes, HS codes, standard, zero-rated and exempt lines
Start with ThumaBooks
Integration

Keep your accounting system

Xero, QuickBooks, Zoho Books, Sage, Odoo or a spreadsheet stay where they are. Their invoices are fiscalised by your ThumaBooks device, and the QR and verification code come back.

  • Send the invoice exactly as your system exports it — we map it
  • Tax-exclusive lines become what the customer paid, to the cent
  • A tax code we can't place is refused with a sentence, never guessed
  • Spreadsheet import: a whole month in one file, never twice
See the integrations
API and resellers

Build fiscalisation into your product

For POS makers, ERP vendors and integrators. One integration fiscalises for every client who grants you access — and stops the moment they revoke it.

  • Test keys from day one: see exactly what ZIMRA would receive
  • Idempotent by your own invoice ID; signed webhooks
  • Partner keys your clients grant and revoke themselves
  • Errors with a code, the field, and a sentence a person can act on
Read the API
How it works

Four steps. One of them is yours.

  1. Register the deviceEnter the device ID and activation key from ZIMRA's portal. We verify the taxpayer with ZIMRA, generate the key pair, and register — the private key never leaves our key service.
  2. Invoice as you do todayFrom ThumaBooks, your accounting system, a spreadsheet or your POS. Each one is checked against every ZIMRA rule before it is sent, so a refusal is caught while it can still be fixed.
  3. Signed and sent at onceEach receipt is signed, chained to the one before, and submitted in real time. If the line drops, it waits in a queue and goes, in order, when the line returns.
  4. Printed with proofThe QR code and verification code ZIMRA requires, on A4, 80 mm or 58 mm. ZIMRA's own signature on the receipt is checked, every time.
Load-shedding proof

Power cuts don't stop the till

ZIMRA expects every point of sale to stay connected. Zimbabwe's grid doesn't always agree. So a sale made offline is signed and numbered on the spot, kept in order, and reported the moment the connection is back — with an alert to you, and to our operations team, if anything is still waiting after four hours.

If ZIMRA puts a device in Offline mode, each closed day is filed as ZIMRA's own files, under 3 MB, in sequence, and followed until ZIMRA has processed them.

What every plan includes

  • Real-time submission, the offline queue and automatic resubmission
  • Automatic fiscal day open and close; certificate renewal before it expires
  • ZIMRA's signature verified on every receipt and every closed day
  • Our receipts sampled against ZIMRA's public verification portal
  • Supplier invoices checked against ZIMRA before you claim the VAT
  • Seven years of records and a full export — even if you stop paying
  • The app in 62 languages; this site and the Desk in English, Shona, Ndebele, Swahili and French
Integrations

Works with what you already use

Each page says honestly how the connection works today — document forwarding through the API, or a spreadsheet — and what is still coming.

For developers

One request. A lawful invoice back.

Send the invoice with your own ID. The answer carries what you print: the verification code, the QR payload and ZIMRA's numbers — now, or by signed webhook once the device has sent it. Send it again and you get the same document, never a second one.

The quickstart

curl https://api.thumaexpress.com/api/v1/fiscal/invoices \
  -H "Authorization: Bearer tbk_test_…" \
  -H "Idempotency-Key: INV-0042" \
  -H "Content-Type: application/json" \
  -d '{
    "source": "my-pos", "externalId": "INV-0042", "currency": "USD",
    "lines": [{ "description": "Cement 50kg", "quantity": 2,
                "unitAmount": 1155, "taxClass": "standard" }],
    "payments": [{ "method": "cash", "amount": 2310 }]
  }'
ZIMRA Public Notice 101 of 2024

Zvingakurasikirai

ZIMRA's penalties are per point of sale, per day. Work out the exposure for your business.

From the notice: US$25 per point of sale per day for not meeting the interface requirements (up to 90 days), US$1,000 for failing to issue a fiscal invoice, and more for tampering. ZIMRA's public notices. This is an illustration, not tax advice.

US$2,250

3 points of sale × US$25 × 30 days.

For buyers

Is that supplier's receipt real?

Input VAT on an invoice that was never fiscalised cannot be claimed. Paste the link from the receipt's QR code to see what it claims — then check it on ZIMRA's own site, the only place that can confirm it.

ThumaBooks customers don't need to do this by hand: supplier invoices are checked against ZIMRA before they are paid.

The honest comparison

Three ways to comply in Zimbabwe

ZIMRA's free portal, a hardware fiscal device, and ThumaBooks Fiscal compared
ZIMRA's portalHardware fiscal deviceThumaBooks Fiscal
CostFreeTypically US$500–800 a device, plus setupFrom US$5 a device a month (intended)
How receipts get to ZIMRATyped in by handFrom the device at the tillAutomatically, from ThumaBooks, your system or the API
Power cutWaitDepends on the deviceSigned offline, sent in order when the line returns
Your accounting systemRe-enter everythingUsually a separate boxXero, QuickBooks, Zoho, Sage, Odoo, spreadsheets, any ERP
Something goes wrongYou noticeYou call the supplierYou and our operations team are alerted, with what to do
Questions

What people ask first

Do I still need a device from ZIMRA?

You need a device registration: ZIMRA issues a device ID and activation key on its portal, one per till that issues receipts at the same time. You don't need hardware — ThumaBooks is the device, in the cloud.

Is ThumaBooks Fiscal certified by ZIMRA?

ThumaBooks is built to ZIMRA's Fiscal Device Gateway API v7.2 and its certification run is rehearsed against every scenario in the specification. The application by Thuma Books Zimbabwe (Private) Limited is with ZIMRA; the trust page shows its status and, once issued, ZIMRA's reference.

I use Xero (or QuickBooks, Zoho, Sage, Odoo). Do I have to switch?

No. Keep it. Its invoices are fiscalised through your ThumaBooks device, and the verification code and QR come back to print. See integrations.

What happens if I stop paying?

Everything already fiscalised stays yours to see and export, for seven years. A lapsed subscription never holds back what was signed.

Which other countries are coming?

We track 104 countries that require fiscal receipts or e-invoicing. Each opens once the code is done and the tax authority has certified it — until then it is greyed in the list. See them all, and ask to be told when yours opens.