BC Restricted Insurance Agency 2027: dealer operating guide

This is operating guidance, not legal advice. Dealers should route product classification, disclosure wording, seller authorization, compensation changes, and implementation decisions through BC counsel before changing the F&I menu or transaction workflow.

The practical point is narrow: British Columbia has created a restricted insurance agency path for certain non-insurance businesses that sell specified insurance products incidentally to their ordinary business. Motor vehicle dealers are in scope for credit protection insurance, guaranteed asset protection insurance, and vehicle warranty insurance under the Restricted Insurance Agent Licence Regulation.

The regime matters because it changes the control surface in the F&I office. A dealer cannot treat RIA readiness as a form, a one-time licence application, or a compliance binder. The store needs a product-by-product map, a designated representative path, seller training evidence, insurer-contract evidence, disclosure logic, transaction records, and a management process for edge cases.

The public argument should not be panic. It should be precision. The law does not say every F&I product disappears. It does not say every product margin is capped. It does say the dealer has to know which insurance products it is allowed to sell, who is allowed to sell them, what has to be disclosed, and how the dealership will prove that the sale was controlled at the time it happened.

Order in Council 598/2025 approved the Restricted Insurance Agent Licence Regulation and brings sections 30 and 31 of the Financial Institutions Amendment Act, 2019 into force effective January 1, 2027. Those provisions create the restricted insurance agent licence architecture and attach the regulation that identifies the prescribed classes of persons and insurance.

For motor vehicle dealers, the regulation lists credit protection insurance, guaranteed asset protection insurance, and vehicle warranty insurance. The regulation also says a restricted insurance agent licensee acts only in respect of optional insurance and only incidentally to the ordinary business of the licensee.

The regulation requires a representative, designated by the licensee and approved by Council, to be the primary contact for Council. In operating terms, that is not just a named person. It is an accountability role that should have access to the product map, insurer authorizations, training records, disclosure versions, exception logs, and renewal calendar.

Order in Council 600/2025 separately brings into force the Financial Institutions Act provision that gives Council rulemaking authority for restricted insurance agents and their employees and agents. That matters because the statute and regulation are the anchor, while much of the operating detail still has to be expressed through Council Rules and implementation materials.

The Insurance Council says the RIA licence program is still being developed through consultation and rulemaking before licences can be issued. Its implementation page says public consultation on the Rules needed to establish the program concluded April 27, 2026, feedback is currently being reviewed, and all new information will be released through its website.

As of source review on May 26, 2026, the public Council Rules and Code of Conduct page identifies the current Council Rules as effective April 1, 2024. The current Council Rules PDF does not yet contain a final restricted insurance agency rule package or a final Rule 7(25) for RIA transactions.

That distinction has to stay visible in dealer materials. The statute and regulation are enacted. The Council rulemaking power is enacted. The proposed licence program, proposed disclosure list, proposed fee path, training details, forms, and final application mechanics should be treated as current implementation guidance until final Council Rules, final forms, or counsel review confirm them.

This is not wordsmithing. If a dealership builds a workflow from proposed wording and the final rules change, the store may need to rework disclosures, training gates, insurer authorization checks, compensation calculations, and audit evidence under launch pressure. The safer build is modular: lock the settled law, isolate the proposed fields, and make version changes easy.

The dealer problem is not just whether the store needs an RIA licence. It is whether each product on the menu is actually inside the RIA path, outside it, or unknown. Labels used in the box do not control the legal answer.

BCFSA Regulatory Statement 24-008 is the source that makes dealers slow down on product classification. BCFSA states that product warranties and vehicle warranties are insurance under BC law, but distinguishes vehicle warranty insurance from automobile insurance. Vehicle warranty insurance relates to loss or damage to motor vehicles arising from mechanical failure. Automobile insurance covers automobile loss or damage from theft, accident, glass, paint, or other fortuitous events.

That means a mechanical-breakdown product, a GAP product, credit protection, paint, glass, tire, key, theft, chemical, appearance, and other protection products should not be treated as one bucket. Some may map cleanly to a listed RIA class. Some may require a different insurance analysis. Some may be non-insurance products with consumer-protection obligations. Some may be unknown until counsel reviews policy wording.

The safe operating sequence is product inventory, policy wording review, class-of-insurance mapping, insurer authorization confirmation, counsel sign-off, disclosure design, then menu design. If the store starts with the menu, it may build sales behavior before it has verified the legal lane.

The public conversation can easily get this wrong. The Insurance Council public materials describe proposed written disclosure requirements, including a compensation disclosure if the amount of commission for the sale is more than 30% of the price paid for the insurance product. That is not the same as a statutory hard cap on dealer margin.

The proposed compensation disclosure should be described as proposed until final Council Rules or counsel-confirmed implementation materials say otherwise. Dealers should avoid public claims that BC has imposed a final 30% cap, that all F&I economics are prohibited, or that a disclosure trigger alone decides whether a product can be sold.

The operating problem is still real. If the final rule requires disclosure above a threshold, the dealership needs a reliable calculation method. The system has to know the client price, the direct or indirect commission, compensation, inducement, or benefit included in the final wording, the product cost treatment, the disclosure version, the seller, the timestamp, and the buyer acknowledgement.

A sentence on a form will not be enough if the store cannot show why the disclosure was or was not required. The control needs to sit before delivery, not after accounting discovers a margin pattern.

Disclosure is not a PDF problem. It is a transaction-control problem. The system must know which product triggered the disclosure, which version of the disclosure applied, who delivered it, when it was delivered, whether the buyer acknowledged it, and whether any required field was incomplete or overridden.

