SEC Regulation E-Delivery Proposal: Comment Deadline

The Securities and Exchange Commission has proposed Regulation E-Delivery, a rule that would set conditions for delivering covered information to recipients electronically without first obtaining their affirmative consent. It appears at 91 FR 45884 under RIN 3235-AN57, and comments should be received on or before September 21, 2026.

Nothing in that document is in force. Regulation E-Delivery is a proposal, the Commission has not adopted it, and there is no compliance date attached to it. A firm that changes how it delivers statutorily required disclosure today would be acting on a rule that does not exist yet. The single date with operational meaning on this page is the date the comment record closes.

This brief covers what the proposal would actually change, who the proposal says it would reach, why a reader cannot look Regulation E-Delivery up in the Code of Federal Regulations today, and one date in the Federal Register record that is easy to misread as a deadline and is not one.

Key Takeaways

The Securities and Exchange Commission has proposed Regulation E-Delivery at 91 FR 45884. It would set conditions for delivering covered information to covered recipients electronically without first obtaining their affirmative consent, rescind a shareholder report transmission alternative, and amend proxy and tender offer dissemination rules. It is not in force. Comments should be received on or before September 21, 2026.

• The proposal is a proposed rule only. There is no compliance date, no phase-in, and nothing a firm is obliged to do because of it.

• It would do four distinct things, listed below. Everything else about it — the conditions themselves — is not stated in the Federal Register abstract and is not summarised here.

• Scope turns on three defined terms the abstract uses but does not define: covered entities, covered information and covered recipients. Any list of covered firms you read elsewhere, including one that sounds obvious, is somebody's inference.

• You cannot read Regulation E-Delivery in the CFR. 17 CFR Part 303 is a proposed new part; it is not in the Code today, per 91 FR 45884.

• This post is informational only and is not legal or tax advice; consult a qualified attorney or compliance professional before acting on any specific situation.

What the proposal would do

The Commission's own abstract sets out four things, and it is worth keeping them separate because they land on different teams.

First, the proposed rule would set forth conditions for covered entities to deliver covered information to covered recipients electronically without first obtaining their affirmative consent, per 91 FR 45884. That full phrase matters. It is not delivery "without consent" and not delivery "without permission" — the proposal addresses the sequencing of affirmative consent, and a shorthand that drops the word "first" describes something materially different and worse than what the SEC put out.

Second, it would establish conditions under which the Commission would consider delivery requirements under the Federal securities laws to be satisfied by electronic delivery. That is the safe-harbour half of the proposal: not just what a firm may send electronically, but when doing so would count as having delivered.

Third, the Commission is proposing to rescind the rule providing alternative means for registered investment companies to satisfy shareholder report transmission requirements. Fourth, it proposes to amend the rules addressing the dissemination of proxy materials and tender offer materials.

What the abstract does not do is state any of the conditions. It says the proposed rule "sets forth conditions" and "establishes conditions" and stops there. So this page names no notice periods, no formats, no opt-out mechanics, no website-availability requirements and no retention durations, because the Federal Register document does not carry them. Anyone publishing a conditions checklist for Regulation E-Delivery right now is writing fiction. The conditions live in the proposing release, which is what a compliance team should be reading if it intends to comment.

This is also a different rulemaking from the ones about firms filing inward to the Commission. Our note on the electronic submission of materials to the Commission covers filings that travel from a firm to the SEC, and the related extension of compliance dates for electronic submission covers timing on that same inward track. Regulation E-Delivery runs the other direction: information going outward from a covered entity to a covered recipient. Conflating the two produces a plausible answer to the wrong question.

Who would be affected

The honest answer is narrower than most readers want. The proposal turns on three defined terms — covered entities, covered information and covered recipients — and the Federal Register abstract uses all three without defining any of them, per 91 FR 45884. Those definitions are the scoping mechanism of the whole regulation, and they sit in the document itself.

So this page will not hand you a list of firm types. A list would look authoritative and would be an invention, and scope is exactly the thing a compliance officer cannot afford to take on a blog's word. Read the definitions in the proposal.

The one population the abstract does name is registered investment companies, and it names them in a specific connection: the rescission of the rule providing alternative means for registered investment companies to satisfy shareholder report transmission requirements. That is a statement about the rescission, not a statement about who Regulation E-Delivery covers generally.

Inside a firm that turns out to be in scope, the work would land on familiar functions. Compliance owns the interpretation and the decision to comment. Investor-communications and transfer-agency operations own the delivery mechanics and the recipient records. Fund administration owns the shareholder report side. None of them can plan against conditions that have not been adopted, but all of them can read the proposal and say something useful about it while the record is open.

The dates in this record, and which one matters

One row deserves an explicit warning. The Federal Register record for this document carries July 21, 2026 in its effective-date field, and that value is identical to the publication date — the document's own dates text states that this proposal was published in the Federal Register on July 21, 2026, per 91 FR 45884. It is a metadata artifact of how the document was recorded. It is not a date the Commission set for anyone to do anything, and Regulation E-Delivery did not become effective, take effect, or begin to apply on it.

Read the date as the publication date and nothing else. There is no countdown to build here and no compliance calendar to populate. The only date a firm can act on is the close of the comment record, September 21, 2026.

Note also the register of the source's own language: the document says comments "should be received on or before" that date, which is softer than the mandatory phrasing that appears in some other rulemakings. We have not hardened it here, and a reader should not either.

Where the rule would live, and what you can read today

