Form NTN 20F Files Dataset

The Form NTN 20F Files Dataset collects every EDGAR submission classified as form type NTN 20F — late-arriving Rule 12b-25 notifications of inability to timely file an annual report on Form 20-F. Each record represents one foreign private issuer's after-the-deadline notice that its Form 20-F annual report will not be submitted on time, and it bundles the structured EDGAR metadata envelope with the plain-text content of every non-image document in the original submission. EDGAR auto-reclassifies an NT 20-F submission as NTN 20F when the Rule 12b-25 notice itself arrives after the original 20-F due date has elapsed — the leading N flags the notice as untimely. Coverage begins on 1996-07-01 and runs to the present, and the dataset is delivered as monthly ZIP containers holding JSON metadata and TXT document payloads.

Update Frequency
Daily
Updated at
2026-04-16
Earliest Sample Date
1996-07-01
Total Size
19.0 KB
Total Records
4
Container Format
ZIP
Content Types
TXT, JSON
Form Types
NTN 20F

Dataset APIs

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:

Dataset Files

6 files · 19.0 KB
Download All
2002-08.zip22 B0 records
2002-07.zip22 B0 records
2002-01.zip22 B0 records
2001-04.zip3.1 KB1 records
2001-03.zip8.8 KB1 records
1996-07.zip7.1 KB2 records

What This Dataset Contains

The dataset is built from Form 12b-25, the SEC's standard "Notification of Late Filing" instrument promulgated under Rule 12b-25 of the Securities Exchange Act of 1934. A registrant uses Form 12b-25 to invoke an automatic short extension — 15 calendar days for annual reports (10-K, 20-F, 11-K, N-CEN) and 5 calendar days for quarterly reports (10-Q, 10-QSB) — by checking the relevant box on the form's report-type matrix. When the extension is invoked for a Form 20-F, EDGAR ordinarily labels the submission NT 20-F. If the Rule 12b-25 notice is itself received after the original 20-F deadline has already elapsed, EDGAR automatically reclassifies the submission to NTN 20F. The leading N flags that the notice was non-timely; the underlying paper form, its instructions, and its content requirements are unchanged.

Because Form 20-F is filed only by foreign private issuers, every record in this dataset originates from a foreign private issuer, and the population is intrinsically tiny — late-late notices for an annual report that itself is filed only by FPIs are rare events. The auto-reclassification is purely an EDGAR header-side relabel: the document body, the check-box selection ([X] Form 20-F), and the registrant's representation in Part II that the report will be filed within the 15-day extension window remain on the document even though the rebadging logic implies the original deadline had already passed at the moment of submission. The contradiction is structural, not editorial, and is a useful interpretive marker.

The dataset is packaged as monthly ZIP archives organized by year, with paths of the form YYYY/YYYY-MM.zip. Each accession is preserved as a folder containing a single metadata.json envelope and one or more sequentially-numbered document-N.txt files; image attachments from the original EDGAR submission are excluded.

Content Structure of a Single Record

1. What one record represents

One record is a single EDGAR submission classified by EDGAR as form type NTN 20F — that is, one Rule 12b-25 notice of inability to timely file an annual report on Form 20-F where the notice itself arrived after the original 20-F due date. Each record is the entire submission as accepted by EDGAR: a structured metadata envelope describing the submission, filer, and document index, together with the textual content of every non-image document that made up the submission. The unit of identity is the EDGAR accession number; one accession equals one record equals one foreign private issuer's late-late notice for a specific Form 20-F annual reporting period.

2. Container and per-record file layout

Each monthly archive's root contains a single folder named after the period (YYYY-MM/), and inside that period folder every accepted submission for the month sits in its own child folder whose name is the EDGAR accession number with hyphens stripped — accession 0000950112-96-002279 becomes folder 000095011296002279. Many monthly archives contain no entries at all, because months without an NTN 20F submission produce no records; this is a structural property of an exceptionally sparse form type, not a packaging defect.

Each accession folder contains exactly two kinds of files and only two:

  • exactly one metadata.json — the JSON envelope, always present.
  • one or more sequentially-numbered document files named document-1.txt, document-2.txt, and so on, where the numbering follows the original EDGAR <SEQUENCE> ordering of the submission's documents.

