A build-to-order ERPNext app that makes your instance compliant with Bahrain NBR VAT rules — bilingual Arabic/English tax invoices, VAT return reporting, and e-invoicing-ready XML scaffolding. ECOSIRE scopes, builds, installs, and supports it for you. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $399.00 USD; request a quote for a scoped proposal.

A build-to-order ERPNext app that makes your instance compliant with Bahrain NBR VAT rules — bilingual Arabic/English tax invoices, VAT return reporting, and e-invoicing-ready XML scaffolding. ECOSIRE scopes, builds, installs, and supports it for you.
لا حاجة للدفع الآن. يؤدي هذا إلى إرسال طلب عرض سعر إلى فريقنا — وسنتواصل معك عبر البريد الإلكتروني بالأسعار والخطوات التالية.
Bahraini SMEs running ERPNext hit the same wall: the NBR expects a 10% VAT regime with strict tax-invoice content rules, bilingual Arabic/English presentation, and — as Bahrain moves toward mandated e-invoicing — structured invoice data that native ERPNext simply does not produce. Out of the box, ERPNext gives you generic tax templates and a standard print format, but nothing that maps cleanly to NBR return boxes, no Arabic-first invoice layout with the mandatory fields, and no XML export scaffold to plug into a clearance or reporting flow. Accountants end up reconciling in spreadsheets and hand-editing PDFs, which does not scale and does not survive an audit.
Namespaced Frappe app with its own module — Bahrain compliance layered on without patching ERPNext core
10% VAT Sales and Purchase Taxes and Charges Templates, plus zero-rated, exempt, and reverse-charge variants
NBR-aligned Item Tax Templates and party Tax Categories for correct rate resolution on every line
Bilingual Arabic/English tax invoice print format with all NBR-mandated fields and per-line VAT breakdown
hooks.py validate and on_submit doc events enforcing VAT number format, tax-category consistency, and rounding at document time
Server scripts and client scripts that block non-compliant invoices before submission rather than at filing time
ECOSIRE builds a proper Frappe application — a namespaced app with its own module, not a pile of loose customizations — that layers Bahrain compliance onto your existing ERPNext without forking core. We configure the 10% VAT Sales Taxes and Charges Template and Purchase Taxes and Charges Template (plus zero-rated and exempt variants), add the item and party tax categories NBR expects, and wire a bilingual tax-invoice print format that renders Arabic and English side by side with the legally required fields (supplier VAT account number, tax point date, per-line VAT breakdown, and totals in words). Custom fields are delivered as fixtures so they migrate cleanly across environments.
Under the hood we use hooks.py document events (validate, on_submit) and server scripts to enforce VAT-number format, tax-category consistency, and rounding rules at document time — so bad invoices are caught before submission rather than at return-filing time. A dedicated report DocType and query/script report produce the NBR VAT return summary, mapping your posted transactions to the standard return boxes (standard-rated sales and output VAT, zero-rated, exempt, imports/reverse charge, input VAT recoverable) with drill-down to source vouchers. For e-invoicing readiness we generate structured XML per invoice via a whitelisted method and a scheduler event, giving you a validated, mappable payload you can adapt to the NBR clearance schema when the mandate finalizes — exposed over the Frappe REST API and guarded by role permissions and a dedicated role profile. Multi-currency BHD handling is respected end to end: foreign-currency invoices carry the BHD-equivalent tax amounts NBR reporting requires.
Because this is build-to-order, nothing ships until we agree on scope. It starts with a short scoping call to confirm your NBR registration profile, invoice types, chart-of-accounts mapping, and Frappe/ERPNext version (we support v15 and v16). We then build against a staging copy of your data, run UAT with your accountant, and only cut over to production with a rollback plan in hand. Typical delivery is 2-4 weeks from confirmed scope, and you receive the full source code and git repository so you are never locked in.
Manages day-to-day NBR VAT obligations and needs compliant bilingual tax invoices and a VAT return that reconciles to ERPNext without spreadsheet gymnastics.
Owns the periodic NBR filing and audit readiness, and wants output/input VAT to map to return boxes with drill-down to source vouchers instead of manual summaries.
Runs the bench instance and wants Bahrain compliance delivered as a clean, versioned Frappe app with fixtures and docs rather than untracked in-place customizations.
Anticipates Bahrain's move to mandated e-invoicing and wants structured XML scaffolding in place now so the eventual mandate is a configuration step, not a rebuild.
قم بشراء الترخيص من موقع ecosire.com وقم بتنزيل تطبيق Bahrain VAT E-Invoicing & Compliance ZIP من لوحة تحكم حسابك.
قم باستخراج ملف ZIP إلى مجلد تطبيقات مقعدك، أو قم بتشغيل "bench get-app" مع المسار إلى التطبيق المستخرج.
قم بتشغيل `bench --site SITE_NAME install-app APP_NAME` متبوعًا بـ`bench migrate` لتثبيت Bahrain VAT E-Invoicing & Compliance وتطبيق مخططه.
افتح إعدادات ترخيص ECOSIRE على موقعك وقم بتنشيط مفتاح الترخيص الخاص بك. يتطلب تطبيقي ecosire_connect وecosire_license_client المجانيين.
| المعيار | ECOSIRE | بناء مخصص | منافس | أودو الأصلي |
|---|---|---|---|---|
| Bahrain NBR VAT fit | Built to your NBR profile and return boxes | Depends entirely on your dev's tax knowledge | Generic GCC assumptions, rarely Bahrain-specific | |
| Bilingual Arabic/English invoice | Arabic-first print format with mandated fields | Hand-built, often incomplete | English-centric, Arabic bolted on | |
| VAT return reporting | Report DocType mapped to NBR boxes with drill-down | Usually spreadsheet reconciliation | Basic tax summary, not return-shaped | |
| E-invoicing XML readiness | Whitelisted method + scheduler, mappable to clearance schema | Rarely scoped in | Seldom offered for Bahrain | |
| Multi-currency BHD handling | BHD-equivalent tax on foreign invoices for reporting | Manual, error-prone | Inconsistent | |
| Upgrade safety | Namespaced app + fixtures, core stays upgradeable | In-place edits risk breaking upgrades | Varies by vendor quality | |
| Ownership & lock-in | Full git repo handover, no lock-in | You own it, but you also maintain it alone | Vendor-controlled, licensed | |
| Delivery & support | 2-4 wks, UAT + rollback + support window | Open-ended timeline and cost | Instant install, self-serve support |
No. This is build-to-order. ECOSIRE builds the app against your specific ERPNext instance, chart of accounts, and NBR registration profile, then installs and supports it. There is no instant download — the value is in a compliant, tested fit to your data.
Typical delivery is 2-4 weeks from confirmed scope. The clock starts after the scoping call when we have agreed the invoice types, account mapping, and your Frappe/ERPNext version. Simpler single-entity setups land near the two-week mark; multi-currency or multi-branch scope trends toward four.
We build for Frappe/ERPNext v15 and v16. We confirm your exact version on the scoping call and target it specifically, since DocType and print-format APIs differ between major versions. The app is delivered as a namespaced Frappe app installed via bench.
It provides validated, structured XML scaffolding that is mappable to the NBR clearance schema. Bahrain's e-invoicing mandate is still finalizing, so we build the generation pipeline and field mapping now; once the official schema is published, adapting the payload is a configuration step rather than a rebuild.
Every engagement includes a post-go-live support window for defect fixes and configuration questions. Because you receive the full git repository, you own the code and can maintain it yourself or contract ECOSIRE for ongoing updates — for example, when NBR rules change or when you upgrade ERPNext major versions.
No. It ships as a separate namespaced Frappe app that adds custom fields (via fixtures), print formats, DocTypes, hooks, and server scripts. Core ERPNext stays upgradeable, and everything the app adds is tracked in its own git repository.
Yes. Multi-currency is handled end to end. Foreign-currency invoices post correctly and carry the BHD-equivalent VAT amounts that NBR reporting requires, so your VAT return reconciles regardless of the transaction currency.
A build-to-order ERPNext app that makes your instance compliant with Bahrain NBR VAT rules — bilingual Arabic/English tax invoices, VAT return reporting, and e-invoicing-ready XML scaffolding. ECOSIRE scopes, builds, installs, and supports it for you.