{"id":"0345e1b1-2463-4d5a-b1ed-845f032874d0","task":"Complete ZATCA Fatoora Phase 2 (Integration) onboarding and submit invoices for clearance or reporting in Saudi Arabia","domain":"government-tax","steps":["Confirm your wave: ZATCA's e-invoicing rollout has two phases — Phase 1 (Generation), enforceable as of 4 December 2021, and Phase 2 (Integration), 'enforceable starting January 1st, 2023 in waves,' with ZATCA stating it 'will notify taxpayers of their Phase 2 wave at least six months in advance.'","Determine whether each invoice type requires Clearance or Reporting: ZATCA defines Clearance as the process where 'the Authority shall verify that the Electronic Tax Invoices and their associated Electronic Notes transmitted to it (through integration)... fulfil the controls and details specified in the E-Invoicing Resolution,' after which 'the Authority shall insert the Cryptographic Stamp only on the Invoices and Notes which fulfil the aforementioned controls and details'; the guideline also states 'the process of Clearance is not applicable to Simplified Tax Invoices.'","For Simplified Tax Invoices, implement Reporting instead: persons subject to the regulation 'will be required to transmit all Simplified Tax Invoices to the FATOORA Portal within (24) hours from its issuance.'","Register your compliant e-invoicing solution on the FATOORA Portal as part of onboarding, generating (or renewing) a Cryptographic Stamp Identifier (CSID) that ZATCA defines as 'a unique identifier that links the E-Invoice... generating cryptographic stamp identifier or renewing the existing one.'","Generate a UUID inside every XML invoice (per the guideline, 'the UUID is generated by a compliant E-Invoice Solution and stored inside the XML invoice') and call the FATOORA clearance API in real time for standard tax invoices, or the reporting API for simplified invoices.","Handle clearance failures per the guideline's stated retry behavior: on failure you must correct and 'submit another invoice for clearance after rectifying the errors,' noting that 'every document shall have its own hash and counter value.'"],"gotchas":["In Phase 1 the cryptographic stamp is applied by the FATOORA Portal itself; in Phase 2 the guideline table shows 'cryptographic stamp mandated' on the taxpayer/solution side instead — confirm which stamping responsibility applies to your wave before going live.","Clearance and Reporting are two distinct API flows in the technical guideline (clearance via real-time API for standard tax invoices, reporting via API upload for simplified invoices) — building only one will leave the other invoice type non-compliant.","A rejected clearance document still consumes its own hash and invoice counter value per the guideline; don't reuse a rejected invoice's counter value when resubmitting."],"contributor":"waymark-seed","created":"2026-07-09T00:09:27Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/0345e1b1-2463-4d5a-b1ed-845f032874d0"}