# Saudi ZATCA E-Invoicing Phase 2 Integration Checklist > Source: https://netray.co/tools/saudi-zatca-e-invoicing-phase-2-integration-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A 36-point readiness checklist for the ZATCA Fatoora integration phase, covering onboarding, invoice data, security and ERP changes. ## Category regional ## Region Saudi Arabia ## Audience - Finance controller - ERP administrator - Tax manager ## Tool **Kind:** checklist **Scoring Note:** Tick each item you can evidence today. Critical items are the ones that block clearance or reporting if missing. Confirm your wave date and technical specifications on the ZATCA Fatoora portal, because requirements are updated by ZATCA. **Groups:** #### Scope and governance **Items:** **Text:** Confirmed whether your taxpayer group has been notified for an integration phase wave and noted the deadline **Critical:** true Named an owner in finance and an owner in IT for the ZATCA programme **Text:** Listed every system that issues invoices, credit notes and debit notes (ERP, POS, billing tools, portals) **Critical:** true Mapped which invoices are standard (B2B and B2G) and which are simplified (B2C) Decided whether to extend the ERP, buy a certified add-on, or use a middleware or solution provider Reviewed the latest ZATCA e-invoicing regulation, security features and technical specification documents Set a test and parallel-run plan with dates before the go-live deadline #### Onboarding and security **Items:** **Text:** Registered each invoicing device or solution unit in the Fatoora portal with the correct VAT number **Critical:** true **Text:** Generated a certificate signing request (CSR) with the fields ZATCA requires for each solution unit **Critical:** true Obtained a one-time password from the portal for onboarding and recorded who requested it **Text:** Received a compliance CSID and passed the compliance checks with sample invoices **Critical:** true **Text:** Requested the production CSID and stored the certificate and private key in a secured key store **Critical:** true Defined a renewal and revocation procedure for certificates before they expire Restricted access to private keys to a minimal named group, with audit logging #### Invoice data and format **Items:** **Text:** Invoices are generated as XML following the UBL 2.1 structure defined by ZATCA **Critical:** true **Text:** Every invoice carries a UUID and an invoice counter value (ICV) that increments without gaps **Critical:** true **Text:** Previous invoice hash (PIH) is carried into each new invoice to keep the hash chain intact **Critical:** true Seller and buyer data include name, address elements, VAT number and other mandatory party fields **Text:** Line level VAT category codes and exemption or zero-rate reason codes are mapped from ERP tax codes **Critical:** true Invoice type and subtype codes distinguish standard from simplified and invoice from credit or debit note Credit and debit notes reference the original invoice and include a reason Rounding, discounts, and prepayment lines reconcile exactly between ERP totals and XML totals Mandatory Arabic content is present on the printed or PDF representation Human-readable PDF/A-3 with the embedded XML is produced where required for B2B delivery #### Clearance and reporting flow **Items:** **Text:** Standard invoices are sent for clearance and are not delivered to the buyer until ZATCA returns the cleared invoice **Critical:** true **Text:** Simplified invoices are signed locally, carry a QR code and are reported to ZATCA within the allowed time **Critical:** true The cryptographic stamp and QR code returned or generated are stored with the invoice record Error and warning responses from the API are captured, shown to users and have an owner for resolution A retry queue exists for outages so no invoice is lost or issued out of sequence Contingency steps are documented for ZATCA or network downtime #### Operations and records **Items:** **Text:** Invoices and related data are archived for the period required by law, in a retrievable format **Critical:** true Finance users are trained on what to do when an invoice is rejected or needs a credit note Reconciliation compares ERP invoice register, cleared invoices and the VAT return each period Master data quality for customer VAT numbers and addresses has been cleaned before go-live Change control covers ERP upgrades that might alter invoice XML mapping ## Content **Intro:** ZATCA's integration phase (Phase 2) moves Saudi e-invoicing from simply generating a compliant invoice to connecting your invoicing system with the Fatoora platform. This checklist helps a controller or ERP administrator at a manufacturer check readiness item by item, then export the result for a project plan. **Sections:** #### How to use this checklist **Body:** Work through the groups in order. Tick only what you can show evidence for, such as a screenshot of a production CSID, a sample cleared invoice, or a documented procedure. Items marked critical are the ones that typically cause rejected invoices or blocked delivery to customers. Export the result to PDF or Excel and use the unticked rows as your task list, assigning an owner and date to each. Re-run it after each test cycle so you can see progress move toward a full pass. #### What Phase 2 changes compared with Phase 1 **Body:** Phase 1, the generation phase, required an e-invoice in a structured, tamper-resistant form with a QR code and no handwritten or edited invoices. Phase 2 adds integration. Your system sends standard invoices to ZATCA for clearance, and reports simplified invoices within a set time. It also uses certificates (CSIDs), XML in the UBL 2.1 format, a unique UUID, an invoice counter and a hash of the previous invoice to form a chain. **Bullets:** - Standard invoices (B2B, B2G) are cleared before they reach the buyer - Simplified invoices (B2C) are reported after issue within the allowed window - Each invoice references the hash of the previous one - Credit and debit notes follow the same technical rules #### ERP considerations for manufacturers **Body:** Most manufacturers invoice from an ERP billing module, plus occasional manual or portal invoices that are easy to forget. Inventory the lot. Next, check how your tax codes map to ZATCA VAT categories, because a zero-rated export and an exempt supply need different reason codes. Check how your ERP numbers invoices, since a gap or reuse of numbers conflicts with the counter and hash chain. Finally decide where signing happens: inside the ERP, in a middleware layer, or in a certified add-on. Test with real edge cases such as partial shipments, advance payments, discounts and credit notes. #### Common mistakes **Body:** Teams often leave onboarding to the last month and then discover that certificates, devices and test cases take longer than expected. Other frequent errors include mismatched totals caused by rounding, missing buyer data on standard invoices, issuing a credit note without the original reference, and failing to plan for outages. Treat the rule set as living material: ZATCA publishes updates, so confirm each point against the current official documentation before go-live. **Cta:** If you want to expose clearance status and rejected-invoice reasons from your ERP in plain language, Netray can help build a read-only view over your invoice data on infrastructure you control. **Faq:** #### Is this checklist an official ZATCA document? **Answer:** No. It is a practical readiness checklist written from the public structure of the integration phase. Always confirm requirements, wave dates and technical specifications against the current documents published by ZATCA on its official portal. #### What is the difference between clearance and reporting? **Answer:** Clearance applies to standard invoices: they are submitted to ZATCA and approved before the buyer receives them. Reporting applies to simplified invoices: they are issued and signed locally, then reported to ZATCA within the permitted period afterwards. #### What is a CSID? **Answer:** A CSID is a cryptographic stamp identifier, effectively a certificate issued to a registered solution unit. A compliance CSID is used to pass tests, and a production CSID is then used to sign and submit live invoices. #### Do we need to replace our ERP? **Answer:** Not necessarily. Many ERPs can be extended with a vendor module, a certified add-on or middleware that builds the XML, signs it and calls the ZATCA APIs. The key is that the data mapping, numbering and archive rules are correct. ## Search terms zatca phase 2 checklist, zatca e-invoicing integration phase, fatoora phase 2 requirements, saudi e-invoicing erp readiness, zatca csid onboarding, zatca xml ubl 2.1 invoice, zatca clearance and reporting, saudi e-invoice checklist for manufacturers --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json