| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2695 |
| Technical Name |
l10n_bh_einvoice_prebuild |
| 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 | 2695 |
| Technical Name |
l10n_bh_einvoice_prebuild |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Bahrain NBR e-Invoice
National Bureau for Revenue e-invoicing readiness pack for Odoo — VAT-compliant UBL 2.1 invoice, GCC TLV QR & future-mandate scaffold
Get ready for Bahrain NBR e-invoicing today. This pack turns your Odoo customer invoices and credit notes into a VAT-compliant UBL 2.1 document with a GCC-style TLV QR, validates them against Bahrain VAT business rules, and ships a transport scaffold that is one configuration change away from live clearance on go-live.
Honest scope
Bahrain levies VAT (10% standard since 1 January 2022, plus 0% zero-rated and exempt classes) and the NBR is building a nation-wide B2B e-invoicing system on the GCC's UBL/Peppol-aligned direction. The technical specification and go-live date are not finalised yet. This is a readiness / pre-build pack: it prepares and validates the e-invoice document and QR now, and its clearance transport is honestly inert until NBR publishes the endpoint. It does not submit to a live government gateway, because none is published.
UBL 2.1 invoice & credit note
VAT-compliant UBL 2.1 documents with S/Z/E/O tax categories, per-line tax classification, tax subtotals, legal monetary totals and credit-note referencing, carrying the NBR readiness CustomizationID.
GCC-style TLV QR
The ZATCA-pioneered tag/length/value QR — seller name, VAT number, timestamp, total and VAT total — base64 encoded and rendered to PNG, with an optional extended variant carrying the buyer VAT and a document reference.
Real VAT & CR validation
A 15-digit NBR VAT account number validator (with an advisory Luhn check digit and head/branch registrant detection) and a Sijilat Commercial Registration validator run on the company and partners.
Bahrain VAT business rules
A Bahrain rule set layered on an EN 16931-style core: seller and buyer VAT, BHD currency, valid tax categories, Commercial Registration, BH country and credit-note referencing — with a clear validation report.
Future-mandate scaffold
A clearance transport client subclassing the engine REST transport (retry/backoff, logging, sandbox/production switching), kept honestly disabled behind an explicit readiness state until NBR publishes the endpoint — then one config change goes live.
Onboarding & automation
A guided onboarding wizard, a connection configuration model and an optional batch-preparation cron pre-build documents ahead of go-live. All multi-company aware, built on the shared e-Invoice Core Engine.
Compatibility & privacy
Compatible with Odoo 18 and Odoo 19. Bring-your-own-key: your VAT/CR identifiers and any future NBR access token are stored solely on your own database. No invoice data is transmitted to any government gateway, because none is published yet.
Screenshots
Bahrain E Invoice Prepared V
Generated Bahrain Ubl E Invo
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