Is A Ransom Payment For Kidnapped Executives Tax-Deductible In Canada? A Canadian Crypto Tax Lawyer's Analysis

France's ongoing crypto kidnapping crisis has put an old question back on the table for Canadian taxpayers: if a ransom is paid to free a kidnapped crypto executive, employee, or business owner, can any part of it be deducted as a business expense? A Canadian tax lawyer works through the purpose test, the personal-expense exclusion, and how the answer changes depending on who is kidnapped and who pays.

Overview: A Question Canadian Tax Law Has Never Had to Answer

France's crypto kidnapping crisis, documented in our companion analysis, France's Crypto Kidnapping Surge Exposes a Deeper Risk, has produced dozens of cases in which crypto executives, employees, and business owners were kidnapped for ransom specifically because of the wealth or public profile their businesses created. French authorities recorded 77 cases of crypto-linked kidnappings, attempted abductions, and extortions in the first half of 2026 alone, a steep rise from previous years.

That fact pattern raises a Canadian crypto tax question with no settled answer: if a ransom is paid to free a kidnapped person, can any part of that payment be deducted as a cost of earning income? There is no reported Canadian decision and no CRA administrative position on point, and the question is arriving at the same time the CRA's own capacity to scrutinize any unusual deduction has grown substantially, as our companion analysis, CRA Using AI to Spearhead Crypto Tax Audits in 2026, sets out.

What follows sets out the strongest argument on each side, since taxpayers considering this question deserve a fair account of both, not a false certainty in either direction.

Why This Question Feels Uncomfortable to Ask

Before turning to the statutory framework, it is worth acknowledging directly why this question feels uneasy even to raise. A CRA appeals officer, or a Tax Court judge, could reasonably feel uncomfortable with a deduction that looks like it rewards paying criminals, or that could be perceived as softening the after-tax cost of a ransom payment in a way that encourages the practice.

That instinct is legitimate, and a taxpayer arguing for deductibility should expect to confront it directly rather than assume a technical purpose-test argument will carry the day on its own. But discomfort is not the same thing as law, and Canadian courts have been explicit that they will not invent a public-policy bar that Parliament has not enacted. That said, the absence of a public-policy bar is not a licence to file an aggressive position quietly and hope it goes unnoticed.

Taking an unsupported deduction without disclosing the uncertainty behind it risks more than a simple disallowance if the CRA disagrees, since unreported or misrepresented positions can expose a taxpayer to gross negligence penalties under subsection 163(2), which are considerably more severe than the interest and adjustment that follow an ordinary reassessment.

The General Framework: Purpose, Not Illegality, Is the Test

It is tempting to assume a ransom is automatically non-deductible because it is paid to a criminal in connection with a crime. Canadian tax law does not work that way. In 65302 British Columbia Ltd v Canada, [1999] 3 SCR 804, the Supreme Court of Canada held that a fine incurred by an egg producer for exceeding its production quota could still satisfy the ordinary purpose test in paragraph 18(1)(a), for the purpose of gaining or producing income, and the Court expressly rejected any freestanding, judge-made rule that payments connected to illegal or quasi-illegal conduct are categorically barred from deduction. Parliament responded by legislating specific exclusions, section 67.6 for fines and penalties, and section 67.5 for bribes, secret commissions, and similar illegal payments, precisely because the ordinary purpose test, left alone, might otherwise have permitted deductions of that kind. No equivalent provision addresses ransom payments. That means the analysis returns entirely to the ordinary framework: does the outlay satisfy the purpose test in 18(1)(a), and is it excluded as a personal or living expense under 18(1)(h). Whether the recipient was a criminal is not, on its own, the deciding factor.

Threats to Life or Health Versus Pure Confinement for Ransom

