How to choose an e-invoicing solution in Saudi Arabia: 10 questions to ask

Every VAT registered business in Saudi Arabia issues e-invoices now, so the question in most finance meetings has changed. It is no longer "do we have to?" but "which system do we buy?" The twenty fifth group of taxpayers, those whose revenues exceed SAR 187,500, start the integration phase on 1 February 2027, and many of them are comparing providers this quarter. The e-invoicing solution Saudi Arabia businesses can live with for the next five years is rarely the one with the smoothest demo.

Below are 10 questions to ask any vendor before you subscribe, a scoring table you can carry into the meeting, and the red flags that should end a sales call early.

First, what ZATCA actually requires

Knowing the requirement narrows the field fast. ZATCA runs e-invoicing in two stages. Phase 1, the generation phase, began on 4 December 2021 and requires you to produce structured electronic invoices, with a QR code on simplified invoices. Phase 2, the integration phase, began on 1 January 2023 and is being rolled out group by group. In Phase 2 your system must build the invoice as XML in UBL 2.1, sign it with a cryptographic stamp tied to your device CSID, and connect to the Fatoora platform so standard invoices are cleared and simplified invoices are reported.

One sentence on the authority's own page settles the biggest myth in this market. ZATCA states that taxpayers may choose any e-invoicing solution provider as long as the solution is compliant with the e-invoicing requirements, and that it will consider the taxpayer compliant even if the provider is not on its indicative list. That list exists to help you find vendors who passed its qualification conditions, not to license them. You can confirm the wording on the ZATCA e-invoicing page. The practical consequence matters: the obligation sits with your business, so verify the system yourself rather than trusting a badge.

Questions 1 to 4: compliance you can verify

Ask these in a live tenant, not against a slide deck. A vendor who cannot show the output in ten minutes is not ready.

1. Can it issue all four document types?

You need standard tax invoices for business buyers, simplified tax invoices for consumers, and credit and debit notes against both. Standard invoices go to ZATCA for clearance before you hand them to the buyer. Simplified invoices are reported after issuing. Ask to see one of each created in front of you, then ask to see the XML behind them.

2. Who holds the CSID, and what happens when a device changes?

The cryptographic stamp identifier is issued per device or per invoicing unit. Find out whether the certificate sits in your own ZATCA account or inside the vendor's, who renews it, and what the process is when you add a branch, replace a point of sale terminal or move to a new server. A system that cannot re-onboard a device without a support ticket will cost you sales hours later.

3. What happens when the connection to Fatoora fails?

Networks drop and platforms have maintenance windows. A serious system queues the invoice, keeps selling, and retries until clearance or reporting succeeds, with a visible list of anything still pending. Ask to see that queue. Then ask what the cashier sees on screen while clearance is pending, because that answer tells you whether the product was built for real counters.

4. Where is the data stored, and can you take it out?

Your invoices are tax records and you must be able to produce them for years. Ask where the data is hosted, how long records are retained, and whether you can export the full set as XML and PDF without asking anyone. Check the answer against the personal data rules you already follow for customer records.

Questions 5 to 7: how it behaves every day

Compliance is the entry ticket. What decides whether staff actually use the system is the daily flow, so test the ordinary path, not the edge case.

5. How many steps from quotation to cleared invoice?

Count the clicks yourself in the demo. If your sales team sends quotations, the invoice should be created from the accepted quotation with the customer, VAT number and line items already filled in. Re-typing the same details into a second system is where wrong VAT numbers and rejected invoices come from.

6. Are the Arabic documents genuinely right to left?

Many systems translate the interface and stop there. Look at a printed Arabic invoice: the layout direction, the number formatting, the customer name, the terms. Then look at the same invoice in English. Saudi buyers, auditors and government customers all ask for both, and fixing templates later is slow work.

7. Who can see and do what?

Decide before you buy who may issue an invoice, who may raise a credit note, and who may change a VAT setting. Ask whether roles are configurable, whether every change is logged with a user and a timestamp, and whether you can report on who issued what last month. Without that log, a disputed credit note becomes an argument instead of a lookup.

