Bahrain's National Bureau for Revenue expects a tax invoice to carry a defined set of fields — supplier and customer VAT account numbers, the invoice date and supply date, a per-line breakdown at the applicable rate, the VAT amount stated in Bahraini Dinar, and Arabic content where the customer requires it. It expects VAT returns to be reconcilable back to the ledger, and it expects the records behind both to survive an audit years later. Dynamics 365 Business Central gives you VAT Posting Setup, VAT Business Posting Group, VAT Product Posting Group, the VAT Entry table and the standard VAT Statement — a genuinely solid foundation, but a generic one. Out of the box there is no Bahrain rate scaffold, no bilingual invoice layout, no BHD-specific rounding discipline on the tax line, no mapping from your statement lines to the boxes on the NBR return, and no correction workflow for the day a customer rejects an invoice. Finance teams close that gap in Excel, and the spreadsheet becomes the thing an auditor actually asks about.

What ECOSIRE builds is an AL extension — delivered as a per-tenant extension for Business Central online, or as an on-premises extension where you host it — that moves that work back into the system. We ship a Bahrain VAT Setup page holding the rate scaffold (standard, zero-rated, exempt, out-of-scope) and the registration details, wired to your existing posting groups rather than replacing them. Table extensions on Sales Header, Sales Invoice Header, Purch. Inv. Header and VAT Entry carry the extra compliance fields — supply date, VAT account number, place of supply, reverse-charge indicator, correction reference — stamped at posting time by a codeunit subscribing to the standard OnAfterPostSalesDoc and OnAfterPostPurchaseDoc publishers. Nothing is bolted on after the fact, which is what makes the archive trustworthy.

One posting event produces both outputs. A Word or RDLC report layout renders the human-readable tax invoice, bilingual Arabic/English where you need it, with the VAT summary block and the BHD amounts rounded to three decimals per Bahraini convention. The same posted data serialises to a machine format — XML or JSON to the schema your filing agent, e-invoicing portal or group consolidation tool expects — from a dedicated codeunit, so the two can never drift apart. A Bahrain VAT Return page groups VAT Entry records by period and maps them to your return boxes, with drill-down from any box to the underlying entries and then to the source document; that drill-down is the whole point, because it is the path an auditor walks. Where a submission is rejected, a correction workflow marks the original, creates the linked corrective document and keeps both in the archive with the rejection reason attached, rather than letting someone delete and re-post. Registered permission sets keep the setup pages away from ordinary users, and a job queue entry can run the period validation, the archive export or an outbound submission on a schedule. API pages (REST API v2.0 / OData v4) expose the return summary and the invoice archive so Power BI, a Power Automate flow or a Dataverse-connected app can read them without anyone touching the database.

This is build-to-order, and we would rather say so plainly than imply a one-click download. There is no AppSource listing behind this page — you request a quotation, we run a scoping call of about thirty minutes to look at your chart of accounts, posting group structure, invoice layout, Arabic requirement and filing route, and we quote against that. From confirmed scope, typical delivery is one working week: build against your Business Central release wave, install into your sandbox, run UAT with your finance team on real documents, then a scheduled production install with a rollback plan.

You get the AL source, not a black box. The repository is handed over on completion, the extension is documented at object level, and your finance users get a written guide plus a live training session. A post-go-live support window covers defects and the questions that only appear once real month-end traffic hits it. If NBR guidance changes, or your business adds a scenario the first build did not anticipate, that is a scoped change on a codebase you already own.