Form F-4MEF Files Dataset

The Form F-4MEF Files Dataset is a complete corpus of EDGAR submissions filed under form type F-4MEF — short-form registration statements filed by foreign private issuers under Securities Act Rule 462(b) to register up to an additional 20 percent of the securities for an offering already covered by an effective Form F-4 business-combination registration. Each record is one EDGAR submission, identified by its 18-digit accession number, materialized as a per-accession folder that bundles a structured metadata.json header with every filer-submitted document of the original submission (excluding image attachments). The dataset's coverage begins on March 1, 2001 — the earliest in-scope F-4MEF submission captured in EDGAR after Rule 462(b) was adopted in 1996 — and extends to the present. Records are distributed as monthly ZIP containers organized by year, with TXT, JSON, and HTML as the only file types found inside.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset captures the full population of F-4MEF filings transmitted to EDGAR. Form F-4MEF, the "More Effective Filing" variant of Form F-4, is a fee-payment-only top-up registration that becomes effective immediately upon filing because Rule 462(b) (17 CFR 230.462(b)) lets it incorporate by reference the prospectus, financial statements, risk factors, and substantive disclosures already on file in the parent F-4. Form F-4 itself, prescribed by 17 CFR 239.34, is the registration form used by foreign private issuers for securities issued in business combination transactions — mergers, exchange offers, consolidations, amalgamations, and similar reorganizations.

Because an F-4MEF tops up an already-effective F-4, the filing itself is intentionally minimal: a cover page, a calculation-of-registration-fee table, an explicit Rule 462(b) declaration, an incorporation-by-reference statement, signatures, and a small set of legally required exhibits — predominantly EX-5 legal opinions and EX-23 auditor and expert consents. The dataset is published as monthly ZIP containers organized by year, with one ZIP per calendar month that has at least one F-4MEF filing. Inside each archive, every accession is materialized as a folder whose name is the accession number with dashes stripped, holding a metadata.json header alongside the unwrapped document files.

Content Structure of a Single Record

What one record represents

A record in the Form F-4MEF Files Dataset is a single EDGAR submission filed under form type F-4MEF, identified by its 18-digit accession number. Inside the dataset, the record materializes as one per-accession folder that bundles a structured metadata.json header together with every filer-submitted document of the original submission, except image attachments. The folder is the atomic unit of the dataset: it captures the complete registration statement as transmitted to EDGAR, comprising the short F-4MEF cover document and its accompanying exhibits (typically legal opinions and auditor or expert consents).

Folder layout of a single record

Inside each monthly ZIP archive, every accession is materialized as a folder whose name is the accession number with dashes stripped — for example, 0000943763-04-000002 becomes 000094376304000002. All filer-submitted documents sit flat inside that folder alongside metadata.json; there is no nested exhibit subdirectory and no separate prospectus directory. A typical accession folder layout is:

          1
          000094376304000002/
        

          2
            metadata.json              (structured submission header)
        

          3
            <primary>.txt              (sequence 1, the F-4MEF document)
        

          4
            <consent-1>.txt            (EX-23 consent)
        

          5
            <consent-2>.txt            (EX-23 consent)
        

          6
            <opinion-1>.txt            (EX-5 legal opinion)
        

          7
            <opinion-2>.txt            (EX-5 legal opinion)
        

          8
            ...
        

Filenames are filer-chosen and not standardized. The canonical mapping from a file to its exhibit role is given by the matching documentFormatFiles[] entry in metadata.json, not by filename convention.

Structure of metadata.json

metadata.json is the structured representation of the EDGAR submission header for the accession. It carries the identifying, classification, and document-inventory fields needed to interpret the rest of the folder.

Top-level fields include:

• formType — the form code, "F-4MEF".
• accessionNo — the canonical EDGAR accession number with dashes (e.g. "0000943763-04-000002").
• filedAt — ISO-8601 timestamp with timezone offset for the moment of acceptance.
• description — a human-readable form description, typically "Form F-4MEF - Registration statement to add securities to prior Form F-4 registration [Rule 462(b)]".
• linkToFilingDetails, linkToTxt, linkToHtml, linkToXbrl — canonical SEC.gov URLs pointing to the EDGAR filing-index page, the complete SGML submission .txt, the HTML index, and any XBRL package. For F-4MEF, linkToXbrl is normally empty.
• id — a hex hash serving as a stable internal record identifier.

The documentFormatFiles array is an ordered inventory of every document in the submission. Each entry contains:

