| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2821 |
| Technical Name |
l10n_tz_vfd_einvoice |
| 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) |
| Community Apps Dependencies | Show |
| Lines of code | 2821 |
| Technical Name |
l10n_tz_vfd_einvoice |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Tanzania VFD e-Invoicing for Odoo
TRA Virtual Fiscal Device fiscal receipts — generate, validate and fiscalize through the VFMS, directly from Odoo.
What It Does
This module makes Odoo ready for the Tanzania Revenue Authority (TRA) Virtual Fiscal Device (VFD) regime. For every customer invoice and credit note it builds the fiscal-receipt (RCT) document, validates it against the TRA VFD business rules, posts it to the Virtual Fiscal Management System (VFMS), and stores the returned receipt verification code together with a QR pointing to the public TRA verification portal so any buyer can confirm the receipt was reported.
It is built on the shared e-Invoice Core Engine, reusing its canonical document builder, validation framework, QR primitives and BYOK REST transport instead of duplicating them.
Key Features
TRA VFD Fiscal Receipt (RCT)
Deterministic fiscal-document generation with device counters (global counter, daily counter, Z-report number, device serial), TRA fiscal tax codes (A 18% standard, B special, C zero, D exempt, E non-VAT), supplier TIN/VRN and customer identifier type.
VFMS Submission
Post receipts to the TRA VFMS through a resilient REST client with retry and backoff, sandbox/production endpoints pre-filled with the documented TRA hosts (always editable), and full request/response logging.
Receipt Verification Code & QR
Each fiscalized receipt carries the TRA verification code and a scannable verify.tra.go.tz QR image, ready for the printed customer copy.
TIN & VRN Validation
9-digit TRA Taxpayer Identification Number validation (with an advisory mod-11 check) and VAT Registration Number format validation on the company and partners.
Pre-Submission Validation
A TRA VFD rule set layered on the engine validation framework checks mandatory identifiers, device counters, totals coherence and tax codes before anything leaves Odoo.
Onboarding Wizard & Status
A guided setup wizard captures the company TIN/VRN and VFMS credentials in one step; each invoice shows a live VFD status (To Send / Sent / Fiscalized / Rejected) with Generate, Fiscalize and Check Status buttons.
Requirements
- Odoo 18.0 or 19.0 (Community or Enterprise).
- The e-Invoice Core Engine module (installed as a dependency).
- A registered virtual fiscal device and credentials from the TRA VFMS.
- Python libraries: lxml, qrcode, requests, cryptography (standard with most Odoo deployments).
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