Form F-10POS Files Dataset

The Form F-10POS Files Dataset is a structured archive of every Form F-10POS post-effective amendment submitted to EDGAR from June 2002 to the present. Each record represents a single EDGAR submission of Form F-10POS — one accession number filed under the Securities Act of 1933 by a Canadian issuer (or co-registrant) operating under the Multijurisdictional Disclosure System (MJDS), 17 CFR 239.40), packaging the amended registration statement, updated Canadian-prepared prospectus material, and all attached exhibits and consents that were transmitted with the filing. F-10POS filings are made by senior Canadian issuers amending an already-effective Form F-10 or Form F-10EF — most often to deregister unsold shelf securities, add or remove selling securityholders, refresh expert consents, register additional securities, or update Canadian disclosure documents incorporated by reference. The dataset preserves both a structured metadata.json describing the submission as an EDGAR object and the registrant-supplied document layer (HTML and TXT files inside their original SGML <DOCUMENT> envelopes), with image attachments excluded. Records are partitioned into monthly ZIP containers under a YYYY/YYYY-MM.zip layout.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset is built from Form F-10POS, a post-effective amendment to a Form F-10 (most commonly to a Form F-10EF, the immediately effective MJDS registration statement). Form F-10 itself is the principal MJDS registration form available to substantial Canadian issuers under 17 CFR 239.40, allowing them to register securities offerings in the United States using Canadian disclosure documents — a Canadian short-form prospectus prepared under National Instrument 44-101 or a base shelf prospectus prepared under NI 44-102 — supplemented by a US-specific cover page, a tax disclosure section, signatures, and a thin set of US exhibits and consents. A "POS" amendment is filed after the original F-10 has gone effective to update the registration statement for material changes (for example, changes in the offered securities, named selling securityholders, the calculation of registration fees, the agent for service, or the incorporated Canadian documents) without resetting effectiveness through a new filing.

Because most substantive disclosure under MJDS is incorporated by reference from Canadian SEDAR/SEDAR+ filings, an F-10POS submission is typically lean: the on-EDGAR document set is dominated by the amended US cover page, an explanatory note describing the post-effective change, an updated Part II ("Information Not Required to be Delivered to Offerees or Purchasers") when applicable, signatures of the registrant and authorized US representative, and a short bundle of exhibits — powers of attorney, consents of Canadian and US counsel, auditor consents, and any new opinion or underwriting agreement triggering the amendment.

The dataset covers all F-10POS filings submitted to EDGAR from June 2002 onward and is distributed as ZIP containers; the file types inside a record are JSON metadata, HTML documents, and (for legacy filings) plain-text documents.

Content Structure of a Single Record

On disk, a record is a folder named with the 18-digit accession number with all dashes stripped (for example, accession 0001104659-25-116095 is materialized as folder 000110465925116095). Inside that folder live exactly one metadata.json describing the submission and a small set of SGML-wrapped document files — typically the F-10POS amendment document itself, optionally the complete submission text file, and any exhibits attached to the post-effective amendment, with image attachments excluded.

Each record presents two parallel layers that should be read together:

1. A structured metadata layer (metadata.json) that describes the submission as an EDGAR object — accession identifiers, filer entities and their identifiers, a per-document manifest, the filing timestamp, and direct links back to EDGAR.
2. A document layer consisting of the registrant-supplied filing artifacts as they were transmitted to EDGAR, each retaining the SGML <DOCUMENT> envelope (<TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, <TEXT>) that wraps the inner HTML or plain-text payload.

The two layers are linked: every entry in metadata.json's documentFormatFiles array names a documentUrl, type, description, sequence, and size corresponding to one of the wrapped document files in the folder, or to the complete-submission text file at EDGAR (which may not be materialized locally when the F-10POS amendment is the only document the registrant transmitted).

The metadata.json object

The metadata file is a single JSON object with a fixed top-level shape:

