Form 8-B12G Files Dataset

The Form 8-B12G Files Dataset is the complete EDGAR corpus of Form 8-B12G registration statements and Form 8-B12G/A amendments — the abbreviated registration filings through which a successor issuer formally inherits a predecessor company's reporting obligation under Section 12(g) of the Securities Exchange Act of 1934. One record corresponds to one EDGAR accession: the parsed submission header packaged as metadata.json, plus every textual document in the original submission (the registration statement and any in-line exhibits) named by EDGAR sequence number. Filings are submitted by successor issuers — newly formed parent holding companies, surviving corporations in mergers, reincorporated entities, or consolidations — after they succeed to a Section 12(g)-registered predecessor through a transaction within the scope of Rule 12g-3. The dataset covers all Form 8-B12G and 8-B12G/A filings on EDGAR from July 1994 to present, distributed as monthly ZIP containers organized by calendar year.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset packages every Form 8-B12G and Form 8-B12G/A submission carried by EDGAR from July 1994 forward. Form 8-B is the registration statement used by a successor issuer to register a class of securities under the Securities Exchange Act of 1934 when that issuer has succeeded to the reporting obligations of a predecessor company through a merger, consolidation, holding-company reorganization, or comparable transaction. The "12G" suffix denotes registration under Section 12(g) of the Exchange Act — the over-the-counter provision — as distinct from Section 12(b) registration for exchange-listed securities (Form 8-B12B). Form 8-B12G/A is the amendment variant: it revises or supplements a previously filed 8-B12G, typically restating only the items being amended and identifying itself as "Amendment No. N" on the cover page.

The form is short, narrative, and exhibit-heavy. Rather than functioning as a standalone disclosure document, it leans extensively on incorporation by reference to the predecessor's existing Exchange Act filings or to a related Form S-4, joint proxy/prospectus, or Form 10 that already describes the succession transaction and the registrant's securities.

Records are partitioned into monthly ZIP archives. The dataset is delivered as a single top-level ZIP that, when expanded, exposes a year directory for each calendar year of EDGAR filings from July 1994 forward, and inside each year directory a <YYYY-MM>.zip archive for each calendar month. Inside any monthly archive the layout is:

          1
          <YYYY-MM>/<accessionNoNoDashes>/<files>
        

<accessionNoNoDashes> is the accession number written as 18 contiguous digits; the dashed form XXXXXXXXXX-XX-XXXXXX is preserved inside metadata.json (accessionNo) but is not used as a folder name. Each accession folder is self-contained: its metadata.json and its document-<N>.<ext> siblings are everything the dataset distributes for that filing. Form 8-B12G is a low-volume form type, so typical monthly archives hold only a handful of accession folders and many months hold zero or one.

Content Structure of a Single Record

One record in the Form 8-B12G Files dataset is one complete EDGAR submission of either a Form 8-B12G registration statement or a Form 8-B12G/A amendment, packaged as a per-accession folder. The folder is keyed by the 18-digit EDGAR accession number with the dashes removed and holds two kinds of artifacts: a metadata.json object capturing the parsed EDGAR submission header, and the textual documents that constituted the original submission (the registration statement plus any in-line exhibits), each renamed to document-<sequence>.<ext> using the EDGAR sequence number. A record therefore corresponds to one accession number, one filer, and one moment in the registration process — either the initial 8-B12G or one specific numbered amendment.

Files inside one accession folder

Each accession folder contains:

1. metadata.json — exactly one per record, a single JSON object describing the submission header.
2. One or more document-<sequence>.<ext> files corresponding to the documents that were part of the original EDGAR submission, named by EDGAR sequence number. The file-types found in the dataset are TXT and JSON; image attachments from the original submission (GIF, JPG, and similar binaries) are excluded by design, and 8-B12G submissions historically have not carried HTML, PDF, or XBRL payloads, so the body documents are plain ASCII text.

The body TXT files are EDGAR-era plain text. They are not wrapped in the SGML <DOCUMENT>...</DOCUMENT> envelope; that wrapper exists only inside the upstream concatenated complete-submission .txt file on EDGAR, which the dataset references by URL but does not redistribute as a local file. Inside each body TXT, legacy EDGAR pagination is preserved: <PAGE> N markers separate the printed pages of the original document and are useful for reconstructing page boundaries of the as-filed registration statement.

