Form S-4 POS Files Dataset

The Form S-4 POS Files Dataset is a corpus of post-effective amendments to Form S-4 (and especially Form S-4EF) registration statements filed under the Securities Act of 1933, harvested in full from EDGAR. One record represents one Form S-4 POS submission — a single accession number — by the registrant whose securities are registered, materialized as an accession folder containing a metadata.json file and the original EDGAR documents (the amended registration statement, any revised prospectus or prospectus supplement, legality opinions, auditor consents, and other exhibits required to reflect changes since effectiveness). The filer base is concentrated in newly formed bank and savings-and-loan holding companies that registered shares on Form S-4EF under General Instruction G of Form S-4, plus other S-4 registrants that amend after their registration statements have already become effective. Coverage runs from January 1, 1994 — aligned with the rollout of mandatory EDGAR filing under Regulation S-T — through the present.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset packages every Form S-4 POS filing transmitted to EDGAR from January 1994 forward. Form S-4 POS is a post-effective amendment to a Form S-4 registration statement under the Securities Act of 1933: the POS suffix designates that the registration statement has already been declared effective and the amendment modifies it after the fact. Within EDGAR, S-4 POS is most often used to amend Form S-4EF registration statements — the auto-effective form available under General Instruction G of Form S-4 for securities issued in connection with the formation of a bank holding company or savings-and-loan holding company — or to convert the residual un-issued portion of a closed merger registration into a Form S-8 covering shares issuable under equity-compensation plans assumed from the acquired entity. Because of that gating, the filer base is heavily concentrated in bank and thrift holding-company SIC codes (6020, 6021, 6022, 6035, 6036), and many filings carry titles such as Post-Effective Amendment No. 1 on Form S-8 to Form S-4 Registration Statement.

For each accession number, the dataset includes a structured metadata.json file plus all documents in the original EDGAR submission except image files. The substantive content covers the amended registration statement itself plus the exhibits that S-4 / S-8 require when newly filed material is being added or refreshed: an updated prospectus or prospectus supplement, refreshed financial statements (or incorporation-by-reference of current periodic reports), a legality opinion of counsel, consents of independent registered public accounting firms, and any further exhibits implicated by changes since the original effectiveness. The container format is a single ZIP archive partitioned into per-month sub-archives, and the included file types are TXT, JSON, HTML, and PDF.

Content Structure of a Single Record

What one record represents

One record in the Form S-4 POS Files Dataset is a single EDGAR accession: one Form S-4 POS submission filed by one registrant (with any co-registrants) on one date, identified by its 18-digit accession number. The record is materialized on disk as a folder named with the accession number in its no-dash form (for example, 000071507225000128). The folder holds two layers of content: a metadata.json file describing the filing event, and the text-bearing documents that constituted the original EDGAR submission, preserved with their original filenames inside their EDGAR SGML wrappers. A record therefore captures both the structured filing-event metadata and the underlying registration-amendment package as it was transmitted to EDGAR.

On-disk layout

A record is laid out as a flat directory:

• metadata.json — structured metadata for the filing; always present.
• One main amendment document — the body of the post-effective amendment, carrying EDGAR <TYPE>S-4 POS and <SEQUENCE>1. The filename is filer-controlled (for example, post-effectiveamendmentonf.htm).
• Zero or more exhibit documents — each its own file, each wrapped in the EDGAR SGML <DOCUMENT> envelope. Filenames generally encode the exhibit number (for example, ex51_phelpsopinion.htm, ex231_horneconsent.htm).

There are no nested subfolders inside an accession folder; every document sits at the same level. The ordering of documents within the original submission is preserved through the <SEQUENCE> numbering inside each SGML wrapper and through the documentFormatFiles[] array in metadata.json, not through directory structure.

The metadata.json block

metadata.json is the canonical structured layer of the record. It describes the filing event, the filer(s), and an inventory of every document that made up the original EDGAR submission.

