Form F-80POS Files Dataset

The Form F-80POS Files Dataset is a complete archive of post-effective amendments to Form F-80 registration statements filed on EDGAR by Canadian foreign private issuers under the U.S./Canadian Multijurisdictional Disclosure System (MJDS). One record is a single EDGAR submission of form type F-80POS — the post-effective amendment registrants use to update an already-effective Form F-80 covering an exchange offer or business combination — identified by its 18-digit accession number and packaged as an accession-level folder containing the structured submission header (metadata.json), the amendment HTML, and any non-image exhibits transmitted under the same accession. The filer is always the Canadian registrant that filed the underlying F-80, signing through its principal officers, a majority of its board, and its U.S. authorized representative. The dataset covers every F-80POS accepted by EDGAR from January 2003 onward and is distributed as monthly ZIP containers holding JSON, HTML/HTM, and TXT files.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset packages every F-80POS filing accepted by EDGAR from January 2003 onward. Form F-80 is the Securities Act of 1933 registration statement available under MJDS for certain large Canadian foreign private issuers registering securities to be issued in connection with an exchange offer or business combination involving a U.S. target. Under MJDS, the substantive Part I disclosure rests on the issuer's home-jurisdiction take-over bid circular or offer document prepared in accordance with Canadian securities law; the SEC accepts that document as the primary disclosure record, with limited U.S.-specific overlay in Part II.

A post-effective amendment ("POS") is filed after the underlying F-80 has been declared effective. Its function is to update, correct, supplement, or extend the effective registration. Typical purposes include reflecting material changes to the offer terms, adding or refiling exhibits (legal opinions, tax opinions, consents of counsel and auditors, supplemental indentures), incorporating updated Canadian disclosure documents, adding new selling securityholders, extending the offer period, reflecting consummation of the offer, or deregistering unsold securities. Structurally, an F-80POS is a delta layered on top of the original F-80 and any prior amendments: it does not re-state the underlying registration in full, and it routinely incorporates large portions of the prior filing by reference rather than republishing them.

Because Form F-80POS is a niche instrument under MJDS, the universe is small and recent years are sparse to empty. The dataset is distributed as year-month ZIP containers holding accession-level folders; included file types are JSON, HTML/HTM, and TXT (with PDF exhibits occasionally appearing where registrants filed binary attachments). Image attachments — logos, scanned signatures, and other raster binaries — are deliberately excluded by the dataset producer; everything else originally accepted by EDGAR for that accession is preserved.

Content Structure of a Single Record

What one record represents

One record in the Form F-80POS Files dataset is a single EDGAR submission of form type F-80POS — a post-effective amendment to a registration statement on Form F-80 — identified by its 18-digit EDGAR accession number. Physically, each record is an accession-level folder packaged inside a year-month ZIP container. The folder is named after the zero-padded, no-dash accession number (for example 000119312514040727) and contains the structured submission header in metadata.json together with the registrant's primary post-effective amendment document and any exhibits or cover materials that were transmitted under the same accession.

Content layout of a single record

Each record is a small, self-contained directory laid out with two layers:

• A single metadata.json file describing the EDGAR submission as structured data.
• One or more attachment files — almost always HTML documents with the .htm extension — each wrapped in EDGAR's SGML <DOCUMENT> envelope. The principal attachment is the F-80POS amendment text; additional attachments correspond to exhibits filed with the amendment.
• Optionally, a complete-submission text file representing the entire SGML .txt package as transmitted to EDGAR.

Together, the JSON metadata and the SGML-wrapped documents reconstruct both the machine-readable header EDGAR built from the filer's <SEC-HEADER> block and the human-readable filing body that the registrant prepared. The file types found in the dataset are JSON and HTML/HTM, with TXT appearing where the bundled complete-submission file is included; PDF exhibits occasionally appear when registrants file binary attachments.

metadata.json — the structured submission header

metadata.json is a single JSON object that flattens the EDGAR submission header for one accession. The salient fields are:

