ZATCA Phase 2: What 'Ready' Means Now That Enforcement Is Live
Wave 24 closed 30 June 2026 and ZATCA's amnesty expired the same day. Here's what a finance team's close actually needs once e-invoicing enforcement is live.
By The Rexfin team
Three and a half years ago, ZATCA’s Phase 2 integration requirement only touched businesses above SAR 3 billion in taxable revenue. Wave 24 dropped that bar to roughly SAR 375,000, with a compliance deadline of 30 June 2026. That date has passed. So has the penalty-waiver program that ran alongside it. If your business crossed a threshold in the last few waves, you are not preparing for enforcement anymore: you are inside it, and the question worth asking has changed from “are we ready” to “is our close defensible under a regime that is already checking.”
That distinction matters because the two questions have different answers. Getting your invoices to clear through FATOORA (the XML formatting, the QR code, the digital signature, the real-time connection) is an e-invoicing integration problem, and ZATCA maintains its own approved list of providers for exactly that. Rexfin is not one of them and doesn’t try to be. What we’re built for is the layer around it: making sure the numbers your close, your tax filings, and your audit trail rest on actually reconcile, so that if a clearance gets rejected or a buyer challenges an input-VAT deduction, you can show, not just claim, where every figure came from.
What full enforcement actually changed
Before the deadline, a rejected invoice or a compliance gap was a warning. Now it’s fines starting at SAR 1,000 and escalating, invoices that don’t clear at all, buyers denying your input-VAT deduction on anything non-compliant, and in the worst case a suspension of your ability to issue invoices. That last one is not a compliance inconvenience: it stops revenue from being recognized. A finance team that treats this as background noise is making a bet it can’t see the size of.
The practical shift: any manual step in your close that assumes “we’ll catch it eventually” now has a live cost attached, dated to the week it happens, not the quarter you notice.
The dual regime that doesn’t expire with any wave
Underneath the e-invoicing deadline sits a second, permanent problem for mixed-ownership companies, common under private equity or foreign joint-venture structures. Every cycle, you’re running two parallel tax-base computations: 2.5% zakat on the Saudi and GCC ownership share, calculated on a net-worth base, and 20% corporate tax on the foreign share, calculated on a profit base. Transfer-pricing rules extended to zakat payers a couple of years ago made getting that split right more, not less, work. Unlike Wave 24, there’s no date this problem goes away.
This is where a reconciled close actually earns its keep. If your zakat computation and your corporate tax computation are being maintained in two disconnected spreadsheets by two different people, the split is only as reliable as whoever last reconciled them by hand. Rexfin ties both bases back to the same underlying ledger figures, so the zakat share and the tax share are two views of one reconciled model rather than two independent guesses that happen to add up. That reconciliation discipline is the same one behind a monthly close walkthrough: the habits that make a close audit-proof don’t change because a new enforcement regime turned on.
What to actually check right now
Three things, in order. First, confirm which wave your revenue band falls into and whether your integration is actually live, not just contracted. Second, if you’re a mixed-ownership entity, check that your zakat and CIT computations trace to the same source ledger rather than being reconciled at quarter-end by memory: that’s the gap that turns into an argument with ZATCA later. Third, make sure the filing and payment dates that follow from your jurisdiction settings are tracked somewhere that updates itself, not a spreadsheet someone inherited from a predecessor. If you’re managing that alongside a UAE entity too, the calendar and the underlying tax logic differ enough that they’re worth preparing for separately.
What this doesn’t fix
Rexfin doesn’t clear your invoices and doesn’t file your zakat return. It doesn’t replace your tax advisor’s judgment on how a transfer-pricing position should be argued. What it removes is the specific failure where your close and your tax filings are built on numbers nobody can trace, which, under live enforcement with real fines attached, is no longer a theoretical risk. If your next zakat and tax season is going to run on the same reconciled base as your e-invoicing exposure, that’s worth mapping out before the next wave, not after. For the full set of season-specific playbooks, see zakat and tax season or the finance team use cases hub. If you want to see how a reconciled KSA close actually traces to source, book a demo.
Part of Finance Team Use Cases: Real Workflows on Verified Numbers