Point of Sale, Accounting and ZIMRA Fiscalisation.
All on one platform.
Connect once. Every invoice after that is signed, submitted and verified automatically.
Follow a 5-minute guide for Odoo, Zoho Books or QuickBooks — or upload Excel, or POST to our REST API. Your team keeps invoicing exactly as before.
ThatFiscal signs each invoice with your registered device key, chains the hash, submits to ZIMRA FDMS, and maintains your fiscal counters and day-ends automatically.
QR code, verification code and fiscal numbering come straight back onto your invoice. Errors are explained in plain language with one-click resend.
ZIMRA requires every VAT-registered business to issue fiscal tax invoices through a registered fiscal device, with the full 8-digit HS code on every line. ThatFiscal is your virtual device — signed, submitted and verified in real time.
The FDMS gateway fully supports non-VAT taxpayers (your invoices simply carry no VAT number and may use 4-digit HS codes). Fiscalising early gives you ZIMRA-recognised invoices that tenders, corporates and NGOs increasingly demand — and a clean, audit-ready sales record from day one.
VAT registration becomes compulsory once your rolling 12-month sales reach ZIMRA's threshold (currently US$25,000). ThatFiscal adds your USD and ZWG sales together, warns you as you approach the line, and tells you the moment you cross it — so registration is a plan, not a panic.
Raise the invoice and the entry is already made. Sales, VAT, the customer's balance, the stock that left the shelf — all of it moves at once, because it is one system rather than an accounting package with a fiscal bolt-on.
A full Zimbabwean chart ready on day one — assets, liabilities, equity, income, cost of sales and expenses — and you can add your own accounts, or rename ours.
Statements computed on accounting principles, sectioned and subtotalled, with gross, operating and net profit derived from each other — on screen and as a document you can hand to a bank.
Who owes you and what you owe, aged into buckets. Record a payment against an invoice, say which account it landed in, and the bank balance moves with it.
Weighted-average cost, per branch, moving on every sale, credit note, purchase and transfer. Cost of sales follows from what the stock actually cost, not from a guess.
Quote, sales order, invoice. Purchase order, goods in, supplier bill, payment. Each document becomes the next one, so nothing is keyed twice.
Output tax by rate, input tax claims, withholding certificates and import VAT on bills of entry — netted the way a VAT7 nets them, per currency, because TaRMS takes a USD schedule and a ZWG schedule.
Real accounts in real currencies, money in and out, transfers between them, and rules that match a bank statement line to the entry it belongs to.
Standing charges raised on their schedule — held for your approval or sent straight through — and fiscalised down the same path as everything else.
Every invoice is signed and submitted to ZIMRA FDMS as it is raised. Compliance stops being a month-end job and becomes something that already happened.
The fiscal half of the platform: what was filed, what ZIMRA said back, and the paperwork to prove it.
Select any months — Jan, Jan–Feb, a whole quarter — and see total fiscalised invoices, credit notes, and net value per currency instantly.
Output VAT by rate and by currency for any period, split taxable vs VAT vs gross, with credit notes netted off correctly.
Fiscal days open and close themselves. Browse every Z-report, download it, and reconcile counters against your ledger.
The full fiscal register — invoice number, global number, verification code, status — as CSV, ready for your auditor or ZIMRA query.
Upload your logo, banking details and standard notes once — they appear on every fiscalised document. Included on Standard and Enterprise; available to Starter as an add-on.
RCPT047 becomes "This product is missing an HS code — add it and resend." Fix, click resend, done.
Every receipt is device-signed and chained per the FDMS spec §13 — verified against ZIMRA's own worked examples.
USD and ZWG side by side, multiple devices and branches under one login, counters kept per currency and tax.
Email, phone and a knowledge base in plain language. You talk to the engineers who built it, in your timezone.
Native webhooks, simple CSV uploads, or one REST endpoint — whichever your system speaks. Every path ends in the same real-time ZIMRA compliance.
Two doors, because two different people come through them. One is written for whoever raises the invoices. The other is written for whoever writes the code.
Plain-language guides that assume nothing and end with a working result.
One endpoint fiscalises anything. Authentication, invoices, credit notes, status, Z-reports and webhooks — with copy-paste examples.
Read the API docs →Three trades that fiscalise for three different reasons — a till that cannot stop, a practice holding other people's books, and a warehouse where every line needs a tariff code.
Register online as an individual or a company, onboard your clients from your own portal, and keep a 20% recurring commission — applied as a discount on every client payment you make.
