A software patent arrives at a Gulf filing desk with a familiar collection of claims: a computer-implemented method, a processor-and-memory system, and a non-transitory storage medium. The United States Patent and Trademark Office (USPTO) has allowed the claims after years of examination. The applicant wants the same protection in Saudi Arabia and the United Arab Emirates (UAE). From a foreign filing coordinator’s perspective, retaining the US claim set appears efficient. From a patent prosecutor’s perspective, the more pressing question is whether the claims describe the technical invention in terms that can survive scrutiny under the law of each destination country.
The distinction matters because a granted US patent supplies neither a Saudi patent nor a UAE patent. Article 4 of UAE Federal Law No. 11 of 2021 expressly treats UAE industrial property rights as independent of those obtained elsewhere. Saudi Patent Law Articles 43 to 45 establish their own patentability requirements and excluded subject matter. A US allowance may help explain the invention and the relevant prior art, but it does not decide the legal status of the claims in either jurisdiction. [1, 2]
Why US Patent Prosecution Success Can Be Misleading Abroad
US software protection begins with 35 U.S.C. Section 101 and the judicial exceptions developed through decisions including Alice Corp. v. CLS Bank and Mayo Collaborative Services v. Prometheus Laboratories. The USPTO’s Manual of Patent Examining Procedure (MPEP), Section 2106, assesses the statutory category, whether a claim recites a judicial exception and, where applicable, whether the claimed additional features integrate the exception into a practical application or supply significantly more. The USPTO updated its subject-matter eligibility guidance in December 2025 to address technological improvements, while preserving the governing Alice/Mayo framework. [3, 4]
US eligibility remains a demanding enquiry. A business objective performed on generic computer hardware may fail Section 101 even when expressed in system or storage-medium form. Equally, a claim addressing an improvement in network operation, computer functionality or another technical field may present a different eligibility analysis. Once granted, the patent reflects the application of US law to the particular claims and prosecution record. The foreign practitioner still needs to examine how the invention is characterized under the chosen national statute. [3]
This is where an apparent drafting shortcut can prove expensive. A US claim may define a commercially attractive result in broad terms, leaving most implementation details to the specification. If the Gulf application faces an objection directed to abstract subject matter, claim support or a particular claim category, the applicant may need a narrower technical formulation. That formulation must already be supported by the filed disclosure. New explanations developed after examination begins cannot reliably replace missing original teaching.
Software Patent Protection in the UAE: What the Law Says
Article 7(1)(d) of UAE Federal Law No. 11 of 2021 lists software, plans, rules, methods for carrying out commercial activity, purely mental activity and games among matters excluded from patent and utility-certificate protection. Article 5 separately requires novelty, inventive step and industrial applicability. The law’s definition of an invention in Article 1 refers to an innovative idea in a technical field concerning a product or manufacturing method that yields an addition or solution to a problem in that field. These provisions must be read together. [1]
The express reference to software is significant, yet it would be unsafe to turn that language into an unsupported rule that every invention involving software must fail in the UAE. A computer-controlled physical apparatus and a program claimed in isolation raise different questions about what constitutes the invention. The statute supplies the exclusion and the general patentability framework; it does not, by itself, establish that UAE examiners apply the precise US Alice/Mayo test or the European Patent Office’s technical-effect methodology. Neither approach should be attributed to UAE examination practice without identifiable supporting authority.
Disclosure quality introduces a second, independent concern. Article 11(5) of the UAE law requires a description enabling a specialist to realize the invention. Article 11(7) requires protection elements to be clear, concise and supported by the description. The Executive Regulations, Cabinet Resolution No. 6 of 2022, set out claim-drafting rules in Article 22: claims relate to products or methods, independent and dependent claims have prescribed forms, and patent applications are limited to 50 claims. Article 26 prevents amendments introducing features outside the original disclosure and applies that principle expressly to national filings of Patent Cooperation Treaty (PCT) applications. [1, 5]
For an international software portfolio, these are practical filing considerations. A boilerplate hardware claim may not supply the necessary technical detail. A broad dependent-claim structure may need restructuring. Technical features that appear only in inventors’ development documents cannot be imported into filed claims unless the application as originally submitted supports them. Counsel should also check the precise dependency language, since Article 22 regulates references to preceding claims and more complex dependencies. [5]
Software Patentability in Saudi Arabia: Key Legal Considerations
Saudi Patent Law Article 43 requires an invention to be new, inventive and industrially applicable. Article 44 addresses novelty, inventive step and industrial applicability. Article 45 excludes discoveries, scientific theories and mathematical methods, as well as commercial schemes, rules and methods, purely mental activities and games. Unlike UAE Article 7(1)(d), the Saudi statute does not separately name software in that list. This difference in statutory wording warrants attention, but it does not settle the outcome for every computer-implemented claim. [2]
A Saudi claim directed to arranging a loan, calculating a price or ranking customer transactions could raise questions under the exclusion concerning commercial methods and under the substantive patentability provisions. By contrast, a claim whose disclosed contribution concerns data transmission, memory architecture, industrial sensing or computer control invites analysis of the technical subject matter actually claimed. These are examples of issues to assess against the statutory text, not established categories of Saudi acceptance or refusal without verified examination records.
Saudi filing also has a procedural feature that foreign prosecution teams sometimes underestimate. The WIPO PCT Applicant’s Guide identifies Arabic as the language of national-phase proceedings and specifies rules for scientific terms and abbreviations. Under the guide’s SA.04 instructions, scientific terms receive both original-language and Arabic treatment at their first occurrence, with particular bilingual treatment in the claims. Defined software terminology, interface names and network protocol expressions therefore deserve dedicated technical translation review. [6]
A translation audit is especially important when a specification uses a term consistently across method, system and computer-readable-medium claims. Translating the same technical feature differently in separate places can create avoidable ambiguity. The national-phase translation should preserve antecedent relationships and the distinctions between functional actors, data structures and control steps. This is a quality-control recommendation founded on the formal translation rules, not a claim about how frequently such errors lead to refusal.
Software Patent Claim Drafting: The Risks of Copying US Claims
US filings often pursue parallel claims to a method, a computing system and a non-transitory computer-readable storage medium. There can be legitimate reasons for that architecture: the categories may describe different infringing acts or products. But a successful US format is not a substitute for examining the categories available and appropriate under local law. UAE Article 22 speaks expressly of claims relating to products or methods. Saudi practice must be considered under its own legislative and administrative framework. [5]
The practical review should begin with the underlying inventive concept. Identify the concrete processing architecture, the relationship between its components, and any demonstrable change in the operation of the technical system. Then ask which parts of that concept were actually disclosed on the relevant filing date. The claims can be compared with the relevant local provisions, but the description must be assessed with equal care. A claim amendment can only work with what the patent application already teaches.
There is a further portfolio-management question. A US examiner’s amendments may have narrowed the independent claims to a particular implementation. Importing those amendments mechanically could abandon alternatives still relevant to a UAE or Saudi application. Conversely, reverting to broad originally filed claims may invite objections that the US prosecution had already exposed. Neither automatic copying nor automatic re-broadening constitutes a reliable strategy. The decision should reflect available disclosure, prior art, timing and each office’s legal requirements.
A Hypothetical Fintech Example: Where the Invention Actually Resides
Assume an applicant holds a US patent for a transaction authentication platform. One claim recites a processor receiving payment data, applying a machine-learning risk model and producing an approval decision. The specification also discloses a particular device-attestation exchange, distributed replay protection and a synchronization mechanism that prevents duplicate authentication requests when several nodes receive the same transaction. This is a hypothetical illustration, not a summary of a reported Saudi or UAE examination decision.
The broad claim presents a commercial outcome and an algorithmic assessment. A careful local review would identify whether the narrower attestation, replay-protection and synchronization mechanisms define a technical contribution supported by the description. If so, counsel could examine whether claims directed to those mechanisms are appropriate in the relevant jurisdiction. The review must also establish novelty and inventive step over the prior art. Technical vocabulary alone cannot establish either requirement, and a more detailed claim may still be unpatentable for other reasons.
Suppose instead that the specification mentions only that “network requests are optimized” without describing any mechanism for doing so. A later claim reciting a deduplication protocol may then encounter an original-disclosure problem. UAE Article 26 prohibits new features beyond the filed disclosure; Saudi Implementing Regulations Article 34 similarly bars amendments exceeding what was disclosed at filing. The procedural record in the United States cannot repair that factual omission in the shared application text. [5, 7]
A Practical Review Before National Filing
A disciplined review can be performed without rewriting the entire patent family. Start by mapping every independent claim to the specific technical operations disclosed in the specification. Separate business objectives and desired results from the mechanisms that deliver them. Identify potential local subject-matter issues and determine whether alternatives can be supported without adding new matter. Check claim dependencies and claim categories against the relevant implementing rules. Finally, compare the international disclosure and any US amendments with the Arabic terminology planned for Saudi proceedings.
That exercise produces a useful instruction package for local counsel: a marked claim set, support references for important limitations, a short analysis of exclusions and available fallback features, and a list of terms requiring technical consistency. The local practitioner can then evaluate the legal consequences in the jurisdiction concerned. The work is particularly worthwhile for patents claiming AI-assisted decision-making, fintech workflows and networked platforms, where the distance between a business result and a technical implementation can be considerable.
Conclusion
Effective software patent protection in Saudi Arabia and the UAE begins with what the inventors built and what the specification disclosed. US prosecution can illuminate the claimed invention, particularly through its prior-art analysis and technical arguments. However, Saudi and UAE prosecution still require an independent assessment under the applicable national laws.
For sophisticated software portfolios, a focused claim and disclosure review before filing can offer more control than attempting to reconstruct the technical invention after an objection arrives. Applicants should assess local exclusions, claim categories, disclosure support and translation requirements before relying on a US claim set across multiple jurisdictions.
Sources and Further Reading
- [1] UAE Federal Law No. 11 of 2021, Articles 1, 4, 5, 7 and 11 (WIPO Lex)
- [2] Saudi Patent Law, Articles 43 to 46 (WIPO Lex)
- [3] USPTO, MPEP Section 2106, Patent Subject Matter Eligibility
- [4] USPTO, December 2025 Updates to Subject-Matter Eligibility Guidance
- [5] UAE Cabinet Resolution No. 6 of 2022, Articles 22 and 26
- [6] WIPO PCT Applicant’s Guide, Saudi Arabia, Sections SA.02 to SA.04
- [7] Saudi Implementing Regulations, Article 34 (2019 Amended Text)
