| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 2770 |
| Technical Name |
fiscal_qr_invoice_engine |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 2770 |
| Technical Name |
fiscal_qr_invoice_engine |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Global QR Invoice
One fiscal-QR engine, every regime — ZATCA, Veri*factu, ATCUD, EU URL and JSON on your invoice PDF
A reusable engine that computes the fiscal QR code tax authorities require on invoices and embeds it in the printed invoice. Pick the regime per company or per invoice; the engine encodes the exact payload — TLV, verification URL or JSON — renders it and drops it on the PDF. Computation is fully local: nothing is transmitted.
Pluggable per-country regimes
Saudi Arabia ZATCA (Phase 1 & Phase 2 TLV), Spain Veri*factu, Portugal ATCUD, a configurable EU verification URL and a generic JSON QR ship built-in. Each regime binds a code to a real in-code encoder, and connectors can register more without touching the engine.
Three encoders, real algorithms
Base64 TLV (single-byte length, ordered tags, round-trip decodable), stable / authority-ordered URL query strings, and compact JSON. Amounts are quantised HALF_UP so the QR string and any signature match byte-for-byte.
Tamper-evident hash chain
Certified-billing regimes (Spain Veri*factu, Portugal ATCUD) carry the previous record's SHA-256 fingerprint forward into each new invoice, forming the immutable chain those rules require. The running fingerprint is kept on the company.
QR on the invoice PDF
The QR is rendered to a PNG (and a crisp print SVG) with the regime's recommended error-correction level, stored on the move and added to the standard invoice report alongside the regime name and chain reference.
Validation before you print
Each regime layers its pre-conditions (seller VAT, totals, ISO dates, ATCUD) on the EN 16931-style core rules of the e-Invoice Core Engine. Missing data is surfaced with precise codes before the QR is built.
BYOK & configurable
Verification-portal URLs and certified-software numbers are editable defaults stored only on your database. A setup wizard, a company configuration block and an optional batch-build cron get you running fast.
Built on the e-Invoice Core Engine
Reuses the shared document model and validation framework — no duplicated plumbing. Odoo-free service layer with a plain-python test suite for the encoders, regimes and hash chain.
Compatible with Odoo 18 and Odoo 19.
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