Form 40-8B25 Files Dataset

The Form 40-8B25 Files Dataset is a per-accession collection of EDGAR submissions accepted under form type 40-8B25 — applications by registered investment companies, under Rule 8b-25(a) of the Investment Company Act of 1940, for additional time to file a specific report or document required under that Act. Each record corresponds to one accepted accession and bundles together a metadata.json describing the EDGAR header and document inventory with the original Form 40-8B25 application document(s). The legal filer is the registrant — open-end and closed-end management investment companies, business development companies, unit investment trusts, and face-amount certificate companies — applying before an impending 1940 Act filing deadline that cannot be met without unreasonable effort or expense. Coverage begins on October 1, 2004 and runs to the present, organized as monthly ZIP containers in which each accession expands into its own folder of HTML, JSON, and TXT files.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset collects every EDGAR submission accepted under the unamended 40-8B25 form code, which is the Investment Company Act of 1940 counterpart to the Exchange Act notification on Form 12b-25. Form 40-8B25 is the application prescribed by Rule 8b-25 (17 CFR 270.8b-25), the exclusive 1940 Act mechanism by which a registered investment company can request additional time to file information, documents, or reports for which no other extension procedure exists. The application must (i) identify the specific filing for which the extension is sought, (ii) explain in narrative form why timely filing is impracticable or impossible, and (iii) propose an extended filing date that, by rule, is no more than 60 days after the original due date.

The form is short, narrative, and self-contained. It is not a periodic report, it carries no financial statements, it is not normally amended on a recurring schedule, and it is never subject to XBRL or inline XBRL tagging. In practice the filings most often seek extensions for Form N-CEN (the annual census report for registered funds) or Form N-CSR (certified shareholder reports), and less commonly for other 1940 Act periodic disclosures. The universe of filers is correspondingly narrow — registered investment companies including registered open-end funds, closed-end funds, business development companies, and unit investment trusts — and the form is genuinely rare relative to mainstream periodic-report form types.

The dataset is delivered as monthly ZIP containers. Each container expands into one folder per accession number, holding the per-accession metadata.json and the original EDGAR submission documents. The file types found inside the containers are HTML, JSON, and TXT. Amended applications filed under form type 40-8B25/A are accepted by EDGAR as a separate form code and are not part of this dataset, which is keyed on the unamended 40-8B25 form code only.

Content Structure of a Single Record

What one record represents

A single record corresponds to one EDGAR submission accepted under form type 40-8B25 — that is, one application by a registered investment company (or a subsidiary thereof) requesting additional time to file a document, report, or piece of information with the Commission under Rule 8b-25(a). The unit of observation is the accession number: every accepted accession produces exactly one record, regardless of how many filer entities, attached documents, or pages are involved. Each record is materialized as an accession-keyed folder inside the dataset's monthly ZIP containers and bundles together a metadata.json describing the submission as a whole and the actual filed document(s) that constitute the application.

Folder layout of a single record

Each record is a small directory tree rooted at the 18-digit zero-padded EDGAR accession number with all dashes removed (for example 000121390025037437 for accession 0001213900-25-037437). The folder always contains exactly one metadata.json plus one or more documents that were part of the original EDGAR submission. The primary document is the Form 40-8B25 application itself; filer-chosen filenames conventionally embed 40-8b25 as a substring (for example ea022895402_40-8b25.htm). When EDGAR's auto-generated "complete submission text file" is preserved as a separate sibling, it appears under the dashed-accession filename pattern <dashed-accession>.txt (for example 0001213900-25-037437.txt).

Image attachments that may have been part of the original EDGAR submission (logos, scanned signatures, ornamental graphics) are excluded from the dataset; everything else from the accepted accession is retained. The file-types found in the dataset are HTML, JSON, and TXT.

The metadata.json layer

metadata.json is a flat JSON object that captures the EDGAR header information and document inventory for the accession. The fields it carries are:

• formType — fixed at "40-8B25" for every record in the dataset.
• accessionNo — the dashed EDGAR accession identifier (for example "0001213900-25-037437").
• id — a 32-character hexadecimal record identifier internal to the dataset.
• filedAt — ISO 8601 timestamp with timezone offset recording the EDGAR acceptance time (for example "2025-04-30T14:14:25-04:00").
• description — short human-readable description of the form's purpose ("Form 40-8B25 - Investment company request for extension of time to file").
• linkToFilingDetails — canonical sec.gov URL of the primary application document.
• linkToTxt — sec.gov URL of the EDGAR complete submission text file for the accession.
• linkToHtml — sec.gov URL of the EDGAR -index.htm filing index page for the accession.
• linkToXbrl — empty string; Form 40-8B25 carries no XBRL.
• documentFormatFiles[] — array describing every document attached to the submission. Each element carries sequence (string-encoded integer such as "1", or a single-space " " for the auto-generated complete-submission wrapper file), size (string-encoded byte count), documentUrl, free-text description (for example "40-8B25" or "Complete submission text file"), and EDGAR type code (for example "40-8B25", or a single space for the wrapper file).
• entities[] — array of filer entities. Each element carries companyName (registrant name with a parenthesized role suffix such as (Filer)), cik, fileNo (Investment Company Act registration numbers in the 811- series, for example "811-23806"), filmNo (EDGAR film number), type (form-context code, typically "40-8B25"), act (statutory act code, "40" for the Investment Company Act of 1940), stateOfIncorporation (two-letter US state or country code), and fiscalYearEnd (MMDD string, for example "1231").
• seriesAndClassesContractsInformation[] — an array; usually empty because the form does not require fund-series or class enumeration.
• dataFiles[] — an array; uniformly empty because the submission carries no XBRL or other structured-data attachments.

The Form 40-8B25 document itself

The primary .htm document opens with EDGAR's SGML wrapper before the HTML body begins. The wrapper consists of a <DOCUMENT> element with five header tags — <TYPE>40-8B25, <SEQUENCE>1, <FILENAME> (the filer-chosen filename), <DESCRIPTION>40-8B25, and <TEXT> — followed by the literal HTML and a closing </TEXT></DOCUMENT>. The header tags are SGML-style and not closed; the HTML body sits inside the <TEXT> block. Inside the <TEXT> block the application follows the fixed three-part scaffold prescribed by the form:

1. Cover block. Centered headings identify "UNITED STATES SECURITIES AND EXCHANGE COMMISSION", "Washington, D.C. 20549", "Form 40-8B25", and "APPLICATION FOR EXTENSION OF TIME". Below these headings the registrant's 1940 Act file number (for example 811-23806) appears under the caption "Investment Company Act File Number", followed by the registrant's exact legal name and the parenthetical "(exact name of registrant as specified in its charter)". A two-column table then presents the state or jurisdiction of organization alongside the IRS Employer Identification Number. A second table gives the principal-office address (street, city, state) alongside the ZIP code captioned "(Address of principal executive offices) / (Zip Code)". The cover block closes with the registrant's underlined telephone number labeled "(Registrant's telephone number)". Page 1 of 3 closes with an EDGAR-style page footer.

2. Part I — Narrative application. Part I opens with a centered "PART I" heading and an introductory paragraph that recites the registrant's name, declares that the application is being filed "pursuant to Rule 8b-25 under the Investment Company Act of 1940, as amended", names the specific document for which additional filing time is being requested (typically Form N-CEN, Form N-CSR, or another 1940 Act periodic report), names the period it covers, names the proposed extended filing date, and affirms that the proposed date is "not more than 60 days" after the original due date. A "Narrative" sub-heading then introduces the substantive explanation, which is rendered as a sequence of justified paragraphs. Typical content includes the statutory or rule-based filing deadline being missed (for Form N-CEN, Rule 30a-1's 75-day window); the registrant's most recent fiscal year-end; cross-references to any prior Form 12b-25 notification or earlier Rule 8b-25 application bearing on the same delayed filing; the substantive reasons the registrant cannot meet the deadline (commonly cited reasons include ongoing accounting analysis, late receipt of audited financial statements, valuation or amortization-methodology issues, sub-adviser transitions, or administrative dislocations); and a closing assertion that the requested relief is consistent with the policies and purposes of the 1940 Act and with investor protection.

