Zakat, Tax and Customs Authority
E-invoicing built into the ledger, not bolted onto it
Raqeem generates the invoice, signs it and archives it inside the same system that posts the journal entry. There is no export step, no middleware, and no second source of truth to reconcile.
What the engine implements today
The technical requirements of Phase 2, implemented and testable before you go live.
UBL 2.1 documents
Standard and simplified tax invoices, credit notes and debit notes produced as compliant UBL 2.1 XML, in both Arabic and English.
ECDSA secp256k1 signing
Cryptographic stamping using the curve the authority specifies, with the private key held per establishment and never shared between tenants.
TLV-encoded QR codes
Every simplified invoice carries the tag-length-value QR code required for verification at the point of sale.
Hash chaining
Each invoice stores the hash of the one before it, so any gap or alteration in the sequence is detectable during an audit.
Six-year archive
Signed XML and the rendered PDF/A-3 are retained together for the statutory retention period, exportable at any time.
VAT return
A chart of accounts to international standards, mapped to the VAT return boxes, so the declaration is produced from the ledger rather than a spreadsheet.
What still depends on you
We would rather be clear about this before you subscribe than after.
Being technically ready is not the same as being live. Integration with the authority is granted per establishment, and three steps belong to you and cannot be done on your behalf by any vendor:
- Registering the establishment with the Zakat, Tax and Customs Authority.
- Generating a certificate signing request and obtaining your own CSID.
- Passing the authority's compliance checks for the invoice types you issue.
Raqeem prepares the request, holds the credentials securely once issued, and walks your finance team through each stage. Any vendor promising instant Phase 2 compliance without these steps is describing something that does not exist.
Compliance questions
Asked by nearly every finance team we onboard.
The technical part is quick once your establishment details are correct in the authority's portal. In practice the timeline is set by how fast those details are verified, not by the software.
Credentials are issued per establishment and per device configuration, so a group with several registered establishments manages several sets. Raqeem keeps them separated and lets you see the status of each from one screen.
Yes. Your trial workspace issues documents against the authority's simulation environment, so your team can see the XML, the stamp and the QR code on your own data before anything is submitted for real.
Simplified invoices are reported after the fact, so selling continues. Documents are queued, signed locally and submitted when the service returns; nothing is lost and the hash chain stays intact.
Want a compliance review before you commit?
Send us how you invoice today and we will tell you what your move to Phase 2 actually involves.