• sequence — EDGAR sequence number as a string ("1", "2", ...; the trailing entry that points to the full SGML submission text uses a blank value).
• size — byte length as a string.
• documentUrl — SEC.gov URL of the individual document.
• description — the filer-supplied label, e.g. "REGISTRATION OF ADDITIONAL SHARES", "EXHIBIT 5", or "EXHIBIT 23(III)".
• type — the document-type tag ("F-4MEF", "EX-5", "EX-23", etc.).

The list always ends with a synthetic entry that points at the full SGML submission .txt (its filename matches the accession number). That complete-submission file is referenced in metadata.json but is not duplicated inside the per-accession folder; the dataset stores only the individual unwrapped documents.

The entities array enumerates the parties on the filing — for an F-4MEF this is normally a single filer entity. Each entity carries:

• act — the Securities Act under which the filing is made ("33" for the Securities Act of 1933).
• cik — the 10-digit zero-padded Central Index Key of the registrant.
• fileNo — the SEC file number, which on an F-4MEF is the same 333- series number assigned to the parent F-4 registration (e.g. "333-111817").
• companyName — registrant name with role suffix, e.g. "GENTERRA INC (Filer)".
• type — the role/form code in the entity context ("F-4MEF").
• sic — SIC industry code with descriptive name.
• filmNo — the EDGAR film number assigned at acceptance.

A dataFiles array lists structured-data attachments such as XBRL packages. For F-4MEF this array is normally empty, consistent with the form's status as a short fee-payment registration that contains no fresh financial statements.

The primary registration document

The sequence-1 document is the F-4MEF registration statement itself, delivered as a plain-text file wrapped in the EDGAR SGML document envelope. The wrapper takes the form:

          1
          <DOCUMENT>
        

          2
          <TYPE>F-4MEF
        

          3
          <SEQUENCE>1
        

          4
          <FILENAME>...
        

          5
          <DESCRIPTION>REGISTRATION OF ADDITIONAL SHARES
        

          6
          <TEXT>
        

          7
          ... document body ...
        

          8
          </TEXT>
        

          9
          </DOCUMENT>
        

Inside <TEXT>, the body is a compact cover filing that typically contains, in order:

• A header block stating "AS FILED WITH THE SECURITIES AND EXCHANGE COMMISSION ON [date]", the new registration number assigned to the F-4MEF, "SECURITIES AND EXCHANGE COMMISSION / WASHINGTON, D.C. 20549", and "FORM F-4MEF / REGISTRATION STATEMENT UNDER THE SECURITIES ACT OF 1933".
• Identification of the registrant: exact legal name, jurisdiction of incorporation or organization, primary SIC code, IRS Employer Identification Number (or local equivalent for non-U.S. filers), principal executive office address, and the name and address of the registrant's agent for service of process in the United States.
• A Rule 462(b) statement (the explicit "[X] Check the appropriate box: This Form is filed pursuant to Rule 462(b) under the Securities Act"), together with the registration number and effective date of the prior Form F-4 whose offering this filing tops up. This establishes the legal basis for immediate effectiveness and identifies the offering whose 20-percent overlay the F-4MEF creates.
• A "CALCULATION OF REGISTRATION FEE" table rendered with SGML <TABLE>, <CAPTION>, <S>, and <C> markup, listing the title of each class of securities, the additional amount being registered, the proposed maximum offering price per unit, the proposed maximum aggregate offering price, and the registration fee. Because the form may register at most 20 percent more securities than the parent F-4, the share counts and fees are characteristically modest.
• An incorporation-by-reference clause that pulls in the prospectus, financial statements, risk factors, and other substantive disclosures of the prior F-4. The F-4MEF therefore relies on the parent registration for nearly all narrative content.
• Signature blocks for the registrant, the principal executive officer, the principal financial officer, the controller or principal accounting officer, and the directors, frequently signed under powers of attorney established in the parent F-4.

By design, the primary document does not contain a fresh prospectus or restated financial statements; the substantive disclosure remains in the parent F-4.

Exhibits

Exhibits are stored as additional documents inside the same flat accession folder, each wrapped in its own EDGAR SGML <DOCUMENT> envelope (<TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, <TEXT> block). For F-4MEF, two exhibit families recur:

• EX-5 — Legal opinion on validity of the securities. Counsel for the registrant opines that the additional shares to be issued — typically in connection with the underlying business combination, exchange offer, or amalgamation — will be duly authorized, validly issued, fully paid, and non-assessable upon issuance. The opinion concludes with consent to its inclusion as an exhibit and to the reference to counsel under "Legal Matters" in the prospectus. Because the registrant is a foreign private issuer, EX-5 opinions on F-4MEFs are frequently delivered in pairs: one from U.S. counsel and one from counsel qualified in the registrant's home jurisdiction (covering the matters of foreign corporate law that U.S. counsel cannot opine on).
• EX-23 — Auditor and expert consents. Independent auditors, valuation firms, and other experts whose reports or opinions are incorporated by reference into the registration consent to that incorporation and to being named in the registration statement. A single F-4MEF may carry several EX-23 documents — one per consenting expert (e.g. independent or chartered accountants, an outside valuation firm, foreign counsel acting as experts on local law).

