Arabic-First Financial Reporting, Not a Translated Afterthought

Most finance software built for the Gulf started somewhere else. It shipped for a US or European market, and then someone added a language pack, a currency dropdown, and called it localized. A GCC finance team can usually tell within a few minutes: the effective tax rate line does not know what zakat is, the fiscal calendar assumes January to December, and the statement labels read like they were translated rather than authored for the region.

Rexfin’s approach starts from the region’s actual reporting reality instead of retrofitting it. That shows up in three concrete places: how tax and zakat get analyzed, how the income statement is presented, and how the underlying data model treats currency and reference data as regional defaults rather than optional settings.

A tax and zakat lens that reads the split correctly

Effective tax rate is a standard metric everywhere. In the Gulf, it is frequently a two-part number: zakat charged on the local ownership share, corporate tax on the rest, and getting the split wrong or ignoring one entirely misreads the business. Rexfin’s tax and zakat lens computes effective tax rate as total tax and zakat divided by profit before tax, using deterministic decimal math, and, where a filing reports both zakat and corporate tax as separate lines, breaks out the split rather than collapsing it into one blended figure. Every input in that calculation is cited and drillable, the same provenance drawer mechanics that back every other number in the product.

When a filing shows zero or a negative profit-before-tax year, that year is honestly excluded from the rate calculation and flagged on the card, because a tax charge over a loss is not a rate and including it would misstate the trend. And when zakat is genuinely absent from a filing rather than reported as zero, Rexfin says so explicitly (“absent, not zero”) instead of quietly treating a missing line as a clean number. An advisory rule also flags a year-over-year swing in effective tax rate beyond a meaningful threshold, the same anomaly-detection logic used elsewhere in the product, because a large unexplained swing is exactly the kind of thing a reviewer wants surfaced, not buried in a footnote.

IFRS-18 presentation, GCC-native from the start

Rexfin renders income statements in the IFRS-18 operating, investing, and financing shape with the two mandated subtotals, a requirement that becomes mandatory for periods from 1 January 2027, with 2026 comparatives restated. That statement structure is covered in more depth in IFRS 18 statement presentation; what matters here is that the category recomputation runs against the same cited, extracted line items already in the model, and the presentation ties out exactly against the printed profit figure the filing reports, rather than approximating it.

Currency and reference data built for the Gulf, not adapted to it

Underneath the presentation layer, the extraction engine’s defaults are Gulf-first: AED and IFRS-full taxonomy out of the box, correct handling of the region’s thousands-scale conventions, and vocabulary for Gulf currencies including the three-decimal currencies (Kuwaiti dinar, Omani rial, Bahraini dinar) that break naive two-decimal formatting logic if nobody thought about them. A real GCC filing, in English or Arabic, should extract clean without artifacts left over from a different region’s assumptions baked into the tool.

That data foundation, along with the region-specific compliance rules Rexfin tracks, is covered in more depth in a ZATCA-aligned data foundation, and the filing and tax deadlines that follow from it are tracked in the compliance calendar.

What “Arabic-first” does not mean

It does not mean Rexfin invents region-specific numbers or applies a tax opinion: the tax and zakat lens is explicit that it is not a tax engine and never computes what you should owe; it reports and reconciles what a filing already states. It also does not mean every GCC jurisdiction is equally covered on day one: coverage is honest about where it stands, and a jurisdiction without a calibrated rule set says so rather than showing a plausible-looking number.

What it does mean is that a GCC reviewer opening a Rexfin statement sees the currency, the tax structure, and the statement shape they actually expect, computed from the same cited, reconciled figures the rest of the product relies on. For the broader picture of how those figures get extracted, verified, and traced back to source, see the Rexfin product tour.