The Form N-54A Files dataset packages every Form N-54A and Form N-54A/A submission accepted by EDGAR, the form a closed-end company files under Section 54(a) of the Investment Company Act of 1940 to elect regulation as a business development company (BDC) subject to Sections 55 through 65 of the Act. Each record corresponds to one EDGAR accession — identified by its 18-digit accession number — and contains a structured metadata.json descriptor plus the original submission documents (typically a primary HTM notification, sometimes a complete-submission TXT rendering, and occasionally a PDF), with image binaries removed. The filer is the electing closed-end company itself, and the form variants covered are N-54A (initial notification of election) and N-54A/A (amendment to a previously filed N-54A). The dataset spans EDGAR coverage of these notifications from April 1996 to the present and is delivered as a ZIP container with TXT, JSON, HTML, and PDF file types.
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 is built around Form N-54A, a notification of election filed pursuant to Section 54(a) of the Investment Company Act of 1940. By filing it, a closed-end company informs the SEC that it elects to be regulated as a business development company and accepts the regulatory regime of Sections 55 through 65 of the Act. The form is short, declarative, and tightly templated: it does not contain financial statements, prospectus narrative, risk discussion, or governance disclosure. Its statutory function is to switch the filer into the BDC framework and to certify the substantive preconditions Section 54(a) requires — closed-end status, an investment program directed at the asset categories enumerated in Section 55(a)(1)–(3), and a commitment to provide significant managerial assistance to the issuers of those securities. Form N-54A/A serves the same statutory purpose but corrects, supplements, or restates a previously submitted N-54A; the body reuses the same template, with only the content of the disclosed fields differing.
The dataset covers the entire EDGAR-era population of these notifications, beginning April 1, 1996, when investment company filings were phased onto EDGAR. Pre-EDGAR paper notifications, which existed from late 1980 onward following the Small Business Investment Incentive Act of 1980, are not in scope. Filings are distributed in a ZIP container, with each accession materialized as a folder whose name is the dash-stripped 18-digit form of the accession number (for example, 000158064225001340 for accession 0001580642-25-001340). Each folder bundles two layers: a metadata.json descriptor that captures filing-level and entity-level facts in structured form, and the original EDGAR submission documents themselves with image binaries removed. The dataset therefore preserves both a machine-readable index of the filing and the substantive notification document(s) as transmitted to the Commission.
A record is organized in two layers that should be treated separately by downstream code.
The first layer is metadata.json, present in every accession folder. It is the canonical parsed descriptor of the filing and the most reliable join key into the rest of the record.
The second layer is the set of original EDGAR submission documents for the accession: typically the primary N-54A notification as an HTM file, sometimes a complete-submission .txt rendering, and occasionally a PDF rendering, depending on what the filer transmitted. Each non-metadata document retains the SGML <DOCUMENT> envelope used throughout EDGAR, so the HTML body of the form is wrapped by leading SGML header lines (<TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, <TEXT>) and closed by </TEXT></DOCUMENT>. Image files that may have been part of the original submission are excluded.
metadata.json descriptormetadata.json describes the filing at three levels: submission identity, document inventory, and filer identity.
Submission identity fields include formType (N-54A or N-54A/A), accessionNo in dashed canonical form (e.g., 0001580642-25-001340), filedAt as an ISO-8601 timestamp with timezone offset, a short human-readable description, linkToFilingDetails pointing at the primary filing document on EDGAR, linkToTxt pointing at the full SGML submission text on EDGAR, linkToHtml pointing at the EDGAR filing index page, and linkToXbrl (typically empty for this form type). An internal id field provides an opaque hex identifier for the record.
Document inventory is carried in documentFormatFiles, an array with one object per attached document. Each entry exposes sequence (document order within the submission), size (byte size as a string), documentUrl (direct EDGAR URL), description (e.g., N-54A, Complete submission text file), and type (the document-type identifier as declared on the SGML envelope). A parallel dataFiles array exists for supplementary structured data files; for N-54A submissions it is normally empty.
Filer identity is carried in the entities array. Each entry typically includes companyName (often suffixed with the parenthesized role such as (Filer)), cik (Central Index Key), fileNo (SEC file number; for BDC filings these are commonly in the 814- series), irsNo (IRS employer identification number), stateOfIncorporation as a two-letter code, fiscalYearEnd formatted as MMDD, act (the securities act under which the filing is made — 40 for the Investment Company Act of 1940), type (the form type as recorded in the EDGAR header), and filmNo (the EDGAR film number assigned to the submission). A seriesAndClassesContractsInformation array can carry series and class contract metadata for fund filers; it is typically empty for N-54A filings.
The primary HTM document follows the standard template required by Section 54(a). Inside the SGML envelope, the HTML body presents the substantive notification, which contains the following components in approximate order:
Because the form is declarative and tightly templated, the body is short — typically a single HTML page on the order of a few kilobytes — and contains no financial tables, no exhibits, and no incorporated narrative.
An N-54A/A record uses the same folder layout, metadata schema, and document conventions as an initial N-54A. The body of the document reuses the same template; the substantive change lies in the disclosed fields — for instance, an updated name or address, a corrected agent for service of process, a revised Section 12 registration status, or a re-execution of the certification. The formType field in metadata.json is the correct discriminator between amendments (N-54A/A) and initial elections (N-54A); both variants are stored under the same folder structure and accession-number naming convention.
For each accession, the record contains the parsed metadata.json descriptor and all documents from the original EDGAR submission package, with image files removed. In practice this is the primary HTM notification, sometimes a complete-submission TXT file, and occasionally a PDF rendering. Non-metadata documents retain their SGML <DOCUMENT> wrapper.
Image files that may have appeared in the original EDGAR submission (such as scanned signature pages or logos) are excluded. Form N-54A does not require exhibits, so no exhibit attachments need to be omitted — what is preserved is exactly the substantive notification and any complete-submission rendering supplied by the filer.
The disclosure obligations imposed by Section 54(a) and the corresponding Form N-54A template have been remarkably stable since EDGAR coverage began in April 1996. The filer has always been required to identify itself, disclose its principal business office and agent for service of process, address its Section 12 status, list any prior Investment Company Act file numbers, and execute the closed-end certification together with the Section 55(a) investment intent and the significant-managerial-assistance undertaking. Because the form serves only as the statutory hinge that subjects a closed-end company to BDC regulation, it has not accumulated the layers of disclosure (risk factors, governance, compensation, structured tagging) added over time to operating-company forms such as 10-K or 10-Q. An N-54A filed in the late 1990s and an N-54A filed in 2025 carry effectively the same substantive content blocks.
Filings in the earliest years of EDGAR coverage were transmitted as ASCII text inside the SGML <DOCUMENT> envelope, with the body rendered in plain-text formatting. Over time, filers transitioned to HTML bodies wrapped in the same envelope, and that is the dominant form encountered in modern records. The file-types found in the dataset are TXT, JSON, HTML, and PDF: the JSON layer is the dataset's own metadata.json, the HTML files are the modern primary documents, the TXT files capture either legacy ASCII bodies or modern complete-submission text renderings, and PDF appears occasionally as a filer-supplied rendering.
metadata.json is present in every accession folder and is the safest entry point for enumeration. Folder names are dash-stripped accession numbers, while the dashed canonical form is preserved inside the JSON as accessionNo; the two forms must be reconciled when joining against external EDGAR data.
Parsers reading the primary HTM document must handle the SGML wrapper. The leading <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, and <TEXT> lines precede the actual <HTML> body, and the document is closed by </TEXT></DOCUMENT> after </HTML>. Treating the file as a pure HTML document without stripping these envelope markers will produce malformed parses.
The document inventory is small. Most folders contain only the primary HTM file plus metadata.json; some additionally include a complete-submission .txt file. This is a property of the form itself rather than a packaging quirk — Form N-54A is a one-page declarative notification and rarely involves additional attachments.
The entities array can contain more than one entry when multiple filers are listed in the EDGAR header (for example, a parent and a controlled BDC making a joint election). Downstream code should iterate through entities rather than assuming a single filer. The combination of act set to 40 and a fileNo in the 814- series is a reliable signal that the entity is being filed as a business development company under the Investment Company Act of 1940.
The substantive content of an N-54A is short, formulaic, and tightly bounded. Extraction-friendly fields — registrant name, principal office, agent for service, Section 12 status, prior Investment Company Act file numbers, signing officer, and execution date — can be reliably parsed from the HTML body once the SGML wrapper is removed, but the certification language itself is boilerplate and carries little record-to-record variation.
A record in the Form N-54A Files dataset is a single Form N-54A or Form N-54A/A submission to EDGAR. The filer is a closed-end company electing, under Section 54(a) of the Investment Company Act of 1940, to be regulated as a business development company and therefore subject to Sections 55 through 65 of the Act. The form is a notification of election, not a registration statement, prospectus, or periodic report.
The filer is the electing closed-end company itself, signed by an authorized officer. The investment adviser, sponsor, or parent holding company is not the filer, even when it organized and controls the BDC.
To be eligible to file, an entity must:
Both publicly traded (exchange-listed) BDCs and non-traded BDCs file the same Form N-54A; the form does not distinguish between the two structures.
The following adjacent entities do not file Form N-54A:
Section 54(a) provides that a closed-end company meeting the Section 2(a)(48) definition may elect to be subject to Sections 55 through 65 by filing a notification of election with the Commission. Form N-54A is the prescribed notification.
Once the notification is filed, the electing company is subject to the BDC subchapter, including:
The BDC subchapter modifies or displaces certain otherwise-applicable provisions of Sections 1 through 53. A BDC is not registered under Section 8; it is regulated through the Section 54(a) election.
Form N-54A is event-driven, not periodic. The triggering event is the filer's own decision, authorized by its board, to elect BDC regulation. There is no externally imposed deadline and no Commission declaration of effectiveness for the election itself; the election takes effect upon filing.
Typical sequencing:
The election remains in effect indefinitely. Form N-54A is filed once and is not refiled on any cycle. A BDC may withdraw its election only by filing Form N-54C under Section 54(c), subject to the conditions in Section 58 governing changes in the nature of the business.
Form N-54A/A amends a previously filed Form N-54A. Because the underlying notification is short, amendments are uncommon and are typically used to:
An N-54A/A does not withdraw the BDC election (that is the function of Form N-54C) and is not a periodic disclosure.
The BDC subchapter was added to the 1940 Act by the Small Business Investment Incentive Act of 1980 (Pub. L. 96-477). Notifications of election existed in paper form from late 1980 onward. The earliest filings in this dataset begin in April 1996, reflecting the EDGAR phase-in for investment company filings; pre-EDGAR paper notifications are not in scope.
Form N-54A marks a single moment: a closed-end company's election to be regulated as a BDC under Section 54(a). Several SEC datasets cluster around this election and are easily mistaken for it. The most useful comparisons are its direct counterpart (N-54C), the BDC's registration and ongoing reporting stack (N-2, 10-K, 8-K), and adjacent 1940 Act notifications and census filings (N-8A, N-CEN, N-1A).
N-54C is the mirror of N-54A: same statute (Section 54), same filer population, same minimal structure. N-54A opts a closed-end company into Sections 55–65; N-54C opts it out. Use N-54A to identify entry into BDC status, N-54C for exit. Together they form the universe of BDC-status transitions; neither alone confirms whether a company is currently a BDC.
Most BDCs file both N-54A and N-2, but the forms answer different questions. N-54A is a 1940 Act status election — a few pages of intent. N-2 is a 1933 Act securities registration — prospectus, fee tables, risk factors, financial statements, and post-effective amendments, often hundreds of pages. Use N-54A for "is this a BDC and when did it elect?"; use N-2 for "what is this BDC offering and on what terms?" N-2 is also far larger in volume than the N-54A corpus.
BDCs do not file N-CSR or fund-style annual reports. After electing under N-54A, they report under the Exchange Act on Forms 10-K and 10-Q, with BDC-specific schedules of investments and Section 55(a) qualifying-asset disclosures. N-54A is a one-time notice with no financials; 10-K is the recurring audited annual report with MD&A, financials, and governance. 10-K is also the only way to verify that an entity is still operating as a BDC years after its election — N-54A alone cannot establish current status.
8-K is a 1934 Act event-driven current report with itemized triggers and a four-business-day deadline. N-54A is a 1940 Act status notification with no recurring trigger. A change in BDC status is announced via N-54A or N-54C, though a BDC may also issue an 8-K describing the same event for investor disclosure. The two are complementary around status events, not substitutes.
Form N-8A is the structural analog to N-54A in the 1940 Act notification family. N-8A registers an entity as an investment company under Section 8(a); N-54A elects BDC treatment under Section 54(a). The two are mutually exclusive: a BDC is not a registered investment company, so it files N-54A and not N-8A. Together they cover the two main 1940 Act entry points; each identifies a distinct regulatory population.
N-CEN is a structured, XML-based annual census of registered investment companies (replacing N-SAR). BDCs are not registered investment companies and do not file N-CEN. The two datasets are essentially disjoint: N-CEN covers mutual funds, ETFs, non-BDC closed-end funds, and UITs; N-54A is unique to the BDC subset N-CEN excludes.
Form N-1A registers open-end mutual funds and most ETFs. Open-end structure is incompatible with BDC status, so an N-1A filer will not appear in the N-54A dataset. Use N-1A for prospectus content on open-end funds; the overlap with N-54A is essentially zero.
N-54A is distinct because of its narrow, status-defining role. It is not a registration statement, not a periodic report, not an event-driven current report, and not a structured census. It is the one-time, statutorily prescribed notification — plus N-54A/A amendments — that converts a closed-end company into a BDC subject to Sections 55–65. The corpus is correspondingly small, document-light, and narrative.
Practical routing:
The Form N-54A Files dataset is best treated as the BDC-population gateway: small, definitional, and most useful when joined to the larger registration and reporting datasets that describe what each BDC does after election.
Because Form N-54A captures a discrete, dateable event that anchors the BDC universe, the dataset is used by a narrow set of professionals who track BDC formation, draft the elections, or model the entities afterward.
Sell-side and buy-side analysts covering listed BDCs use the dataset to maintain a complete roster of every entity that has ever elected BDC status. They pull registrant name, CIK, state of incorporation, and filing date, then reconcile against later 10-K, 10-Q, and N-2 filings to flag active, acquired, and wound-down BDCs. The output is sector sizing, formation-by-year league tables, and entry-rate analysis across credit cycles.
Researchers tracking middle-market direct lending treat new N-54A filings as a leading indicator of fresh BDC capacity, especially non-traded and perpetual-life vehicles signaling pending retail fundraising. They focus on the election date, sponsor or adviser disclosed in the cover document, and the Section 55(a) investment statement, then cross-reference with later N-2 registrations and adviser Form ADV updates to map platform launches and sponsor franchise expansion.
Attorneys preparing a new BDC election use prior N-54A and N-54A/A filings as a precedent library. They examine the closed-end certification, the Section 55(a) statement of intent, the managerial-assistance undertaking, and signature blocks to benchmark drafting against peers and to see how amendments have corrected earlier notifications. The dataset shortens diligence on first-time BDC clients and supports template construction for elections, conversions, and amendments.
Compliance officers at advisers sponsoring BDCs or converting closed-end funds use the dataset to confirm filing posture for affiliated entities, populate internal regulatory calendars from accession numbers and filing dates, and study amendment patterns before filing an N-54A/A.
Capital introduction, prime brokerage, administration, and transfer agency teams use new N-54A accessions as an early-warning list of entities that will shortly need leverage facilities, custody, distribution support, or seed capital. They extract registrant name, address, and any disclosed sponsor to route leads, since the election typically precedes vendor selection.
Economists studying BDC formation, post-2018 leverage rules, and non-bank lending dynamics use the full 1996-to-present series of election dates, geographic distribution, and N-54A/A amendment frequency to build cohort and entry-rate analyses tied to statutory changes.
Quant teams running factor or event-driven strategies on listed BDCs use the election date as the inception point for any BDC-specific factor, preventing contamination from pre-election closed-end performance. The dataset supports clean cohort construction, survivorship correction, and panel datasets for BDC return, leverage, and dividend studies.
Engineers building EDGAR ingestion and entity reference systems consume the metadata file per accession to write CIK, filer name, form type, filing date, and accession ID into entity-lifecycle tables alongside 1940 Act registration, IPO, and deregistration events. The included TXT, JSON, HTML, and PDF documents are used to validate parsers and back-test pipeline logic against the full historical corpus.
Teams building retrieval-augmented systems for fund formation and regulatory advisory use the corpus as a small, structurally consistent set of 1940 Act notifications. The short documents and fixed citation to Section 54(a) make them useful for fine-tuning extractors on filer identity, election date, and certification language, and for grounded question-answering on the BDC election process.
Across these users, the load-bearing fields are consistent: filer identity (CIK, name, address), election date, N-54A/A amendment status, and the certification and undertaking language that gives the filing its legal effect.
The Form N-54A Files dataset supports a narrow set of practical workflows around BDC universe construction, drafting precedent, and event-driven research.
Construct a year-by-year league table of BDC elections by iterating metadata.json across all accession folders and extracting filedAt, entities[].companyName, entities[].cik, and formType. Filtering on formType == "N-54A" (excluding N-54A/A amendments) yields one row per initial election, which feeds sector-sizing dashboards, cohort studies, and entry-rate charts tied to credit-cycle phases or statutory changes such as the 2018 leverage reform.
Poll new N-54A accessions and extract registrant name, principal business office address, telephone number, and agent for service of process from the primary HTM body, plus cik and fileNo (typically 814- series) from metadata.json. The output is a daily lead list of newly-electing BDCs that will shortly need leverage facilities, custody, transfer agency, and distribution arrangements, routed to prime brokerage, administration, and capital introduction desks before vendor selection closes.
Strip the SGML wrapper from the primary HTM document and index the closed-end certification, Section 55(a)(1) through (3) investment-intent statement, managerial-assistance undertaking, Section 12 / Rule 12g-2 election, and signature block. Filtering on formType == "N-54A/A" surfaces amendments and the specific fields they revise (name, agent for service, Section 12 status), giving fund counsel a benchmark library for drafting first-time elections and corrective filings.
Use accessionNo, cik, filedAt, stateOfIncorporation, fiscalYearEnd, and irsNo from metadata.json to write BDC election events into a master entity reference table alongside N-2 registrations, 10-K filings, and N-54C withdrawals. This produces a clean inception date for each BDC, which downstream quant pipelines use to bound BDC-specific factors and avoid contaminating panels with pre-election closed-end history.
Group records by cik and order by filedAt to reconstruct each filer's N-54A / N-54A/A chain. Diffing the parsed body fields between an initial N-54A and its later N-54A/A surfaces the specific correction (revised agent for service, updated Section 12 status, re-executed certification), which compliance teams use to study amendment patterns before filing their own N-54A/A and to populate internal regulatory calendars.
Use the corpus as a structurally consistent training set for fine-tuning field extractors and RAG retrievers on a small, tightly-templated form. The fixed Section 54(a) citation, the boilerplate certification, and the small set of variable slots (registrant identity, address, agent for service, Section 12 status, signing officer) make the dataset well-suited to evaluating extraction accuracy and grounding question-answering systems on the BDC election process.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-n54a-files.json
This endpoint returns the dataset metadata, including name, description, last update timestamp, earliest sample date (1996-04-01), total records and total size, covered form types (N-54A, N-54A/A), container format (ZIP), and included file types (TXT, JSON, HTML, PDF). It also lists every container file in the dataset along with per-container metadata such as size, record count, last updated timestamp, and a direct download URL. Use this endpoint to monitor which containers were updated in the latest refresh run and to decide which containers to download incrementally on a day-by-day basis. This endpoint does not require an API key.
Example response:
1
{
2
"datasetId": "1f13365b-9ae0-69cf-af75-407094932dd9",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-n54a-files.zip",
4
"name": "Form N-54A Files Dataset",
5
"updatedAt": "2026-04-15T12:25:17.308Z",
6
"earliestSampleDate": "1996-04-01",
7
"totalRecords": 430,
8
"totalSize": 5232465,
9
"formTypes": ["N-54A", "N-54A/A"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["TXT", "JSON", "HTML", "PDF"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-n54a-files/2026/2026-03.zip",
15
"key": "2026/2026-03.zip",
16
"size": 184320,
17
"records": 4,
18
"updatedAt": "2026-04-15T12:25:17.308Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-n54a-files.zip?token=YOUR_API_KEY
Downloads the complete dataset as a single ZIP archive containing all Form N-54A and Form N-54A/A filings from April 1996 to the present. This endpoint requires an API key.
Download Single Container: https://api.sec-api.io/datasets/form-n54a-files/2026/2026-03.zip?token=YOUR_API_KEY
Downloads one individual monthly container file rather than the full archive. Container paths are listed in the dataset index JSON response under the containers array. This endpoint requires an API key.
The dataset covers Form N-54A, the notification of election filed under Section 54(a) of the Investment Company Act of 1940, and Form N-54A/A, which amends a previously filed N-54A. Both variants share the same record shape, and the formType field in metadata.json is the authoritative discriminator between an initial election and an amendment.
One record corresponds to a single Form N-54A or Form N-54A/A submission accepted by EDGAR, identified uniquely by its SEC accession number. Each record is materialized as an accession-named folder containing a metadata.json descriptor and the original EDGAR submission documents (typically a primary HTM notification, sometimes a complete-submission TXT rendering, and occasionally a PDF), with image binaries removed.
The filer is the electing closed-end company itself, signed by an authorized officer — typically a domestic closed-end management investment company organized as a corporation, statutory trust, or LLC that meets the BDC definition in Section 2(a)(48). The investment adviser, sponsor, or parent holding company is not the filer, even when it organized and controls the BDC, and open-end funds, UITs, and private funds are categorically ineligible.
Form N-54A is event-driven, not periodic. The triggering event is the filer's own decision, authorized by its board, to elect BDC regulation; the election takes effect upon filing, with no externally imposed deadline and no Commission declaration of effectiveness. The election remains in effect indefinitely and is withdrawn only by filing Form N-54C.
The dataset includes Form N-54A and Form N-54A/A filings submitted to EDGAR from April 1, 1996 to the present, reflecting the EDGAR phase-in for investment company filings. Pre-EDGAR paper notifications, which existed from late 1980 onward following the Small Business Investment Incentive Act of 1980, are not in scope.
The dataset is distributed as a ZIP container, with each accession folder containing a metadata.json descriptor plus the original EDGAR submission documents. File types found in the dataset are TXT, JSON, HTML, and PDF: JSON is the dataset's own metadata layer, HTML is the dominant format for modern primary documents, TXT covers either legacy ASCII bodies or modern complete-submission text renderings, and PDF appears occasionally as a filer-supplied rendering.
Form N-54C is the mirror of Form N-54A: same statute (Section 54), same filer population, same minimal structure, but N-54C opts a closed-end company out of the BDC regime rather than into it. Use the Form N-54A Files dataset to identify entry into BDC status and the Form N-54C dataset for exit; together they form the universe of BDC-status transitions.
The dataset preserves the substantive notification — the primary HTM document, optional complete-submission TXT rendering, and any PDF rendering — while excluding image binaries (such as scanned signature pages or logos) from the original EDGAR submission. Form N-54A does not require exhibits, so no exhibit attachments are dropped; only image binaries are removed.