Other Form F-4 exhibit categories (underwriting agreements, plans of acquisition, charter and bylaw documents, tax opinions, fairness opinions, voting agreements, etc.) are normally already on file with the parent F-4 and are not re-exhibited on the F-4MEF, since the MEF filing piggybacks on the prior registration. The exhibit set on an F-4MEF is therefore generally limited to the items that legally must accompany a Rule 462(b) top-up — predominantly EX-5 and EX-23 — although issuer-specific variation is possible.

Included content

Each record includes:

• The structured metadata.json header, with submission metadata, entity information, and the full document inventory.
• Every filer-submitted document of the submission, each as a .txt file containing the original SGML <DOCUMENT> envelope around its <TEXT> body. This covers the F-4MEF primary registration document and any attached exhibits (typically EX-5 and EX-23).

Excluded or separate content

The following are not part of the per-accession folder:

• Image files. Signature scans, logos, and any other graphic attachments that accompanied the original EDGAR submission are excluded from the dataset. The records contain only textual document payloads and the JSON header.
• The concatenated full SGML submission .txt. The submission-wide text file (named after the accession number, e.g. 0000943763-04-000002.txt) is referenced from metadata.json via linkToTxt and listed as the trailing documentFormatFiles[] entry, but it is not duplicated as a stored file in the folder. The individual unwrapped document files collectively reconstitute the same content.
• The parent F-4 registration statement. The F-4MEF incorporates the prior F-4 by reference but does not bundle it. Reconstructing the substantive offering disclosure requires retrieving the F-4 separately, using the file number cross-reference in metadata.json (entities[].fileNo) and the prior registration number cited in the primary document.
• Any subsequently filed amendments. Post-effective amendments are filed under their own form codes (such as Form F-4/A or F-4MEF/A) and appear in their own datasets, not under F-4MEF. The F-4MEF itself is, by virtue of Rule 462(b), effective on filing and is rarely amended.

Format and historical notes

Form F-4MEF was introduced in 1996 alongside Rule 462(b) and has remained structurally stable. Several format characteristics deserve note:

• Plain-text / SGML envelope dominance. The file-types found in the dataset are TXT, JSON, and HTML. In practice, virtually all filer-submitted F-4MEF documents are transmitted as plain ASCII text inside the EDGAR SGML <DOCUMENT>/<TEXT> envelope, while metadata.json is the only JSON file. HTML rendering of an F-4MEF, where it occurs, follows the same envelope convention with HTML markup placed inside the <TEXT> block.
• No inline XBRL. F-4MEF filings sit outside the inline XBRL regime: they are short fee-payment registrations that introduce no new financial statements of their own, so the XBRL data lives with the parent F-4 (or its incorporated periodic reports). The dataFiles array in metadata.json is normally empty and linkToXbrl is typically blank.
• Stability of required content. Because Rule 462(b) tightly constrains what an F-4MEF may do — register up to 20 percent more securities, become effective immediately upon filing, and rely on incorporation by reference — the required content of the primary document (cover, calculation-of-fee table, Rule 462(b) declaration, incorporation by reference, signatures) and the typical exhibit set (EX-5, EX-23) have not changed materially over the dataset's coverage period. The fee-rate values inside the calculation table change as the SEC's fee schedule is reset annually, but the table's structure does not.

Interpretation and extraction notes

• Incorporation by reference is load-bearing. Reading an F-4MEF in isolation gives only the fee-payment skeleton. The prior F-4 registration number — carried both in the primary document text and indirectly via entities[].fileNo in metadata.json — is the key to retrieving the substantive offering content. The new registration number assigned to the F-4MEF itself appears in the cover header and is distinct from the parent F-4 file number.
• Sequence numbers identify document roles. The authoritative mapping between a .txt file and its exhibit type is the documentFormatFiles[] array, joined on documentUrl or matched by sequence. Filenames are filer-chosen and may not reflect the exhibit type.
• The SGML envelope must be stripped for clean text extraction. Each document file begins with <DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, and <TEXT> lines and ends with </TEXT> and </DOCUMENT>. The substantive content lives between the <TEXT> and </TEXT> markers. The fee-calculation table inside the primary document uses SGML <TABLE>/<CAPTION>/<S>/<C> markup that requires column-aware parsing rather than naive line-based text extraction.
• Multiple opinions and consents are routine. Because the registrant is a foreign private issuer, EX-5 opinions frequently appear in pairs (U.S. counsel plus home-jurisdiction counsel), and EX-23 consents may include several experts. A single accession can therefore have several documents that share the same type value and are distinguished only by description, sequence, and filename.
• Distinguish the F-4MEF record from the parent F-4 record. The dataset stores only the F-4MEF submission; the parent F-4 (and any prospectus supplements, post-effective amendments, or 424 prospectuses associated with it) lives in its own form-type datasets and must be joined on file number to assemble the full offering record.

