Standard Operating Procedure for KSA Tax-Compliant Invoice Generation

Standard Operating Procedure: KSA Tax-Compliant Invoice Generation

Document ID: SOP-FIN-KSA-001
Effective Date: 2024-05-20
Version: 1.0.0
Review Cadence: Semi-annual (or upon ZATCA regulatory updates)

---

1. Executive Summary & Purpose

This SOP establishes the technical and procedural requirements for generating VAT-compliant tax invoices in the Kingdom of Saudi Arabia (KSA). It ensures adherence to the Zakat, Tax and Customs Authority (ZATCA) Phase 1 and Phase 2 (Integration/e-Invoicing) mandates.

2. Scope & Prerequisites

• Scope: All commercial transactions between Template Registry and KSA-based entities.
• Prerequisites:
  • Valid ZATCA-registered Tax Identification Number (TIN).
  • Access to an API-integrated ERP or E-invoicing middleware (e.g., SAP, Oracle, or compliant SaaS).
  • Digital Signature Certificate (for Phase 2 compliance).
  • QR Code generation library (ZATCA Standard compliant).

3. Roles & Responsibilities (RACI Matrix)

---

4. Step-by-Step Procedure

Phase 1: Data Validation & Header Setup

• Verify Buyer TIN and Legal Name match the ZATCA registry.
• Assign unique Invoice Reference Number (IRN) using a strictly sequential, non-repeatable logic.
• Set Invoice Date (Hijri/Gregorian date must be synchronized).

Phase 2: Line Item & Tax Calculation

• Itemize goods/services with distinct VAT category codes (Standard, Zero-rated, or Exempt).
• Apply VAT rate (Current KSA Standard: 15%).
• Calculate "Taxable Amount" and "Total VAT Amount" per line item.
• Validate "Total Invoice Amount" (Sum of taxable amount + VAT).

Phase 3: ZATCA Compliance Formatting

• Generate QR Code string (Tag 1-5: Seller Name, TIN, Timestamp, Total, VAT Total) in Base64 format.
• Embed QR Code in the invoice template.
• (Phase 2 Only) Hash the invoice XML and sign with the CSID (Cryptographic Stamp ID).
• Include the XML-standardized file format (UBL 2.1).

Phase 4: Archival & Transmission

• Transmit invoice to ZATCA FATOORA portal (if applicable).
• Store immutable copy in the secure digital archive for 6 years per KSA commercial law.

---

5. Quality Assurance & Pro-Tips

Best Practices:

• Strict Sequencing: Never recycle invoice numbers; gaps in sequences trigger ZATCA audits.
• Dual-Language: While English is acceptable, providing bilingual (Arabic/English) templates reduces friction in B2G (Business-to-Government) transactions.
• Validation: Use the ZATCA QR Code Generator during testing to ensure your generated QR strings are readable.

Common Pitfalls:

• Incorrect VAT Treatment: Applying 15% VAT to zero-rated goods is the #1 cause of rejection.
• Timezone Mismatch: Ensure server time matches KSA Standard Time (AST/UTC+3).

Metric Thresholds:

• Processing Latency: < 500ms for XML generation.
• Rejection Rate: Target < 0.1% (Compliance failure).

---

6. Frequently Asked Questions

Q: Is a PDF enough for ZATCA compliance?
A: No. Under Phase 2, a PDF is merely a visual representation. The "Source of Truth" is the structured UBL 2.1 XML file that must be digitally signed and sent to ZATCA.

Q: Can we issue manual (handwritten) invoices?
A: No. Electronic invoicing is mandatory for all VAT-registered entities in KSA. Handwritten invoices are strictly non-compliant and subject to heavy penalties.

Q: What happens if an invoice is issued with an error?
A: Do not delete. Issue a "Credit Note" or "Debit Note" linked to the original Invoice Reference Number (IRN) to maintain a transparent audit trail.

---

Authorized by: Julian Vance, Chief Architect, Template Registry