• formType — always the string "S-4 POS" for this dataset.
• accessionNo — the canonical accession number with dashes (for example, 0000715072-25-000128); the on-disk folder uses the no-dash form of the same identifier.
• filedAt — ISO-8601 timestamp, with timezone offset, of the EDGAR filing-acceptance event.
• effectivenessDate — the date the post-effective amendment becomes or became effective. For S-4 POS amendments to S-4EF this is typically the same calendar day as filedAt, reflecting the auto-effective nature of the underlying registration form.
• description — a short prose label for the form type, typically a variant of "Form S-4 POS - Securities issued, formation of bank or savings and loan holding company [General Instruction G], post-effective amendments".
• linkToFilingDetails — URL of the primary filing document on sec.gov/Archives/edgar/....
• linkToHtml — URL of the EDGAR filing index page (the -index.htm page that lists every document).
• linkToTxt — URL of the full submission text file (the concatenated SGML bundle).
• linkToXbrl, dataFiles, seriesAndClassesContractsInformation — present in the schema but typically empty for S-4 POS filings, which carry no fund series/class data.
• id — a 32-character hex internal identifier.
• documentFormatFiles[] — inventory of every document in the original submission, with one entry per file. Each entry carries sequence (1-indexed within the submission), size (bytes, encoded as a string), documentUrl pointing to the file on EDGAR, description (e.g. "S-4 POS", "EX-5.1"), and type (e.g. "S-4 POS", "EX-23.1", "GRAPHIC"). The final element by convention is the complete .txt submission bundle, where type and sequence are encoded as a single space and description is "Complete submission text file".
• entities[] — one entry per registrant on the filing (the principal filer plus any co-registrants). Each entity carries cik, companyName (typically suffixed with the role, for example "RENASANT CORP (Filer)"), fileNo (the registration file number such as 333-281851 that ties the amendment to the original S-4 / S-4EF), filmNo, act ("33" for the Securities Act of 1933), formType, sic (industry classifier, often a 60xx bank code), stateOfIncorporation, fiscalYearEnd, and a tickers array. When the filing relates to a completed merger, tickers frequently lists both the surviving entity's ticker and the acquired entity's former ticker.

Document types inside the record

Every document file is the original EDGAR-submitted artifact, beginning with the SGML <DOCUMENT> header and containing an HTML payload. The file-types found in the dataset are TXT, JSON, HTML, and PDF, although in practice modern S-4 POS records consist almost exclusively of HTM/HTML documents plus the JSON manifest. The principal document types are:

• S-4 POS — the body of the amendment. This is the main document, sequence 1. Its content depends on the purpose of the amendment.
  • For an "on Form S-8 to Form S-4" conversion, the body opens with a facing page identifying the registrant and the registration file number, recites the deregistration of un-issued shares from the original S-4 registration and their re-registration on Form S-8, describes the equity-compensation plans assumed from the acquired entity, and incorporates the registrant's current Annual Report on Form 10-K and other Exchange Act reports by reference.
  • For substantive prospectus updates, the body instead carries a refreshed prospectus or prospectus supplement covering material developments since effectiveness, updated risk factors, updated financial information, and revised plan-of-distribution language.
  • The Part II section of the amendment lists the exhibits, recites the undertakings required by Item 512 of Regulation S-K, and contains the signatures of the registrant, its principal executive and financial officers, and a majority of its directors, together with the power-of-attorney recitation.
• EX-5.1 — opinion of counsel as to legality. A short legal opinion letter, addressed to the registrant, in which counsel opines that the securities, when issued in accordance with the relevant plan or agreement, will be validly issued, fully paid, and non-assessable. Includes counsel's consent to being named in the registration statement and to the filing of the opinion as Exhibit 5.1.
• EX-23.x — consents of independent registered public accounting firms. One consent per audited financial-statement set incorporated by reference. In merger-related conversions this typically means at least two consents: one for the filer's auditor's report on the filer's financial statements, and one or more for the acquired entity's auditor's report on the acquired entity's financial statements. Each consent is a single page on auditor letterhead.
• Other exhibit families. Depending on what changed since effectiveness, an S-4 POS may also include EX-3 (charter or by-laws), EX-4 (instruments defining the rights of security holders), EX-8 (tax opinions), EX-10 (material contracts such as the assumed equity-compensation plans), and EX-99 (additional information such as press releases or completed-merger announcements).
• GRAPHIC entries. Image files (logos, scanned signatures, charts) referenced from the HTML by <img src="..."> tags. These are enumerated in documentFormatFiles[] but are intentionally excluded from the on-disk package, so the materialized HTML carries unresolved image references.

EDGAR SGML wrapper