metadata.json shape

The metadata.json object captures the parsed EDGAR header plus the dataset-internal record identifier. The keys carried for an 8-B12G record are:

• formType — exact form type as filed, either "8-B12G" or "8-B12G/A".
• accessionNo — dashed accession number (NNNNNNNNNN-NN-NNNNNN).
• filedAt — ISO-8601 timestamp with timezone offset, marking the EDGAR acceptance moment.
• description — human-readable label, e.g. "Form 8-B12G - Registrations of Securities of certain successor issuers".
• linkToFilingDetails — URL to the EDGAR archive root for the filing's CIK.
• linkToTxt — URL to the original full-submission text file on EDGAR.
• linkToHtml — URL to the EDGAR *-index.htm page for the submission.
• linkToXbrl — empty string for this form type.
• documentFormatFiles[] — one entry per submitted document. Per-entry fields: sequence (string; numeric for individual documents, blank/space for the complete-submission wrapper entry), size (bytes, as a string), documentUrl (upstream EDGAR URL), description (e.g. "FORM 8-B", "EX-3.1", "Complete submission text file"), and type (e.g. "8-B12G", "EX-3.1").
• dataFiles[] — empty array for 8-B12G filings; no XBRL data files attach to this form.
• seriesAndClassesContractsInformation[] — empty array; this field is reserved for fund and contract series identifiers and is not relevant to corporate succession registrations.
• entities[] — header-extracted parties to the submission. For 8-B12G a single entry is typical, the successor issuer in the Filer role. Per-entity fields: companyName (with role suffix such as (Filer)), cik, irsNo, fileNo (SEC file number, typically 000-XXXXX consistent with Section 12(g) registration), filmNo (EDGAR film number), fiscalYearEnd (MMDD), act ("34" for the 1934 Exchange Act), sic (industry code with description), type (form type from the submission header), and tickers[] (ticker symbols when known).
• id — opaque dataset record identifier.

The documentFormatFiles[] array is the index that ties metadata.json to the sibling document-<N>.<ext> files: the sequence value in each entry maps to the <N> portion of the local filename, and the type value (8-B12G, EX-3, EX-4, EX-99, etc.) identifies the role of that document. Note that one entry in documentFormatFiles[] represents the EDGAR complete-submission wrapper itself; that entry carries a blank sequence, a description of "Complete submission text file", and points only to the upstream URL because the wrapper is not redistributed locally.

Body structure of the Form 8-B registration statement

The principal body document — sequence 1, type 8-B12G — is the registration statement itself. Its top matter is a fixed cover-page block identifying the form, the SEC, the statutory authority (Section 12(b) or (g) of the Securities Exchange Act of 1934), the exact name of the registrant, the state of incorporation, the I.R.S. Employer Identification Number, the address and ZIP code of the principal executive offices, and the title of the class of securities being registered. Below the cover page, the body proceeds through the fixed Form 8-B itemization:

• ITEM 1. GENERAL INFORMATION — state and date of incorporation and fiscal year end. A short identification block, often only a few lines.
• ITEM 2. TRANSACTION OF SUCCESSION — the narrative that distinguishes Form 8-B from other registration statements. Identifies the predecessor issuer by name, file number, and CIK and describes the merger, consolidation, holding-company reorganization, or comparable transaction by which the registrant succeeded to the predecessor. Typical content covers the form of consideration (cash, stock, contingent rights), exchange mechanics, and the predecessor's deregistration path (commonly a Form 15 filing terminating the predecessor's Exchange Act registration).
• ITEM 3. SECURITIES TO BE REGISTERED — authorized and outstanding share counts for the class being registered, plus any classes already outstanding. Pinpoints exactly what is being placed on the Section 12(g) register.
• ITEM 4. DESCRIPTION OF REGISTRANT'S SECURITIES — description of rights, preferences, voting powers, and other terms of the registered class. In practice this item leans heavily on incorporation by reference to a contemporaneous Form S-4, joint proxy statement / prospectus, or to the registrant's certificate of incorporation and bylaws filed as exhibits.
• ITEM 5. FINANCIAL STATEMENTS AND EXHIBITS — inventoried list of exhibits filed with or incorporated into the registration statement. Exhibits commonly include the merger or reorganization agreement, the certificate of incorporation, the bylaws, specimen stock certificates, instruments defining the rights of security holders (rights agreements, indentures, debenture forms), inter-company contribution / services / tax-sharing agreements, stock-incentive plans, lists of subsidiaries, and proxy materials. This item often substitutes for a free-standing financial-statement section, since Form 8-B permits incorporation of the predecessor's audited financials by reference rather than restatement.
• SIGNATURE — dated and signed by an officer of the registrant (typically the President, CEO, or CFO), with name, title, and date of execution. The signature block sits on its own page, marked by a <PAGE> paginator and rendered in the ASCII /s/ NAME convention.