The strength of the business-purpose argument changes considerably depending on what the ransom is actually buying. Where a victim's life or physical safety is genuinely at risk, the payment's function is difficult to separate from ordinary self-preservation, an interest every person holds regardless of whether they carry on any business at all, and one Canadian tax law has consistently treated as personal in character even where a business consequence flows from it. Where, however, the kidnappers intend to keep the victim unharmed until payment and the sole effect of non-payment is continued confinement rather than any threat to health, the question becomes genuinely harder.

The governing Canadian authority on this kind of mixed personal-and-business outlay is Symes v Canada, [1993] 4 SCR 695, in which the Supreme Court of Canada disallowed a self-employed lawyer's attempt to deduct her childcare costs as a business expense, notwithstanding her argument that she could not earn business income without them. The Court's reasoning is the important part: an outlay's practical necessity to earning income is not, on its own, sufficient for deductibility. What matters is the outlay's essential character, and childcare retained the essential character of a personal or living expense, one that exists for a parent whether or not that parent carries on any business at all, notwithstanding how directly it bore on the taxpayer's capacity to earn income.

Applying that essential-character test to a ransom paid for pure confinement produces a genuinely two-sided answer. The case for treating it as personal follows the same pattern Canadian tax law applies to a taxpayer's own health: legal fees to defend one's own liberty in a criminal proceeding are treated as personal even where a conviction would end the taxpayer's ability to work, and the medical expense regime, not the business expense provisions, governs a self-employed person's health costs no matter how directly an illness threatens their income. On that pattern, one's own physical liberty sits in the same personal category as one's own health, regardless of what caused the threat to it, kidnappers or otherwise.

The case for treating it as a business expense rests on a feature Symes did not have to confront, and it is a real one, not a rhetorical point. The need for childcare exists for every parent, working or not; it has nothing to do with whether a business exists. A ransom demand triggered specifically by a business's wealth or public profile has no equivalent independent existence. Absent the business, there would have been no kidnapping and no demand at all. That causal exclusivity distinguishes this fact pattern from Symes in the taxpayer's favour, and it means the essential-character inquiry has to weigh what is being protected, liberty, which tax law treats as personal, against why it was ever at risk, a cause that is entirely and exclusively business, in a way Symes itself never required. This also draws renewed support from the English authority Mitchell v B W Noble Ltd (1927) 11 TC 372, a King's Bench Division decision, where a company's payment to an individual to avoid a scandal that would have damaged the business was deductible because its function was to protect the trade, notwithstanding that the payment ran to a person rather than to property.

The honest conclusion is that this sits closer to a genuine toss-up than either a confident personal or confident business characterization, and it is a harder question than the threat-to-life scenario precisely because the countervailing personal-liberty pattern in Canadian law is real, not because the business-purpose argument is weak.

"This is exactly the kind of question that has never been tested because, until recently, it rarely arose for Canadian taxpayers. Crypto wealth has changed that. A taxpayer in this position should not assume the answer either way. The purpose test genuinely turns on the specific facts, whether life or health was at risk, who was taken, who pays, and how the business is structured, and each of those variables can move the answer."

- David J. Rotfleisch, a Law Society of Ontario Certified Specialist in Taxation.

The Employee Versus the Principal: Different Tax Consequences

Who is kidnapped, and who is making the payment, changes the analysis substantially. Where a business, whether a sole proprietorship, a partnership, or a corporation, pays to free an arm's length employee, the case for deductibility is comparatively strong. The payer is not protecting its own body or liberty, it is protecting its investment in a valuable person and discharging an employer's practical interest in retaining staff and continuing operations, closer in character to the trade-protection purpose recognized in Mitchell. This is broadly consistent with the CRA's own recognition, reflected in Income Tax Folio S2-F3-C2 on employee benefits, that protective measures provided to an employee facing an employment-related threat can be treated as primarily for the employer's benefit rather than as a personal perk to the employee.

Where the person kidnapped is the business's own principal, the analysis is harder, and the answer depends on business structure in a way that has nothing to do with formal legal personality and everything to do with whose personal interest is actually being protected.

Sole Proprietorships and Partnerships