Each document file in the record is the verbatim EDGAR-submitted document, which means each file begins with the SGML <DOCUMENT> envelope before any HTML. The wrapper has a fixed shape:

          1
          <DOCUMENT>
        

          2
          <TYPE>S-4 POS
        

          3
          <SEQUENCE>1
        

          4
          <FILENAME>post-effectiveamendmentonf.htm
        

          5
          <DESCRIPTION>S-4 POS
        

          6
          <TEXT>
        

          7
          <html>... full HTML payload ...</html>
        

          8
          </TEXT>
        

          9
          </DOCUMENT>
        

<TYPE> carries the EDGAR exhibit-type code (S-4 POS, EX-5.1, EX-23.1, etc.); <SEQUENCE> carries the 1-indexed position within the submission; <FILENAME> is the original filename as submitted; <DESCRIPTION> is a short human-readable label, often identical to <TYPE>. The HTML payload itself is what would otherwise render as a normal SEC filing in a browser. Any consumer parsing these files should strip the leading SGML header lines (and the trailing </TEXT></DOCUMENT> block, when present) before feeding the payload to an HTML parser.

Container layout

The dataset is delivered as a single ZIP archive at the top level, partitioned into per-month sub-archives organized by year. The path convention is form-s4-pos-files/<YYYY>/<YYYY-MM>.zip. Inside each monthly ZIP is a single top-level directory named after the month (<YYYY-MM>/) holding one subdirectory per filing keyed by its no-dash 18-digit accession number. Each accession folder contains the files described above (metadata.json plus the EDGAR documents). Monthly archives are small because S-4 POS amendments are short, exhibit-light filings and the form itself is a niche, low-volume series.

Image-file exclusion

The package intentionally omits image and graphic exhibits. metadata.json -> documentFormatFiles[] continues to list every GRAPHIC-typed file from the original submission with its documentUrl, size, and sequence, and the HTML body still contains the corresponding <img src="image_X.jpg"> tags, but the binary image files themselves are not materialized inside the accession folder. Consumers needing the original images can fetch them from the documentUrl values in documentFormatFiles[]. All other text-bearing exhibits — HTML, TXT, and PDF documents — are present in full.

Structural evolution since 1994

The Form S-4 POS form code and its underlying purpose have been stable across the dataset's coverage window (January 1994 to present), but the presentation of the source filings has evolved meaningfully:

• Early-to-mid 1990s filings were submitted as plain ASCII text inside the SGML <DOCUMENT> envelope. The body of the amendment, the legal opinion, and the auditor consents all appeared as <TEXT> payloads with monospaced text formatting rather than HTML markup; tables were rendered as ASCII columns.
• Late 1990s through mid-2000s saw HTML adoption become routine, with documents wrapping HTML payloads inside the SGML envelope and embedding inline graphics for the first time. Exhibit numbering conventions and the mapping of <TYPE> codes to exhibit families stabilized in this era.
• Mid-2000s to present filings are essentially all HTML-wrapped, with image references handled via separate GRAPHIC-typed documents. PDF documents occasionally appear for scanned legal opinions or signed consents but remain a minority. Filing-acceptance metadata, file-number tracking, and the documentFormatFiles[] inventory structure have remained consistent.

The dominant on-disk format trajectory has therefore been ASCII-in-SGML to HTML-in-SGML, with the SGML envelope itself unchanged. A separate substantive evolution worth noting is the practical convergence of S-4 POS use cases on bank and thrift holding-company merger workflows: as the M&A patterns in that segment standardized around assumed equity-compensation plans, the "Post-Effective Amendment No. 1 on Form S-8 to Form S-4" template — body plus EX-5.1 plus paired EX-23.x consents — became the modal exhibit footprint for newer records.

Interpretation and extraction notes

