The Form F-4 POS Files dataset is a complete archive of EDGAR submissions of form type F-4 POS — post-effective amendments to Form F-4 (and, predominantly, Form F-4EF) registration statements filed by foreign private issuers under the Securities Act of 1933 in connection with cross-border business combinations such as mergers, exchange offers, and asset acquisitions. Each record is a single F-4 POS submission identified by its 18-digit EDGAR accession number, packaged as a folder containing a structured metadata.json header plus the filing's documents preserved in their original SGML <DOCUMENT> envelopes. The dataset begins with samples from February 2002 and is maintained through the present, with new submissions added as foreign private issuers file post-effective amendments to keep their effective F-4/F-4EF registrations current, reflect material changes, file omitted exhibits, or deregister unsold securities at the close of an exchange offer. Records are partitioned into monthly ZIP containers (YYYY/YYYY-MM.zip) and distributed in HTML, TXT, and JSON file formats.
Programmatically retrieve the full list of dataset archive files, download URLs and dataset metadata.
Dataset Index JSON API
Download the entire dataset as a single archive file.
Download Entire Dataset:
Download a single container file (e.g. monthly archive) from the dataset.
Download Single Container:
The dataset captures the entire population of EDGAR-accepted Form F-4 POS filings, the post-effective amendment mechanism for Form F-4 and Form F-4EF registration statements. Form F-4 is the registration statement used by foreign private issuers to register securities issued in business combination transactions — mergers, consolidations, asset acquisitions, exchange offers, and similar transactions in which securities of a foreign issuer are offered to U.S. holders of a target's equity. Form F-4EF is the variant that becomes effective automatically upon filing where the registrant qualifies as a well-known seasoned issuer (WKSI) and meets the criteria of Rule 462(e). A Form F-4 POS filing is the post-effective amendment to such an already-effective F-4 or F-4EF, made under Section 8(c) of the Securities Act and Rules 462(d) and 413 of Regulation C.
The post-effective amendment is functionally distinct from the original registration statement. It is filed after effectiveness, typically to:
A given F-4 POS may therefore range from a brief deregistration notice with a single signature block to a full reissue of the prospectus running to hundreds of pages. Every F-4 POS retains the 333- series file number of the parent F-4/F-4EF, tying every amendment back to the same continuous registration. The dataset is partitioned temporally into monthly ZIP containers grouped under year prefixes, with the underlying file types being HTML for form bodies and most exhibits, TXT for the complete-submission aggregate where included and any plaintext exhibits, and JSON for per-record metadata headers. Image binaries (GIF, JPG, PNG) are excluded; everything else from the original submission is retained.
One record in the Form F-4 POS Files dataset is a single EDGAR submission of form type F-4 POS. The record unit is the entire filing as transmitted to EDGAR, identified by its 18-digit accession number. Each record is materialized as a folder named after the accession number with the dashes stripped (e.g. 000119312508008559), grouped into monthly ZIP partitions of the form YYYY/YYYY-MM.zip. Inside the folder are two layers of content: a metadata.json header derived from the EDGAR submission header, and the filing's documents preserved with their original SGML <DOCUMENT> envelopes intact.
A record is a directory whose contents fall into two layers:
metadata.json — the structured filing header, always present, derived from the EDGAR SGML <SEC-HEADER> block. It enumerates identifiers, timestamps, the document inventory, and every legal entity attached to the submission.<DOCUMENT> SGML wrapper before the embedded HTML or plaintext payload.Partitioning is purely temporal — monthly ZIPs grouped under year prefixes. Each accession folder is self-contained: there is no cross-record state, no shared exhibits, and no joining required to reconstruct one submission.
metadata.jsonThe metadata file is a single JSON object that mirrors the EDGAR submission header. Its top-level keys carry:
formType — the EDGAR form code, fixed at "F-4 POS" for every record.accessionNo — the canonical hyphenated accession number (e.g. "0001193125-08-008559"), unique across all of EDGAR.filedAt — ISO-8601 timestamp with timezone offset capturing the EDGAR acceptance time (e.g. "2008-01-18T10:54:52-05:00"), generally in U.S. Eastern Time.description — the EDGAR human-readable form description, "Form F-4 POS - Registration of securities, foreign private issuers, business combinations, post effective".linkToFilingDetails — stable URL to the primary document on www.sec.gov.linkToTxt — URL to the complete-submission .txt (the SGML aggregate with all documents inlined).linkToHtml — URL to the EDGAR filing-index page that lists all documents in the submission.linkToXbrl — URL to XBRL data when present; for F-4 POS records this is generally empty because post-effective amendments to F-4 registration statements typically do not republish inline XBRL financial-statement tagging.documentFormatFiles — array describing every document attached to the submission. Each element carries sequence (ordinal in the submission), size, documentUrl, description, and type. The first element is the F-4 POS document itself (type: "F-4 POS"); the last element is typically the complete-submission .txt. Intermediate elements are the form's exhibits.dataFiles — array of structured-data files (XBRL instance, schema, calculation/label/presentation linkbases) attached to the filing. For F-4 POS records this is typically empty.entities — array describing the legal entities associated with the submission. Each entity object carries the registrant identifiers parsed from the SGML header:
companyName with the EDGAR role suffixed in parentheses, e.g. "AIR FRANCE-KLM /FI (Filer)".cik — ten-digit zero-padded Central Index Key.type — entity-level form code, again "F-4 POS".act — the Securities Act under which the filing is made; "33" for the Securities Act of 1933.fileNo — SEC file number of the parent registration statement (a 333- prefix indicates a 1933 Act registration).filmNo — the EDGAR film number assigned at acceptance.sic — four-digit Standard Industrial Classification code with description appended (e.g. "4512 Air Transportation, Scheduled").stateOfIncorporation — EDGAR two-character state or country code; for foreign private issuers this is typically a country code such as "I0" (France), "M2" (Japan), "X0" (Netherlands), "L2" (Bermuda), "K3" (Cayman Islands).fiscalYearEnd — month-and-day of the fiscal year-end in "MMDD" form.irsNo — IRS employer identification number, often "000000000" for foreign filers without a U.S. EIN.For transactions involving multiple parties — for instance, an issuer plus a co-registrant guarantor of debt securities, or a parent and a subsidiary issuer — the entities array carries one element per role.
id — internal dataset identifier (32-character hex).The primary document is the post-effective amendment itself, almost always delivered as an HTML file (.htm / .html) with an EDGAR SGML wrapper preceding the HTML payload:
1
<DOCUMENT>
2
<TYPE>F-4 POS
3
<SEQUENCE>1
4
<FILENAME>df4pos.htm
5
<DESCRIPTION>POST-EFFECTIVE AMENDMENT NO. 1 TO FORM F-4
6
<TEXT>
7
<HTML>...</HTML>
8
</TEXT>
9
</DOCUMENT>
The wrapper fields (TYPE, SEQUENCE, FILENAME, DESCRIPTION) duplicate the corresponding fields in metadata.json["documentFormatFiles"], so each file can always be matched back to its metadata entry.
The HTML body follows the structure mandated by Form F-4 and General Instruction G to that form. Depending on whether the amendment is a full reissue of the prospectus or a narrow housekeeping amendment, the body may contain, in roughly this order:
For the narrow deregistration variety of F-4 POS, the body is short: an explanatory paragraph stating that the warrant exercise period or exchange-offer expiration has passed, a statement of the number of unsold shares or warrants being deregistered, the Item 22 undertakings, and the signatures.
When the F-4 POS files new exhibits — rather than only incorporating prior ones by reference — each exhibit appears as an additional sequenced document, also wrapped in its own <DOCUMENT> envelope with a distinct TYPE tag. The exhibit-type vocabulary on Form F-4 follows Item 21 of Form F-4 cross-referenced to Item 601 of Regulation S-K. Exhibit types appearing in F-4 POS submissions include:
Exhibits filed as part of the post-effective amendment supersede or supplement the corresponding exhibits of the original F-4 / F-4EF.
.txtThe documentFormatFiles array consistently lists the complete-submission .txt file as the final element. This file is the SGML container holding the full submission with all documents and the <SEC-HEADER> block inlined; it is the canonical EDGAR archival form. Its documentUrl always points to the public SEC URL even when the file itself is not physically materialized inside the per-record folder.
Each record physically contains:
metadata.json header (always present).The metadata's documentUrl fields preserve direct links back to SEC.gov for any document a consumer wishes to retrieve in canonical form.
<IMG> tags whose src attributes point to image filenames not present locally; visual reproduction requires retrieving them from EDGAR..txt is referenced by URL in the metadata but is not necessarily materialized in the folder; its content can be reconstructed from the per-document files plus the SGML header information already captured in metadata.json.Form F-4 and its post-effective amendment mechanism have been substantially stable since the form's modern adoption under Securities Act Release No. 6578 in the mid-1980s. The Item structure of Form F-4 — Items 1 through 22, divided across Part I (prospectus content) and Part II (information not required in the prospectus) — has not undergone wholesale renumbering during the dataset's coverage window beginning February 2002. Substantive disclosure content evolves chiefly through changes to the cross-referenced rules (Regulation S-K Item 503 risk factors, Item 402 executive compensation, Item 1300 mining-property disclosure, etc.) rather than through changes to F-4's own Item list.
Two regulatory developments during the coverage window are visible in record content:
The file types found in the dataset are HTML, TXT, and JSON: HTML for the form body and most exhibits, TXT for the complete-submission aggregate where included and for any plaintext exhibits, and JSON for the per-record metadata header. F-4 POS documents are transmitted as HTML wrapped in EDGAR's SGML <DOCUMENT> envelope, with the per-document HTML payload as the body. Although the SEC's inline XBRL mandates extend to certain financial-statement disclosures within Form F-4, post-effective amendments typically do not re-tag those statements, and the linkToXbrl field is correspondingly empty for the great majority of records in this dataset.
fileNo (the 333- series number) but a distinct accessionNo. Reconstructing the full life cycle of a registration requires grouping records by entities[].fileNo and ordering by filedAt. Matching on companyName is unreliable due to formatting drift and corporate-name changes between filings.entities array preserves the full set; consumers should not assume one registrant per filing.<HTML> element. Tools that parse the file as pure HTML must skip past the wrapper lines up to <TEXT> or treat the wrapper as plaintext metadata. Because the wrapper fields duplicate fields already structured in metadata.json["documentFormatFiles"], the JSON is generally the preferable programmatic source.entities array does not always carry the U.S. agent as a distinct entity, so the signatures page is the authoritative source for that detail.Each record is one EDGAR submission of form type F-4 POS. The filer is the registrant on the parent F-4/F-4EF — a foreign private issuer that previously registered securities to be issued in a business combination (merger, consolidation, asset acquisition, or exchange offer) involving U.S. holders. The amendment is filed under the same 333- SEC file number as the parent. The filer is not a new disclosing party introduced at the post-effective stage; it is the original registrant continuing its obligation to keep the effective registration accurate, current, and properly closed out.
Eligibility to use Form F-4 (and therefore F-4 POS) is limited to foreign private issuers as defined in Rule 405 (Securities Act) and Rule 3b-4 (Exchange Act). Within that population, F-4 POS filers fall into a few recurring categories:
Most F-4 POS filings in this dataset trace back to F-4EF parents, the automatically effective variant available only to well-known seasoned issuers (WKSIs) under Rule 405 and Rule 462(e). Non-WKSI foreign issuers typically file plain F-4 and amend pre-effectiveness via F-4/A.
F-4 POS is event-driven, not periodic. The recurring triggers are:
A single parent F-4/F-4EF can generate a sequence of F-4 POS amendments — substantive updates during the offering and a final deregistration at close — all sharing the parent's 333- file number.
There is no fixed calendar deadline. Timing is driven by the underlying event:
The filedAt timestamp reflects EDGAR acceptance (U.S. Eastern Time). Unlike Form 20-F, there is no periodic due date.
Form F-4 POS sits in a tightly clustered family of Securities Act registration filings for business combinations, with parallel foreign (F-series) and domestic (S-series) tracks and several amendment mechanisms (pre-effective, post-effective, immediate-effective). The most useful comparisons are to its direct parent (F-4EF), its sibling amendment forms in the F-4 lineage, the domestic S-4 POS mirror, the generic POS AM, and the 424B prospectus-delivery route that handles changes too minor to require an amendment.
F-4EF is the immediately effective F-4 variant available to well-known seasoned issuers under Securities Act Rule 462, used to register securities issued in business combinations. F-4 POS exists solely to amend an already-effective F-4EF: F-4EF establishes effectiveness, F-4 POS maintains or updates it. Any F-4 POS is meaningless without the corresponding F-4EF (and often the original F-4) on the same registration file number.
The standalone, full-review version of the registration. F-4 contains the complete prospectus, business descriptions of both parties, financial statements, transaction terms, fairness opinions, and tax disclosures. F-4 POS is not a standalone registration; it presupposes effectiveness and only updates portions of the live filing. F-4 filings are also far more numerous and substantially larger than the narrow F-4 POS population.
F-4/A is filed before effectiveness, typically responding to SEC staff comments during review. F-4 POS is filed after effectiveness, when the registration is already being used to issue securities. F-4/A is part of the iterative review cycle; F-4 POS reacts to post-effectiveness developments such as updated financials, revised deal terms, or extensions of the offering period.
F-4MEF is the Rule 462(b) "additional shares" registration that immediately registers more securities of the same class on the same terms as a pending or recently effective F-4. It expands registered capacity; F-4 POS amends disclosure within an existing registration without (typically) adding shares. Both rely on streamlined effectiveness, but they answer different needs: capacity expansion vs. disclosure update.
Mechanically and procedurally identical to F-4 POS. The only meaningful distinctions are the issuer population (U.S. domestic registrant vs. foreign private issuer) and the underlying disclosure regime carried through from the parent form (Regulation S-K/S-X vs. Form 20-F-style foreign-issuer disclosure, IFRS or reconciled financials, home-country governance). For complete coverage of post-effective business-combination amendments, Form S-4 POS and F-4 POS together form the full pair.
POS AM is the catch-all post-effective amendment used for S-1, S-3, S-11, F-1, F-3, and other registrations that lack a form-specific POS variant. F-4 POS is the form-specific equivalent for the F-4EF lineage. They serve the same legal role under Section 8 and Rule 462 but are not interchangeable: F-4 POS is restricted to F-4EF parents and tied to a specific business combination, while POS AM typically attaches to shelf or continuous offerings. A complete view of a foreign issuer's post-effective amendments requires both.
424B filings deliver the final or supplemental prospectus under Rule 424 after effectiveness. They handle routine pricing supplements, takedown prospectuses, and minor disclosure updates without amending the registration itself. F-4 POS is an actual amendment to the registration statement and is required when the change is material enough that Rule 424 supplementation is insufficient (fundamental changes to the offering, certain selling-securityholder additions, substantive prospectus revisions). Small pricing or terms updates flow through 424B1-424B8; fundamental changes flow through F-4 POS.
RW withdraws a registration statement under Rule 477. F-4 POS and RW move in opposite directions on the registration lifecycle: F-4 POS continues and updates an effective registration; RW terminates one. An abandoned business combination would be addressed through RW or a deregistering POS reducing the registered amount, not through an ordinary F-4 POS update.
F-4 POS occupies a narrow slot: post-effective amendments to F-4EF business-combination registrations filed by foreign private issuers. It differs from F-4 by being an amendment rather than an origination; from F-4/A by occurring after rather than before effectiveness; from F-4MEF by updating disclosure rather than adding shares; from S-4 POS only by issuer nationality and disclosure regime; from POS AM by being form-specific rather than generic; from 424B by amending the registration itself rather than delivering a prospectus; and from RW by sustaining rather than withdrawing the registration. To reconstruct a full foreign-issuer deal record, F-4 POS must be paired with the underlying F-4/F-4EF and any associated F-4/A, F-4MEF, and 424B filings on the same registration file number.
The Form F-4 POS Files dataset serves a narrow set of practitioners who work on cross-border business combination deals, the disclosure that supports them, and the trading and operational activity they generate.
Securities counsel advising foreign private issuers use the dataset as a precedent library for post-effective amendments. They focus on the explanatory note, revised description of securities, updated risk factors, amended exchange-ratio or consideration language, and refiled legality, tax, and fairness opinions in the exhibit index. The output is drafting precedent and judgments on when a POS suffices versus a sticker supplement or a fresh F-4.
In-house securities teams at non-U.S. registrants benchmark amendment practice: what triggered prior POS filings, how peers handle incorporation by reference of recent 20-F or 6-K updates, and how dual-language or home-country cross-references are framed. The output is internal disclosure controls, refresh calendars, and explanatory-note templates.
Deal teams study how amendments handle revised consideration tables, updated pro forma financials, election procedures, and proration rules. They focus on the amended offer sections, comparison of shareholder rights, and any refiled fairness opinions. The dataset informs structuring advice, timing of registration refreshes, and views on whether material changes can be absorbed by POS or require recirculation.
Analysts trading deal spreads on cross-border exchange offers treat each POS as a material update to a live transaction. They focus on changes to the exchange ratio, collars, walk-away rights, regulatory conditions, expiration extensions, minimum tender thresholds, and tax disclosure. The dataset supports backtests linking amendment types to spread movements and templates for what a POS-driven event looks like in comparable deals.
Tax advisors structuring Section 367 and Section 368 reorganizations compare how peers describe U.S. federal income tax consequences in post-effective amendments. They focus on the tax considerations section, tax opinion exhibits, PFIC and CFC discussions, and amendments responding to changes in tax law. The output is tax disclosure drafting and benchmarking of inversion and treaty risk language.
Operational teams administering cross-border tender and exchange offers track amended election forms, letters of transmittal, instructions to nominees, expiration mechanics, and revised proration or odd-lot provisions in the exhibits. The dataset supports system updates, tender processing readiness, and coordination with transfer agents on settlement timing.
Advisors restructuring debt or equity of foreign issuers consult POS filings that respond to shifting market conditions, revised participation thresholds, or amended consent terms. They focus on revised indenture exhibits, amended consideration tables, and fallback risk factors to inform amend-versus-withdraw decisions.
Compliance officers at firms acting as dealer-managers or soliciting dealers monitor POS filings to confirm the prospectus being distributed is current. They focus on amended delivery mechanics, jurisdictional and selling restrictions, and dealer-manager exhibits. The dataset supports supervisory procedures and tracking of which version of the registration statement is operative.
Data teams building cross-border M&A databases ingest POS filings to enrich event timelines tied to parent F-4EF registrations. They use the metadata file for accession numbers, CIKs, dates, and form types, and parse the HTML and TXT documents for amendment narratives, exhibit lists, and incorporated-document references. The output is linked POS-to-F-4EF event chains and signals on amendment frequency and cause.
Researchers studying foreign private issuer access to U.S. capital markets, the WKSI regime, and automatic shelf registration in business combinations use the corpus to categorize amendment triggers, measure intervals between effectiveness and consummation, and study completion patterns for cross-border deals.
Teams building retrieval systems for cross-border deal research use the HTML and TXT documents as embedding content and the JSON metadata for structured filtering by filer, date, and form. The narrow corpus supports fine-tuning and evaluation of models that must distinguish original registration content from post-effective changes.
The use cases below tie directly to fields in metadata.json, the explanatory note, the exhibit index, and the calculation-of-registration-fee table.
Group records by entities[].fileNo (the 333- series number) and order by filedAt to assemble the full chain of post-effective amendments tied to a parent F-4 / F-4EF. The output is a per-deal event timeline showing each amendment, its purpose, and the elapsed time between effectiveness and consummation, suitable for feeding into M&A databases or completion-rate studies.
Parse the explanatory note at the top of each primary F-4 POS document to bucket filings into deregistration of unsold shares, Section 10(a)(3) financial refresh, revised business-combination terms, successor-registrant substitution, or omitted-exhibit filing. The output is a labeled corpus that securities counsel and academics use to benchmark when a POS suffices versus when a fresh F-4 or sticker supplement is required.
Extract the calculation-of-registration-fee table from short-form deregistration POS filings to capture the title of class, amount being deregistered, and any fee offset against the original F-4 / F-4EF. The output is a per-deal measure of unsold securities at the close of an exchange offer, useful for take-up analysis on cross-border tender offers and for risk arbitrage post-mortems.
Index the EX-5, EX-8, EX-23, EX-24, and EX-99 exhibits filed within F-4 POS submissions to construct a searchable corpus of legality opinions, tax opinions, accountant consents, powers of attorney, and revised letters of transmittal. Cross-border M&A counsel and tax advisors retrieve these by registrant, jurisdiction (stateOfIncorporation), and SIC code to source drafting precedent for new deals.
Watch new F-4 POS arrivals in the monthly partitions and diff the amended offer terms (exchange ratio, collars, expiration date, minimum tender, proration) against the prior effective prospectus. The output is a real-time signal feed that risk arbitrage desks and dealer-manager compliance teams use to confirm which prospectus version is operative and to reprice deal spreads on cross-border exchange offers.
Use the HTML and TXT document bodies as embedding content and metadata.json for structured filters on filer CIK, fiscal-year-end, country of incorporation, and filedAt. The narrow, well-bounded corpus supports RAG systems and evaluation sets that must distinguish original F-4 disclosure from post-effective changes when answering questions about a specific transaction.
The Form F-4 POS Files dataset is available through three access methods: a JSON API for dataset metadata, a full archive download, and individual container downloads.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-f4-pos-files.json
This endpoint returns dataset metadata including name, description, last updated timestamp, earliest sample date (2002-02-01), total records and total size, form types covered (F-4 POS), the container format (ZIP), and the included file types (HTML, TXT, JSON). It also lists every available container with its size, record count, last updated timestamp, and direct download URL. Use this endpoint to monitor which containers were refreshed in the most recent update run and decide which files to download incrementally. No API key is required to access this endpoint.
1
{
2
"datasetId": "1f13365b-9ae0-6a50-a824-f842c40afda6",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-f4-pos-files.zip",
4
"name": "Form F-4 POS Files Dataset",
5
"updatedAt": "2026-04-16T08:44:39.294Z",
6
"earliestSampleDate": "2002-02-01",
7
"totalRecords": 106,
8
"totalSize": 5038637,
9
"formTypes": ["F-4 POS"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["HTML", "TXT", "JSON"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-f4-pos-files/2026/2026-03.zip",
15
"key": "2026/2026-03.zip",
16
"size": 412874,
17
"records": 4,
18
"updatedAt": "2026-04-16T08:44:39.294Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-f4-pos-files.zip?token=YOUR_API_KEY
Downloads the complete dataset as a single ZIP archive containing every Form F-4 POS filing from February 2002 to present. This endpoint requires a valid API key.
Download Single Container: https://api.sec-api.io/datasets/form-f4-pos-files/2026/2026-03.zip?token=YOUR_API_KEY
Downloads one monthly container archive instead of the entire dataset. Replace the year and month path segments to target a specific period. This endpoint requires a valid API key.
The dataset covers EDGAR form type F-4 POS — post-effective amendments to Form F-4 and Form F-4EF registration statements filed by foreign private issuers under Section 8(c) of the Securities Act of 1933 and Rules 462(d) and 413 of Regulation C. Each filing carries the same 333- SEC file number as its parent F-4/F-4EF registration.
One record is a single EDGAR submission of form type F-4 POS, identified by its 18-digit accession number and materialized as a folder (e.g. 000119312508008559) containing a metadata.json header plus the filing's documents — the primary post-effective amendment narrative and any sequenced exhibits — preserved in their original SGML <DOCUMENT> envelopes.
The filer is a foreign private issuer (as defined in Rule 405 of the Securities Act and Rule 3b-4 of the Exchange Act) that previously registered securities on Form F-4 or F-4EF for issuance in a business combination — typically a foreign acquirer offering equity, ADRs, or debt as consideration in a merger or exchange offer involving U.S. holders. Co-registrant guarantors and successor registrants under Rule 414 may also appear as filers.
F-4 POS is event-driven, not periodic. Records are added whenever a foreign private issuer files a post-effective amendment — most commonly to deregister unsold securities at the close of an exchange offer, to refresh financial statements under Section 10(a)(3), to reflect material changes to deal terms, or to file omitted exhibits such as legality, tax, or accountant-consent opinions. New monthly ZIP partitions are populated as filings arrive.
The earliest sample in the dataset is dated February 1, 2002, and coverage continues through the present. Records are partitioned into monthly ZIP containers under year prefixes (YYYY/YYYY-MM.zip), allowing both full-archive and incremental retrieval.
Each record contains JSON (the metadata.json header), HTML (the primary F-4 POS document and most exhibits, wrapped in EDGAR's SGML <DOCUMENT> envelope), and TXT (the complete-submission aggregate where included and any plaintext exhibits). Image binaries (GIF, JPG, PNG) referenced by the HTML are excluded from the per-record folder. XBRL tagging is generally absent because post-effective F-4 amendments typically do not republish inline XBRL financial-statement data.
Form F-4 is the initial standalone registration statement and Form F-4EF is its automatically effective WKSI variant under Rule 462(e); both establish effectiveness. Form F-4 POS, by contrast, is the post-effective amendment that maintains, updates, or closes out an already-effective F-4 or F-4EF — it presupposes effectiveness and shares the same 333- file number as its parent. To reconstruct a complete cross-border deal record, F-4 POS records should be joined to the corresponding F-4/F-4EF, F-4/A, F-4MEF, and 424B filings on the same registration file number.
F-4 POS and S-4 POS are mechanically identical post-effective amendments; the dividing line is the issuer population — F-4 POS is for foreign private issuers, S-4 POS is for U.S. domestic registrants. POS AM is the generic post-effective amendment code used for S-1, S-3, F-1, F-3, F-10, and similar shelf or continuous-offering registrations that lack a form-specific POS variant; F-4 POS is the form-specific equivalent restricted to F-4/F-4EF parents tied to a specific business combination.