GCC finance teams running a single ERPNext instance across UAE, KSA, Bahrain, Oman and Qatar hit the same wall: ERPNext ships a generic tax engine and a basic "VAT Audit Report", but it has no concept of a FTA VAT 201 return, a ZATCA-shaped audit file, an Oman VAT return schema, or the reverse-charge and designated-zone rules that differ by country. Teams end up hand-copying figures from the general ledger into spreadsheets each period, re-keying the same numbers into five different tax-authority portals, and hoping nobody applied the wrong tax template to an import or an intra-GCC supply. That manual gap is exactly where filing errors, missed reverse-charge entries and audit exposure come from.

ECOSIRE builds the GCC VAT Compliance Suite as a proper Frappe app (its own module, hooks.py, fixtures and CI-friendly source) layered on top of your existing ERPNext, not a fork of it. At its core is a Country VAT Profile DocType that pins the return format, box mapping, currency and filing frequency per jurisdiction, plus a VAT Return submittable DocType whose fields mirror each authority's actual return (for example the UAE VAT 201 boxes or the KSA return schedule). A Tax Treatment Rule DocType maps ERPNext Sales Taxes and Charges Template / Item Tax Template combinations to the correct box, tax category and reverse-charge flag, so standard-rated, zero-rated, exempt, out-of-scope, import and designated-zone lines land in the right place automatically.

Technically, the suite hooks into the transaction lifecycle rather than bolting on a report. doc_events in hooks.py fire validate and on_submit server-side handlers on Sales Invoice, Purchase Invoice and Payment Entry to stamp each line with its resolved tax treatment and to raise the RCM self-assessment entry where the rule requires it. A whitelisted method (generate_return) aggregates GL and tax rows for the period into the country's return DocType, and a second whitelisted method exports the FAF / audit file in the authority's required layout (CSV or XML) to a File attachment. All of this is reachable through the Frappe REST API for downstream automation, and a nightly scheduler_event runs the VAT reconciliation that ties output/input tax control accounts back to filed returns and flags variances. Access is governed by a dedicated "VAT Compliance Manager" role profile and per-company permissions so a multi-entity group keeps each jurisdiction's data segregated. Client Scripts add the in-form helpers (country selector, box preview, one-click return generation) without patching core ERPNext.

Because every organisation's chart of accounts, entity structure and jurisdiction mix is different, this is a build-to-order engagement, not an off-the-shelf download. It starts with a short scoping call to confirm which of the five countries you file in, your ERPNext version (v15 or v16) and your tax-template setup. ECOSIRE then configures the country profiles and treatment rules to your data, builds against your requirements, and delivers on a staging site for UAT before go-live. Typical delivery is one working week from confirmed scope, and you receive the installable source, a git repository handover, documentation and a post-go-live support window.