Aqid ERPStandard and simplified invoices
B2B invoices go for clearance, B2C for reporting, with credit and debit notes tied to the invoice they correct.
ZATCA Phase 2
E-invoicing built to ZATCA Phase 2
Every invoice leaves Aqid ERP as the regulation asks: signed XML, a QR code, a counter and a hash chain per device, cleared or reported with ZATCA before it reaches your customer.
Start now for free No credit card needed — invoice in minutes
What you get
UBL 2.1 XML with an XAdES signature
The XML is generated from the ledger, signed in a separate service that alone holds the device keys, and kept with the PDF.
QR code and PDF/A-3
A Phase 1 QR on every PDF and the XML embedded in a PDF/A-3, in Arabic and English.
Device onboarding from the app
Register a device with your Fatoora OTP from Compliance; the invoice counter and previous-hash chain are kept per device.
Per-invoice status
See each invoice's clearance or reporting answer and the reason for a rejection; a send that fails is queued and tried again.
Questions
Is Aqid ERP approved by ZATCA?
Aqid ERP is built to the Phase 2 specification (UBL 2.1, XAdES, QR, ICV and PIH). The listing in ZATCA's directory is in progress; until then this page says so.
Do I need a separate e-invoicing device?
No. A device in ZATCA's sense is a software unit; Aqid ERP registers one per branch or point of sale from Compliance.
What happens if ZATCA is unreachable?
The invoice is queued and sent again. Simplified invoices are reported within 24 hours; standard invoices are cleared before they are delivered.