Who Files or Publishes This Dataset, and When

Each record is a single Form F-4MEF submission to EDGAR by a foreign private issuer that already has an effective Form F-4 covering securities issued in a business combination, and that needs to register a small additional tranche of the same class immediately before the offering closes. The filing is a Rule 462(b) abbreviated registration statement that incorporates the prior F-4 by reference and becomes effective the moment it is filed.

Who files

The filer is always the foreign private issuer registrant itself (the issuer of the securities being delivered as merger or exchange consideration). It is never the target, financial advisor, or counsel, even though those parties appear throughout the filing.

To file an F-4MEF, the registrant must:

• Qualify as a foreign private issuer under Rule 405 (Securities Act) and Rule 3b-4 (Exchange Act).
• Have a Form F-4 already declared effective by the Commission for the same business combination.
• Be registering the same class of securities covered by that prior F-4, in connection with the same offering.

F-4MEF inherits the F-4 eligibility universe exactly. Domestic issuers in equivalent situations use S-4MEF; non-business-combination offerings by FPIs use Form F-1MEF or Form F-3MEF.

What triggers the filing

A Form F-4MEF can be filed only when all of the following are true:

1. The registrant's original Form F-4 for the same offering has been declared effective.
2. At or near pricing or closing, the registrant determines the F-4 registered an insufficient amount of securities for the actual issuance.
3. The additional securities, combined with the dollar amount of the same class already registered on the original F-4, do not exceed 20 percent of the maximum aggregate offering price shown on that F-4's "Calculation of Registration Fee" table. This cap is the core quantitative limit of Securities Act Rule 462(b) (17 CFR 230.462(b)).
4. The F-4MEF is filed after the original F-4's effective date and on or before the additional securities are first sold or issued in the business combination.

The trigger is transaction-mechanical, not periodic and not Exchange Act event-driven. A given F-4 produces zero or one F-4MEF; the 20 percent cap is measured in aggregate against the original F-4, so multiple F-4MEFs against the same parent are not contemplated.

Effectiveness and fee mechanics

• Automatic effectiveness on filing. Under Rule 462(b), the F-4MEF becomes effective immediately on filing, with no staff review and no acceleration order. This is the entire operational point of the form: it lets registrants calibrate the registered amount at pricing.
• Outer time limit. Filing must precede the issuance of the additional securities at closing.
• Inner time limit. Filing cannot occur before the underlying F-4 is effective.
• Registration fee. The issuer pays the registration fee on the incremental amount only, computed on the F-4MEF's own fee table under Rule 457, and either remitted at filing or drawn from a prepaid account under Rule 111. Rule 462(b) requires confirmation of fee payment as a precondition of effectiveness.
• Hard 20 percent cap. If additional shares would exceed 20 percent of the original F-4's maximum aggregate offering price, F-4MEF is unavailable; the registrant must file a new Form F-4 (or use a post-effective amendment), reverting to standard staff review.

The F-4MEF itself is a thin instrument: it identifies the registrant, references the prior F-4 by file number and effective date, states the additional shares and dollar amount, computes the incremental fee, and incorporates the prior F-4 by reference. Typical exhibits are a refreshed legality opinion and any consents required for the additional securities.

Important distinctions

• F-4MEF vs. F-4 amendment. A pre-effective amendment to an F-4 is not an F-4MEF. A post-effective amendment updates disclosure on an effective F-4. F-4MEF is a separate registration statement whose sole function is to add registered amount under Rule 462(b).
• F-4MEF vs. S-4MEF. Choice turns entirely on foreign-private-issuer status. Domestic registrants use Form S-4 (17 CFR 239.25) and S-4MEF.
• F-4MEF vs. other MEF variants. Each parent form has its own Rule 462(b) counterpart (Form S-1MEF, Form S-3MEF, S-11MEF, F-1MEF, F-3MEF, S-4MEF, F-4MEF). F-4MEF is uniquely tied to FPI business combinations.
• Out of scope. FPIs that are not currently registering a business combination on F-4 do not appear here. Canadian issuers using the MJDS Form F-80 for business combinations follow a separate regime and do not file F-4MEF.
• Target companies. Targets are not co-filers, even though their securityholders receive the registered securities.
• Amendments to F-4MEF. Rare; typically limited to fee or cover-page corrections, since the form is effective on filing.