The proposed disclosure list points to fields dealers can design now without pretending final forms are settled: optional purchase, possible other sources of coverage, cancellation, insurer contact, coverage information delivery, insurer contracting party, loan mismatch where applicable, and proposed compensation-trigger logic.

The dealer should version disclosures the same way it versions desking worksheets or lender forms. A disclosure printed in January 2027 may not be the same form used after a final Council update, a provider wording change, or a counsel instruction. The transaction record should preserve the version used at the time of sale.

The Insurance Council public materials describe proposed qualification and ongoing requirements that include E&O insurance, at least one contract with an insurer authorized to do business in BC, a Designated Representative, accredited training for sales representatives, disclosure requirements, annual renewal, and continued insurer authorization.

That creates four gates. The agency gate asks whether the dealership has the right licence, E&O, renewal status, and Designated Representative. The seller gate asks whether the employee or agent has completed the required training for the product being sold. The product gate asks whether the product is in a permitted class and tied to an authorized insurer. The disclosure gate asks whether the required fields and acknowledgement are complete.

If those gates live in a binder, they will fail under volume. They need to live in the deal path. A transaction should not proceed through an insurance product sale unless the agency, seller, product, and disclosure conditions are all true at the time of sale.

The store should also define who can override what. A missing seller-training record should not be overridden by the same person who benefits from closing the deal. An unknown product classification should go to the counsel queue, not the desk.

Dealers should not wait for providers to push perfect 2027 packages. A provider may have a training path, a disclosure draft, an insurer authorization story, and a compensation calculation method, but the dealer still owns the store-level control environment.

Every provider packet should answer the same questions: What is the product legal classification in BC? Which insurer underwrites it? Is that insurer authorized for the class? What seller training is required? Who accredits the training? What disclosure fields are required? How are refunds, cancellations, claims, and complaints handled? What product wording changed for 2027? What data can the dealer retain without storing customer PII?

The answer does not need to be public. It needs to be retrievable. When management reviews the product menu, the store should be able to see the source document, effective date, owner, open questions, and counsel status for each product.

The RIA operating file should be dealer-private and no-PII by design. It should not collect customer names, addresses, phone numbers, emails, SINs, or credit application details. The readiness question can be answered with product codes, seller codes, dates, prices, costs, disclosure states, training states, provider records, and exception codes.

A useful operating file has eight tabs: product inventory, legal-classification status, insurer authorization, Designated Representative and E&O, seller training, disclosure versions, transaction evidence, and change log. Each tab should have an owner, last-reviewed date, source link or document reference, and open-question field.

The transaction evidence should be boring and reconstructable. For each in-scope sale, the store should be able to show product class, seller training state, agency licence state, insurer authorization state, disclosure version, required-field completion, buyer acknowledgement, exception code if any, and timestamp.

The purpose is not surveillance. It is evidence. If Council, counsel, a provider, or management asks what happened on a transaction, the store should not need memory, screenshots, or a group chat to answer.

First, build the product inventory. Every F&I product should be listed with provider, policy wording, buyer-facing name, internal product code, class-of-insurance status, underwriter, insurer authorization, retail price, dealer cost, gross per unit, cancellation path, current disclosure, and owner. Do not use informal menu names as the source of truth.

Second, split products into four buckets: likely RIA-eligible, likely outside RIA because it appears to be automobile insurance or another class, non-insurance product requiring separate consumer-protection review, and unknown. Unknown is not a failure. Unknown is the counsel queue.

Third, name the Designated Representative candidate and backup process. Decide who owns Council contact, annual renewal, E&O, insurer authorization evidence, training records, disclosure versions, and exception review.

Fourth, ask providers for dated 2027 transition packets. If a provider cannot answer product classification, insurer authorization, training, disclosure, cancellation, and compensation-calculation questions, record the gap and decide whether the product remains on the future menu.

Fifth, simulate ten recent deals. For each sale, ask whether the proposed 2027 workflow could prove every required condition. If the answer depends on someone remembering what happened, the evidence model is not strong enough.

Sixth, set a pre-launch freeze date. The store should not be trying to classify products, train sellers, rewrite menu logic, and build disclosure proof in the same week applications open.

Do not wait until applications open. November 2026 is too late to begin product classification, disclosure design, training planning, and system changes.

Do not assume the RIA licence fixes every product. It does not. It is a restricted path for specified classes and specified persons. The classification work remains product-specific.

Do not treat proposed Rule 7(25) disclosure as final law unless final Council Rules or counsel-confirmed materials support that conclusion. If the trigger appears in final rules, the dealership needs reliable compensation/benefit calculation, product price, disclosure trigger, record version, and transaction proof.

Do not publish provider-specific claims, margin claims, tax-impact numbers, or appeal-status statements unless the source is verified and counsel has approved the wording. Public RIA material should stay category-level, provider-neutral, and source-tied.

Do not let counsel be the first person to see the product inventory in December 2026. Counsel should review the map early enough that the dealership can change the menu before launch pressure arrives.

The right management standard is not panic. It is control. A dealer that begins now can enter 2027 with a defensible product map, a clean disclosure path, trained sellers, authorized product relationships, designated oversight, and transaction-level evidence.

A dealer that waits may still be able to apply, but it may be building compliance in the same month it is trying to sell vehicles, close contracts, keep funding moving, retrain staff, and answer customer questions. That is how avoidable errors happen.

The RIA regime is not just a legal change. It is a process-design test. The dealerships that treat it as a process-design problem will be calmer, cleaner, and easier to defend.

The internal question should be simple: if a regulator, provider, auditor, or principal asks why a product was sold on a specific day by a specific seller, can the store prove that the product, seller, agency, disclosure, and exception state were valid at that time? If not, the readiness work is not done.