• formType — the literal string F-10POS, identifying the submission type.
• accessionNo — the canonical dashed accession (for example 0001104659-25-116095); the folder name is the same value with dashes removed.
• filedAt — ISO-8601 timestamp with timezone offset reflecting the EDGAR acceptance time, e.g. 2025-11-25T20:23:32-05:00.
• description — short EDGAR-style descriptor, typically Form F-10POS - Post-effective amendment to a F-10EF registration.
• linkToFilingDetails — URL to the primary F-10POS HTM document on sec.gov.
• linkToTxt — URL to the full SGML submission .txt on EDGAR.
• linkToHtml — URL to the EDGAR filing-index page (-index.htm).
• linkToXbrl — empty string for F-10POS records; the field exists for shape consistency across the broader form-files family.
• id — opaque 32-character hexadecimal record identifier.
• documentFormatFiles — ordered array of per-document descriptors, each with sequence, size (byte size as string), documentUrl, description, and type. Sequence "1" is the primary F-10POS document; subsequent integer sequences are exhibits in EDGAR order; a blank " " sequence with type " " denotes the wrapping complete-submission text file.
• dataFiles — array reserved for structured data attachments (e.g. XBRL/XML payloads); typically empty for F-10POS.
• seriesAndClassesContractsInformation — array reserved for investment-company series/class identifiers; not used for typical Canadian-issuer F-10POS filings and therefore typically empty.
• entities — array of filer and co-registrant records. Each entity carries companyName with a parenthetical role suffix such as (Filer), (Co-Registrant), or (Subject); cik; irsNo (often 000000000 for Canadian filers without a US EIN); fileNo (the 333- Securities Act file number under which the original F-10 was registered, preserved across all post-effective amendments); filmNo; the entity-level type and formType (both F-10POS); act set to "33" (Securities Act of 1933); sic (SIC code plus textual industry, e.g. 1000 Metal Mining); stateOfIncorporation using EDGAR's two-character codes (Canadian provinces appear as A0–A9; British Columbia is A1); fiscalYearEnd as MMDD; and tickers, an array of US and Canadian listing symbols.

The entities array is the principal source of issuer-level identification, since the wrapped HTML body does not always expose machine-readable identifiers beyond what is rendered on the cover page.

The document layer

Every non-JSON file in the folder is wrapped in the EDGAR SGML envelope rather than being a bare HTML or text file. The envelope has the form:

          1
          <DOCUMENT>
        

          2
          <TYPE>F-10POS
        

          3
          <SEQUENCE>1
        

          4
          <FILENAME>tm2532224d1_f10pos.htm
        

          5
          <DESCRIPTION>F-10POS
        

          6
          <TEXT>
        

          7
          <HTML> ... </HTML>
        

          8
          </TEXT>
        

          9
          </DOCUMENT>
        

The <TYPE> tag carries the EDGAR document-type code (F-10POS for the primary amendment document; EX-5.1, EX-23.1, etc. for exhibits when present); <SEQUENCE> carries the position within the submission; <FILENAME> carries the registrant-chosen filename; <DESCRIPTION> is the human-readable label that also appears in the EDGAR filing index. Anything inside <TEXT>...</TEXT> is the actual rendered content — for modern filings, an <HTML> document; for very old filings, plain ASCII text. Filename conventions are registrant-chosen: the primary document typically ends in _f10pos.htm, while the complete submission text, when present, is named <accessionNo>.txt (e.g. 0001104659-25-116095.txt).

Content of the primary F-10POS document

The primary document is structurally a US-side wrapper around incorporated Canadian disclosure rather than a full prospectus. Reading in source order, it typically contains:

• A cover-page heading naming the amendment number and the underlying form, for example POST-EFFECTIVE AMENDMENT NO. 1 TO FORM F-10 REGISTRATION STATEMENT UNDER THE SECURITIES ACT OF 1933.
• The registrant's exact legal name, the translated name (if any), the province or country of incorporation or organization (rendered both as text and as the EDGAR state code), the primary SIC code, and the IRS employer identification number when one exists.
• The principal executive office address in Canada and the address and telephone number of the registrant's authorized US representative (commonly Cogency Global, CT Corporation, or US counsel) acting as US agent for service of process under the MJDS.
• An indication of the approximate date of commencement of the proposed sale of the registered securities to the public, alongside the standard MJDS check-box block selecting the F-10 sub-paragraph (annual report, short-form prospectus, MJDS shelf, etc.) under which the original registration was effected.
• An "Explanatory Note" or similar narrative paragraph identifying what is being amended and why — for example, to add or remove selling securityholders, to update the calculation of the registration fee, to reflect a change in the agent for service, or to file additional exhibits or consents.
• Where the amendment changes the offering size or composition, an updated calculation-of-filing-fee table — historically rendered inline; for filings on or after the SEC's Filing Fee Modernization compliance date (general applicability beginning 2022), the fee data is presented through Exhibit 107 (Filing Fee Table) as a separate exhibit document with structured XML behind it, and the inline cover-page fee table is correspondingly retired or thinned.
• A short Part II section ("Information Not Required to be Delivered to Offerees or Purchasers") replicating or amending the indemnification, exhibit list, and undertakings sections from the original F-10 where the amendment touches those items.
• Signature blocks: the registrant's signature page, signed by an executive officer and by a majority of directors or persons performing similar functions (often through a previously filed power of attorney), and the separately required signature of the authorized US representative.
• An exhibit index enumerating exhibits being filed with or incorporated by reference into the post-effective amendment.

