Since the UAE introduced the 9% federal corporate tax, finance teams running ERPNext have been stitching together spreadsheets to get from accounting profit to taxable income. ERPNext core gives you a clean general ledger and financial statements, but it has no concept of a corporate-tax computation: no schedule to reconcile book profit to taxable income, no handling of the AED 375,000 zero-rate threshold, no free-zone qualifying vs non-qualifying income split, no provision entry, and nothing that maps to the Federal Tax Authority (FTA) return. The last mile — adjustments, exempt income, disallowed expenses, and the actual tax number that lands in your books — ends up outside the system, which is exactly where audit risk lives.

ECOSIRE builds a proper Frappe app (for example ecosire_uae_ct) that adds this layer natively to your ERPNext instance. We model the computation as first-class DocTypes: a Corporate Tax Computation document per tax period pulls net profit from your existing GL, then applies configurable adjustment lines (add-backs for disallowed expenses, deductions for exempt income and participation exemption, prior-year losses) to arrive at taxable income and the 9% liability above the AED 375,000 threshold. A Free Zone Qualifying Income DocType lets qualifying free-zone persons classify revenue streams and track the de-minimis test so qualifying income stays at 0% while non-qualifying income is taxed correctly. Supporting master data — tax periods, adjustment categories, rate bands — is held in configuration DocTypes so rules can change without a code change.

Technically, the app is wired the way any well-built Frappe app should be. Computation logic runs in server scripts and Python methods invoked from hooks.py document events (validate, on_submit, on_cancel), so numbers are recomputed and locked on submission. On submit, the app posts the tax provision as a Journal Entry to the accounts you nominate (tax expense vs tax payable), keeping ERPNext's ledger the single source of truth and fully reversible on cancel. Whitelisted methods exposed over the Frappe REST API let your other systems fetch the current liability or trigger a recompute; client scripts drive live in-form totals and validation so preparers see the taxable-income bridge update as they work. Role profiles and DocType permissions separate who can prepare a computation from who can submit and post it, and scheduler events can generate draft computations at period-end and flag filing deadlines. FTA-aligned reports (the taxable-income reconciliation, free-zone split, and a return-ready summary) are delivered as Query/Script Reports with print formats you can export for filing and keep for audit.

Because this is build-to-order, nothing is generic. We start with a short scoping call to confirm your entity structure (single company or multi-company/group), free-zone status, chart-of-accounts mapping, and which adjustments apply to you, then build against your actual ERPNext configuration on Frappe/ERPNext v15 or v16. You get the app installed on a staging site first for UAT, a rollback plan, and the full Git repository handed over so the code is yours. Typical delivery is 2 to 4 weeks from confirmed scope, followed by a post-go-live support window.