You are using an outdated browser and your browsing experience will not be optimal. Please update to the latest version of Microsoft Edge, Google Chrome or Mozilla Firefox. Install Microsoft Edge

November 28, 2011

Business Methods and Computer Programs: Patentable?

Informed Counsel

In the last couple of years the U.S., the U.K., and Europe have been considering whether business methods and computer programs can be patentable. A patent typically protects an invention that is new, not obvious, and capable of industrial application. So why is there controversy surrounding business methods and computer programs? A recent U.K. court decision of October 5, 2011, In re Halliburton Energy Services Inc, helps us to understand the current direction of the world’s lawmakers.

The Position in the U.S. and Canada

For business methods, the argument against patentability is that the method itself does not produce any protectable product nor any process that results in such. It is therefore little more than a theory or an abstract idea, neither of which is actually patentable.

However, in the U.S., business methods constitute a patentable subject matter. Recent guidance was provided in the U.S. Supreme Court decision Bilski v. Kappos (130 S. Ct. 3218 (2010)), in which the Court followed U.S. court precedents’ guidance for assessing patentability. While not the sole test, this involves assessing whether the business method uses a “machine-or-transformation” and has a “useful, tangible and concrete result.” It is important to remember here that patents can cover both products and processes. Therefore a business method would seem to fall under a “process” but at the same time, it must produce a result, just like an inventive and new process to manufacture a pharmaceutical. It is difficult to conceive that a business method could be a “machine” if the method itself is not embodied in any “hardware” or physical machine. It is perhaps better to look to “transformation”: according to U.S. case law, “transformation and reduction of an article ‘to a different state or thing’ is the clue to the patentability of a process claim . . .” (Gottschalk v. Benson, 409 U.S. 63 (1972)) and the U.S. courts seem to consider that an article could be, for example, an electronic signal representative of a physical parameter, such as an electrocardiograph signal which is produced as a result of human cardiac activity.

Compared to the rather vague law on business methods, the law on computer programs is a little clearer, but still not without variations across different jurisdictions. The issue with computer programs is that most jurisdictions consider that the program, itself a source code, is protected by the law of copyright as it is essentially “work.” It is undoubtedly performing a function and perhaps even overcoming a problem as well. These characteristics point toward a computer program also being an invention of sorts and therefore patentable. U.S. law agrees and it is possible to protect computer programs as patents because patentees necessarily link the source code to “hardware” which must perform this function, overall creating a new “machine” or because the program itself achieves a technical function or result. It is also worth noting that following the recent new U.S. legislation contained within the America Invents Act signed on September 16 this year, the U.S. Patent Office now provides an eight-year period within which a petitioner or party being sued on that patent may request a review of that particular patent.

As recently as November 24, 2011, the Canadian Federal Court of Appeal has decided that there is no rule per se that excludes business methods from being patented. This case involved Amazon’s “one-click” patent. The court stated that patentable subject matter must be something with “physical existence or something that manifests a discernible effect or change.” At the same time, the court warned that it did not necessarily follow that a business method that was also an abstract idea and therefore not patentable would become patentable merely because it had a practical embodiment or application. Therefore, the court ordered the Commissioner for Patents to reexamine the application in the light of its decision.

The U.K. and Europe

On October 5, 2011, the U.K. High Court handed down a judgment In re Halliburton Energy Services Inc [2011] EWHC 2508 (Pat). This judgment attempts to tackle where the boundary between patentability and non-patentability of computer software should lie. The U.K. Patent Act states that “programs for computers” are not to be treated as inventions (Section 1(2)(c)). However, U.K. patent law has to follow the European Patent Convention (EPC), which states that while computer programs are not regarded as inventions, this is only to the extent to which that patent application, or part of it, relates to a computer program as such. Therefore, not all patents that deal with computer programs are non-patentable in Europe. If the program is a technical method overcoming a technical problem executed on a computer, then it is likely to be patentable (Enlarged Board of Appeal decision on Microsoft Clipboard formats case T 0424/03). Therefore, the court in the Halliburton Energy case had to consider the EPC position.

