EDGAR Next Frequently Asked Questions

EDGAR Next is a series of updates and improvements to the SEC’s EDGAR (Electronic Data Gathering, Analysis, and Retrieval) system. These changes aim to enhance the security, accessibility, and functionality of the system, making it easier and safer for filers to submit their documents.

All entities and individuals who file documents with the SEC using the EDGAR system will be affected.

• This includes, but is not limited to, public companies (domestic filers and Foreign Private Issuers), Section 16/Form 144 reporting owners, Institutional Advisors, Investment Companies, Asset Backed Security registrants, Co-Registrants, Operating Companies, and Filing Agents.

To file on EDGAR, all existing EDGAR accounts (also referred to as “CIKs” or “filers”) must enroll in EDGAR Next.

Persons associated with filers must access EDGAR with individual credentials from Login.gov and complete multifactor authentication (“MFA”).

The primary goals of EDGAR Next are to improve the security of the filing process, modernize the system’s infrastructure, and provide a more user-friendly experience. These updates address existing gaps in account security and reduce potential risks associated with the filing process.

Prepare – September 30, 2024 – March 23, 2025.

• See ‘Prepare – Between now and March 2025’, for more information.

Enroll – March 24, 2025 – September 12, 2025.

• See ‘Enroll – March – September 2025’, for more information.

Comply – September 15, 2025, and after.

• See ‘Comply – September 15 and after’ for more information.

See this chart to compare current EDGAR and EDGAR Next:

• The CIK will remain the same after enrollment.
• A new CCC will be generated after enrollment. It is imperative to provide the updated CCC to Filing Agents after enrollment.
• The password for a CIK can be reset in the dashboard after enrollment. Passwords will be phased out on September 15, 2025.
• The passphrase and PMAC will be phased out upon enrollment.

In this period, we suggest the following for all CIKs (company, directors, and officers):

• Confirm the:
  • CCC is valid.
  • Passphrase, not the password, is known.
  • EDGAR Point of Contact is valid, and the email inbox is valid (can easily be accessed).
    • Ask your service team to provide an EDGAR Company Profile to review the EDGAR Contact information.
  • See Getting Started with EDGAR Filing for instructions on resetting EDGAR codes.
• Identify who will become the account administrators for each CIK.
  • The company CIK will require two account admins.
  • Director and officer (“D&O”) CIKs only requires one account admin, however we suggest identifying two.
  • If a filer is a D&O of multiple companies, determine which company will enroll on behalf of the filer.
    • See Section 16 Filers section for more details.
• Create Login.gov accounts for each account administrator and any person that interacts with EDGAR.
  • The email address used in creating the Login.gov account must be the same email address that will be used in EDGAR Next. We suggest this is the company email address.
  • See Login.gov instructions here.

We can assist in validating the CCCs, updating EDGAR profiles, and providing instructions for regenerating passphrases.

Enrollment begins and the new Form ID process is required during this period.

• Every existing CIK must complete enrollment during this period.
• Login.gov credentials are required to access the EDGAR Next Filer Management Dashboard on or after 3/24/25.
• The CIK, CCC, and Passphrase are required to enroll each CIK.
  • Power-of-Attorney documentation is not required during enrollment for existing filers (CIKs).
• Upon enrollment:
  • Delegate to your Filing Agent or allow for delegation requests. See Delegation for more details.
  • The CCC is updated automatically. Provide the updated CCC to any other companies that file on behalf of the CIK.
• New filers must complete the Form ID from within the Filer Management Dashboard.
  • Power-of-Attorney documentation is required for the account administrators listed in the Form ID.
    • Power-of-Attorney documentation is not required for an account administrator that is added after the Form ID has been accepted.

See instructions for enrollment, delegation, and Form ID for detailed information.

Every individual that will interact with EDGAR Next, including:

• An Account Administrator of a CIK (e.g., individuals that manage filer codes).
• Any person (User) that presses a ‘file’ button, regardless of the filing platform.
• A Technical Account Administrator.

Individual filers (e.g., reporting owners, Section 16 filers) are not required to have a Login.gov account. The administrator(s) of their CIK must have a Login.gov account.

• Power-of-Attorney (“POA”) documentation is not required during the ‘Enroll’ phase for existing filers.
  • POA documentation is required for the account administrator on the amended Form ID for new CIKs in EDGAR Next.
  • POA documentation is not required for additional account administrators that are added, to the EDGAR Next dashboard, after the Form ID has been approved by the SEC.

If the Section 16 director or officer plans to manage their EDGAR filing codes, then they must register for a Login.gov account.

