Form N-8F NTC Files Dataset

The Form N-8F NTC Files Dataset captures the public-notice stage of every pending application for deregistration of a registered investment company under Section 8(f) of the Investment Company Act of 1940. Each record is a single EDGAR accession keyed to one applicant fund, packaging the Commission-issued notice PDF and a structured metadata.json header. The notices are issued by the SEC's Division of Investment Management — not by the deregistering fund — and identify the applicant, the basis for deregistration (merger, liquidation, qualification for a Section 3(c) exclusion, or conversion to a business development company), the date of the underlying Form N-8F application, and the deadline for requesting a hearing before the Commission. Coverage runs from April 2009 to the present, the dataset is delivered as monthly ZIP containers, and the only file types inside are PDF and JSON.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset captures the N-8F NTC EDGAR submission type on EDGAR — the "Notice" (NTC) variant of Form N-8F that the Commission uses to advertise that one or more Form N-8F deregistration applications are pending under Section 8(f) of the Investment Company Act of 1940. Section 8(f) directs the Commission, on satisfaction that a registered investment company has ceased to be one, to issue an order declaring registration ceased. The notice exists to give interested persons a fixed window in which to request a hearing before any such order is granted by the Division of Investment Management under delegated authority.

Each notice plays a procedural-disclosure role. It identifies the applicant funds, summarizes the factual basis on which each claims to have ceased being an investment company, states when the underlying Form N-8F application was filed, and fixes a deadline for hearing requests. Typical bases for deregistration are complete liquidation and final distribution to shareholders, transfer of all assets to another registered investment company pursuant to an agreement and plan of reorganization, the representation that the applicant never made a public offering, qualification for an exclusion from the investment company definition (most commonly Section 3(c)(1) or Section 3(c)(7) of the 1940 Act), or conversion to a business development company. Because the originating filer on EDGAR is the Commission, the accession number is issued under the SEC's reserved filer CIK 9999999997 rather than the applicant's CIK.

The dataset includes all Form N-8F NTC filings submitted to EDGAR from April 2009 forward. It is delivered as monthly ZIP containers organized in a YYYY/YYYY-MM.zip path scheme, and the file-type surface is narrowly limited to PDF and JSON. No image files from the original EDGAR accession submission are included.

Content Structure of a Single Record

1. What one record represents

One record in the Form N-8F NTC Files Dataset is a single EDGAR accession used by the Securities and Exchange Commission to publicly notice a pending application for deregistration of a registered investment company under Section 8(f) of the Investment Company Act of 1940. Physically, a record is one accession-numbered folder containing exactly two artifacts: a structured metadata.json describing the EDGAR header and the applicant entity, and the Commission-issued notice document filename1.pdf.

A particular property of this dataset's record granularity matters before any other reading. The SEC's Division of Investment Management publishes a single monthly Investment Company Act Release that enumerates every fund whose Form N-8F application is pending in that month. EDGAR then mirrors that one consolidated notice into a separate accession for each applicant listed inside it. The dataset therefore emits one accession per applicant, not one accession per notice. Per-applicant identification (applicant CIK, 1940 Act file number, legal name) lives in metadata.json; the per-applicant narrative (basis for deregistration, application filing date, mailing address) lives only inside the shared PDF, which is byte-identical across every sibling accession that points to the same monthly notice.

2. Container layout and per-record file structure

The dataset is delivered as monthly ZIP containers organized in a YYYY/YYYY-MM.zip path scheme. Decompressing one monthly container yields a flat tier of accession-numbered subfolders, each named with the 18-digit dashless form of the EDGAR accession number (for example accession 9999999997-25-000289 becomes folder 999999999725000289). The leading 9999999997 segment identifies the Commission as the EDGAR filer of these notices.

Each accession folder contains exactly two files:

• metadata.json — the structured EDGAR header and applicant-entity block for the accession.
• filename1.pdf — the official Commission notice document.

No SGML submission wrapper, no -index.htm filing-index page, no exhibits, no XBRL instance, no image attachments, and no .txt complete-submission bundle are bundled inside the ZIP, even though the metadata layer carries a URL pointing to the .txt bundle on EDGAR. The file-types present in the dataset are therefore PDF and JSON only.

When a monthly notice lists multiple applicants, the PDF is byte-identical across every sibling accession folder for that month; the only distinguishing payload between siblings is the metadata.json, which keys each accession to one specific applicant.

3. The metadata.json payload