A sole proprietor who pays to ransom an employee is spending business funds to protect someone else, and that expense is deductible on the same basis as wages or any other cost of retaining staff, regardless of the fact that the proprietor has no separate legal identity from the business. The analysis changes completely, however, once the proprietor is the one kidnapped. There is no entity standing between the proprietor and the expense, so the payment is transparently the taxpayer's own money buying his own release, indistinguishable in that respect from any other personal expenditure simply funded out of business income. A partnership faces a related problem where the ransomed individual is one of the partners: an outlay to free a specific partner reduces income allocated to every partner, including those who were never at risk, which more closely resembles a personal draw charged against partnership funds than a genuine cost of the partnership's business, and CRA's consistent treatment of individual partners' personal expenses run through partnership accounts supports that characterization.

Corporations and the Shareholder-Benefit Problem

A corporation occupies a different position because it has no personal life of its own to protect, which removes the 18(1)(h) objection entirely when a genuine arm's length employee is ransomed. The harder case is a closely held corporation paying to ransom its own controlling shareholder. The corporation's formal legal separateness might suggest the payment is simply a business expense to the corporation, but CRA's shareholder-benefit analysis under section 15(1) looks past that formal separateness to substance, asking whose interest was primarily served. Where the person ransomed is also the person who controls the payer, CRA has a reasonably strong basis to argue the payment was primarily for the personal benefit of the controlling shareholder rather than the corporation's business interest, the same reasoning CRA applies when a closely held company pays an owner-manager's personal legal defence costs or other expenses that are personal in substance despite being paid by the corporation. The likely outcome in that scenario is not a clean denial of the corporate deduction, but a deduction to the corporation paired with a taxable shareholder benefit to the individual, which meaningfully reduces the practical tax benefit even if the technical deduction survives.

"Incorporation does not make this question go away, it just moves where the argument happens," says David J. Rotfleisch, founding tax lawyer at Rotfleisch & Samulovitch P.C. and a Law Society of Ontario Certified Specialist in Taxation. "A controlling shareholder who assumes the corporate structure alone solves the deductibility problem is often surprised to find the same personal-benefit analysis waiting on the other side, just under a different section of the Act."

"A controlling shareholder who assumes the corporate structure alone solves the deductibility problem is often surprised to find the same personal-benefit analysis waiting on the other side, just under a different section of the Act."

Property-Based Extortion Remains the Clearest Case

Set against all of the above, the most defensible deduction by far involves no kidnapped person at all, and here the analysis moves from inference to actual CRA administrative guidance. In External Technical Interpretation 2023-0984251E5, dated September 21, 2023, the CRA confirmed that losses arising from ransomware attacks and business email compromise scams, including payments made directly to the criminals responsible to recover encrypted business data, are generally deductible in computing income from a business, provided the expense falls within the ordinary framework of subsection 9(1) and paragraphs 18(1)(a) and (b), and is reasonable in the circumstances under section 67. The CRA drew a related but distinct line in the same interpretation, denying any deduction for revenue simply lost or forgone as a result of the attack itself, as opposed to amounts actually paid out. Extortion payments made to prevent the destruction of business property, a threat to destroy business records, or a ransomware demand to unlock a crypto business's own wallets fall squarely within the fact pattern the CRA has already addressed. Where the target is property or data rather than a person, the personal-expense objection that complicates every scenario above simply does not arise, and taxpayers in this position now have a genuine administrative position to point to rather than a mere analogy to theft-loss treatment.

How Other Jurisdictions Have Approached This Question