When exhibits are filed in-line rather than incorporated by reference, they appear as additional sibling documents in the accession folder — document-2.txt, document-3.txt, and so on — each carrying its own EDGAR type label (EX-3.1, EX-3.2, EX-4.1, EX-99, etc.) in documentFormatFiles[]. When every exhibit is incorporated by reference to other prior filings, the accession folder is single-document: only the registration statement itself is local, and ITEM 5 contains pointers to other Reg. Nos. and CIKs rather than file references.

Included content

A record contains, locally and in full, the parsed submission header (as metadata.json) and every textual document that EDGAR carried in the original submission — the registration statement and any in-line exhibits — under their EDGAR sequence numbers and types. Cover-page metadata (registrant name, state, IRS number, address, class title), all five Items of the Form 8-B body, the exhibit list, and the signature block are present verbatim in the body TXT. Header-derived structured fields (CIK, IRS number, SEC file number, film number, SIC, fiscal year end, tickers, act, filing timestamp, dashed accession number) are present in metadata.json.

Excluded or separate content

Image attachments from the original submission (GIF, JPG, and similar binary files) are excluded by design. The consolidated complete-submission *.txt wrapper — the SGML envelope EDGAR builds by concatenating all document parts — is not redistributed as a local file; the documentFormatFiles[] entry for that wrapper carries an empty sequence and points only to the upstream EDGAR URL. Documents that the registration statement merely incorporates by reference (the predecessor's Form 10-K, related Forms S-4, prior Forms 10, proxy statements, indentures filed under separate accession numbers, etc.) are not part of the record and must be retrieved from their own filings if needed. There are no XBRL data files and no series-and-classes contract entries, consistent with the form's character.

Differences between 8-B12G and 8-B12G/A

The on-disk anatomy is identical for both form types: a per-accession folder with a metadata.json plus EDGAR sequence-numbered documents. The discriminating fields are metadata.json.formType ("8-B12G" vs "8-B12G/A") and the per-entity type value in entities[]. The body document of an amendment carries an "Amendment No. N" line on the cover page and typically restates only the Items being amended along with any newly substituted exhibits, rather than the full five-Item structure. The signature block is re-executed for the amendment. Where an initial 8-B12G is often a single-document accession because every exhibit is incorporated by reference, an amendment frequently exists precisely to add or replace an exhibit and so is more likely to carry sibling exhibit documents in the folder. Amendments do not share an accession number with the underlying initial 8-B12G — each amendment receives its own EDGAR accession — so reconstructing the full amendment chain for a registrant requires grouping records by CIK and SEC fileNo rather than by accession.

Format and structural notes

Throughout the EDGAR era covered by the dataset (July 1994 forward), Form 8-B12G submissions are dominated by plain-text documents. The body TXT files retain the conventions of the early EDGAR ASCII era — fixed-column cover-page layout, <PAGE> N paginators, ASCII signature lines such as /s/ NAME followed by a printed name and title — even in more recent filings. There is no inline XBRL, no HTML conversion, and no PDF rendering carried by these submissions.

<PAGE> markers are page boundaries from the as-filed paginated document, not paragraph or section delimiters. The semantic section boundaries are the ITEM 1. through ITEM 5. headings, which appear in upper case and conventionally on their own line. Issuer-specific variation in heading capitalization, spacing, and the precise wording of item titles ("ITEM 2. TRANSACTION OF SUCCESSION" vs. "ITEM 2. SUCCESSION") is common and should be tolerated by extractors.

Interpretation notes

Because Form 8-B leans so heavily on incorporation by reference, the local body document often does not contain the substantive disclosure a reader might expect: the description of the registrant's securities, audited financials, and even the merger agreement may be available only by following pointers in ITEM 4 and ITEM 5 to other accession numbers and Reg. Nos. The ITEM 5 exhibit list is therefore the most informative structural feature for understanding what additional filings are needed to assemble a complete picture of the succession.

The entities[] array nominally supports multiple parties, but for an 8-B12G filing the typical case is a single Filer (the successor issuer); the predecessor company is identified narratively in ITEM 2 of the body rather than as a structured entities[] entry. Tickers and SIC codes in metadata.json reflect the successor issuer at the time of filing and may differ from the predecessor's classification. The fileNo field in entities[] is the durable identifier that links an initial 8-B12G to its 8-B12G/A amendments — the accession number does not.

Who Files or Publishes This Dataset, and When

Who files

Each record is a Form 8-B12G (or its amendment, 8-B12G/A) filed by a successor issuer to a predecessor company that had a class of equity securities registered under Section 12(g) of the Securities Exchange Act of 1934. The filer is the successor entity itself, filing under its own CIK as the new registrant of record.

Typical successor filers:

• newly formed parent companies created in one-step holding-company reorganizations
• surviving corporations in mergers that absorb a predecessor reporting company
• entities formed through reincorporation in a different state of domicile
• new corporations formed by the consolidation of two or more constituent companies

The predecessor is the subject of the succession, not the filer. Security holders are not filers either; they are merely the parties whose predecessor shares are exchanged for successor shares.

Triggering event

The filing is event-driven. It is triggered by the consummation of a succession transaction — a merger, consolidation, holding-company reorganization, statutory share exchange, or similar transaction — in which the successor acquires the predecessor's business, assets, and outstanding securities.

The relevant statutory and rule framework:

• Section 12(g) is the Exchange Act registration provision for issuers that meet asset and holder thresholds without being listed on a national securities exchange (the over-the-counter / non-listed regime).
• Rule 12g-3 under the Exchange Act provides that when a successor issues securities to holders of a class of Section 12(g)-registered securities of a predecessor, the successor's securities are automatically deemed registered under Section 12(g) by operation of the rule, effective upon succession.

Form 8-B12G is the registration filing the successor uses to formally register and confirm that automatic Rule 12g-3 succession on EDGAR: it identifies the successor as the new registrant, describes the succession transaction, and attaches successor-specific exhibits (charter, bylaws, instruments defining security-holder rights). Rather than re-filing the predecessor's reporting history, the successor incorporates the predecessor's prior Exchange Act filings by reference and adds only succession-specific information.

Filing timing

There is no fixed calendar deadline. The form is filed as soon as practicable after the succession closes, typically contemporaneously with or shortly after the effective date of the transaction. Because Rule 12g-3 makes the successor's registration effective automatically upon succession, the substantive reporting obligation begins at closing; Form 8-B12G aligns the EDGAR record with that statutory effect. From the closing date forward, the successor files 10-K, 10-Q, and 8-K reports under its own CIK.

Amendments (8-B12G/A)

Amendments are filed to correct errors, add or substitute omitted exhibits (e.g., executed charter, bylaws, security-holder instruments), respond to SEC staff comments, or reflect post-closing changes to the successor's organizational documents.

Important distinctions

• 8-B12G vs. 8-B12B. Form 8-B12G is the Section 12(g) variant, used when the predecessor's class was registered under Section 12(g) (over-the-counter / non-listed). The companion Form 8-B12B is used when the predecessor's class was registered under Section 12(b) (listed on a national securities exchange) and the successor's securities will likewise be 12(b)-registered. Successors that will list on an exchange use 8-B12B, not 8-B12G.
• Form S-4 / F-4 transactions. When a succession is effected through a registered exchange offer or merger on Form S-4 (or F-4 for foreign private issuers), the successor typically relies on the S-4 prospectus for issuer disclosure and on Rule 12g-3 (or Rule 12b-3) for automatic Exchange Act succession, often without filing a standalone Form 8-B. This combination has substantially displaced 8-B12G in modern practice.
• First-time registrants. A new issuer registering under Section 12(g) on its own merits, with no predecessor, files Form 10, not 8-B12G.
• Foreign private issuers. FPI successors registering under Section 12(g) without an exchange listing generally use Form 20-F as a registration statement rather than 8-B12G.
• Predecessor identity. The 8-B12G is filed under the successor's CIK; the predecessor appears in the substantive disclosure but is not the filer of record.

Why the dataset is small

The corpus reflects the form's narrow niche: a 12(g)-registered predecessor must succeed to a non-listed successor through a transaction not already handled via an S-4 prospectus. Pre-EDGAR paper filings on this form are not in the electronic corpus.

How This Dataset Differs From Similar Datasets or Filings

Form 8-B12G occupies a narrow cell of Exchange Act registration: succession-driven, Section 12(g) (over-the-counter) registration by a successor issuer that inherits a predecessor's reporting status. Several adjacent forms touch the same transaction or the same statutory pathway but are not interchangeable.

Form 8-B12B — sibling form, Section 12(b) pathway

The direct counterpart to 8-B12G. Same trigger (corporate succession under Rule 12g-3), same abbreviated disclosure (predecessor identification, succession description, charter and bylaws as exhibits). The only material difference is the listing venue: 8-B12B registers a class listed on a national securities exchange under Section 12(b); 8-B12G registers an OTC class under Section 12(g). Use both datasets together to cover the full successor-issuer population.

Form 10 / 10-12G — first-time Section 12(g) registration

Form 10 (filed on EDGAR as Form 10-12G) registers a class under Section 12(g) for an issuer registering on its own account, not as a successor. Same statutory destination as 8-B12G, but the trigger and content diverge sharply: Form 10 requires a full first-time package (business description, risk factors, audited financials, MD&A, management, executive compensation), while 8-B12G is an abbreviated successor filing that leans on the predecessor's reporting record. Form 10 filings are also far more numerous and substantially larger.

Form 10-12B — first-time Section 12(b) registration

The exchange-listed analog of 10-12G. Stands to 8-B12B as 10-12G stands to 8-B12G. Mentioned only to complete the 2x2 matrix (12(b) vs. 12(g), first-time vs. successor) that determines which Exchange Act registration form applies. (Form 10-12B is the exchange variant of Form 10.)

Form S-4 — Securities Act registration of the deal securities

Often filed for the same merger or consolidation that triggers an 8-B12G, but under a different statute. S-4 registers, under the Securities Act of 1933, the securities issued to target shareholders, with offering and proxy disclosure (deal terms, fairness opinions, pro forma financials, tax treatment). 8-B12G addresses the post-closing Exchange Act reporting status of the survivor or successor. S-4 governs the offer and issuance; 8-B12G governs ongoing periodic reporting. Same transaction, different regulatory question.

Form 8-K — current report on the underlying event

The same merger, consolidation, or share exchange that triggers 8-B12G is typically reported on Form 8-K under Item 1.01, Item 2.01, Item 3.03, Item 5.01, or Item 5.07. The 8-K is a time-pressured (four-business-day) event narrative; 8-B12G is a registration statement establishing the successor's reporting standing. 8-K volume is orders of magnitude higher, and 8-B12G content is registration-style (governance instruments, securities descriptions) rather than press-release-style narrative.

Forms 25 and 15 — predecessor deregistration

Form 25 effects delisting and deregistration of an exchange-listed class under Section 12(b); Form 15 terminates Section 12(g) registration or suspends Section 15(d) reporting. After a successor registers via 8-B12G, the predecessor commonly files Form 15 (and Form 25 if it had been listed) to wind down its own status. These are exit instruments for the predecessor, not registration statements for the successor. A full succession record typically requires pairing 8-B12G with the predecessor's 15 and, where applicable, 25.

Rule 12g-3 automatic succession — no filing at all

Rule 12g-3 provides that, in many merger and consolidation scenarios, the successor's securities are deemed registered automatically by operation of the rule, with no Form 8-B required. The 8-B12G dataset therefore captures only the subset of successions where an explicit registration statement was filed. The broader population of Rule 12g-3 successions leaves no dedicated 8-B trail and must be reconstructed from 8-K, S-4, proxy, and predecessor 15/25 filings.

Boundary summary

Form 8-B12G is uniquely defined by four converging conditions: (1) Exchange Act Section 12(g), not Section 12(b) or the Securities Act; (2) a Rule 12g-3 succession trigger, not a first-time registration; (3) abbreviated successor disclosure anchored on predecessor identification and governance exhibits, not a full Form 10 package; and (4) a small, specialized filing population. 8-B12B shares the succession trigger but routes through Section 12(b); 10-12G shares the Section 12(g) destination but lacks the succession trigger; S-4 covers the same deal under the 1933 Act; 8-K reports the event as news; 15 and 25 close out the predecessor. The dataset is the registration-statement record of OTC-track successor issuers and is most informative when paired with these neighbors to reconstruct a full succession lifecycle.

Who Uses This Dataset

The Form 8-B12G Files dataset draws a narrow set of users who work across three components of each record: the metadata entities[] block (predecessor and successor CIKs, formType, filedAt), the body TXT (Item 2 succession description, Item 4 securities registered, Item 5 exhibit list), and the exhibits themselves (charter, bylaws, instruments defining holder rights).

Securities lawyers and disclosure counsel

Counsel preparing succession registrations use the dataset as a precedent library. They pull comparable 8-B12G and 8-B12G/A filings to model Item 2 (succession mechanics under Rule 12g-3), Item 4 (description of registered securities), and Item 5 exhibits (charter and bylaw drafting). 8-B12G/A redlines reveal which sections drew staff comments. Output: cleaner first drafts and faster turnaround.

M&A transaction counsel

Deal counsel structuring holding-company reorganizations, redomiciliations, and squeeze-outs check entities[] to map predecessor-successor CIK pairs, Item 2 to confirm the legal form (statutory merger, share exchange, consolidation), and Item 5 exhibits to see whether the successor adopted predecessor governance documents wholesale or restated them. This feeds step plans, closing checklists, and SEC filing sequencing.

Corporate secretaries and in-house compliance

Secretaries at successor issuers actually filing the 8-B12G use recent precedents to format their submission, replicate Items 1 through 5, and confirm the EDGAR exhibit list in documentFormatFiles[]. 8-B12G/A patterns indicate what triggers post-effective amendments and the expected timeline. filedAt and acceptance metadata feed internal filing logs.

Corporate governance and academic researchers

Researchers studying reincorporation patterns and charter evolution use the full population as a structured sample. They join on entities[] CIK pairs, run time-series on filedAt, and hand-code Item 2 narratives (state of incorporation, board structure, dual-class adoption) and Item 5 charter exhibits.

Forensic and historical research

Analysts tracing long-lived OTC issuers use predecessor-successor CIK pairs in entities[] to bridge identity gaps that break standard issuer databases. Item 2 supplies the narrative bridge; Item 5 exhibits often contain the underlying plan-of-reorganization. Supports chain-of-title work and dormant-issuer investigations.

Data engineering and reg-tech teams

Engineers building EDGAR entity-resolution pipelines treat the metadata JSON as ground truth for predecessor-successor CIK links, feeding entities[], formType, and filedAt into graph databases that preserve corporate identity over time. The labeled population also trains classifiers that distinguish 8-B12G from adjacent forms (Form 10, S-4, other 8-B variants).

LLM and RAG developers

Teams building retrieval over registration prose use the body TXT as compact, cleanly sectioned examples (Item 2, Item 4, Item 5) for chunking and embedding. Charter, bylaw, and rights-instrument exhibits enrich clause-level retrieval over governance text.

Audit and forensic accounting

Auditors verifying that reporting obligations were properly inherited reconcile filedAt and entities[] against the issuer's stated reorganization date and subsequent periodic filings under the successor CIK, flagging cases where succession was claimed but no 8-B12G appears in EDGAR.

Every user group needs to bridge two corporate identities across one reporting transition. The entities[] CIK pairs, Item 2 succession narrative, Item 4 securities description, and Item 5 governance exhibits are the fields that make that bridge auditable.

Specific Use Cases

Concrete workflows the Form 8-B12G Files dataset supports, grounded in the predecessor-successor linkage, succession narratives, securities descriptions, governance exhibits, and amendment chains the records actually carry.

Building a predecessor-successor CIK bridge for entity-resolution pipelines

Reg-tech engineers maintaining EDGAR entity graphs use metadata.json.entities[] (successor CIK, fileNo, irsNo, SIC, tickers) joined to the predecessor identifiers extracted from the body TXT under ITEM 2 (TRANSACTION OF SUCCESSION). The output is a directed CIK-to-CIK edge with a filedAt timestamp and a transaction-type label (statutory merger, holding-company reorganization, consolidation), inserted into a graph database so that downstream queries on the successor CIK can backfill the predecessor's Form 10-K, Form 10-Q, and 8-K history.

Drafting Item 2 and Item 5 from comparable filings

Securities counsel preparing a new 8-B12G load the dataset as a precedent corpus, filter formType == "8-B12G" by registrant SIC and recent filedAt, and pull the ITEM 2 succession-mechanics paragraph and the ITEM 5 exhibit inventory from the sequence-1 body document. Comparable charter, bylaw, and rights-agreement exhibits filed in-line as document-2.txt, document-3.txt, etc. (typed EX-3.1, EX-3.2, EX-4.1 in documentFormatFiles[]) are reused as drafting templates for the new registrant's governance documents.

Reconstructing amendment chains for a single registrant

Compliance analysts tracking the full registration history of a successor issuer group records by entities[].cik and entities[].fileNo (since each 8-B12G/A receives its own accession number and is not nested under the original), then order them by filedAt to produce an Amendment No. 1 / No. 2 / ... timeline. Diffing the ITEM 4 securities description and the ITEM 5 exhibit list across that chain shows what the staff comment process drove the registrant to add or restate.

Mining ITEM 5 exhibit lists for governance-document corpora

Corporate-governance researchers and LLM/RAG developers parse the ITEM 5 exhibit list from the body TXT and resolve it against documentFormatFiles[] to separate exhibits filed in-line (locally available document-<N>.txt files typed EX-3, EX-4, EX-10, EX-99) from exhibits incorporated by reference (pointers to other Reg. Nos. and CIKs). The in-line set is fed to charter, bylaw, and rights-instrument clause-extraction pipelines; the by-reference pointers drive automated retrieval of the predecessor's prior filings.

Auditing claimed successions against EDGAR

Forensic accountants and audit teams take a list of issuers that publicly described a Rule 12g-3 succession in their 10-K or proxy and check whether a corresponding 8-B12G record exists in the dataset, matching on successor CIK and a filedAt window around the stated reorganization date. Missing records flag candidates for Rule 12g-3 automatic succession (no filing required) versus genuine compliance gaps; matched records confirm the registration path via formType and the ITEM 2 predecessor identification.

Coding charter and rights-plan changes across reorganizations

M&A counsel and academic researchers studying redomiciliations and holding-company restructurings hand-code ITEM 2 (state of incorporation pre- and post-succession) and compare in-line ITEM 5 charter and bylaw exhibits between the predecessor's prior filings and the successor's 8-B12G. The structured output (state change, dual-class adoption, poison-pill insertion, board classification) is keyed to the successor CIK and filedAt, supporting time-series analysis of governance migration.

Training form-type classifiers on a labeled minority class

Data-science teams building EDGAR form-type classifiers use the full 8-B12G and 8-B12G/A population as positive examples for a minority class that is easily confused with Form 10-12G, Form 10-12B, Form 8-B12B, and Form S-4. The body TXT (cover page, ITEM 1 through ITEM 5 headings, signature block) supplies the text features, and metadata.json.formType together with entities[].type supplies the labels.

Dataset Access

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

This endpoint returns dataset-level metadata (name, description, last updated timestamp, earliest sample date, total records and size, form types covered, container format, and file types) along with the full list of container files. Each container entry includes its key, size, record count, last updated timestamp, and direct download URL. Use this endpoint to programmatically enumerate available containers and to monitor which monthly archives have changed in the most recent refresh run, so only the updated containers need to be re-downloaded. No API key is required to call this endpoint.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-6a29-8d83-2462634829d1",
        

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

          4
            "name": "Form 8-B12G Files Dataset",
        

          5
            "description": "Form 8-B12G is a registration statement used by certain successor issuers to register a class of securities under Section 12(g) of the Securities Exchange Act of 1934.",
        

          6
            "updatedAt": "2026-04-16T08:32:02.504Z",
        

          7
            "earliestSampleDate": "1994-07-01",
        

          8
            "totalRecords": 226,
        

          9
            "totalSize": 3455451,
        

          10
            "formTypes": ["8-B12G", "8-B12G/A"],
        

          11
            "containerFormat": "ZIP",
        

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

          13
            "containers": [
        

          14
              {
        

          15
                "downloadUrl": "https://api.sec-api.io/datasets/form-8b12g-files/1994/1994-07.zip",
        

          16
                "key": "1994/1994-07.zip",
        

          17
                "size": 142336,
        

          18
                "records": 9,
        

          19
                "updatedAt": "2026-04-16T08:32:02.504Z"
        

          20
              }
        

          21
            ]
        

          22
          }
        

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