Earliest records

The F-4MEF mechanism derives from Rule 462(b), adopted in 1996 (Release No. 33-7300) as part of registration-process simplification, so no F-4MEF filing predates that rulemaking. Because EDGAR electronic filing was already mandated for the relevant FPI registration statements by then, there is no meaningful paper population. This dataset accordingly begins on March 1, 2001, the earliest in-scope F-4MEF submission captured in EDGAR.

How This Dataset Differs From Similar Datasets or Filings

Form F-4MEF occupies a narrow niche: a registration statement filed by a foreign private issuer under Rule 462(b) to add up to 20 percent more securities to an already-effective Form F-4 business-combination registration. The closest comparison points are the parent F-4, the domestic S-4 family, the other Rule 462(b) "MEF" variants, F-4/A amendments, and the 424B prospectus series. Each overlaps on one axis — same transaction, same issuer, or same registration mechanic — but diverges sharply on another.

Form F-4 (parent registration statement)

F-4 is the underlying registration statement for foreign-private-issuer business combinations under 17 CFR 239.34: mergers, exchange offers, consolidations, and similar transactions. Every F-4MEF presupposes an effective F-4 and functions as a stub that incorporates that F-4 by reference.

The substantive content lives in the F-4: full prospectus, transaction description, risk factors, pro forma financials, fairness opinions, tax discussion, and exhibits. F-4MEF typically contains only a cover page, fee calculation for the additional securities, a reference to the prior F-4, a signature block, and any required legal opinions or consents. F-4 datasets are document-rich and per-deal; F-4MEF datasets are short, formulaic, and signal late-stage upsizing rather than describing the deal itself.

Form S-4 (domestic counterpart)

S-4 covers the same business-combination transactions as F-4 but for domestic registrants. The disclosure regime is parallel; the filer populations are disjoint. F-4MEF inherits this boundary and cannot be used by a domestic issuer regardless of transaction type. S-4 is structurally similar but not a substitute when the research question concerns cross-border or foreign-issuer M&A.

Form S-4MEF (domestic Rule 462(b) counterpart)

S-4MEF is the closest analogue to F-4MEF: identical 462(b) mechanic, identical 20 percent ceiling, identical stub structure, identical business-combination context — only the issuer status differs. The two datasets are mirror images split by foreign vs. domestic registrant. S-4MEF volumes are materially higher, reflecting the relative size of domestic M&A registration activity. Researchers studying last-minute upsizing across all M&A registrations would combine them; researchers focused on cross-border foreign-issuer deals would use F-4MEF alone.

Form F-1MEF and Form S-1MEF (other Rule 462(b) variants)

F-1MEF and S-1MEF apply the same 462(b) mechanic — immediate effectiveness, 20 percent cap, filed before pricing — but to primary capital-raising offerings rather than business combinations. F-1MEF tops up an Form F-1 (foreign private issuer); S-1MEF tops up an Form S-1 (domestic). They share F-4MEF's legal plumbing but contain no merger consideration, no target disclosure, and no fairness opinion. Useful for studying 462(b) usage across offering types; not interchangeable with F-4MEF on transaction content.

The broader Rule 462 family

There is no generic "Form 462B" filing in EDGAR practice. Rule 462(b) is implemented through form-specific MEF variants (F-4MEF, S-4MEF, F-1MEF, S-1MEF, F-3MEF, S-3MEF, S-11MEF, and so on), each tied to its parent registration form. F-4MEF is the narrow slice covering foreign-private-issuer business combinations. Other MEF datasets share the legal mechanic but cover different offering structures and filer populations.

Form 424B prospectus filings

Form 424B (and its sub-variants 424B1–424B8) is the Rule 424(b) prospectus series — final prospectuses, supplements, and pricing information for already-effective registrations. Both 424B and F-4MEF appear late in the offering timeline and often coexist around the same deal, which invites confusion. The legal nature is different: F-4MEF is a registration statement that takes effect immediately on filing and adds incremental registered securities; 424B is a disclosure filing that registers no additional securities. If an issuer needs more registered shares, only an MEF (or a full new registration) supplies them; a 424B cannot. If an issuer only needs to update disclosure for already-registered securities, 424B is the correct vehicle.

Form F-4/A (amendments)

