The Electronic Data Gathering, Analysis, and Retrieval (EDGAR) system, operated by the U.S. Securities and Exchange Commission (SEC), requires filers to adhere to specific formatting standards when submitting documents. This guide outlines the necessary steps to properly format PDF files for EDGAR filing, ensuring compliance with regulatory requirements.
The objective of this guide is to assist 17(H) filers in formatting PDF files to meet EDGAR's acceptable standards, thereby facilitating smooth submission processes.
Before formatting PDF files for EDGAR, it's crucial to understand two key principles:
Prohibited Content: PDF files submitted to EDGAR must not contain active content such as embedded JavaScript, active external references, document passwords, or security controls. Additionally, no embedded files (text, graphic, or audio) are permitted.
Machine Readability: PDF files must be machine-readable to ensure the text is recognizable by the system.
In most cases, electronically "printing" documents to a PDF from the source application is sufficient for EDGAR submission. Follow these steps to electronically print your document to a PDF:
This method removes active content that may cause issues with EDGAR. Avoid using the "Save as PDF" option, as it may embed additional content.
Adobe Acrobat software (or equivalent) is required for the formatting process. If Adobe Acrobat is unavailable, Google Chrome browser may be used to resolve specific error messages.
Documents may fall into one of three categories based on how they were created and formatted. Follow the respective steps for each category:
These documents are electronically printed or saved as electronic PDF files.
These documents lack machine readability and need special attention.
These documents contain a mix of electronically printed and scanned pages.
Distinguishing between readable and unreadable PDF files is essential. Readable files allow text selection and searchability, while unreadable files may contain scanned images without selectable text.
Common error messages such as invalid file names, Java.lang.NullPointerException, external references, and PDF form data issues are addressed with specific resolutions tailored to each scenario.
Unnecessary documents and security considerations are outlined to streamline the filing process and ensure compliance with EDGAR requirements.
Leave a comment