Skip to content

ZATCA invoice XML checker

Check a UBL invoice file against the published ZATCA technical rules.

We process your file on our server, then delete it after 6 hours

You get a list of rule codes, where each one sits in the file, and a count of errors and warnings. A file with no findings is a normal result.

How to use it

  1. 1Upload your filePick an image or a PDF from your device, or drag it into the box.
  2. 2We read what is insideWe show the hidden data the file carries: the device, the date, and the location if there is one.
  3. 3Read the reportIt appears on screen, so you learn what would have traveled with the file if you had sent it as it is.

When it helps

A simplified or standard tax invoice has to match a published set of technical rules before it can be used. Catching a missing UUID or a wrong VAT number on your own file is cheaper than finding out later.

Common questions

Does a clean result mean the invoice is accepted?

No. It means the published technical rules we check all hold on this file. We do not submit the file, and we do not replace the official process.

Which files can I check?

A UBL 2.1 invoice in XML, simplified or standard. PDF invoices are not read in this version.

Is my file stored?

The check itself does not keep the file. You can download the report as JSON. Saving the report to your account is optional and happens only if you ask.

What do the codes mean?

Each code is a published ZATCA technical rule, such as BR-KSA-03 for the invoice UUID. The location points at the element in your file.

6 tools

Tools from other categories