F-4/A is a pre- or post-effectiveness amendment to an F-4, used to address staff comments, update financials, revise deal terms, or register additional securities through full amendment. F-4/A and F-4MEF can both expand a registered offering, but they differ in scope and process. F-4/A is substantive, may trigger staff review, and can restate large portions of the prospectus. F-4MEF is mechanical, effective on filing, capped at 20 percent of the original registration, limited to fee-and-share-count content, and does not reopen the underlying disclosure. Issuers choose F-4MEF over F-4/A specifically when they need a small capacity increase quickly — typically on or just before pricing day — without staff review.

Key differences at a glance

• F-4 vs. F-4MEF: full disclosure document vs. stub that incorporates by reference.
• S-4 vs. F-4: domestic vs. foreign-private-issuer filer population, otherwise parallel.
• S-4MEF vs. F-4MEF: identical mechanic, opposite filer status, much higher S-4MEF volume.
• F-1MEF / S-1MEF vs. F-4MEF: capital-raising offerings vs. business combinations.
• 424B vs. F-4MEF: prospectus disclosure (no new securities registered) vs. incremental registration.
• F-4/A vs. F-4MEF: substantive amendment with possible staff review vs. mechanical 462(b) top-up.

Boundary summary

F-4MEF is defined by the conjunction of four constraints that do not co-occur in any other SEC filing type:

1. foreign private issuer status,
2. business-combination transaction,
3. Rule 462(b) immediate-effectiveness mechanic,
4. 20 percent incremental-registration ceiling.

Drop the foreign-issuer constraint and the comparable dataset becomes S-4MEF. Drop the business-combination constraint and it becomes F-1MEF or F-3MEF. Drop the 462(b) mechanic and it becomes F-4 or F-4/A. Drop the registration nature entirely and the nearest filing is a 424B prospectus.

In practice, F-4MEF filings are short and almost entirely incorporate by reference the substantive disclosures of the parent F-4. The dataset's research value is therefore in the signal it carries — that a specific cross-border merger or exchange offer required last-minute additional registered capacity, by whom, when, and how much — rather than in the text of the filings themselves. For deal content, F-4MEF should be paired with the parent F-4, any F-4/A amendments, and the related 424B prospectuses on the same accession lineage; on its own, it is best read as a marker of late-stage upsizing.

Who Uses This Dataset

Form F-4MEF is a narrow, high-signal filing, and its users are concentrated in cross-border M&A execution, registration-fee accounting, deal tracking, and regulatory monitoring. Different roles pull different parts of the record: the registrant CIK, accession number, prior F-4 reference, additional securities count, registration fee table, and exhibits (counsel and tax opinions, auditor consents).

Cross-border M&A and securities counsel

Deal counsel advising on cross-border mergers, exchange offers, and consolidations use the dataset to draft new F-4MEF filings against precedent. They pull the prior F-4 reference, the 5.1 and 8.1 opinions, 23.x consents, and the cover-page fee table to confirm the additional amount stays within the 20 percent cap and that the fee was computed consistently with the original F-4. Output: precedent libraries, exhibit checklists, and pre-filing review memos.

Capital markets bankers

ECM and M&A execution bankers read F-4MEF filings as a signal that a stock-for-stock or cash-and-stock cross-border deal is sized at or near its upper bound. They use the additional securities count plus the prior F-4 to derive total share consideration, and the filing date to map distance to close. Output: deal-status updates and post-mortem analysis of final-vs-initial registration size.

Event-driven and merger-arbitrage analysts

Sell-side and buy-side analysts use the additional share count and aggregate offering price, tied to the prior F-4 via the accession number reference, to recompute exchange ratios, dilution, and pro-forma share counts. Output: spread models, pro-forma EPS, and confirmation that final-share-count closing conditions are satisfied.

Deal-data vendors and league-table compilers

M&A database and league-table teams ingest F-4MEF as a structured signal for stock-funded cross-border deals. They key on registrant CIK, accession number, filing date, prior F-4 reference, additional securities registered, and aggregate offering price. Output: backfilled historical deal records from 2001 onward, normalized cross-border deal sizes, and credit attribution where F-4MEF is the last registration event before close.

Issuer-side regulatory and compliance staff

In-house securities counsel and SEC-reporting specialists at foreign private issuers (and U.S. acquirers of them) review prior F-4MEF filings to model their own. They check exhibit lists, fee-calculation methodology, and timing relative to F-4 effectiveness. Output: filing checklists, pre-filing legal review, and transfer-agent coordination on additional shares.

Fee and registration specialists

EDGAR filing-fee staff reconcile Rule 462(b) fees against fees paid on the underlying F-4. They focus on the calculation-of-registration-fee table, the proposed maximum aggregate offering price, the applicable fee rate, and any offset or carry-forward references. Output: fee-budget reconciliation, audit support, and QC on cover-page fee math.

