Loading
AlphaFleet issues, signs and submits Phase 2 invoices directly to the Fatoora gateway. No export files. No second system. No month-end scramble.
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.
Phase 2 is mandatory. A rejected invoice is not a technical issue — it is revenue you have not recognised yet.
Every vehicle you add means more invoices, more re-keying, and more chance of a mismatch nobody catches until the filing.
Invoices post to the ZATCA Fatoora API from inside AlphaFleet — not a file you download and upload somewhere else.
Each branch registers its own EGS unit with its own cryptographic identity, so multi-branch operations stay correctly separated.
Standard invoices cleared in real time; simplified invoices reported inside the 24-hour window. The distinction is handled for you.
Every invoice carries an incrementing counter and the hash of the one before it. The chain proves nothing was altered or removed.
The database itself refuses to modify a cleared invoice. Not a policy — a constraint.
Generated at issue in the format ZATCA specifies, in Arabic and English.
Built in, with live gateway integration and production credentials.
Built in, with filing-ready output at 15%.
We read inspection status and expiry straight from Tamm, so what you see is the government record rather than a date someone typed in.
AlphaFleet holds a Wasl licence. Vehicle and driver registration with the Transport General Authority runs through us directly, from the same records the platform already holds.
We issue driver operation cards for your vehicles as a service. Most fleet software reminds you one expired; we renew it.
No integration with Absher, Najm, Saher, Mudad/WPS, Tawakkalna, Elm or Fasah. Those interfaces are not open to us, and we would rather say so than imply otherwise.
Book a walkthrough with a team that knows Saudi fleet operations — in Arabic or English, whichever suits you.