Zakat and Tax Season: Keeping Two Tax Bases From Drifting Apart

If your company in Saudi Arabia has both Saudi or GCC ownership and foreign ownership (the common structure under a private equity deal or a foreign joint venture), tax season isn’t one filing. It’s two, computed on two entirely different bases, due at the same time, and expected to add up to a story that holds together if anyone asks. Zakat is charged at 2.5% on a net-worth base attributable to the Saudi and GCC ownership share. Corporate income tax is charged at 20% on a profit base attributable to the foreign share. Getting that split wrong, or getting each base right individually but disagreeing on the ownership percentage used to compute them, is the actual risk every season carries.

This isn’t a one-time compliance event like an e-invoicing deadline. It’s a standing, recurring obligation that shows up every filing cycle, and it’s arguably the more durable problem for finance teams operating in KSA. A separate transfer-pricing extension from 2024 added a disclosure form and TP affidavit requirement alongside the zakat return, which means the ownership split and the pricing between related entities both need to be defensible, not just internally consistent.

Where the two bases quietly diverge

The failure mode isn’t usually a calculation error inside either base. It’s that the zakat computation and the CIT computation get maintained as two separate spreadsheets, often by two different people, each pulling from the ledger at a slightly different point in time or applying a slightly different version of the ownership percentage. Individually, both numbers look reasonable. Together, they imply a company that’s somehow worth two different things depending on which return you’re reading, and that’s the exact inconsistency a tax authority or an auditor is positioned to notice.

One reconciled base, two views

The fix isn’t a smarter spreadsheet template. It’s making sure both bases are two views of the same underlying model instead of two independent computations that happen to be reconciled at quarter-end by memory. The net-worth figure zakat is charged on and the profit figure CIT is charged on should both trace back to the same source ledger, using the same ownership percentage pulled from the same place, so a change to one doesn’t quietly leave the other out of date. If a tax authority questions either figure, the answer should be a trace to the underlying entry, not a promise to check with accounting and get back to them.

That same reconciliation discipline is what makes a monthly close trustworthy in the first place: tax season doesn’t introduce a new requirement so much as it raises the stakes on one you already have. If your close is already producing numbers that tie to source every month, the zakat and CIT split is a calculation layered on top of that base, not a separate reconciliation exercise built from scratch each season.

What this doesn’t cover

Worth being direct about scope here. This isn’t an e-invoicing compliance tool: clearing invoices through FATOORA is a separate integration problem with its own approved vendor list, and it’s covered on its own terms in ZATCA Phase 2 readiness. It also doesn’t replace your tax advisor’s judgment on how a transfer-pricing position should be argued, or decide what counts as a defensible related-party price. What a reconciled base gets you is the part underneath that judgment: numbers that agree with each other and trace to source, so the advisor’s argument rests on something solid instead of a spreadsheet nobody can fully explain.

If your close spans multiple entities or a fiscal year-end that doesn’t line up neatly with the filing calendar, the discipline in year-end close is worth reading alongside this one: the same reconciliation habits carry the tax season workload, not a separate process built just for it. And if you’re running a UAE entity in parallel, the calendar and the underlying rules differ enough to warrant handling separately.

Zakat and tax season will keep recurring every cycle regardless of what tooling you use. What changes is whether the two bases you file agree with each other on the day someone asks, or only agree because nobody has checked closely yet. For more on how finance teams keep recurring obligations like this reconciled year-round, see the finance team use cases hub.