Image attachments (GIF, JPG, etc.) that may have accompanied the original EDGAR submission are excluded from the dataset; everything else from the submission is preserved as text. For NTN 20F, the typical realisation is a single document-1.txt carrying the Form 12b-25 narrative, because Rule 12b-25 notices rarely include exhibits beyond an optional accountant's statement under Rule 12b-25(c) or a Part IV(3) variance attachment, either of which — when present as a separately sequenced item in the original submission — appears as document-2.txt.

3. metadata.json — the structured envelope

metadata.json is a flat JSON object that captures EDGAR header information for the submission and a normalized index of its documents. The top-level fields are:

  • formType — always "NTN 20F" for this dataset.
  • accessionNo — the canonical hyphenated EDGAR accession identifier (e.g., "0000950112-96-002279").
  • id — a stable 32-character hex hash uniquely identifying the record within the dataset.
  • filedAt — an ISO-8601 timestamp with timezone offset marking the moment EDGAR accepted the submission.
  • periodOfReport — the fiscal period-end of the underlying Form 20-F annual report that the notice concerns (e.g., "1995-12-31"); this mirrors the For Period Ended: line on the 12b-25 face.
  • description — the human-readable form label, "Form NTN 20F - Notices of Late Filings of Form 20-F".
  • linkToFilingDetails — URL of the registrant's filing-archive folder on SEC.gov.
  • linkToHtml — URL of the EDGAR filing-index HTML page for this accession.
  • linkToTxt — URL of the complete-submission text file (the SGML-wrapped aggregate of the entire submission) on SEC.gov.
  • linkToXbrl — an empty string; Form 12b-25 carries no XBRL data and Form NTN 20F has never been subject to XBRL tagging.
  • documentFormatFiles — an array of objects, one per item in the original submission. Each entry carries sequence, size (bytes, as a string), documentUrl, type, and a textual description. The first entry corresponds to the Form 12b-25 document itself (type: "NTN 20F" or, for older filings, the original NT 20-F type label). A trailing entry with empty sequence and type and the description "Complete submission text file" references the aggregate SGML envelope EDGAR generates for the whole submission.
  • entities — an array of filer-entity objects. Each entity object carries cik, companyName (suffixed with the EDGAR role, e.g., "COMET SOFTWARE INTERNATIONAL LTD (Filer)"), fileNo (the SEC-assigned file number), filmNo (the EDGAR film/microfiche number), act (the Exchange Act section under which the filing is made, typically "34"), fiscalYearEnd in MMDD form, sic (the SIC code with its industry text, with HTML entities such as &amp; left intact), and type (the EDGAR form-type label associated with the entity's role on this submission). The block can in principle hold multiple entity objects for joint filings, although NTN 20F submissions are typically single-filer.
  • seriesAndClassesContractsInformation — an array, empty for this form; this field is only meaningful for fund-related forms.
  • dataFiles — an array, empty for this form; there are no XBRL instances, schemas, or other structured data exhibits.

4. document-N.txt — the Form 12b-25 text payload

Each document-N.txt is a plain-text rendering of the corresponding sequenced document from the original EDGAR submission. The file preserves the inner text as filed, including legacy <PAGE> page-break markers, but it does not retain the outer EDGAR SGML wrapper (<DOCUMENT><TYPE>...<SEQUENCE>...<FILENAME>...<TEXT>...</TEXT></DOCUMENT>). The SGML envelope exists only in the aggregate complete-submission .txt on SEC.gov referenced by linkToTxt; the per-record file holds just the inner payload.

Form 12b-25 itself follows a fixed, instruction-defined four-part layout that is consistent across every record in the dataset:

  • Heading and report-type check-box matrix. The face identifies the SEC filing and presents a matrix of late-notice targets — Form 10-K, 10-KSB, 20-F, 11-K, 10-Q, 10-QSB, N-SAR, and others — with the relevant box marked. For every record in this dataset the marked box is [X] Form 20-F.
  • For Period Ended. A single line giving the fiscal period-end of the late annual report. This value is mirrored into metadata.json -> periodOfReport.
  • Part I — Registrant Information. The full registrant name, any former name used in the immediately preceding 12 months, and the address of the principal executive office. Because the population is foreign private issuers, addresses are non-US (e.g., Tel Aviv, Israel; Roadtown, Tortola, British Virgin Islands), and the prior-name field occasionally reflects cross-border re-domiciliations.
  • Part IIRules 12b-25(b) and (c). A small block of check-box representations: that the report could not be filed on time without unreasonable effort or expense, that the report will be filed within the prescribed extension window (15 calendar days for an annual report on Form 20-F), that the requirements of Rule 12b-25(b) are or will be met, and that any accountant's statement contemplated by Rule 12b-25(c) — required when an audit-related delay has caused the lateness — is or will be attached.
  • Part III — Narrative. Free-form prose explaining in reasonable detail the reasons the Form 20-F could not be filed on time. Common substantive themes include incomplete audits, restatement work in progress, transitions in auditors or accounting personnel, cross-border logistical delays, unresolved valuation or going-concern questions, and impacts of corporate transactions. The narrative ranges from a single sentence (sometimes only "See attached." with the substantive explanation appended later in the same document) to several paragraphs of operational and audit-status detail.
  • Part IV — Other Information. Three numbered items: (1) the name and telephone number of a contact person at the registrant, (2) a yes/no statement on whether all other reports required under Section 13 or 15(d) of the Securities Exchange Act of 1934 have been filed during the preceding 12 months (with explanatory text required if no), and (3) a yes/no statement on whether any significant change in results of operations from the corresponding period of the prior year is anticipated, with an attached narrative and quantitative explanation if yes.
  • Signature block. The closing signature: the date, the printed name preceded by /s/ denoting an electronic signature, and the signer's title at the registrant.
  • Optional Part IV(3) attachment. When item (3) of Part IV is answered affirmatively, a quantitative attachment follows the signature, typically presenting comparative figures for revenue, operating loss, net loss, R&D expense, or other income-statement line items, with prose interpreting the variance. When this attachment is filed as a separately sequenced EDGAR document it appears as document-2.txt; when it is concatenated into the same submitted document it sits below the signature in document-1.txt.
  • Optional accountant's statement. When Rule 12b-25(c) applies, a short statement signed by the registrant's independent accountants — confirming the audit-related cause of the delay or the accountants' inability to complete the audit by the deadline — is attached, either inline at the end of document-1.txt or as a further sequenced document.

5. What the dataset record includes

Each record bundles the structured metadata.json envelope and the textual content of every non-image document from the original EDGAR submission, with documents named by their original sequence number. For NTN 20F this is almost always just the Form 12b-25 itself, optionally accompanied by an accountant's statement or a Part IV(3) variance attachment when these were filed as separate sequenced documents.

6. What is outside the record

Image files attached to the original EDGAR submission (signature scans, logos, charts) are excluded. The outer EDGAR SGML <DOCUMENT> wrappers from the aggregate complete-submission text are not carried into the per-document text files; the dataset stores only the inner text payload. The aggregate complete-submission .txt on SEC.gov is referenced by URL in metadata.json -> linkToTxt but is not stored as a separate file inside the accession folder. The Form 20-F itself — the late annual report whose tardiness this record notifies — is a separate filing under a different EDGAR submission type and is not part of the record; only the notice of lateness is here.

7. Stability of the layout over time

The Form 12b-25 instruction set has been stable across the dataset's coverage from 1996 to the present: the report-type check-box matrix, the four-part structure (Registrant Information; Rule 12b-25(b) and (c) representations; Narrative; Other Information), and the signature and optional-attachment conventions have not materially changed. The [X] Form 20-F selection that defines this dataset's scope therefore appears in identical form in early-1990s and recent submissions. The packaging of each record — metadata.json plus sequentially-numbered document-N.txt files inside an accession-named folder — is uniform across the entire dataset, and the textual presentation of Form 12b-25 has not migrated to HTML or XBRL: NTN 20F submissions remain plain-text renderings throughout, because Form 12b-25 has never been subject to inline XBRL tagging or required HTML formatting.

8. Interpretation and extraction notes

  • The NTN 20F label is an EDGAR header-side reclassification artefact, not a separate form. The underlying instrument is still Form 12b-25 with the Form 20-F box checked. Treat the NTN prefix as evidence that the original 20-F deadline had already passed at the moment the notice was accepted, and read Part II's "will be filed within the 15-day extension" representation in that light.
  • The periodOfReport field is the fiscal period-end of the missing 20-F annual report, not the date the notice was filed; filedAt carries the notice's own filing timestamp. The lag between periodOfReport and filedAt is generally larger than the Rule 12b-25 extension window — that is the definitional condition for the NTN rebadge.
  • Because the population is exclusively foreign private issuers, registrant addresses, fiscal-year conventions, signer titles, and corporate forms (Ltd, plc, S.A., GmbH, BVI/Cayman holding companies) skew non-US.
  • Part III narratives vary substantially in length and specificity across registrants; downstream NLP should not assume a fixed sentence count or template wording.
  • When Part IV item (3) is answered yes, the trailing quantitative attachment is the most informationally dense portion of the record, often containing comparative income-statement line items that signal the magnitude of the period's financial change.
  • Section labels in document-1.txt are stable across the coverage window (PART I, PART II, PART III, PART IV, For Period Ended:, SIGNATURES), making regex- or anchor-based extraction reliable. <PAGE> markers should be stripped before downstream text processing but can be useful as document-section delimiters in older filings.
  • metadata.json -> entities[].sic retains raw HTML entity encoding (e.g., &amp;) inherited from EDGAR's header text; consumers should HTML-unescape before display.

Who Files or Publishes This Dataset, and When

Who files the record

The filer is a foreign private issuer (FPI) with an Exchange Act annual reporting obligation that is satisfied on Form 20-F. FPI status is defined by Rule 405 under the Securities Act and Rule 3b-4(c) under the Exchange Act: any non-U.S. issuer (other than a foreign government) unless more than 50% of its voting securities are held of record by U.S. residents and a majority of its officers/directors are U.S. citizens or residents, more than 50% of its assets are in the U.S., or its business is principally administered in the U.S.

The filer population covers FPIs reporting under:

The legal filer is the registrant; Form 12b-25 is signed by an authorized officer (typically a senior financial or legal officer), but the obligation runs to the issuer.

When the record is created or required

The trigger is Rule 12b-25 of the Exchange Act, which conditions any short extension of a periodic-report deadline. The mechanical instrument is Form 12b-25, tagged on EDGAR by reference to the underlying late report (here, Form 20-F).

Timing chain:

  1. Fiscal year ends.
  2. Form 20-F is due 4 months after fiscal year end.
  3. To preserve the rule's safe harbor, the registrant must transmit Form 12b-25 ("NT 20-F") no later than 1 business day after that due date.
  4. If the NT 20-F is timely and Part II's representations hold, the Form 20-F is deemed timely if filed within 15 calendar days of its original due date.
  5. If the registrant misses the 1-business-day window for the notice itself, the safe harbor lapses, the 15-day extension never attaches, and any later-filed Form 12b-25 is auto-reclassified by EDGAR as "NTN 20F" — the "N" prefix marking the notice as untimely. The Form 20-F is delinquent from its original due date.

Records in this dataset are event-driven, not periodic; each one represents a registrant's decision to lodge an after-the-fact Rule 12b-25 notice even though the safe harbor has already expired.

What Form 12b-25 requires (Parts I–IV)

  • Part I — identifies the report and the period covered (here, the Form 20-F annual report and its fiscal year).
  • Part II — three representations: that timely filing would require unreasonable effort or expense; that the report will be filed within the rule's extension window; and that any required subsidiary information is included or explained. On an NTN 20F, the second representation is no longer operative because the safe harbor has lapsed.
  • Part III — narrative reasons the Form 20-F could not be filed on time.
  • Part IV — disclosure of any anticipated significant change in results of operations from the prior period (with explanation), plus contact information.

Content fields are identical for NT 20-F and NTN 20F; only EDGAR's timeliness classification differs.

Consequences of an untimely notice

Because an NTN 20F cannot deem the Form 20-F timely:

  • The issuer is a delinquent filer for purposes of Form S-3 / F-3 eligibility, which requires timely filing of all Section 13 or 15(d) reports during the prior 12 months.
  • The issuer falls out of compliance with Section 13 (for Section 12 registrants) or Section 15(d) until the Form 20-F is filed.
  • Exchange listing standards (NYSE, Nasdaq) treat the late annual report as a deficiency that can lead to notification, listing-standards action, or, if uncured, delisting.

Important distinctions

  • NT 20-F vs. NTN 20F. NT 20-F is the timely notice that can secure deemed-timely status for the annual report; NTN 20F is the EDGAR re-tag showing the notice itself missed the 1-business-day window and cannot cure the delinquency.
  • Form 40-F filers. MJDS-eligible Canadian issuers reporting on Form 40-F use NT 40-F / NTN 40-F instead.
  • Domestic registrants. Late-notice filers reporting on Form 10-K generate NT 10-K / NTN 10-K, not NTN 20F. Investment companies and foreign governments (Form 18-K) have separate regimes.
  • Loss of FPI status. An issuer that fails Rule 3b-4(c) transitions to domestic forms (10-K, 10-Q, 8-K) on the first day of the next fiscal year; thereafter its late-annual-report notices are NT 10-K / NTN 10-K.
  • Rule 12g3-2(b) issuers. An FPI that has terminated Section 12(g) registration in reliance on Rule 12g3-2(b) and has no Section 13 or 15(d) obligation has nothing to extend and does not generate NTN 20F records.
  • Amendments. An amended Form 12b-25 to an already-untimely notice remains in the NTN 20F lineage and does not retroactively cure timeliness.

How This Dataset Differs From Similar Datasets or Filings

Form NTN 20F occupies a narrow slot in EDGAR: Rule 12b-25 notifications for delayed Form 20-F annual reports that themselves arrived after the one business day notice deadline. Several nearby datasets cover the on-time version of the same notice, the equivalent notice for other periodic reports, or the underlying annual report. The comparisons below mark where the boundaries lie.

NT 20-F — the timely 12b-25 notification. Same form content, same Rule 12b-25 mechanism, same foreign private issuer (FPI) population. The only difference is timing. EDGAR enforces it mechanically: a 12b-25 with the Form 20-F box checked is accepted as "NT 20-F" if received within one business day of the 20-F due date, and auto-reclassified as "NTN 20F" if received later — the leading "N" prefix tagging the notice itself as untimely. Together NT 20-F and NTN 20F describe the full 12b-25-for-20-F population; NTN 20F isolates issuers who missed both the 20-F deadline and the notice grace period.

NT 10-K / NTN 10K — domestic annual-report late notices. Identical 12b-25 mechanism and identical EDGAR auto-relabel, but for domestic registrants filing Form 10-K rather than FPIs filing Form 20-F. Use NTN 10K for domestic late-notice research; use NTN 20F for the FPI side.

NT 10-Q / NTN 10Q — quarterly-report late notices. Same mechanism, applied to delayed Form 10-Q filings by domestic issuers. No FPI analog exists: foreign private issuers do not file 10-Qs (their interim reporting moves through Form 6-K), so NTN 20F has a strictly annual cadence and there is no FPI quarterly counterpart.

Form 20-F — the substantive annual report. Form 20-F contains the actual audited financials, MD&A, risk factors, and governance disclosures. NTN 20F is a one- to two-page notice that the 20-F will be late, plus a stated reason. Use Form 20-F for content; use NTN 20F to flag missed-deadline events and the explanations attached to them (audit delays, restatements, internal-control issues, auditor transitions, going-concern questions).

Form 6-K — FPI current-event reporting. Same filer population as NTN 20F, but event-driven and filed many times per year, carrying material information the FPI makes public, files locally, or distributes to holders. A 6-K may describe the same underlying event that caused a 20-F delay, but it is not a Rule 12b-25 notification and is not interchangeable with NT 20-F or NTN 20F.

Form 40-F / NT 40-F — Canadian MJDS annual reports. 40-F is the annual report for Canadian issuers under the U.S.-Canada Multijurisdictional Disclosure System; NT 40-F is its 12b-25 late-notice, with the same NTN-prefix relabel applied when the notice itself is untimely. MJDS issuers are carved out of the 20-F regime, so NTN 20F does not capture them. Cross-jurisdictional late-filing studies need NTN 20F together with NT 40-F / NTN 40F.

Form 12b-25 — the underlying paper form, not an EDGAR submission type. Form 12b-25 is the single late-notice form whose checkbox section indicates which report is delayed (Form 10-K, 20-F, 10-Q, 40-F, N-SAR, etc.). EDGAR does not store filings as "Form 12b-25"; it derives the submission type from the box checked and from whether the notice arrived on time. Searching for "Form 12b-25" as a category really means the union of NT 10-K, NT 10-Q, NT 20-F, NT 40-F, NT N-SAR and their NTN late-relabel variants. NTN 20F is one cell in that matrix: Form 20-F box checked, notice filed late.

Key differences at a glance

  • Timing of the notice: NT 20-F = within one business day of the 20-F due date; NTN 20F = after that window. EDGAR assigns the prefix automatically at acceptance.
  • Filer regime: NTN 20F = foreign private issuers on the 20-F regime. NTN 10K / NTN 10Q = domestic. NTN 40F = Canadian MJDS.
  • Report cadence: NTN 20F is annual only — no FPI quarterly equivalent exists.
  • Content type: NTN 20F is a notification with an explanation; Form 20-F is the substantive annual report; Form 6-K is unrelated event disclosure.

Boundary summary

NTN 20F is distinct on three dimensions simultaneously: it is a notification (not a substantive report), it is FPI-and-annual (not domestic, not quarterly, not MJDS), and it is the late-arriving variant (not the on-time NT 20-F). Substituting any adjacent dataset breaks at least one of these dimensions. NTN 20F is the correct dataset only when the question concerns foreign private issuers who missed both their 20-F deadline and the Rule 12b-25 grace period for the late-notice itself.

Who Uses This Dataset

NTN 20F is a compounded delinquency signal: a foreign private issuer missed its 20-F deadline and then missed the Rule 12b-25 window for filing the late notice itself. Users care because the registrant has now failed twice in sequence on the same reporting period, and the workflows below all key off the same small set of fields — periodOfReport, filedAt, registrant CIK, entities[], and the Part III narrative.

Securities counsel and FPI compliance officers

Track when a client or peer issuer crosses from "late" to "delinquent." periodOfReport and filedAt fix the gap against the 20-F due date, which drives loss of F-3/S-3 shelf eligibility, Rule 144 affiliate restrictions, and exchange notice obligations. The Part III narrative (audit dispute, restatement, auditor change, sanctions) is mined to set remediation timelines. Output: compliance memos, board updates, eligibility calendars keyed off the late-of-late notice date.

External auditors and audit committees

Treat a late-late notice on a peer or prospective client as a flag for material weaknesses, scope limitations, going concern, or auditor resignation. Part III reasons feed root-cause taxonomies; periodOfReport aligns the event with the audit cycle; CIK and entities[] confirm the correct group entity. Used in client acceptance and continuance scoring.

Equity and credit analysts covering FPIs

Read the late-late filing as elevated probability of restatement, covenant breach, or downgrade. filedAt triggers surveillance; periodOfReport identifies the impaired fiscal year; the narrative grades technical-versus-substantive cause. Feeds watchlist updates, rating-action memos, and covenant-timing assumptions for bond models.

Event-driven and short-biased managers

The compounded delinquency is one of the cleaner pre-catalyst indicators in the FPI universe, often preceding restatement, auditor resignation, going concern qualification, or delisting. filedAt drives time-sensitive screens; entities[] and CIK map the notice to listed equity and ADRs; Part III text grades severity for thesis files and sizing.

Exchange listing-qualifications and SRO surveillance staff

Use NTN 20F alongside NT 20-F to identify FPIs that have blown past both the original deadline and the Rule 12b-25 cure window, the threshold at which continued-listing standards are typically breached. periodOfReport, filedAt, and CIK drive automated delinquency tracking; the narrative informs whether cure is plausible. Output: deficiency notices and listing determinations.

Securities-litigation counsel (plaintiff and defense)

Use each record as a dated admission. filedAt anchors when the issuer formally conceded it could not file even the late notice on time; periodOfReport defines the class period boundary; the Part III narrative is treated as the issuer's own characterization of the underlying problem for materiality, scienter, and damage-window arguments.

Academic and policy researchers

Build clean panels of late-of-late FPI events from 1996 forward, aggregating by periodOfReport, home jurisdiction (from CIK and entity metadata), industry, and narrative reason. Supports empirical work on Rule 12b-25 effectiveness and cross-border timeliness.

EDGAR data engineers

Must separate NT 20-F (timely notice) from NTN 20F (notice that itself missed the window) because downstream consequences differ. Consume accessionNo, form type, filedAt, periodOfReport, CIK, and entities[] to maintain delinquency tables, link each late-late notice to the eventual 20-F (or its absence), and reissue records when EDGAR reclassifies.

Governance and stewardship researchers

Flag FPIs with repeat NTN 20F filings across multiple periodOfReport values as evidence of persistent oversight failure. Cumulative gap between fiscal year-end and eventual 20-F filing, plus Part III narrative, feed governance scores and engagement materials.

Specific Use Cases

Each use case below ties to the late-of-late nature of the record: an FPI that missed both its 20-F deadline and the Rule 12b-25 notice window for the same reporting period.

1. F-3/S-3 shelf-eligibility and Rule 144 monitoring (securities counsel)

FPI compliance counsel run a daily diff of new accessions against their issuer watchlist. For each hit, they pull periodOfReport, filedAt, and the registrant CIK from entities[] to compute the elapsed gap from the 20-F due date and decide whether the client has crossed from "late" to "delinquent" — the threshold at which Form S-3/F-3 shelf eligibility lapses and Rule 144 affiliate resales are constrained. Output: a compliance memo and a recalibrated 12-month-timely-filer calendar keyed off the late-of-late notice date.

2. Pre-restatement short screens (event-driven managers)

Event-driven and short-biased desks treat the compounded delinquency as a pre-catalyst signal. A nightly job ingests new NTN 20F records, joins entities[].cik to ADR/ordinary tickers, sorts by filedAt, and grades Part III narrative text for substantive causes (audit dispute, restatement-in-progress, auditor resignation, going-concern). Output: a sized short-thesis file, with periodOfReport defining the impaired fiscal year and the narrative supporting position sizing.

3. Continued-listing deficiency triage (exchange listing-qualifications staff)

NYSE and Nasdaq listing-qualifications teams reconcile NTN 20F arrivals against issuers already on NT 20-F watch. The combination of CIK, periodOfReport, and filedAt confirms an FPI has blown past both the 20-F deadline and the 15-day extension window. Output: deficiency-letter drafts, cure-period schedules, and escalation to delisting review when the Part III narrative makes timely cure implausible.

4. Class-period anchoring in securities litigation (plaintiff and defense counsel)

Litigation teams use each record as a dated, issuer-authored admission. filedAt is treated as the moment the registrant formally conceded it could not even file the late notice on time; periodOfReport bounds the class period; Part III prose is mined verbatim for materiality, scienter, and loss-causation arguments. Output: complaint allegations, motion-to-dismiss exhibits, and damage-window calendars.

5. Auditor-transition and going-concern surveillance (audit committees, peer auditors)

Audit committees and peer firms running client-acceptance reviews scan Part III for auditor-resignation language, scope limitations, and going-concern flags, indexed against entities[].sic and periodOfReport. The late-of-late context elevates these mentions above ordinary NT 20-F noise because the registrant has already exhausted the notice grace period. Output: client acceptance/continuance scores and audit-committee briefing notes.

6. Cross-border delinquency panels (academic and policy researchers)

Researchers studying Rule 12b-25 effectiveness and FPI reporting timeliness build panels keyed on periodOfReport, home-jurisdiction inferences from entities[] addresses, entities[].sic, and Part III reason taxonomies. Because the dataset isolates the late-of-late subset, it provides a clean treatment group against the on-time NT 20-F population. Output: regression panels, summary statistics on cross-jurisdictional cure rates, and policy memos.

7. Delinquency-table maintenance and 20-F linkage (EDGAR data engineers)

Data engineers maintaining issuer-delinquency tables must keep NT 20-F and NTN 20F separated downstream because the legal consequences differ. Pipelines key on accessionNo, formType, filedAt, periodOfReport, and entities[].cik to attach each late-of-late notice to the eventual 20-F filing (or flag its continued absence) and to reissue records when EDGAR reclassifies a submission post-acceptance. Output: a maintained issuer-by-period delinquency ledger feeding compliance, analyst, and surveillance consumers upstream.

Dataset Access

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

This endpoint returns the dataset metadata, including name, description, last updated timestamp, earliest sample date (1996-07-01), form types covered (NTN 20F), container format (ZIP), and content file types (TXT, JSON). It also returns the download URL for the full dataset archive and a containers array listing each monthly ZIP container with its key, size, record count, last updated timestamp, and individual downloadUrl. Use this endpoint to monitor which containers have changed in the latest refresh and to decide which monthly archives to re-download.

This endpoint does not require an API key.

Example
1 {
2 "datasetId": "1f13365b-9ae0-6a78-8876-25e13a542079",
3 "datasetDownloadUrl": "https://api.sec-api.io/datasets/form-ntn-20f-files.zip",
4 "name": "Form NTN 20F Files Dataset",
5 "updatedAt": "2026-04-16T08:55:56.549Z",
6 "earliestSampleDate": "1996-07-01",
7 "totalRecords": 4,
8 "totalSize": 18959,
9 "formTypes": ["NTN 20F"],
10 "containerFormat": "ZIP",
11 "fileTypes": ["TXT", "JSON"],
12 "containers": [
13 {
14 "downloadUrl": "https://api.sec-api.io/datasets/form-ntn-20f-files/2026/2026-03.zip",
15 "key": "2026/2026-03.zip",
16 "size": 13818,
17 "records": 2,
18 "updatedAt": "2026-04-16T08:55:56.549Z"
19 }
20 ]
21 }

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

Downloads the complete dataset as a single ZIP archive containing every monthly container from July 1996 to the present. This endpoint requires an API key.

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

Downloads one monthly container ZIP. Each container is organized by year and month (YYYY/YYYY-MM.zip) and includes a metadata.json file along with the per-document text files for each accession number in that month. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers EDGAR submissions classified as NTN 20F — Rule 12b-25 notifications of inability to timely file an annual report on Form 20-F where the notice itself arrived after the original 20-F due date. The underlying paper instrument is Form 12b-25 with the [X] Form 20-F box checked; EDGAR auto-reclassifies the submission from NT 20-F to NTN 20F when the notice misses the one-business-day grace period.

What does one record in this dataset represent?

One record is a single EDGAR accession of form type NTN 20F: one foreign private issuer's late-arriving Rule 12b-25 notice for a specific Form 20-F annual reporting period. Each record bundles the structured metadata.json envelope and the textual content of every non-image document in the original submission, named document-1.txt, document-2.txt, and so on.

Who is required to file this form?

Foreign private issuers (FPIs) with an Exchange Act annual reporting obligation satisfied on Form 20-F — that is, FPIs reporting under Section 12(b) (commonly through ADSs listed on a U.S. national exchange), Section 12(g), or Section 15(d). Domestic registrants, MJDS-eligible Canadian issuers on Form 40-F, investment companies, and foreign governments do not generate NTN 20F records.

How does NTN 20F differ from NT 20-F?

Both are the same Form 12b-25 instrument with the Form 20-F box checked, with identical content fields. The difference is timing: a 12b-25 received within one business day of the 20-F due date is classified NT 20-F and can deem the late 20-F timely if filed within 15 calendar days; a 12b-25 received after that one-business-day window is auto-reclassified NTN 20F, the safe harbor lapses, and the Form 20-F is delinquent from its original due date.

What time period does the dataset cover?

Coverage begins on 1996-07-01 (the earliest sample date) and runs to the present. Records are event-driven rather than periodic; many monthly archives contain no entries because months without any NTN 20F submission produce no records, which is a structural property of an exceptionally sparse form type.

What file format is the dataset distributed in?

The dataset is delivered as monthly ZIP containers organized by year (YYYY/YYYY-MM.zip). Inside each container, every accession sits in its own folder containing exactly one metadata.json (the structured EDGAR envelope) and one or more sequentially-numbered document-N.txt plain-text files. Image attachments from the original submission are excluded; there are no XBRL instances or schemas, since Form 12b-25 is not subject to XBRL tagging.

How do I access the dataset programmatically?

A dataset index endpoint at https://api.sec-api.io/datasets/form-ntn-20f-files.json returns metadata and a containers array describing each monthly ZIP, and does not require an API key. The full archive is available at https://api.sec-api.io/datasets/form-ntn-20f-files.zip?token=YOUR_API_KEY, and individual monthly containers can be downloaded at https://api.sec-api.io/datasets/form-ntn-20f-files/YYYY/YYYY-MM.zip?token=YOUR_API_KEY; both download endpoints require an API key.