The Form 24F-2NT Files Dataset is a complete EDGAR corpus of Rule 24f-2 annual notices of securities sold, filed by registered investment companies under the Investment Company Act of 1940. Each record is a single EDGAR submission — an original 24F-2NT notice or a 24F-2NT/A amendment — materialized as an accession-number folder containing the full Rule 24f-2 notice (structured XML for modern filings, plain text or HTML for earlier filings), any attached exhibits such as a legal opinion of counsel, the EDGAR-rendered XHTML view, and a dataset-added metadata.json envelope with entity records and a series-and-class enumeration. The filers are open-end mutual funds, unit investment trusts, face-amount certificate companies, closed-end interval funds that are continuously offered, and insurance company separate accounts that have elected indefinite registration under Rule 24f-2. Coverage begins January 1, 1994, when mandatory electronic filing phased in for investment companies, and runs through the present. The dataset is distributed as monthly ZIP containers exposing TXT, JSON, HTML, PDF, and XML artifacts.
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 Form 24F-2NT and Form 24F-2NT/A submission on EDGAR from January 1, 1994 through the present. Form 24F-2NT is the annual notice that registered investment companies file under Rule 24f-2 of the Investment Company Act of 1940. Rule 24f-2 lets an open-end fund, closed-end interval fund, face-amount certificate company, or unit investment trust register an indefinite number of securities and defer payment of Securities Act of 1933 registration fees until after fiscal year-end. The notice then makes definite, on a look-back basis, the number and aggregate sale price of shares actually sold during the preceding fiscal year, nets that against shares redeemed or repurchased (which generate redemption credits usable to offset the fee), applies the current Section 6(b) statutory fee multiplier, and remits the fee due. Filing the notice completes registration under the Securities Act of 1933 for the shares actually sold during the fiscal year and carries forward any unused redemption credits into future fiscal years.
The 24F-2NT/A variant is an amendment to a previously filed annual notice, used to correct sold-share figures, redemption credits, fee arithmetic, series/class scope, fiscal-year dates, or signature information. Amendments use the same form body and the same XML schema as the original.
The dataset is distributed as monthly ZIP containers. Each container holds one accession-number folder per filing, populated with the period-appropriate document set — structured XML plus an XSL-rendered XHTML view for post-2018 filings, and plain text or HTML (sometimes with separate TXT, HTML, or PDF exhibits) for earlier filings — together with a dataset-added metadata.json index. Image files from the original EDGAR submission are excluded.
One record in the Form 24F-2NT Files Dataset is a single EDGAR submission of a Rule 24f-2 annual notice of securities sold, materialized on disk as an accession-number folder that holds every non-image document from that submission plus a dataset-added metadata index. Each folder corresponds to exactly one accession number and therefore exactly one filing event — either an original 24F-2NT notice or a 24F-2NT/A amendment. The folder name is the 18-digit EDGAR accession number stripped of dashes (for example 000089418925004149).
The record unit is the filing, not the fund series or share class. A single 24F-2NT submission frequently covers one registrant with many series and share classes; those entries appear as repeated structured blocks inside the filing's primary XML rather than as separate dataset records. A registrant that files an original notice and later corrects it produces two distinct records (one 24F-2NT, one 24F-2NT/A) with two distinct accession-number folders.
A modern record follows a uniform three-component layout inside its accession-number folder:
primary_doc.xml — the authoritative EDGAR XML submission carrying the Rule 24f-2 notice itself. This is the machine-readable record of the form and the file from which all disclosure content should be extracted.xsl24F-2NT/primary_doc.xml — an XHTML rendering of the same notice produced by EDGAR's official XSLT stylesheet. Despite the .xml extension, it is an HTML document intended for visual display; every value in it is derived from the raw XML.metadata.json — a dataset-added JSON index over the EDGAR submission envelope: form type, accession number, filing and effectiveness timestamps, period of report, canonical EDGAR URLs, the list of submission documents, the filer/issuer entity blocks, and (critically for this form) a seriesAndClassesContractsInformation array enumerating every fund series and share class reported in the filing with their S-codes, C-codes, tickers, and names.Older records depart from this layout. Pre-XML submissions (roughly 1994 through 2018) ship the notice as plain text or HTML inside the accession folder, sometimes accompanied by separate exhibit files (for example a legal opinion of counsel as TXT, HTML, or PDF). In those records, primary_doc.xml and the XSL rendering are absent and metadata.json remains the normalized envelope pointing at the period-appropriate documents.
Image files from the original EDGAR submission (GIF, JPG, etc.) are excluded from the dataset.
primary_doc.xmlThe raw EDGAR submission uses the namespace http://www.sec.gov/edgar/twentyfourf2filer under schema version X0102. It has two top-level branches: headerData (submission-level envelope) and formData (the substantive Rule 24f-2 disclosures).
headerData carries:
submissionType — 24F-2NT or 24F-2NT/A.filerInfo.liveTestFlag — LIVE in production filings.filerInfo.filer.issuerCredentials.cik — the zero-padded filer CIK.filerInfo.filer.issuerCredentials.ccc — masked to XXXXXXXX in public archives.filerInfo.flags — booleans such as overrideInternetFlag and confirmingCopyFlag.filerInfo.investmentCompanyType — the filer's investment company form family, typically N-1A for open-end mutual funds, N-2 for closed-end funds, N-6 for variable life separate accounts, and related codes.formData.annualFilings.annualFilingInfo[] is the substantive body. It is a repeating block: one annualFilingInfo element per reporting scope the filer chose. A filing that covers all series under one aggregate calculation (with rptIncludeAllSeriesFlag=true) carries a single block; a filing that computes the fee class-by-class or series-by-series — common with multi-series ETF trusts — repeats the block, one per scope. Each block follows the eight numbered items of the paper Form 24F-2 plus a signature:
nameOfIssuer and addressOfIssuer with street1, street2, city, state, country, and zipCode.reportSeriesClass, which is either rptIncludeAllSeriesFlag=true (the notice covers all series of the issuer) or a rptSeriesClassInfo block naming seriesName, seriesId (S-code), and one or more classInfo { className, classId } entries (C-codes).investmentCompActFileNo (the 811- number under the 1940 Act) and one or more securitiesActFileNumbers.securitiesActFileNo.fileNumber entries (002- for pre-1981 registrations, 333- for modern Form N-1A / N-2 / N-14 registration statements).lastDayOfFiscalYear in MM/DD/YYYY form and an optional isThisFormBeingFiledLate boolean.seriesOrClassId (optional, when calculating at class or series level),aggregateSalePriceOfSecuritiesSold — gross dollar amount of securities sold during the fiscal year subject to Rule 24f-2,aggregatePriceOfSecuritiesRedeemedOrRepurchasedInFiscalYear — current-year redemption/repurchase proceeds,aggregatePriceOfSecuritiesRedeemedOrRepurchasedAnyPrior — prior-year redemption credits carried in,totalAvailableRedemptionCredits — sum of the two redemption figures,netSales — sales minus applied credits,redemptionCreditsAvailableForUseInFutureYears — unused carry-forward, rendered as a parenthesised negative (e.g. (3,060,000,000)),multiplierForDeterminingRegistrationFee — the Section 6(b) fee rate in effect for that fiscal year (e.g. 0.0001531),registrationFeeDue — the dollar fee computed from net sales at the multiplier.interestDue, populated only when the notice is filed late; typically omitted.totalOfRegistrationFeePlusAnyInterestDue.explanatoryNotes, free text (often None) used to clarify unusual calculations, recharacterized sales, net-of-exchange adjustments, or amendment rationale.signature (signer's typed name), nameAndTitle (signer and corporate title), and signatureDate.xsl24F-2NT/primary_doc.xmlThis file is an XHTML document emitted by EDGAR's official XSLT transform (stylesheet family TWENTYFOURF2NT_print). It re-renders the same notice as a printable Form 24F-2 page: a "Filer Information" header, one "Annual Filing Information Record" section per annualFilingInfo block, and the identical item 1-8 values arranged in labelled tables and fakeBox divs. Every value mirrors primary_doc.xml exactly; the XSL file carries no disclosure content beyond what the raw XML supplies and is included for visual verification rather than as a data source.
metadata.jsonThe metadata file is the dataset's normalized envelope over the EDGAR submission. Salient fields:
formType (24F-2NT or 24F-2NT/A), accessionNo (in dashed form, e.g. 0000894189-25-004149), description (typically "Form 24F-2NT - Rule 24f-2 notice").filedAt as an ISO 8601 timestamp with timezone, effectivenessDate as YYYY-MM-DD, and periodOfReport set to the last day of the fiscal year the notice covers.linkToTxt, linkToHtml, linkToFilingDetails, and linkToXbrl.documentFormatFiles[]: one entry per document in the EDGAR submission, each with sequence, size, documentUrl, type, and an optional description. Modern filings typically list the XSL-rendered XML, the raw primary_doc.xml, and the complete .txt submission bundle.entities[]: one or more filer/issuer entries with cik, companyName, fileNo (the Securities Act file number), filmNo, fiscalYearEnd (MMDD), stateOfIncorporation, act ("33"), and type (submission form type).seriesAndClassesContractsInformation[]: an array of fund series entries, each containing series (an S-code such as S000061208), name, and classesContracts[] of {ticker, name, classContract} with C-codes such as C000198249. A single filing's entry may span from one share class to several dozen across one or more series.id: a dataset-assigned record identifier.When a submission includes attached exhibits, those files appear in the accession folder as individual TXT, HTML, or PDF documents referenced from metadata.json.documentFormatFiles[]. The most common exhibit is an opinion of counsel attesting that the shares reported as sold were validly issued, fully paid, and non-assessable. Such opinions are routine in pre-XML submissions and in amendments but are not present in every record.
Each accession folder contains:
xsl24F-2NT/primary_doc.xml;metadata.json with envelope metadata, entity records, and the series-and-classes enumeration.headerData.filerInfo.filer.issuerCredentials.ccc are masked to XXXXXXXX in public archives and carry no information.Form 24F-2NT's disclosure anatomy has been relatively stable since its modern adoption in 1997, but several shifts are materially relevant to the dataset:
rptIncludeAllSeriesFlag) or a series-/class-specific scope with seriesId and classId. Filings predating the S/C-code rollout identify series and classes by name only.multiplierForDeterminingRegistrationFee moves year to year with the Section 6(b) fee rate set annually by the SEC. Records from different fiscal years therefore carry different multipliers; the field is a direct record of the rate in effect for that fiscal year.24F-2NT/A amendments follow the same schema as the original and are used to correct any of the items above, most commonly item 5 fee-calculation inputs or item 2 series/class scope.Form 24F-2NT submissions traverse three format eras reflected in the dataset:
.txt document. No structured XML is present in this era.primary_doc.xml under the twentyfourf2filer namespace with X0102-family schema versions, and EDGAR auto-generates the XSL-rendered XHTML view shipped here as xsl24F-2NT/primary_doc.xml. Modern filings in the dataset therefore contain only JSON (the dataset-added metadata) and XML (raw plus XSL-rendered), with TXT/HTML/PDF appearing chiefly in older filings or attached exhibits.rptIncludeAllSeriesFlag=true or by repeating annualFilingInfo blocks. The metadata seriesAndClassesContractsInformation[] array and the XML annualFilingInfo[] array together enumerate the scope of each filing.primary_doc.xml is authoritative. The XSL rendering is a view, not a data source. Downstream extractors should parse the XML directly and use the XSL artifact only for human review. In pre-2018 records, the TXT or HTML document referenced by metadata.json.documentFormatFiles[] is the authoritative content carrier.annualFilingInfo repeats and each block carries its own item 5. A filing-level total requires summing across all blocks rather than treating a single block as the whole notice.24F-2NT/A records share the schema of originals; there is no explicit structural marker of what changed relative to the prior filing beyond any text the filer places in explanatoryNotes. Linking an amendment to its predecessor requires matching on filer CIK, fiscal-year end (item 4), and file numbers (item 3).redemptionCreditsAvailableForUseInFutureYears is encoded as a parenthesised negative string (e.g. (3,060,000,000)), consistent with the paper-form accounting convention. It represents credits not consumed in the current year that may offset sales in future notices.002- prefixes mark pre-1981 Securities Act registrations still in use by long-lived funds; 333- prefixes mark post-1981 registrations. The 811- Investment Company Act file number identifies the registrant. A single notice frequently lists multiple Securities Act file numbers when the registrant has consolidated successor registrations.item4.isThisFormBeingFiledLate is true, item 6 interestDue is populated and item 7 sums the fee and interest. Absence of item 6 implies a timely filing.ccc element inside issuerCredentials is always XXXXXXXX in public archives; it carries no information and should not be interpreted as a data field.The legal filer is the registrant itself: the investment company, trust, or separate account that elected indefinite registration under Rule 24f-2. Advisers, principal underwriters, and administrators often prepare the filing operationally, but they are not the filer of record; the form is signed by an authorized officer of the registrant.
The reporting population is effectively limited to:
Entities that do not file Form 24F-2NT include: closed-end funds that register a definite number of shares on Form N-2 for a discrete offering and pay fees at effectiveness; business development companies not relying on Rule 24f-2; operating-company issuers (governed by Rules 456/457 fee mechanics); and private funds that are not registered investment companies.
Two provisions create the obligation:
The form therefore plays a dual role. For Investment Company Act purposes it is the required annual notice. For Securities Act purposes it completes the registration of the shares actually sold during the fiscal year and remits the fee. It is, in effect, a reconciliation-and-fee-payment filing.
The obligation arises from the registrant's continuing Rule 24f-2 election. It persists each fiscal year in which shares were publicly offered and ends only when the registrant terminates its election or ceases to be a registered investment company offering shares on that basis. A fiscal year with no public offering of the indefinitely registered securities does not trigger a filing.
Because fiscal year ends cluster (December, October, September, June, March), filing volume is concentrated in waves roughly 60-90 days after those dates rather than spread evenly across the calendar.
Form 24F-2NT occupies a narrow role in investment company reporting: the backward-looking, fee-settling notice that closes a fiscal year of indefinite share registration under Rule 24f-2 of the 1940 Act. The most useful comparisons are with its paper predecessor, the registration statements that authorize the shares being reported, the post-effective amendments that keep those registrations current, and the periodic fund reports (N-CEN, N-PORT) commonly grouped with it in the post-reform disclosure stack.
The pre-electronic antecedent of 24F-2NT, serving the same Rule 24f-2 function before the SEC moved to the electronic notice format. Content overlap is high: registrant identification, fiscal period, aggregate sales, and fee computation. The difference is structural: 24F-2 filings are scanned paper or early EDGAR text with inconsistent tagging, while 24F-2NT filings are born-electronic and parseable. Researchers reconstructing long-run sales histories across the 1990s transition need both sides; this dataset covers only 24F-2NT.
Included directly in this dataset. An /A filing corrects or supplements a prior 24F-2NT, typically to restate sales, recompute the fee, or swap in a revised legal opinion. It presupposes an original 24F-2NT for the same registrant and fiscal period and should be joined to it rather than counted as an independent observation. Essential for fee-accuracy work, but should be deduplicated against the underlying notice for registrant-coverage counts.
The registration statements under which the shares reported on 24F-2NT were originally offered: N-1A for open-end funds, N-2 for closed-end funds and BDCs, N-3 for separate-account management companies, and N-4/N-6 for variable annuity and variable life separate accounts. A 24F-2NT is the annual fee-settlement epilogue to registrations filed on these forms. The contrast is sharp: N-series filings are long prospectus-and-SAI documents describing objectives, strategies, risks, fees, and governance; 24F-2NT is a short arithmetic notice plus exhibits. Registration statements describe what can be sold; 24F-2NT reports what actually was sold. The two are typically linked by registration file number, which 24F-2NT records preserve.
The post-effective amendments that keep open-end fund registration statements current between 24F-2NT filings: 485BPOS is immediately effective and used for routine annual prospectus updates; 485APOS is filed subject to SEC review. Both share the annual cadence and presuppose a live indefinite registration, which invites confusion. They differ in direction: 485APOS/BPOS update the descriptive and financial disclosures governing future offers and sales, while 24F-2NT looks backward to fix the shares sold and pay the resulting fee. 485BPOS volume per registrant is also much higher because it covers prospectus updates across multiple share classes and series.
Form N-CEN is the structured annual census that replaced N-SAR. It shares the once-per-fiscal-year cadence and the registered-fund filer population, but its content is orthogonal: an XML-tagged census of fund identity, service providers, share class identifiers, securities lending, and auditor information. N-CEN does not report aggregate dollar sales under Rule 24f-2, and 24F-2NT does not report fund structure or service providers. Complements, not substitutes.
Frequently grouped with N-CEN as a core post-reform fund dataset, which is the main source of confusion with 24F-2NT. The overlap is thin. Form N-PORT reports what the fund owns (positions, valuations, derivatives exposures) at month-end; 24F-2NT reports what the fund sold to investors over a full fiscal year. N-PORT is high-frequency, heavily structured XML holdings data; 24F-2NT is low-frequency, lightly structured sales-and-fee data. Neither substitutes for the other.
The 24F-2NT Files Dataset captures the precise moment an indefinite-share registration is converted into a definite, fee-paid quantity for a completed fiscal year. No other EDGAR filing reports aggregate dollar sales under Rule 24f-2 together with the registration fee calculation and supporting legal opinion. N-series registration statements describe the securities offered; 485APOS and 485BPOS refresh those offering documents; N-CEN inventories fund structure; N-PORT discloses holdings. Only 24F-2NT (and its /A amendments) occupies the Securities Act fee-settlement role, with the paper-era Form 24F-2 as its sole historical analog.
The dataset is read by a compact set of fund-operations, legal, compliance, audit, and research functions that each focus on different fields of the Rule 24f-2 notice: aggregate gross sales, redemption credits, net amount subject to fee, carryforward of unsold securities, fiscal period, and the legal opinion exhibit.
Back-office fund administration and transfer-agent accounting teams reconcile the aggregate sale price on each notice to share-class sales blotters, capstock ledgers, and NSCC settlement records. They roll forward prior-year redemption credits under Rule 24f-2(c) and pull historical notices when onboarding a new series to confirm fiscal year-end, 811- file number, and any unsold-securities carryforward.
In-house fund counsel and outside '40 Act lawyers mine the dataset for drafting precedents: how peers word the Rule 24f-2 election, structure the legal-opinion exhibit, amend prior-year figures via 24F-2NT/A, and handle master-feeder or multi-class registrants in a single notice.
Fund-complex reporting teams use the dataset to confirm every required notice was filed within 90 days of fiscal year-end, that period dates tie to the financial statements, and that gross- and net-sales figures reconcile to N-CEN and the annual report. Historical records help diagnose filing gaps and amendment chains for internal-controls documentation.
Mutual fund operations and treasury groups track the Section 6(b) registration fee actually paid each year against budget and adviser-allocation models. The notice is the only filing that shows the prior-year credit applied, making it the anchor for forecasting the next cycle's fee outlay and planning cash movements for payment.
Fund compliance officers and compliance consultants verify that each registrant has properly elected indefinite registration and filed the annual notice on schedule. They cross-check cover data against effective registration-statement amendments and mine 24F-2NT/A amendments to calibrate compliance-testing programs around common reconciliation errors.
Specialists advising on Section 6(b) fee planning and Rule 24f-2 netting use the dataset as the benchmarking population for their clients. They extract gross sales, credits applied, net amount, and carryforward across complexes and fiscal years to project fees, model redemption-spike scenarios, and flag outlier fee profiles.
Financial-statement auditors of registered funds use prior-period 24F-2NT filings as corroborating evidence when testing capital share activity in the statement of changes in net assets. The aggregate sale price, fiscal period, and carryforward provide an externally filed anchor against transfer-agent records; legal-opinion exhibits support testing of share-issuance authorizations.
Staff responsible for the notice-filing queue use the historical population to flag missing notices from funds known to have elected Rule 24f-2, benchmark against peer patterns, and trace how registrants have corrected net-sales and fee calculations through amendment chains.
Research teams at asset managers use the dataset to quantify annual gross- and net-sales activity at the registrant level on a consistent basis, including small complexes not covered by commercial flow vendors. It validates reported flow estimates, surfaces seasoning patterns in new launches, and identifies funds with persistent carryforwards that signal capacity underutilization.
Data engineering teams at market-data and fintech vendors parse aggregate sale price, redemption credits, net amount, fiscal period, and CIK/811-/333- identifiers into structured tables, then join to N-CEN, N-SAR, and N-1A series-and-class data to build long-run panels on registration-fee expense and issuance activity dating back to 1994.
Teams building retrieval and extraction systems for '40 Act filings use the dataset as a narrowly scoped training and evaluation corpus. The constrained numeric fields combined with free-text legal-opinion exhibits support both tabular extraction and legal-text classification within one corpus.
The Form 24F-2NT Files Dataset supports a narrow but well-defined set of workflows built around annual Rule 24f-2 fee settlement, fund share-issuance tracking, and registration-fee analytics.
Parse aggregateSalePriceOfSecuritiesSold, totalAvailableRedemptionCredits, netSales, multiplierForDeterminingRegistrationFee, and registrationFeeDue out of each annualFilingInfo block and join on filer CIK plus lastDayOfFiscalYear. The result is a registrant-level time series of gross sales, applied credits, and Section 6(b) fees usable for budgeting, adviser-allocation models, and multi-year fee-trend benchmarking against peer complexes.
Auditors and fund accountants pull the prior-year 24F-2NT for a given fund and match aggregateSalePriceOfSecuritiesSold and aggregatePriceOfSecuritiesRedeemedOrRepurchasedInFiscalYear against internal capstock ledgers, NSCC settlement totals, and the statement of changes in net assets. The notice serves as the externally filed anchor for capital share activity testing, with the attached opinion of counsel corroborating share-issuance authorization.
Extract redemptionCreditsAvailableForUseInFutureYears (the parenthesised negative) from each filing and chain successive notices by CIK to build a rolling carryforward ledger. This identifies registrants with persistent unused credits (a capacity-underutilization signal), projects the credit balance available to offset next year's sales, and flags arithmetic breaks between one year's carryforward and the next year's prior-year credit input.
Filter on formType = 24F-2NT/A and match each amendment to its original via filer CIK, item 3 file numbers, and lastDayOfFiscalYear. Diffing netSales, registrationFeeDue, and explanatoryNotes between original and amendment surfaces common restatement patterns (misclassified exchanges, recharacterized sales, scope corrections) that compliance teams fold into internal-controls testing and error-calibration programs.
Use periodOfReport (fiscal year-end) and filedAt to compute filing lag per registrant and flag notices filed more than 90 days after fiscal year-end or missing entirely for CIKs that filed in prior years. Combined with isThisFormBeingFiledLate and item 6 interestDue, this produces a late-filing and gap report for SEC staff reviewers, fund compliance officers, and fund-complex reporting teams.
Flatten metadata.json.seriesAndClassesContractsInformation[] into a (CIK, S-code, C-code, ticker, fiscal year) table to see which series and classes were in scope for each annual notice. Joined to N-CEN and N-1A series data, this supports long-run panels of share-class issuance, identifies new-launch seasoning patterns, and resolves whether a filing uses an all-series aggregate (rptIncludeAllSeriesFlag=true) or a class-level calculation across repeated annualFilingInfo blocks.
Fund counsel query the corpus of explanatoryNotes text and attached opinion-of-counsel exhibits to find peer language for unusual calculations (net-of-exchange adjustments, master-feeder structures, multi-class scope), amendment rationales, and validly-issued/fully-paid/non-assessable opinion wording. The structured exhibit list in documentFormatFiles[] makes retrieving opinions across thousands of filings straightforward.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-24f2nt-files.json
This endpoint returns the dataset metadata, including the name, description, last updated timestamp, earliest sample date, total records and total size, form types covered (24F-2NT and 24F-2NT/A), container format (ZIP), and file types included (TXT, JSON, HTML, PDF, XML). It also returns the download URL for the full dataset archive and the list of individual container files, each with its own size, record count, last updated timestamp, and download URL. You can poll this endpoint to monitor which containers have changed in the most recent refresh run and selectively download only the updated containers on a day-by-day basis.
This endpoint does not require an API key.
Example response:
1
{
2
"datasetId": "1f13365b-9ade-61e3-9876-789d9af1f8cb",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-24f2nt-files.zip",
4
"name": "Form 24F-2NT Files Dataset",
5
"updatedAt": "2026-04-22T02:57:31.195Z",
6
"earliestSampleDate": "1994-01-01",
7
"totalRecords": 246102,
8
"totalSize": 738451063,
9
"formTypes": ["24F-2NT", "24F-2NT/A"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["TXT", "JSON", "HTML", "PDF", "XML"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-24f2nt-files/2026/2026-04.zip",
15
"key": "2026/2026-04.zip",
16
"size": 13818783,
17
"records": 154,
18
"updatedAt": "2026-04-22T02:57:31.195Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-24f2nt-files.zip?token=YOUR_API_KEY
Downloads the complete dataset as a single ZIP archive containing all Form 24F-2NT and 24F-2NT/A filings from January 1994 to present. This endpoint requires an API key.
Download Single Container: https://api.sec-api.io/datasets/form-24f2nt-files/2026/2026-04.zip?token=YOUR_API_KEY
Downloads one individual monthly container instead of the full archive, which is useful for incremental syncing after consulting the dataset index. This endpoint requires an API key.
The dataset covers Form 24F-2NT, the annual Rule 24f-2 notice of securities sold that registered investment companies file under the Investment Company Act of 1940, along with its amendment variant 24F-2NT/A. No other form types are included.
One record is a single EDGAR submission of a Form 24F-2NT or Form 24F-2NT/A filing, materialized as an accession-number folder containing the notice itself (as structured XML for post-2018 filings or plain text/HTML for earlier filings), any attached exhibits, the EDGAR-rendered XHTML view where applicable, and a dataset-added metadata.json envelope. The record unit is the filing, not the fund series or share class; a single notice frequently covers many series and classes.
Form 24F-2NT is filed by the registered investment company, trust, or separate account that has elected indefinite registration under Rule 24f-2. The reporting population includes open-end mutual funds (Form N-1A), unit investment trusts, face-amount certificate companies, continuously offered closed-end funds such as interval funds, and insurance company separate accounts issuing variable annuity or variable life contracts on a continuous basis.
Rule 24f-2 requires the notice to be filed no later than 90 calendar days after the end of each fiscal year in which the registrant publicly offered indefinitely registered securities. The Section 6(b) registration fee accompanies the notice; late filings accrue interest, which is reported in item 6 of the form.
Coverage begins January 1, 1994, reflecting the phase-in of mandatory electronic filing for investment companies, and runs through the most recent monthly container. Records from 1994 through roughly 1997 reflect the pre-modern notice format and are predominantly plain-text submissions; filings from 2018 onward use the structured XML schema under the twentyfourf2filer namespace.
The dataset is distributed as monthly ZIP containers. Inside each container, per-filing accession folders contain XML (both raw primary_doc.xml and the EDGAR XSL-rendered XHTML view), JSON (the dataset-added metadata.json), and, for older filings or attached exhibits, TXT, HTML, and PDF documents. Image files from the original EDGAR submission are excluded.
N-PORT reports what a fund owns at month-end (positions, valuations, derivatives exposures); N-CEN is an annual structured census of fund identity, service providers, share-class identifiers, and auditor information. Form 24F-2NT reports neither holdings nor fund structure — it reports what the fund actually sold to investors over a full fiscal year, together with the Rule 24f-2 fee calculation and supporting legal opinion. The three datasets are complements, not substitutes.