E-invoicing that follows ZATCA, without slowing the counter

In Saudi Arabia every taxpayer must issue electronic invoices under the rules of the Zakat, Tax and Customs Authority (ZATCA). Alkaml covers both phases. In phase 1 the compliant QR code is generated with every invoice. In phase 2 each device connects to ZATCA with its own certificate, then signs every invoice and reports or clears it.

Signing happens on the device itself, so a simplified invoice prints at once even when the internet is gone and is reported when the connection returns. Standard tax invoices are sent for clearance first, as the regulation requires. You can see the answer of every attempt, and a rejected invoice can be fixed and sent again as a new attempt.

What you can do

Phase 1 QR code

Seller name, VAT number, time, total, and tax encoded the way ZATCA specifies.

Phase 2 integration

Connect each device with a one time password, in the simulation or production environment.

Signing and the invoice chain

Each invoice is signed, hashed, counted, and chained to the one before it.

Reporting and clearance

Simplified invoices are reported and standard tax invoices are cleared.

Credit notes

Returns become compliant credit notes linked to the original sale.

Exemptions and foreign currency

Zero rated and exempt items with their reason codes, and tax amounts in riyals for other currencies.

Unsent invoices

A clear list of what ZATCA has not accepted yet, with the reason and one button to send it again.

A full history of attempts

Every answer from ZATCA is kept, including warnings, so you can always show what happened.

How it works

1

Fill in your company's tax details and turn on e-invoicing.

2

Integrate the device with the one time password from Fatoora.

3

Sell as usual. Signing and sending happen for you.

Questions

Does Alkaml support ZATCA phase 2?

Yes. Devices integrate with ZATCA directly, sign invoices, and report or clear them.

Can I sell while ZATCA is down or the internet is off?

Yes for simplified invoices. They are signed and printed on the device, then reported when ZATCA can be reached.

What if ZATCA rejects an invoice?

The reason is shown on the invoice. You fix the data and use update and send, which creates a new attempt and keeps the rejected one on record.

Works together with

Start using Alkaml

Start for free