E-invoicing: is your entity ready for integration?

Since the launch of the e-invoicing programme “Fatoora,” issuing an invoice in the Kingdom has moved from an internal accounting step to a technical and regulatory obligation monitored by ZATCA in near real time. As phase-two integration waves expand to smaller entities year after year, the question is no longer “Will I be required?” but “When — and will I be ready?”

The two phases in brief

Phase one (generation) required all VAT-registered entities to stop handwritten and manual invoices and issue electronic invoices through a compliant system with mandatory fields and a QR code on simplified invoices. That phase has applied to everyone since the end of 2021.

Phase two (integration) is the real shift: connecting the entity’s invoicing system directly to ZATCA’s Fatoora platform so that tax invoices are cleared with the Authority before sharing with the customer (clearance model), and simplified invoices are reported within 24 hours of issue. That requires a cryptographic stamp, a digital certificate, a unique invoice identifier (UUID), and a sequential counter that does not allow deletion or alteration.

How do you know your turn is near?

The Authority does not onboard everyone at once. It rolls out waves based on taxable revenue in a reference year and notifies targeted entities at least six months before the integration deadline. With each new wave the revenue threshold falls, so mid-sized then smaller entities enter scope in turn. The practical rule we give clients: do not wait for the notice. If your revenue is approaching the thresholds of the latest announced waves, start readiness now — six months pass faster than you expect when systems need changing.

Five readiness steps

1. Assess your current system. Is your accounting or POS solution on the list of compliant solutions? If it is home-built or outdated, you will need development or an accredited technical intermediary.
2. Clean your master data. What fails integration most often is not technology but data: incomplete customer VAT numbers, incomplete addresses, items without correct tax classification. Fix these before any technical step.
3. Request the cryptographic stamp certificate and complete e-invoicing unit setup on the Fatoora portal in the sandbox first.
4. Test in the sandbox across all document types: tax invoice, simplified, credit note, debit note. Many entities test only the standard invoice and then hit rejections on notes.
5. Train your team on rejection scenarios. What does the accountant do when a platform rejects an invoice? Who follows up? Within how many hours? Without that internal procedure, a simple technical error becomes a violation.

The most common mistakes

From entities that come to us after a failed go-live: starting only a month before the deadline, relying on a vendor’s promises without real testing, leaving branches and extra POS devices out of scope, and assuming that a penalty waiver means a waiver of the obligation itself. Violations here are not symbolic — non-compliance fines start in the thousands of riyals per breach and escalate with repetition.

Bottom line

E-invoicing is not an IT project you hand to the tech team and close. It is an ongoing obligation that touches accounting, sales, and systems together. Entities that engage early turn it from a compliance burden into a chance to clean financial data and automate the revenue cycle.

This article is for general awareness and does not replace professional advice for your entity’s position.

Have you received an integration notice, or are your revenues nearing the mandate threshold? Our zakat and tax team provides a full readiness assessment. Contact us.

Contact us→