• formType — always "F-80POS" for records in this dataset.
• accessionNo — canonical dashed accession number (for example 0001193125-14-040727).
• id — 32-character hex hash used as an internal record identifier.
• filedAt — ISO-8601 timestamp with timezone offset capturing EDGAR's acceptance moment.
• periodOfReport — YYYY-MM-DD reference date supplied by the filer.
• description — human-readable form description such as "Form F-80POS - Post-effective amendment to a F-80 registration".
• linkToFilingDetails, linkToTxt, linkToHtml, linkToXbrl — direct URLs back to the primary HTML document, the SGML .txt complete submission, the EDGAR filing-index page, and (when applicable) XBRL artifacts on sec.gov/Archives.
• documentFormatFiles — array describing each attachment in the SGML manifest. Each element carries a sequence number, a textual description (for example "F-80POS", "EX-5.1", or "Complete submission text file"), an EDGAR document type code, a byte size, and a documentUrl. A sequence of a single space combined with a type of a single space marks the bundled complete-submission text file.
• entities — array of one or more entity objects representing the filer, any co-filers, and the subject company of the exchange offer where applicable. Each entity carries companyName (with the role appended in parentheses such as "… (Filer)" or "… (Subject Company)"), cik, fileNo (the 333-series Securities Act file number for the underlying F-80 registration), irsNo (typically "000000000" for foreign filers), stateOfIncorporation using EDGAR's two-character codes (Canadian provinces appear as codes such as A0 for Alberta, A1 for British Columbia, Z4 for Nova Scotia), fiscalYearEnd as a MMDD string, the Securities act ("33" for the 1933 Act), the sic industry classification with name, the EDGAR filmNo, and the form type repeated at the entity level.
• seriesAndClassesContractsInformation — array reserved for investment-company series/class data; effectively always empty for F-80POS, which is a 1933-Act registration vehicle outside the investment-company regime.
• dataFiles — array of structured data attachments. Empty in practice for F-80POS, which is not subject to the XBRL/iXBRL reporting requirements that apply to operating-company periodic reports.

The SGML <DOCUMENT> wrapper around each attachment

Although attachment files use the .htm extension, each one begins with EDGAR's SGML envelope rather than directly with <html>. The envelope consists of header lines that EDGAR derived from the filer's submission manifest:

          1
          <DOCUMENT>
        

          2
          <TYPE>F-80POS
        

          3
          <SEQUENCE>1
        

          4
          <FILENAME>d671683df80pos.htm
        

          5
          <DESCRIPTION>F-80POS
        

          6
          <TEXT>
        

          7
          <HTML> ... full HTML of the amendment ... </HTML>
        

          8
          </TEXT>
        

          9
          </DOCUMENT>
        

<TYPE> carries the EDGAR document-type tag (the principal attachment uses F-80POS; exhibits use codes such as EX-4, EX-5.1, EX-8.1, EX-23.1, EX-99.1, and — on more recent filings — EX-FILING FEES). <SEQUENCE> orders the attachments as transmitted; <FILENAME> and <DESCRIPTION> mirror the manifest. The substantive HTML payload nests inside <TEXT> and contains the registration-statement prose, with closing </TEXT> and </DOCUMENT> lines after the final </HTML>.

The body of the F-80POS amendment

Within the <TEXT> payload, the F-80POS document follows the structural conventions of MJDS registration statements on Form F-80, adapted to its post-effective character. The major components a reader will encounter, broadly in order, are:

• Facing page / cover page. Identifies the document as a post-effective amendment to a registration statement on Form F-80, the SEC file number assigned to the underlying F-80, the registrant's exact legal name, the province or other Canadian jurisdiction of incorporation, the SIC industry classification, the I.R.S. employer identification number (often shown as "Not Applicable" for foreign issuers), the registrant's principal executive office address in Canada, the name and U.S. address of the agent for service of process (referencing the registrant's Form F-X), and a "Copies to" block listing U.S. and Canadian counsel for the registrant and, where relevant, for the subject company. The cover page also identifies the title and amount of securities to which the amendment relates and may carry a calculation-of-registration-fee table when fees are being adjusted.

• Explanatory note. A short paragraph stating the purpose of the post-effective amendment — for example, to add exhibits, file revised offer materials, extend the expiration date of an exchange offer, reflect consummation of the offer, or deregister unsold securities. This note is what distinguishes one F-80POS from another and is the single most informationally dense block for downstream interpretation.

• Part I — Information required to be delivered to offerees or purchasers. Under MJDS, Part I largely consists of the home-jurisdiction offer document or take-over bid circular prepared in accordance with Canadian securities law. In a post-effective amendment, Part I typically references and incorporates the previously filed Canadian offer materials and amends specific portions, or attaches a supplemental circular reflecting changes since the original F-80 was declared effective. Where the underlying transaction has closed, Part I may be reduced to a confirmation statement and incorporation-by-reference language.

• Part II — Information not required to be delivered to offerees or purchasers. Contains the U.S.-specific overlay required by Form F-80's instructions: indemnification of directors and officers, recent sales of unregistered securities (where applicable), the exhibit index, undertakings, and consents incorporated by reference. The exhibit index in a POS amendment is the authoritative inventory of which exhibits are added, refiled, revised, or carried over by reference from the original F-80 or earlier amendments.

• Signatures. The amendment closes with the registrant's signature block (executed in Canada by an authorized officer of the issuer), followed by the U.S. authorized representative's signature pursuant to the requirements applicable to foreign private issuers. Signatures appear as text within the HTML; original wet-ink images are not preserved because image files are excluded from the dataset.

• Exhibits. Each filed exhibit appears as a separately wrapped <DOCUMENT> block in the same accession, with its own <TYPE>, <SEQUENCE>, <FILENAME>, and <DESCRIPTION> tags. Common exhibit codes include EX-4 (instruments defining the rights of security holders), EX-5.1 (legal opinion as to validity), EX-8.1 (tax opinion), EX-23.1/EX-23.2 (consents of accountants and counsel), EX-99 (additional exhibits, often the Canadian offer/circular and supplemental letters of transmittal), and — on amendments filed after the SEC's 2022 fee-disclosure modernization — EX-FILING FEES carrying the standalone Filing Fee Table. In post-effective amendments, only the exhibits added, refiled, or revised by the amendment are normally present; the rest remain incorporated by reference to the original F-80 or to other reports filed with the SEC.

Included content

Each record includes:

• The structured metadata.json reflecting the EDGAR submission header.
• The full text of the F-80POS amendment as filed, wrapped in its SGML <DOCUMENT> envelope.
• All non-image attachments transmitted under the same accession — exhibits, cover letters, supplemental opinions, consents, supplemental Canadian offer materials, filing-fee exhibits where present, and (when present) the bundled complete-submission text file representing the entire EDGAR .txt package.

Excluded or separate content

• Image files. Logos, signature graphics, charts saved as GIF/JPG/PNG, and any other raster attachments are intentionally omitted. Where the original HTML referenced such images inline, the references remain but the binaries are not present in the record.
• Documents incorporated by reference but not attached. Because a POS amendment is layered on top of the underlying F-80 (and possibly earlier amendments), substantial portions of the substantive disclosure may live in earlier accessions rather than in the F-80POS itself. Those earlier filings are separate EDGAR accessions and reside in the corresponding F-80 (or other) datasets, not within this record.
• Form F-X. The standalone appointment of a U.S. agent for service of process is filed on Form F-X under its own accession number and is not part of an F-80POS record, although the F-80POS cover page typically names the agent and references the underlying F-X.
• Canadian-regulator filings. The original SEDAR/SEDAR+ filings that ground the MJDS disclosure are not redistributed here; only what the registrant filed with EDGAR is included.

Changes in required content and structure over time

Form F-80 and its post-effective amendment counterpart have been comparatively stable since MJDS was adopted jointly by the SEC and the Canadian Securities Administrators in 1991. Across the dataset's coverage, the basic facing-page composition, Part I / Part II split, exhibit-index conventions, and signature requirements have remained materially unchanged. The most consequential evolutions affecting record content over this window are:

• Tightening of MJDS eligibility. Periodic SEC and CSA refinements to the public-float threshold and to the continuous-reporting requirements have narrowed the population of eligible Canadian issuers, contributing to the form's small overall footprint and the near-disappearance of recent filings.
• Fee-table modernization. Following the SEC's 2022 amendments to the fee-disclosure rules under Rule 457 and related provisions, registration-fee calculations migrated from in-document tables to a dedicated Exhibit 107 ("Filing Fee Table"). F-80POS amendments filed after that change include an EX-FILING FEES document in the manifest, and the exhibit index in Part II references it explicitly.
• Foreign-private-issuer rule refinements. Successive SEC rule changes refined the instructions and undertakings applicable to foreign private issuers using MJDS forms. While these did not restructure Form F-80POS, they affected the boilerplate language and the precise consent and incorporation-by-reference exhibits required.
• Subject-company entity disclosure. In transactions where the F-80 registers securities to be issued in an exchange offer for a U.S. target, the EDGAR header increasingly captures the target as a Subject Company entity in addition to the registrant filer; the dataset reflects this in the entities array.

These structural shifts are typically visible at the metadata layer (entity roles, presence of an EX-FILING FEES document) and in the exhibit index of the body, rather than in the gross outline of the document.

Changes in data format over time

Because the dataset begins in January 2003, all records postdate EDGAR's full transition away from the ASCII-only submission era. From the dataset's first record onward, the F-80POS body is essentially always an HTML document wrapped in the EDGAR SGML <DOCUMENT> envelope, accompanied by HTML or PDF exhibits. Within that window the relevant format evolutions are limited:

• HTML conventions. Earlier-decade filings tend to use simpler HTML 4 markup with inline styling and table-driven layout; later filings make greater use of CSS classes, modern table structures, and richer typography. The SGML envelope and the per-document segmentation pattern have not changed.
• Complete-submission .txt package. EDGAR has continuously produced the bundled complete-submission .txt file (the concatenation of all <DOCUMENT> blocks under a single <SEC-DOCUMENT> root) alongside the individual document files; when present in a record it appears in documentFormatFiles with an empty sequence and type and a "Complete submission text file" description.
• Filing-fee exhibits. The 2022 fee-modernization change introduced the EX-FILING FEES document type into the manifest where applicable, slightly widening the set of EDGAR document-type codes that may appear under documentFormatFiles[].type.

Interpretation notes

• Amendment, not a self-contained registration. Treat each F-80POS as a delta on a prior F-80. Disclosures absent from the amendment body are typically present in the underlying F-80; the explanatory note on the cover or just after it is the canonical signal of what changed.
• Accession-folder vs. metadata accession formatting. The folder is named with the 18-digit no-dash accession (000119312514040727); inside metadata.json, accessionNo uses the canonical dashed form (0001193125-14-040727). Joins across the two layers must normalize accordingly.
• Foreign-issuer fingerprints. Expect irsNo: "000000000", MJDS-style two-letter stateOfIncorporation codes for Canadian provinces (A0, A1, Z4, etc.), an empty linkToXbrl, and an empty dataFiles array — these are characteristic of the population rather than missing data.
• SGML header is not HTML. Parsers that consume .htm attachments must skip or capture the leading <DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, and <TEXT> tags before the actual <HTML> content begins, and the matching </TEXT></DOCUMENT> lines after the closing </HTML>.
• Incorporation by reference. Exhibits frequently reference earlier accessions by exhibit number rather than re-attaching them; the exhibit index inside Part II is the authoritative map of what is present in the record versus what continues to live on EDGAR under a prior accession.
• Image-free record. Visual evidence (signature graphics, embedded charts, certificates) is not preserved; downstream consumers relying on image extraction will not find binaries even where the HTML references them.
• Sparse population. Because this filing form has become extremely rare in recent years, gaps between successive records may span many months. Year-month containers may contain only a handful of accession folders or none at all, and absence of records in a given period is informational rather than indicative of missing data.

Who Files or Publishes This Dataset, and When

Who files

Each F-80POS record is filed by the Canadian registrant that originally filed the underlying Form F-80, signing through its principal executive officer, principal financial officer, principal accounting officer, a majority of its board, and its U.S. authorized representative. The post-effective amendment carries forward the original SEC file number assigned to the base F-80.

Form F-80 (and therefore F-80POS) is restricted to a narrow population of foreign private issuers eligible to use the Multijurisdictional Disclosure System (MJDS) jointly adopted by the SEC and the Canadian Securities Administrators in 1991. To qualify, the registrant must:

• Be incorporated or organized in Canada or a Canadian province or territory.
• Be a foreign private issuer (Securities Act Rule 405) and not an investment company, other than a closed-end fund meeting the form's conditions.
• Have been subject to Canadian continuous-disclosure requirements for at least 36 calendar months preceding filing and be in current compliance.
• Have an aggregate public float of at least C$75 million in the equity class concerned, measured within 60 days of filing (for exchange offers, the test applies to the offeror).
• Generally have the relevant securities listed on a recognized Canadian exchange (e.g., the TSX).
• Be using the form for an exchange offer or business combination (amalgamation, plan of arrangement, or similar reorganization) — never a cash offering.

In two-party transactions, the filer is always the offeror or surviving issuer issuing the securities, not the target whose shareholders receive them. The target appears in the filing only through references and consents.

When the record is created

F-80POS filings are event-driven, not periodic. A post-effective amendment exists only after the underlying F-80 has been declared effective (or has become effective by operation of Securities Act Rule 467, the MJDS automatic-effectiveness mechanism). Pre-effective amendments use the form code F-80/A; once effective, every further amendment is filed as F-80POS.

Typical triggering events include:

• Material changes to offering terms during an open exchange offer (revised exchange ratio, extended expiration, new closing conditions, increased consideration).
• Updates to the underlying Canadian disclosure — the F-80 incorporates the issuer's Canadian prospectus, takeover-bid circular, or management information circular, so any amendment to those documents in Canada flows through to an F-80POS.
• Curing material misstatements or omissions discovered after effectiveness.
• Updated exhibits, consents, or opinions (auditor consents, legal or tax opinions, revised exhibits).
• Closing out the registration — deregistering unsold securities, reflecting final share-issuance figures, or terminating the offering after the exchange offer or business combination is consummated, withdrawn, or terminated.

Because triggers cluster around the life of a single transaction, F-80POS filings tend to appear between effectiveness and the offer's expiration, plus a final amendment at or shortly after closing. The disclosure obligation arises under Section 5 of the Securities Act of 1933 and the amendment rules (notably Securities Act Rules 472, 473, and 467), with substantive content governed by the MJDS form instructions adopted in SEC Release No. 33-6902 (June 21, 1991).

Important distinctions

• F-80POS vs. F-80/A. F-80/A is a pre-effective amendment filed during SEC and Canadian regulator review; F-80POS is a post-effective amendment filed after the registration statement is effective.
• F-80POS vs. other MJDS POS forms. F-10POS amends Form F-10 (cash offerings by MJDS issuers); F-7POS amends Form F-7 (rights offerings); F-9POS amends Form F-9 (investment-grade debt and preferred). F-80POS is exclusive to exchange offers and business combinations.
• F-80POS vs. F-4 amendments. Canadian acquirers that fail MJDS eligibility (e.g., insufficient public float or disclosure history) must register on Form F-4 (or Form S-4 if separately eligible) and amend under that regime, which requires full U.S.-style prospectus disclosure rather than incorporating Canadian documents.
• Cash bids and continuous offerings fall outside. MJDS cash tender offers use Schedule 14D-1F, continuous Canadian-style cash offerings use Form F-10, and MJDS annual reports use Form 40-F (not Form 20-F).
• Deregistration vs. withdrawal. A post-effective amendment used to deregister unsold securities is distinct from Form RW, which withdraws a registration statement only while still pending and unaccelerated.
• Loss of MJDS eligibility mid-offering. If the registrant ceases to qualify (public float drops, Canadian compliance lapses), it may need to amend onto a non-MJDS form rather than continue with F-80POS.

EDGAR became fully mandatory for MJDS filers on November 4, 2002, so the EDGAR-resident F-80POS population begins in earnest in early 2003 and reflects how rare MJDS exchange-offer registrations have become.

How This Dataset Differs From Similar Datasets or Filings

Form F-80POS sits at a narrow intersection: post-effective amendments to F-80 registration statements filed by MJDS-eligible Canadian issuers for stock-for-stock exchange offers and business combinations. Three axes — filer eligibility (Canadian, MJDS-qualified), transaction type (securities-for-securities cross-border M&A), and filing stage (post-effective) — define the boundary. The most useful comparisons run along each axis in turn.

Closest related filing types

Form F-80 (initial registration). The base filing on which every F-80POS depends. Same eligibility regime, same transaction context, same prospectus structure built on the Canadian take-over bid circular. The only distinction is filing stage: F-80 launches and clears the offer; F-80POS modifies it after effectiveness — to extend the offer period, add or refile exhibits, reflect consummation, or deregister unsold securities. The two are complements; reconstructing a complete deal record requires both.

Form F-80/A (pre-effective amendment). Same registration, opposite side of effectiveness. F-80/A is filed during SEC and Canadian-regulator review and typically responds to staff comments or restates disclosure before the offer is cleared. F-80POS keeps an already-effective registration current. A user studying review dynamics wants F-80/A; a user studying the live offer's lifecycle wants F-80POS.

Sibling MJDS post-effective amendments (F-10POS, F-7POS, F-9POS). Structurally the closest peers — same MJDS framework, same reliance on Canadian home-country disclosure, same post-effective mechanics. They diverge on transaction type: F-10POS covers general securities offerings (equity, debt, convertibles), F-7POS covers rights offerings to existing holders, and F-9POS covers investment-grade debt and preferred. F-80POS is uniquely tied to exchange offers and business combinations, so its content centers on offer terms, exchange ratios, target securities, and combination disclosures rather than primary-offering economics, rights mechanics, or indenture terms.

Form F-4POS (non-MJDS cross-border M&A POS). Same transaction type as F-80POS — post-effective amendments to stock-for-stock M&A registrations — but a different disclosure regime. F-4POS requires a full SEC-compliant prospectus with U.S. GAAP-reconciled financials and Regulation S-K narrative; F-80POS leans on the Canadian prospectus with only a thin U.S. overlay in Part II. F-4POS is the fallback when a Canadian acquirer fails MJDS eligibility (insufficient float or disclosure history) and is a much larger dataset because non-MJDS cross-border deals are common.

Form S-4POS (domestic M&A POS). Same functional slot, different filer population. S-4POS amends S-4 registrations used by U.S. issuers in mergers and exchange offers. The disclosure regime is fully domestic (U.S. GAAP, Regulation S-K), and the dataset is orders of magnitude larger. The right comparison only when the question is U.S. domestic deal amendments rather than cross-border Canadian deals.

Schedule 14D-1F (MJDS cash tender offers). Same MJDS filer pool and same cross-border takeover context, but cash consideration rather than securities. Because no securities are issued, no Securities Act registration is required — so 14D-1F replaces, rather than amends, the F-80 family. A complete map of MJDS cross-border takeovers needs both: F-80/F-80POS for stock deals, 14D-1F for cash deals.

Form 425 (M&A communications). Frequently appears in the same EDGAR docket as an F-80 transaction and covers the same deal, but 425 captures press releases, investor presentations, and other written communications — not the binding registration document. 425 is the marketing layer; F-80POS is the formal updated offer document the SEC has accepted.

Form F-X (agent for service of process). A procedural one-page consent appointing a U.S. agent for service. F-X is filed alongside F-80 transactions and useful for linking MJDS issuers across filings, but contains no offer or business disclosure and is never a content substitute for F-80POS.

Key differences at a glance

• Stage: F-80 = initial; F-80/A = pre-effective amendment; F-80POS = post-effective amendment.
• Transaction type within MJDS: F-80POS = exchange offer / business combination; F-10POS = general offering; F-7POS = rights offering; F-9POS = investment-grade debt; 14D-1F = cash tender (no registration).
• Disclosure regime for cross-border M&A: F-80POS = MJDS, Canadian prospectus; F-4POS = U.S. regime, Reg S-K and GAAP reconciliation.
• Filer geography: F-80POS = Canadian MJDS issuers only; S-4POS = U.S. domestic issuers; F-4POS = other foreign and non-MJDS Canadian issuers.
• Document role: F-80POS = registration content; 425 = communications; F-X = procedural appointment.

Boundary summary

What isolates F-80POS is the simultaneous satisfaction of three conditions: an MJDS-eligible Canadian filer, a securities-for-securities exchange offer or business combination, and a post-effective stage. Strip any one and the filing migrates elsewhere — to F-80 or F-80/A on the stage axis, to F-10POS / F-7POS / F-9POS on the transaction axis, to F-4POS or S-4POS on the regime axis, and to 14D-1F, F-X, or 425 when the document is cash-only, procedural, or communications-only. The dataset's small footprint is a direct consequence of that intersection, and is what gives it analytical value: it isolates the post-effective lifecycle of every MJDS stock-for-stock cross-border deal registered on Form F-80.

Who Uses This Dataset

The user base for the Form F-80POS Files Dataset is small, specialized, and cross-border in focus, reflecting the niche regulatory slot the form occupies.

Cross-border M&A counsel

Lawyers structuring share-for-share deals between Canadian acquirers and US targets mine the dataset for amendment precedents: cover-page language, revised exchange-ratio mechanics, updated offer terms, and exhibit packaging. They use prior filings to decide whether to amend an outstanding offer rather than withdraw and refile.

MJDS and Canadian securities specialists

Practitioners advising on dual-jurisdiction filings use the records to map how Canadian takeover-bid circulars and information circulars feed US registration mechanics. They focus on cover information, signature blocks, and consents from Canadian auditors and counsel to determine when changes to the home-jurisdiction document trigger a US post-effective amendment.

Deal-tracking analysts

Analysts maintaining cross-border M&A databases use metadata fields (CIK, filing date, accession number, period of report) to anchor each F-80POS to its underlying F-80 and announced transaction. The amended prospectus tells them whether consideration ratio, minimum tender condition, or expiry date changed.

Risk-arbitrage and event-driven desks

Trading teams holding positions in announced exchange offers watch F-80POS filings for terms changes that move spreads: extended deadlines, increased consideration, waived conditions. Filing timestamps drive trade sequencing against public announcements; revised terms drive position sizing and hedge ratios on the acquirer's stock.

In-house compliance and registration teams

Securities compliance staff at Canadian MJDS filers benchmark their own amendment packages against accepted filings, checking exhibit lists, consent letters, signatures, and cover structure before EDGAR submission.

Financial printers and EDGAR filing agents

Service providers preparing MJDS submissions use the corpus as a reference library of accepted F-80POS packages, checking submission structure, file naming conventions, and prospectus HTML formatting against historical precedent.

Forensic and disclosure analysts

Reviewers comparing the original F-80 against the F-80POS amendment produce diff-level change logs covering risk factors, pro forma financials, target descriptions, and US tax disclosures, often supporting litigation or regulatory work product.

Academic and policy researchers

Researchers in securities regulation and cross-border finance use the complete post-2003 population for longitudinal work on MJDS adoption, amendment frequency, and the split between substantive terms revisions and housekeeping updates. Policy analysts use the same corpus to assess whether the MJDS regime continues to deliver streamlined access or shows friction worth reform.

Credit and counterparty analysts

Credit teams covering Canadian issuers funding US acquisitions with stock track amended terms and updated pro forma financials to revise views on leverage, dilution, and integration risk.

Data engineers and RAG developers

Teams building filing-extraction and retrieval pipelines treat the small, bounded F-80POS corpus as a clean test bed for MJDS-specific parsing: cross-border deal-term extractors, exhibit classifiers, and amendment-aware retrieval against the parent registration.

Specific Use Cases

The dataset's narrow scope — post-effective amendments to MJDS Form F-80 registrations for Canadian-acquirer share exchange offers — supports a focused set of operational workflows.

• Tracking changed offer terms in live Canadian-acquirer exchange offers. Risk-arbitrage and event-driven desks parse the explanatory note and amended cover page of each new F-80POS to detect extended expiry dates, revised exchange ratios, increased consideration, or waived minimum-tender conditions. The filedAt timestamp in metadata.json anchors the change to the trading tape; the deltas drive spread re-pricing and hedge resizing on the acquirer's stock.

• Reconstructing the full lifecycle of an MJDS exchange offer. Deal-tracking analysts join each F-80POS to its underlying F-80 (and any F-80/A) using the shared 333-series fileNo and the registrant cik, then sequence amendments by filedAt to produce a per-deal timeline of launch, pre-effective revisions, post-effective updates, consummation, and deregistration of unsold shares.

• Exhibit-package precedent search for MJDS counsel and filing agents. Cross-border M&A lawyers and EDGAR filing agents query documentFormatFiles across the corpus to retrieve accepted exhibit inventories — EX-5.1 validity opinions, EX-8.1 tax opinions, EX-23 consents from Canadian auditors, EX-99.1 supplemental Canadian circulars, and post-2022 EX-FILING FEES tables — and use them as drafting templates and submission-structure checklists before transmitting their own amendments.

• Diff-level change logs between F-80 and F-80POS bodies. Forensic and disclosure reviewers extract the SGML-wrapped HTML payload of the amendment, strip the <DOCUMENT> envelope, and run section-aligned diffs against the original F-80 to flag substantive revisions to risk factors, target-company descriptions, pro forma financials, and U.S. tax disclosure for litigation support or regulatory work product.

• Subject-company linkage for U.S. target identification. Analysts walk the entities array to separate the Canadian filer from the U.S. Subject Company, joining the subject CIK back to the target's own EDGAR record (10-K, 14D-9, proxies) to assemble both sides of each cross-border combination in a single relational view.

• Longitudinal study of MJDS usage and post-effective behavior. Securities-regulation researchers use the bounded post-2003 population to measure F-80POS frequency over time, classify each amendment by purpose (term extension, consummation, deregistration, fee adjustment, exhibit refile) from the explanatory note, and correlate trend breaks with MJDS eligibility tightening and the 2022 fee-disclosure modernization.

• Test corpus for MJDS-aware extraction pipelines. Data engineers and RAG developers use the small, complete F-80POS set as a controlled benchmark for parsers that must handle EDGAR's SGML envelope, foreign-issuer metadata fingerprints (Canadian-province stateOfIncorporation codes, irsNo of 000000000, empty linkToXbrl), and amendment-aware retrieval that resolves incorporation-by-reference back to the parent F-80 accession.

Dataset Access

Dataset Index JSON API: [https://api.sec-api.io/datasets/form-f80pos-files.json](https://sec-api.io/datasets)

This endpoint returns dataset metadata including the name, description, last updated timestamp, earliest sample date, total record count and size, covered form types, container format, and content file types. It also lists the full dataset download URL together with every individual container file and per-container metadata such as size, record count, last updated timestamp, and download URL. Poll this endpoint to monitor which containers were updated in the most recent refresh run and decide which files to download incrementally. No API key is required to call this endpoint.

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-6a5c-81eb-07b880006b8b",
        

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

          4
            "name": "Form F-80POS Files Dataset",
        

          5
            "updatedAt": "2026-04-16T08:47:53.081Z",
        

          6
            "earliestSampleDate": "2003-01-01",
        

          7
            "totalRecords": 38,
        

          8
            "totalSize": 638050,
        

          9
            "formTypes": ["F-80POS"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

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

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

          16
                "size": 13818783,
        

          17
                "records": 154,
        

          18
                "updatedAt": "2026-04-16T08:47:53.081Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

Download Entire Dataset: [https://api.sec-api.io/datasets/form-f80pos-files.zip](https://sec-api.io/datasets)?token=YOUR_API_KEY

Downloads the complete Form F-80POS Files dataset, covering all filings from January 2003 to the present, as a single ZIP archive. This endpoint requires an API key.

Download Single Container: [https://api.sec-api.io/datasets/form-f80pos-files/2026/2026-03.zip](https://sec-api.io/datasets)?token=YOUR_API_KEY

Downloads one monthly container file rather than the full dataset, which is useful for incremental updates. Replace the year and month path segments with the container key returned by the dataset index API. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form F-80POS, a post-effective amendment to a Form F-80 registration statement. Form F-80 is the Securities Act registration form available under the U.S./Canadian Multijurisdictional Disclosure System (MJDS) for Canadian foreign private issuers registering securities to be issued in connection with an exchange offer or business combination involving a U.S. target.

What does one record in this dataset represent?

One record is a single EDGAR submission of form type F-80POS, identified by its 18-digit accession number and packaged as an accession-level folder inside a year-month ZIP container. The folder holds a metadata.json file describing the EDGAR submission header plus the registrant's amendment HTML and any non-image exhibits transmitted under the same accession.

Who is required to file Form F-80POS?

The Canadian registrant that originally filed the underlying Form F-80 files each F-80POS, signing through its principal officers, a majority of its board, and its U.S. authorized representative. To use the F-80 family the registrant must be a Canadian foreign private issuer with at least 36 months of Canadian continuous-disclosure history, a public float of at least C$75 million in the equity class concerned, and a transaction structured as an exchange offer or business combination rather than a cash offering.

What triggers an F-80POS filing?

F-80POS filings are event-driven and only exist after the underlying F-80 has been declared (or deemed) effective. Typical triggers include material changes to offer terms (revised exchange ratio, extended expiration, increased consideration), updates to the Canadian disclosure documents incorporated by reference, refiled exhibits or consents, curing material misstatements or omissions, and closing out the registration by deregistering unsold securities after the deal is consummated, withdrawn, or terminated.

How does F-80POS differ from F-80/A and from F-4POS?

F-80/A is the pre-effective amendment used during SEC and Canadian-regulator review; F-80POS is the post-effective amendment that updates an already-effective registration. F-4POS covers the same transaction type — post-effective amendments to stock-for-stock M&A registrations — but uses the full U.S. disclosure regime (Regulation S-K, U.S. GAAP-reconciled financials) and is the fallback when a Canadian acquirer fails MJDS eligibility, whereas F-80POS leans on the Canadian prospectus with only a thin U.S. overlay in Part II.

What time period does the dataset cover and in what file format?

The dataset covers every F-80POS filing accepted by EDGAR from January 1, 2003 onward, reflecting the period after EDGAR became fully mandatory for MJDS filers on November 4, 2002. It is distributed as monthly ZIP containers holding JSON, HTML/HTM, and TXT files; PDF exhibits occasionally appear, while image attachments (logos, scanned signatures) are deliberately excluded.

How do I download the dataset?

Call the dataset index API at https://api.sec-api.io/datasets/form-f80pos-files.json (no API key required) to enumerate available monthly containers, then download either the entire dataset via https://api.sec-api.io/datasets/form-f80pos-files.zip?token=YOUR_API_KEY or a single monthly container via https://api.sec-api.io/datasets/form-f80pos-files/{YYYY}/{YYYY-MM}.zip?token=YOUR_API_KEY. Both download endpoints require an API key.