Tenant management
Create and suspend clients, control licences, and keep every Odoo database under a clear admin umbrella.
ZIMRA FDMS bridge · by Thinking Minds
Fiscalisation for Odoo — centralised, keyed, and under your control
Fiscal Hub is the server between your Odoo databases and ZIMRA FDMS. Thin clients send documents with a Bearer API key; device credentials and FDMS talk stay on the Hub — not on every ERP instance.
Built in Zimbabwe by Thinking Minds · www.thinkingminds.co.zw
What you get
Everything you need to run multi-tenant fiscalisation without scattering secrets across Odoo sharded installs.
API key lifecycle
Issue and revoke Bearer keys per tenant. Keys follow licence expiry so inactive clients cannot fiscalise.
Device routing
Map Hub device refs to ZIMRA journals. Odoo never stores device secrets — the Hub holds routing.
Document fiscalisation
POST invoices and credit notes with Idempotency-Key, then poll status by hub_ref until signed.
Admin & client portals
Admins run the whole estate. Clients sign in to manage their own keys, devices, and licence renewals.
Odoo-ready thin clients
Works with zimra_fiscal_v20 / v19. Point Hub URL + API key in Settings → ZIMRA Fiscalisation.
How it works
Three steps from empty Hub to invoices fiscalising in Odoo.
Provision a client
Admin creates a tenant, optional portal user, and first device ref (e.g. hq-backoffice).
Issue an API key
Copy the Bearer key into Odoo. Licence state and key expiry stay in sync on the Hub.
Fiscalise from Odoo
Posting invoices hits Hub → FDMS path. Clients never hold device keys or talk to FDMS directly.
Admin
Create or suspend clients, provision devices, issue or revoke API keys for any tenant, and oversee licence status across the estate.
Client
Sign in for your tenant only — manage your API keys, view devices, and buy or renew licence so keys stay valid for Odoo.
Client API
Authenticate with Authorization: Bearer fh_live_…. Document posts require an Idempotency-Key.
| Method | Path | Purpose |
|---|---|---|
| GET | /v1/licence | Licence state, expiry, and API key expiry |
| GET | /v1/devices | Active device routing keys for the tenant |
| POST | /v1/documents | Fiscalise invoice or credit note (Idempotency-Key required) |
| GET | /v1/documents/:hub_ref | Poll document signing status |
Built by Thinking Minds
Software for Zimbabwean operations
Fiscal Hub is developed and supported by Thinking Minds — helping businesses run compliant, practical systems around Odoo, fiscalisation, and day-to-day operations. Need setup, custom modules, or a Hub deployment for your organisation? Get in touch.