No Canadian court or tribunal has addressed the deductibility of a ransom paid to free a kidnapped person, but at least two foreign courts have, and they reached opposite conclusions. In Commissioner of Income Tax v Khemchand Motilal Jain, Tobacco Products (P) Ltd, ITR No. 42 of 1998, the Madhya Pradesh High Court in India held that ransom money paid by a company to secure the release of one of its kidnapped directors was deductible as business expenditure. The court's reasoning turned on a provision specific to Indian tax law, an explanation to section 37(1) of India's Income Tax Act that disallows deductions for expenditure incurred for a purpose that is itself an offence, and the court held that provision did not apply because the company had not committed any offence, the offence had been committed against it. That is a different statutory question than the personal-expense analysis under Canada's 18(1)(h), and the decision is foreign and non-binding in any Canadian proceeding, but it remains a genuine judicial precedent for the fact pattern this section examines, a business paying to free one of its own officers, and it resolved in favour of deductibility.

Germany's Finanzgericht Münster, a fiscal court, reached the opposite result in a judgment dated October 5, 1979, file number X-II 3122/77 F, when Aldi co-founder Theo Albrecht sued to have the ransom paid for his own 1971 kidnapping recognized as a deductible Betriebsausgabe, a business expense, of the company. The court rejected the claim, holding that the kidnapping was a Privatsache, a private matter, notwithstanding that Albrecht was the company's own principal and that the demand arose directly from his position and wealth. Read together, the Indian and German decisions bracket the exact uncertainty this section has identified in the Canadian context: one court found a business ransomed for one of its own officers to be a business expense, and another found the same category of payment to be inherently personal.

The widely repeated account of the 1973 kidnapping of John Paul Getty III is often cited alongside these cases but does not belong in the same category, and it is frequently misattributed. Contrary to popular retellings that describe the ransom as deductible under Italian law, contemporaneous and retrospective reporting, including an account published by Time magazine, indicates the relevant law was American: Getty's advisors reportedly capped the payment at the maximum amount deductible as a personal casualty loss under the United States Internal Revenue Code as it then stood, which limited such write-offs to a percentage of the taxpayer's income. That characterization, a personal casualty or theft loss rather than a business expense, was reportedly the position taken by Getty's own accountants rather than the holding of any court or tax authority, and it is worth noting for what it actually illustrates: even in the one prominent historical case popularly cited as ransom being tax-advantaged, the mechanism used was a personal loss provision, not a business expense deduction, which is broadly consistent with the personal-liberty characterization this section has identified as the more traditional default, even as the Indian and German cases show that default is not universal.

Kidnap and Ransom Insurance Premiums: A Subset of the Same Question, Not a Separate One

The premium paid for kidnap and ransom insurance is not an independent question requiring its own justification. A policy that would fund an individual's own ransom is simply the taxpayer arranging, through a third-party risk pool, to fund the very payment examined above. Its deductibility should be coextensive with the payment's, on the same facts, not derived from separate insurance-specific reasoning, and it should not be assumed to sit on safer or more settled ground than the payment itself does.

It might seem relevant that most individuals who carry this kind of coverage never actually collect on it, but that fact does not move the analysis in either direction. The same is true of virtually all business insurance. Most businesses carrying fire, theft, or liability coverage never file a claim, and no one treats those premiums as anything less than fully deductible in every year regardless. An insurance premium's character has never turned on how often the insured event actually occurs; it turns on the character of the risk being insured, exactly the same essential-character question already at issue for the ransom payment itself.

Where a business owns a policy that indemnifies the business itself for the cost of freeing a genuine third-party employee, ransom reimbursement, crisis-response consultants, negotiation services, and related legal and public-relations fees, the underlying risk is a business risk, and the premium is deductible under the ordinary purpose test in paragraph 18(1)(a) for the same reason the direct payment would be in that scenario. A business incurring GST/HST on these response costs should also confirm it is claiming the input tax credits it is entitled to, since these are ordinary commercial expenses for GST/HST purposes just as they are for income tax purposes. Where an individual instead takes out a policy on his own person, intending any payout to fund his own eventual ransom, the premium's character should track whatever conclusion applies to the direct payment on the same facts, discussed above as a genuinely close question turning on whether life or health was ever at risk. It should not be treated as more clearly deductible than that underlying payment merely because it has been packaged as a periodic premium rather than a lump sum paid at the moment of crisis.