The substantive offering disclosure — the Canadian short-form or base-shelf prospectus, the issuer's Annual Information Form, MD&A, audited financial statements, and material change reports — is not re-filed in full with an F-10POS. It is incorporated by reference from the underlying F-10EF and from the Canadian SEDAR/SEDAR+ record, with only the specifically updated documents attached as exhibits to the amendment. As a result, F-10POS primary documents are often short — sometimes only a cover page, an explanatory note, and signatures — and the apparent terseness is a feature of the form rather than a sign of a truncated record.

Exhibits

When exhibits are present, they appear as additional <DOCUMENT> blocks with <TYPE> values drawn from the F-10 exhibit index of Item 9 (Part II), most commonly:

• EX-4 — instruments defining rights of holders (indentures, supplemental indentures, warrant agreements).
• EX-5.1 — opinion of Canadian counsel as to the legality of the securities under the laws of the issuer's home jurisdiction.
• EX-5.2 / EX-8 — tax opinions covering Canadian and/or US tax consequences.
• EX-15 — letter regarding unaudited interim financial information.
• EX-23.1, EX-23.2, ... — consents of independent auditors and consents of Canadian and US counsel where their opinions are referenced.
• EX-24 — powers of attorney covering directors' signatures.
• EX-25 — Statement of Eligibility of Trustee on Form T-1 for debt offerings.
• EX-99 — additional documents, including underwriting agreements and supplemental Canadian prospectus pages.
• EX-FILING FEES (Exhibit 107) — the structured Filing Fee Table introduced by the SEC's filing-fee modernization rules.

Each exhibit is a separately wrapped document file and is enumerated as its own entry in documentFormatFiles with type, description, and registrant-chosen <FILENAME>.

What the dataset record includes

Inside one folder, the dataset preserves:

• The metadata JSON for the accession.
• The primary F-10POS HTML document, named by the registrant (commonly ending _f10pos.htm).
• All non-image exhibits transmitted with the submission, each retained inside its EDGAR <DOCUMENT> envelope.
• For older filings transmitted as plain text rather than HTML, the corresponding .txt document.

The documentFormatFiles array in metadata is the authoritative manifest for what is present in the submission as filed, and links each manifest entry to a live sec.gov URL even when the local archive does not materialize that file.

What is excluded

Image attachments referenced by the HTML (logos, signature scans, charts) are excluded during dataset assembly, and <IMG SRC="..."> references inside the HTML body are therefore unresolved in the local copy. Documents incorporated by reference — the Canadian short-form prospectus on SEDAR+, the issuer's prior F-10EF, intervening F-X submissions (consent to service of process for the US agent), and Annual Reports on Form 40-F — are not bundled into the F-10POS folder; they reside in their own EDGAR accessions or on Canadian repositories and must be fetched independently if needed. Form F-10 has not historically been part of the inline XBRL regime, and the linkToXbrl field is empty for F-10POS records; the only structured XML payload that appears within an F-10POS submission is the Filing Fee Table inside EX-FILING FEES (Exhibit 107), where present.

Changes in required content and structure over time

The underlying form has been stable in its core architecture since MJDS was adopted in 1991, but several rule changes have shaped what an F-10POS record looks like across the dataset's June 2002–present coverage window:

• The expansion of Form F-X consent-to-service practice and the elaboration of agent-for-service blocks on the cover page have made the US-representative section more standardized over time, generally replacing ad hoc descriptions with a uniform name-and-address block.
• The 2005 Securities Offering Reform did not displace MJDS but tightened the relationship between Rule 415 shelf practice and F-10, leading to more F-10POS amendments associated with shelf takedowns and selling-securityholder updates rather than full re-registrations.
• The SEC's 2018–2022 Filing Fee Modernization rules introduced Exhibit 107 (the structured Filing Fee Table). Filings on or after the relevant compliance dates carry an additional EX-FILING FEES document inside the F-10POS submission, with both rendered HTML and a structured XML payload, and the inline cover-page fee table is correspondingly retired or thinned.
• Successive updates to Item 9 of Form F-10's exhibit list (consents, opinions, T-1 statements) have refined the exhibit bundle that typically accompanies a post-effective amendment.

