Quebec CDAE 2026: Complete Guide to the E-Business Development Tax Credit

If you run an IT or software business with a Quebec footprint and you've only ever heard about SR&ED, you're leaving real money on the table. Quebec's Tax Credit for the Development of E-Business — CDAE — pays up to 30% on the salaries of qualifying IT employees, capped at roughly $25,000 per employee per year. It is not an SR&ED credit. It is not an expenditure-based credit. It is a salary-based provincial incentive that, when stacked correctly with federal SR&ED and Quebec's own R&D credits, can change the economics of running an engineering team in Montreal, Québec City, Sherbrooke, or Gatineau. In this guide we walk through every rule that actually matters — the 75% activity test, the 75% time test, the qualification certificate process, the activities that get excluded, and where most applications quietly fail.

What CDAE is — and why it isn't SR&ED

CDAE was introduced in 2008 to anchor Quebec's information-technology and software sector. It is jointly administered by Investissement Québec (which issues the eligibility certificates) and Revenu Québec (which administers the credit through the corporate tax return). It is one of the most generous provincial tax credits available to IT businesses anywhere in Canada, and yet it is consistently under-claimed — usually because companies assume it overlaps with SR&ED or that they don't qualify.

The key conceptual point: CDAE is salary-based, not expenditure-based. SR&ED reimburses a percentage of qualifying R&D expenditures (salaries, contractors, materials, overhead). CDAE only looks at one thing — eligible Quebec salaries paid to eligible employees performing eligible activities. There is no proxy method, no overhead pool, no contractor calculation, no materials line. You count salaries that meet the test, apply the rate, and apply the cap. That structural simplicity is part of why the credit is so valuable: most of the noise in an SR&ED file (allocation arguments, proxy vs. traditional, contractor classifications) simply doesn't exist in a CDAE file.

Three other structural points worth flagging up front:

• Activity scope is broader than SR&ED. SR&ED requires scientific or technological uncertainty, hypothesis-driven experimentation, and systematic investigation under the S/THERI and CRA IC 2012-02 frameworks. CDAE doesn't. It accepts ordinary — even routine — e-business consulting, software development, and IT systems integration as eligible work, as long as the activity itself qualifies and the corporation passes the company-level tests.
• It's annual, not project-based. There's no project file, no technical narrative in the CRA sense, no claim of advancement. Each year, the corporation re-applies for an annual qualification certificate from Investissement Québec confirming it still meets the corporate and employee tests, and Revenu Québec then accepts the credit on the corporate return.
• You can claim CDAE and federal SR&ED on the same employees. The two regimes target different things. Where eligibility overlaps — for example, an engineer whose work is both SR&ED-eligible R&D and CDAE-eligible e-business development — you can claim both, subject to the usual rules against double-counting the same dollar of expenditure inside SR&ED. We come back to the mechanics below.

The 30% rate — broken down

The headline 30% rate is a composite of two parts that behave very differently on the corporate return:

This split matters more than it looks. A profitable Montreal software company with $5 million in eligible Quebec IT salaries (after the per-employee cap is applied) sees most of the value land as a refund cheque, but also locks in a meaningful reduction in Quebec tax payable through the non-refundable 6%. A pre-revenue Quebec-based scaleup with the same salary base sees the 24% refundable portion as essentially a wage subsidy and may not be able to absorb the 6% non-refundable portion in the year it's earned.

The annual per-employee cap

The 30% rate doesn't apply to unlimited salary. CDAE caps eligible salary at approximately $83,333 per employee per year, which translates to roughly $25,000 per employee per year of credit (30% × $83,333 = $25,000). That ceiling is per eligible employee, per tax year, and it applies regardless of how much you actually pay the employee. A senior Quebec-based principal engineer earning $250,000 still generates the same maximum CDAE as a mid-level developer earning $90,000 — the credit just stops accruing above the cap.

The cap is what determines whether CDAE is a small line item or a major part of the engineering economics. For a 30-person Quebec engineering team where most employees are above the salary cap and fully engaged in eligible work, the math is simple: 30 employees × $25,000 = $750,000 per year in CDAE credits, of which roughly $600,000 is refundable cash and $150,000 is a non-refundable reduction in Quebec tax payable.

The 75% activity test (company level)

Before any individual employee can generate CDAE, the corporation must qualify. The first hurdle is the 75% activity test: at least 75% of the corporation's gross revenue for the tax year must come from eligible IT-sector activities. This is a structural test, not a "best-effort" test. If the corporation is a hybrid business — for example, IT services plus a hardware reseller arm, or a consulting practice that also bills heavy professional services unrelated to e-business — the IT-sector revenue stream has to clear 75% of total revenue. Eligible IT-sector activities for the purposes of the 75% test are defined by reference to specified NAICS codes (most commonly the 541510-series and related software publishing and computer systems design codes).

