Form NT-NCSR Files Dataset

The Form NT-NCSR Files Dataset is a complete corpus of late-filing notifications submitted by registered management investment companies under Exchange Act Rule 12b-25 when they cannot file Form N-CSR — the certified annual or semi-annual shareholder report mandated by Rule 30b2-1 of the Investment Company Act of 1940 — within the prescribed ten-day window after transmittal to shareholders. One record represents a single Form NT-NCSR or NT-NCSR/A submission as accepted into EDGAR, identified by its accession number and packaged as an accession-numbered folder containing a structured metadata.json descriptor plus the original EDGAR source documents in HTML, TXT, and PDF. The filer population is exclusively registered management investment companies — open-end mutual funds, closed-end funds, and ETFs organized as registered open-end companies — whose own N-CSR obligation under Rule 30b2-1 has slipped. Coverage begins in May 2003, when Form N-CSR (and concurrently NT-NCSR) was first adopted under Investment Company Act Release No. IC-25914, and runs through the present.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset packages every Form NT-NCSR and Form NT-NCSR/A submission accepted into EDGAR. NT-NCSR is the Form 12b-25 variant used by registered management investment companies to notify the SEC that they cannot file Form N-CSR on time; NT-NCSR/A is the amendment variant used to correct or supplement a previously submitted NT-NCSR. The form is mechanically identical to other Form 12b-25 notifications (NT 10-K, NT 10-Q, NT 20-F, NT 10-D, NT-NCEN), differing only in the underlying form whose late filing is being excused — in this dataset, the covered form is always N-CSR.

Coverage is the entire NT-NCSR filer population from the form's inception in May 2003 through the present. Original notices and amendments share an identical record shape and differ only in formType (NT-NCSR versus NT-NCSR/A). One filing maps to exactly one record, even when many fund series are covered by that single notice; multi-series coverage is represented inside the record rather than across multiple records. Records are distributed as ZIP containers and the file types found inside the dataset are HTML, JSON, TXT, and PDF.

Content Structure of a Single Record

What one record represents

One record is a single Form NT-NCSR or Form NT-NCSR/A submission as accepted into EDGAR, identified by its accession number. Physically, the record is an accession-numbered folder containing a metadata.json descriptor and the full set of source documents from the original EDGAR submission, with image files removed.

The accession folder is named with the 18-digit dash-stripped accession number (for example 000199937125008958 for accession 0001999371-25-008958). Folder contents are flat: there are no subdirectories, no separate exhibit folders, and no XBRL instance documents.

What the underlying filing is

Form N-CSR is the Certified Shareholder Report of Registered Management Investment Companies, mandated by Rule 30b2-1 under the Investment Company Act of 1940 and required to be filed within ten days after the registrant transmits its annual or semi-annual report to shareholders pursuant to Rule 30e-1. When that ten-day window cannot be met, the registrant files an NT-NCSR under Exchange Act Rule 12b-25, asserting one or more statutory grounds for relief and committing to a revised filing date.

EDGAR implements the entire late-filing family as a single Form 12b-25 template with a checkbox group identifying the covered form; in this dataset the covered form is always N-CSR.

Content layers in a single record

A record has three concentric layers:

1. The outer EDGAR submission metadata, captured in metadata.json.
2. The SGML document envelope wrapping each exhibit, expressed as <DOCUMENT> blocks with <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, and <TEXT> tags.
3. The rendered Form 12b-25 notice itself inside the <TEXT> payload, plus any supporting exhibits.

The first layer is structured JSON intended for programmatic joins. The second is the standard EDGAR document framing carried inside each .htm, .txt, or .pdf file. The third is the substantive disclosure: a short, highly templated form with a four-Part structure plus optional attached statements.

The metadata.json descriptor

Every accession folder contains a metadata.json object describing the filing in structured form. The analytically important fields are:

• formType — NT-NCSR for an original notice, NT-NCSR/A for an amendment. This is the primary discriminator between the two form variants in the dataset.
• accessionNo — the canonical dashed accession number (for example 0001999371-25-008958), the universal join key for EDGAR records.
• filedAt — full ISO-8601 timestamp with timezone offset capturing the moment EDGAR accepted the submission.
• effectivenessDate — the date the filing became effective, generally coincident with the filing date for these notices.
• periodOfReport — the fiscal period to which the missed N-CSR pertains, expressed as YYYY-MM-DD. For an annual N-CSR this is the fiscal year-end; for a semi-annual N-CSR this is the mid-year balance date. Combined with the entity's fiscalYearEnd, this field identifies whether the late report belongs to the annual or semi-annual cycle.
• description — a short boilerplate label describing the form, typically referencing Exchange Act Rule 12b-25 and the inability to file Form N-CSR on time.
• linkToFilingDetails, linkToHtml, linkToTxt, linkToXbrl — direct URLs back to the EDGAR filing's index page, primary HTML document, complete-submission text file, and (where applicable) XBRL data. linkToXbrl is empty for NT-NCSR because Form 12b-25 carries no XBRL.
• id — an internal md5-style identifier.
• documentFormatFiles — an array enumerating each document in the original EDGAR submission. Each entry carries sequence, size (in bytes), documentUrl, description, and type. The type values mirror EDGAR's <TYPE> tags (for example NT-NCSR for the primary notice, or accountant exhibit types for Rule 12b-25(c) attachments). The complete-submission text file appears as an entry with a blank sequence and blank type.
• dataFiles — an array reserved for structured data files; empty for NT-NCSR submissions.
• entities — an array of filer entities. Each entity object carries companyName (with a role suffix such as (Filer)), cik, fileNo (the Investment Company Act file number, in the 811- series for registered investment companies), irsNo, stateOfIncorporation, fiscalYearEnd (as MMDD), act (the statutory regime, 40 for the Investment Company Act of 1940), type (form type filed by that entity), and filmNo (the EDGAR film number).
• seriesAndClassesContractsInformation — an array describing each fund series implicated in the late filing. Each series object carries an EDGAR series identifier (S000xxxxxxx), the series name, and a classesContracts array; each class entry carries the share-class ticker, the class name, and the class contract identifier (C000xxxxxxx). A single NT-NCSR filed by a trust on behalf of many series can populate this array heavily; it is the primary one-to-many child relationship inside a record.

The SGML document envelope

Each non-JSON file inside the accession folder is an EDGAR document envelope rather than a bare HTML or text payload. The opening lines of the primary notice file follow the canonical pattern:

          1
          <DOCUMENT>
        

          2
          <TYPE>NT-NCSR
        

          3
          <SEQUENCE>1
        

          4
          <FILENAME>...-ntncsr_...htm
        

          5
          <DESCRIPTION>NOTICE OF LATE FILING
        

          6
          <TEXT>
        

          7
          <HTML>
        

          8
          <HEAD>...</HEAD>
        

          9
          <BODY>... rendered Form 12b-25 ...</BODY>
        

          10
          </HTML>
        

          11
          </TEXT>
        

          12
          </DOCUMENT>
        

The <TEXT> block holds the rendered notice, typically formatted as a sequence of HTML tables that reproduce the boxed layout of the paper Form 12b-25. Supporting exhibits, when present, appear as additional <DOCUMENT> blocks in separate .htm, .txt, or .pdf sibling files inside the same accession folder, each with its own <TYPE>, <SEQUENCE>, <FILENAME>, and <DESCRIPTION>. The complete-submission text file consolidates all envelopes into a single .txt artifact.

Parts I through IV of the Form 12b-25 body

The substantive content inside the primary document follows the rigid Form 12b-25 structure. The form opens with a header block identifying the Commission File Number and a checkbox group declaring which underlying form is being notified as late; in this dataset the N-CSR checkbox is always selected. Below the header, four numbered Parts appear in order:

