The Form F-8 POS Files dataset is a record-level archive of every EDGAR-filed Form F-8 POS submission — post-effective amendments to Form F-8 registration statements used by Canadian issuers under the U.S.-Canada Multijurisdictional Disclosure System (MJDS) to register securities offered as consideration in cross-border exchange offers, amalgamations, plans of arrangement, and other business combinations under 17 CFR 239.38. One record corresponds to a single EDGAR submission of F-8 POS, identified by accession number, packaged as a flat accession folder containing a canonical metadata.json header alongside the primary F-8 POS document and its exhibits in their original EDGAR SGML envelopes. Filers are exclusively the Canadian issuer-registrants of the underlying F-8 — a narrow class of MJDS-eligible foreign private issuers — and filings are event-driven post-effective amendments rather than periodic reports. The dataset spans May 2002 to the present, is distributed as ZIP containers organized by year and month, and carries HTML, TXT, and JSON file types.
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:
This dataset packages every Form F-8 POS submission filed through EDGAR since the post-ASCII era of mandatory electronic filing for MJDS forms began. Form F-8 itself is a short-form U.S. registration statement available exclusively to issuers incorporated or organized under the laws of Canada or any Canadian province or territory, used to register securities issuable in connection with an exchange offer or business combination — typically a statutory amalgamation, plan of arrangement, takeover bid, or merger requiring a shareholder vote — under 17 CFR 239.38 and the Multijurisdictional Disclosure System. Form F-8 POS is the post-effective amendment vehicle for such a registration: it updates a previously effective F-8 to reflect new prospectus disclosure, revised offer mechanics, additional auditor consents, registration-fee true-ups, additional securities, or other material changes that arise after effectiveness but before the offer or transaction closes.
The form leans heavily on the MJDS premise of home-jurisdiction disclosure: rather than reproducing a U.S.-style prospectus, the F-8 incorporates by reference the Canadian management proxy circular, takeover-bid circular, or directors' circular and supplements it with a thin U.S. wrapper carrying registrant identification, undertakings, indemnification disclosure, signatures, and the exhibits required by the form's General Instructions. Form F-8 POS is a low-volume event filing — the dataset spans May 2002 to the present — so monthly ZIP containers commonly hold a single accession folder, a small handful, or none at all. The dataset preserves the complete EDGAR submission as filed, with the exception of image files (logos, signature scans, cover-page graphics) that are stripped from the package while their inventory rows remain visible in metadata.json. Container format is ZIP and file types are HTML, TXT, and JSON.
One record is a single EDGAR submission of Form F-8 POS — one post-effective amendment to a previously declared-effective Form F-8 registration statement — uniquely identified by an accession number. On disk, the record is an accession-numbered folder whose name is the eighteen-digit accession with dashes removed (for example 000104746903017039 for accession 0001047469-03-017039). The folder is flat: a metadata.json header sits at its root, and every non-image document of the original EDGAR submission is preserved as a sibling file. Records are grouped under year-level directories into year-month ZIP containers (for example 2003-05.zip), with no nesting beneath the accession.
A record carries an outer dataset-packaging layer and an inner SEC-filing layer.
The packaging layer consists of the accession folder, the canonical metadata.json header, and one EDGAR-SGML-wrapped document file per submission component. Every non-metadata file in the dataset — whether .htm or .txt — is delivered exactly as it sat inside the original EDGAR complete-submission text bundle, preserving the SGML document envelope <DOCUMENT><TYPE>...<SEQUENCE>...<FILENAME>...<DESCRIPTION>...<TEXT> ... </TEXT></DOCUMENT>. The <TEXT> payload is full HTML when the source file is .htm and plain ASCII when the source file is .txt. Image files (typically .jpg and .gif graphics referenced by the HTML — issuer logos, signature scans, cover-page artwork) are intentionally stripped from the dataset; their entries still appear in the metadata.json documentFormatFiles array as GRAPHIC rows with original sizes and EDGAR URLs, but the bytes are not packaged. The file types found in the dataset are therefore HTML, TXT, and JSON — JSON exclusively as the per-record metadata.json header.
The SEC-filing layer consists of the primary F-8 POS document plus its exhibits. The primary document carries the cover page, the registration-fee calculation table, Parts I/II/III of the form, and the signature blocks. Exhibits sit alongside as separate documents in the accession folder, each numbered according to the F-8 exhibit table.
metadata.json is the canonical, machine-readable header for the filing and is always present, exactly once, at the root of the accession folder. Its keys describe both the EDGAR submission envelope and the per-document inventory:
formType — the literal string "F-8 POS".accessionNo — the dash-formatted accession number (e.g. "0001047469-03-017039"), which corresponds to the dash-stripped folder name.filedAt — the EDGAR acceptance timestamp in ISO 8601 with timezone offset (e.g. "2003-05-05T20:10:03-04:00").description — the human-readable form description, typically "Form F-8 POS - Registration statement for securities of certain Canadian issuers, post effective".linkToFilingDetails, linkToTxt, linkToHtml, linkToXbrl — back-links to the live EDGAR primary document, the complete-submission .txt bundle, the filing-index HTML page, and (where present) the XBRL instance. For F-8 POS, linkToXbrl is generally an empty string and dataFiles is an empty array.dataFiles — the structured-data exhibit inventory; empty for this form type.documentFormatFiles — the per-document inventory. Each entry carries sequence (EDGAR document ordinal), size (bytes), documentUrl (EDGAR archive URL), description (human label such as EXHIBIT 1.4 or EXHIBIT 4.7), and type (EDGAR document type such as F-8 POS, EX-1.4, EX-4.7, or GRAPHIC). The list enumerates every original component of the submission, including the stripped graphic files and a trailing synthetic entry pointing at the complete-submission text bundle.entities — an array of EDGAR entity blocks. For F-8 POS this ordinarily contains a single filer block. Each block carries companyName (with a parenthetical role suffix such as "(Filer)"), cik, fileNo (the 333-... registration-statement number being amended), irsNo (commonly "000000000" because the filer is a Canadian corporation without a U.S. EIN), act ("33" for the Securities Act of 1933), sic (industry code and label), fiscalYearEnd, filmNo, type ("F-8 POS"), and tickers (an array, frequently U.S. OTC pink-sheet symbols).id — the dataset's internal record identifier.Every document file inside the accession folder is one SGML-wrapped EDGAR submission segment. The opening lines name the EDGAR <TYPE> (form/exhibit type), the <SEQUENCE> ordinal that mirrors the documentFormatFiles entry, the original <FILENAME>, and a free-text <DESCRIPTION>; the <TEXT> block then holds either HTML or ASCII content until a closing </TEXT></DOCUMENT> pair. A typical auditor-consent exhibit opens with <DOCUMENT>, <TYPE>EX-4.7, <SEQUENCE>12, <FILENAME>a2110258zex-4_7.txt, <DESCRIPTION>EXHIBIT 4.7, <TEXT>, the consent letter text, and closes with </TEXT></DOCUMENT>. HTML exhibits use the same envelope but the payload is a complete HTML document (occasionally including <Page> page-break markers carried over from the original text-mode EDGAR conventions). Downstream consumers must strip this outer wrapper before HTML parsing and must not assume the wrapper is well-formed XML — it is SGML, and the inner header tags are unclosed in the EDGAR convention.
The primary document is conventionally named with the issuer's filing slug followed by a zf-8pos.htm suffix (for example a2110258zf-8pos.htm). Its internal structure follows the form's General Instructions in a fixed order.
The cover begins with the EDGAR filing-date stamp and the registration number being amended (Registration No. 333-104122), then the SEC banner, the explicit overprint Post-Effective Amendment No. <n> to FORM F-8 REGISTRATION STATEMENT UNDER THE SECURITIES ACT OF 1933, the registrant's exact legal name, the jurisdiction of incorporation (a Canadian province or "Canada"), the SIC code or codes, the IRS Employer Identification Number (commonly "Not Applicable" for a Canadian filer), the address and telephone number of the principal executive office in Canada, the name and address of the U.S. agent for service of process (often a U.S. subsidiary, satisfying the F-X requirement), and the name and address of U.S. counsel.
A tabular block titled "CALCULATION OF THE REGISTRATION FEE" enumerates each title of securities being registered, the amount to be registered, the proposed maximum offering price per unit, the proposed maximum aggregate offering price, and the registration fee. Post-effective amendments routinely show both the fee currently due and the amount previously paid, since the F-8 POS may add securities, true up valuations, or carry forward the fee from the original F-8.
Part I houses four short Items, almost all of which are satisfied by cross-reference to the Canadian home-jurisdiction document rather than by full U.S.-style narrative disclosure:
Part II carries the indemnification disclosure required by the form's instructions: a description of the registrant's by-law or board-resolution indemnification provisions for directors, officers, and controlling persons, the underlying Canadian corporate-statute basis (typically the Canada Business Corporations Act or a provincial counterpart), and the standard SEC public-policy paragraph stating that indemnification for Securities Act liabilities is, in the opinion of the Commission, against public policy and therefore unenforceable.
Part III contains two Items:
Two signature blocks close the primary document. The first is the registrant's signature, executed by an authorized officer in a Canadian city on a stated date, in the form /s/ <NAME> followed by the officer's title. The second is a directors-and-officers table listing each director and principal officer with title, date, and signature line. Most director signatures are typically executed by an attorney-in-fact under a power of attorney filed as an exhibit and are marked with an asterisk or similar indicator.
Exhibits are filed as siblings of the primary document, one EDGAR document per file, and follow the F-8 exhibit-numbering scheme. Filenames typically combine the issuer slug with zex-<n>_<m> and either .htm or .txt, mirroring the EDGAR <TYPE> value (for example a2110258zex-1_4.htm is EX-1.4). The convention used by F-8 / F-8 POS filings groups exhibits by purpose:
.txt.Not every F-8 POS filing carries every exhibit class. A post-effective amendment frequently re-files only those exhibits actually being updated, leaving the others as effective from the prior filing; consequently any given accession may contain only an EX-1.x cluster plus EX-4 consents, or only opinions, or only a re-issued circular.
The dataset record includes the full metadata.json header, the primary F-8 POS document with its cover page, fee table, Parts I/II/III, and signatures, every exhibit document of any EDGAR <TYPE> other than GRAPHIC, and the EDGAR SGML envelope around each document. Both .htm and .txt source forms are preserved exactly as filed, so HTML markup, embedded tables, and ASCII formatting (page breaks, <Page> markers, fixed-column layouts) survive intact.
Image files referenced by the HTML — typically the issuer's logo, signature scans, or cover-page graphics — are stripped from the ZIP. Their documentFormatFiles entries remain visible in metadata.json (as GRAPHIC rows with original sizes and EDGAR URLs), but the bytes are not packaged. The complete-submission .txt bundle is not redistributed inside the accession folder; metadata.json.linkToTxt points at it on EDGAR. The original Form F-8, the Form F-X consent to service of process, and any prior or subsequent post-effective amendments are separate accession numbers and are not included in this record — only the specific F-8 POS submission identified by accessionNo is.
Form F-8 POS is a narrow, low-volume form whose required content is fixed by 17 CFR 239.38 and the form's General Instructions, and the dataset spans from May 2002 to the present without material change in record anatomy. Across the full date range the cover-page elements, the calculation-of-registration-fee table, the three-part Item structure, the indemnification and undertakings disclosures, the F-X cross-reference, and the registrant-plus-directors signature blocks all appear in essentially the same order. Exhibit numbering continues to follow the EX-1.x / EX-2 / EX-3 / EX-4.x / EX-5 partition. Because the dataset begins in May 2002, all records sit in the post-ASCII era of EDGAR: primary documents and most exhibits are HTML wrapped in the EDGAR SGML envelope, while a minority of plain-language exhibits — auditor consents and short option-holder letters — arrive as .txt with the same envelope.
Several nuances matter when reading or extracting one record:
fileNo is the original registration's number, not the amendment's. The 333-... value carried in entities[].fileNo belongs to the underlying F-8; a single registration may produce several F-8 POS records over time, each with the same fileNo and a different accessionNo. The cover-page overprint always names the post-effective-amendment ordinal (Post-Effective Amendment No. 1, No. 2, and so on), and that ordinal is the authoritative version marker — filedAt alone is not sufficient because intervening filings under the same registration may have non-F-8-POS form types.irsNo = "000000000" and ticker arrays often consist of U.S. OTC pink-sheet symbols (for example five-letter XXXXF-style tickers) rather than primary Canadian listings. The absence of an NYSE/Nasdaq ticker does not imply an unlisted issuer.<TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>) inside the wrapper. The matching </TEXT></DOCUMENT> pair is reliable; the per-field opening tags are not.documentFormatFiles is the manifest of record. It is the source of truth for what the original submission contained, including the stripped graphic files. Diffing documentFormatFiles against the actual files in the folder is the cleanest way to detect what was excluded by the dataset rather than missing from the original filing.Form F-8 POS is filed by the original Form F-8 registrant: a Canadian issuer that previously registered securities with the SEC on Form F-8 and is now amending that registration after it has become effective. The "POS" suffix marks the filing as a post-effective amendment, distinguishing it from a pre-effective F-8/A.
Eligible filers are a narrow class of foreign private issuer under the Multijurisdictional Disclosure System (MJDS), adopted by the SEC in 1991 (Release No. 33-6902) and prescribed for Form F-8 by 17 CFR 239.38 under the Securities Act of 1933. To file on Form F-8 (and therefore on F-8 POS), an issuer must:
The filer of record is always the issuer-registrant whose securities are being registered. Targets, dissident shareholders, financial advisors, and Canadian counsel are not filers, even when their information appears inside the amended prospectus.
Issuers outside this universe (non-Canadian foreign private issuers, Canadian issuers that fail MJDS thresholds, or Canadian issuers using a different MJDS form) do not appear here. They register on Form F-1, F-3, F-4, S-1, S-3, S-4, F-7, F-9, F-10, or F-80, and their post-effective amendments carry the corresponding * POS designations.
F-8 POS filings are event-driven, not periodic. They occur after the underlying F-8 has been declared (or become) effective and only when a development requires the registration statement to be updated, corrected, or supplemented while still being relied upon for offers and sales.
The triggering legal hooks are:
Typical operative events that surface through these hooks include revised exchange ratios or cash components, extensions or condition waivers, restated or newly issued financial statements of the registrant or target, revised pro forma data, new or refreshed risk factors, amended exhibits (support, lock-up, voting, or definitive transaction agreements), supplemental tax and validity opinions, refreshed auditor consents, registration of additional securities under Rule 457, and corrections of material misstatements or omissions.
Because each F-8 supports a specific transaction, the F-8 POS population per registrant is small — typically one or two amendments tied to discrete events in a single deal — rather than the recurring cadence seen with shelf registrations on Form F-10 or S-3. Pre-EDGAR F-8 amendments existed on paper before mandatory electronic filing for MJDS forms was phased in by the early 2000s; the dataset begins with the May 2002 onset of consistent electronic filing.
F-8/A is pre-effective and F-8 POS is post-effective. Only the latter is in this dataset.Form F-8 POS occupies a narrow slot in the Securities Act system: a post-effective amendment to an already-effective Form F-8 registration, used by Canadian issuers in exchange offers or business combinations under MJDS. The most useful comparisons are to other filings in the same lineage (original F-8, F-8/A), the parallel MJDS forms (F-80/F-80 POS, F-10/F-10 POS), the non-MJDS deal-registration analogs (F-4 POS, Form S-4), and the procedural companion filing (F-X).
The parent registration under 17 CFR 239.38. The original F-8 contains the full first-time prospectus, complete risk factors, financial statements, and the full exhibit list. F-8 POS exists only as a post-effective update to that filing.
Use F-8 to identify which deals were registered; use F-8 POS to track post-effective updates, term changes, or extensions to those same deals.
Same parent form, opposite side of the effectiveness line.
Do not pool F-8/A and F-8 POS in time-series work: one captures pre-launch iteration, the other post-launch maintenance.
The other MJDS exchange-offer registration form. Transactional content is nearly identical to the F-8 family; the split is eligibility-driven by relative-size and shareholder-distribution thresholds.
For complete MJDS exchange-offer coverage, F-8 POS must be paired with F-80 POS; the form numbers are not interchangeable.
The MJDS general-registration form for Canadian issuers raising capital (underwritten offerings, debt, certain rights offerings).
Same MJDS framework, different transaction type. Exclude F-10 POS from any study of registered Canadian M&A.
The non-MJDS analog for foreign private issuers registering securities issued in mergers or exchange offers.
F-4 POS is the closest content analog to F-8 POS, but the disclosure regimes are not equivalent and the documents are not directly line-comparable.
The U.S.-domestic counterpart for mergers, exchange offers, and similar business combinations.
S-4-family filings vastly outnumber F-8-family filings. S-4 cannot stand in for F-8 POS when the question concerns MJDS mechanics or Canadian cross-border deals, and F-8 POS cannot represent overall North American exchange-offer volume.
Not a registration form but a procedural appointment of a U.S. agent for service of process, required of Canadian issuers using MJDS forms.
F-X is useful as a linkage table for identifying MJDS filers and their U.S. agents but is not a content substitute.
Form F-8 POS is defined by three simultaneous constraints: (1) post-effective rather than initial or pre-effective, (2) MJDS rather than general foreign-private-issuer or domestic, and (3) exchange-offer or business-combination only, not general offerings. Relax any one constraint and the dataset changes: dropping post-effective yields F-8 or F-8/A; dropping MJDS yields F-4 POS or S-4 amendments; dropping the deal-type limit yields F-10 POS. The dataset is small precisely because all three constraints bind at once. For broader coverage, pair F-8 POS with F-80 POS (full MJDS exchange-offer scope), the original F-8 filings (parent registrations), and F-X (procedural layer).
The user base for the Form F-8 POS Files Dataset is small but specialized, mirroring the narrow legal niche occupied by MJDS exchange-offer registrations.
Securities lawyers advising Canadian issuers on US-registered exchange offers are the primary readers. They use the dataset as a precedent bank: what triggered each amendment (revised exchange ratio, supplemental disclosure, refreshed financials, extended offer period), how the change was described on the facing page, and how the prospectus supplement was integrated. The cover page, explanatory note, exhibits index, legal opinion (Exhibit 5), and tax opinion (Exhibit 8) matter most. Output: precedent files, know-how memos on POS-versus-Rule 425 thresholds, and drafting checklists for live mandates. A subset focuses on MJDS mechanics specifically — wrapper language, incorporation by reference, Canadian receipts, and IFRS/auditor-consent refreshes.
Bankers structuring cross-border share exchanges mine the dataset for collar mechanics, fractional-share treatment, and election procedures. Arbitrage analysts track amendments to exchange ratios, minimum tender conditions, expiry dates, and withdrawal rights, since each directly moves the spread and close probability. Key fields: prospectus supplement narrative, fee table, updated pro formas. Output: deal models, structuring memos, and trade decisions.
Registration teams at Canadian issuers and dealer-managers use the dataset to manage their own POS workflows. They focus on metadata (CIK, accession, file number, filing date), Rule 457 fee-table mechanics, signature pages, powers of attorney, and exhibit completeness. Output: filing checklists and internal controls documenting that the amendment was filed correctly and on time.
Diligence lawyers reconstruct the disclosure record around prior cross-border combinations — predecessor entities, deal structure, updated risk factors and legal proceedings. Restructuring and litigation researchers use the same record in appraisal, oppression, fraudulent-transfer, and post-closing indemnity disputes, where what was disclosed and when becomes evidence in pleadings and expert reports.
Finance and law researchers use the filings as a clean population for studies of MJDS usage, cross-border capital-market integration, and announcement effects, focusing on filing dates, registrants, and amendment counts. Data engineers ingest the metadata and exhibit list to enrich proprietary deal tables, link POS records to parent F-8 filings and related Schedule 13D or 13D entries, and feed completion-probability models.
The Form F-8 POS corpus is narrow but high-value for a handful of concrete workflows tied to MJDS exchange-offer mechanics, post-effective amendment practice, and Canadian-issuer registration tracking.
Cross-border M&A counsel filter the dataset by the cover-page Post-Effective Amendment No. <n> overprint and the EX-1.x cluster to extract every amendment that updated offer mechanics — revised exchange ratios, extended expiry dates, new election forms, refreshed letters of transmittal. Pulling the primary zf-8pos.htm plus the EX-1.x letters of transmittal and election guides yields a precedent set keyed by trigger type. Output: a drafting checklist mapping amendment trigger to facing-page explanatory language and to the specific exhibit re-filed.
Arbitrage analysts join entities[].fileNo (the underlying 333-... registration) across multiple F-8 POS accessions to reconstruct the term-change history of a single live deal. The fee table, the EX-1.x letter of transmittal, and any re-filed circular (EX-2) carry the dated record of changes to consideration, minimum tender condition, expiry, and withdrawal rights. Output: a per-deal event log feeding spread and close-probability models.
Diligence and registration teams iterate the EX-4.x consent letters and EX-3 legal/tax opinions across every accession sharing a fileNo to verify which audit firms, Canadian counsel, and U.S. counsel signed off at each amendment. Because EX-4.x consents commonly include both the registrant's and the target's auditors, this surfaces auditor turnover or scope changes mid-offer. Output: a consent-refresh trail used to satisfy internal closing checklists and to evidence completeness in post-closing disputes.
Because F-8 POS filings selectively re-file only the exhibits being changed, data engineers diff documentFormatFiles across the original F-8 (sourced separately) and every F-8 POS sharing the same 333-... fileNo, taking the latest version of each exhibit slot (EX-1.x, EX-2, EX-3, EX-4.x, EX-5). Output: a deduplicated, version-resolved exhibit set per registration, suitable for loading into a deal-document store or proprietary M&A database.
Researchers studying MJDS usage extract entities[].cik, companyName, sic, tickers, and the cover-page U.S. agent for service of process to build a registry of Canadian issuers using F-8 plus their U.S. process agents (often a U.S. subsidiary satisfying the Form F-X requirement). Joining on cik against F-X and original F-8 corpora yields the full MJDS linkage table. Output: a population frame for academic studies of cross-border capital-market integration and a cleaned identifier map (CIK to OTC pink-sheet ticker to Canadian listing) for proprietary deal tables.
Because Part II indemnification disclosure and Part III undertakings sit in fixed positions in the primary document, counsel extract these sections across the dataset to compare by-law and Canada Business Corporations Act (or provincial counterpart) indemnification language, and to confirm standard Commission public-policy paragraphs. Output: clause libraries and benchmarking tables used when drafting indemnification provisions for new MJDS registrations.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-f8-pos-files.json
Returns dataset-level metadata (name, description, last updated timestamp, earliest sample date, total records, total size, form types, container format, file types), the full dataset download URL, and a list of all available container files with per-container size, record count, updated timestamp, and download URL. Poll this endpoint to detect which containers were modified in the most recent refresh and download only those that changed. This endpoint does not require an API key.
1
{
2
"datasetId": "1f13365b-9ae0-6a69-a960-2d639dff239a",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-f8-pos-files.zip",
4
"name": "Form F-8 POS Files Dataset",
5
"updatedAt": "2026-04-16T08:51:43.011Z",
6
"earliestSampleDate": "2002-05-01",
7
"totalRecords": 31,
8
"totalSize": 622106,
9
"formTypes": ["F-8 POS"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["HTML", "TXT", "JSON"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-f8-pos-files/2002/2002-05.zip",
15
"key": "2002/2002-05.zip",
16
"size": 41280,
17
"records": 2,
18
"updatedAt": "2026-04-16T08:51:43.011Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-f8-pos-files.zip?token=YOUR_API_KEY
Downloads the complete dataset as a single ZIP archive containing every monthly container from May 2002 to the present. This endpoint requires an API key.
Download Single Container: https://api.sec-api.io/datasets/form-f8-pos-files/2002/2002-05.zip?token=YOUR_API_KEY
Downloads one monthly container ZIP, useful when you only need filings from a specific month or want to fetch only containers updated since the last refresh. This endpoint requires an API key.
The dataset covers Form F-8 POS — the post-effective amendment to a Form F-8 registration statement under 17 CFR 239.38 and the U.S.-Canada Multijurisdictional Disclosure System. F-8 itself is the short-form U.S. registration used by Canadian issuers to register securities offered as consideration in exchange offers and business combinations such as amalgamations, plans of arrangement, takeover bids, and mergers.
One record is a single EDGAR submission of Form F-8 POS, uniquely identified by its accession number and stored on disk as an accession-numbered folder containing a metadata.json header at the root and one EDGAR-SGML-wrapped document per submission component (the primary zf-8pos.htm document plus its exhibits). Records are grouped under year directories into year-month ZIP containers such as 2003-05.zip.
The filer is always the original Canadian issuer-registrant of the underlying Form F-8 — a foreign private issuer incorporated in Canada or a Canadian province or territory that meets MJDS substantive eligibility (a 36-month Canadian reporting history, public float and exchange-listing thresholds, and good standing with a Canadian securities regulator) and whose registration is being used to offer securities in an exchange offer or business combination. Targets, advisors, and counsel are never the filer of record, even when their information appears inside the amended prospectus.
F-8 POS filings are event-driven, not periodic. They are triggered after effectiveness by Section 10(a)(3) staleness, the Item 512 fundamental-change undertaking, material changes outside Rule 424's permissible-supplement scope, Canadian regulatory developments in the underlying transaction (such as amendments to a takeover-bid circular or court-approved changes to a plan of arrangement), or by the closing or termination of the offer.
F-8/A is a pre-effective amendment to the same parent Form F-8 and is excluded from this dataset, which contains only post-effective amendments. F-4 POS is the non-MJDS analog used by foreign private issuers generally and requires U.S.-style Securities Act disclosure rather than MJDS home-country documents; it is the closest content analog to F-8 POS but the disclosure regimes are not equivalent.
The dataset is distributed as ZIP containers organized by year and month (for example 2003-05.zip). File types inside the containers are HTML and TXT — the original EDGAR document files preserved with their SGML envelopes — plus JSON, used exclusively for the per-record metadata.json header.
No. Image files such as issuer logos, signature scans, and cover-page artwork (typically .jpg and .gif) are intentionally stripped from the dataset. Their inventory rows still appear in metadata.json.documentFormatFiles as GRAPHIC entries with original sizes and EDGAR URLs, so they can be fetched directly from EDGAR if needed.