A second related test sits inside the activity definition: a meaningful share of the corporation's revenue must come from services rendered to arm's-length parties, not just intra-group billing. The exact threshold and how it interacts with related-party services is one of the most-litigated points in CDAE files, and it's the test that most often surprises in-house captive IT shops trying to claim CDAE on internal corporate IT work. We come back to this in the "Excluded activities" section.

The 6-employees minimum

In addition to the 75% activity test, the corporation must employ at least six eligible employees — that is, six employees who individually pass the 75% time test described below. The minimum-six rule is a deliberate filter to keep the credit oriented to real IT-sector employers and to exclude one-person consultancies and small captive teams. The six employees must be on payroll, must be full-time (or full-time-equivalent in the manner Investissement Québec defines), and must be working at the corporation's Quebec permanent establishment.

The 75% time test (employee level)

Once the corporation qualifies, each employee for whom you want to claim CDAE must independently pass the employee-level test: at least 75% of the employee's time in the tax year must be spent on eligible activities. This is a per-employee, per-year test. An engineer who spends 90% of their time on eligible e-business software development passes. An engineer who spends 60% of their time on eligible work and 40% on sales support or non-eligible internal IT does not pass — and generates zero CDAE for that year. There is no partial credit at the employee level. It's binary.

The practical implication is that the time test demands clean, contemporaneous time tracking. Investissement Québec and Revenu Québec both have audit visibility into this, and "we estimated 75%" is not a defensible position in a review. Successful CDAE claimants log time at least monthly, document role descriptions tied to eligible-activity categories, and keep the supporting documentation alongside the SR&ED time-tracking infrastructure (if they have any).

Roles that typically pass the 75% time test

• Software developers and engineers building or maintaining e-business platforms, SaaS products, or business application software
• Systems architects and integration specialists working on e-business systems and APIs
• QA engineers and DevOps engineers whose work is dedicated to eligible e-business products
• Technical product managers spending the majority of their time on technical specification, architecture, and design of eligible e-business systems
• Data engineers and analytics engineers building e-business analytics, customer-data, and operational-data infrastructure

Roles that typically don't pass

• Sales engineers and pre-sales solutions consultants whose primary function is revenue closing
• Account managers and customer success managers, even on technical accounts
• General IT support and helpdesk staff whose work isn't tied to a specific e-business solution being delivered to clients
• HR, finance, marketing, and back-office roles, even at a software company
• Hardware-focused technicians, network technicians, and infrastructure roles where the primary deliverable is hardware rather than software

Eligible activities — what CDAE actually funds

CDAE-eligible activities cluster into four broad categories. The activity has to be carried out at a Quebec permanent establishment, performed by an eligible employee, and tied to e-business solutions delivered (in most cases) to arm's-length clients.

The IT-sector activity definition itself is anchored to NAICS codes — principally the computer systems design and related services codes (NAICS 541510 family), software publishing (NAICS 511210), and certain data-processing and hosting categories. If the corporation's primary NAICS classification is outside this cluster, the 75% revenue test becomes much harder to satisfy, and Investissement Québec will expect the application to justify the IT-sector classification at length.

Excluded activities — where CDAE stops

CDAE has a deliberately narrow exclusion list, but the exclusions are absolute. The following categories of work do not count toward eligible salaries even when performed by an otherwise-eligible employee at an otherwise-eligible corporation:

• Hardware sales and hardware-only services. Selling computers, servers, network equipment, peripherals, or any tangible hardware product is not e-business consulting under CDAE, even if performed by a software engineer.
• Generic IT support and helpdesk operations. Tier-1 helpdesk, password resets, user-account administration, and similar general IT-support functions are excluded unless they're tied directly to a specific e-business solution being delivered to a client.
• Internal corporate IT. Running the corporation's own IT (its email, its desktops, its internal networks) is excluded. CDAE funds services delivered to arm's-length clients, not internal cost-center work. This is the rule that disqualifies most captive IT shops.
• Pure infrastructure and network management. Network operations, server administration, and infrastructure-only roles are generally excluded unless they're embedded in a broader e-business solution being delivered.
• Activities outside Quebec. Work performed by employees based outside Quebec, even by Quebec-incorporated employers, does not generate CDAE. The credit is anchored to Quebec permanent establishment salaries.
• Telecommunications operations. Operating a telecom network or providing telecom services is excluded from the IT-sector definition for CDAE purposes.
• Activities funded by a non-arm's-length party or by another government program in a way that creates a stacking conflict (see SR&ED interaction below).

