Regulatory Explainer
BC Restricted Insurance Agency 2027: dealer operating guide
The retained local authority record describes a 2027 restricted insurance agency regime that reaches product mapping, seller readiness, disclosure, authorization, and evidence control. Verify current official sources before action.
- Retained
- The local statute and regulation record states the 2027 operating deadline.
- Recheck
- Council Rules and implementation details require current official-source verification.
- Control
- Public claims stay provider-neutral and source-tied.
01 / Understand
Read the operating guide and separate the enacted regulation from what the Council is still finalizing.
02 / Assess
Move to the Decision Dossier and map the product, seller, provider, authority, and evidence questions.
03 / Act
Use the builder only after the store has numbers and counsel has a review lane.
01 / Guide
The operating point
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.
03 / Guide
What still requires current-source verification
At the July 18, 2026 local source review, Insurance Council materials stated that public consultation had concluded April 27, 2026 and that feedback was being reviewed. Current rulemaking and Ministry-approval status was not checked in this implementation review.
The retained local record did not establish a final restricted insurance agency rule package or final Rule 7(25). Treat detailed rule text as unverified until the current adopted text is confirmed at the official source.
Keep retained enacted material separate from dated consultation material. The local OIC record states the product classes and January 1, 2027 commencement. Application mechanics, fees, training, forms, and final Council Rules require current official-source and counsel confirmation before a workflow relies on 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: preserve the retained enacted record, isolate unverified fields, and make version changes easy.
04 / Guide
The product boundary issue
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.
05 / Guide
The proposed 30 percent issue is a disclosure trigger
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.
06 / Guide
Disclosure is a transaction system
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.
08 / Guide
Provider readiness has to be documented
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.
09 / Guide
Build the RIA operating file
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.
The file is only useful if it is one file. When classification lives with the F&I manager, insurer paperwork with the controller, and training records in someone's inbox, the store has the information and still cannot answer the question.
The transaction evidence should be boring and reconstructable. For each in-scope sale, the store should be able to show that the product, the seller, the licence, the insurer authorization, and the disclosure were all valid at the moment of sale.
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.
10 / Guide
What the dealer should do now
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 transition packets keyed to the controlling authority then in force. 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 workflow could evidence every dealer-defined condition. If the answer depends on someone remembering what happened, the evidence model needs review.
Sixth, set a dealer-approved preparation checkpoint. The Insurance Council expects to open applications in November 2026, and says a dealership still selling under the prior exemptions must apply by March 31, 2027 to continue. Both are the Council's stated expectations, so confirm them at the official source, and do not postpone product classification, seller planning, menu logic, and disclosure evidence waiting for a firm opening.
11 / Guide
What management should not do
Do not treat the expected November 2026 opening or the March 31, 2027 deadline as guaranteed. They are the Insurance Council's stated expectations; confirm the current dates at the official source, and finish the preparation that does not depend on the exact date regardless.
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.
Route the product inventory for counsel review early enough that the dealership can address classification questions before relying on the future menu.
12 / Guide
The management standard
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.
Evidence and source notes
Last local source review: July 18, 2026. Current-law status in this implementation review: NOT CHECKED. Verify each current official source before action.
Open Decision Dossier- BC Government, New licence helps people understand add-on insurance
- Order in Council 598/2025, Restricted Insurance Agent Licence Regulation
- Order in Council 599/2025, related exemption and commission-regulation amendments
- Insurance Council of BC, Restricted Insurance Agency Licence
- Insurance Council of BC, RIA implementation and consultation status
- Insurance Council of BC, Getting a Restricted Insurance Agency Licence
- Insurance Council of BC, Council Rules and Code of Conduct page
- Insurance Council of BC, Council Rules PDF, version April 1, 2024
- BCFSA Regulatory Statement 24-008, Product Warranty, Vehicle Warranty, and Automobile Insurance
Where this goes next
Gate design is not a template. The control that stops the repeat is built with the store, against its own policy and volumes, in the mini-audit debrief.
Proof approach
The operating file is designed to be dealer-private and no-PII, so counsel and management can reconstruct the compliance state without relying on customer identity data or memory.