Q1. The documentation talks about clearance flag being enabled or disabled. How is that set?
I am confused about the concept of clearance. Reporting API says
‘This API will be used to submit test Simplified e-invoices, credit or debit note to a test ZATCA backend system as part of the Reporting process
When Clearance is disabled, this API can also be used to submit test Standard e-invoices, credit or debit notes for Reporting’
Q2. Why should clearance be disabled for Standard e-Invoices but not for the others?
Q3. The “Clearance API” clears a single standard invoice, credit note, or debit note. If it is disabled for standard invoice, it should be sent as Reporting.
How is reporting done for credit and debit notes? Is clearance disabled or enabled?
Q4. I assume there is no clearance process for simplified invoices?
Certificate Type Codes: Meaning & Required Compliance Checks
The TITLE field in your CSR represents what invoice types your EGS (E‑Invoicing Generation Solution) unit will support. It’s represented by a 4‑digit binary code "TSCZ":
T = Tax Invoice (standard)
S = Simplified Tax Invoice
C, Z – reserved for future use, currently set to 0.
A1: You can ignore this header in the clearance API, stick only to basic auth + accept-version + accept-language.
A2: Clearance is for B2B tax documents while reporting is for B2C tax documents, however, clearance hasn’t been disabled for a signle time till now by ZATCA, it’s just a pre-defined procedure by ZATCA in case of any disaster circumstances.
A3:reporting is for B2C invoicee. and no clearance disabled/enabled needs to be specefied in the API request.
Q4: Yes, B2C tax documents can be shared directly with the customers without any clearance procedure, taxpayers has 24 hours to report the XML invoice to ZATCA.