3. Part II — Other information and signatures. Part II opens with centered "PART II" and "OTHER INFORMATION" headings and the boilerplate "Name and telephone number of person to contact with respect to this notification" caption, even though the contact block typically supplies name, title, employer, mailing address, and email rather than a phone number. The block lists the contact officer (commonly the registrant's President, Principal Executive Officer, Treasurer, or Principal Financial Officer), employer (often the investment adviser or fund administrator rather than the registrant itself), street address, city/state/ZIP, and email address. The document closes with a centered "SIGNATURES" heading, the standard attestation paragraph ("The registrant has duly caused this application to be signed on its behalf by the undersigned, thereunto duly authorized."), and a signature table containing By: followed by an /s/ typed-string electronic signature, the printed signatory name, the signatory's officer title, and the filing date.

The HTML is paginated using EDGAR-style <!-- Field: Page; Sequence: N --> and <!-- Field: /Page --> comment markers wrapping each page footer, with "N/3" page numbers rendered through <!-- Field: Sequence; Type: Arabic; Name: PageNo --> markers inside a bottom-bordered <DIV>. Styling is plain inline CSS, almost universally font: 10pt Times New Roman, Times, Serif. Typical documents run roughly 10-20 KB across three printed pages because the form is a short application rather than a substantive disclosure document.

Included content

Each record contains the full metadata.json for the accession, the primary Form 40-8B25 application document as filed (HTML inside the SGML <DOCUMENT> envelope), and any companion documents that were part of the same submission — most commonly the EDGAR-generated complete submission text file. All filer-entity metadata, document-inventory metadata, file numbers, CIKs, statutory-act codes, jurisdictions, and EDGAR header attributes are preserved in metadata.json.

Excluded or separate content

Image files that may have been part of the original EDGAR submission (scanned signature blocks, embedded logos, ornamental graphics) are excluded from the dataset. Form 40-8B25 carries no XBRL, no inline XBRL, no structured-data exhibits, and no series/class enumeration, so the corresponding linkToXbrl field, dataFiles[] array, and seriesAndClassesContractsInformation[] array are present but uniformly empty. The dataset does not redistribute the SEC's broader index files, EDGAR full-text search artifacts, or company submission histories; only the per-accession contents are packaged into the monthly ZIP containers.

Interpretation and extraction notes

• Identifying the underlying delayed filing. The form identifies the delayed document narratively rather than through a structured field. Downstream extraction of the underlying form name (Form N-CEN, Form N-CSR, Form N-SAR, etc.), the period it covers, and the proposed extended date all require parsing of the Part I body text rather than a metadata lookup.
• Cross-references to Form 12b-25 and prior Rule 8b-25 applications. Part I narratives commonly reference earlier Form 12b-25 notifications (filed under the Exchange Act) and earlier Rule 8b-25 applications addressing the same delayed filing. Recovering the chain of related submissions requires text parsing of those references; there is no structured priorAccession field in metadata.json.
• Repeat applications. A single registrant can file multiple Form 40-8B25 applications across consecutive periods, and occasionally files a follow-on application after an earlier extension proves insufficient. Each such application is its own accession and therefore its own record; the connection between them is visible only in the Part I narrative.
• Multi-entity filings. The entities[] array can contain multiple filer entities when a fund family files a single application covering several registered funds. Each entity carries its own CIK, file number, jurisdiction, fiscal year-end, and act code; the parenthesized role suffix in companyName distinguishes the primary filer from co-registrants or subsidiaries.
• Signature semantics. Signatures appear as /s/-prefixed typed strings rather than as scanned images, and are wrapped in the signature <TABLE> rather than emitted as free-floating paragraphs. The signatory's officer title is the most reliable indicator of which officer attests to the application.
• Document-inventory layout. documentFormatFiles[] always includes one entry per attached document. When the EDGAR-generated complete submission text file is present it appears as an additional entry recognizable by its single-space sequence and type values, its description of "Complete submission text file", and its documentUrl matching linkToTxt.
• Page-footer parsing. Body extractors that strip HTML should be aware of the EDGAR <!-- Field: ... --> comment markers that wrap page-break <DIV>s; these are pagination artifacts, not document content, and removing them yields cleaner narrative text. The "N/3" page footers are likewise pagination scaffolding rather than substantive content.
• Format stability. EDGAR coverage of Form 40-8B25 begins in October 2004, by which point HTML had already become the standard document format; the dataset does not contain the early-EDGAR ASCII-art era. Throughout the coverage window the primary document is delivered as HTML inside the SGML <DOCUMENT> wrapper. Older records tend to use simpler HTML with minimal styling; more recent records use inline-CSS-styled HTML with explicit page-break comments and structured cover-page tables. The substantive three-part scaffold (cover block, Part I narrative, Part II other information and signatures) and the required cover-page identifying elements (registrant name, 1940 Act file number, jurisdiction, EIN, principal-office address, ZIP, telephone) have been stable across the coverage window. What has shifted is the population of underlying delayed filings: extension targets pre-2018 are dominated by Form N-SAR and Form N-CSR, while Form N-CEN — which replaced Form N-SAR in 2018 — only appears as an extension target after that date. This evolution is visible in the Part I body text, not in the form's structure.

Who Files Form 40-8B25 and When

Who files or discloses the record

Form 40-8B25 is filed by registrants subject to the reporting regime of the Investment Company Act of 1940, applying to the Commission for additional time to file an information document, periodic report, or other report required under that Act. The eligible filer population includes:

• Open-end management investment companies (mutual funds), including individual series of registered fund trusts.
• Closed-end management investment companies, including listed closed-end funds and interval funds.
• Unit investment trusts (UITs) registered under the 1940 Act.
• Business development companies (BDCs), for reports required of them under the 1940 Act (not for their Exchange Act periodic reports).
• Face-amount certificate companies registered under the 1940 Act.

The legal filer is the registrant itself. Where a fund complex contains multiple separately registered entities, each affected registrant files its own Form 40-8B25 even when the operational reason for delay is shared. Service providers (administrators, auditors, sub-advisers) whose delays may be the cause are described in the filing's narrative but are not the filers.

The form is not used by ordinary operating-company Exchange Act registrants, by foreign private issuers, or by issuers reporting only under Sections 13(a) or 15(d) of the Securities Exchange Act of 1934 in respect of non-fund securities.

When the record is created or required

The trigger is an impending statutory deadline for an underlying 1940 Act filing that the registrant has determined cannot be met within the prescribed time without unreasonable effort or expense. Underlying delayed filings commonly include:

• Form N-CEN — annual report of registered investment companies (replaced Form N-SAR effective June 1, 2018).
• Form N-CSR — certified semi-annual shareholder reports filed under Section 30(e) and Rule 30e-1.
• Form N-SAR — the predecessor semi-annual report, relevant for earlier records in the dataset.
• Other 1940 Act filings required under Section 8(b), Section 30, or rules thereunder.

Form 40-8B25 must be filed on or before the original due date of the underlying report. It is a pre-deadline application, not a post-hoc cure; once the deadline passes without an approved extension, the registrant becomes delinquent and Rule 8b-25 is no longer the available mechanism.

The maximum extension obtainable is 60 days from the original deadline. The extension is not self-effectuating: the Commission must grant the application before the registrant may rely on it. Additional time beyond 60 days is not available under Rule 8b-25(a) and would require separate procedural relief.

The dataset is purely event-driven, with no periodic cadence. A record exists only when a specific registrant has applied to extend a specific 1940 Act filing deadline.

Regulatory framework

Form 40-8B25 implements Rule 8b-25(a) under the Investment Company Act of 1940 (17 CFR 270.8b-25). The rule provides that if any information, document, or report required to be filed under the 1940 Act and the rules thereunder cannot be filed within the prescribed time without unreasonable effort or expense, the registrant may apply to the Commission for an extension of up to 60 days, upon a showing of good cause. The application must identify the specific report, state in detail the reasons timely filing is impracticable, and propose a definite extended filing date within the 60-day cap.

Important distinctions

• Form 40-8B25 vs. Form 12b-25. Form 12b-25 (under Exchange Act Rule 12b-25, 17 CFR 240.12b-25) is a self-effectuating notification of late filing for Exchange Act periodic reports, granting an automatic 5 calendar days for Form 10-Q and 15 calendar days for Form 10-K. Form 40-8B25 is an application requiring Commission approval for 1940 Act filings and offers up to 60 days. A BDC may use Form 12b-25 for its Exchange Act 10-K or 10-Q and Form 40-8B25 for its 1940 Act reports.
• Application, not notification. The extension is not in effect until granted; submission alone does not authorize late filing.
• One report per application. A single Form 40-8B25 generally addresses one identified report; multiple distinct delayed reports typically require separate applications.
• Amendments. A previously filed application may be amended (40-8B25/A) to update facts or revise the proposed filing date within the 60-day cap; an amendment continues the original application rather than starting a new one.
• Not a registration-statement extension. Form 40-8B25 covers filing deadlines for required reports and documents, not the effectiveness of registration statements or post-effective amendments, which follow separate procedures.

How This Dataset Differs From Similar Datasets or Filings

Form 40-8B25 sits at the intersection of two SEC reporting traditions: late-filing relief and Investment Company Act applications. The most useful comparisons are with the Exchange Act late-filing notification regime (Form 12b-25 and its NT variants), the underlying 1940 Act periodic reports whose deadlines 40-8B25 seeks to extend (N-CEN, N-CSR, and historically N-SAR), and other 1940 Act applications such as 40-APP.

Form 12b-25 and the NT 10-K / NT 10-Q family

The closest functional analog. Both regimes address a registrant that cannot file a periodic report on time, but they differ structurally:

• Statutory authority and posture. 12b-25 operates under Exchange Act Rule 12b-25 as a notification: if the rule's conditions are met, an extension is self-effectuating (5 calendar days for quarterly reports, 15 calendar days for annual reports) and requires no SEC action. 40-8B25 operates under Investment Company Act Rule 8b-25 as an application: the SEC must affirmatively grant the request, and the extension can run up to 60 days.
• Filer population. NT filings are dominated by Exchange Act operating-company registrants. 40-8B25 is restricted to registered investment companies (mutual funds, closed-end funds, BDCs, UITs).
• Underlying reports covered. NT 10-K, NT 10-Q, NT 20-F, and NT 10-D cover Exchange Act periodic reports. 40-8B25 covers 1940 Act reports such as N-CEN, N-CSR, and (historically) N-SAR, which are outside Rule 12b-25's scope.

A researcher using NT data to study late-filing behavior will systematically miss the fund-industry population captured by 40-8B25, and vice versa.

Forms N-CEN, N-CSR, and N-SAR (the underlying delayed reports)

These are not overlapping disclosure types but the substantive reports whose deadlines 40-8B25 applications seek to extend:

• N-CEN is the annual census report for registered investment companies, in effect since 2018.
• N-CSR is the certified semiannual shareholder report for registered management investment companies.
• N-SAR was the pre-2018 semi-annual report, replaced by N-CEN. Earlier portions of the 40-8B25 dataset reference N-SAR as the delayed filing; later portions reference N-CEN. The 40-8B25 form itself did not change.

The relationship is one of dependency, not content overlap. N-CEN, N-CSR, and N-SAR contain structured fund-level data; a 40-8B25 filing contains only the explanation for delay and the proposed revised filing date. Researchers studying late or amended fund reports can cross-reference 40-8B25 to identify which delays were formally sanctioned by the SEC rather than simply filed late.

Form 40-APP

Both 40-APP and 40-8B25 are Investment Company Act applications submitted by registered funds, which makes them easy to confuse. Their statutory purposes diverge:

• Subject matter. 40-APP seeks substantive exemptive or interpretive orders under various sections of the 1940 Act (affiliated transactions, fund-of-funds structures, ETF operation, etc.). 40-8B25 seeks only a procedural extension of time for a specific report.
• Process and outcome. 40-APP filings are extended legal proceedings, frequently amended (40-APP/A) and culminating in an exemptive order with ongoing legal effect. 40-8B25 filings are short, time-bound requests yielding a one-time deadline extension of up to 60 days.

Same statutory regime, same filer population, fundamentally different statutory purpose.

Boundary summary

Form 40-8B25 is uniquely identified by the conjunction of three features:

1. Filer scope limited to registered investment companies (excluding the operating-company NT universe).
2. Procedural purpose limited to extending a filing deadline (excluding 40-APP and other substantive 1940 Act applications).
3. Application posture requiring SEC approval (distinguishing it from the self-effectuating 12b-25 notification regime).

The dataset is therefore the unique source for SEC-granted late-filing relief in the fund industry. It complements, but does not substitute for, the NT family (different statutory regime), the N-CEN / N-CSR / N-SAR datasets (substantive content rather than procedural extension), and 40-APP filings (exemptive relief rather than time relief).

Who Uses This Dataset

The Form 40-8B25 Files Dataset is used by a defined set of fund-industry professionals who each read a different slice of the record: metadata.json fields (accessionNo, filedAt, entities, documentFormatFiles), the Part I narrative explaining why timely filing is impracticable, the proposed extended filing date, and the signature block.

Fund compliance officers and CCOs

Compliance teams at fund complexes track every 8b-25(a) application filed by their own funds and peers. They reconcile entities and filedAt against internal compliance calendars, read Part I to confirm the stated reason matches the underlying operational issue, and store accessionNo references in audit trails supporting periodic certifications. Prior filings serve as drafting precedent for tone and specificity.

Fund administrators

In-house and third-party administrators assemble the delayed filings. They mine Part I narratives for recurring causes (sub-adviser data delays, valuation issues, recordkeeping conversions, audit timing, custody breaks) to calibrate service levels. The proposed extended filing date sets the operational target; the signature block identifies which officer (treasurer, secretary, or principal financial officer) executed the application.

Fund auditors and fund-accounting teams

External auditors and fund accountants use Part I to identify when audit timing or close issues drive extensions, often on N-CSR or financial-statement exhibits. They benchmark how peers describe audit-related delays and use clustering of filedAt around fiscal year-ends to anticipate workflow stress.

Investment company counsel

Lawyers advising registered funds use the dataset as a precedent library. They review Part I phrasings of "impracticable," typical proposed extended filing date ranges relative to the original deadline, and signature-block authority levels to draft and sign off on new applications.

Regulatory operations and EDGAR filing teams

Filing operations groups inside advisers use accessionNo, filedAt, and documentFormatFiles to confirm EDGAR acceptance, populate filing-status dashboards, and surface 8B25 events to compliance and legal stakeholders for year-over-year operational metrics.

Fund-board secretaries

Board secretaries compile 8B25 filings into board books, summarize the Part I rationale for trustees, attach documentFormatFiles as exhibits, and use the proposed extended filing date to schedule follow-up updates. Historical entities records support recurrence reporting to independent trustees.

Transfer agents, custodians, and other service providers

Service providers monitor Part I for references implicating their performance, and track entities across client funds to inform service-quality reviews, contract negotiations, and operational risk reporting.

Outsourced compliance providers and fund-services consultants

Consultants advising smaller complexes use patterns across Part I narratives and proposed extended filing dates to advise on when to seek extensions, how to frame the cause, and how to set realistic targets. Outputs include filing-calendar reviews and post-event remediation plans.

Academic researchers on disclosure timeliness

Researchers in accounting, finance, and law link entities and filedAt to other filings by the same registrant to study which documents are most often delayed, how stated reasons cluster, and whether late filing predicts restatements, liquidations, or adviser changes. Part I is the primary text for content analysis; the proposed extended filing date supports duration models.

Operational-risk analysts and platform gatekeepers

Risk analysts, fund raters, and institutional allocators treat repeat 8B25 filings as operational stress signals. They count accessionNo occurrences per entities record over time and read Part I language for severity, feeding operational due-diligence questionnaires and watchlists used by advisory and retirement platforms.

Form 40-8B25 sits at the intersection of compliance calendars, fund accounting, audit timing, board oversight, and service-provider performance. Producers of the filing (compliance, counsel, administration, accounting, board secretarial) rely on metadata.json identifiers, Part I narratives, the proposed extended filing date, and signature-block details to draft, file, and document each application. Reactors (service providers, consultants, researchers, and operational-risk analysts) use the same fields to benchmark, study, and monitor late-filing behavior across the registered fund population.

Specific Use Cases

The following workflows show how fund-industry users, researchers, and risk teams put Form 40-8B25 records to work. Each draws on specific fields in metadata.json and the three-part scaffold of the application document itself.

Building a peer-precedent library for drafting new applications

Starting input: a fund complex preparing a new 8b-25(a) application for a delayed Form N-CEN or N-CSR. The user filters the dataset by documentFormatFiles[].type = "40-8B25" and the entities[].fileNo prefix 811-, extracts Part I narratives, and clusters them by the cited reason for delay (audit timing, sub-adviser transition, valuation or amortization issues, custody break). The output is a curated set of phrasings of "impracticable," typical gaps between the original due date and the proposed extended filing date, and signature-block officer titles, used directly as drafting precedent by counsel and the fund administrator.

Reconciling SEC-sanctioned late filings against an N-CEN/N-CSR tracker

Starting input: an internal list of late or amended N-CEN and N-CSR filings observed for a watchlist of fund families. The user joins each registrant's CIK and 1940 Act file number from entities[] to that watchlist, parses Part I to identify which underlying form and reporting period each application targets, and pulls the proposed extended filing date out of the introductory paragraph. The output is a reconciled table separating filings that ran late under a granted Rule 8b-25 extension from those that simply missed the deadline without one — a key distinction for compliance scoring and operational due diligence.

Detecting repeat-extension and follow-on-application clusters

Starting input: the full per-month dataset over a multi-year window. The user groups records by entities[].cik, sorts by filedAt, and text-mines Part I for cross-references to prior Form 12b-25 notifications or earlier Rule 8b-25 applications addressing the same delayed filing. The output is a registrant-level timeline of repeat or follow-on applications, used by fund raters and platform gatekeepers as an operational-stress signal feeding due-diligence questionnaires and platform watchlists.

Calibrating workflow stress around fiscal year-ends

Starting input: filedAt timestamps and entities[].fiscalYearEnd (MMDD) for every record. The user computes the distribution of acceptance dates relative to each registrant's fiscal year-end and the statutory deadline (for example, Rule 30a-1's 75-day N-CEN window), then overlays Part I cause-of-delay tags. The output is a seasonal pattern of audit-related and accounting-close delays by fund type (open-end, closed-end, BDC, UIT) that fund auditors and fund-accounting teams use to anticipate staffing pressure and that consultants use to advise smaller complexes on filing-calendar planning.