In giving his judgment, Judge Birss explained that there is an exclusion to patentability where the invention was simply a “mental act” and that if “the claim cannot be performed by purely mental means then the exclusion is irrelevant . . . the exclusion will not apply if there are appropriate non-mental limitations in the claims.” These “nonmental limitations” seem to be rather close to the U.S.’s “machine-or-transformation” test where there is a “useful, tangible and concrete result.” In summary, Judge Birss stated that the question of patentability “is decided by considering what task it is that the program (or the programmed computer) actually performs. A computer programmed to perform a task which makes a contribution to the art which is technical in nature, is a patentable invention and may be claimed as such.” Therefore, the fact that the software in Halliburton’s patent created a better way of making a drill bit showed that there was a technical contribution.

Thailand and Asia

In Thailand, the patentability of computer programs remains ambiguous. While the Thai Patent Act specifically precludes “computer programs” (Section 9(3)), software-related inventions can be protected as patents only if they are embodied in a patentable subject matter, such as a device, and that device has to be new, inventive, and capable of industrial application. In any event, this uncertainty often leaves the inventor/author with only copyright law to protect the source code, even though copyright is seen as a weaker form of protection than patents. This weakness stems from the fact that when copying a source code under copyright law, a substantive part of the work must be copied, whereas under patent law, just one of the claims of the patent must be infringed (and claims can be drafted fairly broadly).

Elsewhere in Asia, Japan does allow computer programs to be patented as long as the invention “concretely realizes the information processing performed by the software by using hardware resources” (“Examination Guidelines for Inventions for Specific Fields (Computer Software-Related Inventions) in Japan, Japanese Patent Office, April 2005”).

Conclusion

So can the recent U.K. decision be applied to business methods as well as computer programs? Judge Birss states: “The business method cases can be tricky to analyse by just asking whether the invention has a technical effect or makes a technical contribution. The reason is that computers are self evidently technical in nature. Thus when a business method is implemented on a computer, the patentee has a rich vein of arguments to deploy in seeking to contend that his invention gives rise to a technical effect or makes a technical contribution. For example the computer is said to be a faster, more efficient computerized book keeper than before and surely, says the patentee, that is a technical effect or technical advance.”

Therefore, it could be said that a program for a computer that uses a business method is not patentable unless the program implements an industrial process that contributes a technical effect to the art. Whether Thailand will start to accept such patents remains to be seen, but the U.K. position seems to be a sensible one since it still excludes the patentability of purely mental processes, which is what Section 9(3) of the Thai Patent Act is also designed to exclude.

RELATED INSIGHTS​ 

