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.

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 one working week from confirmed scope, and you receive the full source code and git repository so you are never locked in.