Summary

  • Delegating filings to an agent does not automatically give that agent control of the client's account or authority to perform its annual confirmation.
  • An outside professional can separately be appointed as the client's account administrator. The purchasing decision concerns both the work and the powers needed to perform it.
  • The SEC allowed bulk delegation but rejected bulk annual confirmation, preserving a separate review for each filer even when accounts look alike.

There is a useful question to ask a filing agent before buying the comforting phrase “we handle everything”: which person can keep the client's account in working order?

Under EDGAR Next, an agent can be authorised to send a client's filings without being authorised to perform the client's annual account confirmation. Yesterday's successful submission proves the first capability. It says nothing about the second.

The client can buy both jobs from the same firm. But a broad promise on a sales proposal needs a matching, rather more precise grant of authority inside the system. Otherwise an outsourced process contains a task that everybody assumes somebody else owns.

The bulk discount stops at confirmation

The SEC considered making this particular task easier to bundle. During consultation on EDGAR Next, commenters proposed bulk annual confirmation for related accounts with similar administrators, users and information. One operation could cover a portfolio of apparently identical housekeeping jobs.

The commission rejected that approach in its final rule. Information can differ from filer to filer, it explained, and confirming hundreds of accounts together could displace careful review of each one. The unit of confirmation would remain the individual filer.

The same rule allowed bulk delegation and acceptance of multiple invitations, alongside API support for preparatory work. This was a deliberate boundary within automation. Shared tools could organise the work; the statement that a particular account had been checked still needed a particular account behind it.

That distinction matters to the economics of a filing service. Collecting changes and preparing records can benefit from a common system. Reviewing who remains authorised on a client's account requires information about that client. A price based solely on documents transmitted leaves out the unit of work the regulator chose to preserve.

The missing inputs for an actual cost calculation are the firm's administrator hours, missed-confirmation frequency and contracted service scope. Those records determine whether consolidation saves money. The rule supplies a mechanism, not a universal price for forgetting a deadline.

A filing agent wears one hat until given another

According to the SEC's frequently asked questions, EDGAR Next requirements took effect for compliance on September 15, 2025. Legacy access ended. Individuals acting for filers use their own Login.gov credentials, multifactor authentication and an appropriate role. Filing deadlines and disclosure obligations continue under their respective rules.

The roles guide assigns an account administrator authority over people, delegations and annual confirmation, as well as the ability to file. Delegating filing authority to another CIK, such as a filing agent's, creates a narrower relationship.

The agent's own account administrators become delegated administrators for that client. They can file and choose which of their own users will work for the client. Delegation alone does not open the client's dashboard or confer its account-administration powers. Nor does the client manage the agent's employees through the client's own dashboard.

The two organisations are connected without merging their access controls. An agent can be fully capable of submitting the next document and still lack the role needed for the client's annual confirmation.

An employee of that agent can separately become an account administrator for the client. The current EDGAR Filer Manual, Volume I, version 43, sets out the Form ID appointment route. A company appointing someone who is not its employee or an affiliate's employee needs the relevant power of attorney bearing the authorised person's notarised signature. Later invitations made through the dashboard by an existing administrator follow a different route; the final rule did not impose the same notarisation requirement on every subsequent dashboard appointment.

So the annual job can be outsourced. The buyer must commission the right function and authorise the person performing it. A service provider's logo does not tell the client which hat that person is wearing.

Two administrators need not mean two new salaries

The general minimum is two account administrators. Individuals and a precisely defined single-member company may have one. For the latter exception, a single individual must be the sole equity holder, director and officer, or hold the equivalent positions. The exception is narrower than an everyday reference to a company with one owner.

These are authorised roles, rather than a requirement to hire two additional full-time employees. Individuals can hold roles for multiple filers, and outside appointments are permitted. The operating question is whether suitable, authorised people remain available when someone leaves.

Technical administration is another layer. Direct API use brings technical-administrator requirements. A client using a delegated entity's API connection can dispense with its own technical administrators and filer API token where the delegate meets the requirement for two technical administrators. Sharing that infrastructure can remove duplicate technical work.

It still does not confer the client's annual-confirmation role. Where an individual user token is required, the person acting uses the token they generated. A shared connection does not turn the actual operator into an anonymous corporate identity.

A buyer therefore needs to distinguish three useful things: transmitting documents, administering the client's account and supplying the technical connection. One supplier may provide all three. They remain different pieces of the service.

The annual date has its own calendar

The annual-confirmation instructions require a review of whether all people and delegated entities remain authorised and whether the filer's information is accurate. Errors must be corrected before confirmation. Any one of the account administrators can perform it. The general requirement to maintain two administrators does not require two signatures for this operation.

Filers choose March 31, June 30, September 30 or December 31 as their annual date, moving to the next business day when EDGAR is closed on that date. Four choices of quarter-end still amount to one annual obligation.

Doing the job in an earlier quarter can change the next deadline. The SEC's example takes a December 31 deadline confirmed in August: the next confirmation becomes due on September 30 of the following year. The relevant quarter-end has moved. An agent that gets ahead of the work must update next year's diary as well as mark this year's task complete.

Reminders begin six weeks before the deadline. A three-month grace period follows it, with normal access, filing and account actions continuing. If confirmation remains undone at the end of that period, the account is deactivated and fresh access requires Form ID.

Approval preserves the CIK and filing history. Former individual authorisations and delegations cease to be effective; the newly designated administrators must invite people again and establish the necessary delegations. The archive survives. The working organisation around it needs rebuilding.

This makes access recovery more than a password exercise. The work may include a new application followed by a new arrangement of people and permissions. A service contract should make clear who performs it.

The exit clause needs an authorised hand

The delegation guide bases the relationship on an existing filing agreement and tells users to verify the exact CIK, because similar names can identify different entities. One administrator at the invited entity accepts to activate the delegation. Terminating it does not require the other side's acceptance.

That gives the client a practical exit route, provided someone remains authorised to use it. A termination letter cannot click the dashboard controls. Replacing an agent therefore involves both ending a commercial relationship and keeping the capacity to arrange the next one.

The procurement comparison should include preparation, review, corrections, replacement of people and recovery of access. A low submission price answers only one part of that comparison. The less visible work is what allows another submission to happen next year.