| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) • Point of Sale (point_of_sale) • Inventory (stock) |
| Community Apps Dependencies | Show |
| Lines of code | 4003 |
| Technical Name |
l10n_zw_fdms_pos |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) • Point of Sale (point_of_sale) • Inventory (stock) |
| Community Apps Dependencies | Show |
| Lines of code | 4003 |
| Technical Name |
l10n_zw_fdms_pos |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Zimbabwe FDMS POS
ZIMRA Fiscal Device Gateway fiscalisation of Point of Sale orders — signed receipts, fiscal footer & verification QR
Fiscalise Odoo Point of Sale orders with the Zimbabwe Revenue Authority FDMS Fiscalisation Data Management System. Each paid order and refund is mapped to the ZIMRA submitReceipt document, signed by your registered virtual fiscal device, and the returned fiscal numbers, server signature and verification QR are stored on the order — ready for the printed receipt footer.
POS order fiscalisation
Every order is mapped to the FDMS receipt with the ZIMRA A/B/C tax codes — 15% standard, zero-rated and exempt — per-line receipt lines, the tax breakdown in integer cents and a device-signed SHA-256 hash chained to the previous receipt.
Refund handling
POS refunds are submitted as credit notes referencing the original fiscalised receipt, with the reversed magnitudes carried to the gateway exactly as ZIMRA expects.
Payment-method mapping
Each POS tender is mapped to the FDMS money-type code — cash, card, mobile wallet (EcoCash, OneMoney, InnBucks) and bank transfer — so the receipt records the real tender split.
Fiscal footer + verification QR
The device id, fiscal day, receipt and global numbers, device and server signatures and the ZIMRA verification URL are formatted into a printable footer block, with the verification QR rendered to a PNG for the receipt.
Mandatory buyer detail
When a registered (B2B) customer is attached, the buyer's registered name and BPN/TIN are transmitted, enforcing the buyer-detail rule in force since 31 May 2025 so the buyer can claim input tax. Walk-in B2C slips are exempt.
Auto-fiscalise at payment or session close
Choose to fiscalise each order as it is paid, drain the session's orders when it closes, or leave it manual — per company and per shop. An optional batch cron retries anything left pending.
Per-device counters & fiscal day
Reuses the FDMS fiscalisation connector's device receipt counter, global number and fiscal-day management, with the previous-receipt hash chaining the device signatures across the day.
Real BPN validation
The ZIMRA Business Partner Number mod-11 check digit and the 9-digit VAT structural check run on the company and registered customers, with a Zimbabwe POS rule set layered on the engine's EN 16931-style core.
Bring-your-own-key
Your device certificate and private key live on the device record (system-restricted), never in the module. They are transmitted only to the ZIMRA endpoint you configure — nowhere else.
Compatible with Odoo 18 and Odoo 19.
Disclosure
This module transmits POS order data only to the ZIMRA FDMS Fiscal Device Gateway endpoint you configure. Your device certificate and private key are bring-your-own-key, stored solely on your own database, and are never sent anywhere else. It builds on the Zimbabwe FDMS Invoice connector and the shared e-Invoice Core Engine.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module