• The SEC recommends that the email used for Login.gov credentials must correspond to the email the person will use in connection with EDGAR when the EDGAR Next changes are effective.
• We encourage filers to utilize a business email address for EDGAR filings.
  • The email used in the EDGAR Filer Management Dashboard will be visible to others.

Yes, you can have two separate Login.gov accounts.

Enrollment is a streamlined process that allows EDGAR filers to transition to EDGAR Next without completing Form ID, notarizing documents, or presenting a power of attorney to SEC staff. Moreover, enrollment requests are typically processed and effective the same day they are submitted, and enrolled filers may access the optional EDGAR Application Programing Interfaces.

Resource – SEC’s FAQ question 1

Every active CIK must enroll in EDGAR Next. This includes Company, Transfer Agent, Individual (e.g., Section 16 or Beneficial Owners), and Filing Agent CIKs.

Each filer may only enroll once. Therefore, each filer should coordinate carefully with all entities and individuals that may currently be filing on its behalf as soon as possible to determine which entity or individual the filer will authorize to enroll it.

EDGAR filers whose Form ID applications for EDGAR access are submitted and granted by SEC staff on or after March 24, 2025, are immediately subject to the requirements of EDGAR Next and do not need to enroll.

Resource – SEC’s FAQ questions 1 & 2

March 24, 2025 – the new EDGAR Filer Management website will go live.

• Existing filers can begin enrolling on the dashboard.
• New filers must complete and submit the Form ID from the dashboard.
• ABSCOMP submissions must be made through the dashboard.

September 15, 2025 – EDGAR Next compliance required.

• Filers must be enrolled on EDGAR Next to file via EDGAR.
• Late enrollment for existing filers is allowed.

December 22, 2025 – any existing filers, that have not enrolled, must file the amended Form ID to reapply for access to their EDGAR accounts.

Filers must be enrolled on EDGAR Next by September 15, 2025, to file via EDGAR.

Filers that have not enrolled by September 15, 2025, are allowed to enroll until December 19, 2025, without filing a full new Form ID. Filers will be unable to file with EDGAR after September 15, 2025, until their CIK has been enrolled in EDGAR.

Delegation of authority to file on behalf of another filer.

Delegation of authority is made from the EDGAR Filer Management dashboard of the filing CIK to another CIK.

• Any Account Administrator or user, listed within the delegated CIK, will be allowed to transmit a filing on behalf of the filing CIK.

To set delegation authority:

• By Account Administrator, of the filer’s CIK.
  • See step-by-step instructions here.

EDGAR Next allows the filer to delegate to multiple CIKs. Be sure that the delegations have been provided to each filing agent CIK.

• Note – the CCC will automatically be updated upon enrollment. Be sure to alert each filing agent that you have delegated to them and provide them with the updated CCC.

The amended Form ID will be accessed on the EDGAR Next Dashboard.

The EDGAR Next Dashboard can only be accessed by an individual with Login.gov credentials.

The company or individual applying for access codes, and the prospective account administrator(s), must disclose if they have been criminally convicted as a result of a federal or state securities law violation, or civilly or administratively enjoined, barred, suspended, or banned in any capacity (e.g., officer or director bar, prohibition from associating with brokers, dealers, investment advisers, and/or other securities entities, or bar from participation in certain industries), as a result of a federal or state securities law violation.

The amended Form ID will automatically enroll the newly created CIK into EDGAR Next.

Beginning March 24, 2025, any new filer will be required to complete the Form ID from within the EDGAR Next Dashboard.

Beginning December 22, 2025, any existing CIKs that have not yet enrolled into EDGAR Next will be required to complete the amended Form ID from within the EDGAR Next Dashboard.

Yes, the amended Form ID must be signed by an authorized individual of the company and notarized.

Companies must coordinate who will complete the enrollment when a filer is a director for multiple boards/issuers.

• After enrollment, we suggest that an administrator is added to the filer’s account from each Issuer.

Note – The CCC will change upon enrollment. Ensure each company is alerted with the updated CCC.

Corporate staff can enroll the filer/reporting person into EDGAR Next. The filer is not required to have a Login.gov account and/or access to EDGAR Next.

The individual transmitting the test and/or live filing, within a SaaS platform, must:

• Be an administrator or a user of the filer’s EDGAR codes.
  • See ‘Add User(s) in EDGAR Next Dashboard’ for instructions.
• Have Login.gov credentials.
• Generate a ‘user token’ from the EDGAR Next Dashboard.
  • The user token will be placed within the SaaS platform, specific details on where the user token will be placed will vary depending on the platform.
    • The user token expires every 30 days.