• Incorporation by reference is heavy. S-4 POS bodies typically forgo restating financial statements or full prospectus content in favor of incorporating the registrant's current Annual Report on Form 10-K, subsequent Quarterly Reports on Form 10-Q, and intervening Current Reports on Form 8-K by reference. Readers seeking the financial statements supporting a record will generally need to follow the fileNo and the registrant's CIK out to those separately filed documents.
• The file number is the through-line. Every entity in entities[] carries fileNo — the 333-xxxxxx Securities Act registration number assigned to the original S-4 / S-4EF. This number is the key for tying an S-4 POS record back to the parent registration statement and to any earlier or later amendments in the same registration chain.
• Multiple registrants are common. Bank holding-company combinations frequently produce filings with co-registrants (the surviving holding company plus subsidiary trust-preferred issuers, for example). Each appears as its own entities[] entry with its own CIK, SIC, and ticker set.
• Filenames are filer-controlled and not standardized. While conventions like ex51_*.htm and ex231_*.htm are widespread, filenames are chosen by the filer's printer or counsel and should not be relied on for classification. The authoritative classifier is the <TYPE> value in the SGML wrapper and the type field in documentFormatFiles[].
• Signatures live in the body. The signatures of the registrant, its principal executive and financial officers, and a majority of its directors appear at the end of the main S-4 POS body, not as a separate document.
• Effectiveness is often same-day. Because S-4EF is an auto-effective form under General Instruction G, effectivenessDate and filedAt frequently fall on the same calendar day, which differs from the typical lag pattern seen on full Securities Act registrations.
• Unresolved image references are expected. HTML payloads referencing image_0.jpg, image_01.jpg, and similar filenames will not render those images locally; this is by design rather than a defect of the record. Resolve them on demand from the documentUrl values in documentFormatFiles[] when needed.
• One record, one accession. Splitting a record by document, or stitching documents across accessions, is not implied by the layout. The accession folder is the natural unit for indexing, hashing, or downstream parsing.

Who Files or Publishes This Dataset, and When

Who files the record

Each record is one Form S-4 POS submission to EDGAR by the registrant on the underlying Form S-4 (or S-4EF) registration statement. The filer is always the issuer whose securities are registered — never the target company, target shareholders, underwriters, financial advisors, or exchange agents, even when those parties are named in the prospectus.

The dataset description focuses on Form S-4EF (the auto-effective variant under General Instruction G of Form S-4, used to form bank and savings-and-loan holding companies). In practice the "S-4 POS" submission type is also used by ordinary S-4 registrants amending after effectiveness, so the filer population in this dataset includes both groups.

Filer population

• Newly formed bank and savings-and-loan holding companies that registered shares on Form S-4EF under General Instruction G — typically shell entities organized to acquire an existing bank or thrift in exchange for the holding company's shares, where shareholder rights are not materially altered.
• Other Form S-4 registrants — operating companies registering securities for mergers, exchange offers, or reclassifications — when they amend after effectiveness rather than before (S-4/A is used pre-effectiveness).
• Successor or surviving entities that adopt an existing S-4 registration after a name change, redomiciliation, or completed business combination.

The signing block of an S-4 POS must include the registrant, its principal executive, financial, and accounting officers, and a majority of the board (or persons performing similar functions). Required expert consents (auditors under Section 7, counsel for legality opinions) are typically refiled because prior consents speak only as of the earlier effective date.

Triggering events

Form S-4 POS is event-driven, not periodic. A filing is triggered when, after the registration statement has become effective, one of the following occurs:

• Section 10(a)(3) updating obligation — the prospectus is being used past the point where its financial information is current, requiring refreshed Section 10(a) disclosure (often satisfied by incorporating the latest 10-K, 10-Q, or 8-K by reference).
• Item 512(a) fundamental change — facts or events arising after effectiveness represent a fundamental change in the registration statement, or material plan-of-distribution information was not previously disclosed.
• Deregistration of unsold securities after the business combination or exchange offer closes with shares left unissued.
• Name change, redomiciliation, or successor registrant continuation, where the existing registration is carried forward to a new or renamed issuer.
• Carry-forward to Form S-8 — in holding-company formations, shares originally registered on S-4EF that relate to assumed employee plans are deregistered by S-4 POS concurrent with a new S-8 filing.
• Curative amendments correcting material misstatements or omissions identified after effectiveness, including responses to staff comments delivered post-effectiveness.

Regulatory framework

The governing statute is the Securities Act of 1933. Post-effective amendments are governed by Section 10(a)(3), Rules 401, 413, and 462, and the Item 512 undertakings in Regulation S-K. Whether an S-4 POS is auto-effective on filing or requires Commission action depends on its content under Rule 462; the auto-effectiveness of the underlying S-4EF does not by itself extend to substantive amendments. Re-signing the registration statement re-exposes signing officers and directors to Section 11 liability as of the amendment's new effective date.

Timing and cadence

There is no fixed deadline. Common timing patterns:

• Promptly after annual financials go stale under Section 10(a)(3), if the registration is still in use.
• Promptly after a material development that would otherwise leave the prospectus misleading.
• At or shortly after closing of the underlying transaction, to deregister unsold shares.
• Concurrent with a name change, reorganization, or S-8 carry-forward.

