ZIMRA fiscalisation software for Zimbabwean businesses
Connect your POS, ERP or e-commerce to ZIMRA FDMS through one API and dashboard. Automate compliant fiscal invoices, fiscal day management and verifiable QR receipts.
- ZIMRA FDMS Virtual Fiscalisation
- Certificate lifecycle handled
- Verifiable QR receipts
curl https://api.fiscalflow.co.zw/v1/invoices \
-H "Authorization: Bearer sk_live_…" \
-d device_id=vfd_8842 \
-d currency=USD \
-d '{
"type": "FISCAL_INVOICE",
"lines": [
{ "name": "Consulting", "qty": 1,
"price": 250.00, "tax": "VAT_15" }
]
}'// 200 OK — signed & submitted to ZIMRA
{
"receipt_id": "rcpt_01HZ…",
"zimra_ref": "FDMS-2026-004421",
"qr": "https://fdms.zimra.co.zw/…",
"status": "APPROVED"
}
Virtual
Cloud-based FDMS compliance
USD · ZWG
Multi-currency fiscal receipts
API-first
POS, ERP & e-commerce integrations
The regulatory mandate
A compliance-driven market, not a discretionary one
Zimbabwe's fiscalisation regime is not optional for most operators. All VAT-registered operators must fiscalise under Section 90 of the Income Tax Act (read with Sections 80D/80DD) and SI 104 of 2010, as reinforced by Public Notice 50 of 2023 — a durable foundation for a subscription business.
- Public Notice 50 of 2023
- reinforces mandatory fiscalisation for VAT-registered operators.
- Jan 2024 onward
- FDMS compliance is a prerequisite for Tax Clearance (ITF 263).
- USD 25k threshold
- obligation extends below it — most B2B operators fiscalise anyway.
- Option B virtual
- software interface to FDMS — the segment FiscalFlow targets.
Regulatory detail changes over time — verify current requirements against ZIMRA's published notices at zimra.co.zw.
ZIMRA FDMS overview
Two paths to fiscal compliance
The Fiscalisation Data Management System is ZIMRA's back-end platform for recording taxable sales. Operators choose between upgrading hardware or integrating virtually via API.
Option A
Hardware-based fiscal devices
The taxpayer procures a ZIMRA-approved fiscal device from an approved manufacturer. The supplier tests FDMS compatibility; upon approval the device is registered in the live FDMS platform.
Option B
Virtual fiscalisation
A software-based interface where the taxpayer's server, POS or accounting system connects directly to FDMS via API — no dedicated hardware device required. Suited to centralised systems and small traders via mobile POS.
The problem
Going direct to FDMS is harder than it looks
Businesses attempting Virtual Fiscalisation on their own hit the same recurring obstacles.
Cryptography is unfamiliar
Direct FDMS integration needs CSR generation and NIST P-256 or RSA-2048 signing — territory most in-house teams have never touched.
Approved-supplier bottleneck
ZIMRA requires production access to be requested through an approved software provider, not directly by the taxpayer.
Unforgiving fiscal day state
Open, submit, close, retry — the fiscal day lifecycle is stateful, and a single error can block invoicing entirely.
Constant spec churn
Regulations, tax codes and FDMS API versions evolve, requiring ongoing maintenance most SMEs cannot resource.
Duplicated across systems
POS, ERP and e-commerce each need their own fiscalisation logic — duplicating effort and risk across the organisation.
Solution overview
One integration point, six products
FiscalFlow abstracts ZIMRA's cryptographic, stateful fiscal protocol behind a clean REST API, merchant dashboard, and developer tools. Your systems only ever talk to FiscalFlow.
Fiscal API
REST endpoints for device registration, fiscal day open/close, invoice, credit-note and debit-note submission, and status queries.
Merchant Dashboard
Onboarding, certificate status, fiscal day monitoring, receipt search and reporting in one web console.
Developer Portal
API keys, sandbox credentials, documentation and code samples to ship fast.
Analytics & Reporting
VAT input/output summaries, Z-report history and reconciliation exports.
Webhooks
Real-time events for invoice approval, fiscal day status and certificate expiry.
SDKs & Plugins
Client libraries and drop-in plugins for the common POS, ERP and e-commerce platforms used across Zimbabwe.
Why FiscalFlow
Compliance without the complexity
Everything you need to fiscalise with ZIMRA — whether you integrate via API or manage everything from the dashboard.
Auto compliance
QR-coded invoices, duplicate detection, instant error reporting, and autogenerated VAT and Z-reports at day close.
Data security
End-to-end encryption, secure FDMS submission, and a full audit trail for every fiscal transaction.
Network resilience
Queue transactions when offline. Sync automatically when connectivity returns so invoicing never blocks your business.
Analytics & reporting
Real-time dashboards, transaction history, and exports by product, branch, currency or date.
Dedicated support
Guided onboarding, remote setup assistance, and Zimbabwe-first support from compliance to go-live.
Developer friendly
REST API, webhooks, sandbox environment and documentation — build custom integrations on your stack.
Integrations
Connect your current software stack
FiscalFlow plugs into accounting, ERP, POS and e-commerce systems so teams avoid duplicate entry and manual uploads.
Platform transaction flow
From point-of-sale to a signed fiscal receipt
A typical fiscal transaction moves through FiscalFlow in seven steps — from sale capture through day-end closure validated by FDMS.
- 01
Sale is captured
Your POS, ERP or e-commerce checkout sends a sale to the FiscalFlow API.
- 02
Payload validated
We validate tax codes, currency and line items against the merchant’s registered configuration.
- 03
Invoice signed
The FDMS Adapter signs the invoice with the device certificate — ECDSA-SHA256 or RSA-2048.
- 04
Submitted to ZIMRA
The signed invoice is submitted to FDMS; we store the request and poll for the response.
- 05
QR code built
On success, FDMS confirmation data is used to build the verifiable QR code for the receipt.
- 06
Receipt returned
The fiscal receipt — with QR and ZIMRA reference — flows back to your system and is logged for audit.
- 07
Day closed
At day end, the merchant or FiscalFlow triggers fiscal day closure; FDMS validates fiscal counters and confirms closure.
Getting started
Onboarding in four clear steps
From sign-up to production fiscalisation with guided checks at each stage.
Step 1
Sign up
Create your account and submit business and tax details.
Step 2
Connect device
Register your virtual fiscal device and certificate workflow.
Step 3
Test in sandbox
Open day, submit sample invoices, and close day successfully.
Step 4
Go live
Move to production and issue ZIMRA-compliant fiscal receipts.
Live preview
See invoice data update in real time
Preview totals, VAT and fiscal metadata instantly before submission.
Invoice inputs
Customer: Acme Corporation
Line items: 3
Subtotal: $1,445.00
VAT (15%): $216.75
Total: $1,661.75
Fiscal output
Status: PENDING
Device ID: HRE-FD-00147
Fiscal Day: 247
Global Counter: 8847
Verification: 7F3A-B8C2-D4E6-9K1M
Fiscal day lifecycle
A state machine we handle so merchants aren’t left blocked
FDMS enforces a stateful fiscal day model that the integration layer must respect. FiscalFlow surfaces validation errors clearly instead of leaving merchants stuck silently.
Opened
A fiscal day must be opened before any invoice can be created. Opening can be recorded without active internet at that moment, provided it is transmitted before receipts are sent.
Receipting
Invoices, credit notes and debit notes are signed and submitted while the day is open.
CloseInitiated
Closure is a two-step process. While closing, no new closure request or invoice is accepted.
Validated / Closed
FDMS validates fiscal counters and confirms closure — or surfaces errors to correct and resubmit.
Security & cryptography
Non-negotiable requirements, implemented natively
FDMS integration has hard cryptographic and transport security requirements. FiscalFlow builds them in — and layers its own platform-level controls on top.
X.509 v3 device certificates
Issued after a Certificate Signing Request (CSR) submitted to FDMS.
NIST P-256 or RSA-2048 signing
ECDSA-SHA256 or SHA-256WithRSA — secure to current planning horizons.
Certificate expiry tracking
Per-device expiry monitoring with renewal before lock-out.
Verifiable QR codes
Generated from the transaction signature hash, verifiable on the public FDMS portal at fdms.zimra.co.zw.
HTTPS-only FDMS transport
All communication with FDMS endpoints is over HTTPS. Device registration is the only bootstrap endpoint that does not require a certificate.
Platform-level security
- OAuth2 / API-key auth with per-merchant scoping
- Role-Based Access Control across dashboard & admin
- mTLS for service-to-service traffic in production
- Encryption at rest and TLS 1.2+ in transit
- Comprehensive audit logging of every fiscal submission, certificate operation and admin action
Testimonials
Trusted by Zimbabwean businesses
“FiscalFlow cut our FDMS integration from months to days. The API is clean, the dashboard surfaces fiscal day errors clearly, and month-end is far less stressful.”
“We needed virtual fiscalisation without building cryptography in-house. Sandbox to production was straightforward, and the team understood ZIMRA requirements.”
Business model
Usage-based pricing that scales with compliance
FiscalFlow monetises through subscriptions and per-invoice fees. Start free in sandbox, pay only when you fiscalise real transactions.
SaaS subscription
Tiered monthly fee per merchant or branch for API and dashboard access.
Per branch / device
Transaction fees
Small fee per fiscal receipt processed above plan allowance.
Per invoice
Enterprise licensing
Dedicated infrastructure, SLAs and support for large retail and ERP clients.
Annual contract
White-label
FiscalFlow engine embedded under a partner's own brand.
Licence + revenue share
Integration services
Paid setup, custom plugin development and migration support.
Project-based
Starter
For developers evaluating the API in sandbox.
- Full sandbox FDMS environment
- Up to 100 test invoices / month
- REST API & webhook access
- Community support
Growth
For SMEs and single-branch merchants going live.
- Production fiscalisation
- Device registration & cert lifecycle
- Automated fiscal day management
- Per-invoice pricing after allowance
- Email & chat support
Enterprise
For POS vendors, chains & payment processors.
- Volume per-invoice pricing
- White-label & multi-tenant
- Dedicated infrastructure & SLA
- Priority ZIMRA change tracking
- Solutions engineering
FAQ
Frequently asked questions
Key compliance and integration questions from Zimbabwean businesses.
What is ZIMRA fiscalisation?
It is the requirement to submit invoice and receipt data to ZIMRA FDMS for compliance and auditability.
Can FiscalFlow integrate with existing systems?
Yes. Use our REST API and webhooks for ERP, POS and e-commerce integrations.
What happens when internet is down?
Transactions can be queued and synchronized once connectivity returns, reducing business disruption.
Do I need special hardware?
No dedicated hardware is required for virtual fiscalisation; a browser-based workflow is supported.
Contact
Need help with onboarding or integration?
Reach the team for demos, technical support, and partnership enquiries.
Ship ZIMRA-compliant invoices this week
Skip months of FDMS integration work. Get sandbox keys, sign your first fiscal invoice, and go live with a single, well-documented API.