Changes in data format over time

Because dataset coverage starts in June 2002, the earliest F-10POS records sit close to the boundary between EDGAR's legacy plain-text era and the HTML era. The format trajectory across the dataset is:

• Early-2000s submissions are sometimes filed as ASCII text inside the SGML <DOCUMENT>/<TEXT> envelope; the inner payload is plain text rather than HTML, with tabular cover-page content rendered via spaced columns.
• From the mid-2000s onward, HTML becomes the dominant inner payload, using inline-styled <P> and <TABLE> constructs typical of EDGAR filings (10pt Times New Roman, Times, Serif paragraphs; bordered tables for the jurisdiction/SIC/IRS block and the signature block).
• The SGML outer envelope (<DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, <TEXT>) is preserved consistently throughout the dataset's history and remains present in current filings.
• After 2020–2022, the addition of Exhibit 107 introduces a structured XML sidecar to the otherwise unstructured document layer; its XML is wrapped inside its own <DOCUMENT> block.

Interpretation notes

A few practical considerations apply when reading these records:

• The fileNo on each entity (a 333- Securities Act number) ties the F-10POS to its parent F-10/F-10EF and to all prior post-effective amendments under the same registration; chaining records by fileNo reconstructs the lifecycle of a single registration across multiple accessions.
• Substantive disclosure is incorporated by reference; downstream extraction of risk factors, financial information, or offering terms requires resolving those references to the underlying F-10EF and the Canadian short-form prospectus rather than parsing the F-10POS document alone.
• Multiple entities are common: the issuer, any guarantor co-registrants, and (occasionally) the US authorized representative may all appear with role suffixes such as (Filer), (Co-Registrant), or (Subject). The role suffix on companyName should be parsed alongside the rest of the entity record.
• Exclusion of image files means scanned signatures and logos referenced by the HTML body will be missing; the textual content of the cover page and signature block remains intact and is the canonical source for signatory names.
• The linkToTxt URL pointing to the complete submission text on EDGAR provides a fallback path to any content that was not materialized as a separate file in the local folder, including any image-bearing documents excluded from the dataset.
• All non-JSON document files retain the SGML <DOCUMENT> envelope; downstream HTML/text parsers must either strip the SGML header or operate on the inner <TEXT>...</TEXT> payload before applying a standard HTML parser.

Who Files or Publishes This Dataset, and When

Who files

Form F-10POS is filed by the Canadian issuer-registrant that has an existing, effective Form F-10 (or F-10EF) registration statement on file with the SEC. The filer is therefore not a new entrant to U.S. registration, but an issuer amending a Securities Act registration statement after it has become effective.

Eligibility to file on the F-10 family is restricted to issuers qualifying under the Multijurisdictional Disclosure System (MJDS), jointly adopted by the SEC and the Canadian Securities Administrators in 1991 to allow Canadian issuers to register U.S. offerings primarily on the basis of disclosure documents prepared under Canadian provincial and territorial securities law. Under General Instruction I to Form F-10 (17 CFR 239.40), the issuer generally must:

• Be incorporated in Canada or a Canadian province or territory.
• Be a foreign private issuer (Rule 405) or a Canadian Crown corporation.
• Have been subject to Canadian continuous disclosure requirements for at least 12 calendar months and be in compliance.
• Meet the public float threshold for equity, or the alternative tests for investment-grade debt or preferred securities, rights offerings, or certain exchange offers and business combinations.

On EDGAR the filer is identified by the issuer's CIK. The form must be signed by the issuer, its principal executive, financial, and accounting officers, a majority of its directors, and an authorized U.S. representative (the agent for service of process). Underwriters, selling securityholders, experts, and U.S. representatives are referenced or sign consents but are not the legal filer.

When the record is created

F-10POS is a post-effective amendment filed when the issuer must, or chooses to, modify a registration statement that is already effective. Common triggers:

• Section 10(a)(3) updates — when the prospectus is used more than nine months after the effective date, or to reflect a fundamental change. Required under the Item 512 undertakings of Regulation S-K.
• Updated Canadian disclosure — to conform the U.S. registration statement to a new Canadian base shelf prospectus, prospectus supplement, annual information form (AIF), or audited financial statements for a new fiscal year.
• Rule 462(d) exhibit-only amendments — to add exhibits such as definitive indentures, supplemental indentures, opinions, and consents of Canadian or U.S. counsel and auditors. Effective immediately upon filing.
• Rule 462(c) substantive updates — to incorporate substantive prospectus changes that may become effective on filing where the rule's conditions are met.
• New experts' consents and restated financials �� to incorporate updated audit reports, successor auditor consents, or restated financial statements (relevant under Section 11(a) liability).
• Additional securities or fee adjustments — to register additional securities, reallocate amounts, or update Exhibit 107 / Calculation of Filing Fee Tables, sometimes in conjunction with Rule 462(b).
• Deregistration of unsold securities — filed at the end of a shelf or continuous offering to remove unsold securities pursuant to the original registrant undertakings. This is one of the most common F-10POS uses observed.
• Successor registrants — where a successor adopts the registration statement following an amalgamation, arrangement, or other Canadian reorganization.

Effectiveness timing depends on the trigger. Rule 462(c) and 462(d) amendments and deregistration filings are typically effective on filing. Substantive amendments outside those rules require SEC declaration of effectiveness, though MJDS staff review is generally limited, consistent with reliance on Canadian regulatory review under Rule 467.

The dataset begins in June 2002, reflecting EDGAR submission-type history; pre-EDGAR paper MJDS amendments (1991 onward) are out of scope.

Important distinctions

• F-10POS vs F-10/A — F-10/A is a pre-effective amendment filed during SEC review; F-10POS is filed after effectiveness.
• F-10POS vs F-10EF — F-10EF is an initial registration that becomes effective on filing under Rule 467(a); F-10POS amends an already-effective F-10 or F-10EF.
• F-10POS vs S-3/F-3 amendments — U.S. domestic seasoned issuers amend through S-3 post-effective amendments and 424 supplements; non-Canadian foreign private issuers use F-1 or F-3 and their POS variants. Only MJDS-eligible Canadian issuers use the F-10 family.
• F-10POS vs F-7POS, F-8POS, F-80POS — other MJDS forms cover Canadian rights offerings (F-7) and business combinations or exchange offers (F-8, F-80), each with its own POS amendment (F-7POS, F-8POS, F-80POS). F-10POS amends only F-10/F-10EF.
• Investment companies excluded — Canadian investment companies register under the Investment Company Act on forms such as N-1A or N-2 and do not file F-10POS.
• Loss of MJDS eligibility — an issuer that ceases to qualify (for example, losing foreign private issuer status) generally cannot continue substantive updates on F-10POS and must transition to another form, though wind-down deregistration amendments may still occur.
• New offering by a different issuer — a fundamentally new offering or a different issuer requires a new F-10 or F-10EF, not an F-10POS.

How This Dataset Differs From Similar Datasets or Filings

Form F-10POS occupies a narrow slot: post-effective amendments to MJDS registration statements filed by senior Canadian issuers. The most useful comparisons are other forms in the F-10 lifecycle, sibling MJDS forms, the domestic post-effective amendment regime (POS AM), and the ongoing reporting forms used by the same filer population.

Closest related filing types and datasets

Form F-10 / F-10EF (the registrations being amended). F-10 is the original MJDS registration statement; F-10EF is the Rule 467(a) variant that becomes effective immediately on filing once the Canadian prospectus has cleared the home jurisdiction. F-10POS is filed only after one of these is effective. F-10 and F-10EF datasets capture the original offering structure and the full first-time MJDS disclosure package; F-10POS captures only later modifications (added securities, deregistrations, revised offering terms, updated risk factors, refreshed expert consents). The relationship is sequential, not overlapping.

Form F-10/A (pre-effective amendment). Same form family, opposite legal posture. F-10/A revises a registration that has not yet gone effective, typically in response to staff comments or updated financials during review. F-10POS revises a registration that is already live. Content can look similar (revised prospectus pages, new exhibits), but F-10/A is part of the review process while F-10POS modifies an active registration with current investors.

424B prospectus supplements. A 424(b) supplement delivers pricing or tranche-specific terms for a takedown off an effective F-10 shelf without amending the registration itself. F-10POS amends the registration. 424B captures takedown-level pricing data; F-10POS captures registration-level structural changes (added or deregistered securities, substantive prospectus updates).