The dataset begins 1994-01-01, reflecting the rollout of mandatory EDGAR filing under Regulation S-T. Paper post-effective amendments to Form S-4 (adopted in 1985) predate that window and are not in scope.

Important distinctions

• S-4 POS vs. Form S-4/A — S-4/A is the pre-effective amendment; S-4 POS is the post-effective amendment. The choice turns solely on whether the registration statement is already effective.
• S-4 POS vs. 424B prospectus filings — Rule 424 filings deliver a varying prospectus without amending the registration statement. When the registration statement itself must change, an S-4 POS is required.
• S-4EF vs. S-4 underlying form — both are amended on EDGAR as "S-4 POS"; the form-type tag does not distinguish them, so users must inspect the document to know which is being amended.
• Foreign private issuers use Form F-4 and file "F-4 POS"; those records are not in this dataset.
• Shelf-based acquisition shelves on Form S-3 or Form F-3 are amended as "S-3 POS" or "F-3 POS," not S-4 POS.
• Target shareholders and target companies are described in the prospectus but never file the S-4 POS; the registered-securities issuer is the sole filer.

How This Dataset Differs From Similar Datasets or Filings

The Form S-4 POS dataset sits at a narrow intersection: post-effective amendments to S-4EF registration statements, the auto-effective bank and savings-and-loan holding company formation track under General Instruction G of Form S-4. Because of that narrow scope, the most useful comparisons fall into three groups: other members of the S-4 family, parallel "POS" amendments in adjacent registration regimes, and the merger-disclosure documents that travel alongside an S-4 process.

Form S-4EF (the underlying registration)

S-4EF is the immediate parent of every filing in this dataset. It is the auto-effective S-4 variant used by bank and savings-and-loan holding companies forming under General Instruction G, becoming effective on filing without staff review. S-4 POS captures only what changes to that statement after it has gone effective. Use S-4EF for the original formation filing; use S-4 POS for everything that follows on the same registration.

Form S-4 (the general parent form)

Form S-4 is the full registration statement for securities issued in mergers, exchange offers, asset acquisitions, and reclassifications. It carries the substantive deal disclosure: deal description, fairness opinions, target and acquirer financials, pro formas, risk factors, and the merger agreement. S-4 POS does not duplicate this content; it carries only the post-effective revisions and applies only to the bank-holding-company auto-effective subset. For the deal itself, go to S-4. For changes after a holding-company registration is already effective, S-4 POS.

Form S-4/A (pre-effective amendment)

Both S-4/A and S-4 POS amend an S-4-family registration, but at opposite sides of effectiveness. S-4/A revises the statement during SEC staff review, before it goes effective, and reflects the comment-and-response cycle. S-4 POS revises a registration that is already effective, typically to refresh stale financials, reflect post-closing adjustments, deregister unsold shares, or update incorporated periodic reports. Use S-4/A for review-cycle analysis; use S-4 POS for after-effectiveness maintenance.

Form S-4MEF (additional-securities short form)

Form S-4MEF is a Rule 462(b) short-form registration that adds up to 20% more securities of the same class when the original S-4 amount proves insufficient, effective immediately on filing. It and S-4 POS both adjust a live S-4 registration, but S-4MEF expands capacity while S-4 POS revises content. They can coexist in one transaction and answer different questions.

Form F-4 POS (foreign-issuer counterpart)

Form F-4 POS is the post-effective amendment to F-4, the foreign-private-issuer version of S-4. The split is jurisdictional: S-4 POS covers domestic issuers (and within that, only the bank-holding-company auto-effective subset), F-4 POS covers foreign issuers. Cross-border merger research may need both; domestic bank-holding research stays in S-4 POS.

Form S-1 POS, S-3 POS, F-3 POS, S-8 POS

These are structurally analogous post-effective amendments in adjacent registration regimes and are the most common source of confusion by name. They are not interchangeable with S-4 POS:

• Form S-1 POS amends standalone primary-offering registrations (IPOs, follow-ons), not merger registrations.
• Form S-3 POS and Form F-3 POS amend shelf registrations for seasoned domestic and foreign issuers, typically to add selling stockholders, deregister unsold shelf capacity, or update a multi-year base prospectus.
• Form S-8 POS amends employee-benefit-plan registrations. The "POS AM on S-8 to S-4" pattern, in which an acquirer rolls an assumed target S-8 into its own framework, is filed as S-8 POS and lives in the S-8 POS dataset, not here.

