Why was my EDGAR submission rejected?

Rejections usually result from format errors, incorrect file naming, missing exhibits, or XBRL validation failures. Review the rejection message, correct the specified issues, and resubmit with updated files and metadata.

Can I use eSignatures on documents for EDGAR?

Yes, electronic signatures are acceptable when they meet legal validity tests (intent, consent, attribution, retention). Retain audit trails and ensure signatory authority is documented before embedding signed documents in EDGAR submissions.

How should XBRL tagging problems be fixed?

Re-run XBRL validation against the correct taxonomy, resolve mapping errors, ensure instance and linkbase consistency, and repackage the corrected XBRL instance with the filing for resubmission.

What authentication is required for automated transmit clients?

Use SEC-approved account credentials, recommended certificate or token-based authentication, and follow account role restrictions to ensure only authorized systems can transmit filings.

How do I file an amendment to a previously accepted filing?

Prepare the amended document using proper amendment form type or amendment flag, ensure exhibits are correctly linked, and submit following the same validation steps; indicate amendment reason where required.

How long should I retain EDGAR submission records?

Keep submission receipts, signed documents, validation reports, and working papers for several years—follow federal guidance (minimum 3 years) and industry-specific retention rules that may extend retention.

Electronic Signature
Templates
Other
EDGAR Filer Manual Volume II

EDGAR Filer Manual Volume II

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

What the EDGAR Filer Manual Volume II Covers

The EDGAR Filer Manual Volume II is the SEC's technical and procedural guide for preparing and submitting electronic filings via the EDGAR system. It describes permitted document types, file naming conventions, required metadata, validation rules, XBRL tagging expectations where applicable, transmission protocols, and post-submission handling. Volume II is focused on the mechanics of file construction, acceptable formats and structure, error codes returned by automated validation, and special instructions for amendments, exhibits, and confidential submissions. Practitioners use it to ensure filings meet SEC format and transmission requirements and to minimize rejections and processing delays.

Why Volume II Matters for Accurate Filings

Following EDGAR Filer Manual Volume II reduces submission errors, accelerates acceptance, and ensures filings meet the SEC's technical format and XBRL expectations. Clear adherence to its rules lowers operational risk and supports consistent, auditable submission workflows.

Who Relies on the EDGAR Filer Manual Volume II

Legal, corporate reporting, and finance teams use Volume II as the technical playbook for EDGAR submissions; IT and vendor partners reference it for integration and transmission rules.

Corporate reporting teams preparing 10-Ks, 10-Qs, 8-Ks, and registration statements who manage content, exhibits, and XBRL tagging.
Securities counsel and compliance officers who verify legal conformity, certification language, and amendment procedures.
Third-party filing vendors and internal IT staff responsible for EDGAR transmission, validation, and automated error handling.

Use the manual alongside SEC filing checklists and business processes to reduce rework and maintain a defensible audit trail.

Core Sections and Features in Volume II

Volume II groups technical requirements into discrete areas that address file formats, metadata, validation, transmission, exhibits, and error handling to support machine-checked submission and auditor-friendly records.

File Formats

Specifies allowed file types (PDF, ASCII, XBRL instance and linkbases), size limits, and encoding rules to ensure the EDGAR parser accepts attachments and primary documents.

Naming Conventions

Defines file and document naming patterns, exhibit headers, and metadata fields so the SEC can index filings consistently and link exhibits to the parent submission.

Validation Rules

Lists client-side and server-side checks, required headers, and common reject codes; following these rules reduces round trips and prevents rejections during the initial intake phase.

XBRL Requirements

Outlines tagging conventions, instance document structure, taxonomy mapping, and embedding guidance so financial statements render correctly and meet SEC XBRL quality checks.

Transmission Protocols

Covers authenticated access, submission endpoints, acknowledgements (receipt and acceptance), and recommended retry logic for resilient automated filing clients.

Amendments & Exhibits

Explains how to file amendments, attach exhibits, submit confidential materials, and link exhibit metadata to maintain continuity across original and amended filings.

Essential Data Elements Required for EDGAR Filings

CIK Number: Unique filer identifier

Company Name: Exact legal name

Form Type: e.g., 10-K, 8-K, S-1

Filing Date: MM/DD/YYYY format

Document Title: Descriptive exhibit title

Contact Information: Phone and email for reviewer

Step-by-Step: Preparing an EDGAR Submission

Follow these sequential steps to prepare a compliant EDGAR submission with minimized validation errors and clear audit trails.

01

Assemble Materials: Gather signed documents, exhibits, and financials.
02

Format Files: Convert to required PDF or XBRL formats.
03

Validate Locally: Run pre-submission checks and XBRL validation.
04

Transmit: Submit through EDGAR endpoint and monitor response.

How to Configure an eSubmission Workflow

Set up a repeatable workflow with defined roles, file checks, and transmission settings to streamline EDGAR submissions and reduce manual errors.

Field	Configuration
Authentication	SSH/secure certificate, account credentials
File Naming	Follow SEC naming conventions
XBRL Tagging	Validate against chosen taxonomy
Delivery Mode	Direct EDGAR endpoint or vendor

Where and How Submissions Are Sent

EDGAR submissions are transmitted to SEC intake endpoints; acceptance is confirmed by a receipt and then processed for acceptance or rejection by automated checks.

