Canada: Off-Coverage Still Means On-Claims

Last Updated: November 3 2016
Article by Daniel Strigberger

A FSCO arbitrator has confirmed that the first insurer that receives a completed application for accident benefits is required to adjust and pay the claim, even if the insurer is taking an off-coverage position.


In Cankaya v. Intact / Cankaya v. Unifund, the claimant was working on the engine of a 2001 BMW vehicle he was about to repair at his mechanic shop. The cooling fan or other part of the BMW broke apart and flew into his face. He sustained multiple injuries. He was acting in the course of his self-employment as a garage repairman when the incident occurred.

At the time of the incident, the claimant was insured with Unifund under a standard Ontario Automobile Policy (OAP 1), which insured his personal vehicle. He was also insured with Intact under the standard Ontario Garage Automobile Policy (OAP 4). Both policies were valid at the time of the incident.

The claimant submitted an application for accident benefits to Unifund on January 10, 2014. On March 27, 2014, Unifund advised the claimant that he was precluded from receiving any accident benefits under his policy because of the garage exclusion under section 1.8.4 of the OAP 1.

On April 15, 2014, the claimant's lawyer wrote to Unifund and advised about the Intact policy. The claimant's lawyer encouraged Unifund to pursue a priority dispute against Intact, pursuant to O. Reg. 283/95 . Unifund refused to do so.

On June 18, 2014, the claimant submitted an application for accident benefits to Intact. Intact denied the application on the basis that it was not the first Insurer to receive a completed application.

The claimant did not receive any benefits, so he applied for mediation and arbitration at FSCO. A preliminary issue hearing was held to determine a number of issues, the main one being whether FSCO had jurisdiction to determine whether section 1.8.4 of the OAP 1 could relieve Unifund of its obligations to respond/adjust and pay benefits, pursuant to section 2.1 (6) of O. Reg. 283/95. In other words, could FSCO determine coverage or was that issue reserved for a priority dispute?

Priority Dispute Scheme ( in a nutshell)

Section 2.1 (6) of O. Reg. 283/95 requires the first insurer who receives a completed application for accident benefits to respond and pay benefits pending the outcome of any priority dispute with another insurer. In Kingsway v. Ontario (2007), the Court of Appeal stressed that the "pay now, fight later" principle is vital:

Section 2 of regulation 283 is critically important in the timely delivery of benefits to victims of car accidents. The principle that underlies section 2 is that the first insurer to receive an application for benefits must pay now and dispute later. The rationale for this principle is obvious: persons injured in car accidents should receive statutorily mandated benefits promptly; they should not be prejudiced by being caught in the middle of a dispute between insurers over who should pay, or as in this case, by an insurer's claim that no policy of insurance existed at the time.

Where an insurer receives a completed application and believes that another insurer has priority over it for the claims, O. Reg. 283/95 allows the insurer to compel the other insurer(s) to participate in a priority dispute. The entire procedure is contained in the Regulation and disputes are resolved in private arbitration, pursuant to the Arbitration Act, 1991.

O. Reg. 283/95 has strict timelines: When an insurer receives a completed application for accident benefits, it has 90 days from the date of receipt to investigate priority and to give a target insurer written notice of the dispute, pursuant to section 3. An insurer that fails to give written notice within that 90-day period is barred from pursuing priority against the other insurer, unless it can show, firstly, that 90 days was not enough time to make its determination and, secondly, that it made reasonable investigations during those 90 days. These two "saving provisions" are often difficult to satisfy.

Section 4 requires the insurer giving notice under section 3 to also give the claimant a Notice to Applicant of Dispute Between Insurers form, which is a prescribed document that advises the claimant of the dispute and the name or names of the other insurer(s) who might have priority over the claims. The claimant is given 14 days to object to the transfer of their file. If the claimant objects, he or she becomes a participant in any proceeding to determine priority. The Superior Court1 held recently that the notice under section 4 must be given within 90 days after the insurer receives the claimant's completed application for benefits.

