ZATCA Phase 2 e-invoicing, in Odoo and in ERPNext

No, neither is. Odoo ships a Saudi fiscal localisation and ERPNext has community-maintained ZATCA apps, but in both cases the installed system still has to be configured for your invoice types, taxes and item data, onboarded unit by unit through the Fatoora portal, and passed through ZATCA's compliance checks. The product gives you a foundation; the implementation gives you compliance.

No. ZATCA publishes a solution providers directory, but states on that page that the list is guiding and non-binding, that inclusion "is not considered as an approval by ZATCA of the e-solutions provided", and that ZATCA bears no liability for publishing it. Vendors marketing themselves as "ZATCA approved" are describing a listing, not an accreditation. Compliance is assessed against the taxpayer and the invoices, not against a product brand.

By your revenue subject to VAT in the years ZATCA names for each wave. Once your revenue in any of those years exceeds a wave's threshold, you fall into that wave. ZATCA also states that it notifies targeted taxpayers directly at least six months before their integration date, so a notification is the definitive answer — but the threshold table lets you see it coming before the letter arrives.

A standard tax invoice is the B2B and B2G document, and in Phase 2 it must be cleared by ZATCA before it is handed to the buyer. A simplified tax invoice is the B2C document issued at the point of sale; it is given to the customer immediately and reported to ZATCA afterwards within the window the regulation sets. The two follow different technical paths, which is why a retail business has more integration work than a wholesaler of the same size.

The compliant electronic issuing system, the mandated invoice fields and the QR code carry over. What does not is the integration itself: the cryptographic stamping, the certificate issued per invoice-generation unit, the hash chain, and the clearance or reporting call to Fatoora. In practice, Phase 1 got your data and your print formats into shape; Phase 2 is a genuine technical project on top of that.

It is enough if your ERP is already live and your master data is clean. It is not much if you are also selecting and implementing the ERP in the same window, because the compliance work sits at the end of a project whose earlier phases tend to overrun. If you expect to be in an upcoming wave, the useful move is to start before the notification rather than after it.

Yes. Onboarding is done per invoice-generation unit, so each terminal or branch system that issues documents is onboarded and tested in its own right. A company with one ERP and forty tills has forty-one things to onboard, not one. This is the single most common reason a retail ZATCA project takes longer than the estimate.

ZATCA publishes a violations guide, and the structure matters more than the amounts: general violations start with a notice and a correction window — 30 days for the integration and issuing violations, 60 days for things like a missing QR code or non-compliant archiving — and the fines escalate only on repetition. Recurrence resets after twelve months without a repeat. So a first miss that you correct promptly is a different situation from a sustained one. Read the current guide rather than the figures circulating in blog posts, several of which are from a superseded 2022 edition.

No, and neither can anyone else. There is no certificate an implementer can issue. What we can do is configure the system, onboard your units, pass ZATCA's compliance checks with you and document what was done. BDC implements both Odoo and ERPNext, is an official partner of neither, and takes commission from neither, so the recommendation on which system to use is not a licence sale in disguise.