OpenAI, Anthropic (Claude) and Google (Gemini) all bill in US dollars, and Canadian developers keep asking the same question: are these API charges actually deductible, and if so, where do they go on the return? Yes, they are. The interesting part is not whether. It is where, how, and what you need to keep on file if a CRA reviewer ever picks up your T2125.
Key takeaways
- API tokens from OpenAI, Anthropic (Claude) and Google (Gemini) are deductible when the usage earns business income. Treat them as current operating expenses, not capital assets.
- On a sole proprietor's T2125, most developers should book API charges to line 8810 Office expenses or line 9270 Other expenses. Both are correct. Pick one and stay consistent.
- Your source document is the invoice or usage report from the vendor's billing dashboard. Not the credit card statement.
- Convert USD invoices to Canadian dollars using the Bank of Canada daily exchange rate on the invoice date.
- Prepaid API credits are deducted as you consume them, not when you buy them. A $500 top-up in December that is only 40% used by year-end deducts $200 this year and $300 next year.
- If the same OpenAI account also runs hobby projects, you can only deduct the business portion.
The quick answer
Yes. If you use OpenAI, Anthropic (Claude) or Google (Gemini) API tokens to build a product, run client work, or otherwise earn business income, the fees are a fully deductible business expense in the year they are incurred.
They are not a capital asset. There is no CCA class for API usage. There is no depreciation schedule. Under the general deductibility test in the Income Tax Act, an expense laid out to earn income from a business is deductible unless something specific in the Act denies it. Metered software usage sits comfortably inside that test. The Canada Revenue Agency's own guidance on business expenses treats recurring software costs the same way it treats phone bills, cloud hosting and office supplies. Metered charges from OpenAI's ChatGPT, Claude and Gemini API endpoints, along with any other LLM or GPT-powered service in your stack and the AI tools you use to categorize or simplify tax information for your own clients, all fit inside that same bucket.
The interesting question is not whether. It is where, how, and what you need to keep. This is where most Toronto and Waterloo indie developers, AI SaaS founders and freelance developers using AI to build client work get quietly sloppy. A CRA reviewer looking at a T2125 with $18,000 in "software" and zero supporting invoices in USD is going to have questions.
Where API charges actually go on the T2125
For a sole proprietor or single-member partnership, API fees have two reasonable homes.
Line 8810 Office expenses. This is the standard bucket for the day-to-day cost of running an office, including recurring software you subscribe to. If you already put your Google Workspace, Notion, GitHub and Adobe bills here, put these charges here too. Most developers land on 8810 because it is where the rest of their SaaS stack lives.
Line 9270 Other expenses. This is the catch-all for legitimate business expenses that do not fit the named lines above it. If your spend on these services is large enough that you want it clearly visible on its own line rather than buried inside a mixed office-expenses total, book it here and label the schedule "Computer and software subscriptions."
Either line is defensible. What is not defensible is moving the same expense between lines from year to year, or splitting it across both. Pick a home in year one and keep these charges there for the life of the business.
For a corporation filing a T2, the same logic applies. The usage goes on the income statement under "Office expenses" or a "Computer and software subscriptions" sub-account within operating expenses, and flows through Schedule 125 (the GIFI) under codes 8811 or 9270. Your bookkeeping software will map to GIFI automatically if the sub-account is named clearly.
Do not put these charges under capital assets. Do not create a CCA class. Do not depreciate them. That is a category error that will slow down any audit response.
The four things Canadian developers get wrong
1. USD conversion at the wrong rate
OpenAI, Anthropic and Google all bill in US dollars. The credit card statement shows a Canadian dollar amount after the card issuer's markup. That number is not what CRA wants.
The Canada Revenue Agency accepts the Bank of Canada daily exchange rate on the date of the transaction. For a vendor invoice, the transaction date is the invoice date shown on the billing dashboard, not the credit card posting date. Look up the rate on the Bank of Canada's daily exchange rates page, multiply the USD invoice by that rate, and record the Canadian dollar figure in your books.
If the invoice date falls on a weekend or holiday, use the rate from the closest preceding business day.
The gap between the card issuer's rate and the Bank of Canada rate is usually small on a single invoice. Across twelve months of daily usage it can distort your deduction by hundreds of dollars in either direction. Do it properly once, build the habit, move on.
2. Treating the credit card statement as the receipt
The credit card statement shows "OPENAI *SUBSCRIPTION $47.28." That is a bank record. It is not OpenAI's actual invoice, and it is not a source document that will hold up in a CRA compliance review.
Your source document is the invoice or usage report inside the vendor's billing dashboard. Log in to platform.openai.com, console.anthropic.com or ai.google.dev at least once a month, download the PDF invoice for the prior month, and save it. Name the file with the vendor and invoice date so a future reviewer can match it to your general ledger in seconds.
The invoice tells CRA three things the credit card line item does not. It confirms the vendor and the service, it separates any GST/HST from the base fee, and it locks in the invoice date you will use for USD conversion. If you are ever asked to prove a deduction, the reviewer is going to ask for this document.
3. Deducting prepaid credits when you buy them
Many developers keep a running balance of API credits. You top up $500 in September, burn through it over four months, top up again in January. It feels like a $500 expense in September.
For tax purposes it is not. Canadian business income follows accrual matching: the deduction lands in the year the service is consumed, not the year the cash leaves your account. This treatment comes from the long-standing CRA position on prepaid expenses (originally set out in the archived IT-417R2 bulletin on prepaid expenses and deferred charges) and it applies to any prepayment for services not yet received.
The practical fix: at year-end, ask the billing dashboard for the credit balance remaining. The portion consumed is this year's expense. The portion still sitting on the account is a prepaid expense on your balance sheet, and it gets deducted next year when it is spent.
If your prepayments are small and the timing consistent, most accountants will not fight you on immaterial amounts. If you top up $5,000 in December and only use $600 by year-end, the difference matters.
4. Mixing personal and business use on the same account
This is the trap most solo developers fall into. You have one OpenAI account. You use it for a client project you invoice. You also use it to help write a wedding speech, plan a trip, categorize your personal information, and mess around with a hobby side project you have never earned a dollar from. Your account history ends up mixing business records with the kind of personal details CRA has no reason to see.
CRA only allows the business portion. If 70% of your API calls in the year were for the SaaS product you sell and 30% were personal, you deduct 70% of the fees. Do not deduct 100% and hope no one looks.
The clean fix is to run two separate accounts on two separate email addresses, one strictly for the business and one strictly personal. Different API keys, different billing methods, zero overlap.
If separating accounts is not practical, keep a defensible allocation method. Token counts by project tag inside the OpenAI dashboard, monthly time logs, or a documented percentage based on how the account is used. Whatever method you pick, write it down, apply it consistently, and revisit it once a year.
The GST/HST wrinkle
Most Canadian developers see one of two things on their vendor invoices. Either no tax at all, or Canadian GST/HST charged by the vendor.
When it is charged: if your business is a GST/HST registrant, you may be able to claim an Input Tax Credit for GST/HST actually paid on the invoice, provided the usage is for taxable commercial activity and you have the invoice to support it. Whether the tax collected under the non-resident digital-economy simplified regime is recoverable as an ITC depends on how the vendor is registered, and this is worth a quick check with your accountant if the amounts are meaningful.
When it is not charged: if the vendor does not charge Canadian tax, GST/HST-registered businesses may have a self-assessment obligation on imported services used outside their commercial activity. For most developers whose usage is fully commercial, no self-assessment is required, but the general rule is worth knowing.
A monthly bookkeeping template that will pass a review
Once a month, the same fifteen minutes:
| Step | What to do | Where it lives |
|---|---|---|
| 1 | Download the PDF invoice from each vendor's billing dashboard | Cloud folder, named openai-2026-08.pdf, anthropic-2026-08.pdf, etc. |
| 2 | Note the invoice date and USD amount | Same folder, or a running sheet |
| 3 | Look up the Bank of Canada daily rate for that date | bankofcanada.ca daily rates page |
| 4 | Enter the CAD amount in your books to Office expenses (8810) or a Computer and software subscriptions sub-account | Bookkeeping software |
| 5 | If prepaid credits are involved, adjust for the unused balance at year-end | Year-end journal entry |
| 6 | If you are a GST/HST registrant, separate any GST/HST charged for the ITC | Bookkeeping software |
Fifteen minutes a month, twelve months a year, and your deduction is audit-ready without a scramble in April.
What Canadians using AI tools often miss
The rules above cover the metered API side. A few adjacent questions come up almost every week from Canadians running a business with artificial intelligence in the loop.
The 90% rule for tax deductions in Canada. This is not a rule that applies to LLM APIs, but it is a rule people mix up. CRA's 90% test applies to specific things like the home office simplified method and certain input tax credits. Ordinary business deductions, including AI tools, tax filing software, a good tax calculator, and the automation subscriptions you use to simplify your workflow, follow the general deductibility test in the Income Tax Act. All of it is tax-deductible against the business portion. No 90% threshold required.
AI tools beyond the raw API. Chatbot builders like Voiceflow, chatbots that wrap GPT (including ChatGPT's browser plugins and thin wrapper products), generative writing tools, TaxGPT-style tax filing and tax return assistants, and the AI features baked into the accounting software you use to file your taxes are all deductible on the same lines as the API charges themselves. The 2023 wave of new AI-powered SaaS tools sits comfortably inside Canada's tax system as ordinary business expenses, and Canada's tax rules on tax filing in Canada, and taxes in Canada generally, still treat this as ordinary tax information for T2125 or T2 filers.
A few smaller things Canadian AI users should keep clean and up-to-date each fiscal year: your billing address matches your province of business so provincial tax and jurisdiction on the invoice are right, the vendor's privacy practices and retention policies suit the personal information you feed into a chatbot on a client's behalf, and your budget for AI spend is documented for cost optimization against how much you actually use it. If a trustworthy paid AI advisor or a human tax professional or tax expert saves you money on complex tax work, they are deductible too. For any Canadian filing through NetFile, the tax rates and tax-filing lines that carry your AI-related deductions are the same ones they always were: nothing on the tax return has been carved out for AI yet.
Getting the treatment right the first time
Most of the developers we talk to are not missing the deduction. They are missing the paperwork that lets the deduction survive a CRA review. Downloaded invoices, a documented USD conversion method, a clean year-end adjustment for prepaid credits, and a defensible split between business and personal use turn a nervous "I think this is fine" into a boring "here are the files."
If you are unsure whether your current setup would hold up, or you are moving from freelance to incorporated and want the treatment reviewed properly, the EK CPA Pro team works with independent developers and AI SaaS founders across Ontario and remotely across Canada. Have a look at how we handle tax planning and bookkeeping, or book a call with our team and bring your last three months of API invoices along.
This article is general information, not tax advice. Rules, rates and CRA positions change. Confirm your specific situation with a CPA before filing.