Upload: Send files to EDGAR transmission endpoint
Receipt: Receive timestamped submission receipt
Validation: SEC runs automated format checks
Acceptance: System returns accepted or rejected status

Technical and Security Requirements for eSubmission

Use secure transmission methods, authenticated credentials, and deterministic file formats to meet EDGAR acceptance criteria.

Secure Transport: TLS-based channels and approved protocols
Account Controls: Role-based access to filing accounts
Audit Trail: Store submission receipts and logs

When integrating eSignature or third-party tools, ensure the platform supports required file formats, retained audit trails, and secure storage aligned with compliance needs.

Timing and Processing Expectations for Filers

EDGAR filing timing varies by form type and filer classification; plan internal review, signature collection, and pre-submission validation well in advance of statutory deadlines.

Form-Specific Deadlines:

Deadlines depend on form and filer category

Internal Review Buffer:

Allow multiple business days for legal and accounting review

XBRL Quality Checks:

Allocate time for taxonomy validation and corrections

Transmission Window:

Submit before market open for same-day processing

Amendment Handling:

Amendments may require revalidation and reprocessing

Key Processing Stages from Preparation to Acceptance

Track these numbered stages to coordinate teams and monitor progress from draft to SEC acceptance.

01

Stage 1 — Draft and Review

Internal drafting, counsel sign-off, and exhibit collation.

02

Stage 2 — File Preparation

Convert to required formats and apply naming conventions.

03

Stage 3 — Pre-Submission Validation

Run local validation tools and correct flagged issues.

04

Stage 4 — Transmission and Acceptance

Send to EDGAR, capture receipt, and confirm acceptance status.

Common Mistakes That Trigger EDGAR Rejections

Incorrect file naming or metadata that prevents proper indexing and exhibit linking, typically leading to automated rejection.
Unvalidated XBRL instances or missing linkbases that fail SEC taxonomy checks and force manual remediation.
Using non-permitted file formats or oversized attachments that exceed EDGAR limits and cause transmit or parse errors.
Submitting an amendment with mismatched exhibit cross-references or inconsistent revision history, which complicates acceptance and review.

Risks and Consequences of Incorrect or Late Filings

Submission Rejection: Delays processing and public availability

Regulatory Action: Possible SEC inquiries or enforcement

Market Harm: Investor confusion or trading impact

Legal Exposure: Increased litigation risk

Remediation Costs: Time and attorney fees increase

Reputation Risk: Public perception and stakeholder distrust

eSignature Vendor Pricing Overview for EDGAR Workflows

Comparing baseline pricing and common feature availability can help determine which eSignature provider fits filing volume and compliance needs. Pricing shown is vendor-level starting points and plan availability may vary by billing cycle.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day free trial	Varies by vendor	Varies by vendor	Varies by vendor	Varies by vendor
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

Practical Tips to Improve Accuracy and Efficiency

Adopt these practices to reduce rework, speed acceptance, and keep a defensible audit trail for EDGAR filings.

Standardize Templates and Naming

Use approved templates and consistent filename conventions across filings so automated processes can parse exhibits and attachments without manual intervention; this reduces indexing errors and reviewer confusion.

Pre-Validate Locally

Run XBRL and format validation tools before transmission to catch common taxonomy and structure errors that would otherwise cause rejections or delays with the SEC intake system.

Maintain an Audit Trail

Retain timestamps, version history, receipt acknowledgements, and signer metadata for each submission to support compliance reviews and any subsequent regulatory inquiries.

Coordinate Signatures Early

Collect authorized signatures in advance using secure eSignature tools and confirm signer identity to avoid last-minute delays and to ensure signatory authority is documented.

Frequently Asked Questions and Troubleshooting

Answers to common issues encountered when preparing, signing, validating, and submitting EDGAR filings, including eSignature and XBRL concerns.

Need help? Contact support

Why was my EDGAR submission rejected?
Rejections usually result from format errors, incorrect file naming, missing exhibits, or XBRL validation failures. Review the rejection message, correct the specified issues, and resubmit with updated files and metadata.
Can I use eSignatures on documents for EDGAR?
Yes, electronic signatures are acceptable when they meet legal validity tests (intent, consent, attribution, retention). Retain audit trails and ensure signatory authority is documented before embedding signed documents in EDGAR submissions.
How should XBRL tagging problems be fixed?
Re-run XBRL validation against the correct taxonomy, resolve mapping errors, ensure instance and linkbase consistency, and repackage the corrected XBRL instance with the filing for resubmission.
What authentication is required for automated transmit clients?
Use SEC-approved account credentials, recommended certificate or token-based authentication, and follow account role restrictions to ensure only authorized systems can transmit filings.
How do I file an amendment to a previously accepted filing?
Prepare the amended document using proper amendment form type or amendment flag, ensure exhibits are correctly linked, and submit following the same validation steps; indicate amendment reason where required.
How long should I retain EDGAR submission records?
Keep submission receipts, signed documents, validation reports, and working papers for several years—follow federal guidance (minimum 3 years) and industry-specific retention rules that may extend retention.

Explore Templates

Petition for Change of Name Child Name Change Form Orange County NY Notice of Hearing on Petition to Change Name Illinois Minor Name Change Illinois Secured Promissory Note Agent's Certification and Acceptance of Authority Form

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now