Use this URL to download the complete dataset as a single ZIP archive containing every Form 8-B12G and 8-B12G/A filing from 1994 onward. This endpoint requires an SEC API key supplied via the token query parameter.

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

Each monthly container can be downloaded individually using the URL listed in the index JSON, which is useful for incremental updates or fetching only specific months. This endpoint also requires an API key passed as the token query parameter.

Frequently Asked Questions

What is Form 8-B12G?

Form 8-B12G is a registration statement under the Securities Exchange Act of 1934 used by a successor issuer to register a class of securities under Section 12(g) — the over-the-counter registration provision — when the issuer has succeeded to a predecessor's reporting obligation through a merger, consolidation, holding-company reorganization, or similar transaction. Form 8-B12G/A is the amendment variant of the same form.

Who is required to file Form 8-B12G?

The filer is the successor issuer itself, filing under its own CIK as the new registrant of record. Typical filers are newly formed parent companies in holding-company reorganizations, surviving corporations in mergers that absorb a predecessor reporting company, entities formed through reincorporation in a different state, and new corporations formed by the consolidation of two or more constituent companies. The predecessor company is described narratively in the filing but is not itself the filer.

How does Form 8-B12G differ from Form 8-B12B?

Both forms address the same trigger — a corporate succession under Rule 12g-3 — and use the same abbreviated successor-disclosure structure. The difference is the listing venue: Form 8-B12B registers a class listed on a national securities exchange under Section 12(b), while Form 8-B12G registers an over-the-counter (non-listed) class under Section 12(g). Successors that will list on an exchange use 8-B12B; successors whose class will trade OTC use 8-B12G.

