Find the Right GRC Solution

Search and compare GRC technology built for the problems you’re trying to solve

FINRA Urges SEC to Extend Reg E-Delivery to SRO Rules & Retain Existing Guidance

FINRA Urges SEC to Extend Reg E-Delivery to SRO Rules & Retain Existing Guidance

By
Regulatory data powered by Corlytics
FINRA supports the SEC's proposed Regulation E-Delivery, which would allow default electronic delivery without prior affirmative consent.
🔒
Cancel anytime
Full archive access
Custom alerts
Key Takeaways
  • FINRA supports the SEC's proposed Regulation E-Delivery, which would allow default electronic delivery without prior affirmative consent.
  • It asks the SEC to (1) bring SRO delivery requirements and the E-SIGN Act exemption within the rule's scope and (2) keep the 1995, 1996, and 2000 SEC e-delivery guidance as an alternative.
  • The outcome will determine whether firms operate under one unified delivery framework or manage overlapping SEC and SRO regimes.
Deep Dive

FINRA supports the SEC's proposed Regulation E-Delivery, which would allow default electronic delivery without prior affirmative consent. It asks the SEC to (1) bring SRO delivery requirements and the E-SIGN Act exemption within the rule's scope and (2) keep the 1995, 1996, and 2000 SEC e-delivery guidance as an alternative. The outcome will determine whether firms operate under one unified delivery framework or manage overlapping SEC and SRO regimes.

First, the Proposal's definition of "covered information" excludes state law and SRO rule disclosures, including FINRA and MSRB requirements. FINRA asks the SEC to include SRO delivery requirements. Without that, each SRO would need separate rulemaking, including Section 19(b) filings, and implementation timelines would likely diverge and trail Reg E-Delivery's effective date. FINRA also flags the E-SIGN Act. Section 101(c) requires affirmative consumer consent for "in writing" requirements. The SEC proposes an exemption (§ 303.100), but SROs lack express authority under Section 104(d)(1) to create one. Some firms therefore read FINRA "in writing" rules as still requiring affirmative consent. FINRA also suggests clarifying that rules permitting multiple delivery methods, such as FINRA Rule 2124(c), can be satisfied under Reg E-Delivery. Second, FINRA asks the SEC to retain the existing guidance as an alternative. The Proposal would supersede the 1995 and 1996 Releases and keep most of the 2000 Release, and FINRA's 1998 guidance (Notice to Members 98-03) is built on that guidance. FINRA argues that small and online-only firms may prefer the current model, which allows account opening to be conditioned on global e-delivery consent. It also argues that firms keeping affirmative-consent models would still face most Reg E-Delivery conditions, and that older investors prefer paper more often: 48% of those ages 55 to 64 and 43% of those 65 or older prefer electronic delivery, versus 57% of those ages 25 to 54.

The letter is dated September 21, 2026. No effective or compliance dates are stated. FINRA expects SRO implementation to follow the effective date of Reg E-Delivery if SROs must act separately. Any final rule could change these dynamics.

Compliance teams should:
- Inventory delivery obligations across SEC, FINRA, MSRB, and state requirements, and identify which would sit outside Reg E-Delivery.
- Assess how current consent-based processes, website and system capabilities, paper-on-request workflows, and record retention compare with the Proposal's conditions.
- Evaluate whether to adopt Reg E-Delivery, remain on existing guidance if retained, or adopt a hybrid approach.
- Update policies and procedures, and monitor the final rule and any FINRA rule filing.
- Consider submitting comments, especially on E-SIGN Act treatment and small-firm costs.

The main risks are fragmented frameworks, inconsistent E-SIGN interpretations, confusing customer notices, late or missed delivery, and implementation costs that the SEC acknowledges it cannot fully quantify.

Source: Financial Industry Regulatory Authority

Oops! Something went wrong