S-4 POS is tied to a single, discrete bank-holding-company formation rather than ongoing offering programs or benefit-plan administration.

Form 424B prospectus filings (424B1–424B8)

A 424B filing transmits a prospectus or prospectus supplement under Rule 424(b) shortly after effectiveness or pricing. An S-4 POS is a formal post-effective amendment under Section 8(c) of the Securities Act that revises the registration statement itself, not just the delivered prospectus. Form 424B is high-volume and routine across all registration forms; S-4 POS is narrow and revises the underlying filing. Use Form 424B1–424B8 for delivered prospectus content; use S-4 POS when the registration document has been amended.

Form 425 (merger communications)

Form 425 captures written deal communications (press releases, investor decks, employee FAQs) filed under Rules 425, 165, and 14a-12. Its relationship to S-4 POS is contextual, not structural: 425 records what was said about the deal in public; S-4 POS records formal changes to the registered offering document.

DEF 14A (merger proxy)

DEF 14A is the definitive proxy statement filed under Section 14(a) when a merger requires a shareholder vote, and it often runs as a joint proxy/prospectus alongside an S-4. Content overlaps (merger agreement, fairness opinions, financials, pro formas), but the regimes differ: DEF 14A solicits votes under the Exchange Act proxy rules; S-4 POS amends a Securities Act registration. For General Instruction G holding-company formations, the auto-effective S-4EF path often removes or restructures the proxy step, further separating these two records.

What makes the S-4 POS dataset distinct

S-4 POS is intentionally narrow. A filing belongs in this dataset only when (a) the underlying registration was a bank or savings-and-loan holding company formation under General Instruction G filed on S-4EF, (b) that registration has already gone auto-effective, and (c) the registrant is formally amending the effective statement. Reach for S-4 POS specifically to study how bank and thrift holding-company formation registrations evolve after effectiveness: stale-financials refreshes, post-closing structural changes, deregistration of unsold shares, prospectus revisions tied to the holding-company entity, and carry-forward exhibits. For any other slice of the merger-and-registration landscape, a neighboring dataset is the better fit, and none of them substitute for S-4 POS when the object of interest is the post-effective amendment document itself.

Who Uses This Dataset

The dataset serves a narrow set of professionals working on bank and savings-and-loan holding company formations. Each group reads a different slice of the same record: the amended prospectus, the revised financial statements or incorporation-by-reference language, the legality and tax opinions, the auditor consents, or the filer metadata.

Bank holding company formation counsel

Securities lawyers in community-bank and thrift practice groups use the dataset as a precedent library for drafting post-effective amendments under General Instruction G. They mine the cover page, prospectus narrative, description of the reorganization agreement, description of capital stock, and exhibit index to model share-exchange mechanics, dissenters' rights, regulatory approvals, and closing conditions. Output: drafting checklists and disclosure-completeness reviews on live engagements.

Bank M&A advisors and sector research analysts

Advisors structuring small-cap bank combinations and holding company formations use the corpus to benchmark exchange ratios, pro forma share counts, transaction descriptions, and any fairness disclosures. Sector research desks treat the population as a clean sample for league tables and pipeline reports on community and regional bank reorganizations.

Transaction tax counsel

Tax advisors read the federal tax disclosure in the amended prospectus and any EX-8 opinion to benchmark how peers treat reorganization qualification, fractional shares, and basis carryover. The corpus is small enough to read end-to-end and large enough to surface drafting variation.

Legality and consent providers (EX-5.1, EX-23)

Law firms issuing EX-5.1 opinions compare assumptions, qualifications, and reliance carve-outs across post-effective amendments. Audit firms reviewing EX-23 consents check how prior-period reports are referenced and how incorporated periodic filings are described. Both groups work directly off the exhibit files.

Diligence teams in later transactions

When a holding company originally registered on Form S-4EF later pursues an M&A deal, capital raise, or change-in-control transaction, diligence teams pull the original S-4EF together with each S-4 POS amendment to reconstruct the reorganization chain. They rely on the as-amended prospectus, EX-5.1, EX-8, and EX-23 to substantiate the validity and tax treatment of outstanding securities.

Federal banking supervisory analysts

Analysts at federal banking supervisory agencies cross-reference S-4 POS filings against holding company applications and change-in-control submissions. The prospectus disclosures on regulatory approvals, ownership thresholds, and pro forma capital structure corroborate facts in supervisory records and feed policy work on the holding company formation pipeline.