Form F-10MEF (and S-3MEF analog). A Rule 462(b) filing that registers up to 20 percent additional securities for the same offering and becomes effective immediately as a separate new registration. Form F-10MEF, by contrast, modifies the existing registration. S-3MEF is the right comparison whenever the question is "how were extra securities added" and the answer was a 462(b) shortcut rather than a post-effective amendment.

POS AM (domestic post-effective amendment). The closest functional analog. Mechanically identical purpose: amend an already-effective registration. The decisive differences are filer population and disclosure regime. POS AM filers use U.S.-style disclosure under Regulation S-K and S-X and S-X; F-10POS filers are MJDS-eligible Canadian issuers using disclosure prepared primarily under Canadian securities law, with Canadian prospectus formats, Canadian auditor consents, and Canadian regulatory references that do not appear in POS AM filings.

Adjacent MJDS and reporting forms

Sibling MJDS post-effective amendments (F-7POS, F-8POS, F-80POS). Same regulatory mechanics, different transaction types: rights offerings (F-7), exchange offers and business combinations (F-8/F-80). F-10POS amends the general-purpose MJDS form covering ordinary registered offerings of equity, debt, and derivatives. Amendments to MJDS exchange-offer or rights-offering registrations live in those sibling datasets, not here.

Form 40-F (MJDS annual report). The Exchange Act periodic counterpart to F-10. 40-F is recurring and time-driven; F-10POS is event-driven and tied to a specific registered offering. No overlap in trigger or content.

Form 6-K (foreign private issuer current report). Furnish-only Exchange Act report for material developments disclosed in the home jurisdiction. Some F-10POS amendments incorporate facts that were also furnished on 6-K, but 6-K carries no Securities Act effect, while F-10POS formally amends a live registration.

Forms F-1, F-3, F-4 (non-MJDS foreign issuer registrations). Useful only for boundary clarification. A Canadian issuer that fails MJDS senior-issuer eligibility, or chooses not to use MJDS, registers on F-1 or F-3 and amends via POS AM. Those filings are out of scope here.

Boundary summary

F-10POS is distinct on four simultaneous dimensions:

• Filer population: MJDS-eligible Canadian issuers only.
• Legal posture: post-effective amendments only — excludes F-10/A (pre-effective), F-10 and F-10EF (original registrations), 424B (takedowns), and F-10MEF (462(b) add-ons).
• Disclosure framework: primarily Canadian-prepared, separating it from POS AM even where mechanics align.
• Trigger: offering-specific, separating it from 40-F (periodic) and 6-K (current developments).

The dataset is high-signal: each filing is a deliberate registration-level change by a senior Canadian issuer. Full lifecycle reconstruction of an MJDS offering typically requires pairing F-10POS with F-10/F-10EF, any F-10/A, 424B supplements, and the issuer's 40-F or 6-K stream.

Who Uses This Dataset

F-10POS filings are post-effective amendments to MJDS shelf registrations by Canadian issuers. The dataset is used by a narrow set of cross-border specialists in legal, capital markets, research, audit, and regulatory roles.

Cross-border securities counsel

MJDS practitioners and US co-counsel use F-10POS records as precedent when drafting their own amendments under 17 CFR 239.40. They mine exhibit indexes, opinions, auditor and qualified-person consents, fee tables, and the text incorporating updated Canadian short-form prospectuses to redline against templates and confirm what scope of change requires a POS versus a new registration.

Capital markets and DCM bankers on Canadian shelf takedowns

ECM and DCM desks structuring US tranches off MJDS shelves use the amendment text, fee tables, and updated prospectuses to track active shelf capacity, repricings, and changes to distribution mechanics. Syndicate teams reference updated underwriting exhibits to confirm lead/co-manager roles and benchmark fee structures for pitch books on Canadian bank, energy, mining, and pipeline issuers.

In-house compliance at Canadian issuers and their underwriters

Disclosure and compliance officers compare their own filing posture against peers, using accession metadata, exhibit lists, and consents to identify which events (reserves revisions, NI 43-101 updates, acquisitions, restatements) trigger amendments at comparable issuers. Underwriter compliance teams align selling-restriction memos, blue-sky work, and FINRA filings to amended shelves.

Equity and credit research analysts

Sell-side and buy-side analysts covering Canadian large-cap miners, oil and gas producers, banks, pipelines, railroads, and insurers treat F-10POS filings as signals of imminent takedowns or acquisition financing. They read updated risk factors and class-of-securities tables for dilution sizing and capital-structure modeling. Credit analysts on maple-paper desks track indenture exhibits, guarantor changes, and shelf availability for new-issue concession and relative-value work.

