Can I Claim SR&ED for Cloud Infrastructure Costs?

For modern software companies, the physical lab has been replaced by the cloud. Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP) represent massive monthly expenditures.

Can these cloud infrastructure costs be claimed as SR&ED expenditures? Generally, the answer depends heavily on which overhead method you select.

The Proxy Method: No Direct Cloud Claims

As discussed in previous articles, the vast majority of software companies elect to use the Proxy Method for calculating overhead. Under this method, the CRA allows you to calculate a proxy amount (55% of the eligible SR&ED salary base) to cover all overhead expenses.

If you choose the Proxy Method, you cannot claim any cloud hosting costs, specific software licenses, or general utility bills. The 55% proxy amount is deemed to cover all of these infrastructure costs, regardless of how high your AWS bills actually are.

The Traditional Method: Direct Allocation

If you choose the Traditional Method, you are allowed to claim the exact costs of overhead items—including cloud infrastructure—but only to the extent that they were directly attributable to the SR&ED activities.

This is where it gets incredibly complicated for SaaS companies.

The Allocation Problem

If your AWS bill is $10,000 a month, you must prove to the CRA exactly how much of that compute power was used by the engineering team to run experimental simulations, versus how much was used to host the live production application for your customers.

The CRA explicitly excludes "commercial production" costs from SR&ED. Your production web servers, your customer databases, and your outbound bandwidth are completely ineligible.

Proving Experimental Cloud Costs

If you wish to claim cloud costs under the Traditional Method, you must have rigid structural separation in your cloud environments:

1. Separate Accounts/VPCs: You should maintain entirely separate AWS accounts or VPCs designated exclusively for "R&D Sandbox" or "Experimental Testing."
2. Tagging: Every instance, database, and storage bucket must be relentlessly tagged (e.g., Env: SRED-Testing).
3. Billing Reports: You must produce detailed AWS Cost Explorer reports showing exactly how much the specific SR&ED-tagged resources cost during the period the experiments were running.

The Reality for Most Startups

Because the burden of proof is so high, and because segregating production compute from experimental compute is often messy, almost all software companies elect the Proxy Method.

The value of the 55% salary proxy usually far outweighs the value of the specific experimental cloud instances they could prove under the Traditional Method, avoiding a massive administrative headache during an audit.