A ZATCA-Aligned Data Foundation for KSA Reporting

ZATCA’s e-invoicing rollout has been tightening for three and a half years, and the trajectory is the whole story. Wave 1, back in January 2023, only applied to businesses above SAR 3 billion in taxable revenue. The most recent wave dropped that threshold to roughly SAR 375,000 (a reduction of something like 99.99 percent), which means the entire VAT-registered mid-market in Saudi Arabia is now inside the mandatory integration regime, connecting invoicing systems directly to ZATCA’s FATOORA platform with real-time clearance, XML formatting, QR codes, and digital signatures.

The deadline for that wave, and the penalty-waiver amnesty program alongside it, has already passed. Enforcement is live: fines, invoice rejection at the clearance layer, denial of input-VAT deduction for the buyer on a non-compliant invoice, and in the worst case suspension of a business’s ability to issue invoices at all. This is not a soft compliance nudge anyone can push to next quarter. For a business that has crossed the threshold, the honest question is no longer “are we ready”: it is “is our close audit-proof under a regime that is already enforcing.”

Why the underlying data model matters, not just the invoicing layer

E-invoicing compliance is one piece. What sits underneath it, and does not expire with any single wave’s deadline, is a data foundation that treats Saudi tax, currency, and filing conventions as defaults rather than settings someone has to configure correctly by hand.

Rexfin’s extraction and reference-data layer is built with Gulf conventions as the starting point: correct handling of SAR alongside AED and the wider region’s currency vocabulary, IFRS-full taxonomy defaults, and the thousands-scale formatting a GCC filing actually uses. That foundation is what makes the rest of the region-specific work (the tax and zakat lens and IFRS-18 statement presentation) possible without a consultant re-mapping the model by hand for every KSA filing that comes in.

The zakat and corporate tax dual regime

Underneath the e-invoicing deadline is a second, standing problem that does not go away once a wave’s compliance date passes: mixed Saudi-GCC and foreign-owned mid-market companies, common under private equity or foreign joint-venture structures, run two parallel tax-base computations every cycle. Zakat at 2.5 percent applies to the Saudi and GCC ownership share on a net-worth base; corporate tax at 20 percent applies to the foreign ownership share on a profit base. Recent extensions of transfer-pricing rules to zakat payers add another layer of complexity to getting that split right.

This is a natural fit for a system built to reconcile two different computations against one set of underlying records rather than treat them as separate spreadsheets maintained by different people. Rexfin’s tax and zakat lens computes the effective rate correctly across both bases and cites every input back to its source line, so when a filing reports both a zakat charge and a corporate tax charge, the split is visible and traceable rather than blended into a single number that obscures which ownership share is paying what.

Deadlines that follow from the data, not a separate spreadsheet

Once your workspace’s jurisdiction is set to KSA, the filing and payment dates that follow from these rules (zakat and corporate tax roughly 120 days after fiscal year end, with native support for the Hijri calendar where a filing depends on it, and the recurring VAT cadence) are tracked automatically in the compliance calendar, rather than living in someone’s separate tracking sheet, disconnected from the numbers they are computed against.

Who actually buys this

Worth being direct here, because the KSA buying pattern is easy to misjudge. Finance and close software in the Saudi mid-market is bought and owned by the in-house CFO or finance function, not by accounting firms reselling it as a compliance service. Audit and advisory firms play an important role as implementers and advisors, but the budget and the ownership sit with the company. If you are a finance leader at a mid-market KSA business who has crossed a ZATCA threshold, or who manages a mixed-ownership structure with both zakat and corporate tax exposure, this is the layer that keeps your close reconciled to both regimes at once.

What this is not

Rexfin is not a tax engine and does not calculate what you owe ZATCA or the zakat authority: it reconciles and cites the figures a filing already reports, carrying the same “verify with your advisor” posture as the rest of the compliance tooling. It is also not a substitute for e-invoicing software; ZATCA maintains its own approved list of integration providers for that specific requirement. What Rexfin does is make sure the numbers behind your KSA close (currency, tax split, filing dates) are built on a foundation that already understands the region, instead of one you bend into shape after the fact.

For the broader set of GCC-specific capabilities, see Arabic-first financial reporting, or explore the rest of the Rexfin product tour.