Once an insurer gives its written notice, subsection 7 (3) states that any arbitration to decide the issues between the parties must be initiated within one year from the date the insurer paying benefits gave its priority dispute notice.

Cankaya Decision

As noted above, Unifund rejected the application on the basis that the claimant was subject to the garage exclusion under section 1.8.4 of the OAP 1. Having determined that there was no coverage under the policy, Unifund refused to adjust and pay benefits pending the outcome of any priority dispute with Intact. Actually, Unifund refused to initiate a priority dispute against Intact.

Meanwhile, Intact refused to adjust the claim on the basis that it was not the first insurer to receive an application for accident benefits. Essentially, Intact argued that Unifund was the first insurer to receive an application, so only Unifund was compelled to pay now and dispute later.

The first issue was whether FSCO had jurisdiction to determine whether section 1.8.4 of the OAP 1 could relieve Unifund of its obligations under section 2.1 (6) of O. Reg. 283/95. The arbitrator relied on previous FSCO decisions (Vieira and Royal & SunAlliance and Chubb, 2004 FSCO App) and Bianca v. Wawanesa, 2004 FSCO Arb) and held that FSCO did not have jurisdiction to make that decision.

Put another way, FSCO (and the courts, and likely the LAT) often determines whether a particular claimant was involved in an "accident". This is a general coverage issue that applies to a claimant regardless of where she applied for benefits. If she was involved in an "accident", she is entitled to benefits from at least one insurer. If she was not involved in an "accident", she is not entitled to benefits from any insurer. FSCO has jurisdiction to make this determination.

However, where there is no issue as to whether a claimant was involved in an "accident", any other coverage issues (i.e., whether the claimant is an "insured person" under a particular policy) is determined in a priority dispute between insurers. FSCO does not have the jurisdiction to make that determination.

Although FSCO does not have jurisdiction to determine coverage in a priority dispute, it t is well settled law that FSCO has the jurisdiction to determine whether an insurance company complied with section 2.1 (6) of O. Reg. 283/95. The test is whether there is a sufficient nexus between the claimant and the target insurer. For example, in Vieira, there was a nexus even though the policy under which the application was made was not in force at the time of the accident.

It is easy to see the nexus between Mr. Cankaya and Unifund: At the time of the accident he was a named insured of Unifund. Therefore, Unifund's obligations under section 2.1 (6) of O. Reg. 283/95 would have been triggered when its insured applied for benefits under his policy. It would be open to Unifund to rely on any exclusions under section 31 of the SABS to deny certain benefits. Unifund could also pursue a priority dispute against another insurer, such as Intact. In this case, it failed to do both.

Consequently, the arbitrator found that Unifund was required to adjust the claims and pay benefits:

Given my findings above in Issue 1, Unifund is obliged to respond and adjust Mr. Cankaya's application for statutory accident benefits.  This finding is necessary so Mr. Cankaya may be treated fairly and receives benefits under the SABS to which he is entitled.  As well it is consistent with the purpose and rationale of O. Reg. 283/95.


Except in the most unusual circumstances, any insurer in Unifund's position should take the safe route: They should accept the application, pay the benefits, and dispute priority.

If Unifund was correct that there was no coverage under its policy, the file would have gone to Intact and Unifund would not be responsible for paying benefits.

However, Unifund failed to pursue priority against Intact, so the merits of the dispute will never be resolved because the priority dispute would be time-barred. Accordingly, Unifund is now saddled with the responsibility to pay benefits indefinitely, regardless of whether priority rested with another insurer.

See Cankaya and Intact, FSCO A14-009220


1. Unifund Assurance Company v The Dominion of Canada General Insurance Company, 2016 ONSC 4337 (CanLII),

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.

To print this article, all you need is to be registered on

Click to Login as an existing user or Register so you can print this article.

Daniel Strigberger
In association with
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at and we will use commercially reasonable efforts to determine and correct the problem promptly.