ZATCA Phase 2 E-Invoicing Integration Guide

The short answer

First confirm the taxpayer’s notice, wave and date, then compare the ERP with current requirements, fields and invoice types. Configure and integrate through the developer environment, test reporting, clearance, errors, cancellation and credit notes, and monitor submission after production.

Three actions to take

  • Do not infer a wave from an unofficial revenue figure alone.
  • Test the invoice types and routes the business actually uses.
  • Manage logs, keys and certificates under a security policy.

1. Scope and gap assessment

Collect the ZATCA notice, entities, branches, VAT numbers, document types and issue points, then review fields, calculations and sequence.

  • Reconcile seller, buyer and branch data.
  • Test tax, discounts, rounding and credit notes.

2. Configuration and integration

Prepare units, devices, keys, signatures, XML and QR behavior for the relevant type and requirements using the current developer tools.

  • Separate test and production secrets.
  • Keep a result for every scenario and version tested.

3. Launch and monitor

Implement queues, retries, alerts and daily reconciliation and define business continuity when connectivity is unavailable.

  • Monitor submission state and rejection by reason.
  • Reconcile ERP invoices with interface records daily.

Need to apply this to your facility?

Share the activity, city and current stage, and we can help define an appropriate work scope.

Explore healthcare IT solutions