Software Development Company Saudi Arabia: Buyer's Guide

A good software development company in Saudi Arabia builds Arabic-first screens, tells you in writing where your data is hosted, and can show how your invoices will connect to ZATCA's FATOORA platform. If a vendor can't answer those three points clearly, keep looking.

This guide gives you the checks, a table of questions to ask, and a short buying process.

A note on sources. Official ZATCA, SDAIA, NCA and CST pages are the final word. The e-invoicing facts below come from advisory firms and guides that summarise ZATCA's rules, so we link them and tell you to confirm on zatca.gov.sa before you sign anything.

Why is ZATCA readiness the first thing to check?

Because the next Phase 2 deadline is close. Wave 25 was announced on 24 July 2026. It covers taxpayers with VAT revenue above SAR 187,500 in any of 2022, 2023, 2024 or 2025, with a deadline of 1 February 2027, according to FBS Advisory. Today is 6 November 2026, so that is under three months away.

Here is how the earlier waves looked.

Say a Jeddah trading company had VAT revenue of SAR 200,000 in 2025. On these figures it could fall into Wave 25. If it wants new software, that software must handle e-invoicing from day one. Check your own position with ZATCA, because the thresholds apply to specific years and your notice is what counts.

What does "ZATCA-ready" actually mean?

It means the system can create, sign, send and store invoices the way ZATCA's Phase 2 rules require. Many vendors write "ZATCA-ready" on their sites without saying what is behind it. According to FBS Advisory, integration involves:

• XML in the UBL 2.1 structure, or PDF/A-3 with embedded XML
• a cryptographic stamp on each invoice
• a UUID and a hash linked to the previous invoice
• a QR code
• a connection to ZATCA's FATOORA platform through an API

Two flows matter, and your vendor should explain both.

• Standard invoices (B2B and B2G) use clearance. They are sent to ZATCA in real time and cleared before you share them with the buyer, per Origami.
• Simplified invoices (B2C) are reported to ZATCA within 24 hours, per Luba Global Ventures.

Phase 2 also has no manual portal route that replaces API integration, according to Flick. So "we'll upload the invoices by hand" is not a plan.

Penalties are graduated. e-invoice.app reports that a missing QR code, missing fields or poor storage start at SAR 1,000 and can reach SAR 40,000, and that the scale sits in a ZATCA guideline published in Arabic only. Ask a Saudi tax adviser to confirm the current figures for your case.

Questions that test the claim

• Is the invoicing part already integrated with FATOORA, or will it be built for us?
• Who updates it when ZATCA changes the technical rules?
• Can we see a cleared standard invoice and a reported simplified invoice from a test environment?
• What happens to an invoice if the ZATCA connection is down?

Does the software really need Arabic support?

Yes, and "we have an Arabic translation" is not enough. Guides to the rules say invoices must carry Arabic as the primary language, with English allowed alongside but not on its own. Confirm that point on zatca.gov.sa.

Arabic support has several layers. Check each one.

• Right-to-left layout. The whole screen should mirror, not just the text. Tables, forms and menus all need to flip.
• Arabic and English data in one record. A customer name in Arabic should print correctly on the invoice and show up in search.
• Numbers and dates. Agree how you want them shown, and whether Hijri dates are needed anywhere.
• Saudi addresses. If your customers use the Saudi National Address, the form should capture it properly.
• Staff and support. Your team in Riyadh, Jeddah or Dammam should be able to get help in Arabic if they need it.

A quick test: ask the vendor to put one of your real Arabic customer names through a demo invoice, then print it as a PDF. Broken letters or reversed text show up straight away.

Where should your data be hosted?

Ask the vendor to tell you in writing: which cloud, which region, where backups sit, and which subcontractors can touch the data. There is no single answer that fits every business. Requirements depend on the kind of data, your sector and your customers, and they change over time.

Take it in this order.

1. Decide what data the system will hold: customer details, staff records, invoices, shipment data.
2. Check what applies to you on the official sites: sdaia.gov.sa for the Personal Data Protection Law (PDPL), nca.gov.sa for cybersecurity, and cst.gov.sa for cloud and telecom rules.
3. Ask the vendor to say which of those rules they work to, and how.
4. Ask a Saudi lawyer if your sector, such as government work or financial services, adds stricter rules.

Be careful with vendors who say "PDPL-compliant" and stop there. That is a claim, not an explanation. Ask what they do about consent, access, retention and deletion.

If your software sends WhatsApp messages, the same care applies. Message only contacts who opted in, and keep a record of that opt-in.

How do you choose a software development company in Saudi Arabia?

Choose it like a supplier, not a logo. Most search results are vendor lists where each vendor ranks itself first. A list won't tell you if a team can build your invoice flow, so run your own process.

1. Write a one-page brief. Say what the software must do, who uses it, how many invoices or orders it handles, and which systems it must connect to, such as Salla, Zid, noon or your accounting tool.
2. Mark the compliance needs. Put ZATCA, Arabic and data hosting at the top of the brief, not at the bottom.
3. Shortlist three vendors. Ask each the same questions, in writing.
4. Ask for a working demo. A slide deck is not a demo. Ask to see Arabic screens and a test invoice.
5. Speak to a reference. Ask for a client with a similar business who will take your call. Don't rely on logos.
6. Fix the scope in phases. Start with the part that has a deadline, such as invoicing, and add the rest later.
7. Sign a contract that covers the after-launch period. ZATCA rules change, so ask who maintains the integration.

What should you ask a vendor? A comparison table

Use this table in your calls. A strong vendor answers each row without hesitation.

What mistakes do Saudi buyers make most often?

• Buying on price alone. A cheap quote that leaves out ZATCA integration costs more once you add it.
• Treating Arabic as a final polish step. Layout and data problems are expensive to fix late.
• Leaving ZATCA until the deadline month. Testing and fixes take time, so start early.
• Accepting a vague hosting answer. If it isn't in writing, you can't rely on it.
• Skipping the ownership clause. If the vendor owns the code, switching later gets hard.
• Forgetting existing systems. Many older systems need an upgrade or a middleware layer to produce compliant XML, apply the stamp and connect to the API, per Origami.

Where does Quickship fit?

Quickship is a software company based in Dubai, serving the GCC. We build custom software on quote for logistics, e-commerce and trading businesses, and you can read more on our software development page. We are a technology company only. We don't ship, store or clear goods.

If you talk to us, expect the same questions from this guide. Bring your brief, your list of connected systems and your ZATCA wave notice. Ask us about Arabic, data hosting and invoicing in writing, and judge the answers the way you would any other vendor's.