Compiling board-book exhibits and trustee summaries

Starting input: an upcoming board meeting for a registrant identified by CIK. The board secretary pulls every record where the registrant appears in entities[], attaches the primary 40-8B25 HTML from documentFormatFiles[] as an exhibit, summarizes the Part I rationale and proposed extended filing date for trustees, and reads the signature block to confirm which officer (President, Treasurer, Principal Financial Officer) executed each application. The output is a board package documenting recurrence, rationale, and officer accountability for independent trustees.

Academic content analysis of stated reasons for delay

Starting input: the cleaned Part I narrative text from every record over the coverage window (October 2004 onward), with EDGAR <!-- Field: Page; ... --> pagination comments stripped. The user codes each narrative for cause categories (audit delay, sub-adviser transition, valuation methodology, administrative dislocation), links entities[].cik to subsequent restatements, fund liquidations, or adviser changes via other SEC datasets, and uses the proposed extended filing date to fit duration models. The output is an empirical study of whether stated reasons predict downstream events and how the population of underlying delayed filings shifted from N-SAR to N-CEN after 2018.

Dataset Access

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

This endpoint returns dataset-level metadata together with the list of available container files. The response includes the dataset name, description, last updated timestamp, earliest sample date, total record and size counters, the form types covered, the container format, the file types contained inside each container, the download URL for the full dataset archive, and a containers array. Each container entry exposes its key, size, record count, last updated timestamp, and direct download URL, making it suitable for monitoring which monthly containers have been refreshed in the most recent run and selecting only the changed containers for incremental download.