• Part I — Registrant Information. Carries the registrant's full name, any former name during the past five years if applicable, the address of principal executive offices, and the Investment Company Act file number. For a series trust, this identifies the trust entity rather than each constituent fund.
• Part II — Rules 12b-25(b) and (c). A short checkbox affirmation block in which the registrant represents that the conditions for relief under Rule 12b-25(b) are satisfied: the report could not be filed without unreasonable effort or expense, the report will be filed within the cure period (15 calendar days after the original due date for annual reports, five calendar days for periodic reports of the type covered, applied here in the N-CSR context), and any required accountant's statement under Rule 12b-25(c) is attached as an exhibit.
• Part III — Narrative. The free-text statement of the reasons the N-CSR could not be filed on time. This is the only genuinely narrative section of the form. Typical content addresses delays in completing audited financial statements, NAV calculation issues, sub-adviser or fund-accountant transitions, recent fund launches, mergers or reorganizations, and similar operational causes. The expected filing date for the late N-CSR is also stated here, completing the registrant's commitment to a revised submission timeline.
• Part IV — Other Information. Contains the name and telephone number of a contact person at the registrant, two yes/no representations (whether any person other than the registrant is a co-issuer of any of the registrant's securities, and whether the registrant anticipates that any significant change in results of operations from the comparable prior period will be reflected in the report), and the signature block. The signature block carries a typed /s/ Name, Title line, the signer's printed name and capacity (typically Treasurer, Principal Financial Officer, or Trust Secretary), and the signing date.

Included content

Each record contains:

• The structured metadata.json descriptor.
• The primary NT-NCSR document with the rendered Form 12b-25 notice.
• Any additional exhibits filed under the same accession, including accountant's statements required by Rule 12b-25(c) when applicable, in their original HTML, PDF, or TXT formats inside SGML envelopes.
• The complete-submission text file enumerated as a separate document entry in documentFormatFiles.

The file-types found in the dataset are HTML, JSON, TXT, and PDF.

Excluded or separate content

Image files referenced by the original EDGAR submission are excluded by the dataset producer. Where a notice's HTML references a logo, signature image, or scanned attachment, the <img> tag will resolve to a file that is not present in the accession folder. The notice text itself remains intact because Form 12b-25 is a text-driven rather than image-driven form.

The underlying Form N-CSR shareholder report whose late filing is being notified is not part of this dataset; it is a separate filing under a separate accession number, retrieved (when later filed) under a distinct N-CSR or N-CSRS submission. The dataset also does not include the sibling NT-NCEN late-filing notice, which is a separate Form 12b-25 variant covering Form N-CEN rather than Form N-CSR.

Historical context

Form N-CSR was adopted by the SEC in 2003 (Investment Company Act Release No. IC-25914) to consolidate the reporting of certified annual and semi-annual reports by registered management investment companies, replacing the prior Form N-30D regime for these registrants. NT-NCSR notifications begin appearing on EDGAR in mid-2003 alongside the rollout of N-CSR itself, which is the practical lower bound of the dataset's coverage. Subsequent rule changes affecting certifications under Sarbanes-Oxley (Sections 302 and 906), the addition of Schedule of Investments disclosures, and shareholder-report tailoring for ETFs and feeder funds altered the substance of N-CSR but had limited effect on the structure of the NT-NCSR notice itself, which has remained a faithful Form 12b-25 instantiation throughout the period. Because periodOfReport carries either the fiscal year-end (annual cycle) or the fiscal mid-year date (semi-annual cycle) of the missed report, the distribution of periodOfReport values across the dataset tracks the calendar of investment-company fiscal years rather than a single uniform cadence.

The presentation of NT-NCSR has been HTML-dominant throughout the dataset's time span, wrapped in EDGAR's SGML <DOCUMENT> envelope. PDF and plain-text exhibit attachments occur but are uncommon.

Interpretation and extraction notes

Several nuances matter for downstream use:

• The dashed accessionNo in metadata.json and the dash-stripped folder name on disk refer to the same filing in different syntactic forms; either can serve as a join key.
• A single record can implicate many fund series. Treat seriesAndClassesContractsInformation as a one-to-many child relationship rather than a scalar field, and key children by the S000 series identifier and the C000 class contract identifier.
• The entities array can carry more than one entity when a trust and an affiliated filer co-sign the notice; each entity carries its own role suffix in companyName.
• Amendments (NT-NCSR/A) supersede or supplement the corresponding original notice but are stored as independent records with their own accession numbers. Chronological reconciliation across an original notice and its amendment requires matching on registrant CIK and periodOfReport, since amendments do not carry an explicit pointer to the prior accession.
• Primary document filenames are issuer-chosen and follow no fixed convention; mapping a file inside an accession folder to its role should always go through documentFormatFiles[*].documentUrl (using the basename) and the corresponding type and description.
• The <TEXT> payload inside the SGML envelope is rendered HTML rather than free narrative; the four-Part structure of Form 12b-25 is typically realized as nested HTML tables rather than semantic headings, so extraction of the Part III narrative usually requires walking table rows and locating the cell that follows the Part III prompt rather than relying on heading tags.
• The contact telephone number in Part IV and the signer's name and title are reliably present and useful for entity disambiguation when CIK alone is insufficient.
• The Rule 12b-25(c) accountant's statement, when attached, is a separate <DOCUMENT> block with its own <TYPE> and is enumerated as a distinct entry in documentFormatFiles; it should be treated as exhibit content rather than as part of the four-Part body.

Who Files or Publishes This Dataset, and When

Who files the record

Form NT-NCSR is filed exclusively by registered management investment companies that are themselves obligated to file Form N-CSR under Rule 30b2-1 of the Investment Company Act of 1940. The filing population includes:

• Open-end management investment companies (mutual funds), including each registered series within a series trust that has its own fiscal year-end and N-CSR cycle.
• Closed-end management investment companies, both exchange-listed and non-listed (interval funds, tender offer funds).
• ETFs organized as registered open-end management investment companies, which file N-CSR through the registrant trust and therefore use NT-NCSR when a report is delayed.

The legal filer is the registrant as it appears on EDGAR, identified by CIK and registrant name. For series trusts, the trust is the EDGAR filer; affected series and class identifiers typically appear in the Part III narrative when the late report covers fewer than all series.

When the record is created or required

The trigger is the registrant's determination that it cannot file Form N-CSR within the period prescribed by Rule 30b2-1 — ten days after transmittal to shareholders of the annual or semi-annual report required by Rule 30e-1. The ten-day clock runs from the date of transmittal to shareholders, not from fiscal year-end, so an N-CSR (and any NT-NCSR) generally arises twice per fiscal year.

Form NT-NCSR is the investment-company analogue of Form 12b-25 under Exchange Act Rule 12b-25, and it operates on the same scaffolding: the notification must be filed on or before the original N-CSR due date. A timely, properly executed NT-NCSR — with a Part III narrative explaining the delay and the Part IV representations regarding expected filing date and any significant change in results of operations — extends the deadline by fifteen calendar days. An N-CSR filed within that fifteen-day cure window is deemed timely; if the registrant misses the cure window, or fails to file NT-NCSR by the original due date, the N-CSR is treated as delinquent from the original deadline.

The form is signed by an authorized officer of the registrant (typically the principal executive officer, principal financial officer, or treasurer), whose signature supports the Part IV representations.

NT-NCSR/A amendments

Form NT-NCSR/A amends a previously filed NT-NCSR — for example, to correct the Part III narrative, update the expected filing date, fix the affected series or fiscal period, or revise the signing officer or representations. An amendment does not extend the fifteen-day cure window established by the original timely notification; it is purely corrective or clarifying.

Important distinctions

• Operating companies use a different NT form. A late 10-K, 10-Q, or 20-F from an Exchange Act operating-company issuer is notified on Form NT 10-K, NT 10-Q, or NT 20-F under Rule 12b-25 — not NT-NCSR. The NT-series is partitioned by underlying form.
• N-CSR and N-CSRS share one notification. Both annual and semi-annual N-CSR filings use the same NT-NCSR when delayed; there is no separate semi-annual late form.
• N-CEN delays use NT-NCEN. The annual N-CEN census filing has its own late-notice form (NT-NCEN), distinct from NT-NCSR.
• Non-management investment companies are outside the regime. Unit investment trusts that are not management investment companies do not file N-CSR and therefore never file NT-NCSR. Face-amount certificate companies and similar entities follow different late-notice mechanics.
• Unregistered and foreign funds are excluded. Private funds, hedge funds, and non-U.S. funds not registered under the 1940 Act do not file N-CSR and never appear in this dataset.
• Failure to file the notice forfeits the cure window. A registrant that misses the N-CSR deadline without filing NT-NCSR loses the fifteen-day extension; the late N-CSR is treated as untimely from the original due date.

How This Dataset Differs From Similar Datasets or Filings

Form NT-NCSR sits at the intersection of two reporting regimes: late-filing notifications under Exchange Act Rule 12b-25, and registered investment company shareholder reporting under Investment Company Act Rule 30b2-1. The most useful comparisons are therefore the substantive report it stands in for (N-CSR), the parallel 12b-25 notifications used by other filer populations or for adjacent fund reports (NT 10-K, NT 10-Q, NT-NSAR, NT-NCEN, 24F-2NT), the transmittal obligations that start the N-CSR clock (N-30D, N-30B-2), and the original-vs.-amendment split (NT-NCSR vs. NT-NCSR/A).

Form N-CSR — the underlying substantive report

N-CSR is the certified annual or semi-annual shareholder report that registered management investment companies file under Rule 30b2-1, due within ten days of transmitting the report to shareholders under Rule 30e-1. It carries the full shareholder report: audited (annual) or unaudited (semi-annual) financial statements, schedule of investments, Sarbanes-Oxley Section 302 and 906 certifications, code of ethics, and audit committee financial expert disclosures. NT-NCSR is the procedural placeholder for that same filing — a short Form 12b-25 cover with Parts I-IV stating registrant identity, fiscal period, reason for delay, and expected filing date. To obtain fund financials, holdings, or certifications, pull the eventual N-CSR; NT-NCSR only signals that one is late and why.

NT 10-K and NT 10-Q — the operating-company analogs

NT 10-K, NT 10-Q, and NT-NCSR are all instances of Form 12b-25 and share the same four-part structure. They differ on filer population and statutory hook: NT 10-K and NT 10-Q are filed by Exchange Act operating issuers under Sections 13 or 15(d) when annual or quarterly reports will be late; NT-NCSR is filed by registered management investment companies (typically open-end and closed-end funds) when an Investment Company Act shareholder report will be late. Volumes diverge sharply — NT 10-K/NT 10-Q each run into the tens of thousands of filings, while NT-NCSR sits in the high hundreds.

NT-NSAR — the rescinded predecessor in the fund family

NT-NSAR was the 12b-25 notification for Form N-SAR, the semi-annual operational/statistical report for investment companies and unit investment trusts. It shares NT-NCSR's filer population and 12b-25 scaffolding but covers a different underlying report: N-SAR was a structured Y/N operational questionnaire on fees, distribution, and service providers, whereas N-CSR is a certified narrative-and-financial shareholder report. The SEC rescinded N-SAR effective June 1, 2018, so NT-NSAR is a historical-only dataset. It is the closest pre-2018 analog to NT-NCSR within the fund family but notifies delays in an entirely different report.

NT-NCEN — the census-report sibling

NT-NCEN is the 12b-25 notification for Form N-CEN, the structured annual census report that replaced N-SAR in 2018 under Rule 30a-1. NT-NCEN and NT-NCSR draw from the same registrant population and use the same 12b-25 framework but cover non-overlapping disclosures: N-CEN is a standardized XML annual census of operational, governance, and service-provider data; N-CSR is the certified shareholder report. A fund late on N-CEN files NT-NCEN; a fund late on N-CSR files NT-NCSR. The two streams are not interchangeable, and a single complex may file both in the same year for different reasons.

Form 24F-2NT — the registration-fee notification

24F-2NT is the 12b-25 notification for Form 24F-2, the annual securities-sold notice that open-end funds use to true up registration fees under Section 24(f) of the Investment Company Act. It shares NT-NCSR's filer population and 12b-25 scaffolding but operates under a different statutory regime — registration-fee accounting rather than shareholder reporting. Useful as a same-family comparator; not a substitute on either side.

N-30D and N-30B-2 — the transmittal predicate, not a notification

N-30D (historical) and N-30B-2 (current) cover the transmittal of periodic shareholder reports to investors under Rule 30e-1. That transmittal is the event that starts the ten-day Rule 30b2-1 clock for N-CSR — and by extension defines when an NT-NCSR becomes necessary. These are operational transmittal filings rather than late-filing notifications; they sit upstream of NT-NCSR rather than parallel to it, and NT-NCSR filings often reference the transmittal date in explaining timing.

NT-NCSR vs. NT-NCSR/A

NT-NCSR is the original notification; NT-NCSR/A amends one. Amendments typically correct administrative errors, revise the stated reason for delay, or update the expected filing date when the original estimate slips. Form structure and fields are identical; the difference is position in the filing chain. For an authoritative final late-filing position, treat NT-NCSR/A as superseding its original; for studies of initial disclosure behavior, retain the original separately.

Boundary summary

NT-NCSR is narrow on three axes at once: one procedural form (Form 12b-25), one triggering report (N-CSR), one filer population (registered management investment companies under the 1940 Act). It is event-driven and explanatory — recording why an N-CSR is late and when it is expected, not what a fund holds or earned. For substantive fund data it must be paired with the eventual N-CSR (and, where relevant, N-CEN, N-PORT, or N-30D/N-30B-2). For cross-regime late-filing analysis it pairs with NT 10-K, NT 10-Q, NT-NCEN, and historically NT-NSAR. None of those alternatives substitute for it.

Who Uses This Dataset

The Form NT-NCSR Files Dataset is narrow but cross-functional, used wherever fund administration, audit, custody, and compliance intersect. Each user group reads a different slice of the same core fields: the Part III narrative, registrant CIK and series/class IDs, periodOfReport, expected filing date, the NT-NCSR/A amendment chain, and the Part IV signing officer block.

Fund Compliance and Regulatory Operations

Chief compliance officers and fund-administration compliance leads reconcile their own NT-NCSR submissions against expected N-CSR delivery dates and benchmark Part III language used by peer complexes for sub-adviser transitions, fair-valuation disputes, and audit-timing issues. Workhorse fields: CIK, series/class IDs, periodOfReport, expected filing date, and the NT-NCSR/A chain to confirm whether the original promised date held.

SEC Examinations and Enforcement Staff

Exam staff and enforcement attorneys use NT-NCSR filings as a low-cost risk signal for sweep design and risk-weighted exam selection. Patterns that drive scoring: repeated NT-NCSR/A amendments revising the expected date, Part III narratives invoking auditor disagreements or service-provider failures, and the cadence between the original NT-NCSR, any amendments, and the eventual N-CSR.

Independent Auditors and Audit-Committee Advisers

Investment-company audit partners, quality-review partners, and audit-committee counsel study how peers describe delays tied to scope expansions, internal-control matters, going-concern questions, or restatements. They use the corpus to calibrate disclosure language when their own engagement signals a delay and to refine engagement-acceptance frameworks. Key fields: Part III reasons, periodOfReport, and the gap between the stated expected filing date and any subsequent NT-NCSR/A.

Buy-Side Analysts and Fund-of-Funds Operations

Manager-research analysts at multi-manager allocators, model-portfolio teams, and advisory due-diligence groups treat a late N-CSR as an operational flag on underlying funds, sub-advisers, or outsourced administrators. They pull CIK, series/class IDs, Part III explanation, and expected filing date into watchlists to trigger follow-up with the fund's compliance and operations contacts.

Vendor Risk and Asset-Servicing Teams

Risk officers at fund administrators, transfer agents, custodians, and pricing-service providers use the dataset to detect when a service failure cascades into a client's NT-NCSR, classify root cause, and feed it into incident-management workflows. Fund boards evaluating asset-servicing vendors use the same narratives in reverse to identify providers repeatedly implicated in late filings. Load-bearing fields: Part III narrative, registrant CIK, fiscal year-end alignment, and amendment history.

Investment-Management Attorneys and SEC-Practice Paralegals

Fund counsel and SEC-practice paralegals use the corpus when drafting or reviewing their own NT-NCSR filings, calibrating reason-for-delay specificity, expected filing dates, and signature blocks against precedent. Paralegals maintain internal precedent libraries keyed by CIK, periodOfReport, and Part III scenario type, and the dataset supports memos on whether a situation requires NT-NCSR, Form 12b-25, or a different disclosure path.

Fund-Board and Governance Researchers

Independent trustees, fund-board secretaries, and governance consultants brief boards on how delays are communicated and resolved across the industry. Repeated NT-NCSR/A amendments by the same registrant, signing-officer turnover between the NT-NCSR and the eventual N-CSR, and recurring Part III themes feed board-effectiveness reviews and audit/compliance committee agendas.

Academic Researchers

Accounting, financial-economics, and law-and-finance researchers assemble the full population from May 2003 forward into panel datasets for studies on audit delays in registered investment companies, determinants of late filings, links between operational events and subsequent fund flows, and the effectiveness of disclosure regimes. Variables typically used: periodOfReport, CIK, expected filing date, NT-NCSR/A lineage, and structured Part III text.

Financial Journalists and Newsletter Writers

Beat reporters and newsletter writers covering fund complexes, closed-end funds, and specialized strategies track which families are filing late, why, and how often. CIK, series/class IDs, periodOfReport, and the Part III narrative are sufficient to build stories on audit-firm disputes, sub-adviser blowups, or operational disruptions, with coverage back to 2003 supplying historical context.

Quantitative Researchers and Signal Engineering Teams

Quants building fund-level operational-risk scores and counterparty-quality features encode NT-NCSR presence and recurrence as time-stamped features: first-time filers in a year, complexes with elevated NT-NCSR-to-N-CSR ratios, repeat amendments pushing the expected date, and Part III narratives clustered into topic categories via text models. Feature inputs: CIK, periodOfReport, expected filing date, amendment flag, and Part III text.

LLM and RAG Developers for Investment-Management Retrieval

Teams building retrieval-augmented systems for fund compliance, audit, and due-diligence ingest the corpus to power question-answering over late-filing precedents (for example, peer descriptions of auditor-driven delays for December year-ends, or all NT-NCSR filings by a given complex and their resolutions). Inputs to chunking and indexing pipelines: HTML and TXT Part III bodies plus structured metadata (CIK, periodOfReport, form type, amendment flag, signing officer).

Specific Use Cases

Beyond the user-group inventory above, the dataset supports a compact set of operational workflows centered on the Part III narrative, periodOfReport, expected filing date, registrant CIK, series/class identifiers, the NT-NCSR/A amendment chain, and the Part IV signing officer block.

Peer benchmarking of reason-for-delay language for compliance drafting

Fund compliance teams and outside counsel pull Part III narratives across all registrants sharing a December or June periodOfReport and cluster them by stated cause (auditor scope expansion, sub-adviser transition, fair-value dispute, fund reorganization). The output is a precedent library keyed by CIK and periodOfReport that lets a CCO calibrate the specificity of their own forthcoming NT-NCSR before signature.

Risk-weighted exam targeting for SEC staff

Exam and enforcement analysts join NT-NCSR records to subsequent N-CSR filings on registrant CIK plus periodOfReport to compute the original-to-final delivery gap, then flag complexes that file repeated NT-NCSR/A amendments revising the expected filing date. Combined with Part III topic tags (auditor disagreement, internal-control concern, NAV error), the result is a registrant-level risk score that feeds sweep design and exam selection.

Operational watchlists for fund-of-funds due diligence

Manager-research and DD teams ingest new NT-NCSR records each business day, extract registrant CIK, the seriesAndClassesContractsInformation array, expected filing date, and Part III text, and route any hit on an underlying held fund or sub-adviser into their incident tracker. Allocators use the cadence between original notice, NT-NCSR/A, and eventual N-CSR as a tripwire for redemption or hold-and-monitor decisions.

Service-provider failure attribution for asset-servicing vendors

Vendor risk teams at fund administrators, custodians, and pricing services scan Part III narratives for named-provider mentions and operational keywords (sub-accountant transition, NAV recalculation, auditor handover) and aggregate hits by registrant CIK and fiscal year-end. The output supports root-cause classification, board-level vendor scorecards, and identification of providers recurring across unrelated complexes' late notices.

Operational-risk features for quantitative fund scoring

Quant teams encode each record as time-stamped features keyed on CIK and periodOfReport: NT-NCSR presence in a fiscal cycle, NT-NCSR/A count, days between original expected filing date and eventual N-CSR acceptance, and topic vectors over the Part III text. These features feed fund-level operational-risk scores, manager-quality models, and counterparty due-diligence pipelines.

RAG indexing over late-filing precedent

LLM teams chunk Part III HTML bodies and attach structured metadata (CIK, periodOfReport, formType, NT-NCSR vs. NT-NCSR/A flag, signing officer name and title, series and class IDs) for retrieval-augmented question answering. This powers queries such as "show prior NT-NCSR filings by this trust and how each was resolved" or "auditor-driven delay narratives for December year-ends in the past five cycles" inside compliance and audit copilots.

Audit-delay academic panels

Researchers assemble the full 2003-forward population into a panel keyed on CIK and periodOfReport, with structured Part III text, expected filing date, NT-NCSR/A lineage, and links to the eventual N-CSR accession. The panel supports studies on determinants of fund audit delay, association between operational events and subsequent shareholder flows, and the effect of disclosure regime changes on late-filing behavior.

Dataset Access

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

This endpoint returns dataset metadata and the list of container files. The metadata includes the dataset name, description, last updated timestamp, earliest sample date (2003-05-01), total records, total size, covered form types (NT-NCSR, NT-NCSR/A), container format (ZIP), and content file types (HTML, JSON, TXT, PDF). The response also includes the full dataset download URL plus an array of individual containers, each with its own download URL, S3 key, size, record count, and updated timestamp. Use this endpoint to monitor which containers have changed in the most recent refresh and decide which monthly archives to pull on a day-to-day basis. No API key is required to access the index.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-69bd-959d-691ba66c19cf",
        

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

          4
            "name": "Form NT-NCSR Files Dataset",
        

          5
            "updatedAt": "2026-04-15T12:16:50.416Z",
        

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

          7
            "totalRecords": 591,
        

          8
            "totalSize": 2717176,
        

          9
            "formTypes": ["NT-NCSR", "NT-NCSR/A"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

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

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

          16
                "size": 48213,
        

          17
                "records": 6,
        

          18
                "updatedAt": "2026-04-15T12:16:50.416Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

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

Downloads the full dataset as a single ZIP archive covering all NT-NCSR and NT-NCSR/A filings from May 2003 to present. Inside the archive, each accession number has its own folder containing a metadata.json file plus the original EDGAR documents (HTML, PDF, TXT) for that filing. This endpoint requires an API key, passed either as the token query parameter or via the Authorization header.

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

Downloads one monthly container ZIP instead of the full dataset, which is useful for incremental syncs of recently updated months. Container paths follow a YYYY/YYYY-MM.zip pattern and are listed in the containers array of the index response. This endpoint requires an API key, passed either as the token query parameter or via the Authorization header.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form NT-NCSR and its amendment variant Form NT-NCSR/A — the Form 12b-25 late-filing notification that registered management investment companies file when they cannot deliver Form N-CSR, the certified annual or semi-annual shareholder report mandated by Rule 30b2-1 of the Investment Company Act of 1940, within the prescribed ten-day window.

What does one record in this dataset represent?

One record is a single NT-NCSR or NT-NCSR/A submission as accepted into EDGAR, identified by its accession number. Physically it is an accession-numbered folder containing a metadata.json descriptor plus the original EDGAR source documents (HTML, TXT, and any PDF exhibits) wrapped in their SGML <DOCUMENT> envelopes.

Who is required to file Form NT-NCSR?

Only registered management investment companies that are themselves obligated to file Form N-CSR — open-end mutual funds, closed-end funds (both exchange-listed and interval/tender-offer), and ETFs organized as registered open-end management investment companies. Unit investment trusts that are not management investment companies, private and hedge funds, and non-U.S. funds not registered under the 1940 Act do not file N-CSR and never appear in this dataset.

When must Form NT-NCSR be filed?

It must be filed on or before the original N-CSR due date, which is ten days after transmittal to shareholders of the annual or semi-annual report required by Rule 30e-1. A timely, properly executed NT-NCSR extends the N-CSR deadline by fifteen calendar days; missing the original due date forfeits that cure window.

How does this dataset differ from Form N-CSR itself?

NT-NCSR is the procedural placeholder — a short Form 12b-25 cover stating registrant identity, fiscal period, reason for delay, and expected filing date — while N-CSR carries the full shareholder report, including audited or unaudited financials, schedule of investments, and Sarbanes-Oxley Section 302 and 906 certifications. To obtain fund financials or holdings, pull the eventual N-CSR; NT-NCSR only signals that one is late and why.

What time period does the dataset cover?

The dataset begins with the earliest NT-NCSR filings on EDGAR in May 2003, when Form N-CSR (and concurrently NT-NCSR) was first adopted under Investment Company Act Release No. IC-25914, and continues through the present.

What file format is the dataset distributed in?

The dataset is distributed as ZIP containers. Inside each container, every accession number has its own folder with a metadata.json descriptor plus the original EDGAR documents in HTML, TXT, and (occasionally) PDF. Containers follow a YYYY/YYYY-MM.zip monthly path and can be downloaded individually for incremental syncs or as a single full-dataset archive.