EPO Software Patents: The Technical Character Requirement Explained

Why "software patent" is a misleading phrase in Europe

Businesses often ask whether they can obtain a "software patent" in Europe. The honest answer is that the European Patent Office does not issue patents for software in the abstract, yet it grants many patents every year for inventions that happen to be implemented in software. The distinction turns on how the invention is characterised rather than on whether code is involved. Understanding that distinction early saves a great deal of wasted drafting effort, and it shapes how you should frame an invention before you file. For the broader European patent route overview, see the EU patents pillar; this guide drills into the specific question of software and computer-implemented inventions.

A first point of orientation: the EPO is not an EU institution. It operates under the European Patent Convention, a treaty whose membership is wider than the European Union. So an "EPO software patent" is governed by the EPC and the Boards of Appeal case law, not by EU directives or the Court of Justice of the European Union. Keep this in mind when reading the EU patents overview, because the European patent route via the EPO sits alongside, and is distinct from, the EU's own instruments.

The Article 52 "as such" exclusion

Article 52(2) EPC lists things that are not regarded as inventions, and among them are "programs for computers". Crucially, Article 52(3) qualifies the exclusion: these items are excluded only "as such". A computer program claimed in the abstract, as a set of instructions divorced from any technical effect, falls within the exclusion. But the moment a claimed invention produces a further technical effect that goes beyond the ordinary physical interactions between the program and the computer, it escapes the "as such" bar and becomes eligible for examination on its merits.

In practice the EPO applies a low threshold at the Article 52 "invention" stage. Almost any claim that recites technical means, such as a computer, a processor or a network, clears the first hurdle. The real contest happens later, at the inventive-step stage, which is where most software and artificial-intelligence applications succeed or fail.

Technical character and the COMVIK approach

The organising idea across EPO practice is technical character. An invention must solve a technical problem by technical means in a way that is new and inventive. When a claim mixes technical and non-technical features, as software claims almost always do, the EPO uses what is commonly called the COMVIK approach (named after a Board of Appeal decision). Under it, features that do not contribute to the technical character of the invention are not taken into account when assessing inventive step. Instead, non-technical aims can be handed to the skilled person as part of the problem to be solved, and only the technical implementation is weighed for inventiveness. The Enlarged Board of Appeal has since endorsed this framework in the context of computer-implemented simulations, so it is settled rather than contested practice.

The consequence is significant. A clever business method, a pure mathematical scheme or an administrative rule, however novel, earns no inventive-step credit on its own. What can be patentable is the technical solution to the technical problems that arise in implementing it, for example a data-processing method that improves memory use, reduces bandwidth, controls a physical process or enhances the internal functioning of the computer. For machine learning and artificial-intelligence inventions the same logic applies: a mathematical model is non-technical in itself, but a specific technical application or a technical implementation that produces a further technical effect can carry inventive step. The cross-jurisdiction discussion of these questions lives at the AI and IP hub.

How this differs from the US position

It is tempting to assume Europe and the United States ask the same question, but they do not. In the US the relevant enquiry runs through the Alice/Mayo framework: US examiners and courts ask whether a claim is directed to an abstract idea, and if so whether it contains an "inventive concept" that amounts to significantly more than the abstract idea itself. Eligibility and the abstract-idea exception dominate the analysis, and much of the fight happens at the subject-matter stage, including during prosecution before the patent office.

The EPO, by contrast, rarely refuses at the Article 52 "invention" stage. It admits the claim readily and then does the heavy lifting through the technical-character filter at the inventive-step stage. So a claim can pass the European gate and still fail because its only inventive contribution is non-technical, while the same claim might be attacked in the US as an ineligible abstract idea. The practical upshot is that a single specification often needs different emphasis for the two systems, and a drafting strategy tuned only to Alice may leave a European application weaker than it should be.

Costs, timing and next steps

Official fees apply to a European patent application, and the amounts and the procedural time limits are reviewed periodically, so confirm the current figures and deadlines directly with the EPO or with local counsel rather than relying on a fixed number quoted online. Timeframes from filing to grant vary considerably with the technology and the examination backlog, so treat any single duration as indicative only.

IPEnvoy is not a law firm and does not provide legal advice; this is general information. Confirm the current position with the EPO and a qualified local IP professional before you act. If it would help, IPEnvoy can introduce you to a vetted European patent attorney experienced in computer-implemented and AI inventions, so your application is framed for technical character from the first draft.