Navigating Saudi Tax

Blog

  • VAT Group Registration in Saudi Arabia

    P1-B — Part of the P1 Registration Cluster on dariba.co
    01

    What is a VAT Group?

    A VAT group is one of the most powerful structural tools available to corporate groups operating in Saudi Arabia. Used correctly, it eliminates VAT friction across the entire group and simplifies compliance dramatically.

    Under Articles 10–12 of the VAT Implementing Regulations, two or more related legal persons can apply to ZATCA to be treated as a single taxable person for VAT purposes. Once approved, the group files one VAT return, holds one Tax Identification Number, and — critically — all supplies between group members are disregarded for VAT. They fall completely outside the scope of the tax.

    The group is treated as a taxpayer entirely independent of its individual members. One entity is appointed as the Tax Group Representative, who is primarily responsible for all compliance obligations — filing, payment, and ZATCA correspondence — on behalf of the entire group.

    02

    Eligibility: The April 2025 Rules

    The April 2025 amendments to Article 10 materially tightened the eligibility criteria for VAT group registration. The updated rules now require that all of the following conditions are met — and continue to be met throughout the group’s registration:

    Condition Requirement Changed in April 2025?
    Residency Each member must be resident in the Kingdom and eligible to register as a taxable person Tightened
    Common Control 50%+ of capital, voting rights, or market value of each member is held directly or indirectly by the same person(s), or one member has the power to control and dominate the others Expanded
    Special Zones No member may be licensed to operate in a special zone with tariff suspension status New
    Refund Eligibility Neither the applicant nor any member may be a person eligible for a VAT refund under Article 70 (with limited exceptions) New
    No Dual Membership No member may simultaneously be a member of another tax group New
    Existing Groups — 180-Day Grace Period

    Tax groups registered before the April 2025 amendments were issued have a grace period of up to 180 days from the publication date to bring their group structure into compliance with the new rules. This is a live and time-sensitive obligation for any group currently registered. If your group includes members in free zones or members eligible for VAT refunds, this needs immediate review.

    The April 2025 amendments also expanded the control test: previously, only capital and voting rights were measured. The updated rule now also captures control through market value or through one member having the practical power to control and dominate the others — even without majority ownership. This is a broader, more substance-based test.

    03

    The Business Case for a VAT Group

    Every intra-group invoice without VAT group status is a cash flow drag. Every month without a group return is duplicated compliance work.

    The practical benefits are substantial for any multi-entity corporate structure:

    Intra-group VAT eliminated. Services, goods, management fees, and loans between group members carry no VAT once the group is registered. A holding company charging management fees to subsidiaries, an IP entity licensing rights across the group, a shared services centre billing operational costs — all of these become VAT-neutral. No output VAT to charge, no input VAT to recover, no invoices to reconcile.

    Single VAT return. One filing per period instead of one per entity. For a group of five companies, that collapses five monthly returns into one — significantly reducing compliance workload and the risk of filing errors.

    Cash flow optimisation. Where some group entities generate input VAT credits and others generate output VAT liabilities, the group return nets these off. Instead of one entity claiming a refund and another making a payment in the same period, the group position is calculated once and a single net amount is either paid or refunded.

    Scenario — Cash Flow Impact of Group Registration

    A Saudi holding group has three entities: a management company that provides services to the operating subsidiaries (charging SAR 200,000/month + VAT), and two trading subsidiaries. Without group registration, the management company charges SAR 30,000 in output VAT each month, which the subsidiaries pay and then wait to recover. That is SAR 30,000 in cash locked between entities every single month — SAR 360,000 per year in unnecessary VAT friction. With group registration, the intra-group charge is VAT-free. The cash flow drag disappears entirely.

    04

    The Application Process

    Under the April 2025 amendments to Article 11, the application process now requires more documentation than before. The application must be submitted by the appointed Tax Group Representative using ZATCA’s prescribed form, and must include:

    • Full member information for all entities in the group, per the standard registration requirements of Article 8
    • A copy of the group agreement — a formal agreement concluded between all members, including the appointment of the tax representative and evidence of the representative’s consent to the appointment
    • The agreement is treated as an acknowledgment by the group of its commitment to all terms and conditions of tax group registration

    ZATCA may request additional supporting documents to verify eligibility. If the application is refused, ZATCA must issue a written notification of refusal.

    Once approved, the group takes effect from the first day of the month following approval, unless ZATCA specifies a later date. ZATCA issues a new registration certificate and a new TIN for the group. The individual TINs of previously registered members are suspended — not cancelled — for the duration of group membership.

    05

    Managing the Group: Changes, Additions, and Disbandment

    VAT groups are not static. Businesses grow, restructure, and divest — and the group registration must reflect those changes promptly.

    Notifying changes: The Tax Group Representative must notify ZATCA within 20 days of any change to the information originally provided in the application, or any event that affects a member’s continued eligibility. This includes changes in ownership structure, a member losing residency status, or a member entering a free zone.

    Adding or removing members: Subject to all group members’ approval, the representative can apply to add new eligible entities or remove existing ones. Changes from an approved application take effect from the date the request is made, unless ZATCA specifies otherwise.

    Disbanding the group: The group can be disbanded by application of the representative, with all members’ consent. Where a member leaves or the group disbands, any entity that remains eligible as a taxable person in its own right will have its individual TIN reinstated. Members who were never individually registered before joining the group will receive a new TIN.

    Joint and several liability: All group members remain jointly and severally liable for VAT liabilities, penalties, and obligations that arose during their period of membership — even after they leave the group. This is a significant point for any corporate transaction involving a former group member: the buyer inherits exposure for the period of group membership.

    M&A Due Diligence Note

    When acquiring an entity that was previously part of a VAT group, always verify the group’s historic compliance position. Joint and several liability means the acquired entity carries potential exposure for the entire group’s unpaid VAT obligations during its membership period — not just its own.

    06

    ZATCA’s Override Powers

    Two ZATCA override provisions deserve specific attention, as they can override the group’s own intentions.

    Disregarding group status: ZATCA can issue a notice to the group representative to set aside the VAT group’s effect — meaning it can reinstate VAT on intra-group supplies — where the group structure results in a tax advantage that is contrary to the purpose of the law, and obtaining that advantage is one of the principal purposes of the group. This notice can be applied retrospectively. This is effectively an anti-avoidance power targeting VAT groups structured primarily for tax benefit rather than genuine commercial reasons.

    Imposing group status: Conversely, ZATCA can issue a notice to two or more persons who are not in a group but are eligible to form one — requiring them to be treated as a VAT group — where separate registration produces a tax advantage contrary to the law. Groups cannot use separate registration to generate artificial input VAT recovery or refund positions that would not exist under group treatment.

    07

    Compliance Risks

    • Failing the 180-day remediation deadline. Existing groups with members in special zones or with refund-eligible entities must regularise their structure within the grace period. Missing this deadline means the group is non-compliant with the April 2025 rules — exposing it to ZATCA action.
    • Ongoing eligibility monitoring. All conditions must be met continuously, not just at application. A change in ownership that drops a member below the 50% control threshold must be notified within 20 days. Continuing to file as a group when eligibility has lapsed is a material compliance failure.
    • Joint and several liability in transactions. Buyers acquiring entities with prior group membership often overlook the historic VAT exposure. This is a standard due diligence item that is frequently under-examined in Saudi M&A transactions.
    • Treating group TIN as suspended TINs. Once the group is registered, the group TIN must be used on all tax invoices and ZATCA correspondence. Using a suspended individual member TIN on an invoice after group registration creates non-compliant invoices that will not support input VAT recovery for recipients.
    Key Takeaways
    1. A VAT group treats multiple related entities as a single taxable person. All intra-group supplies are outside the scope of VAT — there is no output VAT to charge and no input VAT to recover between members.
    2. The April 2025 amendments significantly tightened eligibility. Three new disqualifying conditions were added: membership in a special zone with tariff suspension status, eligibility for VAT refunds under Article 70, and dual membership in another tax group.
    3. The control test now captures economic dominance — not just formal ownership. One entity having the practical power to control others can satisfy the control condition even without 50% ownership.
    4. Existing groups have a 180-day grace period from April 2025 to comply with the new Article 10 conditions. This is time-sensitive and should be reviewed immediately.
    5. The application now requires a formal group agreement — a new April 2025 requirement — appointing the representative and confirming all members’ commitment to the group’s obligations.
    6. All group members are jointly and severally liable for VAT liabilities during their membership period — even after leaving the group. This creates real exposure in corporate acquisitions that must be surfaced in due diligence.
    7. ZATCA can disregard group status retrospectively if the structure produces a tax advantage that is contrary to the purpose of the law. Group structures must have genuine commercial justification beyond tax efficiency.
    Next in the Registration Cluster
    P1-C — VAT Deregistration: When, How, and What It Triggers
    Read Next →

    This article is published for informational purposes only and does not constitute legal or tax advice. Content is grounded in ZATCA’s VAT Implementing Regulations (as amended through April 2025). Readers should confirm regulatory positions with qualified Saudi VAT advisors for their specific circumstances. The official Arabic text of the Regulations is authoritative. dariba.co is an independent platform with no consulting relationships.

  • Fatoorah and VAT Compliance: How Saudi E-Invoicing Affects Your VAT Obligations

    Part of Saudi E-Invoicing (Fatoorah): The Complete Series — Article 7 of 7
    01

    The Legal Connection — E-Invoicing and VAT Are One Obligation

    The E-Invoicing Resolution (Clause First, Paragraph 3) states explicitly that electronic invoices cleared by or reported to the Authority are the tax invoices considered valid for exercising the right of input tax deduction under Article 48(1) of the Unified VAT Agreement. An uncleared Tax Invoice has no legal basis for input tax deduction purposes — regardless of its content accuracy.

    This means e-invoicing compliance and VAT compliance are not separate workstreams. An e-invoicing failure becomes a VAT problem — often for both the seller who issued an invalid document and the buyer whose input tax deduction is at risk. Finance teams that treat Fatoorah as an IT obligation and VAT as a tax obligation, managed separately, are underestimating the connection between the two.

    Worked Example — Input Tax Risk for the Buyer

    Sanad Engineering Co. (Riyadh) purchases SAR 2 million of equipment from a supplier in Q1 2025, generating SAR 300,000 of input VAT on the Tax Invoice received. Sanad files its Q1 VAT return and claims the deduction. The supplier’s FATOORA integration is later found to have been non-operational for six weeks in Q1 — those invoices were never cleared. ZATCA’s cross-referencing flags the discrepancy: Sanad’s input tax claim appears against invoices with no FATOORA clearance record. Sanad faces a SAR 300,000 VAT adjustment plus potential surcharge — despite acting in good faith. The liability rests with the party that claimed the deduction, not the party that failed to clear the invoice.

    02

    Input Tax Deduction — What Makes an Invoice Valid

    For a buyer to validly deduct input VAT, they must hold a valid tax invoice. Under Fatoorah, a Tax Invoice is valid for this purpose only if it has been cleared by FATOORA and carries ZATCA’s cryptographic stamp. The buyer cannot independently verify whether the supplier’s system was correctly configured or whether clearance actually occurred — they rely on the cleared document they receive.

    The practical protection for buyers: verify that key suppliers are Phase 2 integrated and generating cleared invoices before processing large input tax claims — particularly with new suppliers or recently wave-notified businesses. This is not something most businesses currently do systematically, and it is an area where risk is materially underestimated.

    03

    VAT Supply Types — How They Appear in E-Invoices

    Supply TypeVAT RateE-Invoice Requirement
    Standard-rated supply15%VAT amount stated; standard rate code at line and document level
    Zero-rated supply (exports, certain medical goods, international transport)0%Zero-rate code applied; exemption/zero-rating reason code mandatory
    Exempt supply (financial services, certain educational services)ExemptExempt code applied; exemption reason code mandatory
    Mixed supply (standard-rated and zero/exempt on same invoice)MixedVAT treatment applied at line level; document-level totals must reconcile
    Out-of-scope supplyN/ASeparate out-of-scope code applied
    Exemption Reason Codes Are Mandatory

    An invoice for an exempt or zero-rated supply that shows zero VAT without a reason code from ZATCA’s approved list is non-compliant and will be rejected by FATOORA. Using the wrong code is also a compliance failure, even if the correct treatment is zero VAT. This is one of the most consistently missed requirements across all supply types.

    04

    Credit Notes and VAT Adjustments

    Electronic credit and debit notes are issued to correct or adjust the value of previously issued invoices under Article 40(1) and Article 54(3) of the VAT Implementing Regulation. Every credit or debit note must reference the original invoice by Invoice Reference Number. A note without a valid reference fails FATOORA validation — the VAT adjustment it represents cannot be applied.

    The compliance model follows the original invoice. A credit note against a Tax Invoice must go through clearance. If a VAT adjustment needs to appear in a specific VAT return period, the credit note must be cleared within that period — and clearance requires FATOORA to be available and responsive. Manage credit note timing actively, not as an afterthought.

    Credit Notes Cannot Cancel an Invoice — Only Adjust It

    A credit note adjusts the value — it does not cancel the original invoice. The original invoice remains in FATOORA’s records. To fully reverse a transaction, issue a credit note for the full invoice amount. Both the original and the credit note remain in your archive and FATOORA’s data. You cannot delete or overwrite the original.

    05

    E-Invoicing and Your VAT Return — The Data Connection

    FATOORA holds your cleared and reported invoice data. Your VAT return is filed separately through the taxpayer portal. ZATCA reconciles the two: your output VAT on the return should match the VAT amounts on cleared and reported invoices; your input VAT deductions should correspond to cleared Tax Invoices from your suppliers. Discrepancies flag you for review.

    Reconciling FATOORA-cleared invoice totals against VAT return line items before filing is a pre-filing control, not a post-filing exercise. The discrepancies ZATCA will query are visible in your data before the return is submitted. Identifying them first puts you in a very different position than explaining them after the return has been filed and ZATCA has raised the query.

    06

    Common VAT and E-Invoicing Errors

    • Claiming input tax on uncleared Tax Invoices. The buyer’s accountant may not know to check whether the supplier’s invoice was cleared. The VAT return is filed in good faith. ZATCA’s data cross-referencing identifies the mismatch months later, and the adjustment falls on the buyer — not the supplier who failed to clear.
    • Wrong VAT rate hard-coded in the XML. A standard 15% rate hard-coded for all lines — including zero-rated ones — generates an incorrect XML that fails FATOORA validation. The invoice that looks correct on the PDF may not match the XML FATOORA actually validates.
    • Missing exemption reason codes. Supplies coded as zero-rated or exempt must carry the ZATCA reason code. An invoice showing 0% VAT without a reason code is rejected. If the system is not correctly handling rejections, the invoice may appear to have been filed while actually failing.
    • Credit notes without original invoice reference. A credit note without a valid Invoice Reference Number is rejected by FATOORA. The VAT adjustment cannot be applied. If this happens near period-end, the adjustment misses the intended return period — creating a timing difference requiring correction in the following period.
    • Treating e-invoicing and VAT as separate team responsibilities. Where IT owns e-invoicing and finance owns VAT, the handover is where errors accumulate. Rejected invoices IT logs as system errors but finance never sees. FATOORA reconciliation gaps finance discovers at year-end but IT considers resolved. Both teams must work from the same data with a shared understanding of the tax consequence of every e-invoicing failure.
    07

    Frequently Asked Questions

    No — not validly. The E-Invoicing Resolution states that only invoices cleared by or reported to ZATCA are valid for exercising input tax deduction rights from the Phase 2 integration date. If the buyer claimed input tax on an uncleared invoice and ZATCA identifies the discrepancy through data cross-referencing, the buyer faces a VAT adjustment — even though the invoice content may have been entirely correct.
    Yes. The E-Invoicing Regulation covers all taxable supplies — including zero-rated and exempt. An invoice for an exempt supply must still be generated through a compliant EGS, carry the correct exemption reason code, and — in Phase 2 — go through the appropriate clearance or reporting process. The zero VAT amount does not remove the e-invoicing obligation.
    Issue a credit note to reverse the original invoice and a new Tax Invoice with the correct treatment. Both must go through clearance. The over-charged VAT creates an overstated output VAT liability for you and may create an overstated input tax claim for your buyer — both need to be corrected in the relevant VAT return period.
    Run a reconciliation report comparing your FATOORA-cleared Tax Invoice totals and reported Simplified Tax Invoice totals against the output VAT figure on your VAT return before filing. Any variance — invoices in FATOORA not on the return, or return figures exceeding FATOORA data — should be investigated before submission. ZATCA performs a similar reconciliation from its side.
    Generally no. Simplified Tax Invoices are for B2C transactions and do not support input tax deduction for business buyers. If you are VAT-registered and purchasing for business purposes, you need a Tax Invoice. If a supplier issues you a Simplified Tax Invoice for a B2B transaction, request a Tax Invoice. Without it, the VAT on that purchase cannot be recovered.
    ◆ Key Takeaways
    1. E-invoicing compliance and VAT compliance are the same obligation in two systems. An e-invoicing failure is a VAT problem — often for both the seller (invalid document) and the buyer (input tax deduction at risk).
    2. Only invoices cleared by or reported to ZATCA are valid for input tax deduction from the Phase 2 integration date. The buyer’s ability to deduct VAT depends on the seller’s e-invoicing compliance — not just on the invoice content.
    3. Every zero-rated and exempt supply must carry the correct exemption or zero-rate reason code from ZATCA’s approved list. An invoice showing zero VAT without a reason code is non-compliant and will be rejected by FATOORA.
    4. Credit notes must reference the original invoice to be valid. Without the Invoice Reference Number, the note fails FATOORA validation and the VAT adjustment cannot be applied to the relevant tax period.
    5. Reconciling FATOORA-cleared invoice data against your VAT return before filing is a pre-filing control. The discrepancies ZATCA will query are visible in your data before the return is submitted — finding them first is substantially better than explaining them afterwards.

    Also in this series

    Tax Intelligence
    Tax Invoice vs. Simplified Tax Invoice — Which Type Applies to Your Business?
    Tax Intelligence
    Clearance vs. Reporting — What’s Actually Required and When
    Tax Intelligence
    E-Invoicing Penalties — What ZATCA Charges and How to Avoid It
    Tax Intelligence
    The Complete Fatoorah Compliance Guide — Pillar Article

    Saudi E-Invoicing (Fatoorah) — 7-article series

    Continue with the full series on dariba.co

    View all articles →

    This article reflects ZATCA’s E-Invoicing Regulation (December 2020), the Controls, Requirements, Technical Specifications and Procedural Rules Resolution (May 2023), and the VAT Implementing Regulation. It is for informational purposes only and does not constitute legal or tax advice. Confirm the current position at zatca.gov.sa or with a qualified Saudi tax advisor. dariba.co is an independent platform.

  • Saudi E-Invoicing Penalties: What ZATCA Can Fine You For and How to Stay Compliant

    Part of Saudi E-Invoicing (Fatoorah): The Complete Series — Article 6 of 7
    01

    The Penalty Framework

    E-invoicing penalties are applied under the VAT Law framework, with violation classifications and specific penalty amounts determined by ZATCA’s Board of Directors resolutions. The key principle: penalties accumulate across assessment periods. A business that fails to integrate with FATOORA is not facing a single fine — it faces potential exposure for each period of continued non-compliance.

    Penalty Amounts — A Note on Sources

    The penalty ranges below are drawn from ZATCA’s publicly communicated guidance and industry sources. Exact amounts for specific violation categories are set by ZATCA Board resolutions, which are periodically updated. Where ranges are given, they represent the published spectrum from minor to severe instances of each violation. Confirm current figures at zatca.gov.sa or with a qualified advisor.

    02

    Violations and Penalty Ranges

    ViolationPenalty RangeNotes
    Failure to issue invoices through a compliant EGSSAR 5,000 – SAR 50,000Per assessment period; escalates for repeat violations
    Using an EGS with prohibited functionalities enabledSAR 5,000 – SAR 50,000All invoices produced by the solution are affected
    Failure to integrate with FATOORA by wave deadlineSAR 5,000 – SAR 50,000Ongoing non-compliance compounds across periods
    Sharing a Tax Invoice before clearanceSAR 1,000 – SAR 10,000Also creates input tax risk for the buyer
    Failure to report Simplified Tax Invoices within 24 hoursSAR 1,000 – SAR 10,000Per period; systematic failure escalates
    Failure to maintain e-invoice records as requiredSAR 10,000 – SAR 50,000Archive must be accessible to ZATCA at any time
    03

    How ZATCA Detects Non-Compliance

    ZATCA processed over 8.2 billion e-invoices through FATOORA in 2025 — a 64% increase from 2024. Every cleared Tax Invoice and reported Simplified Tax Invoice flows through the platform. Detection mechanisms include: tracking clearance rates and rejection patterns by taxpayer; cross-referencing buyer VAT return input tax claims against FATOORA-cleared invoices; comparing taxpayer VAT return output tax figures with FATOORA-submitted invoice volumes; and identifying taxpayers above a revenue threshold with zero FATOORA activity.

    The “We Haven’t Been Checked” Defence No Longer Exists

    Pre-Fatoorah, a business might go years without a tax audit. FATOORA data means audit-style analysis of your compliance can happen at any time through automated data matching, without a field auditor visiting your premises. The question is not whether ZATCA can detect gaps — it is when the authority prioritises acting on what the data is already showing.

    04

    The 5 Violations Most Likely to Trigger a Penalty

    • Failure to complete FATOORA onboarding by the wave deadline. FATOORA data shows zero or partial activity for these taxpayers. This is the highest-exposure category and one of the most common — often caused by delayed IT projects or the assumption that a vendor notification would arrive before the deadline.
    • Sharing Tax Invoices before clearance confirmation. A workflow that dispatches invoices immediately on generation — before the clearance response is received — is issuing invalid documents on every B2B transaction. Often a system configuration error, but the legal consequence is identical to deliberate non-compliance.
    • Systematic 24-hour reporting failures for Simplified Tax Invoices. Businesses relying on manual batch reporting — or whose automated reporting has silent failure handling — accumulate violations across every transaction during periods when reporting fails. High-volume B2C businesses are particularly exposed.
    • Using a Phase 1-only solution after Phase 2 wave deadline. A system that generates correct Phase 1 invoices but lacks CSID capability, XML generation, or FATOORA API connectivity is non-compliant from the wave deadline forward. Every invoice it produces after that date is technically non-compliant.
    • Incomplete archive — inability to produce historical invoices on request. Businesses that have migrated ERP systems or purged old data cannot meet the record production obligation. This surfaces on audit, and its consequences can be substantial where ZATCA auditors need records to verify input tax claims or VAT return accuracy.
    05

    The Penalty Waiver Initiative — What It Covers and When It Ends

    ZATCA’s “Initiative to Cancel Fines and Exempt Taxpayers from Penalties” has been extended to 30 June 2026. This initiative covers a range of tax compliance areas including e-invoicing violations. It provides a meaningful window for businesses with known historical non-compliance to regularise their position without incurring the full penalty exposure.

    The waiver does not apply automatically. The business must take steps to correct the underlying non-compliance: completing FATOORA integration, correcting EGS configuration, addressing archive gaps, and ensuring current compliance. After 30 June 2026, the window closes and normal enforcement applies.

    Use the Waiver Window Strategically

    The waiver is a time-limited opportunity — not a signal that ZATCA is relaxed about enforcement. Businesses that use the window to identify gaps, implement corrections, and document the remediation are in a materially different position after June 2026 than those that do nothing. If you have known compliance gaps — Phase 1, Phase 2, archive, onboarding — now is the time for an honest internal assessment and a structured remediation plan.

    06

    Frequently Asked Questions

    Failure to integrate with FATOORA by your wave deadline is treated as using a non-compliant invoicing solution, with penalties ranging from SAR 5,000 to SAR 50,000 per assessment period under the VAT Law framework. The exposure compounds across periods — a business 12 months overdue on integration is not facing a single fine but potentially multiple periods of non-compliance. The penalty waiver (open until 30 June 2026) offers a window to correct this without financial penalty.
    Yes. ZATCA can examine records within the relevant VAT assessment periods — typically six years from the end of the tax period. Phase 1 invoices from 2022 remain within scope for audit today. Non-compliant Phase 1 invoices are invalid VAT documents, and the audit exposure from that period has not expired.
    The legal compliance obligation rests with the taxpayer, not the vendor. If your EGS failed to meet ZATCA’s requirements because the vendor’s software was not Phase 2 compliant, the penalty exposure is yours. You may have a commercial claim against the vendor, but that does not reduce your liability to ZATCA. This is why verifying software compliance before go-live — rather than relying on vendor assurances — is so important.
    ZATCA’s waiver covers a broad range of tax violations including e-invoicing failures. The specific application depends on the nature of the violation and the steps taken to correct it. Businesses with complex or large-scale non-compliance should seek professional advice on how to use the waiver window effectively and what documentation ZATCA expects in a remediation context.
    ZATCA typically issues an information request or audit notification before formal penalty assessments. However, where non-compliance is identified through data matching and the evidence is clear, ZATCA may assess penalties directly. Treat any ZATCA communication about e-invoicing compliance as a priority and do not wait for a formal penalty notice to begin corrective action.
    ◆ Key Takeaways
    1. Penalties accumulate across assessment periods — a failure to integrate with FATOORA is not a one-time fine but compounding exposure for each period until compliance is achieved.
    2. ZATCA’s ability to detect non-compliance is now data-driven and near-real-time. FATOORA processes billions of invoices and automatically flags taxpayers with zero activity, high rejection rates, or discrepancies between VAT return claims and cleared invoice records.
    3. The five violations most commonly generating penalties are: failure to complete FATOORA onboarding, sharing Tax Invoices before clearance, systematic 24-hour reporting failures, using a Phase 1-only solution after the Phase 2 deadline, and inability to produce archived invoices on request.
    4. The penalty waiver initiative is open until 30 June 2026. It is a time-limited window to regularise historical non-compliance before enforcement action begins. Businesses with known gaps should use this window actively, not passively.
    5. The compliance obligation rests with the taxpayer. Software vendor failures and IT project delays do not reduce your legal liability to ZATCA. Verify compliance before each invoice is generated.

    Also in this series

    Tax Intelligence
    Phase 2 Integration Requirements — What Your Business Must Prepare For
    Tax Intelligence
    EGS Solution Requirements — What Your System Must Be Able to Do
    Tax Intelligence
    Fatoorah and VAT Compliance — How E-Invoicing Affects Your VAT Obligations
    Tax Intelligence
    The Complete Fatoorah Compliance Guide — Pillar Article

    Saudi E-Invoicing (Fatoorah) — 7-article series

    Continue with the full series on dariba.co

    View all articles →

    Penalty figures in this article are drawn from ZATCA’s publicly communicated guidance and industry sources. Exact amounts are set by ZATCA Board resolutions, which are updated periodically. Confirm current figures at zatca.gov.sa or with a qualified Saudi tax advisor. This article is for informational purposes only and does not constitute legal or tax advice. dariba.co is an independent platform.

  • ZATCA E-Invoice Solution Requirements: What Your EGS Must Be Able to Do

    Part of Saudi E-Invoicing (Fatoorah): The Complete Series — Article 5 of 7
    01

    What Is an EGS?

    An E-Invoice Generation Solution (EGS) is the software system — whether an ERP, a standalone billing application, a point-of-sale system, or a purpose-built e-invoicing platform — that generates, applies security features to, stores, and transmits electronic invoices. In Phase 2, it must also connect to ZATCA’s FATOORA platform via API for clearance and reporting.

    A single business may have multiple EGS units. Each cash register that independently generates and stamps invoices is a separate unit. A billing server generating invoices for all branches is one unit. Identifying your units correctly is the first step in any Phase 2 implementation — because each unit requires its own CSID, and one CSID shared across multiple units is a compliance failure.

    02

    Mandatory Technical Capabilities

    CapabilityWhat It Means in Practice
    XML invoice generation (UBL 2.1)Invoices must be in structured XML conforming to ZATCA’s XML Implementation Standard. Field names, encoding, and structure must match precisely — FATOORA validates against it.
    UUID generation per invoiceEach invoice must carry a UUID — a 128-bit unique identifier. No two invoices from any EGS unit should ever share a UUID.
    Cryptographic stamp application (ECDSA)The EGS must digitally sign every invoice using ECDSA with the private key associated with its CSID. This makes invoices tamper-evident: modification after stamping is mathematically detectable.
    Previous Invoice Hash (PIH) embeddingEach invoice must contain a SHA-256 hash of the immediately preceding invoice, creating a tamper-evident chain. A break in the chain is detectable by FATOORA.
    Invoice counter (tamper-proof)A sequential, non-resettable counter incrementing with every invoice. The value is embedded in the invoice and QR code.
    9-field TLV QR code (Phase 2)Machine-readable QR in TLV base64 format containing: seller name, VAT number, invoice date/time, total with VAT, VAT total, invoice hash, cryptographic stamp, CSID, and previous invoice hash.
    FATOORA API connectivityThe EGS must connect to FATOORA’s REST-based API endpoints for clearance (Tax Invoices) and reporting (Simplified Tax Invoices).
    03

    The Cryptographic Stamp — Why It Matters

    The cryptographic stamp is a digital signature using ECDSA applied to a hash of the invoice content using the private key stored in your EGS and associated with your CSID. Anyone in possession of the invoice — a buyer, ZATCA, an auditor — can verify the stamp by checking it against the public key in the CSID. If the invoice content has been modified after stamping, verification fails. This is what makes the invoice genuinely tamper-evident: not just a software prohibition on modification, but cryptographic proof that any modification is detectable.

    The Private Key Must Stay in the EGS

    The E-Invoicing Resolution explicitly prohibits the EGS from providing an option to export the cryptographic stamp private key. It must remain in the system that uses it. A solution that allows private key export — for backup, for migration, for any reason — is non-compliant. If migrating to a new system, the process involves revoking the old CSID and obtaining a new one for the new unit, not transferring the key.

    04

    Prohibited Functionalities

    Prohibited FunctionWhy It Matters
    Anonymous access / default password operationEvery user action must be attributable to a specific identified user. Anonymous or default-credential access makes the audit trail unreliable.
    Invoice alteration or deletion after generationOnce generated, an invoice is immutable. Corrections are via credit note. Any system permitting edit or delete of a generated invoice destroys record integrity.
    Log modification or deletionSystem activity logs must be immutable. No staff member can alter or erase entries.
    Inaccurate timestamp generationUsers cannot change system date to backdate or forward-date invoices.
    Invoice counter resetThe sequential counter must be permanent. No reset on year-end, update, or system restart.
    Multiple invoice sequences from one unitEach EGS unit must maintain a single, continuous hash chain. Parallel sequences break the integrity ZATCA audits verify.
    Export of cryptographic stamp private keyThe private signing key must remain secured within the EGS. Exportable keys undermine the entire trust model.
    Capability Test, Not Usage Test

    The existence of a prohibited functionality makes your EGS non-compliant — regardless of whether it has ever been used. A system that allows invoice deletion but where no deletion has occurred is still non-compliant. ZATCA’s test is capability. Review your system configuration against this list explicitly, not by assumption.

    05

    Onboarding and the CSID Lifecycle

    Before any Phase 2 invoice can be generated, your EGS unit must be registered with FATOORA and issued a CSID. The process: access the FATOORA portal using ERAD credentials → generate an OTP for each unit → enter the OTP into the EGS → receive the CSID → accept ZATCA’s subscriber agreement → test in ZATCA’s sandbox before going live.

    CSIDs have a validity period and must be renewed before expiry. A lapsed CSID means your EGS can no longer apply a valid cryptographic stamp — every invoice it produces after expiry is non-compliant. Monitor CSID expiry dates and schedule renewal at least 30 days in advance. This is an active compliance task, not an automated one.

    ZATCA’s Testing Toolkit

    ZATCA provides three testing resources: a sandbox environment mirroring the live FATOORA platform, an SDK for offline testing of invoice generation and cryptographic features, and a web-based validator for checking individual invoices. Use all three before go-live — sandbox for end-to-end integration testing, SDK for unit-level feature testing, validator for spot-checking specific configurations.

    06

    Choosing or Upgrading Your Solution

    When assessing whether your existing system is Phase 2 compliant, ask your vendor specifically: which software version added Phase 2 ZATCA compliance? Does it support XML UBL 2.1, CSID management, FATOORA API integration, clearance, and reporting? Has it been declared or verified compliant by ZATCA?

    • Do not confuse Phase 1 compliance with Phase 2. Many systems certified as e-invoicing compliant in 2021 have not been updated for Phase 2. The vendor’s “ZATCA compliant” badge on its website may be a Phase 1 certification. Ask explicitly for Phase 2.
    • Confirmed software compliance is not confirmed deployment compliance. A compliant software version incorrectly configured — wrong field mapping, CSID associated with the wrong unit, clearance not triggered for Tax Invoices — is not compliant in production.
    • Test with realistic invoice samples. FATOORA imposes a maximum submission size (~10MB). Invoices with large numbers of line items can approach this limit. Test with typical invoice volumes, not just minimal test cases.
    07

    Frequently Asked Questions

    Yes. A custom EGS is permissible — there is no requirement to use a commercial solution. However, it must meet all ZATCA technical requirements: XML UBL 2.1 generation, cryptographic stamping using ECDSA with a ZATCA-issued CSID, UUID and hash chain management, prohibited functionality exclusions, and full FATOORA API integration. The development, testing, and onboarding process is substantial.
    A lapsed CSID means your EGS can no longer apply a valid cryptographic stamp. All invoices generated after expiry fail FATOORA validation. Track CSID expiry dates and schedule renewal at least 30 days before expiry. If a CSID has already expired, renewal reissues a new certificate — but invoices generated during the gap are non-compliant.
    Not necessarily. If a centralised server generates and stamps invoices for all branches, that is one EGS unit requiring one CSID. If each branch generates its own stamps locally via POS terminals, each terminal is a separate unit requiring its own CSID. The distinction is whether stamping and hash-chain maintenance happens centrally or locally.
    A declared compliant solution is one where the vendor has self-certified against ZATCA’s requirements. A verified compliant solution has been independently tested by an authorised body and confirmed compliant. Both are listed on ZATCA’s website. Verified solutions carry more certainty. Ask your vendor which category applies and request the supporting test results.
    ◆ Key Takeaways
    1. “Supports e-invoicing” is not the same as “Phase 2 compliant.” Always confirm the specific Phase 2 capabilities — XML UBL 2.1, CSID management, cryptographic stamping, FATOORA API integration — with your vendor in writing, with a specific software version reference.
    2. Your EGS unit count determines your CSID count. Map your invoice generation architecture before starting onboarding. One CSID across multiple units is a compliance failure from day one.
    3. Prohibited functionalities are capability tests, not usage tests. A system that allows invoice deletion — even if no one has ever deleted one — is non-compliant. Review your system configuration against the prohibited functions list explicitly.
    4. CSIDs expire. Add expiry dates to your compliance calendar and schedule renewal at least 30 days in advance. Invoices generated after CSID expiry are non-compliant from that moment.
    5. ZATCA’s sandbox is your primary risk management tool. Test every clearance scenario, rejection and resubmission workflow, and PIH mismatch edge case before processing a single live transaction.

    Also in this series

    Tax Intelligence
    Phase 2 Integration Requirements — What Your Business Must Prepare For
    Tax Intelligence
    Clearance vs. Reporting — What’s Actually Required and When
    Tax Intelligence
    E-Invoicing Penalties — What ZATCA Charges and How to Avoid It
    Tax Intelligence
    The Complete Fatoorah Compliance Guide — Pillar Article

    Saudi E-Invoicing (Fatoorah) — 7-article series

    Continue with the full series on dariba.co

    View all articles →

    This article reflects ZATCA’s E-Invoicing Regulation (December 2020) and the Controls, Requirements, Technical Specifications and Procedural Rules Resolution (May 2023). For informational purposes only — not legal or tax advice. Confirm with zatca.gov.sa or a qualified Saudi tax advisor. dariba.co is an independent platform.

  • E-Invoice Clearance vs. Reporting in Saudi Arabia: A Plain-English Guide

    Part of Saudi E-Invoicing (Fatoorah): The Complete Series — Article 4 of 7
    01

    The Core Distinction

    Clearance applies to Tax Invoices (B2B): ZATCA must validate and stamp the invoice before it can legally be shared with the buyer. Reporting applies to Simplified Tax Invoices (B2C): the invoice is shared with the customer immediately after generation, then transmitted to FATOORA within 24 hours.

    FeatureClearance (Tax Invoice)Reporting (Simplified Invoice)
    When FATOORA is involvedBefore sharing with buyerAfter sharing with customer (within 24 hours)
    Invoice validity without FATOORA responseInvalid — cannot be sharedValid for customer immediately; reporting fulfils compliance
    ZATCA stamp appliedBy FATOORA after clearance — embedded in returned XMLBy EGS (using CSID) before sharing
    Submission format to FATOORAXML only (not PDF/A-3)XML only (not PDF/A-3)
    Format shared with buyerCleared XML or PDF/A-3 with embedded cleared XMLPrinted copy, electronic format, or any human-readable format
    Credit/debit notesTax Invoice notes go through clearanceSimplified Invoice notes go through reporting
    02

    Clearance — The Step-by-Step Process

    Your EGS generates the invoice in XML (UBL 2.1), assigns a UUID, calculates and embeds the Previous Invoice Hash (SHA-256), applies your CSID-backed cryptographic stamp, and transmits the complete XML to FATOORA via API. FATOORA runs multi-layer validation. If it passes, FATOORA applies ZATCA’s own cryptographic stamp, updates the QR code, and returns the cleared XML. You then deliver the cleared document to the buyer — as XML or as a PDF/A-3 with the cleared XML embedded.

    The Hash Chain Cannot Be Broken

    Every invoice incorporates the hash of the previous invoice — creating a tamper-evident chain. Even a rejected invoice that is never corrected or resent still occupies a position in the chain. Its hash must appear as the Previous Invoice Hash in the next invoice you generate. A system that skips rejected invoices breaks the chain — and ZATCA audits can detect the break mathematically. Confirm your EGS handles this correctly during sandbox testing.

    03

    Reporting — The 24-Hour Obligation

    Your EGS generates the invoice, assigns a UUID, embeds the Previous Invoice Hash, and applies your cryptographic stamp. The invoice is immediately shared with the customer — printed, emailed, or in any human-readable format. Within 24 hours of the invoice’s generation timestamp, the XML must be submitted to FATOORA. FATOORA validates it and returns a confirmation. If validation fails, the submission must be corrected and resubmitted before the window closes.

    Worked Example — Reporting at Scale

    A Jeddah supermarket chain generates approximately 4,500 Simplified Tax Invoices per day across three branches. Its POS system transmits invoices to FATOORA in rolling batches every two hours. By 2am, all invoices from the previous trading day have been reported and confirmed. Retry logic catches any connectivity issues automatically. The 24-hour window is met consistently through automated process design — not through manual vigilance.

    04

    Rejection Handling

    ResponseTax Invoice ActionSimplified Invoice Action
    AcceptedShare cleared invoice with buyerReporting obligation fulfilled
    Accepted with WarningsShare cleared invoice; investigate warning for future invoicesReporting fulfilled; investigate warning
    RejectedDo NOT modify original. Generate new corrected invoice with new UUID. Use rejected invoice hash as PIH in new invoice.Correct data issue; resubmit before 24-hour window expires
    No connectivityRetry every 5 min; share uncleared invoice temporarily if no response after ~5 min; retry every 15 minQueue for retry; 24-hour window still runs
    05

    What FATOORA Validates

    Validation LayerWhat It Checks
    XML schema conformanceInvoice structure matches UBL 2.1 as defined in ZATCA’s XML Implementation Standard
    Mandatory field presenceAll mandatory fields for the invoice type and phase are populated
    VAT calculation accuracyVAT amounts at line and document level are mathematically consistent
    Cryptographic stamp validityEGS-applied stamp verifiable against the registered CSID
    UUID uniquenessUUID has not been used in a previously submitted invoice
    Invoice counter sequenceCounter value is consistent with the sequence of prior invoices from that EGS unit
    Previous Invoice HashPIH matches the hash of the last accepted invoice from that EGS unit
    Seller VAT registrationSeller VAT number matches the registered taxpayer profile
    06

    When ZATCA’s Systems Are Unavailable

    Tax Invoice during FATOORA outage

    Retry clearance every five minutes. After approximately five minutes of failed attempts, you may share the uncleared invoice with the buyer as a temporary measure — ZATCA acknowledges the operational reality. Continue retrying every 15 minutes. Once clearance succeeds, provide the buyer with the cleared version. Retain detailed logs of all retry attempts and timestamps.

    Simplified Tax Invoice during FATOORA outage

    Share the invoice with the customer immediately as normal. The 24-hour reporting window continues running — it does not pause for FATOORA outages. Queue the invoice for submission and retry automatically until the report is accepted. Log all retry attempts as evidence if the deadline is missed due to a prolonged outage.

    07

    Frequently Asked Questions

    Not under normal circumstances. Clearance is a legal prerequisite — an uncleared Tax Invoice is not a valid VAT document. Only in the event of a FATOORA outage may you share an uncleared invoice temporarily, following the outage protocol. Do not make this a routine practice.
    No. Clearance confirms technical compliance with format, structure, and field requirements. It does not constitute ZATCA’s approval of the VAT treatment. If you applied the wrong VAT rate or misclassified the supply, clearance will not catch that error. ZATCA may still audit the substantive tax position of a cleared invoice.
    A missed window is a compliance violation. The invoice should still be reported — a late submission is better than none. ZATCA’s penalty framework applies. The waiver initiative (open until 30 June 2026) may cover historical missed windows, but it does not change the obligation going forward. Automated reporting with reliable retry logic is the only protection against systematic window misses.
    This is an operational risk that Phase 2 introduces and that businesses must plan for. Build clearance into your order-to-delivery workflow with enough lead time that a single rejection and resubmission does not delay the shipment. Systems that generate and submit for clearance early in the transaction cycle — not at the moment of dispatch — are operationally more resilient.
    ◆ Key Takeaways
    1. Clearance is a legal prerequisite for Tax Invoices — it must happen before the invoice leaves your system. An uncleared Tax Invoice is not a valid VAT document, regardless of content accuracy.
    2. The 24-hour reporting window for Simplified Tax Invoices is absolute — it does not reset at midnight, pause for weekends, or extend during outages. Automated reporting with fault-tolerant retry logic is the only reliable solution at any transaction volume.
    3. Rejected invoices retain their identity in the hash chain. Do not modify or drop a rejected Tax Invoice — it must remain in your system, and its hash must appear as the PIH in the next invoice you generate.
    4. Clearance confirms technical compliance — not correct VAT treatment. ZATCA can still audit the substantive tax position of any cleared invoice.
    5. Keep detailed logs of all clearance attempts, responses, and retries. Evidence of good-faith compliance during a FATOORA outage substantially changes how a missed window or temporary uncleared invoice is assessed.

    Also in this series

    Tax Intelligence
    Tax Invoice vs. Simplified Tax Invoice — Which Type Applies to Your Business?
    Tax Intelligence
    Phase 2 Integration Requirements — What Your Business Must Prepare For
    Tax Intelligence
    EGS Solution Requirements — What Your System Must Be Able to Do
    Tax Intelligence
    Fatoorah and VAT Compliance — How E-Invoicing Affects Your VAT Obligations

    Saudi E-Invoicing (Fatoorah) — 7-article series

    Continue with the full series on dariba.co

    View all articles →

    This article reflects ZATCA’s E-Invoicing Regulation (December 2020) and the Controls, Requirements, Technical Specifications and Procedural Rules Resolution (May 2023). For informational purposes only — not legal or tax advice. Confirm with zatca.gov.sa or a qualified Saudi tax advisor. dariba.co is an independent platform.

  • Tax Invoice vs. Simplified Tax Invoice in Saudi Arabia: What’s the Difference?

    Part of Saudi E-Invoicing (Fatoorah): The Complete Series — Article 3 of 7
    01

    The Core Rule — One Test, Two Invoice Types

    A Tax Invoice is issued for supplies to VAT-registered buyers (B2B and B2G). A Simplified Tax Invoice is issued for supplies to consumers and non-registered buyers (B2C). The classification flows from the nature of the transaction — not preference — and determines the Phase 2 compliance model: clearance before sharing (Tax Invoice) or reporting within 24 hours after sharing (Simplified Tax Invoice).

    FeatureTax InvoiceSimplified Tax Invoice
    Issued toVAT-registered buyers, government entitiesIndividuals, consumers, non-VAT-registered buyers
    Phase 2 compliance modelClearance — FATOORA must stamp before sharingReporting — share immediately, report within 24 hours
    Buyer VAT number requiredYes — mandatoryNo
    Buyer name and address requiredYes — mandatoryNo
    Supports buyer input tax deductionYesNo
    B2B supplies below SAR 1,000Seller may optionally issue simplified — but buyer can request Tax InvoicePermitted — buyer loses input tax recovery
    Commercial Consequence of Wrong Classification

    Issuing a Simplified Tax Invoice to a VAT-registered business customer means that buyer cannot deduct input VAT. If they claim it anyway, they face a VAT adjustment on audit. The problem compounds over months before anyone notices. Classification must be correct at system configuration stage — not fixed retrospectively.

    02

    Mandatory Field Differences — Phase 2

    The fields where the two types diverge most significantly relate to buyer identification. Phase 2 adds additional fields beyond Phase 1 — including UUID, invoice issue time (HH:mm:ss), cryptographic stamp, and Previous Invoice Hash — to both types.

    FieldTax InvoiceSimplified Tax Invoice
    Buyer nameMandatoryNot required
    Buyer VAT registration numberMandatoryNot required
    Buyer address (street, building, city)MandatoryNot required
    Invoice issue time (HH:mm:ss)MandatoryMandatory
    UUIDMandatoryMandatory
    Cryptographic stamp (EGS-applied)MandatoryMandatory
    ZATCA cryptographic stamp (after clearance)Mandatory — applied by FATOORANot applicable (reporting model)
    9-field TLV QR codeMandatoryMandatory
    Exemption reason code (zero-rated / exempt)Mandatory where applicableMandatory where applicable
    Buyer Address — A Common Data Gap

    Buyer address is mandatory on Tax Invoices in Phase 2: street address, building number, and city. Many businesses never collected or stored structured buyer address data. Collecting this from existing customers before go-live is an operational task that must be planned — not assumed. Discovery of this gap six weeks before a wave deadline is a very different problem from six months out.

    03

    Worked Example — Two Invoice Types, One Business

    Worked Example — Al Noor Medical Supplies

    Al Noor Medical Supplies Co., Jeddah, distributes to hospitals (VAT-registered, B2B) and operates a retail pharmacy for walk-in patients (B2C). For every hospital delivery, Al Noor issues a Tax Invoice — submitted for clearance before the delivery is dispatched. For every over-the-counter pharmacy sale, Al Noor issues a Simplified Tax Invoice — stamped and printed at the cash register, then reported to FATOORA in automated batches within 24 hours.

    Al Noor’s EGS must be configured to handle both workflows. The system must prompt for a buyer VAT number at transaction initiation — if one is provided, the transaction routes to the Tax Invoice workflow. If not, it routes to the Simplified Invoice workflow. Getting this classification right at configuration stage is everything; getting it wrong means 18 months of invoices requiring correction.

    04

    Credit and Debit Notes — They Follow the Original Invoice

    Credit notes and debit notes must follow the same classification as the invoice they are issued against. A credit note against a Tax Invoice is a Tax Invoice credit note — it must go through clearance. A credit note against a Simplified Tax Invoice follows the reporting model.

    Both types must reference the original invoice. The Invoice Reference Number of the original must appear in the reference fields. A credit note without a valid reference fails FATOORA validation. Where a single credit note covers multiple original invoices, a range reference is permitted.

    Most Commonly Misconfigured Feature

    Credit note handling is the most frequently misconfigured element of Phase 2 implementations. Systems that default all credit notes to the simplified reporting workflow — regardless of original invoice type — will pass Tax Invoice credit notes through reporting when they should be cleared. Test credit notes against both invoice types explicitly during sandbox testing. It will not surface in standard testing unless you specifically test for it.

    05

    Edge Cases

    Supplies below SAR 1,000 to a registered business buyer

    For B2B supplies below SAR 1,000, the seller has the option to issue a Simplified Tax Invoice. The buyer accepts this — unless they need to claim input tax, in which case they can request a Tax Invoice. The rule permits — it does not force. A business that always issues Tax Invoices for B2B transactions, including low-value sales, is fully compliant.

    Businesses serving both B2B and B2C customers

    Both workflows must be configured in the EGS. Classification should be driven by whether the buyer provides a VAT registration number — and your system should prompt for this at transaction initiation, not as an afterthought.

    Self-billed invoices

    In B2B scenarios, a buyer may issue an invoice on behalf of the supplier (self-billing). Self-billed invoices are only applicable in B2B contexts — they are always Tax Invoices subject to clearance. The invoice must carry a self-billing flag, but the format and compliance model are identical to a standard Tax Invoice.

    06

    Frequently Asked Questions

    A Tax Invoice is issued for B2B supplies to VAT-registered buyers and must be cleared by ZATCA before being shared. A Simplified Tax Invoice is issued for B2C supplies to consumers, shared immediately, and reported to FATOORA within 24 hours. The Tax Invoice supports the buyer’s input tax deduction claim; the Simplified Invoice does not.
    Generally no. Simplified Tax Invoices do not support input tax deduction for business buyers. If a VAT-registered buyer needs to claim input tax, they must receive a Tax Invoice — either proactively issued by the seller for transactions above SAR 1,000, or requested by the buyer for smaller amounts where the seller issued a simplified format.
    Issuing a Simplified Tax Invoice to a VAT-registered business customer means that buyer cannot validly deduct input VAT. The practical consequence is operational: the buyer will request a corrected Tax Invoice, requiring you to issue a credit note against the original simplified invoice and a new Tax Invoice — adding administrative complexity for every affected transaction.
    Yes. The E-Invoicing Regulation covers all taxable supplies — including zero-rated and exempt. An invoice for an exempt or zero-rated supply must carry the applicable exemption reason code from ZATCA’s approved list. Showing zero VAT without a reason code is non-compliant and will be rejected by FATOORA.
    A credit note follows the compliance model of the original invoice it is issued against. A credit note against a Tax Invoice must go through clearance. A credit note against a Simplified Tax Invoice follows the 24-hour reporting model. Configure this specifically in your EGS — it will not default correctly without explicit setup.
    ◆ Key Takeaways
    1. Invoice type is determined by buyer status — VAT-registered business gets a Tax Invoice; consumer or unregistered buyer gets a Simplified Tax Invoice. This is a tax rule, not a design preference.
    2. A Simplified Tax Invoice does not support a business buyer’s input tax deduction. Issuing simplified invoices to registered business customers silently invalidates their VAT deductions — a problem that compounds over months.
    3. Credit notes follow the type of the original invoice. Configure this explicitly in your EGS and test it — it does not default correctly without specific setup.
    4. For B2B transactions below SAR 1,000, sellers may issue simplified invoices — but buyers can request a Tax Invoice to support their input tax claim.
    5. Getting invoice type classification right at system configuration costs a few hours. Fixing it retrospectively — reissuing invoices, handling VAT adjustments, explaining to customers — costs significantly more.

    Also in this series

    Tax Intelligence
    Clearance vs. Reporting — What’s Actually Required and When
    Tax Intelligence
    Phase 2 Integration Requirements — What Your Business Must Prepare For
    Tax Intelligence
    Fatoorah and VAT Compliance — How E-Invoicing Affects Your VAT Obligations
    Tax Intelligence
    E-Invoicing Penalties — What ZATCA Charges and How to Avoid It

    Saudi E-Invoicing (Fatoorah) — 7-article series

    Continue with the full series on dariba.co

    View all articles →

    This article reflects ZATCA’s E-Invoicing Regulation (December 2020) and the Controls, Requirements, Technical Specifications and Procedural Rules Resolution (May 2023). For informational purposes only — not legal or tax advice. Confirm with zatca.gov.sa or a qualified Saudi tax advisor. dariba.co is an independent platform.

  • Saudi E-Invoicing Phase 2: Integration Requirements and What to Expect

    Part of Saudi E-Invoicing (Fatoorah): The Complete Series — Article 2 of 7
    01

    What Phase 2 Adds — The Operational Shift

    Phase 2 (Integration Phase) adds mandatory real-time connectivity between your invoicing system and ZATCA’s FATOORA platform. For Tax Invoices (B2B), clearance by ZATCA is a legal prerequisite before the invoice can be shared with the buyer. For Simplified Tax Invoices (B2C), reporting to FATOORA must occur within 24 hours of generation. Phase 1 asked: does your system generate a valid invoice? Phase 2 asks: does your system connect to ours, in real time, for every transaction?

    RequirementPhase 1Phase 2
    Invoice formatAny electronic formatXML (UBL 2.1) or PDF/A-3 with embedded XML
    Cryptographic stampNot requiredApplied by your EGS using ZATCA-issued CSID
    UUID per invoiceNot requiredMandatory
    Previous Invoice HashNot requiredMandatory — links each invoice to the prior in sequence
    QR code fields4 fields (simplified only)9 fields TLV base64 (both invoice types)
    FATOORA API connectionNot requiredMandatory
    Tax Invoice clearanceNot requiredMust occur before sharing with buyer
    Simplified Invoice reportingNot requiredWithin 24 hours of generation
    EGS device registration (CSID)Not requiredMandatory — one per EGS unit
    02

    The Wave System — How Your Notification Works

    ZATCA rolls out Phase 2 in waves, with each wave targeting taxpayers in a specific revenue band determined by their highest VAT-taxable annual revenue in any designated reference year. Waves have expanded from SAR 3 billion at launch (Wave 1, January 2023) to SAR 375,000 at Wave 24 (deadline June 2026). ZATCA is required to notify businesses at least six months before their integration deadline.

    The wave criteria are public. You do not need to wait for a personal notification to know whether you are in scope. If your revenue exceeds SAR 375,000 in any of 2022, 2023, or 2024, Wave 24 applies at minimum. The clock runs from the published deadline — not from the date you receive a notification.

    Check All Reference Years

    Your wave is based on your highest revenue in any of the applicable reference years — not your most recent year. A business with SAR 2 million revenue in 2022 but only SAR 800,000 in 2024 is still captured by the 2022 figure. Always check across the full reference period before concluding which wave applies.

    03

    Onboarding Your System to FATOORA

    Before a single Phase 2 invoice can be cleared or reported, your EGS must be registered with FATOORA and issued a Cryptographic Stamp Identifier (CSID). The process requires accessing the FATOORA portal with ERAD credentials, generating an OTP for each EGS unit, entering the OTP into the EGS, receiving the CSID, accepting ZATCA’s subscriber agreement, and testing in ZATCA’s sandbox before going live.

    One CSID Per EGS Unit — Not Per Business

    A business with 20 POS terminals needs 20 CSIDs. A central billing server plus a separate POS system needs 2. Onboarding one unit and applying its CSID to multiple systems is a compliance failure. Invoices stamped by an incorrectly associated unit are invalid. Map your EGS units before starting onboarding and confirm the count with your IT team.

    04

    Clearance for Tax Invoices — Step by Step

    Your EGS generates the invoice in XML, applies your cryptographic stamp, assigns a UUID, embeds the Previous Invoice Hash, and transmits to FATOORA via API. FATOORA validates the XML schema, field completeness, VAT mathematical accuracy, stamp validity, and referential integrity. If everything passes, FATOORA applies its own stamp and returns the cleared XML. You then share the cleared document — as XML or PDF/A-3 with embedded XML — with the buyer.

    FATOORA ResponseMeaningAction Required
    AcceptedInvoice fully cleared — ZATCA stamp appliedShare cleared invoice with buyer
    Accepted with WarningsCleared but minor issues notedShare invoice; investigate warning for future invoices
    RejectedMandatory field errors, schema failures, VAT miscalculationsDo NOT modify original. Generate new invoice with new UUID. Use rejected invoice hash as PIH in new invoice.
    No connectivityFATOORA unreachableRetry every 5 min; after ~5 min share uncleared invoice temporarily; retry every 15 min until cleared
    05

    Reporting for Simplified Tax Invoices

    Your EGS generates the invoice, applies your cryptographic stamp, and you share it with the customer immediately — before any interaction with FATOORA. All Simplified Tax Invoices must then be transmitted to FATOORA within 24 hours of generation. The window is measured from the timestamp on each individual invoice and does not reset at midnight, extend over Eid, or pause for connectivity issues.

    What 24 Hours Actually Means

    An invoice generated at 11:45pm must be reported by 11:45pm the following day. Your reporting system must run continuously and handle retry logic automatically — not depend on staff manually submitting batches. For high-volume B2C businesses, automated batch reporting running throughout the day is the only sustainable approach.

    06

    Common Phase 2 Implementation Mistakes

    • Treating Phase 2 as an IT project only. Both IT and finance must be engaged. The invoice type classification, VAT field mapping, and rejection handling all have tax consequences that IT teams cannot assess alone, and compliance failures that finance teams cannot detect without access to FATOORA data.
    • Not testing in the ZATCA sandbox before go-live. ZATCA provides a full sandbox environment and SDK. Skipping this guarantees configuration errors on live transactions. Discover them in sandbox, not in production.
    • Missing the OTP window during onboarding. The OTP generated in the FATOORA portal has a short validity window. If it expires before entry into the EGS, the entire onboarding restarts. Have your IT team ready at the moment the OTP is generated.
    • Underestimating Phase 2 field requirements. Buyer address fields — street, building number, city — are mandatory on Tax Invoices. Many businesses have never collected or stored this data. Identifying the gap six weeks before go-live is a very different problem from six months out.
    • No retry logic for clearance failures. FATOORA returns rejections, warnings, and connectivity failures. Your system must handle each programmatically — logging rejections, queuing retries, and alerting the finance team. Silent failure is non-compliance accumulating with every transaction.
    07

    Frequently Asked Questions

    ZATCA is required to notify businesses at least six months before their integration deadline. However, the wave criteria are published publicly — you do not need to wait for a notification to know whether you are in scope. Check your highest VAT-taxable revenue across 2022, 2023, and 2024 against the published wave thresholds.
    It depends on whether your ERP vendor has added Phase 2 compliance features — specifically XML invoice generation (UBL 2.1), cryptographic stamping via CSID, UUID generation, Previous Invoice Hash linking, and a FATOORA API integration module. Ask your vendor for written confirmation of Phase 2 compliance with a specific release version reference. “We support e-invoicing” may refer only to Phase 1.
    A rejected Tax Invoice must not be modified. It retains its own UUID and counter position. A new invoice with corrected content must be generated with a new UUID and the hash of the rejected invoice as its Previous Invoice Hash. Your EGS must handle this correctly — a system that drops rejected invoices from the hash chain breaks the sequential integrity ZATCA audits can verify.
    You need a separate CSID for each EGS unit that independently generates and stamps invoices. Whether that maps to one per branch or one per terminal depends on your architecture. A centralised server generating stamps for all branches is one unit. Individual POS terminals generating their own stamps are separate units.
    The sandbox is a test environment that mirrors the live FATOORA platform. Use of the sandbox is not formally mandated — but going live without testing is a significant operational risk. A clearance rejection rate of even 5% on live transactions means compliance failures accumulating across hundreds of invoices while you debug the issue. Sandbox testing before go-live is standard practice for any serious implementation.
    ◆ Key Takeaways
    1. Phase 2 is a real-time infrastructure obligation. Your invoicing system must be connected to FATOORA via API, with live clearance for Tax Invoices and 24-hour automated reporting for Simplified Tax Invoices.
    2. Six months’ notice from ZATCA is the minimum. ERP configuration, vendor engagement, data gap remediation, sandbox testing, and CSID onboarding all take time. Treat the notification as the start of an urgent project, not confirmation of an eventual one.
    3. Each EGS unit needs its own CSID. Map your units before starting onboarding. A CSID applied to the wrong unit or shared across multiple units invalidates every invoice those units produce.
    4. Clearance is a prerequisite for Tax Invoices — not a background process. A Tax Invoice shared before FATOORA has cleared it is legally invalid for VAT purposes.
    5. The 24-hour reporting window for Simplified Tax Invoices does not pause for outages, weekends, or public holidays. Automated, fault-tolerant reporting with retry logic is the only way to reliably meet this obligation at meaningful transaction volumes.

    Also in this series

    Tax Intelligence
    Phase 1 Generation Phase Requirements — What Saudi Businesses Were Required to Do
    Tax Intelligence
    Clearance vs. Reporting — What’s Actually Required and When
    Tax Intelligence
    EGS Solution Requirements — What Your System Must Be Able to Do
    Tax Intelligence
    E-Invoicing Penalties — What ZATCA Charges and How to Avoid It

    Saudi E-Invoicing (Fatoorah) — 7-article series

    Continue with the full series on dariba.co

    View all articles →

    This article reflects ZATCA’s E-Invoicing Regulation (December 2020) and the Controls, Requirements, Technical Specifications and Procedural Rules Resolution (May 2023). It is for informational purposes only and does not constitute legal or tax advice. Confirm the current position at zatca.gov.sa or with a qualified Saudi tax advisor. dariba.co is an independent platform with no consulting relationships.

  • Saudi E-Invoicing Phase 1: Generation Phase Requirements Explained

    Part of Saudi E-Invoicing (Fatoorah): The Complete Series — Article 1 of 7
    01

    What Phase 1 Actually Required

    Phase 1 (Generation Phase), effective 4 December 2021, required all VAT-registered resident taxpayers to generate invoices electronically through a compliant E-Invoice Generation Solution (EGS). The key word is “generation” — Phase 1 had nothing to do with ZATCA’s systems. The obligation was entirely on the taxpayer’s side: use a compliant system to produce, store, and present on demand a valid electronic invoice.

    Critically, Phase 1 did not mandate a specific invoice format. XML was not required. PDF was acceptable. Any electronic format was permitted — as long as it was produced by a compliant EGS. The format restriction came with Phase 2. What Phase 1 did mandate, from day one, was the full set of tamper-proofing and prohibited functionality rules.

    RequirementPhase 1 Position
    Electronic generationMandatory from 4 Dec 2021
    Invoice format (XML, PDF etc.)No format mandated — any electronic format
    QR codeRequired on Simplified Tax Invoices (4-field basic format)
    Cryptographic stamp / UUIDNot required
    FATOORA platform integrationNot required
    Tamper-proofing and prohibited functionalitiesMandatory from 4 Dec 2021
    Record keeping and archivalMandatory — ongoing (6-year retention)
    02

    Mandatory Fields — Tax Invoice vs. Simplified Tax Invoice

    Both invoice types carry mandatory fields defined in Article 53 of the VAT Implementing Regulation and Annex 2 of the E-Invoicing Resolution. The Tax Invoice (B2B) carries more fields — reflecting the buyer’s need for the document to support an input tax deduction claim.

    FieldTax InvoiceSimplified Tax Invoice
    Invoice type descriptionMandatoryMandatory
    Invoice reference number (sequential)MandatoryMandatory
    Invoice issue dateMandatoryMandatory
    Seller name and VAT registration numberMandatoryMandatory
    Seller addressMandatoryMandatory
    Buyer nameMandatoryNot required
    Buyer VAT registration numberMandatoryNot required
    Buyer addressMandatoryNot required
    Line items with VAT per line and totalsMandatoryMandatory
    QR codeNot required in Phase 1Mandatory (4-field)
    Exemption reason code (where applicable)Mandatory for zero-rated/exempt suppliesMandatory for zero-rated/exempt supplies
    Exemption Reason Codes Are Not Optional

    An invoice for a zero-rated or exempt supply that simply shows “VAT: SAR 0” without an exemption reason code from ZATCA’s approved list is non-compliant — even if the zero-rating treatment is correct. This is one of the most consistently missed Phase 1 requirements.

    03

    What “Electronically Generated” Means

    ZATCA’s regulation is explicit: a paper invoice converted to an electronic format through copying, scanning, or any other method is not a compliant electronic invoice. A PDF exported from Microsoft Word or Excel is not compliant. A handwritten invoice photographed and emailed is not compliant.

    A compliant Phase 1 EGS is a purpose-built electronic system — software that generates the invoice natively in a structured digital format, with the mandatory tamper-proofing features active. The distinction is between a document-creation tool and an invoice-generating system. ZATCA distinguishes between these categories, and the distinction is tested on audit.

    Worked Example

    Al-Rashid Consulting Co. issued invoices in 2022 using a Word document template saved as PDF and emailed to clients. All mandatory fields were present, VAT was correct at 15%. On a 2024 ZATCA audit, the auditor identifies every invoice as non-compliant: the generating “system” was a word processor with no tamper-proofing, no session logging, no sequential counter, and no prohibition on deletion. Every invoice from that period is technically an invalid VAT document — regardless of content accuracy.

    04

    Prohibited Functionalities — From Phase 1 Go-Live

    The E-Invoicing Resolution (Section 5.6) specifies functionalities that no compliant EGS may enable — effective from 4 December 2021. A system that permits any of the following is non-compliant, regardless of how well-formatted its invoices are.

    Prohibited FunctionWhat This Means in Practice
    Anonymous accessSystem must require unique login credentials — no shared logins, no guest access
    Default password operationFactory passwords must be replaced on first use — system must enforce password reset
    Absence of user session managementSystem must log all user activities from login through invoice generation — a full audit trail
    Invoice alteration or deletionOnce generated, invoices cannot be modified or deleted. Cancellations must be via credit note
    Log modification or deletionSystem activity logs must be immutable — no staff member can alter or erase them
    Inaccurate timestampsUsers cannot change the system date to backdate or forward-date invoices
    Non-sequential log generationAll log entries must be time-stamped and chained — making sequence manipulation detectable
    Invoice counter resetThe sequential counter must increment continuously and cannot be reset, even at year-end
    Capability Test, Not Usage Test

    The existence of a prohibited functionality in your system makes every invoice it generates non-compliant — regardless of whether that functionality was ever used. A system that allows invoice deletion but where no invoice has ever been deleted is still non-compliant. ZATCA’s test is capability, not usage history.

    05

    Record-Keeping — The Obligation That Does Not Expire

    Phase 1 invoices must be archived in accordance with VAT Law requirements. The standard retention period is six years from the end of the tax period to which they relate. Invoices from December 2021 must be retained until at least 2027. They must be accessible to ZATCA at any point in time on request.

    Storage can be on-premises in Saudi Arabia or in a cloud environment — both are permissible. What matters is that the archive is complete, searchable, and can be produced to ZATCA auditors in a workable format. If your old system has since been decommissioned, the archived data must still be producible. “We upgraded our ERP” is not an answer to a record production request.

    06

    Common Phase 1 Compliance Mistakes

    • Using a PDF-from-Word or Excel workaround. The most widespread Phase 1 mistake. The generating tool was not an EGS — it had no tamper-proofing, no session logging, no sequential counter. Every invoice produced this way is non-compliant.
    • Missing the QR code on Simplified Tax Invoices. Phase 1 required a QR code on B2C simplified invoices from 4 December 2021. Businesses that issued simplified invoices without a QR code — or with one containing incorrect data — have non-compliant records.
    • Shared login credentials. Multiple staff members logging in under a single shared account violates the session management requirement. ZATCA cannot identify which individual generated or modified any given record. The system is non-compliant from first use.
    • Scanning paper invoices as a transition measure. A paper invoice converted to electronic format through scanning is explicitly not a compliant e-invoice, regardless of what happens to it afterwards.
    • Failing to preserve the archive after a system upgrade. Migrating to a new ERP without carrying across Phase 1 invoice data — or storing it in a format no longer accessible — creates an archive gap. The original non-compliance may have been zero, but the failure to preserve the record creates a new and separate violation.
    07

    Frequently Asked Questions

    Yes. Phase 1 compliance obligations are ongoing. The record-keeping requirement means ZATCA can audit your Phase 1 invoices for up to six years after the relevant tax period. Non-compliance discovered on audit — through a system review or invoice validity check — can result in penalty assessments regardless of Phase 2 status.
    Yes. Penalties under the VAT Law apply to violations within the assessment periods ZATCA can examine. ZATCA’s penalty waiver initiative (open until 30 June 2026) offers a window to correct historical non-compliance before enforcement action becomes the only option.
    It depends on the software, not the output format. A PDF generated by a properly configured, ZATCA-compliant accounting system is valid in Phase 1 — the format was unrestricted. A PDF generated by a word processor or non-compliant application is not valid. The key question is whether the generating system had the required tamper-proofing features and all prohibited functionalities disabled. Review the system against ZATCA’s Detailed Guidelines, Section 5.6.
    Switching systems does not erase the archive obligation on historical invoices. You must ensure the data from your old system is preserved, accessible, and can be produced to ZATCA on request. If the old system’s data was not transferred or archived in an accessible format, that gap needs to be addressed — ideally before a ZATCA audit reveals it.
    ZATCA’s penalty waiver initiative runs until 30 June 2026 and covers historical violations including Phase 1 gaps. It does not automatically resolve the underlying non-compliance — but it offers a window to correct the position before enforcement begins. Businesses with known Phase 1 gaps should seek professional advice on using this window effectively.
    ◆ Key Takeaways
    1. Phase 1 required electronic generation through a compliant EGS from 4 December 2021. No specific format was mandated, no FATOORA integration required — but the tamper-proofing and prohibited functionality rules applied in full from day one.
    2. A PDF from Word, a scanned paper invoice, or an Excel-generated document is not a compliant Phase 1 e-invoice. The test is the system, not the format of the output file.
    3. Simplified Tax Invoices required a QR code from Phase 1. Tax Invoices did not. Any B2C business that issued simplified invoices without a QR code from December 2021 has a Phase 1 compliance gap.
    4. The record-keeping obligation runs for six years. ZATCA auditors can examine Phase 1 records today. The archive must be preserved even after a system upgrade — failure to produce records on demand is a separate violation.
    5. ZATCA’s penalty waiver initiative (open until 30 June 2026) is the practical route for businesses with known Phase 1 gaps to regularise their position before enforcement action.

    Saudi E-Invoicing (Fatoorah) — 7-article series

    Continue with the full series on dariba.co

    View all articles →

    Also in this series

    Tax Intelligence
    Phase 2 Integration Requirements — What Your Business Must Actually Prepare For
    Tax Intelligence
    Tax Invoice vs. Simplified Tax Invoice — Which Type Applies to Your Business?
    Tax Intelligence
    E-Invoicing Penalties — What ZATCA Charges and How to Avoid It
    Tax Intelligence
    Fatoorah and VAT Compliance — How E-Invoicing Fits Into Your VAT Obligations

    This article reflects ZATCA’s E-Invoicing Regulation (December 2020) and the Controls, Requirements, Technical Specifications and Procedural Rules Resolution (May 2023). It is for informational purposes only and does not constitute legal or tax advice. Confirm the current position at zatca.gov.sa or with a qualified Saudi tax advisor. dariba.co is an independent platform with no consulting relationships.

  • Saudi E-Invoicing (Fatoorah): The Complete Business Compliance Guide

    Pillar article — Saudi E-Invoicing (Fatoorah): The Complete Series — 7 deep-dive articles below
    01

    What Is Fatoorah?

    Fatoorah is Saudi Arabia’s mandatory electronic invoicing system, introduced by ZATCA under the E-Invoicing Regulation issued in December 2020. It requires all VAT-registered resident taxpayers to generate, store, and — from Phase 2 onwards — transmit invoices electronically through a ZATCA-compliant system. The regulation covers Tax Invoices (B2B), Simplified Tax Invoices (B2C), and their associated credit and debit notes.

    The name simply means “invoice” in Arabic. But behind it sits a compliance framework far more demanding than the word suggests. Fatoorah is not about producing a digital PDF instead of a paper document — it mandates specific XML formats, mandatory data fields, cryptographic stamps (tamper-evident digital seals), QR codes, and in Phase 2, real-time connectivity between your invoicing system and ZATCA’s FATOORA platform.

    Legal Basis

    The E-Invoicing Regulation was issued by ZATCA’s Board of Governors on 4 December 2020. The implementation rules are set out in the Controls, Requirements, Technical Specifications and Procedural Rules Resolution (last updated May 2023). The regulation is read alongside the VAT Law and VAT Implementing Regulation — a non-compliant e-invoice is not a valid tax invoice and cannot support a buyer’s input VAT deduction.

    02

    Who Must Comply

    The E-Invoicing Regulation applies to all resident taxable persons registered for VAT in Saudi Arabia, and to any third party issuing invoices on behalf of a resident taxable person. There are no industry or sector exemptions. Non-resident taxpayers without a Saudi establishment are outside scope.

    Taxpayer CategoryPhase 1Phase 2
    Resident VAT-registered taxpayersYes — since Dec 2021Yes — wave-based rollout
    Third parties billing on behalf of a resident taxpayerYesYes
    Non-resident taxpayersExemptExempt
    Businesses making only exempt suppliesLimited — in-scope for taxable transactionsLimited — in-scope for taxable transactions

    If your business is VAT-registered, Fatoorah applies — there is no opt-out and no size exemption for Phase 1. The only variable is timing: which wave determines your Phase 2 integration deadline.

    03

    Phase 1 vs Phase 2 — What Each Requires

    Phase 1 (Generation Phase), effective 4 December 2021, required all VAT-registered taxpayers to switch from paper or unstructured digital invoices to electronically generated invoices produced by a compliant EGS. No specific format was mandated. No connection to ZATCA’s systems was required. But the tamper-proofing rules applied in full from day one — no invoice deletion, sequential counters, session logging, unique login credentials.

    Phase 2 (Integration Phase), rolling out in waves from January 2023, requires real-time API connectivity between your invoicing system and ZATCA’s FATOORA platform. Tax Invoices (B2B) must be cleared by FATOORA before being shared with the buyer. Simplified Tax Invoices (B2C) are shared immediately and reported to FATOORA within 24 hours. Format is now mandatory XML (UBL 2.1) or PDF/A-3 with embedded XML.

    RequirementPhase 1Phase 2
    Invoice formatAny electronic formatXML or PDF/A-3 with embedded XML
    Cryptographic stampNot requiredMandatory — applied by EGS using CSID
    UUID per invoiceNot requiredMandatory
    FATOORA API connectionNot requiredMandatory
    Tax Invoice clearanceNot requiredRequired before sharing with buyer
    Simplified Invoice reportingNot requiredWithin 24 hours of issuance
    QR codeRequired on simplified invoices (4 fields)Required on both types (9 fields)
    Critical Distinction

    Many businesses believe they are “Phase 2 compliant” because their accounting software generates well-formatted invoices. Compliance is not determined by how the invoice looks — it is determined by whether the system is onboarded to FATOORA with a valid Cryptographic Stamp Identifier and whether Tax Invoices are being cleared in real time. A formatted XML invoice that never reaches FATOORA is not compliant.

    04

    Phase 2 Wave Timeline — All 24 Waves

    ZATCA rolls out Phase 2 in waves, each targeting taxpayers in a specific revenue band. The rollout began in January 2023 at the SAR 3 billion threshold and has progressively expanded. Wave 24, announced September 2025, brings the threshold down to SAR 375,000 — bringing thousands of SMEs into mandatory scope for the first time. ZATCA must notify businesses at least six months before their integration deadline.

    WaveRevenue Threshold (VAT-taxable)Reference PeriodDeadline
    Wave 1Above SAR 3 billion20211 Jan 2023
    Wave 2SAR 500M – SAR 3B20211 Jul 2023
    Wave 3SAR 250M – SAR 500M20211 Oct 2023
    Wave 4SAR 150M – SAR 250M20211 Nov 2023
    Wave 5SAR 100M – SAR 150M20211 Dec 2023
    Wave 6SAR 70M – SAR 100M2021 or 20221 Jan 2024
    Wave 7SAR 50M – SAR 70M2021 or 20221 Feb 2024
    Wave 8SAR 40M – SAR 50M2021 or 20221 Mar 2024
    Wave 9SAR 30M – SAR 40M2022 or 20231 Jun 2024
    Wave 10SAR 25M – SAR 30M2022 or 20231 Oct 2024
    Wave 11SAR 15M – SAR 25M2022 or 20231 Nov 2024 – 31 Jan 2025
    Wave 12SAR 10M – SAR 15M2022 or 20231 Dec 2024
    Wave 13SAR 7M – SAR 10M2022 or 20231 Jan 2025 – 31 Mar 2025
    Wave 14SAR 5M – SAR 7M2022 or 20231 Feb 2025
    Waves 15–22SAR 1M – SAR 5M2022, 2023, or 2024Apr 2025 – Dec 2025
    Wave 23SAR 750K – SAR 1M2022, 2023, or 202431 Mar 2026
    Wave 24SAR 375K – SAR 750K2022, 2023, or 202430 Jun 2026
    How Your Wave Is Determined

    Your wave is based on your highest VAT-taxable revenue in any of the listed reference years — not your most recent year. If your revenue was SAR 900,000 in 2022 but fell to SAR 500,000 in 2024, you still fall within Wave 23 (SAR 750,000 threshold) based on the 2022 figure. Always check across all reference years before concluding you are outside a particular wave’s scope.

    Penalty Waiver — Extended to 30 June 2026

    ZATCA’s “Initiative to Cancel Fines and Exempt Taxpayers from Penalties” has been extended until 30 June 2026. This window covers historical e-invoicing violations. It does not remove the underlying compliance obligation — but it is a time-limited opportunity to correct past gaps without financial penalty.

    05

    Tax Invoice vs. Simplified Tax Invoice

    Every transaction requires either a Tax Invoice or a Simplified Tax Invoice. The classification flows from the nature of the transaction — not preference — and determines the Phase 2 compliance model for that invoice.

    FeatureTax InvoiceSimplified Tax Invoice
    Issued toVAT-registered buyers, government entities (B2B/B2G)Consumers, non-registered buyers (B2C)
    Phase 2 modelClearance — FATOORA must stamp before sharing with buyerReporting — share immediately, report within 24 hours
    Buyer VAT number requiredYesNo
    Supports buyer input tax deductionYesNo
    B2B sales below SAR 1,000Optional — seller may issue simplified, but buyer can request Tax InvoicePermitted — but buyer loses input tax recovery

    Credit notes and debit notes follow the type of the original invoice they are issued against. A credit note against a Tax Invoice must go through clearance. A credit note against a Simplified Tax Invoice follows the reporting model.

    06

    Clearance and Reporting — How the Mechanics Work

    Clearance (Tax Invoices): Your EGS generates the invoice in XML, applies your cryptographic stamp using your CSID, assigns a UUID and Previous Invoice Hash, then transmits to FATOORA via API. FATOORA validates the invoice, applies ZATCA’s stamp, and returns the cleared XML. You then share the cleared document with the buyer. An uncleared Tax Invoice is legally invalid — the buyer cannot claim input tax on it.

    Reporting (Simplified Tax Invoices): Your EGS generates and stamps the invoice, you share it with the customer immediately, then transmit the XML to FATOORA within 24 hours. The 24-hour window is absolute — it does not pause for weekends, public holidays, or connectivity issues. Automated reporting with retry logic is the only reliable solution at any meaningful transaction volume.

    What FATOORA Validates

    FATOORA validates XML schema conformance, presence of all mandatory fields, mathematical VAT accuracy, cryptographic stamp validity, UUID uniqueness, invoice counter sequence, and the Previous Invoice Hash linkage. Every layer must pass before clearance or acceptance.

    07

    EGS Requirements — What Your System Must Do

    Your E-Invoice Generation Solution must generate XML invoices in UBL 2.1, assign a UUID to every invoice, apply a cryptographic stamp using ECDSA with your CSID private key, embed the Previous Invoice Hash, generate a 9-field TLV QR code, and connect to FATOORA via API. It must also exclude all prohibited functionalities.

    Prohibited functionalities (active from Phase 1): anonymous or default-password access, invoice deletion or alteration after generation, log modification, inaccurate timestamps, invoice counter reset, multiple invoice sequences from one unit, and export of the cryptographic stamp private key.

    Onboarding requires accessing the FATOORA portal, generating an OTP per EGS unit, entering it in your system to receive a CSID, and testing in ZATCA’s sandbox before going live. A CSID is required per unit — not per business. A business with 10 POS terminals needs 10 CSIDs.

    08

    Option for Very Small Businesses: The ZATCA Online Portal

    ZATCA has announced an important accommodation for businesses issuing fewer than 1,000 invoices per year: these taxpayers can generate e-invoices directly through ZATCA’s own online Fatoora portal — without integrating their internal ERP or billing system with the platform.

    Under this route, the taxpayer logs into the FATOORA portal using ERAD credentials and generates invoices manually through the portal interface. ZATCA’s system handles XML generation, cryptographic stamping, UUID assignment, clearance, and reporting within the portal environment. The taxpayer downloads the cleared invoice and shares it with the buyer.

    Practical Limitations

    The portal route is a compliance-grade solution, not an operational efficiency tool. At 900 invoices per year — roughly 17 per week — it is workable but requires reliable internet access at the time of invoice generation. Businesses approaching the 1,000-invoice threshold should plan an EGS integration before they cross it rather than retrofitting under pressure. Verify current eligibility criteria with ZATCA’s official guidance, as specifics may be refined as the portal option rolls out.

    09

    Common Compliance Mistakes

    • Treating Phase 1 as finished business. ZATCA auditors examine historical records going back to December 2021. Non-compliant Phase 1 invoices — generated by a Word template, produced by a system with prohibited functionalities, missing QR codes on simplified invoices — are invalid VAT documents. The exposure has not expired.
    • Confusing “compliant software” with compliant deployment. A software version that supports Phase 2 is not compliant unless it is correctly configured, every EGS unit is onboarded with its own CSID, and clearance/reporting are actually occurring. Software compliance and deployment compliance are different things.
    • Not onboarding every EGS unit. One CSID per business is a common misconception. One CSID per unit is the requirement. Invoices stamped with the wrong or absent CSID are non-compliant — regardless of their content.
    • Sharing Tax Invoices before clearance. A workflow that dispatches the invoice on generation — before the clearance response is received — is issuing legally invalid VAT documents on every B2B transaction. This is the single most commercially damaging error because it also puts your buyer’s input tax deduction at risk.
    • Missing the 24-hour reporting window. Manual batch reporting that depends on staff availability will miss this window systematically over weekends, public holidays, and holidays. Automated reporting is not optional for any meaningful B2C volume.
    10

    Penalties and Enforcement

    E-invoicing penalties are applied under the VAT Law framework, with violation classifications set by ZATCA Board resolutions. The key principle: penalties accumulate across assessment periods. A business that fails to integrate with FATOORA is not facing a single fine — it faces exposure for each period of continued non-compliance.

    ViolationPenalty Range
    Failure to issue invoices through a compliant EGSSAR 5,000 – SAR 50,000
    Using an EGS with prohibited functionalitiesSAR 5,000 – SAR 50,000
    Failure to integrate with FATOORA by wave deadlineSAR 5,000 – SAR 50,000
    Sharing a Tax Invoice before clearanceSAR 1,000 – SAR 10,000
    Failure to report Simplified Tax Invoices within 24 hoursSAR 1,000 – SAR 10,000
    Failure to maintain e-invoice records as requiredSAR 10,000 – SAR 50,000

    ZATCA processed over 8.2 billion e-invoices in 2025 — a 64% increase from 2024. The data flowing through FATOORA gives ZATCA near-real-time visibility into which businesses are issuing invoices, at what volumes, and whether those invoices are passing clearance. The ability to detect non-compliance without a field audit has never been stronger.

    11

    Frequently Asked Questions

    Fatoorah is Saudi Arabia’s mandatory e-invoicing system, introduced by ZATCA in December 2020. It requires all VAT-registered resident taxpayers to generate, store, and — in Phase 2 — transmit invoices electronically through a compliant system connected to ZATCA’s FATOORA platform. A non-compliant invoice is not a valid VAT document, meaning buyers cannot claim input tax on it.
    If your business is VAT-registered and resident in Saudi Arabia, Fatoorah applies regardless of size. Phase 1 has applied to all VAT-registered taxpayers since December 2021. Phase 2 is rolling out in waves based on annual revenue, with Wave 24 (deadline 30 June 2026) covering businesses with VAT-taxable revenue above SAR 375,000 in any of 2022, 2023, or 2024.
    Your wave is determined by your highest VAT-taxable annual revenue in any of the applicable reference years — typically 2022, 2023, or 2024 for recent waves. Check your revenue across all three reference years. ZATCA will notify you at least six months before your integration deadline. The wave criteria are public — you do not need to wait for a notification to know whether you are in scope.
    Clearance is the process by which FATOORA validates and stamps a Tax Invoice before it can legally be shared with the buyer. An uncleared Tax Invoice is not a valid VAT document — the buyer cannot deduct input tax on it. Clearance must happen before the invoice leaves your system, not as a background process after delivery. This is a workflow requirement, not just a technical one.
    ZATCA has introduced an option for businesses issuing fewer than 1,000 invoices per year to generate e-invoices directly through the ZATCA online Fatoora portal, without integrating their internal systems. ZATCA handles XML generation, cryptographic stamping, and clearance within the portal environment. Verify current eligibility criteria with ZATCA’s official guidance, as the details may be refined as the option is rolled out.
    A CSID is a digital certificate issued by ZATCA to each EGS unit — a specific invoicing system, cash register, or billing server. It enables that unit to apply a valid cryptographic stamp. Without a CSID, the unit cannot produce legally valid Phase 2 invoices. A CSID is required per EGS unit, not per business — a company with multiple POS terminals needs one CSID per terminal.
    Penalties range from SAR 1,000 for specific invoice-level violations (such as missing the 24-hour reporting window) to SAR 50,000 for systematic non-compliance such as failing to integrate with FATOORA or using a non-compliant EGS. Penalties accumulate across assessment periods. ZATCA’s penalty waiver initiative (open until 30 June 2026) offers a time-limited window to correct historical gaps without financial penalty.
    Yes. The E-Invoicing Regulation covers all taxable supplies — including zero-rated and exempt. Invoices for exempt or zero-rated supplies must carry the appropriate reason code from ZATCA’s approved list. Showing zero VAT without a reason code is non-compliant and will be rejected by FATOORA.
    ◆ Key Takeaways
    1. Fatoorah is a tax compliance obligation managed through technology — not an IT project with tax implications. A non-compliant e-invoice is an invalid VAT document. The stakes go well beyond a technical checklist.
    2. Phase 1 compliance is not a closed chapter. ZATCA can examine records back to December 2021. Businesses with Phase 1 gaps carry live audit exposure, and the penalty waiver window (open until 30 June 2026) is the practical route to resolve it.
    3. Wave 24 (deadline 30 June 2026) covers businesses with VAT-taxable revenue above SAR 375,000 in any of 2022, 2023, or 2024. The threshold has expanded significantly. Check all reference years before concluding you are out of scope.
    4. ZATCA has introduced a portal-based option for businesses issuing fewer than 1,000 invoices per year — allowing invoice generation directly in the Fatoora platform without ERP integration. Verify eligibility criteria with ZATCA’s official guidance.
    5. Clearance is a prerequisite for Tax Invoices, not a background step. A Tax Invoice that reaches your buyer before FATOORA has cleared it is legally invalid. Configure your workflow so clearance completes before delivery — not after.
    6. Each EGS unit requires its own CSID. Map your units before onboarding. A shared or missing CSID makes every invoice that unit produces non-compliant from day one of Phase 2.
    7. With 8.2 billion invoices processed in 2025 alone, ZATCA’s ability to detect non-compliance through FATOORA data is near-real-time. The question is not whether gaps will be found — it is when enforcement action follows.

    Saudi E-Invoicing (Fatoorah) — 7-article deep-dive series

    Continue with the full series on dariba.co

    View all articles →

    Deep-dive articles in this series

    Tax Intelligence
    Phase 1 Generation Phase Requirements — What Saudi Businesses Were Required to Do
    Tax Intelligence
    Phase 2 Integration Requirements — What Your Business Must Actually Prepare For
    Tax Intelligence
    Tax Invoice vs. Simplified Tax Invoice — Which Type Applies to Your Business?
    Tax Intelligence
    Clearance vs. Reporting — What’s Actually Required and When
    Tax Intelligence
    EGS Solution Requirements — What Your System Must Be Able to Do
    Tax Intelligence
    E-Invoicing Penalties in Saudi Arabia — What ZATCA Charges and How to Avoid It
    Tax Intelligence
    Fatoorah and VAT Compliance — How E-Invoicing Fits Into Your VAT Obligations

    This article reflects ZATCA’s E-Invoicing Regulation (December 2020) and the Controls, Requirements, Technical Specifications and Procedural Rules Resolution (May 2023 edition), supplemented by publicly available ZATCA wave announcements through September 2025. It is for informational purposes only and does not constitute legal or tax advice. Wave deadlines and eligibility criteria may be updated by ZATCA — confirm the current position at zatca.gov.sa or with a qualified Saudi tax advisor. dariba.co is an independent platform with no consulting relationships.

  • ZATCA Transfer Pricing Audits: What Triggers a Review, How Adjustments Work, and How to Defend Your Position

    Part of Transfer Pricing in Saudi Arabia: The Complete Guide — Article 7 of 7
    01

    ZATCA’s Audit Approach: A Maturing Enforcement Environment

    ZATCA’s TP enforcement posture has changed materially since the Bylaws were introduced in 2019. The June 2024 Guidelines signal an authority that has moved beyond framework-setting and is increasingly focused on operational enforcement. TP review is integrated into ZATCA’s annual assessment process — the Disclosure Form is its primary risk-screening tool.

    The June 2024 Guidelines (Chapter 13) confirm the enforcement framework: where a taxpayer has not prepared TP documentation in accordance with the Guidelines, the burden of proof on that taxpayer is increased. ZATCA will assess to what extent the taxpayer has provided sufficient information to meet requirements under the increased burden. In practice, this means documentation absence shifts evidentiary leverage to ZATCA before any dispute begins.

    02

    Risk Indicators That Attract ZATCA Scrutiny

    Risk IndicatorWhy It Attracts ScrutinyRisk
    Persistent Saudi entity losses in profitable groupSuggests profit shifted out via over-priced charges or under-priced salesHigh
    Disproportionate management fees or royalties as % of revenueClassic profit-shifting indicator; intragroup charges consuming most Saudi revenueHigh
    Transactions with entities in low-tax jurisdictionsProfit-shifting risk highest where counterparty pays materially lower tax ratesHigh
    Incomplete or inconsistent Disclosure FormMissing information, discrepancies vs. prior years, or descriptions not matching known activitiesHigh
    No documentation produced within 30-day windowFailure to produce shifts burden of proof and suggests TP was not properly consideredHigh
    Business restructurings disclosedTransfer of functions/assets/risks out of Saudi Arabia requires TP analysis and may require compensationMedium-High
    Significant IP royalty payments without clear value creationRoyalties eroding the Saudi tax base must be supported by evidence of genuine commercial valueMedium-High
    Intercompany debt at below- or above-market ratesUnder/over-pricing of intercompany loans represents implicit profit transferMedium-High
    03

    Article 4 Adjustment Powers

    Taxpayer’s self-adjustment obligation (Article 4(A)): Where controlled transaction conditions are not arm’s length, the taxpayer must make adjustments to its tax or Zakat base and report these in the annual declaration. This is a self-assessment obligation — taxpayers are required to identify and correct non-arm’s-length pricing, not wait for ZATCA.

    ZATCA’s adjustment powers (Article 4(B)): Where the taxpayer has not made necessary adjustments, or ZATCA disagrees with the taxpayer’s position, ZATCA may: (1) direct that the tax or Zakat base be adjusted to include the returns that should have accrued; or (2) reallocate or disregard the result of a controlled transaction to reflect what would have arisen in a comparable arm’s length transaction. This second power — to disregard a transaction — is most likely exercised where substance differs materially from form.

    Adjustment to the most appropriate point in the range: Under Article 12, ZATCA adjusts to the point within the arm’s length range that best reflects the facts and circumstances — not automatically to the median.

    04

    The Burden of Proof: How It Shifts

    Documentation StatusBurden of Proof PositionPractical Impact
    Contemporaneous Local File and Master File meeting Guidelines’ requirementsShared — ZATCA must demonstrate the pricing is not at arm’s lengthTaxpayer has a clear evidentiary foundation to defend its position
    Absent or inadequate documentationMaterially shifted against the taxpayerZATCA may proceed on available information; taxpayer must demonstrate arm’s length without contemporaneous support
    Documentation prepared retrospectively after audit contactWeaker than contemporaneous — even if technically correctZATCA and experienced practitioners identify retrospective preparation from structure, content, and timing
    05

    Corresponding Adjustments and MAP

    When ZATCA makes a TP adjustment, the consequences extend beyond the Saudi entity:

    Primary adjustment: ZATCA’s upward revision of the Saudi entity’s taxable income or Zakat base to reflect arm’s length conditions.

    Corresponding adjustment (Article 20): If the primary adjustment is consistent with the arm’s length principle, ZATCA makes a corresponding reduction to the tax base of the related foreign party, to eliminate economic double taxation. This requires the foreign jurisdiction to agree — typically through MAP under the applicable tax treaty.

    ZATCA may reject a corresponding adjustment application where: (1) the arrangement is artificial, abusive, or primarily tax/Zakat motivated; or (2) a final, unappealable judicial decision on the matter already exists.

    The Mutual Agreement Procedure (MAP) is available under Saudi Arabia’s tax treaties for disputes involving taxation not in accordance with the treaty. Where ZATCA makes a primary adjustment and the foreign authority does not agree to the corresponding reduction, the taxpayer can request MAP through both competent authorities. Without a qualifying treaty or an effective MAP, double taxation on the adjusted profit results.

    06

    Advance Pricing Agreements: Certainty for Complex Transactions

    The APA framework was formally introduced by Article 23 of the TP Bylaws via the March 2023 amendments — a significant development enabling upfront certainty for qualifying taxpayers. Key features:

    FeatureDetail
    Minimum transaction valueSAR 100 million per transaction (ZATCA Governor may exempt complex transactions)
    Lead time requiredAt least 12 months before the first covered fiscal year begins
    Pre-filing meetingZATCA holds a preliminary meeting before accepting the application
    APA termThree years, with annual compliance reports required
    ApplicationProspective only — does not apply retroactively to years under examination
    APA Programme Status

    The APA framework was established in March 2023. The practical procedures, timelines, and ZATCA’s processing capacity are still developing. Taxpayers considering an APA should verify the current status directly with ZATCA or through a qualified TP advisor before committing to the application process.

    APAs are available in unilateral form (ZATCA only) or bilateral form (ZATCA and the foreign competent authority under an applicable treaty). A bilateral APA provides certainty on both sides of the transaction and eliminates double taxation risk for the covered period.

    07

    Common Mistakes That Compound TP Audit Risk

    • Treating the Disclosure Form as a formality. ZATCA uses every line — transaction type, counterparty jurisdiction, TP method, amounts — as an audit selection tool. Careless preparation creates exactly the triggers ZATCA looks for.
    • Accepting ZATCA’s initial position without analysis. ZATCA’s initial TP adjustment proposal is not necessarily the final word. A well-prepared Local File and economic analysis are the tools for contesting it.
    • Not pursuing corresponding adjustments. When accepting a primary adjustment, consider whether to seek a corresponding reduction in the foreign jurisdiction through MAP. Without this, double taxation results on the same profit.
    • Not updating documentation for business changes. A restructuring, new intercompany arrangement, or change in functional profile all require documentation to be updated. Last year’s Local File for a materially different business is non-compliant.
    • Ignoring the APA option for material transactions. For high-value, complex arrangements above SAR 100M, the APA removes audit uncertainty entirely for the covered period. The 12-month lead time means APA planning must begin well before the transaction year.
    08

    Worked Example: ZATCA TP Adjustment

    Worked Example

    Al-Tamimi Trading Co. — Distributor Under Scrutiny

    Al-Tamimi Trading Co. is a Saudi-based distributor of imported capital equipment (70% German-owned / 30% Saudi-owned). It has reported operating losses in three of the last four years — margins ranging from -3% to -6% — while the German parent reports strong consolidated profitability.

    ZATCA’s analysis: Al-Tamimi’s own Local File benchmarking study (TNMM on operating margin) shows an IQR of 2%–9% for comparable independent distributors. Al-Tamimi’s -3% to -6% results are below the lower bound of its own analysis. Al-Tamimi holds inventory, bears collection risk, manages the local sales force, and has minimum purchase volume commitments — a risk profile that should produce a positive, stable return under the arm’s length principle.

    The adjustment: ZATCA applies TNMM and adjusts Al-Tamimi’s purchase price from the German parent to produce operating margin at the lower bound of the range (2%). For the year where Al-Tamimi’s revenue was SAR 120M and operating loss was SAR 3.6M (margin: -3%), the arm’s length operating profit at 2% = SAR 2.4M. Primary adjustment = SAR 2.4M − (−SAR 3.6M) = SAR 6 million additional taxable income. Additional CIT at 20%: SAR 1.2 million on the 70% non-Saudi share.

    Cross-regime consequence: The SAR 6M adjustment simultaneously increases Al-Tamimi’s CIT base (on the 70% non-Saudi share) and potentially its Zakat base (on the 30% Saudi share). Both must be addressed.

    The documentation gap: Al-Tamimi’s Local File contains a TNMM analysis but does not adequately explain the multi-year losses or document specific adverse business circumstances that might justify below-range performance. Without contemporaneous explanation, ZATCA’s adjustment stands.

    09

    Frequently Asked Questions

    ZATCA uses the TP Disclosure Form as its primary risk-screening tool. Key triggers: persistent Saudi entity losses while the group is profitable; disproportionate management fee or royalty charges; transactions with entities in low-tax jurisdictions; incomplete or inconsistent Disclosure Forms; absence of adequate documentation; and business restructurings.
    Yes. Under Article 4(B)(2) of the Bylaws, ZATCA can reallocate or disregard the result of a controlled transaction to reflect what would have arisen from a comparable arm’s length transaction. This power is most likely exercised where the substance of the transaction differs materially from its form.
    An APA is a binding agreement with ZATCA on the TP methodology for specific transactions before they occur, providing certainty for a three-year period. Formally introduced in Saudi Arabia by the March 2023 Bylaws amendments (Article 23). Minimum transaction value: SAR 100 million. Application must be initiated at least 12 months before the covered fiscal year begins.
    Where a taxpayer has prepared documentation meeting the Guidelines’ requirements, ZATCA must demonstrate the pricing is not at arm’s length. Where documentation is absent or inadequate, the burden shifts materially to the taxpayer — who must demonstrate arm’s length without contemporaneous documentation. This is a significantly weaker position in any dispute.
    Yes. For entities with both Saudi (Zakat) and non-Saudi (CIT) ownership, a TP adjustment to income affects both the CIT base and potentially the Zakat base. A TP compliance assessment must always consider both regimes simultaneously.
    ◆ Key Takeaways
    1. ZATCA uses the TP Disclosure Form as its primary audit risk-screening tool. Treat it with the same care as the tax return itself.
    2. Under Article 4 of the Bylaws, ZATCA can adjust controlled transactions that are not arm’s length — and can disregard transactions where substance differs from form.
    3. The burden of proof shifts materially against the taxpayer where documentation is absent or inadequate. Contemporaneous documentation does not guarantee success — but its absence makes success very difficult.
    4. When accepting a primary adjustment, always consider whether a corresponding adjustment from the foreign entity’s tax authority should be sought — through MAP or bilateral agreement. Without this, double taxation results.
    5. The APA framework (Article 23, March 2023) provides three years of certainty for complex transactions above SAR 100M. Planning must begin at least 12 months before the covered fiscal year.

    Back to the Complete Guide

    Transfer Pricing in Saudi Arabia: The Complete Compliance Guide (2024)

    Read the Pillar →

    Also worth reading

    Tax Intelligence
    Transfer Pricing in Saudi Arabia — The Complete Compliance Guide (2024)
    Tax Intelligence
    Saudi TP Documentation: Master File, Local File & CbCR
    Tax Intelligence
    Intercompany Services & Management Fees — TP Compliance
    Tax Intelligence
    Intercompany Financing — Loans, Guarantees & Cash Pooling

    This article reflects the Saudi Transfer Pricing Bylaws (March 2023 version) and the ZATCA Transfer Pricing Guidelines (June 2024 edition). It is for informational purposes only and does not constitute legal or tax advice. Readers should confirm the current position with ZATCA guidance or a qualified Saudi TP advisor. dariba.co is an independent platform with no consulting relationships.