Section 20.01 of the Income Tax Act remains useful here, though for a narrower point than insurance-specific reasoning might suggest. That section permits a self-employed individual to deduct premiums for a private health services plan only by expressly overriding paragraphs 18(1)(a) and 18(1)(h), its opening words state the deduction applies notwithstanding both provisions. Parliament would not have needed to legislate that override if a self-employed individual's premium for a personal-risk policy were already deductible under the ordinary purpose test. What the provision confirms is that insuring a risk whose essential character is personal does not become a business expense merely by being packaged as insurance rather than paid directly. It does not, on its own, tell us whether kidnap and ransom risk is properly categorized as personal or business in the first place, since that categorization is precisely the open question already identified for the direct payment, not a question insurance law answers independently.

The closely held corporation scenario again sits in between, and here the analysis is more settled. A corporation that owns a kidnap and ransom policy insuring its own controlling shareholder faces the same shareholder-benefit analysis that applies to a direct payment in that scenario: the premium may well be deductible to the corporation, but CRA has a reasonable basis to treat all or part of the coverage as conferring a personal benefit on the insured shareholder under subsection 15(1), particularly where the policy would pay proceeds to that individual or their family rather than reimbursing the corporation's own documented response costs. The safer structure, for the same reasons discussed throughout this section, has the corporation as both policyholder and beneficiary, indemnifying its own costs of responding to a genuine third-party employee's kidnapping, rather than insuring the business's own principal.

No Canadian ruling addresses kidnap and ransom insurance specifically, so this remains, like the ransom payment itself, an area of principled inference rather than settled law. What should not be assumed is that the premium occupies safer ground than the payment it is designed to fund. On the facts that matter most, an individual insuring his own eventual ransom, the two questions are, in substance, the same question asked twice.

Where This Leaves Canadian Crypto Entrepreneurs

No part of this analysis should be read as a confident answer either way, and as noted above, none of it reflects settled law. This is a genuinely novel and unresolved area of the Income Tax Act, and a taxpayer who assumes a ransom payment, or its associated insurance premium, is automatically deductible, or automatically denied, is equally likely to be wrong. What can be said with more confidence is that the answer depends heavily on facts a taxpayer should document carefully at the time, whether life or health was at risk, precisely who was taken or insured, who made the payment, and how the business is structured, and that a taxpayer facing this situation should obtain advice from an experienced crypto tax lawyer in Toronto before filing a position on either side of this question, given the complete absence of direct Canadian authority and the real possibility of a CRA challenge regardless of which position is taken. A taxpayer whose deduction is denied on reassessment is not without options at that point either; our guide to challenging a CRA reassessment that denies a claimed business deduction sets out the objection deadlines and evidentiary burden that apply from that stage forward.

Pro Tax Tips for Anyone Facing a Ransom Deductibility Question

A taxpayer who has actually paid, or is insuring against, a ransom should treat contemporaneous documentation as the single most important step available. Whether the victim's life or health was genuinely threatened, who was taken, who made the payment, and how the business is structured will all drive the outcome of any later CRA review, and these are precisely the details that are hardest to reconstruct after the fact. Recording them at the time, including any communications with kidnappers, law enforcement, or a crisis-response firm, preserves the factual record a filing position will ultimately depend on.

Given the complete absence of Canadian authority in either direction, this is a poor candidate for a taxpayer to resolve alone or through an accountant in the first instance. Consulting a Canadian tax lawyer before taking any filing position preserves solicitor-client privilege over the analysis and strategy, protection that does not extend to the same conversation held with an accountant first. Where a corporation is considering deducting a payment made to free its own controlling shareholder, the shareholder-benefit exposure under subsection 15(1) should be assessed before the return is filed, not after CRA raises it on audit, since structuring the payment and any related insurance proceeds properly at the outset materially affects the practical outcome.