This endpoint does not require an API key.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-6a00-bd2b-97fc627eb829",
        

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

          4
            "name": "Form 40-8B25 Files Dataset",
        

          5
            "updatedAt": "2026-04-15T18:20:05.742Z",
        

          6
            "earliestSampleDate": "2004-10-01",
        

          7
            "totalRecords": 141,
        

          8
            "totalSize": 508026,
        

          9
            "formTypes": ["40-8B25"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

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

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

          16
                "size": 13818,
        

          17
                "records": 4,
        

          18
                "updatedAt": "2026-04-15T18:20:05.742Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

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

Returns the complete dataset as a single ZIP archive covering all Form 40-8B25 filings from October 2004 to the present. This endpoint requires an API key passed via the token query parameter.

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

Containers are organized as monthly ZIP archives following the year/yyyy-mm.zip path layout. Each archive expands into one folder per accession number, with each folder holding the metadata JSON and the original EDGAR submission documents (HTML and TXT) for that filing. This endpoint requires an API key passed via the token query parameter.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers EDGAR submissions accepted under form type 40-8B25 — applications filed under Rule 8b-25(a) of the Investment Company Act of 1940 by registered investment companies seeking additional time, of up to 60 days, to file a specific 1940 Act report or document. Amended applications filed under 40-8B25/A are a separate EDGAR form code and are not included.

What does one record in this dataset represent?

One record corresponds to one accepted EDGAR accession on Form 40-8B25. It is materialized as a folder keyed on the 18-digit zero-padded accession number and contains a metadata.json describing the EDGAR header and document inventory plus the original Form 40-8B25 application document(s), most often an HTML primary document and the EDGAR-generated complete submission text file.

Who is required to file Form 40-8B25?

The legal filers are registrants under the Investment Company Act of 1940: open-end and closed-end management investment companies, unit investment trusts, business development companies (for their 1940 Act reports), and face-amount certificate companies. Operating-company Exchange Act registrants and foreign private issuers do not use Form 40-8B25; they use Form 12b-25 for their Exchange Act periodic reports.

How does Form 40-8B25 differ from Form 12b-25?

Form 12b-25 is a self-effectuating notification under Exchange Act Rule 12b-25 that grants an automatic extension of 5 calendar days for Form 10-Q and 15 calendar days for Form 10-K. Form 40-8B25 is an application under Investment Company Act Rule 8b-25 that requires affirmative SEC approval and can extend a 1940 Act filing deadline by up to 60 days. A BDC may use Form 12b-25 for its Exchange Act 10-K or 10-Q and Form 40-8B25 for its 1940 Act reports.

What 1940 Act reports do these applications most often seek to extend?

Most applications target Form N-CEN (the annual census report for registered investment companies, which replaced Form N-SAR effective June 1, 2018) or Form N-CSR (certified semi-annual shareholder reports). Earlier records in the dataset reference Form N-SAR; later records reference Form N-CEN. The underlying delayed filing is identified narratively in Part I of the application rather than through a structured metadata field.

What time period does the dataset cover and how is it refreshed?

EDGAR coverage of Form 40-8B25 begins on October 1, 2004 and runs to the present. The dataset is event-driven rather than periodic — a record exists only when a registrant has applied to extend a specific 1940 Act filing deadline — and is delivered as monthly ZIP containers under a year/yyyy-mm.zip path layout, with the JSON index endpoint exposing per-container updatedAt timestamps for incremental refresh.

What file format is the dataset distributed in?

The dataset is distributed as ZIP containers organized by month. Each container expands into one folder per accession number containing HTML, JSON, and TXT files: the primary Form 40-8B25 application as HTML inside an EDGAR SGML <DOCUMENT> wrapper, the per-accession metadata.json, and (when present) the EDGAR-generated complete submission text file. Image attachments from the original EDGAR submission are excluded; Form 40-8B25 carries no XBRL.

Does a Form 40-8B25 filing mean the registrant is automatically late?

No. Form 40-8B25 must be filed on or before the original due date of the underlying report and the extension is not self-effectuating — the Commission must grant the application before the registrant may rely on it. A granted Rule 8b-25 extension is therefore the mechanism that distinguishes a sanctioned late filing from a delinquent one, which is a key compliance and due-diligence distinction when reconciling 40-8B25 records against late or amended N-CEN and N-CSR filings.