M&A and corporate development bankers

Bankers advising on or competing against Canadian acquirers monitor F-10POS activity as a leading indicator of deal currency. Authorized share classes, registered amounts, and revised underwriting arrangements feed financing-capacity models and timing inferences cross-referenced with rumored or announced transactions.

Auditors and consenting experts

Audit partners at large accounting networks, reserves engineers, and NI 43-101 qualified persons use exhibits to track which of their consents are live in US offerings and to benchmark consent language for quality control and engagement-letter drafting on cross-border work.

Financial data engineering teams

Engineers building filing search, alerting, and analytics products ingest the metadata.json fields (CIK, accession number, filing date, exhibit list) into normalized filing tables and parse HTML prospectuses and exhibits for fee tables, signatories, and incorporated-by-reference references. The text also feeds LLM and RAG fine-tuning and evaluation on cross-border disclosure language that differs from domestic S-3 amendments.

Regulatory and academic researchers

Staff at securities regulators and SROs, plus academic researchers in finance, law, and accounting, use the 2002-to-present series to measure MJDS utilization, issuer-type mix, and the frequency and substance of disclosure changes between F-10EF filings and their amendments. Outputs include rulemaking commentary, consultation responses, and panel studies of cost of capital and shelf-program timing for cross-listed Canadian issuers.

Specific Use Cases

The Form F-10POS Files dataset supports a small number of MJDS-specific workflows tied to post-effective amendments by Canadian issuers. The use cases below describe concrete operations against the metadata and document layers.

1. Reconstructing the lifecycle of an MJDS shelf registration

Chain F-10POS accessions to their parent F-10/F-10EF by joining on the 333- fileNo carried in each entities record. Sort the resulting set by filedAt and parse the explanatory note in each primary _f10pos.htm document to produce a per-registration timeline of structural changes (added securities, deregistrations, agent-for-service updates, selling-securityholder additions). The output is a registration-keyed event log used to audit shelf usage and to seed lifecycle reconstruction tools that join F-10POS with 424B takedowns and F-10MEF add-ons.

2. Building a precedent library of MJDS post-effective amendment exhibits

Walk every record's documentFormatFiles array and extract exhibits by type (EX-5.1 Canadian counsel opinions, EX-23.1 auditor consents, EX-25 Form T-1 statements, EX-FILING FEES Exhibit 107). Strip the <DOCUMENT> envelope, retain the inner HTML or XML, and tag each exhibit with the issuer name, SIC code, and amendment trigger lifted from the explanatory note. The result is a cross-border drafting precedent library that MJDS counsel redline against when preparing new POS amendments.

3. Monitoring auditor and qualified-person consent activity

Filter documentFormatFiles entries on type values of EX-23.x and EX-15, then parse the inner text for the consenting firm's name, the date of the underlying audit or NI 43-101 report, and the financial statements being consented to. Aggregating across the dataset produces a per-firm count of live US offerings, useful to audit partners managing engagement-letter scope and to reserves engineers tracking which technical reports remain incorporated by reference.

4. Extracting Exhibit 107 fee data for shelf-capacity tracking

For filings on or after the SEC's Filing Fee Modernization compliance date, locate the EX-FILING FEES document, parse its structured XML payload, and pull registered share or principal amounts, offering prices, and fee offsets. Combined with the issuer's cik, tickers, and sic from the entities block, this yields a normalized table of incremental shelf capacity created or deregistered by each amendment, feeding DCM and ECM coverage models for Canadian banks, miners, energy issuers, and pipelines.

5. Tagging amendment triggers for issuer-comparable analysis

Run a classifier or rule-based extractor over the explanatory note section of each primary F-10POS document, mapping free text to canonical trigger categories (selling-securityholder update, fee-calculation change, agent-for-service substitution, deregistration of unsold securities, addition of guarantor co-registrants, refreshed expert consents). Group results by issuer SIC and stateOfIncorporation to produce a benchmark of which corporate events drive post-effective amendments at comparable Canadian issuers, used by in-house disclosure officers to calibrate their own filing posture.

6. Resolving co-registrant and guarantor structures

Parse the entities array on each record, splitting companyName on its role suffix ((Filer), (Co-Registrant), (Subject)) and joining on cik across the dataset to map guarantor-issuer relationships in maple-paper debt programs. The resulting graph supports credit-analyst work on cross-guarantee structures and feeds entity-resolution pipelines that link Canadian parent issuers to their US-registered finance subsidiaries.

