Skip to content
Enjoy complimentary data migration when switching from your existing bookkeeper or CPA to Institution.

Choosing a provider

Engage an SEC filing agent with a clear delegation and release process

Separate account authority, document preparation and permission to submit so a filing agent can perform the agreed work while the company retains an understandable approval record.

By Institution5 minute readPublished View sources
In this guide

Define the filings and services the agent will handle

A filing agent may prepare technical documents, assemble exhibits, validate a package or submit an approved filing. State which of those services the company is buying. Identify the filer, forms and expected volume with the appropriate legal and reporting advisers before requesting a proposal.

Separate the decision about what must be disclosed from the work of formatting and submitting it. The engagement should identify the company's advisers and reviewers for content questions. A production provider should not be expected to resolve an unassigned legal or accounting judgment at the submission deadline.

List related work such as Inline XBRL tagging, document conversion and post-submission assistance. Ask which items the agent performs directly, which involve another provider and which require a separate fee. A quoted submission price can be misleading if most preparation work is excluded.

Agree the operating calendar and the information the agent needs before reserving capacity. The company should know when a complete source package is due and what turnaround the agent has actually committed to under the agreement.

Use the supported EDGAR authority model

Confirm the filer's current account setup and the people authorized to manage it. The SEC's EDGAR Next role guidance describes individual roles and individual Login.gov credentials, which should not be shared. Keep access administration separate from the provider's commercial promise to perform filing work.

The SEC describes delegation as giving another EDGAR account authority to file on the filer's behalf. Its guidance says the filer should delegate only to an account with an existing filing agreement and should verify the intended entity. Match the agent's exact account information to the signed relationship before authorizing it.

Name the company owner who can oversee the delegation and the agent contact who coordinates its acceptance. Record the relevant filer and delegated-entity identifiers without placing reusable credentials in the project file. The company should be able to explain why the authority exists and which service it supports.

Ask the agent how it controls the individuals acting under its delegated arrangement. The company may not administer the agent's internal account, but the contract can require clear responsibility, access practices and prompt communication of relevant changes. Review the actual terms with the appropriate advisers.

References: SEC: Understand and manage EDGAR delegation; SEC: Understand EDGAR Next roles

Build a release instruction that identifies the package

Decide who may authorize submission for the company and what evidence the agent must receive. The instruction should identify the filer, form, period where relevant and the exact approved package. A broad email saying go ahead can become ambiguous when several drafts are circulating.

Keep preparation access distinct from permission to submit. The agent may need time to format and validate a draft before the company's review is complete. The workflow should make the pending approval status clear so technical readiness is not mistaken for a release instruction.

Agree how the agent verifies a release instruction through established contacts. Include a backup authorized approver if the company's governance permits one. An unexpected sender or changed contact route should be resolved before a public filing is made.

Address last-minute changes explicitly. If the company replaces an exhibit after approval, require the relevant renewed review and an updated instruction. The final package should not contain a mixture of approved and unreviewed versions simply because the deadline is close.

Define validation and exception handling

Ask the provider to show the technical checks included before submission and the evidence the company receives. Identify who reviews warnings or formatting differences. A completed automated check should inform the release process without substituting for the company's substantive review.

Discuss what happens if the system rejects a submission or the agent identifies an unresolved issue. Name the contacts who can decide whether to correct the package, obtain professional advice or take another authorized step. Keep that escalation route available during the agreed filing window.

Do not let a commercial turnaround target become an instruction to suppress a known problem. The agent should report the condition and its practical effect clearly. The company's qualified advisers should assess any filing obligation or timing consequence in the actual circumstances.

Use a walkthrough or supported test process to confirm the handoffs before the first live assignment. The team should understand where drafts, approvals, validation output and submission status are stored. Avoid experimenting with uncontrolled live submissions merely to test the provider's workflow.

Require evidence of the actual submission outcome

Specify the confirmation and final records the agent will deliver after submission. The company needs to distinguish a package sent by the agent from a filing accepted and available through the relevant SEC process. Retain the applicable identifiers and acknowledgment with the approved source package.

Have the responsible reviewer inspect the resulting filed materials through the appropriate official route. Compare the filer, form, period, exhibits and visible content with the release instruction. This check helps identify a wrong version or missing item while the people involved still have the assignment in view.

Agree how the agent supports a discovered error or later amendment. The contract should define the included assistance, additional fees and communication route. Decisions about the proper regulatory response belong with the company's qualified advisers rather than a generic promise to replace the file.

Preserve a concise submission history. It should connect each attempt and correction to the relevant package and authorization. The record will be more useful than a folder of similarly named drafts if another team must later understand what was filed and why.

Plan the end of the filing relationship

Ask for the final handover of agreed source files, tagged materials, submission records and upcoming commitments. Check that the company or successor can locate and use them before ending the operational arrangement. Separate proprietary production tools from the records the company needs to continue filing.

The SEC's delegation guidance explains that a filer can terminate delegation through the Filer Management dashboard. Coordinate that step with the authorized company administrator once the appropriate handover and remaining assignments are resolved. Review any other access granted for the service as well.

The engagement should leave a clear chain from company-approved disclosure to an identifiable filing outcome. Defined authority and usable records make the agent relationship easier to operate, review and transfer when the company's needs change.

References: SEC: Understand and manage EDGAR delegation

Sources

Requirements and product details can change. Check the linked guidance for the facts that apply to your situation.

Related reading

Need help with this work?

General information, not personalized accounting, tax, legal, or investment advice. Have the appropriate qualified professional review decisions that depend on your circumstances.