The Form 40FR12G Files Dataset collects every Form 40FR12G and Form 40FR12G/A submission accepted by EDGAR from April 2002 to the present, packaged one accession folder per filing. Form 40FR12G is the registration statement used by MJDS-eligible Canadian issuers to register a class of securities under Section 12(g) of the Securities Exchange Act of 1934 — that is, a class not listed on a U.S. national securities exchange. Each record represents a single EDGAR submission of either an initial 40FR12G registration or a 40FR12G/A amendment, and bundles a metadata.json manifest together with the primary inline-XBRL form document and all exhibit HTML/HTM/TXT/PDF files received with that submission. The filer is always the Canadian issuer itself; the disclosure package — Annual Information Form (AIF), audited IFRS or Canadian GAAP financial statements, management's discussion and analysis (MD&A), description of the registered securities, and supporting Canadian-format exhibits — is incorporated under the U.S.-Canada Multijurisdictional Disclosure System (MJDS). The dataset is distributed as monthly ZIP containers organized by year and month.
Programmatically retrieve the full list of dataset archive files, download URLs and dataset metadata.
Dataset Index JSON API
Download the entire dataset as a single archive file.
Download Entire Dataset:
Download a single container file (e.g. monthly archive) from the dataset.
Download Single Container:
The dataset contains every Form 40FR12G and Form 40FR12G/A submission filed on EDGAR since April 2002, the month EDGAR opened to MJDS Canadian filings electronically. Earlier MJDS registrations exist only on paper and are out of scope. Form 40FR12G is the MJDS Section 12(g) registration form created by the bilateral framework adopted in 1991 (SEC Release No. 33-6902), which allows eligible Canadian issuers to satisfy U.S. registration and continuous-disclosure obligations using documents prepared primarily under Canadian securities law. The 12G suffix denotes registration under Exchange Act Section 12(g), which covers classes of equity securities that are not listed on a U.S. national securities exchange (as distinct from Form 40FR12B, used for Section 12(b) listings). A 40FR12G/A carries the same body content but is filed to amend a prior 40FR12G — typically to update financial statements, correct errors, supplement exhibits, or respond to SEC staff comments.
The dataset is distributed as monthly ZIP containers organized by year and month (<year>/<year>-<month>.zip). Inside each monthly container the records are grouped into accession-number folders, one per EDGAR submission. Across the dataset as a whole the file types found are HTML, JSON, TXT, and PDF: TXT appears for older filings whose exhibits were submitted as plain ASCII text, and PDF appears when issuers attached PDF copies of technical reports or Canadian disclosure documents permitted by Rule 104 of Regulation S-T. Image files referenced from exhibits, the full EDGAR .txt complete-submission concatenation, and the XBRL data files (schema and linkbases) are not bundled into the archive; their canonical sec.gov URLs are preserved in metadata.json.
One record is one EDGAR submission of either a Form 40FR12G (initial registration of a class of securities under Section 12(g) of the Securities Exchange Act of 1934 by an MJDS-eligible Canadian issuer) or a Form 40FR12G/A (an amendment to a previously filed 40FR12G). Each record is materialized as a single accession-number folder; the folder name is the 18-digit EDGAR accession number with dashes removed (for example 000164117225007932), and it always contains a metadata.json manifest plus the HTML/HTM documents of the original EDGAR submission.
The dataset packaging has three nested layers: a year-level directory, a month-level ZIP container whose internal root is YYYY-MM/, and one or more accession folders inside that month directory. The accession folder is the canonical record-level boundary — everything inside it belongs to one filing, and every bundled artifact representing that filing is grouped there.
Substantively, a 40FR12G is a wrapper document. Item 1 requires the registrant to file the Canadian disclosure documents that, taken together, are deemed to satisfy U.S. Form 10-style registration content: the issuer's most recent Annual Information Form (AIF), the audited annual financial statements (with auditor's report and any required reconciliations), management's discussion and analysis (MD&A), and any material change reports, information circulars, or interim financial statements issued since the last AIF. Item 2 requires a description of the securities being registered (rights, preferences, restrictions, voting and dividend characteristics, transfer agent, listing status). Item 3 covers undertakings, consents, and the exhibit list. The bulk of the substantive textual disclosure therefore lives in the attached exhibits — Canadian-format documents incorporated into the form.
Inside an accession folder, three classes of content appear.
First, metadata.json — a parsed mirror of the EDGAR submission header. It is always present and serves as the manifest of every document EDGAR received, whether or not that document is bundled into the ZIP.
Second, the primary form document, typically named form40fr12g.htm (or a similar form-named HTML for amendments). For modern filings this file is an inline-XBRL XHTML document: it opens with an XML declaration, the <html> root declares the ix, ixt, xbrli, dei, ifrs-full, srt, and issuer-specific namespaces, and the body interleaves narrative XHTML with tagged facts wrapped in <ix:nonNumeric> and <ix:nonFraction> elements. The primary form file is not wrapped in an EDGAR <DOCUMENT> SGML envelope — it is delivered as a clean (X)HTML document intended to be rendered through the SEC's inline-XBRL viewer.
Third, zero or more exhibit documents. The dominant naming pattern is ex99-N.htm for EX-99.N exhibits, with N running consecutively. A single 40FR12G filing can carry dozens of exhibit attachments, particularly for natural-resource issuers whose technical reports are split across many EX-99 files. Exhibits use the legacy EDGAR SGML document envelope: each file opens with <DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, and <TEXT> headers and then contains a full <HTML>...</HTML> body, often using uppercase legacy tags. Exhibit bodies range from richly formatted narrative text (annual information forms, MD&A) to scanned-image pages whose <IMG SRC> attributes reference local .jpg files.
Image assets referenced from exhibit HTML, and the full EDGAR .txt complete-submission concatenation, are deliberately omitted from the bundled archive even though they are listed in the metadata; resolving any image reference requires fetching the corresponding sec.gov URL.
The manifest mirrors the EDGAR submission header and exposes both top-level filing identifiers and nested arrays describing every artifact of the submission.
Top-level identifier and link fields include formType ("40FR12G" or "40FR12G/A"), accessionNo (the dashed accession number), description (human-readable form caption such as "Form 40FR12G - Registration of a Class of Securities of certain Canadian issuers [Section 12(g)]"), filedAt (ISO-8601 timestamp with timezone offset), id (an opaque hash), and four canonical sec.gov URLs: linkToFilingDetails (primary form HTML), linkToTxt (full submission text file), linkToHtml (filing index page), and linkToXbrl (XBRL instance, empty when not applicable).
documentFormatFiles[] enumerates every document referenced in the EDGAR header — the primary 40FR12G, every numbered exhibit, every embedded GRAPHIC image, and the complete submission text file. Each element carries sequence (string EDGAR sequence number; the trailing complete-submission entry uses a single space), size (bytes, as a string), documentUrl (canonical sec.gov URL, using the /ix?doc= viewer prefix for inline-XBRL documents and a direct Archives/edgar/data/... path otherwise), description (a short EDGAR description, occasionally the literal string "null" when EDGAR provided none), and type (EDGAR document-type code, e.g. 40FR12G, EX-99.1 ... EX-99.N, GRAPHIC).
dataFiles[] follows the same per-element shape and lists the XBRL artifacts attached to the submission: the schema (EX-101.SCH, *.xsd), calculation linkbase (EX-101.CAL, *_cal.xml), definition linkbase (EX-101.DEF, *_def.xml), label linkbase (EX-101.LAB, *_lab.xml), presentation linkbase (EX-101.PRE, *_pre.xml), and the extracted XBRL instance (*_htm.xml). These XBRL files are not bundled into the ZIP; only their canonical URLs are recorded.
entities[] describes the parties on the filing. Each element typically captures companyName with a parenthesized role suffix such as "(Filer)", cik, type (the role/form code on this filing, e.g. 40FR12G), act ("34" for the Exchange Act), fileNo (SEC file number under the 000- block reserved for Section 12(g) registrants), filmNo, stateOfIncorporation (a two-character code in which Canadian province codes such as A0 for Alberta, A1 for British Columbia, and A6 for Ontario dominate), and a tickers array.
seriesAndClassesContractsInformation[] exists structurally but is empty for ordinary 40FR12G filings; it carries content only when the filing involves registered investment-company series or contracts.
The substantive disclosure in a 40FR12G is delivered through a small number of demarcated content blocks, most of which are physically materialized as separate exhibits.
The Annual Information Form (AIF) is the central narrative document. Prepared under Canadian National Instrument 51-102, it parallels the description-of-business and risk content that a U.S. issuer would put in Items 1, 1A, 2, and 3 of Form 10-K. Typical sections inside the AIF are corporate structure and intercorporate relationships, three-year general development of the business, description of the business by segment (products and services, production and operations, specialized skill and knowledge, competitive conditions, intangible properties, cycles, economic dependence, environmental protection, employees, foreign operations), risk factors, dividends and distributions, capital structure, market for securities, prior sales, escrowed securities and securities subject to contractual restriction on transfer, directors and executive officers, audit committee information, legal proceedings and regulatory actions, interest of management and others in material transactions, transfer agents and registrars, material contracts, interests of experts, and additional information.
The audited annual financial statements form a second core block. They are prepared under International Financial Reporting Standards (IFRS) for most Canadian issuers (mandatory for public companies since 2011) or, for pre-2011 filings and certain exempt filers, under Canadian GAAP. The block contains the auditor's report, statement of financial position, statement of comprehensive income (or income and OCI), statement of changes in equity, statement of cash flows, and the accompanying notes. For older filings, a U.S. GAAP reconciliation note accompanied the statements; this requirement was eliminated for IFRS filers after the SEC's 2007/2008 amendments allowing IFRS without reconciliation for foreign private issuers.
Management's Discussion and Analysis (MD&A), prepared under Canadian Form 51-102F1, supplies the narrative analysis of operations, liquidity, capital resources, off-balance-sheet arrangements, related-party transactions, fourth-quarter information, proposed transactions, critical accounting estimates, and disclosure-controls/internal-controls discussion. It is filed as a separate exhibit rather than inline with the financials.
The description of the securities being registered is delivered in the body of the form itself (Item 2) and lists the title and class of the securities, voting rights, dividend rights, liquidation preferences, redemption and conversion features, registration rights, and any anti-takeover or restriction-on-foreign-ownership provisions arising under Canadian corporate law.
Exhibits typically include consents of the auditors and any other named experts, the issuer's certificate of incorporation/articles and by-laws or equivalent constating documents (where material contracts incorporate them), recent material change reports, recent management information circulars (proxy circulars) and interim unaudited financial statements with their accompanying MD&A, and any technical or qualifying reports required by Canadian instruments such as NI 43-101 (mineral projects) or NI 51-101 (oil and gas activities). For natural-resource issuers, the technical-report exhibits can run to dozens of separate EX-99.N files, which is why a single 40FR12G accession folder may carry a very long sequence of exhibit HTMLs.
A signature page closes the form, signed under the laws of the home jurisdiction by an authorized officer or by a duly authorized representative resident in the United States, accompanied by the date and capacity.
Although the dataset begins in April 2002 (when EDGAR was opened to MJDS Canadian filings) and runs to the present, the substantive content of a 40FR12G has evolved in several material ways.
Through 2010, audited financial statements were generally prepared under Canadian GAAP, accompanied by a Canadian-to-U.S. GAAP reconciliation note for filings made before the SEC's elimination of the reconciliation requirement for foreign private issuers using IFRS as issued by the IASB. Beginning in 2011, mandatory IFRS adoption by Canadian public companies caused the financial-statement block in 40FR12G filings to switch to IFRS, which is why modern primary documents declare the ifrs-full namespace.
The AIF and MD&A content evolved in step with Canadian NI 51-102 and its companion Form 51-102F1/Form 51-102F2 instructions, including expanded disclosure on internal control over financial reporting (NI 52-109 certification regime), audit committee composition (NI 52-110), and corporate governance practices (NI 58-101). For natural-resource issuers, technical-report exhibit content shifted with successive amendments to NI 43-101 (mineral disclosure) and NI 51-101 (oil and gas), each of which restructured the qualified-person attestation, certification, and report-form requirements.
On the U.S. side, the SEC's interactive-data rules and their phased extension to foreign private issuers brought XBRL tagging into 40FR12G filings; for the most recent filings, the primary form is delivered as inline-XBRL with the dei and ifrs-full taxonomies. Pay-versus-performance, cybersecurity, and recently adopted climate disclosures generally do not flow into 40FR12G content because the form relies on Canadian disclosure documents rather than U.S. Items, but where Canadian disclosure rules introduce parallel requirements (climate-related disclosure under CSA proposals, ESG content within MD&A) those are surfaced inside the AIF and MD&A exhibits.
The earliest 40FR12G filings in the dataset (2002-2003) are dominated by plain ASCII .txt exhibits, occasional simple .htm files, and frequent PDF attachments where preserving Canadian formatting mattered (auditor reports, technical reports, certified copies). Through the mid-2000s, HTML progressively replaced ASCII as the default exhibit format, and by the 2010s nearly all submissions are HTML-only with PDF reserved for legacy or graphic-heavy attachments. Following the SEC's adoption of inline-XBRL for foreign private issuers, the primary form file in modern submissions is an inline-XBRL XHTML document; older filings carry no XBRL at all, and intermediate-era filings may include a separate XBRL instance and linkbase set rather than inline tagging. Throughout the entire date range, exhibit files carry the EDGAR SGML <DOCUMENT> envelope while the primary form is delivered as a clean HTML/XHTML body, so any parser must accept both wrappers.
Several details matter for downstream extraction. The accession-folder boundary is the only safe iteration unit; record counts elsewhere often reflect documents-per-filing rather than filings-per-month and should not be used as filing counters — consumers iterating filings should iterate accession sub-folders.
The metadata.json manifest is authoritative for the inventory of EDGAR-side assets, including those not bundled into the archive, so consumers must consult it rather than the directory listing when reasoning about what the EDGAR submission contained. The literal string "null" appears in description fields where EDGAR supplied no description — it is not a JSON null and must be normalized in code.
The formType field cleanly disambiguates initial filings (40FR12G) from amendments (40FR12G/A). Amendments are otherwise structurally identical: same folder shape, same primary-form anatomy, same exhibit-numbering scheme; only the content within the exhibits typically differs.
Exhibit numbering follows EDGAR's EX-99.N convention and reflects the order in which documents were attached to the submission, not the substantive type of each exhibit. Identifying which exhibit holds the AIF, which holds MD&A, and which holds the audited financials therefore requires reading either the EDGAR description field on the corresponding documentFormatFiles[] entry or the exhibit body itself.
Because 40FR12G content is grounded in Canadian disclosure documents incorporated as exhibits, the most extractable narrative and financial content lives in the EX-99.* files rather than the primary form itself. The primary form is largely a cover document whose principal substantive role is to list the incorporated Canadian documents and describe the securities being registered; extraction pipelines targeting business descriptions, risk factors, MD&A, or financial statements should plan to read the exhibits, not the wrapper form.
The filer is always the Canadian issuer itself, registering a class of its own securities with the SEC under MJDS. The issuer signs and submits through its authorized officers, paired with a Form F-X appointing a U.S. agent for service of process.
To use Form 40FR12G, the issuer must satisfy MJDS eligibility under the General Instructions to Form 40-F (which Form 40FR12G adopts for content and eligibility) and the SEC's MJDS rules adopted in Release No. 33-6902 (1991):
Underwriters, selling shareholders, affiliates, officers, directors, and auditors are not filers; they appear as parties referenced inside the registration statement. Their own U.S. reporting obligations (Schedule 13D/G, Section 16 forms, etc.) are separate filings.
Form 40FR12G is event-driven, not periodic. A record is generated when an eligible Canadian issuer registers a class of equity securities under Section 12(g) of the Exchange Act, i.e., a class that is not being listed on a U.S. national securities exchange (an exchange listing would instead route through Form 40FR12B under Section 12(b), or commonly Form 8-A).
Two trigger paths produce a 40FR12G record:
Form 40FR12G is filed (not furnished) and becomes effective automatically 60 days after filing under Section 12(g)(1), unless withdrawn or amended in a manner that resets the clock. Once effective, the issuer enters Exchange Act reporting and begins filing Form 40-F annually and furnishing Form 6-K.
A Form 40FR12G/A record arises when the registrant amends the registration statement, typically pre-effectiveness to update Canadian disclosure documents (e.g., a newly filed AIF or revised audited financials), to respond to SEC staff comments, or to cure deficiencies. Post-effective amendments are uncommon but possible.
Form 40FR12G sits at the crossing of three SEC regimes: Exchange Act Section 12 registration, the U.S.-Canada Multijurisdictional Disclosure System (MJDS), and foreign private issuer reporting. Several adjacent forms can be confused with it. The most relevant comparisons are 40FR12B, 40-F, the F-series MJDS prospectuses, Form 10, Form 20-F, Form 8-A, Form F-X, and Form 6-K.
Form 40FR12B (and 40FR12B Files Dataset). The nearest sibling. Identical disclosure package (Canadian AIF, MD&A, IFRS audited financials), identical MJDS eligibility, identical filer population (Canadian issuers). The only meaningful split is the registration trigger: 40FR12B is filed under Section 12(b) when securities will list on a U.S. national exchange (NYSE, Nasdaq, NYSE American); 40FR12G is filed under Section 12(g) when registration is driven by the asset and shareholder thresholds, voluntary registration, or off-exchange trading. To capture the full MJDS Exchange Act registration population, both datasets must be combined.
Form 40-F (40-F Files Dataset). The MJDS annual report that follows registration. Same disclosure inputs (AIF, MD&A, IFRS financials), but 40-F is a recurring periodic obligation, not a registration event. 40FR12G is the one-time entry point into Exchange Act reporting; 40-F is what the issuer files every year afterward. Use 40-F for time-series financials; use 40FR12G to identify the moment of entry.
Form F-10 / F-7 / F-8 / F-80. MJDS forms under the Securities Act of 1933, used to register offerings of securities (primary, secondary, rights, exchange, business combination). They share Canadian-disclosure reliance and MJDS eligibility with 40FR12G but operate under a different statute: Securities Act offering registration vs. Exchange Act class registration. An F-10 prospectus and a 40FR12G can coexist for the same issuer; they are not substitutes.
Form 10. The U.S. domestic Section 12(g) registration form. Same statutory anchor as 40FR12G, but the disclosure content is structurally different: Form 10 demands the full Regulation S-K item set and U.S. GAAP financials, while 40FR12G accepts the Canadian AIF, Canadian-MD&A, and IFRS financials prepared under Canadian rules. Eligibility is the decisive divider: only MJDS-qualifying Canadian issuers may use 40FR12G; everyone else uses Form 10.
Form 20-F. The non-MJDS FPI form, available to foreign private issuers from any jurisdiction. Used as both a Section 12 registration statement and an annual report. Content scope is broader and more U.S.-styled (full FPI item set, IFRS-as-issued-by-IASB or reconciled financials). Canadian issuers that fail MJDS criteria (insufficient reporting history or public float) fall back to 20-F. 40FR12G is therefore a narrower, MJDS-only path with a Canadian-formatted disclosure package.
Form 8-A (8-A12G). A short-form Section 12 registration that incorporates by reference a registration statement already on file. Targets the same statutory outcome as 40FR12G but carries no substantive disclosure of its own. Some Canadian MJDS issuers pair an 8-A with an F-10 instead of filing 40FR12B/40FR12G; in that path, the substantive content lives in the F-10, not the 8-A.
Form F-X. The appointment of agent and consent to service of process. Procedural, not substantive. F-X is filed alongside 40FR12G, 40FR12B, 40-F, and F-series prospectuses but contains no issuer disclosure. Pair the two when reconstructing a complete MJDS filing package; do not treat F-X as a content source.
Form 6-K. The FPI current report/interim reporting form. Recurring and event-driven, not a registration document. After 40FR12G effectiveness, interim and material disclosures flow through 6-K and the annual report flows through 40-F. 6-K presupposes Exchange Act registration; it does not establish it.
Form 40-APP (not a real neighbor). Despite the shared "40" prefix, 40-APP is an Investment Company Act of 1940 exemptive application. No MJDS, no Canadian-issuer connection, no overlap in content or filer population. Adjacent only in alphanumeric EDGAR listings.
The 40FR12G dataset isolates one specific event: Section 12(g) registration of a class of securities by an MJDS-eligible Canadian issuer using a Canadian-style disclosure package, where no U.S. exchange listing drives the filing. It is distinguished from 40FR12B by statutory subsection and listing context, from 40-F by being a one-time entry rather than a recurring report, from the F-series by being Exchange Act rather than Securities Act registration, from Form 10 and 20-F by filer eligibility and disclosure format, from 8-A by carrying its own substantive content, from F-X by being substantive rather than procedural, and from 6-K by being a registration document rather than ongoing reporting. Used together with 40FR12B, 40-F, F-X, and the F-series, it completes the MJDS picture; on its own, it pinpoints Canadian Section 12(g) entrants without a U.S. listing.
The user base is small but well-defined, drawn together by the need for a complete, consistently structured corpus of Canadian-issuer Section 12(g) registrations.
Counsel advising on MJDS eligibility and drafting use the dataset as a precedent library. They mine the AIF, securities description, exhibit list, auditor consents, and 40FR12G/A amendment patterns to model registration structure, eligibility representations, and reconciliation language for new candidates — replacing ad-hoc precedent searches.
Deal teams sequencing a U.S. registration for a TSX/TSXV-listed issuer use peer 40FR12G filings to scope feasibility and timeline. AIF business and risk disclosure, MD&A trend analysis, audited statements, and the share-capital description establish the disclosure benchmark; filing-date metadata and 40FR12G/A cadence inform expected SEC review duration and comment-letter triggers.
Diligence teams evaluating Canadian targets — especially in mining, energy, biotech, and tech — treat the 40FR12G as a single consolidated public snapshot. They pull the AIF for corporate history and material contracts, audited statements for historical financials, MD&A for liquidity narrative, and exhibits for articles, bylaws, and material agreements. CIK and file number link the registration to subsequent 40-F and 6-K filings for a longitudinal view across the deal window.
Analysts covering newly registered Canadian small- and mid-caps anchor models on the AIF (segment operations, customer concentration, regulatory exposure), MD&A, and audited statements. The securities description clarifies dual-class structure, dilution, and warrant overhang. Mining and petroleum engineers extract NI 43-101 and NI 51-101 technical reports for qualified-person sign-offs, resource categories, grade-tonnage tables, reserve classifications, and recovery assumptions feeding NAV and resource-life models.
Legal and disclosure staff at Canadian reporting issuers benchmark their own MJDS drafts against peers — AIF format, MD&A reconciliation language, auditor consents, signature blocks, cover-page structure — and review how peers responded to staff comments and refreshed exhibits across 40FR12G/A amendments.
Policy staff and academics studying MJDS uptake aggregate filings by year, industry, and province of incorporation to track Section 12(g) registration patterns since 2002, amendment frequency, and correlations with capital-market conditions. CIK, file number, and filing dates anchor the longitudinal series; the underlying documents support qualitative analysis of disclosure convergence.
Onboarding analysts at broker-dealers and prime brokers verify corporate identity, jurisdiction of incorporation, fiscal year end, agent for service of process, directors and officers, and authorized capital for Canadian issuers requesting U.S. market access. They combine EDGAR metadata and cover-page fields with AIF disclosures on ownership concentration, related-party arrangements, and material litigation.
Reference-data and fundamentals teams at data vendors map 40FR12G CIKs to Canadian SEDAR+ identifiers, link initial registrations to downstream 40-F, 6-K, and F-series filings, and tag issuers by MJDS pathway. Audited statements and MD&A feed standardized fundamentals products; structured metadata drives corporate-actions and identifier-mapping pipelines.
Teams building retrieval and document-understanding systems for cross-border equity research use the corpus to train and evaluate section classification, risk-factor extraction, reserve-table parsing, and Canadian-vs-U.S. accounting-language normalization. Stable accession numbers, CIKs, and file numbers support reproducible retrieval.
Governance and activist teams map share structure, voting arrangements, related-party disclosures, executive-compensation references, and Canadian-style governance practices from the description of securities and AIF — inputs into engagement strategy, voting recommendations, and contested-situation work.
Cross-border counsel preparing a 40FR12G for a Canadian client query the corpus by entities[].stateOfIncorporation (province codes such as A0, A1, A6) and industry to pull comparable initial filings. They diff the Item 2 securities description, eligibility representations, exhibit lists, and 40FR12G/A amendment chains against the candidate's facts to draft cover language, schedule auditor consents, and anticipate which exhibits will need refreshing. The output is a marked-up precedent set and a checklist of expected staff-comment topics.
Mining and petroleum analysts identify resource issuers in the dataset, then walk documentFormatFiles[] to enumerate the long EX-99.N technical-report sequences that natural-resource 40FR12G filings carry. They extract qualified-person certifications, mineral resource and reserve categories, grade-tonnage tables, recovery assumptions, and oil-and-gas reserve classifications into structured tables that feed NAV models and resource-life forecasts at the moment of U.S. registration.
Reference-data and fundamentals teams use cik, fileNo, and filedAt to anchor the U.S. reporting timeline of each issuer at the 40FR12G event, then join forward to the issuer's 40-F annual reports, 6-K interim filings, and any later F-series prospectuses. The result is an MJDS issuer master table — registration date, province, ticker, fiscal year end, agent for service — that drives identifier mapping (CIK to SEDAR+), corporate-actions pipelines, and entity hierarchies.
Document-AI teams parse the SGML-wrapped EX-99.* exhibits to isolate the AIF risk-factor section and the MD&A liquidity-and-capital-resources discussion across the full population. The extracted text is used to train and benchmark section classifiers, evaluate Canadian-vs-U.S. accounting-language normalization, and run topic models on risk evolution from the Canadian-GAAP era (pre-2011) into the IFRS era — using formType to separate initial filings from amendment-driven content updates.
Buy-side diligence teams treat a target's 40FR12G accession folder as a consolidated public-record snapshot at the moment of U.S. entry. They pull the AIF for corporate history, three-year general development, material contracts, and legal proceedings; the audited IFRS statements for the historical financial baseline; the MD&A for liquidity and related-party narrative; and the share-capital description for dual-class, warrant, and anti-takeover features — then compare the snapshot against later 40-F filings to surface what changed during the deal window.
Policy researchers and academics aggregate the dataset by filedAt year, province, and industry to track Section 12(g) registration volume since EDGAR opened to MJDS in April 2002, the share of filings that go effective without amendment, and the median number of 40FR12G/A iterations per registrant. The longitudinal series is paired with capital-market conditions and Canadian regulatory changes (NI 51-102, NI 43-101, NI 52-109) to study disclosure convergence and MJDS attrition into Form 20-F.
Broker-dealer onboarding analysts use metadata.json and the cover-page fields to verify legal name, CIK, file number, jurisdiction of incorporation, agent for service, and authorized capital for a Canadian counterparty. They cross-check against the AIF's directors-and-officers section, ownership concentration, and material-litigation disclosure to complete the counterparty-risk file before opening a prime-brokerage or market-access account.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-40fr12g-files.json
Returns dataset-level metadata (name, description, last updated timestamp, earliest sample date, form types, container format, file types) along with the full archive download URL and a list of container files. Each container entry includes its key, size, record count, updated timestamp, and download URL. Poll this endpoint to detect which containers changed in the most recent refresh and download only those that were updated. This endpoint does not require an API key.
Example response:
1
{
2
"datasetId": "1f13365b-9ae0-6a40-9449-dc3051f12cd6",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-40fr12g-files.zip",
4
"name": "Form 40FR12G Files Dataset",
5
"updatedAt": "2026-04-16T08:39:55.771Z",
6
"earliestSampleDate": "2002-04-01",
7
"totalRecords": 2170,
8
"totalSize": 41148258,
9
"formTypes": ["40FR12G", "40FR12G/A"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["HTML", "JSON", "TXT", "PDF"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-40fr12g-files/2026/2026-04.zip",
15
"key": "2026/2026-04.zip",
16
"size": 412355,
17
"records": 6,
18
"updatedAt": "2026-04-16T08:39:55.771Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-40fr12g-files.zip?token=YOUR_API_KEY
Downloads the complete dataset as a single ZIP archive containing every monthly container from April 2002 to the current month. Requires an API key.
Example:
curl -o form-40fr12g-files.zip "https://api.sec-api.io/datasets/form-40fr12g-files.zip?token=YOUR_API_KEY"
Download Single Container: https://api.sec-api.io/datasets/form-40fr12g-files/2026/2026-04.zip?token=YOUR_API_KEY
Containers are organized by year and month using the <year>/<year>-<month>.zip path pattern shown in each container's downloadUrl. Use this route to fetch a specific monthly archive instead of the entire dataset. Requires an API key.
Example:
curl -o 2026-04.zip "https://api.sec-api.io/datasets/form-40fr12g-files/2026/2026-04.zip?token=YOUR_API_KEY"
The dataset covers Form 40FR12G and its amendments Form 40FR12G/A. Form 40FR12G is the registration statement filed by MJDS-eligible Canadian issuers to register a class of securities under Section 12(g) of the Securities Exchange Act of 1934, where the class is not listed on a U.S. national securities exchange.
One record is one EDGAR submission of either an initial 40FR12G or a 40FR12G/A amendment, materialized as a single accession-number folder. The folder name is the 18-digit EDGAR accession number with dashes removed, and it always contains a metadata.json manifest plus the HTML/HTM documents of the original EDGAR submission, including the primary inline-XBRL form file and all exhibit files.
The filer is always the Canadian issuer itself. To use Form 40FR12G, the issuer must satisfy MJDS eligibility under the General Instructions to Form 40-F: incorporated under the laws of Canada or any Canadian province or territory, qualifying as a foreign private issuer under Exchange Act Rule 3b-4, a reporting issuer in good standing under Canadian provincial or territorial securities laws (typically with at least 12 months of continuous-disclosure history), and meeting the applicable public-float test for most equity-class uses.
Form 40FR12G is event-driven, not periodic. Mandatory filings are triggered when, on the last day of the issuer's most recent fiscal year, total assets exceed USD 10 million and the class is held of record by 2,000 persons or 500 non-accredited holders, with registration due within 120 days after that fiscal year-end. Voluntary filings occur when an eligible Canadian issuer elects to register without being compelled, often to support OTC quotation, U.S. resale activity, or full Exchange Act reporting status without an exchange listing.
40FR12B and 40FR12G share the same MJDS disclosure package, the same eligibility rules, and the same Canadian filer population. The split is the registration trigger: 40FR12B is filed under Section 12(b) when securities will list on a U.S. national exchange (NYSE, Nasdaq, NYSE American), while 40FR12G is filed under Section 12(g) when registration is driven by the asset and shareholder thresholds, voluntary registration, or off-exchange trading. Combine both datasets to capture the full MJDS Exchange Act registration population.
The dataset begins in April 2002, the month EDGAR opened to MJDS Canadian filings electronically, and runs to the present. Earlier MJDS registrations exist only on paper and are out of scope.
The dataset is distributed as monthly ZIP containers organized under a <year>/<year>-<month>.zip path pattern. Inside each container the records are accession-number folders, each holding metadata.json and the HTML/HTM documents of the EDGAR submission. Across the dataset the file types found are HTML, JSON, TXT, and PDF; image files, the full EDGAR .txt complete-submission concatenation, and XBRL data files are not bundled and are referenced only by URL in metadata.json.