7. Training and evaluating models on MJDS disclosure language

Use the cleaned inner-HTML payloads (envelope stripped) of primary F-10POS documents and their attached prospectus pages as a corpus for LLM fine-tuning and RAG evaluation focused on Canadian-prepared disclosure. Because the language, exhibit conventions, and incorporated-by-reference patterns differ systematically from domestic POS AM filings, the corpus is a targeted complement for models that must answer questions about MJDS mechanics, NI 44-101/44-102 prospectus references, and Canadian counsel opinion structure.

Dataset Access

The Form F-10POS Files dataset is available through three access methods: a dataset index JSON API, a full archive download, and individual monthly container downloads.

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

This endpoint returns dataset metadata including the name, description, last updated timestamp, earliest sample date, total record count, total size, covered form types, container format, and content file types. It also returns the full dataset download URL and a list of all individual container files with per-container size, record count, updated timestamp, and download URL. Use this endpoint to monitor which containers were refreshed in the latest run and decide on a daily basis which containers to re-download. No API key is required to call this endpoint.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-6a0b-afbb-faa8550d1482",
        

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

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

          5
            "updatedAt": "2026-04-15T18:23:48.098Z",
        

          6
            "earliestSampleDate": "2002-06-01",
        

          7
            "totalRecords": 220,
        

          8
            "totalSize": 1734800,
        

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

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

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

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

          16
                "size": 13818783,
        

          17
                "records": 154,
        

          18
                "updatedAt": "2026-04-15T18:23:48.098Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

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

Downloads the complete dataset as a single ZIP archive containing all F-10POS filings from June 2002 to present. This endpoint requires an API key passed via the token query parameter.

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

Containers are partitioned by month using the path pattern YYYY/YYYY-MM.zip. Each container includes the metadata file and all documents (excluding images) for filings submitted in that month. This endpoint requires an API key passed via the token query parameter.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form F-10POS, a post-effective amendment to a Form F-10 (most often to a Form F-10EF, the immediately effective MJDS variant) filed under the Securities Act of 1933. F-10POS amendments are filed by MJDS-eligible Canadian issuers under 17 CFR 239.40 to modify a registration statement that has already become effective.

What does one record in this dataset represent?

One record corresponds to a single EDGAR submission of Form F-10POS — that is, one accession number. On disk, the record is a folder named with the 18-digit accession number (dashes stripped) containing one metadata.json file and the registrant-supplied document files (the primary F-10POS HTML document and any attached exhibits) inside their original SGML <DOCUMENT> envelopes.

Who is required to file Form F-10POS?

The filer is the Canadian issuer-registrant that has an existing, effective Form F-10 or F-10EF registration statement on file with the SEC. The issuer must qualify under the Multijurisdictional Disclosure System (MJDS) — generally, a foreign private issuer or Canadian Crown corporation incorporated in Canada, subject to Canadian continuous disclosure requirements for at least 12 months, and meeting the applicable public float or alternative MJDS thresholds.

What time period does the dataset cover?

The dataset includes all F-10POS filings submitted to EDGAR from June 2002 to present. Pre-EDGAR paper MJDS amendments dating back to MJDS adoption in 1991 are out of scope.

What file format is the dataset distributed in?

The dataset is distributed as ZIP containers partitioned by month under a YYYY/YYYY-MM.zip path pattern. Each record folder inside a container holds a metadata.json file plus HTML or TXT document files (the primary F-10POS document and any non-image exhibits), each preserved inside its EDGAR SGML <DOCUMENT> envelope. Image attachments are excluded.

How does this dataset differ from POS AM filings?

POS AM is the domestic equivalent: a post-effective amendment to an already-effective Securities Act registration. The mechanics are functionally identical, but the filer population and disclosure regime differ. POS AM filers are U.S. domestic issuers using Regulation S-K and S-X disclosure, while F-10POS filers are MJDS-eligible Canadian issuers whose disclosure is prepared primarily under Canadian securities law, with Canadian prospectus formats, Canadian auditor consents, and Canadian regulatory references that do not appear in POS AM filings.

How does F-10POS differ from F-10/A?

F-10/A is a pre-effective amendment filed during SEC review of a not-yet-effective F-10 registration, typically in response to staff comments or updated financials. F-10POS is filed only after the underlying F-10 or F-10EF has become effective, to modify a registration that is already live with current investors.