M&A diligence and integration teams

Diligence teams advising acquirers, lenders, or successors use the dataset retroactively to confirm a target's prior consideration shares were properly registered. They focus on the additional registered amount, counsel opinions, and consents tied to historical accession numbers. Output: diligence memos and capitalization-history reconstruction.

Academic researchers

Finance, accounting, and securities-law researchers use F-4MEF as a clean sample of late-stage, upsized cross-border registrations. They link registrant CIK to other EDGAR datasets, use the additional offering amount for sizing, and align filing date with deal-close data to study how often issuers hit the 20 percent ceiling and how Rule 462(b) use varies by jurisdiction. Output: empirical papers and policy analysis.

Risk and compliance monitors at trading firms

Surveillance teams at broker-dealers and proprietary trading firms feed registrant CIK, prior F-4 linkage, and filing date into watch-list and information-barrier systems to flag positions around late-stage deal activity. Output: automated alerts, restricted-list updates, and post-trade review for securities tied to active cross-border combinations.

Data engineers and RAG developers

Filings-warehouse engineers and retrieval-augmented system developers ingest the JSON metadata, accession-number identifiers, and HTML/TXT exhibit bodies as a complete, low-volume corpus covering a distinctive transaction type. Output: indexing pipelines, exhibit classifiers, fee-table extractors, and Q&A systems for deal lawyers and capital markets professionals.

Specific Use Cases

The use cases below exploit the F-4MEF signal and the specific fields in metadata.json, the SGML-wrapped primary document, and the EX-5 / EX-23 exhibit set.

Demand-overshoot detection in cross-border business combinations

Build a pipeline that joins each F-4MEF accession to its parent F-4 by entities[].fileNo (the shared 333- series number) and parses the calculation-of-registration-fee table from the sequence-1 document to extract the additional shares registered and proposed maximum aggregate offering price. Express the increment as a percentage of the parent F-4's originally registered amount and flag accessions clustered near the 20 percent ceiling as cases where deal demand or final exchange ratios outran initial sizing. The output is a per-deal "ceiling-hit" panel useful for deal post-mortems and exchange-offer subscription analysis.

League-table refinement for stock-funded cross-border M&A

Ingest accessionNo, filedAt, registrant cik, companyName, sic, and the additional aggregate offering price from the fee table to backfill or correct M&A databases for cross-border, stock-funded transactions. Because an F-4MEF is the last registration event before pricing in many deals, treating it as the authoritative final-size record (rather than the initial F-4) corrects league-table credit and consideration values. The result feeds normalized historical deal records covering March 2001 to present.

Fee-table reconciliation for capital markets administrators

Extract the SGML <TABLE>/<S>/<C> fee-calculation grid from the primary document, recompute fee = aggregate offering price x applicable Rule 457 fee rate for filedAt, and reconcile it against the fee paid and any offset or carry-forward references back to the parent F-4. Discrepancies surface arithmetic errors, stale fee-rate usage across fiscal-year boundaries, or misapplied 457 offsets. The workflow supports filer-fee QC, billing reconciliation, and audit trails for in-house registration teams.

Exhibit-template benchmarking for cross-border M&A counsel

Use the documentFormatFiles[] inventory to enumerate every EX-5 and EX-23 attached to F-4MEFs in a given jurisdiction, then strip the SGML envelope from each .txt to assemble a clause-level corpus of validity opinions (typically paired U.S. and home-country counsel) and auditor / expert consents. Counsel drafting a new F-4MEF can benchmark home-jurisdiction opinion language (Cayman, Bermuda, England and Wales, Israel, Canada, Netherlands, etc.) against precedent and confirm a complete consent set per the parent F-4's named experts. The output is a precedent library keyed by registrant CIK, jurisdiction (from the primary document's "jurisdiction of incorporation" header), and exhibit type.

Surveillance watchlist triggers around late-stage deal activity

Stream new F-4MEF accessions on filedAt, key on registrant cik and the prior F-4 file number, and push the pair into broker-dealer information-barrier and restricted-list systems. Because an F-4MEF is filed before close of business on the parent F-4's effectiveness day, its appearance is a tight late-stage timing signal that the underlying cross-border combination is at or near pricing. The output is automated restricted-list updates and post-trade review tickets for securities tied to active foreign-issuer combinations.

Empirical research on Rule 462(b) usage by foreign issuers