The qualification certificate from Investissement Québec

CDAE is administratively a two-step credit. First, Investissement Québec issues two annual documents: a corporation qualification certificate confirming the entity passes the 75% activity test, the six-employees test, and the IT-sector NAICS test; and an employee eligibility certificate for each individual employee being claimed, confirming that employee passes the 75% time test for the year. Second, the corporation files the credit on its Quebec corporate tax return (form CO-1029.8.36.DA and related schedules), attaching or referencing the Investissement Québec certificates.

The certificate process is the part that trips up most first-time claimants. It is not a tax filing — it is a separate, document-heavy application to a different government agency, with its own forms, its own timelines, and its own fee schedule. Investissement Québec reviews each application substantively: it tests the corporation against the 75% revenue threshold, validates the NAICS classification, reviews the description of activities, and reviews each employee's role and time allocation. For active files, expect questions and back-and-forth. For complex hybrid businesses, expect the review to extend over several months.

What an application typically includes

• Corporate financials demonstrating the 75% IT-sector revenue split
• NAICS classification documentation and a narrative justifying the IT-sector classification
• A list of eligible employees, their roles, their time allocations, and supporting role descriptions
• A description of the eligible activities performed in the year, mapped to the CDAE category definitions
• Evidence that the corporation has a permanent establishment in Quebec and that the eligible employees physically work from it
• For services delivered to clients, descriptions of the client engagements and confirmation of arm's-length status where relevant

Timelines

Plan on a multi-month process. The certificate application itself should be filed for each tax year as the year unfolds or shortly after the year-end, and Investissement Québec's substantive review typically takes a few months from a complete file. The corporate return that claims CDAE has to wait for the certificate, so any delay at Investissement Québec delays the cash refund downstream. Most well-run Quebec CDAE claimants build the certificate application into a recurring annual rhythm, similar to how Canadian businesses build SR&ED into the year-end close.

How CDAE interacts with federal SR&ED

This is the question we get asked most often: can a Quebec IT company claim both CDAE and federal SR&ED on the same engineering team? The short answer is yes, but with care.

The longer answer turns on two principles. First, the two credits target different activity definitions. SR&ED requires scientific or technological uncertainty, hypotheses, experimentation, and systematic investigation under the IC 2012-02 framework. CDAE requires eligible IT-sector activity at a Quebec PE, performed by employees passing the 75% time test. Many activities qualify for both — an engineer building a novel SaaS pricing engine may be doing both SR&ED-eligible R&D and CDAE-eligible e-business software development — but the qualification is independent. You don't get one for free just because you have the other.

Second, where the same salary dollar is being counted in both credits, the SR&ED expenditure base has to be reduced by the amount of CDAE attributable to that dollar — specifically, government assistance (including CDAE) reduces the SR&ED qualified expenditure pool. This is the standard "government assistance" rule in the federal SR&ED regime, and Quebec has its own analogous rules on the provincial side. The net effect is that you don't get to double-claim the same dollar, but you do get to capture both regimes' separate benefits across the broader engineering team where eligibility overlaps.

In practical terms, the right mental model for a Quebec IT company is:

• CDAE captures up to $25K per eligible Quebec employee per year, refundable in large part, with relatively light eligibility friction once the corporation qualifies.
• Federal SR&ED captures a percentage of qualifying R&D expenditures (salaries, contractors, materials, overhead) on the subset of work that meets the S/THERI test — typically the harder, more uncertain engineering work.
• Quebec's own R&D tax credits (the RD wage credit and related) stack on top of SR&ED on the same eligible R&D work, with their own rules.
• Where the same employee touches both eligible CDAE activity and eligible SR&ED R&D activity, you allocate cleanly between the two and accept that the SR&ED expenditure base will be reduced by the CDAE attributable to that allocation.

Language of work in Quebec — a practical note

This isn't a CDAE rule, but it's an operational reality for any Quebec employer claiming the credit: under Quebec's language regime, internal documentation, role descriptions, and HR records for Quebec-based employees are expected to be available in French. The CDAE certificate application itself can be filed in French (and in practice, files in French move more smoothly through Investissement Québec). For Anglophone parent groups with Quebec subsidiaries, the practical implication is that the year-end CDAE documentation pack needs to be assembled in French even if the engineering team's working language is English. This is normal, it doesn't change eligibility, but it adds lead time if your operation hasn't built that muscle.

