Finance teams filing VAT or sales-tax returns across more than one country quickly hit the edge of what ERPNext gives out of the box. Native ERPNext tracks tax through the Sales Taxes and Charges and Purchase Taxes and Charges tables and can produce a generic tax report, but it has no concept of a jurisdiction-specific return layout — the numbered boxes of a UK VAT100, a UAE FTA VAT201, an EU-style return, or a country SAF-T file. Teams end up exporting the General Ledger to spreadsheets every period, hand-mapping tax accounts to return boxes, and manually reasoning about reverse-charge, import VAT, and partial exemption. That work is slow, error-prone, and impossible to audit cleanly.

The VAT/Tax Return Filing & Reports Pack is a proper Frappe app (its own module, DocTypes, and hooks.py) that ECOSIRE builds to your jurisdictions. At its core is a configurable mapping layer: a Tax Return Template DocType defines the boxes for a given country and return type, and child-table rules map each box to a set of tax accounts, tax rates, item tax templates, and transaction directions (sale/purchase, standard/reduced/zero/exempt, domestic/import/reverse-charge). A Tax Return transaction DocType then runs against a selected company and period, aggregates the underlying GL Entry and tax-detail rows through that mapping, and produces a box-by-box return you can review, adjust, lock, and export. Reverse-charge and import VAT are handled explicitly — the mapping can post both the output and input legs of a reverse charge to the correct boxes so the net is correct without double counting.

Technically, the pack is built for Frappe/ERPNext v15 and v16. Aggregation runs in whitelisted server-side methods (parameterized queries, never string-built SQL), exposed over the Frappe REST API so returns can be generated or fetched programmatically. hooks.py doc events guard period integrity — once a Tax Return is submitted and the period is locked, controllers block back-dated edits to tax transactions in that window, and any correction flows through a controlled Tax Adjustment Entry that lands in the next open return. Client scripts drive the return workspace UI (recalculate, drill from a box down to the contributing invoices, flag variances). Role profiles and permission rules separate who can prepare a return from who can lock and file it, and scheduler events can pre-stage draft returns and send period-end reminders. Where a jurisdiction needs a machine-readable file, the pack ships SAF-T / tax-audit-file export scaffolding you extend to the exact schema.

Because this is build-to-order, you are not downloading a fixed marketplace app. After a short scoping call we confirm your jurisdictions, return layouts, chart-of-accounts and tax mapping, and any audit-file format, then build and configure the app against your ERPNext instance. Typical delivery is one working week from confirmed scope. You receive the installable source for your version, UAT on a staging copy of your data, a go-live window, and a support period — not a black box.