Treat the full corpus as a sample frame of late-stage upsizing events for cross-border deals. Link cik to Compustat / company datasets, use the additional offering amount and ceiling-utilization ratio as dependent variables, and stratify by registrant jurisdiction, SIC, and deal year to study which issuers and transaction types most often need 462(b) capacity. Pairing F-4MEF records with their F-4 and 424B siblings on file number reconstructs the full offering lineage for event studies on cross-border merger pricing and dilution.

Dataset Access

Dataset Index JSON API: https://api.sec-api.io/datasets/form-f4mef-files.json This endpoint returns dataset-level metadata such as the name, description, last updated timestamp, earliest sample date, total records and size, form types covered, container format, and content file types. It also lists every monthly ZIP container with its key, size, record count, updated timestamp, and signed download URL. Use this index to monitor which containers were refreshed in the most recent run and to decide which containers to download incrementally. This endpoint does not require an API key.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-6a64-a158-2c264006dec1",
        

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

          4
            "name": "Form F-4MEF Files Dataset",
        

          5
            "updatedAt": "2026-04-16T08:50:09.402Z",
        

          6
            "earliestSampleDate": "2001-03-01",
        

          7
            "totalRecords": 89,
        

          8
            "totalSize": 258008,
        

          9
            "formTypes": ["F-4MEF"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

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

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

          16
                "size": 13818,
        

          17
                "records": 2,
        

          18
                "updatedAt": "2026-04-16T08:50:09.402Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

Download Entire Dataset: https://api.sec-api.io/datasets/form-f4mef-files.zip?token=YOUR_API_KEY Downloads the full dataset, covering all Form F-4MEF filings from March 2001 to present, as a single ZIP archive containing every monthly container. This endpoint requires an SEC API key.

Download Single Container: https://api.sec-api.io/datasets/form-f4mef-files/2026/2026-03.zip?token=YOUR_API_KEY Downloads one individual monthly container instead of the full dataset. Containers are organized by year and month, and each ZIP holds accession-numbered subfolders containing a metadata.json file alongside SGML-wrapped TXT exhibits from the original EDGAR submission. This endpoint requires an SEC API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form F-4MEF, a short-form registration statement filed under Securities Act Rule 462(b) (17 CFR 230.462(b)) by foreign private issuers to register up to an additional 20 percent of the securities for an offering already covered by an effective Form F-4 business-combination registration.

What does one record in this dataset represent?

One record is a single EDGAR submission filed under form type F-4MEF, identified by its 18-digit accession number. The record materializes as a per-accession folder containing a structured metadata.json header alongside every filer-submitted document of the original submission (excluding image attachments) — typically the F-4MEF primary registration document plus EX-5 legal opinions and EX-23 auditor and expert consents.

Who is required to file Form F-4MEF?

The filer is always the foreign private issuer registrant itself — the issuer of the securities being delivered as merger or exchange consideration. The registrant must qualify as a foreign private issuer under Rule 405 and Rule 3b-4, must already have an effective Form F-4 covering the same business combination, and must be registering the same class of securities covered by that prior F-4. Targets, financial advisors, and counsel are not co-filers.

What time period does the dataset cover?

Coverage begins on March 1, 2001 — the earliest in-scope F-4MEF submission captured in EDGAR — and extends to the present. Rule 462(b) was adopted in 1996, and EDGAR electronic filing was already mandated for the relevant FPI registration statements by then, so there is no meaningful paper-only population predating the dataset.

What file formats are inside the dataset?

The dataset is distributed as monthly ZIP containers organized by year. Inside each container, every accession is a flat folder holding a metadata.json header plus filer-submitted documents as .txt files wrapped in the original EDGAR SGML <DOCUMENT> envelope. The file types found in the dataset are TXT, JSON, and HTML.

How does Form F-4MEF differ from Form S-4MEF?

S-4MEF is the closest analogue to F-4MEF: identical Rule 462(b) mechanic, identical 20 percent ceiling, identical stub structure, identical business-combination context — only the issuer status differs. F-4MEF is filed by foreign private issuers; S-4MEF is filed by domestic registrants. The two datasets are mirror images split by foreign vs. domestic registrant, and S-4MEF volumes are materially higher.

Why is the F-4MEF filing itself so short?

By design. Rule 462(b) lets the F-4MEF incorporate by reference the prospectus, financial statements, risk factors, and other substantive disclosures already on file in the parent F-4. The F-4MEF filing therefore contains only a cover page, a calculation-of-registration-fee table, an explicit Rule 462(b) declaration, an incorporation-by-reference statement, signatures, and a small set of legally required exhibits (predominantly EX-5 and EX-23). Reconstructing the substantive offering disclosure requires retrieving the parent F-4 separately, using the file number cross-reference in metadata.json.