SoftwareUAE & KSA7 min read
SRS Template for UAE and Saudi Software Projects
Free SRS template for UAE and Saudi software projects. Covers Arabic and RTL, e-invoicing, PDPL and local integrations so developers can quote accurately.
By Quickship Editorial Team · Published
Looking for the software itself? See our custom software development Dubai.
An SRS template is a fill-in document that lists what your software must do, who uses it, what it connects to and how you will accept it as finished. For a business in the UAE or Saudi Arabia, a good one also covers Arabic and right-to-left screens, e-invoicing, personal data and the local platforms your team already uses. Give a developer that document and they can quote a fixed scope instead of guessing.
Most templates online are generic. Nothing in the top results covers PDPL, e-invoicing or how a GCC developer prices from a document. This post fills that gap with a template you can copy.
What goes in an SRS template for a GCC project?
A solid SRS has nine parts. The structure follows the usual IEEE-style outline, which you can see in the NASA software engineering handbook and the open Markdown SRS template on GitHub. The right-hand column shows what a GCC buyer should add.
| Section | What it holds | GCC addition |
|---|---|---|
| 1. Purpose and scope | The problem, what is in, what is out | Which entities and countries (UAE, KSA, or both) |
| 2. Users and roles | Who logs in and what each role can do | Arabic-speaking staff, drivers, customers |
| 3. Functional requirements | Numbered features | Workflows tied to local steps, such as COD collection |
| 4. Non-functional requirements | Speed, uptime, security, browsers | Arabic and RTL, data location |
| 5. Integrations | Systems it talks to, required or optional | Marketplaces, couriers, accounting, e-invoicing |
| 6. Data and privacy | What personal data is stored and why | PDPL in the UAE and in Saudi Arabia |
| 7. Reports and documents | Invoices, labels, exports | Tax invoice fields, bilingual output |
| 8. Acceptance criteria | How you test each requirement | Test with real Arabic and English data |
| 9. Out of scope and open items | What you are not buying yet | Items waiting on a regulator or a vendor |
How do you write requirements a developer can quote against?
Write each requirement as one numbered sentence a tester can pass or fail. A developer can only price what they can count, so vague lines like "easy to use" give you a vague quote.
Use this method:
- Give every requirement an ID, such as REQ-014.
- Tag it Must, Should or Could. Must means you cannot go live without it.
- Write one sentence in the form "The system shall...".
- Add an acceptance test: what a person does and what they should see.
- Mark integrations as Required or Optional, with the system name.
- List open questions separately, with an owner and a date.
Here is a hypothetical example for a Dubai courier company:
- REQ-021 (Must): The system shall let a dispatcher mark a parcel as delivered with cash collected and enter the amount.
- Acceptance test: The dispatcher opens a parcel, enters AED 250 collected, and the driver's cash balance rises by AED 250.
- REQ-022 (Should): The system shall flag any COD amount that differs from the order value.
- Acceptance test: Enter AED 240 against a AED 250 order. The parcel appears on a mismatch list.
Notice there is no "fast" or "user friendly". Each line can be checked in a minute.
What GCC-specific requirements should you add?
Add requirements for language, tax invoicing, personal data and local integrations. These four are where GCC projects most often go over budget, because nobody wrote them down at the start.
Arabic and right-to-left screens
Say exactly what you need. "Arabic support" can mean translated labels, or it can mean full RTL layouts, Arabic invoices and Arabic search. Write which screens, which documents and which users. Also say which language the data is entered in. A customer name typed in Arabic must still print correctly on a label and an invoice.
UAE e-invoicing
The Ministry of Finance has published timelines for the UAE e-invoicing system. On the MoF announcement:
- Businesses with revenue of AED 50 million or more go live on 1 January 2027.
- Businesses below AED 50 million appoint a provider by 31 March 2027 and go live on 1 July 2027.
- Government entities go live on 1 October 2027.
The appointment deadline for the larger group was amended after the first announcement, so check mof.gov.ae for the current dates. The page also says issuers and recipients must each appoint an Accredited Service Provider (ASP). The Ministry lists approved companies on its accredited provider register.
What this means for your SRS: write a requirement for sending invoices to, and receiving them from, your chosen provider. Name the provider, or list it as an open item. Ask your developer to read the provider's technical documents before they quote. Also read the MoF e-Invoicing Guidelines for the data you will need to capture.
Saudi e-invoicing (ZATCA)
ZATCA's guide on getting ready for Phase 2 describes two phases. Phase one is generation: creating and storing e-invoices in the specified format, which is XML, or PDF/A-3 with embedded XML. Phase two is integration with the Fatoora portal.
For your SRS, state which phase your business is in and which wave applies to you. Check that on ZATCA's site, because it can change. Then write separate requirements for invoice generation, storage and the integration. Mark the integration Required.
Personal data
The UAE Personal Data Protection Law is Federal Decree-Law No. 45 of 2021 and came into force on 2 January 2022, according to u.ae. The same page notes the law text is available as a PDF in Arabic only. DIFC and ADGM have their own data laws. Saudi Arabia has its own Personal Data Protection Law too. Ask a lawyer how both apply to you.
Do not try to write legal rules into the SRS. Write what the system must do. For example:
- List every personal data field you store (name, phone, Emirates ID number, address) and why.
- Record whether a customer opted in to WhatsApp messages, and when.
- Let an admin export or delete a customer's record on request.
- Limit who can see which fields, by role.
- Name where the data is hosted.
Local integrations
List every system the software must connect to and mark each Required or Optional. Typical GCC examples are Amazon.ae and noon seller accounts, Shopify, Salla or Zid stores, courier APIs, your accounting tool and a payment gateway. For each one, say what data moves, which direction, and how often. Developers can only confirm effort once they see the other system's API documents, so ask who will supply access.
Copy-and-fill SRS skeleton
Paste this into a document and fill it in.
SRS: [Project name] Version: 0.1 Date: [date]
Owner: [name, role] Markets: [UAE / KSA / both]
1. Purpose and scope
Problem we are solving:
In scope:
Out of scope:
2. Users and roles
Role | What they do | Language | Device
3. Functional requirements
ID | Priority (Must/Should/Could) | Requirement | Acceptance test
4. Non-functional requirements
Languages and RTL:
Number of users and records (our best estimate):
Hosting location:
Browsers and devices:
5. Integrations
System | Required/Optional | Data moved | Direction | Who gives API access
6. Data and privacy
Personal data fields | Why we need it | Who can see it | Retention
7. Reports, invoices and documents
Name | Fields | Language(s) | Format
8. Acceptance
Who signs off:
Test data we will supply:
9. Open items
Question | Owner | Due date
Only fill in numbers you know. If you do not know the number of users, write "estimate, to be confirmed" instead of inventing one.
How does a developer price from your SRS?
A developer reads each Must requirement, checks the integrations and open items, then estimates the work. Clear requirements allow a fixed-scope quote. Unclear ones push the vendor to quote time and materials, or to add a large safety margin.
Expect questions back. Good ones include "Who supplies the API keys?" and "Is the Arabic invoice a separate template?" That is a good sign. It means someone read the document.
If you want a team to turn the SRS into a quote, Quickship builds custom software for logistics, e-commerce and trading businesses in the UAE and Saudi Arabia, priced on quote. Bring your draft, even if it is rough.
What mistakes make an SRS useless?
These are the common ones:
- Mixing "what" and "how". Say what the system must do, not which database to use, unless you have a reason.
- No priorities. If everything is a Must, the quote covers everything, and so does the price.
- Skipping the open items. An unanswered question about e-invoicing will come back as a change request.
- Writing Arabic as one line. Specify screens, documents and data entry separately.
- No acceptance tests. Without them, "done" is an opinion.
- Copying an overseas template unchanged. It will miss VAT invoice fields, local couriers, COD and local data rules.
Frequently asked questions
How long should an SRS be for a small business system?
Length matters less than clarity. A simple order or quote tool can fit in 8 to 15 pages if every requirement is numbered and testable. A long document full of vague sentences is worse than a short one with clear acceptance criteria.
Do I need an SRS if I only want a mobile app?
Yes, but you can keep it shorter. Screens, user roles, backend data, push notifications, Arabic support and the integrations still need to be written down. Without them, two developers will quote very different things for the same idea.
Who owns the SRS, the business or the developer?
The business should own it, even if the developer helps write it. Agree in the contract that the document is yours and can be taken to another vendor. Check the intellectual property wording with your lawyer.
Should the SRS name the e-invoicing provider?
If you have already chosen one, yes. If not, list it as an open item with an owner and a date. In the UAE, businesses appoint an Accredited Service Provider, and the Ministry of Finance publishes the register of accredited providers.
Can I change the SRS after the developer starts?
Yes, but treat each change as a new numbered requirement and ask for the effect on cost and timeline in writing. Keep a version log at the top of the document. This stops small changes from turning into a dispute later.
Sources
- UAE Data Protection Laws (u.ae)
- Ministry of Finance: Ministerial Decisions on e-invoicing scope and timelines
- Ministry of Finance: Accredited e-invoicing service providers
- NASA Software Engineering Handbook: SRS contents
- SRS Template (Markdown, IEEE 830 and ISO/IEC/IEEE 29148)
Rules and fees in the UAE and Saudi Arabia change. This guide reflects the sources above on 20 November 2026. Check the official source before acting on it.