The metadata file is a single JSON object combining the EDGAR submission header with sec-api.io packaging fields. Its shape is stable across the dataset because every record shares the same form type and the same Commission filer prefix. The principal fields are:

• formType — always the string "N-8F NTC".
• accessionNo — the dashed 18-digit accession number (for example "9999999997-25-000289").
• filedAt — the ISO-8601 acceptance timestamp with an Eastern-time offset (-05:00 or -04:00).
• description — a free-text description from the EDGAR header. For these notices it typically carries Item YYYYMMDD tokens encoding both the notice's publication date and the Investment Company Act Release date (for example "Form N-8F NTC - N-8F Notice - Item 20250203 Item 20250131").
• linkToFilingDetails — absolute URL of filename1.pdf on www.sec.gov.
• linkToTxt — absolute URL of the complete-submission .txt bundle on EDGAR; the bundle itself is not packaged inside the ZIP.
• linkToHtml — absolute URL of the EDGAR -index.htm filing-index page.
• linkToXbrl — always an empty string; these notices carry no XBRL.
• documentFormatFiles[] — an enumeration of the documents the EDGAR submission references. Each element carries sequence, size, documentUrl, type, and an optional description. For these accessions the array enumerates the notice PDF and the complete-submission text URL.
• dataFiles — always an empty array for this dataset.
• seriesAndClassesContractsInformation — typically empty, since these notices advertise deregistration rather than ongoing series/class registration.
• items[] — the EDGAR Item codes parsed from the header, e.g. ["Item 20250203: ", "Item 20250131: "]; these encode the notice date and the release date and are not substantive disclosure items in the Form 8-K sense.
• id — an internal sec-api.io record identifier.
• entities[] — a single-element array describing the applicant entity to which this accession is keyed.

4. Entity object

The one element of entities[] describes the applicant investment company, not the Commission as the EDGAR filer. Its fields are:

• companyName — the applicant's legal name, generally suffixed with the EDGAR role marker (Filer) even though the Commission is the actual filer.
• cik — the applicant's CIK; this is the CIK that links each notice to the registrant's broader EDGAR history.
• fileNo — the Investment Company Act file number (the 811- series identifier), which is the canonical key for the deregistration application.
• irsNo — the applicant's IRS employer identification number, often zero-filled when not supplied.
• filmNo — the EDGAR film number.
• act — the statutory act code; "40" indicates the Investment Company Act of 1940.
• type — repeats the form type at the entity row level.
• stateOfIncorporation — the applicant's state of incorporation, when supplied.
• fiscalYearEnd — MMDD fiscal-year-end, when supplied.
• tickers — an array of trading tickers, when applicable; rare in practice for liquidating or never-publicly-offered funds.

stateOfIncorporation, fiscalYearEnd, and tickers are routinely absent for separate-account, insurance-product, or never-publicly-offered applicants.

5. The notice PDF (filename1.pdf)

The PDF is a four-page Commission release in the standard Investment Company Act Release No. [number] format issued by the Division of Investment Management. It follows a consistent two-part template: a procedural front matter shared by every applicant in the monthly notice, followed by a sequence of per-applicant blocks.

Front matter — agency, action, and hearing procedure

The opening page identifies the issuing agency ("Securities and Exchange Commission"), states the action ("Notice of applications for deregistration under Section 8(f) of the Investment Company Act of 1940"), and prints the Investment Company Act Release number and release date. It then sets out the boilerplate hearing-request procedure: any interested person may request a hearing on any of the listed applications by writing to the Commission's Secretary; the notice supplies the Commission's mailing address and the Secretary's office email (Secretarys-Office@sec.gov); and it fixes a hard deadline (date and 5:30 p.m. Eastern time) by which hearing requests must be received. The front matter also states that, absent a hearing request, an order granting each application will be issued by the Division of Investment Management under delegated authority on or about a stated date.

Per-applicant blocks

The remainder of the document is an ordered sequence of per-applicant blocks, one for each investment company seeking deregistration in that monthly notice. Each block follows the same template:

• A header line giving the applicant's legal name followed by its Investment Company Act file number in bracketed form [811-XXXXX].
• Summary: — a one- or two-sentence factual narrative explaining the basis for deregistration. Typical wording covers a complete liquidation with the date of final distribution to shareholders, a transfer of all assets to another registered investment company pursuant to an agreement and plan of reorganization (naming the acquiring entity and the closing date), a representation that the applicant never made a public offering of its securities, qualification for an exclusion such as Section 3(c)(1) or 3(c)(7), or conversion to a business development company.
• Filing Date(s): — the date(s) on which the underlying Form N-8F application (and any amendment) was filed with the Commission.
• Applicant's Address: — the applicant's mailing address as supplied in the application.

