E-invoicing that clears with ZATCA — from the same system that runs your fleet
SaudiConnect issues, signs and submits Phase 2 invoices directly to the Fatoora gateway. No export files. No second system. No month-end scramble.
Two systems, one invoice
Your fleet system tracks the job. Your accounting system bills it. Someone re-types it in between. That gap is where errors and delays live.
Compliance is not optional
Phase 2 is mandatory. A rejected invoice is not a technical issue — it is revenue you have not recognised yet.
Manual work scales badly
Every vehicle you add means more invoices, more re-keying, and more chance of a mismatch nobody catches until the filing.
What built in actually means
Most platforms say they are ZATCA compliant. Here is exactly what ours does.
Six mechanisms behind the badge — each one a technical fact you can verify on a demo call.
Direct gateway submission
Invoices post to the ZATCA Fatoora API from inside SaudiConnect — not a file you download and upload somewhere else.
Production CSIDs, per branch
Each branch registers its own EGS unit with its own cryptographic identity, so multi-branch operations stay correctly separated.
Clearance and reporting
Standard invoices cleared in real time; simplified invoices reported inside the 24-hour window. The distinction is handled for you.
Tamper-evident invoice chain
Every invoice carries an incrementing counter and the hash of the one before it. The chain proves nothing was altered or removed.
Immutable once issued
The database itself refuses to modify a cleared invoice. Not a policy — a constraint.
QR and signature on every invoice
Generated at issue in the format ZATCA specifies, in Arabic and English.
Your invoice is only as accurate as the operations behind it
Compliance is downstream of how the work actually ran. Ours comes from the same database.
- The trip that generated the charge sits in the same system as the invoice
- VAT at 15% calculated on real operational data, not figures re-entered by hand
- Fuel, maintenance and rental charges reach the invoice from the work itself
- Hijri and Gregorian dates, Arabic-Indic numerals and SAR formatting throughout
- Filing-ready VAT reports built from cleared invoices
- Standard + simplified tax invoices
- Per-branch EGS units
- Hash-chained, immutable invoice records
Straight answers on what is and is not connected
Every vendor in this market claims every integration. Here is where we actually stand.
ZATCA Phase 2 e-invoicing
Built in, with live gateway integration and production credentials.
VAT reporting
Built in, with filing-ready output at 15%.
Fahas (government vehicle inspection) — connected
We read inspection status and expiry straight from Tamm, so what you see is the government record rather than a date someone typed in.
WASL — not integrated
Our data model is prepared for it, but that interface is not open to us yet. We would rather say so plainly than imply otherwise.
Questions about e-invoicing
See it clear an invoice in real time
Book a walkthrough with a team that knows Saudi fleet operations — in Arabic or English, whichever suits you.