Quick summary
Saudi e-invoicing came in two phases: the first requires issuing invoices electronically in a structured format instead of paper or a Word file, and the second (integration) requires your system to talk to the authority's platform technically. The practical surprise: phase two is not a setting you configure but a change to your system's structure — an unbreakable sequential numbering, a cryptographic stamp, and archival in a specific format. The biggest decision is whether to build the integration yourself or go through an approved provider — and for most businesses, a provider is cheaper and safer.
What actually changes in your system
| Aspect | Before | What becomes required |
|---|---|---|
| Invoice numbering | An internal number that can be edited or deleted | An unbroken sequence with no deletions — a deletion becomes a credit note |
| Invoice format | PDF or print | A machine-readable structured format, plus a human-readable copy |
| Integrity | Nothing | A cryptographic stamp proving the invoice was not altered after issue |
| Archival | In your database | Retained for defined periods in a retrievable format |
| Tax | Sometimes computed at display time | Stored with the invoice — inclusive prices decomposed precisely |
The mistake that forces a rebuild
The most dangerous flaw we see in custom systems is deleting or editing invoices after issue. Many systems let a user delete an order or change its amount — acceptable before invoicing, destructive after. The rule we build on: an issued invoice is an untouchable record, and any correction is a new credit or debit note linked to it. Fixing this later means redesigning the orders and invoices tables together.
The second mistake is computing tax at display time rather than storing it. If your prices are tax-inclusive, decomposing them later with a floating calculation produces halala-level differences that accumulate and surface at reconciliation. Store net, tax and total as fixed values at the moment of issue.
Build it or use a provider?
Going through an approved invoicing provider is faster and lower-risk for most businesses: your system sends invoice data, the provider handles format, stamping and transmission. A direct integration earns its cost only when your invoice volume makes subscription fees exceed the build, or when you have a requirement no provider supports.
We build custom business systems that are invoicing-ready from the start rather than patched later.
Important: this article explains what changes in your software. It is not accounting or legal advice. Requirements, deadlines and targeted groups change — consult your accountant and the authority's official source before deciding anything.