What is the relationship between Form 8-B12G and Rule 12g-3?

Rule 12g-3 under the Exchange Act provides that when a successor issues securities to holders of a class of Section 12(g)-registered securities of a predecessor, the successor's securities are automatically deemed registered under Section 12(g) by operation of the rule, effective upon succession. Form 8-B12G is the registration filing the successor uses to formally register and confirm that automatic Rule 12g-3 succession on EDGAR — it identifies the successor as the new registrant, describes the succession transaction, and attaches successor-specific exhibits.

What does one record in this dataset contain?

One record is one EDGAR submission of either Form 8-B12G or Form 8-B12G/A, packaged as a per-accession folder keyed by the 18-digit accession number. The folder contains a metadata.json describing the parsed EDGAR submission header (formType, accession number, filedAt, filer entities, document index) and one or more document-<sequence>.<ext> files for the registration statement and any in-line exhibits, named by EDGAR sequence number.

What time period does the dataset cover, and what file format is it distributed in?

The dataset covers all Form 8-B12G and 8-B12G/A filings on EDGAR from July 1994 to present. It is distributed as ZIP containers organized by year and month — a top-level ZIP that, when expanded, exposes a year directory for each calendar year and a <YYYY-MM>.zip archive for each calendar month. Inside each accession folder the files are plain-text TXT documents and the metadata.json header; image attachments and the SGML complete-submission wrapper are excluded.

Why does the dataset have so few records compared to other SEC form datasets?

Form 8-B12G occupies a narrow regulatory niche: a Section 12(g)-registered predecessor must succeed to a non-listed successor through a transaction not already handled via a Form S-4 prospectus. In modern practice, S-4 transactions combined with Rule 12g-3 automatic succession have substantially displaced standalone 8-B filings, and many Rule 12g-3 successions occur with no Form 8-B filed at all. The dataset therefore captures only the subset of successions where an explicit Form 8-B12G registration statement was submitted, and pre-EDGAR paper filings on this form are not in the electronic corpus.