The Form 24F-2TM Files Dataset is a closed historical corpus of EDGAR submissions through which open-end management investment companies, face-amount certificate companies, and unit investment trusts formally terminated their declarations of election to register an indefinite number of securities under Rule 24f-2 of the Investment Company Act of 1940. Each record represents one complete EDGAR submission of a Form 24F-2TM termination notice, identified by its accession number and materialized on disk as a per-accession folder containing one metadata.json and one or more document-N.txt files — typically the thirteen-item form notice plus an Exhibit 5 legal opinion of counsel. The legal filer is the registered investment company itself, although the form is frequently signed by a sponsor, depositor, trustee, or principal underwriter acting as agent. The dataset spans submissions from February 1994 — when investment company filings were phased onto EDGAR — through the form's eventual retirement, after amendments to Rule 24f-2 reorganized the indefinite-registration regime and EDGAR stopped accepting new submissions. Filings are distributed as monthly ZIP containers holding plain-text TXT payloads alongside per-filing JSON metadata.
Programmatically retrieve the full list of dataset archive files, download URLs and dataset metadata.
Dataset Index JSON API
Download the entire dataset as a single archive file.
Download Entire Dataset:
Download a single container file (e.g. monthly archive) from the dataset.
Download Single Container:
The dataset captures every EDGAR submission of Form 24F-2TM, the terminating variant of the Rule 24f-2 annual-notice family. Rule 24f-2 historically allowed certain investment companies to register an indefinite number of shares prospectively and pay registration fees retroactively, on a fiscal-year basis, via Form 24F-2 (the "Annual Notice of Securities Sold Pursuant to Rule 24f-2"). The "TM" suffix denotes the variant filed when an issuer ends its standing election under Rule 24f-2(a)(1), reconciles any final fee owed for the partial registration period, and exits the indefinite-registration regime.
Form 24F-2TM is administrative and reporting-oriented rather than disclosure-oriented: it does not contain risk discussion, MD&A, or financial statements. Its content is dominated by issuer identification, fund-series identification, fiscal-year boundary information, and a closely scripted fee calculation that reconciles units sold against units redeemed and computes any residual amount due to the SEC at the rate of 1/33rd of 1% of net sales. The form was filed in EDGAR from February 1994 onward and was eventually retired; EDGAR no longer accepts new submissions of this form type, so the dataset is bounded on the early side by EDGAR's adoption of the form in early 1994 and on the late side by the form's retirement.
The dataset is delivered as monthly ZIP containers holding plain-text document payloads and per-filing JSON metadata. The on-disk file types are TXT and JSON. Image files that may have accompanied the original submissions are excluded; everything else is present as plain text after the EDGAR SGML envelope is stripped during extraction.
A single record is one complete EDGAR submission of a Form 24F-2TM notice. Each record is identified by its EDGAR accession number and is materialized on disk as a per-accession folder containing one metadata.json describing the submission and one or more document-N.txt files carrying the plain-text payloads of the form and any accompanying exhibits. The unit of the record is therefore the filing — not the issuer, not the fund series, and not any single document — although in practice almost every 24F-2TM submission consists of exactly two documents: the numbered form notice and an EX-5 legal opinion of counsel.
The dataset is delivered as monthly ZIP containers. Each ZIP holds a single top-level directory named for its year and month (YYYY-MM/); beneath that directory sits one sub-folder per filing. Each sub-folder is named after the EDGAR accession number with the hyphens stripped, yielding an 18-digit numeric string (for example 000093485097001526); the canonical dashed form (0000934850-97-001526) is preserved inside metadata.json rather than on the file system.
Every accession folder contains:
metadata.json describing the submission, anddocument-N.txt per real component of the original EDGAR submission, where N is the integer sequence number assigned in the SGML envelope.The document-N.txt payloads are not raw EDGAR .txt submissions. The SGML envelope (<SEC-DOCUMENT>, <DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, <TEXT> and their closing tags) is stripped during extraction; only the inner document body remains. The original <FILENAME> value is not preserved as the on-disk filename — the positional convention document-<sequence>.txt is used instead, and the mapping back to the original EDGAR sequence and document type is recovered through the documentFormatFiles[] array in metadata.json.
metadata.json structuremetadata.json is the authoritative index for the record. Its top-level fields describe the filing as a whole:
formType — always the string "24F-2TM".accessionNo — the EDGAR accession number in the standard dashed 18-digit format.description — a fixed human-readable descriptor identifying the filing as a Form 24F-2TM termination of declaration of election under Rule 24f-2.filedAt — the filing timestamp as ISO-8601 with an Eastern offset (-04:00 or -05:00 depending on daylight saving), typically with a midnight time component because Form 24F-2TM is filed on a per-day basis without an intraday timestamp.linkToFilingDetails — URL to the filer's EDGAR archive root for the relevant CIK.linkToTxt — URL to the original SGML-wrapped complete submission .txt on EDGAR.linkToHtml — URL to the EDGAR -index.htm overview page for the accession.linkToXbrl — empty string for this form type.id — a 32-character hex internal identifier for the record.Three array fields catalogue the components of the submission:
documentFormatFiles[] — one entry per submission component plus a trailing synthetic entry that points at the complete-submission .txt URL. Each entry exposes sequence (a string such as "1", "2", or a single space " " for the trailing summary row), size (byte size as a string), documentUrl (a URL to either the individual component or the full submission .txt for the summary row), type (the EDGAR document type — "24F-2TM" for the form, "[EX-5](https://www.ecfr.gov/current/title-17/chapter-II/part-229/subpart-229.600/section-229.601#p-229.601(b)(5))" for the legal-opinion exhibit, and " " for the summary row), and an optional description (typically populated for EX-5 with values such as "NOTICE OPINION" and for the summary row with "Complete submission text file"). The on-disk count of document-N.txt files equals the length of this array minus the trailing summary row.entities[] — one entry per filer entity associated with the submission. For 24F-2TM filings there is typically a single filer. Each entry contains companyName (with a parenthesized role suffix such as " (Filer)"), cik (numeric string, unpadded), fileNo (the SEC file number, e.g. 033-00941 or 002-93490), type (the EDGAR form type for that entity's role, here "24F-2TM"), act (the securities act under which the file number was issued, typically "33" for the Securities Act of 1933), stateOfIncorporation (two-letter state code), fiscalYearEnd (four-digit MMDD), sic (Standard Industrial Classification code; frequently "0000" for unit investment trusts of this vintage that were never assigned a meaningful SIC), and filmNo (the EDGAR film/microfiche identifier).seriesAndClassesContractsInformation[] — empty for 24F-2TM filings; the EDGAR series-and-classes registration framework was introduced after this form's lifecycle and the array is reserved for newer schemas.dataFiles[] — empty for 24F-2TM filings; no structured data exhibits were carried by this form type.document-1.txtThe first document in every record is the form notice, structured as a numbered list of items 1 through 13 in the form's prescribed order. The content is plain text rendered from the original ASCII or HTML submission, with the SGML envelope removed.
-TM variant from a regular 24F-2 annual notice. It occasionally appears as "Not Applicable" when termination is being effected by the filing itself.1/33rd of 1% multiplier to the net amount, and arrives at the fee due. In termination filings this section is often dominated by zeros except for sub-item (iii), which carries the aggregate price of shares redeemed or repurchased during the final period.After item 13 the document concludes with a SIGNATURES block. The signature block carries a typed /s/-prefixed signature line, the signer's printed name, the signer's title (typical examples include "Vice President" or analogous officer titles for the agent or sponsor), and a date that reconciles to the filedAt timestamp in the metadata. Where the filer is a sponsor's agent — for example, a broker-dealer acting as agent for the sponsors of a defined-asset trust series — the signature block identifies the agent capacity explicitly.
document-2.txtForm 24F-2TM filings are accompanied, almost without exception, by an Exhibit 5 opinion of counsel. EX-5 is the legality-of-securities opinion required as part of registration-related filings: counsel's formal view that the securities registered under Rule 24f-2 during the period covered by the notice were duly authorized and, when issued in accordance with the relevant trust or organizational documents and upon receipt of the agreed consideration, were legally issued, fully paid, and non-assessable.
The exhibit is short — typically well under sixty lines of text — and is rendered as a letter on counsel's letterhead, addressed to the issuer or to the sponsor's agent, dated, and concluded with a /s/-style signature line identifying the law firm. The body usually:
The exhibit's documentFormatFiles[] entry typically carries a description such as "NOTICE OPINION" to distinguish it from other EX-5 use cases. In rare filings additional exhibits or an absent EX-5 may be observed, in which case the documentFormatFiles[] array reflects the actual composition and the on-disk document-N.txt files follow the same sequence-based naming convention.
The dataset includes:
metadata.json per filing that exposes the submission's identifying fields, filer-entity attributes, and the full documentFormatFiles[] index.Excluded from the dataset are:
<FILENAME> values, which are replaced by the positional document-N.txt naming convention.The seriesAndClassesContractsInformation[] and dataFiles[] arrays in metadata.json are present in the schema but unused for this form type because the corresponding EDGAR registration layers and structured-data exhibits were not in scope when 24F-2TM filings were active.
Form 24F-2TM was introduced into the EDGAR universe in February 1994 alongside the broader 24F-2 family and remained substantively stable through its life. The thirteen-item structure described above persisted across the entire run of the dataset, anchored to the underlying Rule 24f-2 fee-reconciliation framework. Within that life span the only material content evolution involved minor refinements to the fee-calculation worksheet in item 12 (the breakdown of redemptions, dividend reinvestments, and the application of the 1/33rd of 1% multiplier) and the gradual standardization of the lockbox remittance checkbox in item 13 as the SEC migrated fee handling to its depository institution.
The larger regulatory change is what ultimately retired the form: amendments to Rule 24f-2 streamlined the indefinite-registration regime and reorganized fee reporting under Form 24F-2 generally, after which the terminating-variant Form 24F-2TM ceased to be accepted by EDGAR.
Throughout the form's EDGAR lifetime, 24F-2TM filings were submitted under EDGAR's SGML envelope convention. Within that envelope, individual documents in the earliest filings were predominantly ASCII plain text with positional formatting (fixed-column layouts for item numbers and dollar figures); later filings increasingly embedded HTML markup inside the <TEXT> block of the SGML wrapper. In both cases the dataset's extraction step removes the SGML envelope and surfaces only the inner document body as document-N.txt. The fee-calculation worksheet in item 12 is preserved as a text-rendered tabular layout (with whitespace alignment) rather than as structured data, which matters when extracting the (i) through (vi) sub-items programmatically.
Several practical points matter when working with these records.
Document count. The relationship between documentFormatFiles[] and the on-disk files is positional via sequence. The trailing array entry whose sequence and type are both a single space (" ") is a synthetic summary row pointing at the complete-submission .txt URL on EDGAR; it is not extracted to disk and should be filtered out before counting documents. The number of document-N.txt files equals the length of documentFormatFiles[] minus one for that summary row.
Per-filing variation is concentrated in a small number of fields. Across batch filings by the same agent for related fund series, the issuer name and series name (items 1 and 2), file numbers (item 3), state of incorporation, and the redemption/repurchase amount in item 12(iii) typically vary, while the structural fields, signature party, and EX-5 issuer are stable. Many termination notices report zeros across items 9, 10, and 12 except for the redemption sub-item, reflecting the wind-down nature of the filing.
Accession-number reconciliation. The accession-number folder naming uses the unhyphenated 18-digit form, so callers reconciling against EDGAR's standard dashed accession format must add the dashes (NNNNNNNNNN-YY-NNNNNN) or read accessionNo from metadata.json directly. The CIK in entities[].cik is unpadded, and the fileNo carries the leading two-digit act prefix (033- or 002- for Securities Act of 1933 file numbers).
Batch filings. 24F-2TM filings frequently arrive in tightly sequenced batches from a single sponsor or agent covering multiple fund series filed on the same day, so accession numbers within a single monthly container may differ only in the trailing serial digits and reference closely related issuers. Joining records by entities[].cik, by sponsor-agent name, or by filing date is therefore often more informative than treating each accession as fully independent.
Historical interpretation. Because the dataset is closed and the form is retired, field semantics must be interpreted in the regulatory context that prevailed during the 1994-through-retirement window of Rule 24f-2, including the 1/33rd of 1% fee rate baked into item 12 and the fiscal-year reconciliation logic that drives the entire form. Newer EDGAR conventions (series-and-classes identifiers, structured fee exhibits, inline tagging) that postdate the form do not apply.
Each Form 24F-2TM is a notice filed by a registered investment company that had previously made a declaration of election under Rule 24f-2 and is now terminating that election for a specific Securities Act registration statement. The legal filer is the investment company registrant, identified by its 1940 Act file number (the 811- prefix) and Securities Act file number (typically 033- or 002-).
In practice, the form is often signed by a sponsor, depositor, trustee, or principal underwriter acting on the registrant's behalf — common in the unit investment trust context, where a broker-dealer signs "as Agent for the Sponsors." That delegation is administrative; the disclosure obligation rests with the investment company itself.
Only the three categories of investment company eligible to make a Rule 24f-2 election appear:
Closed-end funds and business development companies do not continuously offer redeemable securities, were not eligible for Rule 24f-2, and never appear in this dataset. Operating-company issuers reporting under the Exchange Act are entirely outside the regime.
Section 24(f) of the 1940 Act lets the Commission permit registration of an indefinite number of investment company shares. Rule 24f-2 implemented that authority. An eligible issuer filed a one-time declaration of election to register an indefinite number of securities under the Securities Act of 1933, with registration deemed effective as shares were sold. In return, registration fees were paid retrospectively each fiscal year on Form 24F-2, calculated under Section 6(b) of the 1933 Act (the historical "1/33rd of 1%" multiplier in the form's worksheet) on net sales after redemptions.
A declaration of election persisted indefinitely until the issuer terminated it. Termination typically occurred when:
Form 24F-2TM is the notice of that termination. It both notified the SEC that the indefinite registration was being shut down for the identified fund and carried the final fee reconciliation for the stub period between the prior annual notice and the termination date.
A 24F-2TM filing is event-driven, not periodic. The trigger is the issuer's decision to terminate its Rule 24f-2(a)(1) declaration for a specific fund, series, or registration statement. Item 6 of the form captures the date of termination of the declaration, anchoring the filing to that event.
Timing followed Rule 24f-2 and the form's instructions. The annual Form 24F-2 was due within a defined window after fiscal year end (60 days for much of the relevant period); the terminating variant replaced or supplemented that annual notice for the final partial period and was filed in connection with the termination itself. Item 5 includes a checkbox for cases filed more than 180 days after fiscal year end, accommodating terminations effected well into the following fiscal year.
A given fund could only file Form 24F-2TM once per registration statement. Sponsored UIT families, however, often produced clusters of 24F-2TM filings on a single day — one per series being terminated — yielding tightly sequenced accession numbers tied to a single sponsor or agent.
The filing rests on a layered structure:
Most records also include an Exhibit 5 legal opinion confirming that the shares sold under the indefinite registration during the covered period were duly authorized and, when issued, legally issued, fully paid, and non-assessable.
Form 24F-2TM appeared on EDGAR in February 1994 as investment company filings were phased onto the system; the dataset's earliest sample date of 1994-02-01 reflects EDGAR onboarding, not the introduction of Rule 24f-2. The form was retired when the SEC amended Rule 24f-2 to restructure how investment companies pay registration fees on continuously offered shares. Annual fee reconciliation moved to a successor reporting framework, and the older declaration-of-election structure ceased to exist in the same form. With no Rule 24f-2(a)(1) declaration of that character left to terminate, the terminating-variant notice lost its regulatory role and EDGAR stopped accepting new submissions.
Form 24F-2TM occupies a narrow niche: a one-time terminating notice in the Rule 24f-2 fee-administration lifecycle under the Investment Company Act of 1940. The most informative comparisons are to other 24f-2 family filings, the broader fund-exit forms (N-8F, Form 15), and the periodic fund reports filed by the same registrant population (N-SAR/N-CEN). Each touches the same filers, but each answers a different legal or operational question.
Form 24F-2 (annual notice). The single most directly related form. 24F-2 is the recurring annual notice through which a fund reports prior-year share sales and pays the corresponding registration fee while the indefinite-registration election remains in force. 24F-2TM is its terminal counterpart: filed once, it closes the election rather than continuing to report sales. A fund's 24F-2 series and its single 24F-2TM should be read together to reconstruct the full indefinite-registration history.
Form 24F-2NT (notice). A supplemental notice within the 24f-2 regime, typically used for informational updates tied to an active election (timing, NAV, related notifications). 24F-2NT may recur during a fund's life and presupposes a continuing election; 24F-2TM is terminal and ends the relationship.
Form 24F-1. The predecessor share-registration mechanic that preceded the Rule 24f-2 annual-notice regime. 24F-1 records earlier registration steps, not termination, and is primarily of historical interest when tracing the lineage of indefinite-registration practice.
Rule 24f-2 declaration of election. The affirmative filing that creates the indefinite-registration relationship 24F-2TM unwinds. No content overlap, but every 24F-2TM implies a prior election in the registrant's history.
Form N-8F (deregistration of an investment company). The Section 8(f) application by which a fund exits 1940 Act registration entirely. N-8F ends the fund's status as a registered investment company; 24F-2TM only ends one fee-administration election within that status. A fund can file 24F-2TM and continue operating under a different registration approach. The two may appear in proximity during a wind-down but resolve different legal questions.
Form 15 (Exchange Act deregistration). Terminates 1934 Act reporting for a class of securities. It lives in the Exchange Act world; 24F-2TM lives in the 1940 Act registration-fee world. No substantive overlap with the 24f-2 election.
Form N-SAR / Form N-CEN. N-SAR was the semi-annual operational report; N-CEN replaced it as an annual census filing in 2018. Both are recurring operational disclosures (board, service providers, share activity) covering the fund's life. Overlap with 24F-2TM is limited to filer population; neither records fee-election terminations.
Form N-Q / N-PORT and Form N-30D / N-30B-2. Holdings reports (N-Q, now N-PORT) and shareholder reports (N-30D, N-30B-2) sit on the disclosure side of fund reporting. They share filers with 24F-2TM but contain no information about Rule 24f-2 elections.
Because EDGAR no longer accepts 24F-2TM and Rule 24f-2 itself was restructured, modern fee administration runs through registration-statement amendments and current fee-payment mechanics rather than a dedicated termination form. There is no like-for-like successor; 24F-2TM should be treated as a closed historical series.
24F-2TM is distinct on three axes: it is event-driven, not periodic (unlike 24F-2, N-SAR, N-CEN, N-PORT, N-30D); it is election-specific, not entity-level (unlike N-8F); and it operates under the 1940 Act fee regime, not Exchange Act reporting (unlike Form 15). Its sole function is to close a specific indefinite-registration arrangement, making it useful for reconstructing the end of a fund's 24f-2 activity and for pairing with prior 24F-2 annual notices to compute final fee positions, but not a substitute for any operational, financial, holdings, or broader deregistration dataset.
The Form 24F-2TM Files Dataset is an archival reference. Users mostly need three things from each record: registrant identity (CIK, SEC file number, name), termination date, and final-period fee treatment.
Compliance staff at open-end fund sponsors, face-amount certificate issuers, and UIT depositors use the dataset to confirm that legacy vehicles formally exited Rule 24f-2 before being merged, liquidated, or repurposed. They reconcile CIK and termination date against internal registration logs to close out registration obligations on entities the firm still controls.
Fund counsel pull these filings when structuring deregistrations on Form N-8F, fund mergers, and reorganizations of legacy product lines. The fee-calculation section is what matters: counsel needs evidence that final-period fees were properly computed before signing off on a successor registrant's filing history.
Audit teams reconstructing historical registration-fee accruals or restating prior periods use the final fee and adjustment fields to reconcile SEC fees paid over the indefinite-registration period against actual share issuances through the termination date.
Administrators servicing legacy series and UITs use the termination date to close out closing-period share-issuance accounting. Transfer agents handling escheatment, estate research, and long-tail shareholder lookups rely on the registrant identifiers to confirm a fund's exit from indefinite-shares registration on a specific date.
In fund-related disputes, breach-of-fiduciary-duty matters, and successor-liability cases, support teams cite the original submission and accession metadata as a primary EDGAR record. Registrant name, CIK, and file number anchor cross-references to other filings in the same fund family.
Diligence teams evaluating acquisitions of fund advisers or UIT sponsor roles use the dataset to verify that every legacy vehicle's indefinite-shares election was properly terminated, so the acquirer does not inherit residual registration or fee exposure.
Teams maintaining fund-master databases and corporate-action histories ingest the dataset to attach a structured termination-of-election event to legacy CIKs. Output feeds fund-status timelines, deregistration trackers, and successor-fund mappings.
Researchers studying mutual fund mortality, UIT lifecycles, and the post-NSMIA evolution of Rule 24f-2 treat the termination date as a survival-analysis variable and join the records to N-SAR, N-1A, and N-8F histories. The form's retirement gives the dataset a defined, closed population, useful for cohort and event-study designs.
Teams building fund-law retrieval systems include the dataset so corpora cover retired form types. The submission text and metadata serve as grounding for questions about Rule 24f-2 mechanics and specific historical terminations.
The Form 24F-2TM Files Dataset supports a focused set of retrospective workflows built around three core fields per record: registrant identity (CIK, SEC file number, name), the Rule 24f-2(a)(1) termination date in item 6, and the final-period fee reconciliation in item 12. Because the corpus is closed and spans February 1994 through EDGAR's retirement of the form, every use case below is archival in nature.
Acquirer-side diligence teams join the target's legacy CIKs against entities[].cik and entities[].fileNo across the dataset to confirm that every open-end fund, face-amount certificate company, or UIT in the seller's history filed a 24F-2TM before being merged, liquidated, or repurposed. The item 6 termination date and the item 12 fee reconciliation provide the evidence that no residual indefinite-registration obligation transfers with the deal. Output feeds a deal-level checklist of registrant exits to the closing memo.
Audit teams restating prior periods or unwinding registration-fee accruals extract item 9 (gross sales), item 10 (sales relying on Rule 24f-2), item 11 (DRIP issuances), and the item 12 sub-items (i) through (vi) — particularly sub-item (iii) for redemptions and repurchases — and apply the 1/33rd of 1% multiplier to verify the final fee paid to the SEC. Pairing each 24F-2TM with the registrant's prior Form 24F-2 annual notices yields a complete fee history through termination.
Fund-data engineering teams parse metadata.json plus item 6 of document-1.txt to emit one termination event per legacy CIK, keyed by accessionNo and the dashed file number (033-, 002-, or 811-). The resulting table attaches to fund-status timelines, deregistration trackers, and successor-fund mappings, distinguishing 24f-2 election termination from full 1940 Act deregistration captured in N-8F.
Academic and regulatory researchers treat the item 6 termination date as a right-censored survival-analysis variable and join records by CIK to N-SAR, N-CEN, N-1A, and N-8F histories. The closed nature of the corpus and its concentration of UIT filers (often with sic "0000" and 002-prefixed file numbers) supports cohort designs studying post-NSMIA changes to Rule 24f-2 and event studies around fund-family wind-downs.
Litigation support, fund counsel, and historians use the tendency of 24F-2TM filings to arrive in same-day batches from a single sponsor or agent. Grouping accessions by signer in the signature block, by EX-5 law-firm letterhead in document-2.txt, and by filedAt date reveals coordinated terminations across related fund series — useful for tracing sponsor exits from defined-asset trust programs and for cross-referencing related accessions in successor-liability matters.
Teams building fund-law retrieval systems index the plain-text document-N.txt payloads alongside metadata.json so that queries about Rule 24f-2 termination procedure, the 1/33rd of 1% fee calculation, and specific historical terminations resolve against authoritative filing text rather than secondary commentary. The EX-5 notice opinions provide grounding for questions about the legality-of-securities language customary in the 24f-2 wind-down context.
The Form 24F-2TM Files Dataset is available through three access patterns: a JSON metadata index, a full archive download, and per-container downloads. Filings cover submissions from February 1994 onward and are packaged as monthly ZIP containers holding the original EDGAR documents (TXT) and metadata (JSON).
Dataset Index JSON API: https://api.sec-api.io/datasets/form-24f2tm-files.json
This endpoint returns dataset-level metadata (name, description, last updated timestamp, earliest sample date, total records, total size, form types covered, container format, and file types) along with the full list of container files and per-container metadata such as size, record count, updated timestamp, and download URL. Use it to discover available containers and to monitor which containers were updated in the most recent refresh, so you only re-download containers that changed. This endpoint does not require an API key.
Example response:
1
{
2
"datasetId": "1f13365b-9ae0-69bb-b9db-611229503cba",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-24f2tm-files.zip",
4
"name": "Form 24F-2TM Files Dataset",
5
"updatedAt": "2026-04-15T12:15:46.478Z",
6
"earliestSampleDate": "1994-02-01",
7
"totalRecords": 1169,
8
"totalSize": 1849668,
9
"formTypes": ["24F-2TM"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["TXT", "JSON"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-24f2tm-files/1994/1994-02.zip",
15
"key": "1994/1994-02.zip",
16
"size": 18432,
17
"records": 7,
18
"updatedAt": "2026-04-15T12:15:46.478Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-24f2tm-files.zip?token=YOUR_API_KEY
Downloads the complete dataset as a single ZIP archive containing every monthly container. Use this for an initial bulk load. This endpoint requires an API key.
Download Single Container: https://api.sec-api.io/datasets/form-24f2tm-files/1994/1994-02.zip?token=YOUR_API_KEY
Downloads one monthly container ZIP. Substitute the year and month in the path to fetch a specific period, or use any downloadUrl returned by the index API. This endpoint requires an API key.
The dataset covers Form 24F-2TM, the terminating variant of the Rule 24f-2 annual-notice family under the Investment Company Act of 1940. Filers used it to give the SEC formal notice that they were ending a declaration of election to register an indefinite number of securities under Rule 24f-2(a)(1) and to settle any final registration fee owed.
Each record is one complete EDGAR submission of a Form 24F-2TM notice, identified by its accession number. On disk it appears as a per-accession folder containing one metadata.json and one or more document-N.txt files — typically the thirteen-item form notice as document-1.txt and an EX-5 legal opinion of counsel as document-2.txt.
Only the three categories of investment company eligible to make a Rule 24f-2 election: open-end management investment companies, face-amount certificate companies, and unit investment trusts. Closed-end funds and business development companies were never eligible and do not appear in the dataset, although the form is frequently signed by a sponsor, depositor, trustee, or principal underwriter acting as agent for the registrant.
Form 24F-2TM filings appeared on EDGAR starting February 1994 as investment company filings were phased onto the system. The form was retired after amendments to Rule 24f-2 reorganized the indefinite-registration regime, and EDGAR no longer accepts new submissions, so the dataset is a closed historical corpus.
Form 24F-2 (no suffix) is the recurring annual notice through which a fund reports prior-year share sales and pays the registration fee while its indefinite-registration election remains in force. Form 24F-2TM is its event-driven terminal counterpart, filed once per registration statement to close the election and reconcile any final fee. A fund that filed 24F-2 annually for a decade typically filed 24F-2TM at most once.
The dataset is delivered as monthly ZIP containers organized by year and month. Inside each container, every accession folder holds a metadata.json index file and one or more document-N.txt plain-text payloads with the EDGAR SGML envelope removed. The on-disk file types are TXT and JSON.
Form N-8F is the Section 8(f) application by which a fund exits 1940 Act registration entirely; Form 24F-2TM only ends one fee-administration election within that status. A fund can file 24F-2TM and continue operating under a different registration approach, and the two filings may appear in proximity during a wind-down without resolving the same legal question.