Entity-structure and corporate governance analysts

Teams maintaining corporate family trees and beneficial-ownership maps use the issuer metadata, reorganization description, and post-reorganization capital structure to record the transition from stand-alone bank to holding company and to flag charter, bylaw, and equity-plan changes.

Academic researchers in banking and financial economics

Because the S-4EF/S-4 POS path is specific to holding company formation, the dataset isolates a population otherwise hard to extract from broad S-4 data. Researchers build samples from the metadata, cover page, and prospectus narrative for studies of charter conversions, dual-bank-system migration, and post-formation capital actions.

EDGAR data engineering and RAG teams

Data and ML teams use the bundled corpus (TXT, HTML, PDF, plus per-accession JSON) for parser development, exhibit-type classification, and prospectus-section extraction. The narrow, exhibit-light S-4 POS corpus is practical for end-to-end pipeline tests and for fine-tuning retrieval models on holding-company-formation concepts: exchange ratios, regulatory approval language, dissenters' rights, and incorporation-by-reference patterns.

Specific Use Cases

The Form S-4 POS dataset is small and narrowly gated, which makes it well suited to specific workflows tied to bank and thrift holding-company formation registrations and their post-effective maintenance.

Building a precedent library for post-effective amendments under General Instruction G

Bank holding-company counsel pull the main S-4 POS body across the corpus to compare facing pages, deregistration recitals, exhibit indexes, and Item 512 undertakings when drafting their own amendments. Filtering entities[].sic on 6020/6021/6022/6035/6036 and grouping by fileNo yields a clean per-registration history for each precedent. Output: drafting checklists, redline-ready templates, and disclosure-completeness reviews on live engagements.

Reconstructing a registration chain from a single file number

Diligence teams investigating a bank holding company's outstanding shares use entities[].fileNo (the 333-xxxxxx Securities Act number) as the join key to assemble the original S-4EF, every S-4 POS amendment, and any S-4MEF or 424B filings on the same registration. The metadata.json effectivenessDate, the body's deregistration language, and the EX-5.1 opinion together establish what was registered, what was issued, and what was carried forward or deregistered.

Benchmarking EX-5.1 legality opinions and EX-23 consent practices

Law firms and audit firms read the exhibit set directly: EX-5.1 for assumptions, qualifications, validly-issued language, and reliance carve-outs; EX-23.1 and sibling consents for how prior-period auditor reports and incorporated 10-K/10-Q filings are described. Because consents typically appear in pairs after a closed merger (filer auditor plus acquired-entity auditor), the corpus surfaces drafting variation across both sides of the transaction.

Tracking assumed equity-compensation plans in the "POS AM on Form S-8 to Form S-4" pattern

Compensation counsel and entity-structure analysts isolate filings whose body recites conversion of un-issued S-4 shares onto Form S-8, then read the assumed-plan descriptions and any EX-10 plan exhibits to record which target equity plans the acquirer assumed and on what terms. Combined with the tickers array, which often lists both the surviving and the acquired ticker, this produces a dataset of assumed-plan rollovers tied to specific bank combinations.

Building a clean population for academic studies of holding-company formation

Researchers in banking and financial economics use the dataset as a pre-filtered sample of General Instruction G formations, since the S-4EF/S-4 POS path is otherwise hard to extract from generic S-4 data. The metadata.json fields (filedAt, effectivenessDate, entities[].cik, sic, stateOfIncorporation) seed event-study panels, while the prospectus narrative and reorganization description support hand-coding of charter conversions, dual-bank-system migrations, and post-formation capital actions.

Pipeline development for EDGAR parsers and exhibit classifiers

Data and ML teams use the bundled accession folders to develop SGML-wrapper strippers, exhibit-type classifiers keyed on <TYPE> and documentFormatFiles[].type, and section extractors for facing pages, deregistration recitals, signatures, and undertakings. The dataset's stable schema and well-defined edge cases (ASCII-in-SGML legacy filings, unresolved GRAPHIC image references, multi-registrant filings) make it practical for end-to-end test runs and for fine-tuning retrieval models on holding-company-formation language.

Supervisory cross-referencing against holding-company applications

Analysts at federal banking supervisory agencies match S-4 POS records to internal holding-company formation and change-in-control applications using CIK, file number, and effectivenessDate. Prospectus disclosures on regulatory approvals, ownership thresholds, and pro forma capital structure corroborate facts in supervisory records and feed pipeline statistics on bank and thrift formation activity.

