Quick answer
An electronic invoice is one issued by an electronic system in a structured format and stored there, not a paper slip or a hand-typed PDF. A small store selling to consumers normally issues a simplified tax invoice carrying a QR code, a sequential number and the seller's details, and all of that is built into the store rather than a separate program. What stays with you: registering for VAT once you reach the threshold, and entering your business details accurately. Thresholds and phase two timing are set by the Zakat, Tax and Customs Authority (ZATCA), so take them from its website.
What e-invoicing is, and simplified versus standard invoices
ZATCA requires VAT-registered businesses to issue invoices electronically in two phases. Phase one, the generation phase, requires invoices to come from an electronic system that blocks editing after issue, stores them, and prints a QR code on simplified invoices. Phase two, the integration phase, requires connecting that system to the authority's platform so invoices are reported or cleared, and it is rolled out to businesses in waves, with the authority notifying each business ahead of its date. A business that does not know its wave asks the authority, not the developer.
The difference between the two invoice types decides what gets built in your store. A simplified tax invoice is issued to an individual consumer, which is the case for most small online stores: it carries the seller's name and VAT number, the date, the total and the VAT amount, plus a QR code that a customer or inspector can read with the authority's app. A standard tax invoice is issued to a VAT-registered business and additionally carries the buyer's name, VAT number and address so it can reclaim the tax. If you sell to companies, the store must ask at checkout whether the customer wants an invoice in their company's name. Most small stores need only the first type; some need both, and settling that before the build saves rework.
What gets built into the store
E-invoicing is not a button added at the end of the project. It is four parts that enter the store's design from the start:
- Automatic issue: when payment is confirmed the invoice is generated from the order data itself, with no manual entry, and sent to the customer as a link or file in their account, by email or by WhatsApp.
- QR code: generated for every simplified invoice, carrying the seller's name, VAT number, timestamp, total and VAT amount in the format the authority specifies, so its app reads it without error.
- Sequence: a consecutive number that never skips, repeats or gets reused, even when an order is cancelled. Cancellations and returns do not delete an invoice; they issue a credit note that references it.
- Storage: the invoice is kept in its final form, never edited after issue, and remains retrievable and exportable for the period the regulations require, with a backup outside the main server.
Phase two adds a fifth part: connecting to the authority's platform with a digital signature and a certificate issued by the platform to your system, and reporting simplified invoices within the required window. We cover the technical integration in detail in our ZATCA integration article; this one stays on what a small store owner needs to understand before ordering.
What stays with the store owner
| Item | Who does it | Why it cannot be delegated |
|---|---|---|
| VAT registration | The owner, through the authority's portal | Depends on your actual and expected revenue; the threshold is on the authority's website |
| VAT number, business name and address | The owner, in the admin panel | Printed on every invoice and QR code; one wrong character invalidates the invoice |
| Prices inclusive or exclusive of VAT | The owner | A pricing decision that affects display and line-level tax calculation |
| Return policy and credit notes | The owner decides, the store executes | When to issue a credit note and when to refuse a return is a commercial decision |
| Periodic VAT return | The owner or their accountant | The store gives you the invoice report, but filing is your responsibility |
| Tracking your phase two wave | The owner | The authority notifies the business, not the developer; you pass us the date |
How we guarantee it in the store package
In the online store package we build at a published price, the simplified invoice is part of the store rather than a paid add-on: it is issued at payment with a sequential number and QR code, stored and sent to the customer, and the admin panel lets you issue a credit note on a return and export an invoice report for any period to hand to your accountant. You enter the business details in the panel and we review them with you before launch, because most errors come from there.
Phase two integration with the authority's platform depends on your wave and activity, so we price it after a free analysis session and write its value and duration into the contract under custom business systems. If you already have an accounting system you want to remain the source of invoices, we connect the store to it rather than duplicating invoices in two places. The rest of the packages are on pricing.
Common mistakes
- Issuing invoices from Word or Excel after each order. That is not electronic in the authority's sense, carries no valid QR code, and exhausts the owner with every sale.
- Editing an invoice after issue to fix a mistake. Issued invoices are never edited; the correction is a credit note followed by a new invoice.
- A wrong VAT number or a business name that differs from the registration. It appears on every invoice and QR code and surfaces at the first audit.
- Deleting invoices of cancelled orders, which breaks the sequence. Cancellation is documented with a note and the sequence stays intact.
- Treating the payment gateway's receipt as the invoice. A payment notification is not a tax invoice.
- Waiting for the phase two notice before asking. Ask the authority about your business's position today.
