Skip to main content

EDGAR Next—Improving Filer Access and Account Management

Sept. 8, 2023

EDGAR Next proposing release

On September 13, 2023, the SEC proposed rule and form amendments concerning EDGAR filer access and account management (the "proposing release") that are related to potential technical changes to EDGAR (collectively referred to as "EDGAR Next"). The SEC is seeking comment on the proposing release.  The proposing release was published in the Federal Register on September 22, 2023, and comments are due no later than November 21, 2023.  The release encourages testers to provide feedback on related EDGAR technical functionality. 

On September 18, 2023, the SEC opened to the public a dedicated test environment for filers that reflects the proposed rule and form changes and the related technical functionality set forth in the proposing release (the "EDGAR Next Proposing Beta”).

2021 Request for Comment. Prior to the proposing release, on September 30, 2021, the SEC issued a Request for Comment on Potential Technical Changes to EDGAR Filer Access and Filer Account Management Processes (PDF). As a result, the SEC received comments from and engaged in a dialogue with interested parties, considered feedback from these parties, and gathered additional information about filers’ interactions with EDGAR.

On this page:

Access EDGAR Next Proposing Beta

You may access the EDGAR Next Proposing Beta landing page from September 18, 2023, until March 15, 2024. Registration is not required. 

You must have Login.gov individual account credentials and submit a Proposing Beta Form ID to obtain a Proposing Beta Central Index Key (CIK) number in order to fully test functionality on the EDGAR Next Proposing Beta.

Login.gov individual account credentials

From the EDGAR Next Proposing Beta landing page, follow prompts to Login.gov to create a Login.gov account for testing (or to log into the EDGAR Next Proposing Beta using your existing Login.gov account). Your Login.gov account username and password are your Login.gov individual account credentials. 

Login.gov individual account credentials created to test on the EDGAR Next Proposing Beta are actual Login.gov credentials that will persist and may be used to log in to EDGAR if the SEC adopts the EDGAR Next proposal and Login.gov is specified as the credential provider.

Please use your real name and a valid email address that you can currently access to create the individual account credentials.

Login.gov will automatically redirect you to the dashboard in the EDGAR Next Proposing Beta.

Proposing Beta Form ID and Proposing Beta CIK

On the dashboard, navigate to “Apply for EDGAR Access” and submit a Proposing Beta Form ID as a new filer to obtain a Proposing Beta CIK number for testing.

Step-by-step instructions are provided in Test Cases 1 and 2 linked in the “Courtesy test cases” section below.

Courtesy test cases (PDF)

Test cases (PDF) are available as a courtesy to filers to facilitate testing functionality in the EDGAR Next Proposing Beta. Each test case describes a potential filer action, any pre-conditions to complete the action, the relevant role, test steps, and the expected results.

Note that the CIK number created in Test Case 2 can only be used for testing on the EDGAR Next Proposing Beta. No actual EDGAR CIK account will be created.  

Testers should submit only fictional data on the EDGAR Next Proposing Beta. In particular, do not submit any sensitive personally identifiable information (Sensitive PII) or information that you may wish to keep confidential.

For creation of Login.gov individual account credentials, however, testers should use their real name and a valid email address they can currently access.  

Reporting technical bugs

The EDGAR Next Proposing Beta provides an online form to report technical bugs. Please use this form to report any technical bugs that you encounter during testing, providing as much information as possible.

Do NOT use the technical bug report form to submit comments or technical feedback on the EDGAR Next proposing release. Comments and technical feedback on the proposing release should be submitted through one of the methods described in the EDGAR Next proposing release.

Help desk

A dedicated email help desk is available—Monday – Friday, 9 a.m. – 5:30 p.m. ET—to respond to requests for technical assistance related to the EDGAR Next Proposing Beta.

  • Email EDGARNextBeta@sec.gov

Kick-off webinar for EDGAR Next Proposing Beta

The EDGAR Business Office (EBO) hosted a live kick-off webinar via Webex on September 19, 2023, from 12:00 p.m.to 1:00 p.m. ET, to demonstrate functions on the EDGAR Next proposing beta. The recording of the demonstration is on the SEC's YouTube channel

EDGAR Next API Development Toolkit

An EDGAR Next API Development Toolkit is available to the filing community for additional guidance regarding EDGAR APIs. See the Overview of EDGAR APIs (PDF).

API development support sessions 

EBO is hosting four live EDGAR Next API development support Q&A sessions, specifically for developers, to facilitate discussion and guidance regarding the API Developer Toolkit. EBO invites the filing community’s development teams to attend these open forums for additional information.

EBO-hosted EDGAR Next API development support Q&A sessions

1) September 26, 2023: 12:30 p.m. to 2:00 p.m. ET

2) September 28, 2023: 11:30 a.m. to 1:00 p.m. ET 

3) October 13, 2023: 11:30 p.m. to 12:30 p.m. ET

4) October 26, 2023: 11:30 p.m. to 12:30 p.m. ET

EDGAR Next Proposing Beta release notes

EDGAR Next Proposing Beta Release – September 18, 2023

  • EDGAR Next Proposing Beta go-live, including:
    • Login.gov individual account credentials required to access EDGAR
    • EDGAR Filer Management website updated to include new dashboard functionality to manage filer accounts
    • EDGAR Filing and EDGAR Online Forms websites updated to include “login CIK” so individuals controlling multiple CIKs can choose which CIK will be reflected in accession numbers
    • 424H submission type updated to add front and backend validation involving account administrator
    • Application Programming Interfaces (“APIs”) for EDGAR submission, submission status, and operational status.  See the EDGAR API Development Toolkit.
  • Consult the EDGAR Next Proposing Release for more information.

   

Return to Top