Dataset Access

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

This endpoint returns the dataset's metadata, including its name, description, last update timestamp, earliest sample date, total record and size counts, covered form types (S-4 POS), container format (ZIP), and included file types (TXT, JSON, HTML, PDF). It also returns the full dataset download URL and the list of individual container files with per-container metadata such as size, record count, last updated timestamp, and a download URL. This endpoint does not require an API key. Polling it on a regular schedule lets you detect which containers were modified during the latest refresh run and download only those that changed.

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-69d8-a2af-93081476cc1c",
        

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

          4
            "name": "Form S-4 POS Files Dataset",
        

          5
            "updatedAt": "2026-04-15T12:29:08.436Z",
        

          6
            "earliestSampleDate": "1994-01-01",
        

          7
            "totalRecords": 826,
        

          8
            "totalSize": 14677764,
        

          9
            "formTypes": ["S-4 POS"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

          14
                "downloadUrl": "https://api.sec-api.io/datasets/form-s4-pos-files/2026/2026-03.zip",
        

          15
                "key": "2026/2026-03.zip",
        

          16
                "size": 412853,
        

          17
                "records": 4,
        

          18
                "updatedAt": "2026-04-15T12:29:08.436Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

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

The complete dataset is distributed as a single ZIP archive that bundles every monthly container from January 1994 onward. Because the corpus is small, a single download is usually the most convenient way to retrieve all filings at once. This endpoint requires an API key.

Download Single Container: https://api.sec-api.io/datasets/form-s4-pos-files/2026/2026-03.zip?token=YOUR_API_KEY

Containers are organized by year and month, so you can fetch one monthly archive instead of the full dataset. Each container ZIP holds the metadata file and submission documents (TXT, JSON, HTML, PDF; image files excluded) for the filings published in that month. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form S-4 POS — post-effective amendments to Form S-4 registration statements under the Securities Act of 1933, predominantly amendments to Form S-4EF (the auto-effective variant under General Instruction G of Form S-4 used to register securities issued in connection with the formation of a bank or savings-and-loan holding company).

What does one record in this dataset represent?

One record is a single EDGAR accession — one Form S-4 POS submission filed by one registrant (with any co-registrants) on one date, identified by its 18-digit accession number. On disk it is a folder containing a metadata.json file plus every text-bearing document from the original EDGAR submission, each preserved inside its EDGAR SGML <DOCUMENT> wrapper.

Who is required to file Form S-4 POS?

The filer is always the issuer whose securities are registered on the underlying S-4 or S-4EF registration statement. The filer base is dominated by newly formed bank and savings-and-loan holding companies registering shares under General Instruction G, plus other S-4 registrants amending after their registration statements have already become effective; target companies, target shareholders, advisors, and exchange agents do not file.

When is a Form S-4 POS triggered?

There is no fixed deadline; filing is event-driven. Common triggers are the Section 10(a)(3) updating obligation when prospectus financials go stale, an Item 512(a) fundamental change after effectiveness, deregistration of unsold securities after a closed transaction, name changes or successor-registrant continuations, and carry-forward of un-issued S-4 shares onto Form S-8 for assumed employee plans.

What time period does the dataset cover?

The dataset begins on January 1, 1994 — aligned with the rollout of mandatory EDGAR filing under Regulation S-T — and runs through the present. Paper post-effective amendments to Form S-4 from before the EDGAR mandate are not in scope.

What file format is the dataset distributed in?

The dataset is distributed as ZIP containers partitioned by year and month at paths of the form form-s4-pos-files/<YYYY>/<YYYY-MM>.zip. Inside each accession folder the included file types are TXT, JSON, HTML, and PDF; image and graphic exhibits are intentionally excluded but are still enumerated in metadata.json -> documentFormatFiles[] with their documentUrl for on-demand retrieval.

How does this dataset differ from Form S-4/A?

S-4/A is the pre-effective amendment, filed during SEC staff review before the registration statement goes effective; S-4 POS is the post-effective amendment, filed after the registration statement is already effective. The choice between them turns solely on whether the registration is effective, and the two datasets answer different questions: S-4/A for review-cycle analysis, S-4 POS for after-effectiveness maintenance such as stale-financials refreshes, deregistration of unsold shares, and carry-forward to Form S-8.