Taxes in Saudi Arabia
The standard rate has been 15% since 2020-07-01. The rates below are published for orientation — check them with the authority before relying on them.
The taxes, by name
| Tax | Kind | Rate |
|---|---|---|
| VAT 15%On most sales inside the Kingdom. | Standard rate | 15% |
| Zero-ratedInternational transport, qualifying medicines and medical equipment, investment metals. | Zero-rated | 0% |
| Export outside the GCC 0% | Export | 0% |
| ExemptMargin-based financial services and residential rent. | Exempt | 0% |
| Import VAT 15% | Import | 15% |
| Reverse charge 15%Services bought from a supplier who is not resident. | Reverse charge | 15% |
| Withholding 20% | Withholding | 20% |
| Withholding 15% | Withholding | 15% |
| Withholding 5%On payments to non-residents, by payment type. | Withholding | 5% |
What JooDax does not do in Saudi Arabia
- JooDax fills in no return for this country and submits nothing.
- The Phase 1 QR, and the Phase 2 UBL document with its hash and chain. The cryptographic stamp, clearance and reporting work with a certificate the business obtains from the authority for its own tax number, using a one-time password it fetches from the authority’s portal itself. JooDax is not certified, approved or accredited by ZATCA or by any tax authority, and anything produced in the sandbox or the simulation is a test document with no legal effect.
- Withholding is not computed for you when a payment is made.
What it does
It works the tax out line by line and rounds it once, prints a bilingual invoice, keeps what you charged and what you paid in two separate accounts, and then reads the period off your own books on the VAT page: the figure from the accounts, the breakdown from the invoices and sales behind it.
The Phase 2 document is built on our own server, and tells you what it does not satisfy before you send it
A UBL document, a hash, a chain and the QR, with your business’s own certificate — and a named list of every rule the document knows it does not satisfy.
- UBL 2.1
- SHA-256
- XAdES
Document status · last 5 invoices
Illustration- Demo customer 1INV-2026-00414,312.50Stamped
- Demo customer 2INV-2026-0042975.00Stamped
- Demo customer 3INV-2026-004312,650.00Stamped
- Demo customer 4INV-2026-0044588.00Stamped
- Demo customer 5INV-2026-00452,124.00Being built
A panel with demo figures. “Stamped” is the document’s state inside JooDax — built, and stamped with the business’s own certificate — and not acceptance by any tax authority.
What is built here, on our own server
- The Phase 2 UBL document, in the shape the published standard describes, business term by business term.
- The document’s hash, and the chain that links each invoice to the one before it.
- The cryptographic stamp, with your business’s own certificate: you obtain it from the authority for your own tax number and paste it into Settings, or onboard the unit from there.
- Shared sandbox
- Simulation
- Production
TEST DOCUMENT — no legal effect
This mark appears on screen, in print and in the email subject line, in both languages at once. A document from a test environment can never be presented as a cleared tax invoice.The Phase 2 document, on our own server
Built as UBL 2.1 out of your own invoice, in the shape the published standard describes. Nothing leaves our server while it is built.
A hash, and a chain that does not break
Each document has its SHA-256 hash and carries the hash of the one before it. The sequence is one unbroken run, and a test document is never allowed a place in it.
Six QR fields without a certificate, nine with one
The Phase 1 QR on every simplified invoice. Fields seven, eight and nine are a signature, a public key and the authority’s own signature — left out until the certificate exists, rather than filled with something that would look real.
The certificate is yours, not ours
One step this product cannot take for you: the one-time password, which you fetch from the authority’s portal with your own business account. JooDax is not certified, approved or accredited by any tax authority.
Three environments, and the test document is marked
The shared sandbox, the simulation and the live environment. Anything made in a test environment carries its mark on screen, in print and in the email subject line, in Arabic and in English.
No tax number, no document
A tax invoice without the seller’s registration number tells the reader the seller is not registered. JooDax refuses to build the document at all rather than emitting one that says so.
The rules a document records about itself
- KSA-15
- Security Features §4.1, tags 7–9
- KSA-5 / BR-KSA-15
- BT-35
- KSA-17 / BR-KSA-44
- KSA-3
- BT-38
- BT-44
- BT-50, BT-52, BT-55
- BT-48
It tells you what is wrong with the document before you send it, not after it comes back
Without a pre-emptive warning
A mandatory field is left empty, and nothing on the screen says a rule of the standard was not met. You learn it when the document comes back to you, after it has gone out.
With the system
JooDax checks the document as it builds it and records on it, by name, every rule it knows the document does not satisfy — the rule’s number and what it says — at build time, not after.
3 warnings before you send
- KSA-17 / BR-KSA-44
The seller’s address has no four-digit building number.
- BT-48
The buyer’s VAT number is not recorded. It is required when the buyer is VAT-registered.
- KSA-5 / BR-KSA-15
JooDax records no supply date, and the standard requires one on a tax invoice. Putting the issue date there would be inventing a fact.
These are warnings, not blocks: they do not stop you issuing the invoice. They are recorded on the document itself as it is built, so you are the first to know them.
- The Phase 1 QR on every simplified invoice
- The Phase 2 document, its hash and its chain
- Your keys and your certificate, encrypted on our server
JooDax is not certified, approved or accredited by the Zakat, Tax and Customs Authority or by any tax authority, and it fills in no VAT return and sends one to nobody. What JooDax does not do in Saudi Arabia, written out