When i use Clearance-Status as 1 or 0 in api

Clearance and Reporting
1

Hi @idaoud

When using reporting and clearing api, the header include clearing-status 1 or 0

What mean by it.

2

Dear @Shameem

Thanks for reaching out,

Your concerns is not clear, can I kindly ask you to elaborate more with more details to provide the usual comprehensive support?

Thanks,
Ibrahem Daoud.

3

Dear @idaoud

-H 'Clearance-Status: 1'

This header is required in clearing , reporting api.

how to decide the clearing-status is enabled or desabled

4

Dear @Shameem

There is nothing as what you mentioned in ZATCA APIs header, Please find the required Headers for both clearance & Reporting APIs:

key: accept-language                 value: en 
Key: Accept-Version                     value: V2

Thanks,
Ibrahem Daoud.

5

Dear @idaoud

I am referring

https://sandbox.zatca.gov.sa/IntegrationSandbox

in this page

API Documentation guide > Clearance API

in this doc

Clearance-Status *
string
(header)
	

Specifies the clearance status, while "0" when clearance is disabled and "1" when clearance is enabled

and the example api is like

curl -X 'POST' \
  'https://gw-fatoora.zatca.gov.sa/e-invoicing/developer-portal/invoices/clearance/single' \
  -H 'accept: application/json' \
  -H 'accept-language: en' \
  -H 'Clearance-Status: 1' \
  -H 'Accept-Version: V2' \
  -H 'Authorization: Basic VFVsSlJETnFRME5CTkZOblFYZEpRa0ZuU1ZSRlVVRkJUMEZRUmprd1FXcHpMM2hqV0hkQlFrRkJRVFJCZWtGTFFtZG5jV2hyYWs5UVVWRkVRV3BDYVUxU1ZYZEZkMWxMUTFwSmJXbGFVSGxNUjFGQ1IxSlpSbUpIT1dwWlYzZDRSWHBCVWtKbmIwcHJhV0ZLYXk5SmMxcEJSVnBHWjA1dVlqTlplRVo2UVZaQ1oyOUthMmxoU21zdlNYTmFRVVZhUm1ka2JHVklVbTVaV0hBd1RWSnpkMGRSV1VSV1VWRkVSWGhLVVZWc2NFWlRWVFZYVkRCc1JGSldUa1JSVkZGMFVUQkZkMGhvWTA1TmFsRjNUVlJGZUUxRWEzaFBWRTEzVjJoalRrMXFhM2ROVkVFMVRVUnJlRTlVVFhkWGFrSXhUVkZ6ZDBOUldVUldVVkZIUlhkS1ZGRlVSVzFOUTFGSFFURlZSVU5vVFdSVVYwWTBZVmN4TVdKVFFsUmpSMVpzV2tOQ1ZWcFhUbTlKUms0eFkwaENjMlZUUWsxV1JWRjRSbXBCVlVKblRsWkNRWE5VUkZaS2NHVlhSbXRoUTBKRFkyMUdkVmt5WjNoS2FrRnJRbWRPVmtKQlRWUklWbEpVVmtNd05FOUVXVEJOZWtWNFRrUlZkRTE2YXpWUFZHczFUMVJyTlU5VVFYZE5SRUY2VFVaWmQwVkJXVWhMYjFwSmVtb3dRMEZSV1VaTE5FVkZRVUZ2UkZGblFVVnZWME5MWVRCVFlUbEdTVVZ5VkU5Mk1IVkJhME14VmtsTFdIaFZPVzVRY0hneWRteG1OSGxvVFdWcWVUaGpNREpZU21Kc1JIRTNkRkI1Wkc4NGJYRXdZV2hQVFcxT2J6aG5kMjVwTjFoME1VdFVPVlZsUzA5RFFXZGpkMmRuU1VSTlNVZDBRbWRPVmtoU1JVVm5ZVlYzWjJGTGEyZGFPSGRuV25kNFQzcEJOVUpuVGxaQ1FWRk5UV3BGZEZaR1RsVm1SRWwwVmtaT1ZXWkVUWFJhVjFGNVRXMVplRnBFWjNSYVZGcG9UV2t3ZUUxVVJUUk1WR3hwVGxSbmRGcEViR2hQUjFsNFRWZFZNRTVFVm0xTlVqaDNTRkZaUzBOYVNXMXBXbEI1VEVkUlFrRlJkMUJOZW1zMVQxUnJOVTlVYXpWUFZFRjNUVVJCZWsxUk1IZERkMWxFVmxGUlRVUkJVWGhOVkVGM1RWSkZkMFIzV1VSV1VWRmhSRUZvVTFWc1NrVk5hbXQ1VDFSRllVMUNaMGRCTVZWRlJIZDNVbFV6Vm5kalIzZzFTVWRHYW1SSGJESmhXRkp3V2xoTmQwaFJXVVJXVWpCUFFrSlpSVVpGV0N0WmRtMXRkRzVaYjBSbU9VSkhZa3R2TjI5alZFdFpTekZOUWpoSFFURlZaRWwzVVZsTlFtRkJSa3AyUzNGeFRIUnRjWGR6YTBsR2VsWjJjRkF5VUhoVUt6bE9iazFJYzBkRFEzTkhRVkZWUmtKM1JVSkNSemgzWWxSQ2NrSm5aM0pDWjBWR1FsRmpkMEZ2V21aaFNGSXdZMFJ2ZGt3eVJuQlpWRkYxWlcxR01Ga3lSWFZhTWpreVRHNU9hRXd3VG14amJsSkdZbTVLZG1KSGQzWlZSa3BoVWxWc2RXUnRPWEJaTWxaVVVUQkZNRXh0VmpSa1IyUm9aVzVSZFZveU9USk1iWGgyV1RKR2MxZ3hRbE5YYTFaS1ZHeGFVRk5WVGtaVk1FNUNUa014UkZGVFozaExVelZxWTI1UmQwUm5XVVJXVWpCUVFWRklMMEpCVVVSQloyVkJUVVIzUjBOVGMwZEJVVkZDWjJwalZrSjNVWFpOUXpCSFNsTnpSMEZSVVVKbmFtTldRMGxIUjNGQ01rVXdVSE5UYUhVeVpFcEpaazhyZUc1VWQwWldiV2d2Y1d4YVdWaGFhRVEwUTBGWFVVTkJVa2wzU0ZGWlJGWlNNR3hDUWxsM1JrRlpTVXQzV1VKQ1VWVklRWGROUjBORGMwZEJVVlZHUW5kTlEwMURZMGREVTNOSFFWRlJRbWRxWTFaRFoxRmhUVUpuZDBObldVbExkMWxDUWxGVlNFRjNUWGREWjFsSlMzZFpRa0pSVlVoQmQwbDNRMmRaU1V0dldrbDZhakJGUVhkSlJGTkJRWGRTVVVsb1FVeEZMMmxqYUcxdVYxaERWVXRWWW1OaE0zbGphVGh2Y1hkaFRIWkdaRWhXYWxGeWRtVkpPWFZ4UVdKQmFVRTVhRU0wVFRocVowMUNRVVJRVTNwdFpESjFhVkJLUVRablMxSXpURVV3TTFVM05XVnhZa012Y2xoQlBUMD06Q2tZc0VYZlY4YzFnRkhBdEZXb1p2NzNwR012aC9ReW80THpLTTJoLzhIZz0=' \
  -H 'Content-Type: application/json' \
  -d '{.......
6

Dear @Shameem

Please note that the sandbox is only to clarify the onboarding process steps, you can’t successfully integrate with ZATCA during Sandbox as it contains a static certificate, However our recommendation is to start with Simulation environment to avoid any issues when proceeding to production environment, As I mentioned previously only (accept-language: en) and (Accept-Version: V2).

I hope it is clear enough now, for any further support, do not hesitate to reach out to our support team via below mail:

SP mail: sp_support@zatca.gov.sa

Thanks,
Ibrahem Daoud.

7

Thanks you @idaoud

Please help me for below queries

1 .When i completed the clearing api, in response it contains the invoice, did i want to extract it and find the qr code , is that qr append in printing invoice .

  1. Currently my client is printing invoice in their own style, did i want to change to the pdf format as mentioned in sdk or i use the qr in our own pdf.
8

@Shameem

  1. for Tax Invoices, You need to extract and use the QR value from clearance response API Invoice xml to display it in Invoice pdf
  2. There are no pdf invoice style limitations. However, Invoice should contain the Mandatory fields as mandated by ZATCA. You can refer the E-Invoice guide lines / data dictionary for list of fields and their format
1 Like