Questions 8 to 10: price, support and the exit

8. What exactly is in the price?

Get the full picture in writing: users, branches, invoice volume, the rate once you pass the included volume, onboarding, template changes and integration work. Then model it at twice your current invoice count, because a growing business pays the overage rate, not the headline rate. Compare the three year total, not the monthly figure.

9. What support do you get, in which language, and how fast?

An invoice that will not clear at the end of the month is an urgent problem. Ask for the support channel, the working hours, the committed first response time and whether the people answering work in Arabic. Ask what happens during Ramadan and the national holidays, when your volume peaks and support teams run short.

10. What does leaving look like?

The best time to negotiate the exit is before you sign. Ask how notice periods work, what you can export on the last day, whether historical invoices stay readable after the subscription ends, and who deletes your data afterwards. A vendor who answers this calmly is usually a vendor worth signing with.

Score the shortlist instead of trusting the demo

Three vendors will all say yes to everything. Give each answer a score out of 10, weight it, and the ranking usually settles itself. Here is a starting weighting for a Saudi SME entering the integration phase.

Red flags that should end the call

Any one of these is a reason to keep looking.

• The vendor claims the authority has approved, certified or licensed its system. No such status is granted to the software you buy.
• Nobody can show a cleared standard invoice in a sandbox during the meeting.
• The CSID lives in the vendor's own account with no documented way to move it.
• Per invoice pricing with no stated overage rate and no cap.
• No Arabic interface, Arabic invoice templates or Arabic speaking support.
• Your invoices cannot be exported without a paid service request.
• Access to historical invoices stops on the day the subscription stops.

Run a two week proof before you sign

A short structured trial answers more than another demo. Block two weeks, use your own data, and involve the person who will issue invoices daily. If you are working towards the February 2027 date, fit this inside a wider plan such as the 15 week Fatoora integration plan so the selection does not eat the implementation time.

1. Days 1 and 2: set up a sandbox, onboard one device and get a CSID.
2. Days 3 to 5: issue 20 invoices that look like your real ones, including your longest item list.
3. Days 6 to 8: break things on purpose. Use a wrong VAT number, a zero rated line, a discount and a credit note against a cleared invoice.
4. Days 9 and 10: export everything, open the XML, and reconcile the totals with your accounts.
5. Days 11 to 14: settle the commercial terms, the support response times and the exit clause.

Where Daftarix fits

Daftarix is business software for companies in Saudi Arabia, and its ZATCA e-invoicing module is built for Phase 1 and Phase 2. It issues standard and simplified tax invoices, adds the QR code to simplified invoices, builds the XML in UBL 2.1, signs it with a cryptographic stamp using your device CSID, and connects to the Fatoora platform for clearance. Documents are produced in Arabic and English with a right to left layout, VAT is applied at 15% in Saudi Riyals, and invoices can be raised from an accepted quotation so customer details carry across.

Use the 10 questions above on us as well, with your own invoices and your own edge cases. Book a demo and bring the list.

Frequently asked questions

Does the authority officially approve any e-invoicing system?

No. ZATCA publishes an indicative list of solution providers that passed its qualification conditions, but states that taxpayers may use any provider whose solution complies with the e-invoicing requirements, listed or not. The compliance obligation stays with your business, which is why you should verify the output yourself.

Does a small business really need Phase 2 integration?

It depends on your group. ZATCA announces each group separately, and the criteria for the twenty fifth group cover taxpayers with revenues above SAR 187,500, with integration starting 1 February 2027. The criteria are set out in the published decision, so check your own revenue against it rather than assuming.

Can we keep issuing invoices from a spreadsheet?

Not in the integration phase. The invoice has to be generated as structured XML, stamped cryptographically and sent to the Fatoora platform, which a spreadsheet cannot do.

Should we buy a full business system or a dedicated invoicing tool?

Ask where your invoices begin. If they start from quotations, customer records or support tickets, one connected system removes the double entry that causes most rejected invoices. If invoicing truly stands alone in your business, a focused tool can be enough.