Signature

The notice closes with a signature block from an Assistant Secretary of the Commission, signed "For the Commission, by the Division of Investment Management, pursuant to delegated authority." There are no investor-facing exhibits, schedules, financial statements, or certifications attached to the release — the document is procedural and narrative throughout.

6. Content included in the record

A record packages:

• the structured metadata.json payload, including the applicant-keyed entities[0] block and the full set of EDGAR header URLs;
• the official Commission notice in PDF form, containing the procedural front matter, every per-applicant block for that month's notice, and the Assistant Secretary signature.

Because the PDF inside any one accession is the full multi-applicant notice rather than an applicant-specific excerpt, every record carries the disclosures for every applicant in that month, even though the metadata keys the accession to only one of them.

7. Content excluded or structurally separate

Several artifacts associated with the source EDGAR submission are deliberately not bundled into the dataset record:

• The EDGAR SGML complete-submission .txt bundle is referenced by linkToTxt and by documentFormatFiles[] but is not packaged inside the ZIP.
• The EDGAR -index.htm filing-index page is referenced by linkToHtml but is not packaged.
• Image files associated with the original EDGAR submission are excluded by design across the dataset.
• The underlying Form N-8F application itself — the substantive deregistration application filed by the fund, as opposed to this Commission-issued notice — is a separate EDGAR filing under the applicant's own CIK and is not part of this dataset.
• The eventual Form N-8F ORDR / deregistration order that the Division of Investment Management issues after the hearing-request window closes is a separate downstream filing under the Commission's 9999999997 filer prefix and is not part of this dataset.

There are no exhibits, certifications, financial tables, or attachments inside the notice itself, and linkToXbrl is empty in every record. The dataset's file-type surface is therefore narrowly limited to PDF and JSON.

8. Stability of structure over time

Form N-8F NTC has been issued in a stable Commission-release format throughout the dataset's coverage from April 2009 forward. Because the document is a procedural release rather than a registrant-prepared disclosure, it has not gone through the ASCII-to-HTML-to-iXBRL evolution that registrant filings experienced; it has been delivered as a PDF Commission release for the entire period. The internal template — procedural front matter, hearing-request mechanics, per-applicant blocks structured as [811-XXXXX] header / Summary: / Filing Date(s): / Applicant's Address: lines, Assistant Secretary signature under delegated authority — has likewise remained consistent. The most visible drift over time is the migration of the hearing-request channel from paper-only to the Secretarys-Office@sec.gov email address (a post-2020 procedural shift) and rotation in the names of the signing Assistant Secretaries. The metadata.json schema is constant across the dataset, with formType fixed to "N-8F NTC", act fixed to "40", and the 9999999997 filer-CIK convention used throughout.

9. Interpretation and extraction notes

Several anatomical features of the dataset bear directly on how a record should be read or programmatically extracted.

