Form 8A12BEF Files Dataset

The Form 8A12BEF Files Dataset is a complete EDGAR-sourced collection of short-form Exchange Act registration statements filed under SEC submission code 8A12BEF — Section 12(b) registrations of a class of (typically debt) securities that take effect automatically the moment the form is accepted by EDGAR, with no exchange certification step and no concurrent Securities Act registration required. Each record corresponds 1:1 with an EDGAR accession number and is materialized as a self-contained accession folder bundling one normalized JSON metadata descriptor and the plain-text bodies of the documents that made up the original SGML submission. The filer is the issuer whose class of listed debt securities is being registered, and filings are transactional rather than periodic — one submission per class registered. The dataset's electronic record begins in January 1995, consistent with the mid-1990s phase-in of mandatory EDGAR filing, and continues to the present. Because the BEF effectiveness path is narrow — listed debt of an issuer whose Securities Act posture for the underlying offering is already settled — the population is small and tightly scoped.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset captures every EDGAR submission whose form code is 8A12BEF: a Form 8-A short-form Exchange Act registration filed under Section 12(b) (listed securities), with the General Instruction A(c)(2) election that causes the registration to take effect immediately on filing. The BEF suffix marks exactly that election — the registration takes effect on filing without waiting for exchange certification or for a parallel Securities Act registration statement to reach effectiveness on a different form.

Form 8-A's role is purely registration of the class with the Commission so the issuer becomes subject to Exchange Act reporting and the security may trade on a national securities exchange. It is not an offering document and does not contain a prospectus, financial statements, MD&A, risk factors, or extensive narrative disclosure. Most substantive content concerning the security itself is incorporated by reference to other filings — typically a Securities Act registration statement on Form S-3, a prospectus or prospectus supplement, an indenture, or board authorizing resolutions — and the on-the-page text of the form is short, frequently only a few pages.

The dataset preserves these filings as plain text plus normalized JSON metadata. The file types found in the dataset are TXT and JSON only; image attachments referenced in the original SGML are excluded by dataset policy. Containers are distributed as monthly or yearly ZIP archives grouped under year directories, and every record lives in its own deterministic accession folder inside those archives. Coverage starts at January 1995 and runs to the present; only original 8A12BEF filings are included — amendments are filed under separate submission codes and are outside this dataset.

Content Structure of a Single Record

What one record represents

A single record in the 8A12BEF Files Dataset is one complete EDGAR submission whose form code is 8A12BEF. Each record corresponds 1:1 with an EDGAR accession number and is materialized in the dataset as a single accession folder bundling one normalized JSON metadata descriptor and the plain-text bodies of the documents that made up the original SGML submission.

The on-disk layout is a deterministic transformation of EDGAR's accession number identifier. Monthly ZIP containers are grouped under year directories (for example 1996/1996-11.zip); each ZIP unpacks to a <YYYY>-<MM>/ folder; inside that folder, every record lives in its own subdirectory whose name is the EDGAR accession number with all dashes removed — an 18-digit zero-padded directory name. So accession 0000950115-96-001682 becomes the folder 000095011596001682/, and that folder is the record. The accession folder always contains exactly one metadata.json plus one or more document-<N>.txt files, where <N> is the sequence number assigned to that document in the original EDGAR submission header.

Content layers of a single record

Each record has two clearly delineated content layers that complement each other.

1. A normalized metadata layer — the metadata.json file — that describes the filing at the EDGAR submission level using fields parsed from the SGML header.
2. A document body layer — one or more document-<N>.txt files — that contain the textual content of the registration statement and any attached exhibits, with the SGML <DOCUMENT> wrapper stripped and only the document body preserved.

The two layers are linked by sequence number: the documentFormatFiles array in metadata.json enumerates each document with a sequence value, and the document-<N>.txt files on disk are named by that same sequence, so the semantic role of any text file (primary registration statement vs. specific exhibit) is recovered by joining on the sequence value.

The metadata.json descriptor

metadata.json is a single JSON object whose keys describe the filing at submission granularity. The notable fields are:

• formType — SEC form code, fixed at "8A12BEF" for every record in this dataset.
• accessionNo — canonical dashed accession (for example "0000950115-96-001682"); the on-disk folder name is this value with dashes removed.
• filedAt — ISO-8601 timestamp with timezone offset capturing the EDGAR receipt time.
• description — human-readable form description, typically "Form 8A12BEF - Registrations of certain classes of Securities".
• linkToFilingDetails — URL pointing to the filer's CIK directory on EDGAR.
• linkToTxt — URL of the consolidated SGML/text submission on EDGAR.
• linkToHtml — URL of the EDGAR filing index page (the ...-index.htm file).
• linkToXbrl — URL of XBRL data when present; for 8A12BEF this is essentially always an empty string because debt-class registration on this short form does not carry XBRL.
• id — 32-character hex identifier internal to the dataset.
• documentFormatFiles — array of document descriptors, one entry per <DOCUMENT> block in the SGML submission. Each entry carries sequence, size (bytes, as a string), documentUrl, description, and type. The primary registration statement appears as a type: "8A12BEF" entry. A synthetic "Complete submission text file" entry is also present whose sequence is a single space (" "); that entry has no on-disk counterpart in the accession folder and is a metadata pointer to the consolidated EDGAR-hosted .txt representation.
• dataFiles — array of supplemental data files; effectively always empty for 8A12BEF, since this form does not carry financial-data exhibits.
• seriesAndClassesContractsInformation — investment-company series/class block; populated only for fund filings and effectively always empty for 8A12BEF debt-registration submissions.
• entities — array of entity records associated with the filing. For 8A12BEF the array typically contains a single filer entity. Each entity object exposes the registrant's cik, companyName (with role suffix such as "(Filer)"), type (role-form code), act (Exchange Act section, "34"), fileNo (SEC file number, e.g. "001-09186"), filmNo (SEC film number), irsNo (IRS Employer Identification Number), stateOfIncorporation (two-letter state code), fiscalYearEnd (MMDD), sic (SIC code with description), and tickers (array of stock symbols).

All textual values, including numeric-looking fields such as size, act, fileNo, and filmNo, are emitted as JSON strings; downstream parsers should cast them explicitly.

The document body files

Each document-<N>.txt is the unwrapped text body of one document from the original EDGAR submission. The SGML <DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, and <TEXT> wrapper tags are not retained around the body — only the textual content between <TEXT> and </TEXT> survives. Pagination markers such as <PAGE> that appeared inline within the body text are preserved verbatim. Because filenames are sequence-indexed rather than carrying the original <FILENAME> value, the role of each text file (registration statement vs. exhibit) must be resolved through the corresponding entry in metadata.json.documentFormatFiles.

document-1.txt contains the Form 8-A registration statement itself, organized in the order in which the form is laid out:

• Cover page banner. The opening lines reproduce the document head used on the SEC's published form: a centered SECURITIES AND EXCHANGE COMMISSION heading, the Washington, D.C. 20549 city line, and the form title FORM 8-A. The form heading on the page does not carry the BEF suffix; the BEF distinction lives in the EDGAR submission code, not in the printed cover.
• Registrant identification block. The exact name of the registrant as specified in its charter, the state or other jurisdiction of incorporation or organization (rendered as a two-letter or short jurisdiction code), the IRS Employer Identification Number, and the registrant's principal executive office address.
• General Instruction A(c) checkbox election. A two-option checkbox that selects between A(c)(1) (delayed effectiveness pending exchange certification or Securities Act registration effectiveness) and A(c)(2) (immediate effectiveness on filing). For 8A12BEF filings A(c)(2) is the elected path — the BEF code reflects exactly that choice.
• Section 12(b) listing table. A two-column table listing, for each class to be registered, the title of the class on the left and the name of the national securities exchange on which it is to be listed on the right. For debt-class registrations the title typically reads as a coupon-and-maturity description (for instance 8 3/4% Senior Subordinated Notes due 2006) and the exchange line names the exchange of intended listing (for instance [New York Stock Exchange](https://www.nyse.com/index)).
• Section 12(g) header. A second header line for any classes to be registered under Section 12(g); for 8A12BEF debt registrations under Section 12(b) this is generally marked Not Applicable or None.
• Item 1 — Description of Registrant's Securities to be Registered. A short narrative item that, in 8A12BEF filings, almost universally incorporates by reference to the description of the debt security in a separately filed Securities Act registration statement (typically a Form S-3 or its prospectus and prospectus supplement) or to the indenture. The item is rarely written out in full on the form itself.
• Item 2 — Exhibits. A numbered list of exhibits filed with the registration statement. For listed-debt 8A12BEF filings the exhibits routinely consist of the indenture governing the notes, any supplemental indenture, the form of note, and the authorizing resolutions of the registrant's board — frequently incorporated by reference to a contemporaneous or earlier filing rather than physically attached.
• Signature block. A section captioned SIGNATURE (or SIGNATURES) containing the certification line, the registrant's name, the execution date, and the typed name and title of the duly authorized officer who signed, prefixed by the conventional /s/ electronic-signature notation.

Where exhibits are physically attached rather than incorporated by reference, they appear as additional document-2.txt, document-3.txt, and so on — one text file per <DOCUMENT> block in the underlying SGML submission. Common attached-exhibit content for this form includes the indenture text, the form of note, supplemental indentures, and authorizing board resolutions; their description and type in documentFormatFiles distinguish them.

Included content

A record packages: the parsed submission-level metadata as metadata.json; the textual body of the registration statement as document-1.txt; and the textual bodies of any further documents (additional exhibits) as sequentially numbered document-<N>.txt files. The folder is self-contained — no shared resources sit outside it — and metadata.json is always present, never absent.

Excluded or separate content

• Image attachments referenced from the original EDGAR submission are excluded; the file types found in the dataset are TXT and JSON only.
• The synthetic "Complete submission text file" entry in documentFormatFiles (with sequence set to a single space) is a metadata pointer to the consolidated .txt representation hosted on EDGAR and has no corresponding file on disk inside the accession folder.
• SGML wrapper tags around the document bodies (<DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, <TEXT>) are stripped during normalization; consumers needing the wrapper-level header values must read them from documentFormatFiles rather than scanning the text files.
• Materials incorporated by reference — Form S-3 registration statements, prospectuses, indentures, prior exhibit filings, board resolutions filed in earlier filings — are not bundled into the 8A12BEF record and must be retrieved from the referenced filings.
• Amendments to a Form 8-A are filed under separate amendment submission codes (8-A12B/A and similar) rather than under 8A12BEF, so amendment records are outside this dataset; every record here is an original filing.

Structural changes over time

The 8A12BEF submission code has had a stable form definition since EDGAR began accepting these filings. The cover page, the A(c) checkbox election, the 12(b) and 12(g) listing tables, Item 1, Item 2, and the signature block are essentially unchanged from 1995 onward. What has shifted modestly is exhibit-citation practice — modern filings are more likely to incorporate by reference to specific accession numbers and exhibit numbers rather than to filing dates alone, reflecting EDGAR's maturation. The practical content has otherwise remained narrow because the form's purpose — automatic-effectiveness registration of a listed debt class — does not invite broader disclosure.

Format notes

8A12BEF filings have been transmitted to EDGAR as plain-text SGML submissions throughout the dataset's coverage window, and the dataset preserves them as plain text. HTML versions are uncommon for this short instrument because the form body is brief and incorporates most substance by reference, leaving little benefit to richer markup. The dataset's TXT-plus-JSON representation therefore captures essentially the full informational content of the filing as the issuer transmitted it.

Interpretation and extraction notes

• The on-disk accession folder name is a deterministic transformation of metadata.json.accessionNo (dashes removed), so joins between folder paths and metadata records are trivial.
• Document filenames are sequence-indexed and not the original EDGAR <FILENAME>, so the semantic role of any document-<N>.txt (primary registration statement, indenture exhibit, board resolution, etc.) must be recovered by matching <N> to the sequence field of the corresponding entry in documentFormatFiles.
• Heavy use of incorporation by reference is the norm for both Item 1 and Item 2; readers seeking the actual description of the security or the actual indenture must follow references to prior Securities Act registration statements or earlier exhibit filings, which are not bundled into the 8A12BEF record.
• Pagination artifacts such as <PAGE> markers remain inline in the text bodies and may need to be filtered when computing line- or word-level metrics or when running text-extraction pipelines.
• Numeric-looking metadata values (size, act, fileNo, filmNo, cik, irsNo, fiscalYearEnd) are encoded as JSON strings; downstream parsers should cast them explicitly.
• The entities array is generally a single filer entity; multi-entity filings are rare for this short, single-issuer registration form.
• The synthetic "Complete submission text file" entry in documentFormatFiles should be filtered out when iterating over real document files — it is identifiable by its single-space sequence value and the absence of a matching document-<N>.txt on disk.

Who Files or Publishes This Dataset, and When

Who files the record

The filer is the issuer whose class of securities is being registered. Form 8-A is the short-form registration statement under Section 12 of the Securities Exchange Act of 1934, available to issuers that already file Exchange Act reports or that are concurrently becoming Exchange Act reporting through a Securities Act registration. The "8A12BEF" variant narrows that path to:

• a registration under Section 12(b) (securities listed on a national securities exchange), and
• the subset of those Section 12(b) registrations that are eligible to become effective immediately upon filing.

In practice, the filers in this dataset are typically:

• Existing Exchange Act reporting issuers listing a class of debt securities (notes, debentures, bonds, or similar fixed-income instruments) on a national securities exchange.
• Issuers whose underlying debt offering is already registered or exempt under the Securities Act of 1933, so Section 12 effectiveness does not need to wait for a concurrent Securities Act registration to go effective.
• Occasionally, finance subsidiaries, banks, and foreign or supranational issuers of listed debt that meet the conditions for the BEF mechanism.

The "registrant" on the cover is the legal entity whose securities are being registered. Underwriters, the listing exchange, the indenture trustee, guarantors, and holders are not filers of Form 8A12BEF; they may be named or described in the registration statement but bear no Section 12 registration duty through this submission type.

Regulatory mechanics: Section 12(b) and the "EF" suffix

Section 12(b) of the Exchange Act requires that any security listed on a national securities exchange be registered with the Commission. Form 8-A is the short-form vehicle for that registration: it incorporates the issuer's existing Exchange Act disclosure record by reference and adds a description of the class being registered, plus the instruments defining holders' rights.

The submission type encodes three pieces of information:

• "12B" identifies a Section 12(b) (exchange-listing) registration, as opposed to "12G" for Section 12(g) registration of a class not listed on an exchange.
• "EF" stands for Effective on Filing. In a standard 8-A12B, Section 12(b) registration becomes effective only when the listing exchange certifies approval to the Commission, or upon concurrent effectiveness of a related Securities Act registration statement, whichever applies. Under the EF variant, the registration becomes effective automatically at the moment the form is accepted on EDGAR — no exchange certification message and no Securities Act registration triggering event is required.
• The absence of an "/A" indicates an initial registration rather than an amendment.

The EF mechanism is therefore available only when the conditions for immediate effectiveness are met (most commonly, listed debt of an issuer whose Securities Act posture for the underlying offering is already settled).

What triggers the filing

Form 8-A is not periodic. It is transactional and registration-driven: one record exists for each class of securities being registered. The 8A12BEF is triggered when:

• the issuer has decided to list a class of (typically debt) securities on a national securities exchange, and
• the registration is structured to take effect on filing rather than on later exchange certification or concurrent Securities Act effectiveness.

There is no fixed deadline. The filing is timed to the listing event: the issuer files at or before the moment Section 12(b) registration must be effective for the securities to begin trading on the exchange. Because effectiveness is automatic, there is no waiting period between EDGAR acceptance and registration taking effect. After registration, the issuer continues its ongoing Exchange Act reporting (10-K, 10-Q, 8-K or the foreign-issuer equivalents) under whatever regime already applies.

An issuer may file multiple 8-A submissions over its life — one per class registered under Section 12 — using different suffixes (12B, 12B/A, 12BEF, 12G) depending on the section, the effectiveness mechanism, and whether the filing is an initial registration or amendment.

Historical reach

Section 12 of the Exchange Act has required registration of exchange-listed securities since 1934, and Form 8-A (with the BEF mechanism for automatic effectiveness) is the Commission's short-form implementation of that obligation for issuers already in the Exchange Act reporting system. The EDGAR-era electronic record of Form 8A12BEF filings in this dataset begins in January 1995, consistent with the mid-1990s phase-in of mandatory electronic filing, and continues to the present.

How This Dataset Differs From Similar Datasets or Filings

Form 8A12BEF lives inside the Form 8-A family of Exchange Act registration filings. The most useful comparisons are its direct siblings (8-A12B, 8-A12G, 8-A12B/A) and the Securities Act and Trust Indenture Act filings (S-1/S-3, F-1/F-3, T-1/T-3) that often surround a debt listing. The single mechanic that sets 8A12BEF apart from every one of these is its automatic effectiveness on filing, with no exchange certification and no concurrent Securities Act registration required.

Form 8-A12B (standard Section 12(b) registration)

The nearest sibling. Same statutory basis (Section 12(b)), same short structure (issuer identification, class description, listing exchange, exhibits defining holder rights), and the same purpose of registering a class for an exchange listing.

The decisive contrast is effectiveness:

• Form 8-A12B does not become effective on filing. It becomes effective only when the listing exchange certifies approval to the SEC, and only if a Securities Act registration statement covering the same securities is on file or simultaneously effective.
• 8A12BEF (the "EF" denotes "effective on filing") becomes effective the moment it is submitted, with no exchange certification step and no companion Securities Act registration.

8-A12B is the high-volume default across both equity and debt. 8A12BEF is reserved for the narrow class of listed debt securities that qualify for this streamlined path.

Form 8-A12G (Section 12(g) registration)

Same form family, different statute. Form 8-A12G registers under Section 12(g), which is triggered by asset and shareholder thresholds rather than an exchange listing. There is no listing exchange and therefore no certification step at all. Compared to 8A12BEF:

• Different trigger: size thresholds, not a listing event.
• Different market context: typically OTC or widely held, not exchange-listed.
• Different effectiveness logic: 12(g) registration follows its own statutory timing and is unrelated to the EF path.

The two are not substitutes; they sit on different statutory tracks.

Form 8-A12B/A (amendment)

The "/A" suffix amends a previously filed 8-A submission to correct, supplement, or update the original registration. It is not a new registration event and only makes sense relative to a primary 8-A filing already on record. For a researcher tracking newly registered debt classes through the 8A12BEF dataset, /A filings should be treated as a separate stream that modifies prior records rather than creating new ones. The 8A12BEF Files Dataset captures only filings tagged with the BEF submission type code.

Form 8-A12B(T) (temporary registration)

The "T" suffix marks a temporary registration used for corporate restructurings, successor-issuer situations, or transitional listings where a permanent 8-A is expected to follow. Like 8A12BEF, it is a low-volume member of the 8-A family. Unlike 8A12BEF, its distinguishing trait is duration, not automatic effectiveness; it still relies on standard 8-A12B effectiveness mechanics.

Forms S-1 and S-3 (domestic Securities Act registration)

Different statute, different stage of the lifecycle. Form S-1 and Form S-3 register the offering and sale of securities under the Securities Act of 1933; the 8-A family registers the resulting class under the Exchange Act for listing purposes. S-1/S-3 filings are long-form documents containing prospectuses, financial statements, MD&A, risk factors, and underwriting details. An 8A12BEF filing is a short administrative record by comparison.

Crucially, the standard 8-A12B path presumes an S-1/S-3 (or equivalent) is on file or concurrently effective. 8A12BEF does not. The absence of any required Securities Act registration is precisely what defines the EF path.

Forms F-1 and F-3 (foreign private issuer Securities Act registration)

The foreign private issuer analogs of S-1/S-3. They appear next to 8-A filings when foreign issuers list on US exchanges. The same logic applies: Form F-1/Form F-3 register the offering; the 8-A family registers the class. 8A12BEF has historically been used by certain foreign debt issuers whose securities qualified for the streamlined effective-on-filing path, but the F-1/F-3 and the 8A12BEF remain complements covering different statutes, not substitutes.

Forms T-1 and T-3 (Trust Indenture Act)

Form T-1 is the indenture trustee's statement of eligibility; Form T-3 is the application for qualification of an indenture where no Securities Act registration is required. Because 8A12BEF registers listed debt classes, related offerings often carry associated T-1 (and occasionally T-3) filings. The overlap is contextual, not substantive: T-1/T-3 address trustee eligibility and indenture qualification; 8A12BEF addresses Exchange Act registration of the class. T-1 filings can be useful for identifying the trustee and indenture referenced in 8A12BEF exhibits, but they do not duplicate or replace the 8-A record.

Boundary summary

The 8A12BEF Files Dataset is defined by the intersection of three narrow conditions:

1. Section 12(b) registration of a class to be listed on a national exchange.
2. Debt securities qualifying for the streamlined path.
3. Automatic effectiveness on filing, with no exchange certification and no concurrent Securities Act registration.

Drop any one condition and the filing belongs elsewhere:

• Remove the automatic effectiveness — 8-A12B (requires exchange certification plus concurrent S-1/S-3 or F-1/F-3).
• Switch to Section 12(g) — 8-A12G.
• Amend a prior filing — 8-A12B/A.
• Move to the offering side — S-1/S-3 or F-1/F-3.
• Move to indenture qualification — T-1/T-3.

For broad debt-listing coverage, 8A12BEF must be combined with 8-A12B; on its own, it is the complete and clean capture of one specific procedural path — Exchange Act class registration that takes effect the instant it is filed.

Who Uses This Dataset

Because the form is short, structurally consistent, and rare, the dataset serves targeted legal, fixed-income, and compliance workflows rather than broad market signal extraction.

Securities and Capital-Markets Attorneys

Counsel to debt issuers, indenture trustees, and underwriters use the dataset as a precedent library when structuring 12(b) registrations that do not need a parallel Securities Act filing. They focus on the registration-statement body, the class description, the named listing exchange, and exhibits defining holder rights. Output: drafting precedent files, listing-eligibility memos, and opinions on whether 8A12BEF is the correct 8-A variant.

Corporate Paralegals and EDGAR Filing Specialists

Filing teams at law firms and in-house legal departments use accepted filings as templates when preparing new 8A12BEF submissions. They rely on the header metadata (CIK, accession number, period of report), the cover-page registrant block, the listing-exchange field, and the exhibit index to build internal style guides and QC checklists.

Fixed-Income Research Analysts

Sell-side and buy-side credit analysts use the filings to detect when a specific class of debt moves onto a national exchange. The relevant fields are CIK, SIC, registrant name, debt-class description, listing exchange, and filing date. Feeds issuance histories, listed-debt inventories, and timelines linking registration to secondary-market activity.

Credit Rating Analysts

Analytical staff at rating organizations use 8A12BEF records to confirm the existence, listing status, and basic terms of a registered debt class, and to pull indenture or supplemental-indenture exhibits. Supports issuer file-building, surveillance updates when a class becomes exchange-listed, and reconciliation against issuer-supplied capital-structure data.

Exchange Listing and Issuer Compliance Officers

Listing-compliance staff at national exchanges and at issuers preparing to list use the dataset to study how 12(b) debt registrations have been documented. They focus on the listing-exchange field, class description, and rights exhibits to support eligibility reviews and reconciliation between exchange listing applications and EDGAR filings.

Treasury and Capital-Markets Teams at Issuers

Treasury and DCM staff at corporate, financial, and sovereign issuers consult prior 8A12BEF filings from comparable issuers when planning a new listed debt program. They examine timing relative to issuance, class description language, and the form of the rights instrument attached as an exhibit to inform internal decision memos and the operational sequence from board authorization to EDGAR submission.

Regulatory Data Engineers

Data teams at compliance vendors, regulatory-analytics providers, and market-data firms ingest the metadata JSON (CIK, SIC, accession, filing date, form type, ticker) and parse the registration text for registrant, class, and listing exchange. Feeds normalized issuance tables, master-security databases, and lineage tools that link a debt instrument back to its initiating Exchange Act registration.

Academic Finance and Legal Researchers

Researchers studying Section 12(b) debt registration and automatic-effectiveness form usage use structured metadata for sample construction and document text for content analysis of class descriptions and rights instruments. Supports empirical work on listed-debt market structure and disclosure practice.

LLM and RAG Developers for Regulatory Filings

Teams building retrieval and extraction systems on EDGAR text use the 8A12BEF corpus as a narrowly scoped, clean form-type slice. Full document text, exhibits, and metadata support form-type classifiers, extraction models for registrant and class fields, and retrieval indexes that distinguish 8A12BEF from other 8-A variants.

Across these users, the recurring fields are registrant metadata, debt-class description, listing exchange, and rights-defining exhibits, each supporting concrete drafting, monitoring, modeling, or research workflows.

Specific Use Cases

The Form 8A12BEF Files Dataset supports a small set of focused workflows in legal drafting, fixed-income tracking, compliance reconciliation, and regulatory data engineering. Each use case below ties to specific record fields or document sections.

1. Building a precedent library for effective-on-filing debt registrations

Securities counsel drafting a new 12(b) listed-debt registration pull document-1.txt files across the dataset to compare cover-page registrant blocks, the General Instruction A(c)(2) checkbox election, and the Item 1 / Item 2 incorporation-by-reference language. Filtering on entities[].sic and entities[].stateOfIncorporation narrows precedents to comparable issuers. Output: a clause bank and a model 8A12BEF shell mapped to specific accession numbers.

2. Identifying newly exchange-listed debt classes

Fixed-income analysts iterate the dataset by filedAt and extract the Section 12(b) listing table from document-1.txt to capture the title-of-class string (for example 8 3/4% Senior Subordinated Notes due 2006) and the named listing exchange (NYSE, AMEX, etc.). Joined to entities[].cik, companyName, and tickers, this produces a chronologically ordered listed-debt inventory feeding issuance histories and secondary-market timing studies.

3. Reconciling capital-structure records against issuer disclosures

Credit rating analysts and master-security data teams use entities[].cik, irsNo, fileNo, and the parsed coupon-and-maturity description from the 12(b) listing table to confirm the existence, terms, and listing venue of a registered debt class. The documentFormatFiles array is filtered on type to locate any attached indenture or supplemental-indenture exhibits, which are pulled from document-<N>.txt to validate trustee, covenant, and ranking fields against issuer-supplied capital-structure tapes.

4. Linking 8A12BEF filings to their referenced S-3, indenture, and T-1 records

Because Item 1 and Item 2 routinely incorporate by reference, regulatory data engineers parse document-1.txt for accession-number citations and prior-filing references, then resolve those to S-1/S-3, prior 8-A, T-1, and exhibit filings using the issuer's CIK directory at linkToFilingDetails. This builds a lineage graph from the listed debt class back through its Securities Act registration and indenture qualification, populating cross-form security-master and disclosure-lineage tables.

5. Training form-type classifiers and field extractors on a clean 8-A slice

LLM and RAG teams use the dataset as a narrowly scoped corpus where every record has formType == "8A12BEF". The deterministic accession-folder layout and the documentFormatFiles.sequence join to document-<N>.txt make it straightforward to label primary-registration text vs. exhibit text. Supports training extractors for registrant name and address, jurisdiction code, IRS EIN, listing exchange, and class description, and discriminative classifiers separating 8A12BEF from 8-A12B, 8-A12G, and 8-A12B/A.

6. Monitoring exchange-listing compliance and amendment activity around an issuer

Listing-compliance staff combine the 8A12BEF record (CIK, fileNo, listing-exchange field from the 12(b) table) with downstream 8-A12B/A amendments filed under separate submission codes to verify that the registration captured in EDGAR matches the exchange's listing application. The filedAt timestamp anchors the registration event for reconciliation against board-authorizing resolutions cited in Item 2 and against the exchange's own listing-approval date.

Dataset Access

The dataset is accessible through a JSON index endpoint that exposes dataset-level metadata and per-container download links, a single archive URL for the complete dataset, and direct URLs for individual container files.

Dataset Index JSON API: https://api.sec-api.io/datasets/form-8a12bef-files.json

This endpoint returns metadata about the dataset (name, description, last update timestamp, earliest sample date, total records, total size, covered form types, container format, and file types) along with the full dataset download URL and a list of all container files. Each container entry includes its key, size, record count, last update timestamp, and individual download URL. Poll this endpoint to detect which containers were updated in the most recent refresh and decide which ones to re-download. No API key is required to access this endpoint.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-6a20-ad35-a0b755d6e10e",
        

          3
            "datasetDownloadUrl": "https://api.sec-api.io/datasets/form-8a12bef-files.zip",
        

          4
            "name": "Form 8A12BEF Files Dataset",
        

          5
            "updatedAt": "2026-04-16T08:29:09.255Z",
        

          6
            "earliestSampleDate": "1995-01-01",
        

          7
            "totalRecords": 125,
        

          8
            "totalSize": 857149,
        

          9
            "formTypes": ["8A12BEF"],
        

          10
            "containerFormat": "ZIP",
        

          11
            "fileTypes": ["TXT", "JSON"],
        

          12
            "containers": [
        

          13
              {
        

          14
                "downloadUrl": "https://api.sec-api.io/datasets/form-8a12bef-files/1995/1995.zip",
        

          15
                "key": "1995/1995.zip",
        

          16
                "size": 124583,
        

          17
                "records": 18,
        

          18
                "updatedAt": "2026-04-16T08:29:09.255Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

Download Entire Dataset: https://api.sec-api.io/datasets/form-8a12bef-files.zip?token=YOUR_API_KEY

Use this URL to download the complete dataset as a single ZIP archive containing all Form 8A12BEF filings from January 1995 to present. This endpoint requires an API key.

Download Single Container: https://api.sec-api.io/datasets/form-8a12bef-files/1995/1995.zip?token=YOUR_API_KEY

Use container URLs from the index API response to download one archive at a time instead of the full dataset. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers SEC submission code 8A12BEF — Form 8-A short-form registration statements filed under Section 12(b) of the Securities Exchange Act of 1934 with the General Instruction A(c)(2) election that causes the registration to take effect immediately on filing. Every record in the dataset has formType == "8A12BEF"; standard 8-A12B, 8-A12G, and 8-A12B/A filings are not included.

What does one record in this dataset represent?

One record is one complete EDGAR submission corresponding 1:1 with an EDGAR accession number. On disk the record is an accession folder named after the accession number with dashes removed; inside the folder are exactly one metadata.json descriptor and one or more document-<N>.txt files containing the unwrapped text of the registration statement and any attached exhibits.

Who is required to file Form 8A12BEF?

The filer is the issuer whose class of securities is being registered under Section 12(b) for listing on a national securities exchange, where the conditions for immediate effectiveness on filing are satisfied. In practice the filer base is dominated by existing Exchange Act reporting issuers listing a class of debt securities (notes, debentures, bonds), along with finance subsidiaries, banks, and certain foreign or supranational debt issuers. Underwriters, the listing exchange, indenture trustees, guarantors, and holders are not filers.

When does the registration become effective?

Under the BEF (Effective on Filing) variant, registration takes effect automatically the moment the form is accepted on EDGAR — no exchange certification message and no concurrent Securities Act registration triggering event is required. This is the single mechanic that distinguishes 8A12BEF from the standard 8-A12B path, where effectiveness depends on exchange certification of listing approval or on concurrent effectiveness of a Securities Act registration statement.

What time period does the dataset cover?

The dataset's electronic record begins in January 1995, consistent with the mid-1990s phase-in of mandatory EDGAR filing, and runs to the present. The 8A12BEF submission code has had a stable form definition over the entire window.

What file format is the dataset distributed in?

The dataset is distributed as ZIP container archives organized by year, with monthly ZIP files inside year directories. Each ZIP unpacks into per-accession folders containing one metadata.json and one or more document-<N>.txt files. The file types found in the dataset are TXT and JSON only; image attachments referenced in the original SGML submissions are excluded by dataset policy.

How does this dataset differ from the 8-A12B dataset?

Both register a class of securities under Section 12(b) for exchange listing. The decisive difference is effectiveness: 8-A12B becomes effective only on exchange certification of listing approval or on concurrent Securities Act registration effectiveness, while 8A12BEF becomes effective on filing. 8-A12B is the high-volume default across both equity and debt; 8A12BEF is reserved for the narrow class of listed debt securities that qualify for this streamlined path. For complete coverage of debt listings, 8A12BEF must be combined with 8-A12B.