"Crypto tax exposure is not static, it compounds. Delay increases both financial and legal risk. The sooner the issue is addressed, the more options remain available," notes David J. Rotfleisch, a Certified Specialist in Taxation with over 35 years of experience in Canadian tax law. "That principle applies just as much to a novel question like this one as it does to an ordinary unreported crypto gain. Document the facts, get advice before you file, and do not assume the answer either way."

"Document the facts, get advice before you file, and do not assume the answer either way."

- David Rotfleisch

Finally, anyone purchasing kidnap and ransom coverage, personally or through a business, should review who owns the policy and who it pays before assuming the premium is deductible. As this article has set out, the safer structure has a business as both policyholder and beneficiary, indemnifying its own documented response costs, rather than an individual insuring his own eventual release or a closely held corporation insuring its own controlling shareholder. A taxpayer who has already filed a return claiming this kind of deduction without the benefit of this analysis, and who is now uncertain whether the position holds up, should also consider whether voluntary disclosure is available to correct the filing before the CRA identifies the issue independently.

Frequently Asked Questions About Ransom Payment Deductibility in Canada

Is a ransom paid to free a kidnapped crypto executive or business owner tax deductible in Canada?

This is an unresolved question with no direct Canadian authority. The outcome depends heavily on the specific facts, including whether the victim's life or health was at risk, whether the person ransomed was an employee or the business's own principal, and whether the business is a proprietorship, partnership, or corporation. Payments to protect business property from destruction have a stronger basis for deduction than payments to free a person, and payments to free a genuine employee have a stronger basis than payments to free the business's own controlling owner. Anyone facing this situation should obtain advice from an experienced Canadian tax lawyer before taking a filing position.

Does it matter whether the ransom is paid to free an employee versus the business owner?

Yes, significantly. A business paying to free a genuine arm's length employee has a comparatively strong case for deductibility, since the payment protects the business's investment in that person rather than the payer's own body or liberty. Where the person kidnapped is the business's own principal, a sole proprietor, a partner, or a controlling shareholder, the analysis is considerably harder and depends on business structure.

Are kidnap and ransom insurance premiums deductible in Canada?

The premium's deductibility generally tracks the deductibility of the ransom payment it would fund, rather than being an independently easier question. A business policy that indemnifies the business itself for the cost of freeing a genuine employee has a strong case for deductibility. An individual's own policy on himself, intended to fund his own eventual ransom, should be analyzed the same way as the direct payment would be on the same facts.

Has any Canadian court ever ruled on whether a ransom payment is tax deductible?

No. There is no reported Canadian decision and no CRA administrative position addressing the deductibility of a ransom paid to free a kidnapped person. Courts in India and Germany have addressed comparable fact patterns and reached opposite conclusions, but neither decision is binding in Canada.

Can a corporation deduct a ransom paid to free its own controlling shareholder?

The corporation may have a technical basis to deduct the payment, but CRA has a reasonable basis to treat all or part of the amount as a taxable benefit to the shareholder under subsection 15(1), since the corporation's shareholder-benefit analysis looks past legal separateness to ask whose interest the payment primarily served. The likely practical outcome is a deduction to the corporation paired with an income inclusion to the individual, which reduces the net tax benefit.

Does it matter if the ransom is paid in cryptocurrency rather than cash?

Yes, for a separate reason. Paying a ransom in cryptocurrency is a disposition of that property at its fair market value for Canadian tax purposes, regardless of whether the payment is ultimately found to be deductible. This can trigger a capital gain on the crypto handed over even where the underlying payment is characterized as personal and non-deductible.

What records should I keep if I pay a ransom and might later claim a deduction?

Contemporaneous documentation is essential given how fact-dependent this question is. Records should establish whether the victim's life or health was genuinely at risk, exactly who was kidnapped and their relationship to the business, who made the payment and from what account or entity, and how the payment amount was determined. Communications with kidnappers, law enforcement, and any crisis-response or negotiation firm, along with corporate resolutions authorizing the payment where applicable, should all be preserved, since these details are far harder to reconstruct after the fact than to record at the time.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.