E‑Invoicing in ERP

From ERPEDIA, the independent ERP knowledge base

E‑invoicing is the electronic exchange of invoice documents between suppliers and buyers, often with real‑time reporting to tax authorities. In the GCC, Saudi Arabia's ZATCA has pioneered mandatory e‑invoicing, while the UAE currently requires QR codes on tax invoices. ERP systems must support these requirements to ensure compliance. This article covers e‑invoicing standards, formats, and links to VAT compliance, APIs, and finance.

Contents

1. What is e‑invoicing?

E‑invoicing replaces paper and PDF invoices with structured electronic documents that can be processed automatically. Benefits include:

  • Faster processing and payment.
  • Reduced errors and fraud.
  • Real‑time visibility for tax authorities (in some countries).
  • Automatic reconciliation.
Models: Cleared Invoice pre‑approved by tax authority (e.g., ZATCA Phase 2). Post‑audit Invoice generated, tax authority audits later (e.g., UAE current model).

2. UAE e‑invoicing requirements

As of 2026, the UAE does not have mandatory e‑invoicing clearance, but tax invoices must:

  • Be issued within 14 days of supply.
  • Include a QR code containing: seller name, VAT number, invoice date, invoice total, VAT amount.
  • Be in Arabic or English (Arabic recommended for B2C).
  • Meet format requirements (PDF/A is common).

The FTA has announced plans to move to a full e‑invoicing model (similar to ZATCA) in the coming years.

See VAT compliance for detailed VAT rules.

3. ZATCA (Saudi Arabia) e‑invoicing

Saudi Arabia's ZATCA has implemented a two‑phase e‑invoicing mandate:

Phase 1 (Dec 2021) → Generate → Store Phase 2 (2023+) → Integrate → Report
  • Phase 1 (Generation): Invoices must be in structured XML/PDF/A format, with a UUID and QR code. No reporting to ZATCA.
  • Phase 2 (Integration): Invoices are submitted to ZATCA in real time for clearance. ERP must integrate with ZATCA APIs.

ERP systems for Saudi businesses must support:

  • XML invoice generation (ZATCA format).
  • Digital signatures (e‑seal).
  • Real‑time API submission.
  • Handling of clearance responses (pass, fail, warning).

4. QR codes on invoices

Both UAE and Saudi require QR codes on tax invoices. The QR code contains encoded data:

UAE QR code data (TLV format):
1. Seller Name: ABC Trading
2. VAT Number: 123456789000000
3. Date: 2026-03-02
4. Total: 1000.00
5. VAT: 50.00
QR

ERP must generate QR codes dynamically and include them on printed/PDF invoices.

5. Invoice formats (PDF, XML, EDI)

FormatUse caseStructure
PDF/AHuman‑readable invoice (UAE, Saudi Phase 1)Visual, with embedded QR code
XMLStructured data for clearance (ZATCA Phase 2)Standardized tags, can be validated
EDIB2B electronic tradingEDIFACT, ANSI X12
JSONAPI‑based invoicingLightweight, used in some cloud ERPs

6. ERP integration with tax authorities

For ZATCA Phase 2, ERP must integrate with tax authority APIs. Key considerations:

  • Authentication: OAuth2 / client certificates.
  • Invoice submission: Real‑time or batch.
  • Response handling: Clearance result, error codes.
  • Retry logic: Handle temporary failures.
  • Reporting: Track submitted invoices, status.

See APIs in ERP and system integration.

7. Implementing e‑invoicing in ERP

Steps to prepare ERP for e‑invoicing:

  1. Assess requirements: UAE vs Saudi vs other GCC.
  2. Configure invoice formats: Set up PDF templates, QR code generation.
  3. Enable XML generation: For ZATCA, ensure XML meets schema.
  4. Implement API integration: Connect to tax authority (if required).
  5. Test thoroughly: Use sandbox environments.
  6. Train staff: Ensure they understand new processes.
Timeline: Start planning at least 6‑12 months before mandate.

8. Future trends

  • GCC‑wide e‑invoicing: Other GCC countries (Oman, Bahrain, Kuwait) are expected to follow Saudi and UAE.
  • Real‑time reporting: More tax authorities moving to clearance models.
  • Peppol: International e‑invoicing framework gaining adoption.
  • AI for validation: Automated checking of invoice data.

Key Takeaways

  • UAE requires QR codes on tax invoices; full e‑invoicing expected.
  • ZATCA (Saudi) mandates two‑phase e‑invoicing – Phase 2 requires real‑time clearance.
  • QR codes encode seller, VAT, date, total, VAT.
  • XML is the standard for clearance; PDF/A for human readability.
  • ERP must integrate with tax authority APIs for Phase 2 compliance.
  • Start planning early to meet deadlines.

Do I need e‑invoicing if I only sell B2C? Yes – QR codes are required on all tax invoices, regardless of customer type.

What is a UUID in ZATCA invoices? Universally Unique Identifier – a unique number for each invoice, required for ZATCA.

Can I use a third‑party e‑invoicing provider? Yes, many ERPs integrate with providers that handle tax authority communication.

Continue Reading in ERPEDIA

ERPEDIA is maintained by Professionals Lobby as an independent ERP knowledge initiative focused on reducing ERP implementation risk in the UAE and GCC.
For structured, vendor‑neutral ERP advisory → Speak with an independent ERP advisor.