Phase 2 made invoicing a live conversation.
And most accounting systems were never built to hold up their end of it.
A standard invoice now has to be cleared with ZATCA before it can be issued; a simplified one has to be reported within twenty-four hours. Both have to be signed, hashed and chained to the invoice before them, in a format most systems have no idea how to produce.
Most companies solved this twice: once badly, in a hurry, before a wave deadline, and then again properly a year later. We built Accurate so the second attempt is the only one you need — a clearance layer that sits between the system you already use and ZATCA, and absorbs the specification changes on your behalf.
Registered here, hosted here, answering the phone here.
Customer invoice data stays in the Kingdom. That is a deliberate constraint rather than a detail: it keeps our customers' residency obligations simple, and it means the people who answer a support question at month end are in the same time zone as the deadline.
Three things we will not trade away.
The spec is the product
We track every Fatoora specification release and every ZATCA implementation resolution, and we ship against the published document — not against what worked last quarter.
Arabic first, not Arabic later
Invoices, support and the product itself are bilingual from the start. A tax document that reads awkwardly in Arabic is not finished.
Boring where it counts
Clearance either happens or it does not. We would rather ship a dull, predictable pipeline than a clever one you have to babysit at month end.
The formalities.
| Legal name | Accurate |
|---|---|
| Commercial registration (CR) | 7023984482 |
| VAT registration | 310459988300003 |
| Registered address | Dammam, Eastern Province, Saudi Arabia |
| General enquiries | info@accurates.sa |