Integrations / ZIMRA FDMS
ZIMRA FDMS virtual fiscalisation for ERPNext
ZIMRA's approved software path lets ERPNext interface with FDMS directly, no fiscal hardware. We engineer that API integration, including the buyer-detail and QR requirements in force since May 2025.
Why this matters now
Every VAT-registered operator must fiscalise, and since 31 May 2025 fiscal devices must transmit buyer details including TIN and VAT number to FDMS and integrate with TaRMS. Input tax claims are only permitted on fiscal invoices from FDMS-connected systems bearing a QR code that validates on the ZIMRA portal. The obligation extends below the USD 25,000 VAT threshold.
ERPNext and compliance in ZimbabweWhat the integration covers
Direct interface with FDMS through ZIMRA's software path: test-environment validation, sample document approval, then live registration, all without fiscal hardware.
Buyer name, address, TIN, contact details and VAT number captured on the document and transmitted in the FDMS payload, per Public Notices 22 and 30 of 2025.
Fiscal invoices, credit and debit notes carry the QR code that returns valid on the ZIMRA FDMS portal.
Fiscalised records flow into TaRMS's pre-filled VAT schedules, so the return draft matches the ledger instead of fighting it.
ZiG and USD books kept honest with ERPNext's native multi-currency accounting, exchange rates carried per transaction.
How we deliver
From discovery to verified go-live
Discovery and compliance mapping
We map your document flows, branches and item catalogue to ZIMRA's FDMS requirements, and confirm registration status and credentials with the authority.
Sandbox integration
ERPNext is connected to the FDMS test environment. Sales invoices, credit notes and debit notes are generated and validated against the authority's schema before anything touches production.
Resilience engineering
Failed transmissions queue and retry automatically, with a circuit breaker for authority downtime. The pattern is proven in our KRA eTIMS module: zero lost receipts when the tax server is down.
Go-live and verification
Production credentials are registered, the first live documents are verified end to end, and your team is trained on exception handling and the FDMS verification workflow.
Support and rate-change watch
We monitor authority notices and ship configuration updates when rules change, under a support agreement with defined response times.
Frequently asked questions
Is this a shipped module?
No. FDMS integration is delivered as an engineering service on ERPNext through ZIMRA's virtual fiscalisation API, using the architecture of our production Kenyan eTIMS module. Test-platform validation and ZIMRA approval are part of the delivery.
What did the 31 May 2025 deadline change?
Devices must transmit buyer details, including TIN and VAT number where relevant, to FDMS, and TaRMS integration became final under Public Notices 22 and 30 of 2025. Invoices without compliant buyer data and a valid QR code no longer support input tax claims.
How does the dual-currency environment affect fiscalisation?
Fiscal documents carry their transaction currency while the ledger maintains both ZiG and USD positions. ERPNext's native multi-currency accounting keeps statutory reporting and trading currencies reconciled, which spreadsheet-based books consistently fail at.
Scope your FDMS integration
A discovery call covers your document flows, registration status with ZIMRA, and a delivery plan with verification criteria. We reply within one working day.