Common reasons CDAE claims get reduced or denied

Beyond the binary corporate-level tests, the most common reasons CDAE files get reduced or denied are predictable.

• The 75% revenue test is too tight. Hybrid businesses with material non-IT revenue lines (hardware, professional services unrelated to e-business, training, real estate) routinely fail this test. The fix is either a corporate restructuring to isolate the IT-sector entity, or accepting that the parent doesn't qualify.
• Employees fail the 75% time test because of poor time records. The most expensive failure mode. An engineer is qualitatively obviously CDAE-eligible, but no contemporaneous time records were kept, and the claim collapses on audit. Fix: monthly time logs tied to role descriptions and activity categories.
• NAICS classification doesn't support the IT-sector claim. If the corporation's CRA and provincial NAICS classification puts it outside the eligible IT-sector cluster, the certificate application starts on the back foot. Reconcile the NAICS classification with the actual revenue mix before filing.
• Captive IT structure. The Quebec entity exists to serve a non-arm's-length parent, fails the services-to-arm's-length-clients test, and gets denied at Investissement Québec. There is sometimes a path through this with careful restructuring; there is not always.
• Ineligible activity mix dragging down individual employees. An engineer spending 30% of their time on infrastructure-only network management can't be claimed even if their other 70% is impeccable e-business software development. The 75% time test is binary at the employee level.
• Missed annual filings. CDAE certificates are annual. Skipping a year (because the application got crowded out by SR&ED season, for example) means losing that year's credit. There's no retroactive recovery for a missed certificate.
• Stacking interaction errors with SR&ED. Failing to reduce the SR&ED expenditure base for CDAE government assistance produces a CRA reassessment risk on the federal side. The two credits have to be modeled together, not in isolation.

Is CDAE right for your business?

CDAE is a strong fit if you run a software, SaaS, e-commerce platform, IT services, or business application company with a Quebec permanent establishment, at least six Quebec-based engineers or IT professionals fully engaged in eligible e-business work, and at least 75% of revenue derived from eligible IT-sector activities sold to arm's-length clients. Quebec-based scaleups in fintech, healthtech, e-commerce infrastructure, B2B SaaS, integration platforms, and enterprise software are typically the cleanest fits.

CDAE is a poor fit — or outright ineligible — if you are a captive in-house IT department of a non-IT parent (a Quebec-based retailer's internal IT, for example), if you sell primarily hardware or telecom services, if your engineering team is mostly outside Quebec, if you have fewer than six Quebec-based eligible employees, or if your revenue mix has too much non-IT content to clear the 75% test.

For Quebec IT employers in the sweet spot, CDAE is one of the most valuable provincial tax credits available in Canada — comfortably in the same conversation as Ontario's OITC and ORDTC and, in many cases, materially more generous on a per-employee basis. A Quebec-based scaleup with 40 eligible engineers can credibly generate $1 million per year in CDAE credits, the bulk of it refundable cash. That is real, recurring, non-dilutive funding.

Final thoughts

CDAE rewards two things: clean corporate structure and disciplined time tracking. If the corporation's revenue mix and NAICS classification are clearly inside the eligible IT-sector cluster, and if each claimed employee's time is logged and defensible against the 75% test, the credit largely runs itself once the annual certificate rhythm is established. The mistakes that hurt are upstream: a parent group structure that makes the 75% revenue test impossible, time records that don't exist, a NAICS classification nobody reconciled to the actual revenue mix.

If you're considering CDAE for the first time, the order of operations matters. Start with the corporate structure and the 75% revenue test — if the entity can't clear that, none of the rest matters. Then layer in the 75% time test at the employee level and the supporting time-tracking infrastructure. Then build the annual Investissement Québec certificate application as a recurring year-end exercise, ideally synchronized with the SR&ED documentation cycle so the engineering team is being asked to log time once, not twice.

And model it alongside federal SR&ED and Quebec's R&D credits from day one. The economics of running an engineering team in Quebec, properly stacked, are very different from running the same team in a province without an equivalent credit. CDAE on its own is meaningful. CDAE + SR&ED + the Quebec R&D wage credit, properly coordinated, can shift a Quebec software company's gross-engineering-cost profile by 20–30% relative to the same team outside Quebec.

CDAE is one of several Quebec and federal-provincial programs we cover. Use our Grant Finder to compare CDAE against federal SR&ED, Quebec's R&D wage credit, Ontario's OITC and ORDTC, and other provincial software and digital-media credits before structuring an engineering team across provinces.