• Record granularity vs. notice granularity. The dataset emits one accession folder per applicant, but the PDF inside each is the consolidated multi-applicant Commission notice. When a monthly notice lists N applicants, N sibling accession folders contain byte-identical PDFs and differ only in their metadata.json. Deduplicating on PDF content hash collapses each month to a single notice document; grouping by accession recovers the per-applicant disclosure unit.
• Joining metadata to PDF text. Per-applicant detail (basis-for-deregistration Summary, application Filing Date(s), and Applicant's Address) lives only inside the PDF. To assemble a fully populated per-applicant record, match the entities[0].fileNo value from metadata.json against the corresponding [811-XXXXX] header inside the PDF; the company-name string is also reliable but is occasionally affected by punctuation or trailing-fund-suffix variation between EDGAR and the release text.
• Filer CIK vs. applicant CIK. The accession number's leading 9999999997 segment is the Commission's reserved filer CIK and does not identify a registrant. The applicant's CIK and 1940 Act file number live in entities[0].cik and entities[0].fileNo. Joins to other EDGAR datasets should always use the applicant's CIK or 811- file number, never the accession's filer prefix.
• EDGAR Item codes. The items[] array and the description string both carry Item YYYYMMDD tokens drawn from the EDGAR header. These encode the notice's publication date and the Investment Company Act Release date; they are date markers, not substantive disclosure-item identifiers as found on Form 8-K.
• No XBRL, no exhibits. Because the notice is a procedural Commission release rather than a registrant disclosure, there are no XBRL facts, no financial statements, and no certifications. Analysts seeking financial detail on a deregistering fund must follow the applicant's CIK back to its last N-CSR, N-CEN, or final liquidation filings, all of which sit outside this dataset.
• Outcome vs. notice. The notice signals only that an application is pending and sets the hearing-request deadline. The deregistration order itself is granted separately by the Division of Investment Management under delegated authority and appears on EDGAR as a distinct N-8F ORDR accession. The absence of a subsequent order accession can indicate that an application was withdrawn, denied, or remains under review.
• Text-extraction practicalities. The per-applicant blocks are reliably delimited by their [811-XXXXX] headers and by the fixed Summary: / Filing Date(s): / Applicant's Address: label sequence, which makes regex-based segmentation of the PDF text straightforward once the PDF is converted to plain text. Page breaks fall mid-block in some months, so any extractor should operate on the full document text rather than page-by-page.

Who Files or Publishes This Dataset, and When

Who issues the record

A Form N-8F NTC filing is not filed by the fund seeking deregistration. It is a notice issued by the SEC, prepared and released by the Division of Investment Management on behalf of the Commission. The "NTC" suffix marks it as a Commission-issued public notice that an application for an order under Section 8(f) of the Investment Company Act of 1940 has been filed and is pending action.

The three-document sequence is consistent:

• The applicant fund files Form N-8F (the deregistration application).
• The Commission issues Form N-8F NTC (the public notice that the application is on file and a hearing may be requested).
• The Commission later issues Form N-8F ORDR (the order granting deregistration).

Every record in this dataset is a Commission-issued notice, not an issuer-filed disclosure. The substantive content inside the notice (applicant name, 1940 Act file number, basis for deregistration, application date) originates in the underlying N-8F application.

The applicant population behind the notice

Every N-8F NTC corresponds to one or more applicants that are registered investment companies seeking an order under Section 8(f) declaring they have ceased to be investment companies. Typical applicants:

• Open-end management investment companies (mutual funds), often individual series of a registered trust, that have liquidated or merged.
• Closed-end management investment companies that have wound up or been acquired.
• Unit investment trusts (UITs) that have reached their stated termination date and distributed all assets.
• Business development companies (BDCs) deregistering as investment companies under Section 8(f).
• Registered funds that have converted into an operating company, holding company, or BDC.
• Entities that have qualified for an exclusion from the investment company definition, typically under Section 3(c) of the 1940 Act.

A single notice may cover multiple applicants, commonly related series within one trust complex deregistering together. Foreign private issuers and ordinary Exchange Act reporting companies do not appear here.

What triggers issuance

The proximate trigger is the filing of a Form N-8F application by a registered investment company. Once the Division of Investment Management reviews the application for completeness and substantive sufficiency under Section 8(f), the Commission publishes the N-8F NTC notice. The notice serves two procedural purposes:

1. Give public notice that an application is pending.
2. Open a window for interested persons to request a hearing before the Commission acts.

The underlying corporate event prompting the application is typically one of:

• Liquidation and final distribution to shareholders.
• Merger or reorganization into another registered fund or surviving entity.
• Conversion into a BDC or other entity outside the investment company definition.
• Qualification for an exclusion under Section 3(c) of the 1940 Act.

Regulatory framework and timing

The governing authority is Section 8(f) of the Investment Company Act of 1940, under which the Commission, upon application, may issue an order declaring that a registered investment company has ceased to be one. Registration cannot terminate without that order. The notice-and-hearing requirement runs through Section 40(a) of the 1940 Act and the SEC's Rules of Practice, which together mandate public notice and an opportunity to request a hearing before the Commission issues substantive orders.

The operative timing marker inside each PDF is the hearing-request deadline: a date stated on the face of the notice (typically a short window after issuance) by which any interested person must request a hearing. If none is requested and the application is meritorious, the Commission issues the N-8F ORDR granting deregistration.

The dataset begins in April 2009, reflecting the period of systematic EDGAR coverage; the Section 8(f) regime itself dates to the original 1940 Act.

Important distinctions

• Notice vs. application vs. order. N-8F is the applicant's filing; N-8F NTC is the Commission's public notice; N-8F ORDR is the Commission's final order. All three are distinct EDGAR submissions.
• Issuer of the record vs. party in interest. The Commission issues the record; the applicant is the named party whose status is being adjudicated. Treating the filer field as an issuer disclosure will misread the dataset.
• BDC election withdrawals. A BDC withdrawing its BDC election uses Section 54(c) of the 1940 Act, a separate mechanism. The N-8F path applies where the entity is deregistering as an investment company under Section 8(f).
• Operating company deregistration. Companies terminating Exchange Act reporting file Form 15, not Form N-8F.
• Never-registered entities. Funds that have always operated under a Section 3(c) exclusion never enter the Section 8(f) channel and produce no N-8F NTC record.

How This Dataset Differs From Similar Datasets or Filings

Form N-8F NTC sits in the middle of a three-document Investment Company Act deregistration sequence and inside the broader 1940 Act notice-and-order ecosystem. The most useful comparisons are to the documents that flank an NTC in time, the Exchange Act analog for non-fund issuers, the parallel exemptive-order machinery that looks structurally identical but addresses opposite substance, and the BDC withdrawal form that is the easiest to confuse operationally.

The N-8F deregistration trio: application -> NTC -> ORDR

The three closest records to this dataset are the other two stages of the same proceeding.

• Form N-8F (the application). Filed by the investment company. Contains the factual record: legal name, file number, basis for deregistration (merger, liquidation, Section 3(c) exclusion, BDC conversion), transaction narrative, distributions to shareholders, residual assets, officer certifications. Not in this dataset. Use it when you need the "why" and the transaction mechanics.
• Form N-8F NTC (this dataset). Issued by the Commission after the application is filed. A short procedural announcement: applicant name and file number, one-paragraph summary of the basis, date of the underlying N-8F, and hearing-request deadline. Carries no financial detail.
• Form N-8F ORDR (the order). Issued by the Commission after the hearing window closes without objection. The dispositive document: the applicant is declared no longer an investment company. Not in this dataset. Use it when you need the legal effective date of deregistration or a confirmed exit count.

Operational rule: NTC = queued; N-8F application = why; ORDR = actually happened. A fund's deregistration is not legally effective on the NTC date; it is effective on the ORDR date. Pipelines built only on NTCs will overstate completed exits because some applications are withdrawn or denied between NTC and ORDR.

Form 15 (Exchange Act deregistration)

The closest non-1940 Act parallel. Form 15 terminates Exchange Act reporting obligations under Sections 12(g)/15(d). Users conflate the two because both end a registration relationship with the SEC, but the regimes diverge sharply:

• Filer population. Form 15 is for operating-company and other non-fund issuers; N-8F is exclusively for registered investment companies.
• Mechanism. Form 15 is largely self-executing — reporting is suspended on filing and terminated after 90 days absent SEC action. N-8F requires an affirmative Commission order; the fund cannot deregister itself.
• Public-notice artifact. Form 15 has no Commission-issued notice because none is needed; the filing itself is the public record. N-8F has the NTC precisely because the Commission, not the filer, controls the outcome.

Use Form 15 datasets for operating-company exits; use N-8F NTC/ORDR for investment-company exits. They are not substitutable in either direction.

Form N-54C (BDC withdrawal) — the most confusable adjacent form

Form N-54C is the notice by which a business development company withdraws its BDC election under Section 54 of the 1940 Act. It is operationally easy to confuse with N-8F NTC because both can appear at a fund's exit from the 1940 Act, and "conversion to a BDC" is one of the four bases listed on the N-8F application itself. The boundaries are precise:

• Direction. N-54C is filed by an entity leaving BDC status (often a step toward leaving the 1940 Act entirely or returning to RIC status). N-8F seeks an order declaring the entity is no longer an investment company at all.
• Who issues it. N-54C is filer-issued; N-8F NTC is Commission-issued.
• Legal effect. N-54C alone does not deregister the entity from the 1940 Act — the entity may still need an N-8F order afterwards. N-8F ORDR is what actually terminates 1940 Act status.
• Related counterpart. Form N-54A is the BDC election notice (entry into BDC status). Neither N-54A nor N-54C appears in this dataset.

A complete BDC lifecycle study needs N-54A (entry), N-54C (BDC withdrawal), N-8F application/NTC/ORDR (1940 Act exit). This dataset supplies only the middle Commission notice in that exit chain.

The broader 1940 Act notice-and-order family: 40-APP / 40-NTC / 40-OIP / 40-OIPC

These forms share N-8F's procedural shape but address the opposite substantive request.

• 40-APP — applicant's request for exemptive relief under specific 1940 Act sections (fund-of-funds structures, ETF operating relief, joint transactions, affiliated transactions, etc.).
• 40-NTC — Commission notice that a 40-APP has been filed; structurally identical to N-8F NTC (summary, hearing deadline).
• 40-OIP / 40-OIPC — Commission notice of intent to issue an order, and the related conditional order.

The structural parallel is strong — all are Commission-issued procedural notices keyed to an underlying applicant filing, with a hearing-request window — which is why an automated pipeline scanning for "notices of application" can sweep them together. The substantive distinction is clean:

• 40-NTC announces a request to bend specific rules while staying inside the 1940 Act regime.
• N-8F NTC announces a request to exit the 1940 Act regime entirely.

If a workflow is filtering for fund deregistration events, 40-NTC filings must be excluded; if it is filtering for exemptive-relief activity, N-8F NTC filings must be excluded.

Boundary summary

In this dataset: Commission-issued notices announcing pending N-8F deregistration applications; applicant names and file numbers; one-paragraph summary of the deregistration basis; date of the underlying N-8F; hearing-request deadline; metadata plus all original EDGAR submission documents (PDF and JSON) except images; April 2009 to present.

Not in this dataset:

• The underlying applicant filing (Form N-8F application) — pull separately for transaction facts, distributions, certifications.
• The final order (Form N-8F ORDR) — pull separately to confirm completed deregistrations and obtain legal effective dates.
• Exchange Act deregistrations (Form 15) — different regime, different filer population.
• BDC election or withdrawal (Forms N-54A, N-54C) — filer-issued, different legal effect.
• Exemptive-relief notices (40-APP / 40-NTC / 40-OIP / 40-OIPC) — same procedural shape, opposite substantive direction.
• Fund periodic content (N-CEN, N-CSR, N-PX) — NAVs, voting, governance are elsewhere.
• Initial registration statements (N-1A, N-2, N-8B-2, S-6) — the lifecycle-entry counterpart to N-8F's lifecycle exit.

What makes this dataset distinct: it is the only SEC data product that captures, in one Commission-issued document type, the public-notice stage of every 1940 Act deregistration application since April 2009 — the pipeline view of fund exits, sitting between the applicant's factual filing (N-8F) and the dispositive order (N-8F ORDR), and not interchangeable with any of them.

Who Uses This Dataset

N-8F NTC notices mark the public step in a registered fund's exit under Section 8(f) of the 1940 Act. A defined set of professionals work directly off the applicant name, 811- file number, basis for deregistration, underlying N-8F filing date, hearing-request deadline, applicant CIK, and mailing address.

Investment Company Act counsel

Attorneys in fund-formation and 1940 Act practices mine prior notices to draft new N-8F applications. They pull every notice citing a given basis for deregistration (merger, liquidation, exclusion qualification, or BDC conversion), read the staff's framing of the basis text, and measure the elapsed days from application date to NTC issuance to set client expectations. The 811- file number and applicant CIK are used to cross-reference earlier filings; the hearing-request deadline defines the comment window they advise interested parties on.

Fund administrators and chief compliance officers

CCOs and administrators at fund complexes plan terminal NAV strikes, final N-CEN/N-PORT submissions, and registration closure around the deregistration timeline. They monitor the applicant name and 811- file number against their own pending wind-downs, use the underlying N-8F filing date and hearing-request deadline to set internal cutoff calendars, and review notices for affiliated funds to confirm successor-entity language before signing off on merger documentation.

Fund-universe reference data teams

Data engineers at financial-data vendors maintain security masters and fund taxonomies. They join the 811- file number and applicant CIK against internal fund identifiers, flip status to "deregistration pending" on the NTC publication date, and parse the basis-for-deregistration text to set the exit-reason attribute. Merger-basis notices trigger lineage updates that link the exiting fund to its surviving entity.

Corporate-action and lifecycle data engineers

Engineers building corporate-action feeds parse the JSON metadata for accession-level fields and extract the applicant name, 811- file number, basis for deregistration, and hearing-request deadline from the PDF notice to populate regulatory end-date and exit-reason columns. These attributes drive ticker retirement, data-ingestion suppression, and successor-entity linkage downstream.

Closed-end fund and BDC event-driven analysts

Analysts trading closed-end fund terminations and BDC conversions treat the NTC as the near-final confirmation event before the deregistration order. They watch the basis for deregistration to distinguish liquidating distributions from merger consummation, and use the hearing-request deadline to time discount-capture and event-arbitrage positions, since the order typically follows shortly after that deadline absent objection.

Market-structure and fund-attrition researchers

Sell-side strategists and academic researchers studying fund mortality build longitudinal panels from the 2009-onward record. The basis for deregistration is the dependent variable in competing-risks and survival models; applicant name, CIK, and 811- file number link each exit to performance and flow histories from other sources; the underlying N-8F filing date anchors event-time windows. Outputs include working papers on complex-level rationalization and the boundary between registered, BDC, and private-fund status.

Transfer agents and fund-services providers

Service providers wind down shareholder accounting, tax reporting, and contractual obligations when a fund client deregisters. They match the applicant name, mailing address, and 811- file number to internal client records, and key off the basis for deregistration to route the file to the correct liquidation or merger-conversion playbook. The hearing-request deadline sets the date after which they expect the Commission order and final off-boarding.

Financial trade-press reporters

Reporters covering fund closings use the notice to verify exit timing and to distinguish a true liquidation from a merger into a surviving fund — a distinction that materially changes how shareholder outcomes are reported. The applicant name, basis for deregistration, underlying N-8F filing date, and hearing-request deadline supply the verifiable facts behind each story.

Synthesis

The user base clusters into five groups: 1940 Act counsel and CCOs running the deregistration process, administrators and service providers aligning operational wind-down with the regulatory clock, data and lifecycle engineers maintaining fund-universe integrity, event-driven analysts and academic researchers studying exits, and trade-press reporters verifying closures. Each works from the same compact field set: applicant name and CIK, 811- file number, basis for deregistration, underlying N-8F filing date, and hearing-request deadline.

Specific Use Cases

The following workflows show how practitioners operationalize Form N-8F NTC records. Each draws on a specific field combination from metadata.json and the per-applicant blocks inside the notice PDF.

1. Maintaining fund-status flags in a security master

Reference-data teams ingest each monthly batch, key on entities[0].fileNo (the 811- number) and entities[0].cik, and flip the matched fund's status from "registered" to "deregistration pending" on the filedAt date. The Summary: block inside the PDF is parsed to populate an exit-reason attribute (liquidation, merger, 3(c)(1)/3(c)(7) exclusion, BDC conversion), and merger-basis records trigger a successor-entity link that points the exiting CIK to the acquiring fund named in the summary text.

2. Sizing the deregistration-pipeline backlog and processing latency

Operations and policy researchers compute, per record, the elapsed days between the Filing Date(s): value inside the PDF and the notice's own filedAt timestamp. Aggregated across the panel from April 2009 forward, this yields monthly application-to-NTC latency curves, backlog levels by basis category, and seasonal patterns useful for setting client expectations on new N-8F applications.

3. Drafting new N-8F applications from analogous priors

Investment Company Act counsel filters the dataset for prior NTCs sharing the client's deregistration basis (for example, "transfer of all assets pursuant to an agreement and plan of reorganization" or "never made a public offering"), extracts the Summary: paragraphs, and uses the staff's preferred phrasing as a template. The entities[0].cik and fileNo on matched records support pulling the underlying applications from EDGAR for full transaction-mechanics comparison.

4. Event-driven trading around closed-end fund and BDC exits

Analysts running discount-capture and merger-arb books extract the hearing-request deadline from the front matter of each notice and the basis text from each per-applicant block. They size positions in funds where the basis is a confirmed merger or liquidation, knowing the Commission order is typically issued shortly after the deadline absent objection. Sibling accessions sharing one byte-identical PDF are deduplicated by content hash so each monthly cohort is treated as one event.

5. Building a longitudinal fund-mortality panel

Academic and sell-side researchers join entities[0].cik and fileNo against CRSP, N-CEN, and N-PORT histories to attach AUM, age, expense ratio, and flow data to each exit. The parsed Summary: text becomes the categorical dependent variable in competing-risks models distinguishing liquidation, merger-driven attrition, exclusion qualification, and BDC conversion across complexes and time.

6. Cross-referencing with N-8F ORDR to identify withdrawn or denied applications

Lifecycle pipelines join this dataset's entities[0].fileNo against the downstream N-8F ORDR accessions on EDGAR (filer CIK 9999999997). NTC records without a matching ORDR within an expected window are flagged as withdrawn, denied, or stalled — a signal that the fund's deregistration is not legally effective and that any "exit" flag set on the NTC date must be rolled back.

7. Calendar-driven wind-down at fund administrators and transfer agents

Fund administrators and transfer agents match the applicant name, mailing address, and 811- file number against client books, then key internal cutoffs (final NAV strike, terminal N-CEN, shareholder-account closure) off the hearing-request deadline. The basis text routes the file to the correct playbook — liquidation distribution mechanics versus merger-conversion successor handling — before the expected Commission order arrives.

Dataset Access

The Form N-8F NTC Files Dataset is accessible through a JSON index endpoint that describes the dataset's contents, and through download endpoints for both the full archive and individual monthly containers.

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

This endpoint returns the dataset catalog, including the name, description, last updated timestamp, earliest sample date (2009-04-01), total records, total size, form types covered (N-8F NTC), container format (ZIP), file types (PDF, JSON), the download URL for the full archive, and the complete list of monthly containers with per-container metadata such as size, records, updated timestamp, and download URL. This endpoint does not require an API key and can be polled to monitor which containers were updated in the most recent refresh run, allowing you to download only the containers that changed.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-6987-9aea-31d67d4cd8ea",
        

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

          4
            "name": "Form N-8F NTC Files Dataset",
        

          5
            "updatedAt": "2026-04-28T03:03:25.276Z",
        

          6
            "earliestSampleDate": "2009-04-01",
        

          7
            "totalRecords": 2171,
        

          8
            "totalSize": 132593761,
        

          9
            "formTypes": ["N-8F NTC"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

          14
                "downloadUrl": "https://api.sec-api.io/datasets/form-n8f-ntc-files/2026/2026-04.zip",
        

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

          16
                "size": 1842310,
        

          17
                "records": 18,
        

          18
                "updatedAt": "2026-04-28T03:03:25.276Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

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

Downloads the complete dataset as a single ZIP archive covering all Form N-8F NTC filings from April 2009 to present. This endpoint requires an API key passed as the token query parameter.

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

Downloads a single monthly container ZIP using the key value from the dataset index (for example 2026/2026-04.zip). Use this endpoint to fetch only the months you need rather than the full archive. This endpoint requires an API key passed as the token query parameter.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers the EDGAR submission type N-8F NTC — the "Notice" variant of Form N-8F that the SEC issues to publicly notice pending applications for deregistration of registered investment companies under Section 8(f) of the Investment Company Act of 1940. It does not include the underlying Form N-8F application filed by the fund, nor the Form N-8F ORDR deregistration order issued afterward.

What does one record in this dataset represent?

One record is a single EDGAR accession keyed to one applicant investment company. Physically it is an accession-numbered folder containing exactly two files: a structured metadata.json describing the EDGAR header and the applicant entity, and filename1.pdf, the Commission-issued notice document. When a monthly Investment Company Act Release lists multiple applicants, EDGAR emits one accession per applicant, and the PDF inside each sibling accession is byte-identical.

Who issues these filings?

Form N-8F NTC notices are issued by the SEC itself, prepared and released by the Division of Investment Management under delegated authority — not by the deregistering fund. Each accession is filed under the Commission's reserved filer CIK 9999999997; the applicant fund's own CIK and 1940 Act 811- file number appear in the entities[] block of metadata.json.

What time period does the dataset cover?

The dataset covers all Form N-8F NTC filings submitted to EDGAR from April 2009 to the present, reflecting the period of systematic EDGAR coverage for this submission type. The Section 8(f) deregistration regime itself dates to the original Investment Company Act of 1940.

What file format is the dataset distributed in?

The dataset is delivered as monthly ZIP containers organized in a YYYY/YYYY-MM.zip path scheme. Inside each container, every accession folder contains exactly two files — a metadata.json and a filename1.pdf — so the only file types present in the dataset are PDF and JSON. Image files from the original EDGAR submission, the SGML .txt complete-submission bundle, and the -index.htm filing-index page are excluded.

How does this dataset differ from Form N-8F ORDR filings?

Form N-8F NTC is the public notice that a deregistration application is pending and that interested persons may request a hearing; Form N-8F ORDR is the Commission's final order declaring that the applicant has ceased to be an investment company. A fund's deregistration is not legally effective on the NTC date — it is effective on the ORDR date. Pipelines built only on NTCs will overstate completed exits because some applications are withdrawn or denied between NTC and ORDR.

How do I distinguish N-8F NTC notices from the broader 40-NTC family?

Both are Commission-issued procedural notices with hearing-request windows and a similar structural shape, but they address opposite substantive requests. N-8F NTC announces a request to exit the 1940 Act regime entirely (deregistration); 40-NTC announces a request for exemptive relief while staying inside the 1940 Act regime. Workflows filtering for fund deregistration events must exclude 40-NTC filings, and workflows filtering for exemptive-relief activity must exclude N-8F NTC filings.