August 11, 2026
On July 27, 2026, the State Bank of Vietnam (SBV) released a draft decree proposing amendments to Decree No. 52/2024/ND-CP dated May 15, 2024, on non-cash payments (Decree 52). The draft decree would amend 17 of Decree 52’s 38 articles, with several key changes directly affecting providers of intermediary payment service (IPS). The key proposed changes affecting IPS providers are outlined below. Streamlining IPS Licensing Procedures A central objective of the draft decree is to simplify regulatory procedures for IPS providers. Notably, it would significantly reduce IPS licensing documentation requirements by removing the need to submit enterprise registration certificates, investment registration certificates, and documents evidencing the qualifications of the legal representative and general director. Instead, the SBV would retrieve this information directly from national business registration and other specialized databases, requesting additional documents only where the relevant information cannot be verified electronically or is incomplete. The draft decree also removes the current limit of two rounds for dossier supplementation and shortens processing timelines for several IPS licensing procedures such as issuance, amendment, and reissuance of IPS licenses. The processing time for new IPS license applications would be thereby reduced from 90 to 60 working days. In addition, several continuing IPS business conditions would be removed. For example, IPS providers would no longer be required to maintain certain representations relating to corporate restructuring or the legality of contributed capital. Likewise, the IPS project plan (đề án) would become a one-time application document rather than an ongoing licensing condition. If retained in the final decree, this change could provide IPS providers with significantly greater flexibility to implement post-licensing technology upgrades, system integrations, and corporate restructuring transactions without needing to revisit the originally approved project plan. The draft decree also removes the requirement for the SBV to consult the Ministry of Public
August 10, 2026
Thailand has finalized its social media KYC (“know your customer”) rules under Notification of the Electronic Transactions Commission on Measures to Prevent Technological Crimes for Social Media Service Providers (No. 2), which was published in the Government Gazette on May 5, 2026, and will take effect on November 1, 2026. While an early draft of the notification proposed requiring social media platforms to arrange identification of every user account, the final notification is significantly more targeted, focusing on paid online advertising and advertiser identity verification. Though the regulatory initiative primarily aims to combat online fraud and technology-related crimes, it also has important consequences for intellectual property enforcement, because the verified platform records that will be generated under the new requirements can help IP rights holders to identify anonymous online infringers. Key Regulatory Mandates The notification requires social media service providers to verify the identity of advertisers before their paid advertisements are published and disseminated in Thailand through social media, regardless of whether the advertising fees come from the advertisers or third parties. Verification of an advertiser is valid for one year, after which verification would have to be performed again before the platform could publish additional paid advertisements from the advertiser. Permitted verification methods are specified under the notification. A platform may verify an advertiser by checking identity evidence and confirming the connection between the advertiser and that identity evidence, with the notification giving facial comparison against certain government-issued identity documents as an example. Alternatively, platforms may verify advertisers through a digital identity verification and authentication system with an identity-proofing assurance level not lower than the level prescribed by Thailand’s Electronic Transactions Commission. The notification further requires platforms to retain only the advertiser’s information necessary to identify the advertiser, beginning from the start of the advertising activity and for
August 10, 2026
On July 31, 2026, Thailand’s Big Data Institute (BDI) launched a public consultation on the principles of a proposed new data-sharing law, with comments accepted until August 31, 2026. If enacted, the law would establish Thailand’s first comprehensive framework for government and private-sector data sharing, creating a systematic, secure, and transparent regime to support analytics, policymaking, research, and innovation. Central Data-Sharing Platform The draft law establishes a central system for data sharing, managed by the BDI. Government agencies would be required to connect to the BDI’s Data Integration and Intelligence Platform (also referred to as D2), in accordance with the BDI’s rules and procedures. Five Dimensions of Data Sharing The draft law covers five key types of data sharing between government (G), businesses (B), and consumers (C): G2B: Private organizations may request government data specifically for research and development purposes. The BDI will assess the applicant’s data governance, security, and privacy capabilities whether such measures meet prescribed standards before forwarding the request to the relevant government agency within 90 days. Any dispute may be escalated to a newly established Data-Sharing Promotion Committee for final determination. G2G: Government agencies may request data from other agencies through the central system. The data-holding agency must respond within 90 days, taking legality, necessity, proportionality, public interest, and personal data protection into account. Disputes may be referred to the Data-Sharing Promotion Committee for adjudication. B2G: In emergency situations involving public safety, economic security, or disaster response, the Minister of Digital Economy and Society may require private entities to provide data through the central data-sharing system. Government agencies must specify the data requested, demonstrate its necessity and expected benefits, and request only data reasonably available to the data holder. Requests for personal data must be limited to the minimum amount necessary. B2C: Royal decrees may
August 10, 2026
Thailand’s Office of the Personal Data Protection Committee (PDPC) recently released draft guidance on records of processing activities (ROPA) for personal data controllers and processors under the Personal Data Protection Act B.E. 2562 (2019) (PDPA). The draft guidance, which was presented to the public on July 7, 2026, addresses both controller records of collection, use, and disclosure of personal data and processor records of processing activities carried out on behalf of controllers. If implemented, the guidance will significantly expand organizational expectations for ROPA preparation, maintenance, and use across all sectors. Key Takeaways The draft guidance contains several important implications for organizations subject to the PDPA: ROPA reframed as a core accountability tool. The guidance elevates ROPA from an administrative record to a central accountability mechanism, connecting controller duties with recordkeeping obligations. ROPA as a source for privacy notices and governance documents. ROPA should serve as the primary source for privacy notices and align with consent management, retention schedules, DPIAs, incident response plans, and vendor contracts. Expanded scope across all activities. ROPA must cover all processing activities across the organization—including security, finance, HR, and external contractors—with correct controller or processor classification for each. Ongoing maintenance and auditability. ROPA must be updated for any change to systems, purposes, or processors, reviewed at least annually, and maintained with version control and a designated owner. Enhanced vendor, processor, and cross-border transfer requirements. Organizations must document all processors, external recipients, and cross-border transfers, specifying purposes, access scope, and destination countries. Linkage with risk assessment, DPIAs, and LIAs. ROPA should assign risk levels to each activity and identify when data protection impact assessments (DPIAs) or legitimate interests assessments (LIAs) are required, functioning as a risk-management tool. ROPA and data breach readiness. Incomplete ROPA can delay breach response and notification. Organizations should map data flows, vendors,