The proposal is scoped to 17 CFR Part 240 and 17 CFR Part 270, both current parts of the Commission's chapter, plus 17 CFR Part 303. That third one is the interesting entry: it is a proposed new part, and it is not in the Code of Federal Regulations today. As of the electronic CFR stamps for title 17 — current to 2026-07-24, with the title last amended 2026-07-20 — Part 303 is simply not there. It is where the regulation would live if adopted.

The practical consequence for anyone researching this: there is no codified text to look up, and a search that returns nothing is returning the correct answer rather than a broken result. The proposal published in the Federal Register is the whole of what exists. 17 CFR Chapter II is the chapter that would host the new part, and it is the right place to watch, but reading it today will not tell you what Regulation E-Delivery says.

Electronic delivery is a records problem before it is a legal one

Whatever conditions the Commission ultimately adopts, if any, the underlying operational question does not change: can the firm show, per recipient and per document, which delivery method was used, when it was sent, what happened to it, and what preference the recipient had on file at that moment? A firm that can answer that today is in a position to evaluate any final rule against its actual practice. A firm that cannot is going to be reconstructing evidence under time pressure later.

That workflow already exists in most firms in some form: capture the delivery preference, execute the delivery, keep proof of what went out and to whom, handle the failures, and retain the record. The proposal would change the conditions attached to parts of that chain. It would not invent the chain. Treating it as prudent operations rather than as a compliance obligation is the accurate framing while the rule is only proposed.

The weak link is almost always the failure path. An electronic delivery that bounces, is undeliverable, or silently fails is the one that later turns into a question nobody can answer, because the bounce landed in a log rather than in front of a person.

Operationalizing the workflow at volume

This is a routing and recordkeeping problem, and it is the kind of thing US Tech Automations is built to sit around. Configured against a firm's own delivery process, a workflow can route a failed electronic delivery to a named person with a due date rather than letting it accumulate in a bounce log, and record for each delivery which method was used, the timestamp, and the operator responsible — so the answer to "what did we send this recipient, how, and when" is a lookup instead of an investigation.

The second piece is keeping delivery preferences attached to the recipient rather than scattered across the systems that happen to touch them. A workflow that treats the preference as a versioned record — what it was, when it changed, who changed it — means a firm can state what preference was on file at the moment of any given delivery, which is the question that actually gets asked. US Tech Automations is the layer around an accountable compliance owner here, not a substitute for one: whether a particular delivery satisfied a requirement under the Federal securities laws is a judgment for the firm and its counsel, and no automation should be making it.

Frequently asked questions

Is Regulation E-Delivery in effect?

No. It is a proposed rule, published at 91 FR 45884, and the Commission has not adopted it. There is no compliance date and no requirement arising from it. A proposal can also be modified, reproposed, or withdrawn before anything is adopted.

When does the comment period close?

Comments should be received on or before September 21, 2026, per 91 FR 45884. That is the date the rulemaking record closes, and it is the only date on this page a firm can act on.

Why does the Federal Register record show a July 21, 2026 date?

Because that is the date the proposal was published in the Federal Register, per 91 FR 45884. The record's effective-date field carries the same value as its publication date, which is a metadata artifact rather than a compliance date. Regulation E-Delivery did not take effect on it, and nothing is required of anyone as of that date.

Who would Regulation E-Delivery apply to?

The proposal turns on three defined terms — covered entities, covered information and covered recipients — and the Federal Register abstract does not define them, per 91 FR 45884. Rather than guess at a list of firm types, read the definitions in the document itself; they are the mechanism that decides scope.

Can I read 17 CFR Part 303 in the CFR today?

No. Part 303 is a proposed new part and is not in the Code of Federal Regulations as of the current electronic CFR stamps for title 17. The proposal in the Federal Register is the entire text that exists. 17 CFR Chapter II is the chapter that would host it.

What would happen to the shareholder report transmission alternative for registered investment companies?

The Commission is proposing to rescind the rule providing alternative means for registered investment companies to satisfy shareholder report transmission requirements, per 91 FR 45884. Because it is a proposal, that alternative is unchanged for now. The abstract does not name the rule being rescinded, so this page does not either.

Which parts of a delivery workflow can be automated without automating the compliance decision?

The mechanical parts: capturing and versioning preferences, executing sends, timestamping, routing failures to a person, and retaining evidence. The judgment calls should not be automated — whether a recipient is in scope, whether a document is covered information, and whether a delivery satisfied a requirement under the Federal securities laws are determinations for the firm and its counsel.

Related guidance

For related financial-services compliance coverage, see our note on Regulation S-P safeguards for customer information. The two inward-submission pages linked earlier — on electronic submission of materials to the Commission and the extension of compliance dates for it — are the boundary against this one: they cover filings going to the SEC, while Regulation E-Delivery concerns information going out to recipients.

Keeping delivery evidence current across recipients and documents is a standing operational function rather than a project that closes, and it is the workflow US Tech Automations packages for compliance and operations teams — see current plans and pricing.

Disclaimer

This article is provided for informational purposes only and does not constitute legal or tax advice. Reading it does not create an attorney-client relationship. Securities regulation is fact-specific, and you should consult a qualified attorney or other qualified professional before acting on any matter discussed here. Every date, citation, RIN, CFR reference, and figure in this post is copied verbatim from the Federal Register and eCFR as of the snapshot date. Nothing is estimated, modeled, or extrapolated. This is not legal or tax advice.

Last reviewed: July 28, 2026.

Source: Federal Register (91 FR 45884); chapter context via eCFR, 17 CFR Chapter II.