An accepted invoice is not a paid invoice.

02Treat structured invoice exchange, commercial approval and payment as distinct states.

03A technically accepted invoice may still lack a purchase-order match, evidence of delivery or payment authorisation.

04Build one traceable workflow around those states, with a separate jurisdiction configuration.

05This is general operational research, not legal or tax advice.

06The two country timelines have separate labels and sit beside a shared operational checklist.

07Do not describe a single MENA deadline or assume that a Saudi-compliant invoice is automatically UAE-compliant.

08The revenue concepts, affected entities and integration mechanisms differ.

02Ordinary PDFs, scans and email attachments alone do not satisfy that definition.

03The portal links June 2026 guidance.

04Its definitions and scope help explain the programme, but its page 19 table still carries the superseded July large-entity provider date.

05Use amending Decision 66 for that milestone.

06MoF eInvoicing portal, checked 16 September 2026 (source 1).

07Ministerial Decision 244 of 2025 establishes phased implementation.

08Its original large-entity provider deadline was subsequently amended.

09The current table below combines its unaffected provisions with Decision 66 of 2026.

10MD 244 of 2025, Articles 1 and 3–5, official PDF, checked 16 September 2026 (source 3).

11The amended large-entity clause includes revenue equal to or exceeding AED 50 million.

12It replaces the original 31 July 2026 appointment date with 30 October 2026 while retaining implementation by 1 January 2027.

13The exact AED 50 million boundary therefore belongs in the earlier cohort.

14MD 66 of 2026, replacement Article 5(1)(a), full official PDF read 16 September 2026 (source 4).

15The ministry also confirms the extension in its amendment announcement, May 2026, checked 16 September 2026 (source 2).

16Some announcement wording says “exceeds”; use the decision's inclusive boundary when writing the table.

17The complete one-page decision was retrieved during the design refresh.

18Its footer date placeholders do not establish a publication day.

19The official indexed announcement was also refreshed; its direct URL timed out.

20Revenue here follows MD 244's most-recent-accounting-period definition.

21Do not substitute Saudi VAT-subject revenue.

22MD 244 also treats B2C transactions separately pending a further ministerial determination.

23Do not simplify the schedule into “all VAT-registered businesses” or “all businesses without exception.”

24Determine actual scope, exclusions and transaction type using current official material and qualified advice.

25The June 2026 guide, sections 3 and 6–9 (source 7) supports the definition of revenue as gross income in the most recent accounting period and explains scope and exclusions.

26Its phase table does not override the amendment.

27This source snapshot was checked on 16 September 2026.

28Source access dates are separate from the article’s eventual publication date.

02Integration is implemented through notified waves, with additional technical requirements.

03The programme's starting dates describe its history, not a fresh grace period for an already covered taxpayer.

04ZATCA, e-invoicing regulations and programme, checked 16 September 2026 (source 5).

05The latest specific wave verified for this explanation is Wave 25, announced 24 July 2026.

06ZATCA states that it covers taxpayers whose revenues subject to VAT exceeded SAR 187,500 in any of 2022, 2023, 2024 or 2025, with notified taxpayers to integrate by no later than 1 February 2027.

07ZATCA, Wave 25 announcement, 24 July 2026 (source 6).

08That wording is not the UAE's annual accounting revenue test.

09Do not change “exceeded” to “at least,” use current-year revenue alone, or assume the wave determines whether someone must register for VAT.

10An entity already required to integrate under an earlier notification cannot treat Wave 25 as an extension.

11Check the taxpayer's actual notice and current ZATCA requirements.

02Give each state a timestamp and accountable owner.

03Preserve rejected invoices and reasons; successful transmission is not evidence of commercial approval or payment.

04Start with entity and master data.

05Verify legal seller and buyer identifiers, registered addresses, currency, item units and tax treatment with the responsible finance owner.

06Then map each required field to its source system.

07A field being visible on a PDF does not prove it is stored reliably in the ERP.

08Test credit notes, cancellations where applicable, partial deliveries, duplicate submissions, unavailable services and reconciliation after recovery.

09Distinguish test records from live tax documents.

10Approval to run a pilot is not approval to issue production invoices or make accounting entries automatically.

11AI can help classify invoice exceptions and extract information for review.

12Arithmetic, schema validation, duplicate detection and posting controls often need deterministic rules.

13A model's confidence score should not replace an authoritative invoice status.

14Bank-detail changes require verification independent of the invoice's appearance.

02It falls in the at-least-AED-50-million cohort.

03This is a category illustration, not a determination for a real company.

04Its provider appointment and implementation dates are separate milestones.

05For a fictional month, assume 2,000 incoming invoices.

06Eighty percent match approved records and 20% need investigation.

07If clean invoices take two minutes and exceptions take 15 minutes, monthly handling is 1,600 × 2 + 400 × 15 = 9,200 minutes, or 153.3 hours.

08Suppose better master data reduces the exception share to 10%, without changing invoice volume or handling times.

09Handling becomes 1,800 × 2 + 200 × 15 = 6,600 minutes, or 110 hours.

10The capacity difference is 43.3 hours.

11This is illustrative arithmetic about exception reduction, not an estimated effect of e-invoicing or AI.

12The calculation excludes implementation, training and investigation of newly detected errors.

13It does not forecast payment speed or cash savings.

14To test the business case, collect the real distribution of handling times and distinguish invoice counts from line counts.

15Separate corrected errors from merely bypassed controls.

02Each source supports only the scope stated beside the claim.

02Then map invoice creation, validation, transmission, commercial checks, exceptions and settlement, with an owner and evidence for every state.

02Poor purchase-order discipline, disputed quantities and slow approvals can keep payment delays unchanged.

03A provider connection also does not fix customer-master quality.

04Compliance does not establish an improvement in cash collection.

05This is a dated research snapshot.

06We verified a specific Saudi wave, not an exhaustive legal history or every subsequent taxpayer notice.

07The June guideline PDF was retrieved during design.

08Relevant sections were read, not every legal detail audited.

09Its old provider appointment date conflicts with Decision 66 and must not be reused.

10Detailed field and penalty claims remain outside this graphic's scope.

11The official decision and announcement support the dates presented, while application to an actual entity depends on its scope and current obligations.