Form N-2 POSASR Files Dataset

The Form N-2 POSASR Files Dataset is a collection of every EDGAR submission of form type N-2 POSASR — post-effective amendments to automatic shelf registration statements filed on Form N-2 by closed-end management investment companies and business development companies (BDCs) that qualify, at the time of filing, as well-known seasoned issuers (WKSIs) under Securities Act Rule 405. Each record is a single accession-numbered EDGAR submission, packaged as one folder containing a metadata.json header view of the filing and the original SGML-wrapped HTML documents (the primary N-2 POSASR document plus its EX-99.(x) exhibits). The dataset begins on February 1, 2021, when EDGAR Release 20.4 introduced the dedicated N-2 POSASR submission type alongside the 2020 Securities Offering Reform for Closed-End Funds (Release 33-10771) that extended automatic shelf registration and Rule 462(e) immediate effectiveness to qualifying funds and BDCs. Records are delivered as ZIP archives organized by calendar year and year-month, with HTML documents preserving EDGAR's standard SGML envelope and JSON metadata exposing accession identifiers, filer entities, document manifests, and effectiveness timestamps.

Update Frequency
Daily
Updated at
2026-04-16
Earliest Sample Date
2021-02-01
Total Size
580.0 KB
Total Records
33
Container Format
ZIP
Content Types
HTML, JSON
Form Types
N-2 POSASR

Dataset APIs

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:

Dataset Files

6 files · 580.0 KB
Download All
2026-02.zip189.9 KB6 records
2022-03.zip33.5 KB4 records
2021-09.zip296.1 KB3 records
2021-08.zip13.8 KB3 records
2021-06.zip31.3 KB13 records
2021-02.zip15.4 KB4 records

What This Dataset Contains

The dataset captures the full population of N-2 POSASR submissions on EDGAR — post-effective amendments used by WKSI closed-end funds and BDCs to keep an effective Form N-2 automatic shelf registration current. Form N-2 is the joint Securities Act of 1933 and Investment Company Act of 1940 registration form for closed-end funds and BDCs; under General Instruction A.2, an eligible WKSI may file an automatic shelf registration statement on Form N-2, and once that shelf is effective, the registrant uses a POSASR to amend it on a post-effective amendment basis — to refresh the prospectus and Statement of Additional Information, update the fee table, add new classes of securities, file or substitute exhibits, or incorporate updated audited financials. Because automatic shelf registrations of WKSIs become effective immediately upon filing under Rule 462(e), a POSASR also takes effect on filing, so effectivenessDate ordinarily equals the filed date.

EDGAR introduced the dedicated N-2 POSASR submission type in Release 20.4 in early 2021 alongside the modernization of investment-company offering rules; before that change, post-effective amendments to N-2 automatic shelves were filed under generic post-effective-amendment submission types and were not separately identifiable as POSASR-on-N-2. Dataset coverage therefore begins on February 1, 2021. Records are distributed as ZIP archives keyed by year and year-month, with each accession folder containing a metadata.json and a small set of .htm documents wrapped in EDGAR's SGML envelope. Image attachments (GRAPHIC documents) and the consolidated complete-submission .txt SGML bundle are referenced inside metadata.json but are not bundled into the dataset record.

Content Structure of a Single Record

What one record represents

A single record in the Form N-2 POSASR Files dataset is one EDGAR submission of form type N-2 POSASR. The unit is the accession numbered filing as a whole, not an individual prospectus, exhibit, or item within it.

On disk, each record materializes as a folder named after the EDGAR accession number with hyphens stripped (for example 000110465921108668 for accession 0001104659-21-108668). The folder holds two complementary layers: a metadata.json capturing EDGAR's structured filing header, and the original filing documents as .htm files wrapped in EDGAR's SGML document envelope. Image attachments and the consolidated SGML submission text file referenced by EDGAR are excluded from the dataset copy.

What the underlying filing is

The underlying filing follows Form N-2's three-part architecture: Part A (prospectus), Part B (Statement of Additional Information), and Part C ("Other Information," including signatures and the exhibit index). A POSASR may restate the full Part A/Part B prospectus and SAI, or — more commonly — restate only the cover, Part C signatures, and exhibit index while incorporating prospectus and SAI content by reference to the existing base registration and to subsequent Exchange Act reports. Substantive Form N-2 disclosure spans investment objectives and principal investment strategies; the fee and expense table together with the standard hypothetical-investment expense example; principal risks specific to closed-end fund or BDC structure (leverage limits under 1940 Act sections 18 and 61, market discount of common shares, illiquidity, valuation of Level 3 assets, RIC qualification under Subchapter M, BDC election under section 54); description of the securities being registered; plan of distribution for shelf takedowns; management of the fund and portfolio managers; dividend reinvestment plan; tax treatment; custodian, transfer agent, and other service-provider identification; senior securities table and financial highlights; and audited financial statements together with the auditor's report.

On-disk structure of a record

Each accession folder is self-contained and has two layers.

metadata.json — a single JSON document that captures EDGAR's structured submission header. It is the only JSON file in the folder and is always present. It is the authoritative machine-readable view of filing-level identifiers, timestamps, links, the entity list, and the document manifest, and should be treated as canonical even where the same facts also appear inside the SGML preambles of the HTML files.

Filing documents — one or more .htm files, each an EDGAR-standard SGML-wrapped HTML document. The set is small: a primary N-2 POSASR document plus a handful of EX-99.(x) exhibit documents. Filenames are issuer- or filing-agent-generated (the tm prefix is common for filings prepared by Toppan Merrill) and are not normalized by the dataset; consumers should rely on documentFormatFiles[].type and description for semantic identification rather than on filenames.

Image files referenced by the submission (EDGAR document type GRAPHIC, normally .jpg or .gif artwork embedded in the prospectus) and the consolidated complete-submission .txt SGML bundle are catalogued inside metadata.json but are not bundled into the dataset record. The HTML continues to reference image filenames internally, but the binaries are absent locally.

metadata.json fields

metadata.json exposes the following intentional fields:

  • formType — always "N-2 POSASR" for this dataset.
  • accessionNo — EDGAR accession number in canonical hyphenated form, e.g. "0001104659-21-108668". The parent folder name strips the hyphens; the hyphenated form lives only inside the JSON.
  • filedAt — full ISO 8601 timestamp with timezone offset for EDGAR acceptance.
  • effectivenessDate — ISO date on which the post-effective amendment becomes effective; for automatic shelf POSASRs, ordinarily the same calendar date as filedAt.
  • description — short EDGAR caption such as "Form N-2 POSASR -".
  • linkToFilingDetails — absolute sec.gov URL to the primary form document.
  • linkToTxt — absolute URL to the complete-submission SGML .txt file on EDGAR.
  • linkToHtml — absolute URL to the EDGAR filing index page (-index.htm).
  • linkToXbrl — URL to inline XBRL content; empty for these filings.
  • id — opaque hex string identifying the record inside the dataset.
  • documentFormatFiles[] — manifest of every document EDGAR recorded for the submission. Each entry carries sequence (numeric string such as "1", "2"; a single space " " is used for the row representing the complete-submission text file), size (byte count as a string), documentUrl (absolute sec.gov URL), description (human caption such as "N-2 POSASR", "EXHIBIT (L)", "GRAPHIC", or "Complete submission text file"), and type (EDGAR document-type code such as "N-2 POSASR", "EX-99.(L)", "EX-99.(N)", "GRAPHIC", or " " for the consolidated SGML bundle). Because the manifest enumerates the full EDGAR submission, it includes entries for documents intentionally omitted from the dataset (GRAPHIC images and the complete-submission text file); consumers must intersect the manifest with the actual files on disk rather than assume every URL maps to a local file.
  • entities[] — filers/registrants associated with the submission. A typical entry carries cik, companyName with the role appended in parentheses (e.g. "... (Filer)"), fileNo (the 333- registration file number), irsNo, act (Securities Act designator, typically "33"), stateOfIncorporation, fiscalYearEnd in MMDD form, filmNo assigned by EDGAR at acceptance, type, and a tickers array. Closed-end funds and BDCs commonly file with a single Filer entity.
  • seriesAndClassesContractsInformation[] — array reserved for series/class identifiers; for N-2 POSASR submissions in this dataset it is generally present but empty, since closed-end funds and BDCs do not typically use the open-end series/class framework.
  • dataFiles[] — array reserved for XBRL or other data exhibits; generally present but empty for these records.

SGML-wrapped HTML documents

Every filing document is a single .htm file that opens with a short EDGAR SGML preamble and closes by terminating the wrapper after the HTML payload. The preamble identifies the document's TYPE (the EDGAR form/exhibit code), SEQUENCE (its position in the submission), FILENAME as stored on EDGAR, and DESCRIPTION caption, before a TEXT block that contains the HTML body. A typical layout:

1 <DOCUMENT>
2 <TYPE>N-2 POSASR
3 <SEQUENCE>1
4 <FILENAME>tm2125601d1_n2posasr.htm
5 <DESCRIPTION>N-2 POSASR
6 <TEXT>
7 <HTML>
8 ... full HTML body of the post-effective amendment ...
9 </HTML>
10 </TEXT>
11 </DOCUMENT>

HTML parsers must tolerate or strip these wrapper lines; treating the file as pure HTML will produce stray text before <html> and a stray closing </TEXT></DOCUMENT> after </html>.

The documents inside a record fall into two categories.

Primary document. EDGAR TYPE=N-2 POSASR, SEQUENCE=1. This file is the post-effective amendment as such. Depending on how the registrant chooses to amend, it may carry only the cover page, Part C signatures, and exhibit index that incorporate the existing prospectus and SAI by reference, or it may restate the full Part A prospectus with updated fee tables, investment-strategy descriptions, risk factors, plan-of-distribution language, and embedded financial highlights.

Exhibit documents. Each remaining .htm file is an exhibit, listed in EDGAR with TYPE of the form EX-99.(x) where x is the parenthetical letter from Form N-2 General Instruction G. The Instruction G exhibit codes are:

  • (a) charter
  • (b) bylaws
  • (c) voting trust agreements
  • (d) instruments defining holders' rights
  • (e) dividend reinvestment plan
  • (f) long-term debt instruments
  • (g) investment advisory contracts
  • (h) underwriting contracts
  • (i) bonus, profit-sharing, and pension plans
  • (j) custodian agreement
  • (k) other material contracts
  • (l) opinion and consent of counsel as to legality of the securities
  • (m) Rule 12b-1 plan
  • (n) consents of independent registered public accountants and other experts
  • (o) information from omitted financial statements
  • (p) initial seed-capital agreements
  • (q) model retirement-plan documents
  • (r) code of ethics
  • (s) calculation of filing fee tables for fee-bearing amendments

Each exhibit file contains the underlying legal letter, contract, schedule, or table rendered in HTML. EX-99.(L) (opinion and consent of counsel) and EX-99.(N) (auditor consent under Securities Act Rule 436) are particularly common in POSASR amendments because both must be refreshed for each post-effective amendment that incorporates audited financials by reference. Exhibit EX-99.(s) / EX-FILING FEES carries the calculation-of-filing-fee table introduced by the 2022 Rule 408 amendments to Item 25 when the amendment is fee-bearing.

Form N-2 prospectus content carried in the record

When the POSASR restates prospectus material rather than purely incorporating by reference, the HTML body of the primary document follows the canonical Form N-2 outline. The cover page identifies the registrant, the 333- file number, the maximum aggregate offering price for the shelf, and the securities being registered (common shares, preferred shares, debt, subscription rights, warrants, or units). The fee table itemizes shareholder transaction expenses (sales load, dividend reinvestment plan fees, offering expenses borne by shareholders) and annual expenses (management fees, leverage-related interest expense, acquired fund fees and expenses, other expenses, total annual expenses), followed by the hypothetical-investment expense example. A summary recapitulates investment objectives, principal strategies, principal risks, and the distribution policy. Risk-factor narrative covers portfolio risks (credit, interest rate, liquidity, valuation), structural risks of closed-end funds or BDCs (leverage limits, market discount, anti-takeover provisions in the charter), regulatory and tax risks (RIC qualification, BDC election), and offering-specific risks. Subsequent sections present the senior securities table, use of proceeds, the manager and portfolio managers, the dividend reinvestment plan, the description of capital stock and any senior securities, plan of distribution for the shelf, custodian and transfer agent, legal matters, experts, and financial highlights. Audited financial statements and notes are typically incorporated by reference from the registrant's most recent annual report on Form N-CSR; the auditor's consent in EX-99.(N) supplies the Rule 436 consent for that incorporation.

Container packaging

The dataset is delivered as ZIP archives organized by calendar year and year-month, addressed at paths of the form YYYY/YYYY-MM.zip. Inside each year-month archive, the top-level directory is the YYYY-MM string, and beneath it sit one folder per accession number with hyphens stripped. Each accession folder holds its own metadata.json and its own filing documents and does not depend on any sibling folder.

Included content

A record reliably includes:

  • one metadata.json capturing EDGAR's complete header view of the submission;
  • the primary HTML document for the N-2 POSASR itself, wrapped in the EDGAR SGML envelope;
  • every exhibit document (EX-99.(x)) attached to the EDGAR submission, each as its own SGML-wrapped HTML file.

Excluded or separate content

The following items are referenced from metadata.json but are deliberately not included in the dataset:

  • GRAPHIC documents (image binaries, typically .jpg artwork embedded in the prospectus). The HTML still references them by relative filename, but the binaries are absent.
  • The complete-submission .txt SGML bundle for the filing. It is reachable via linkToTxt but is not stored locally.

XBRL or other structured data exhibits are likewise not present in this dataset: linkToXbrl is empty and dataFiles[] is empty for these records.

Interpretation and extraction notes

Several details matter for correct extraction.

  • SGML preamble vs HTML body. The leading lines <DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, <TEXT> and the trailing </TEXT></DOCUMENT> are EDGAR wrapper, not HTML. Parsers must skip past <TEXT> before parsing or tolerate the wrapper lines.
  • Manifest vs disk. documentFormatFiles[] lists every document EDGAR recorded for the submission, including those intentionally omitted from the dataset (GRAPHIC, complete-submission text file). Consumers should intersect the manifest with the files actually on disk rather than assume every entry resolves locally.
  • String types in the manifest. documentFormatFiles[].sequence and .size are strings, not numbers. The row corresponding to the complete-submission text file uses a single space " " for both sequence and type.
  • Two forms of accession number. The folder name strips hyphens (000110465921108668) while metadata.json.accessionNo retains them (0001104659-21-108668). Both forms may be needed when joining against external EDGAR data.
  • Embedded role in entity name. entities[].companyName appends the role as a parenthetical suffix (e.g. " (Filer)"); name parsing must strip the suffix to recover the clean company name.
  • Incorporation by reference. Because much of the substantive prospectus content of an N-2 POSASR is often incorporated by reference to the base registration and to the registrant's most recent annual report on Form N-CSR, the local HTML may be considerably smaller than a full restated prospectus. The absence of fee tables, risk factors, or financial statements inside the local files is a normal consequence of incorporation by reference, not a packaging defect; the auditor consent (EX-99.(N)) and counsel opinion (EX-99.(L)) inside the record together with linkToFilingDetails and the registrant's Form N-CSR/N-CSRS filings outside the record provide the connective tissue.
  • Dedicated submission type since EDGAR Release 20.4. Before early 2021, post-effective amendments to N-2 automatic shelves were filed under generic post-effective-amendment submission types and were not separately identifiable as POSASR-on-N-2. The on-EDGAR presentation of N-2 POSASR has been stable since introduction: filings have always been delivered as HTML wrapped in the standard EDGAR SGML envelope, with header metadata exposed through the same metadata.json field set described above.

Who Files or Publishes This Dataset, and When

Who files

A Form N-2 POSASR is filed by a fund issuer that maintains an effective automatic shelf registration statement on Form N-2 and qualifies, at the time of filing, as a WKSI under Rule 405 at the time of filing. The filing population is narrow:

  • Registered closed-end management investment companies registered under the Investment Company Act of 1940 and offering securities under the Securities Act of 1933 on Form N-2.
  • Business development companies (BDCs) that have elected regulation under Sections 55-65 of the Investment Company Act and register their securities on Form N-2.

The legal filer is always the registrant. Underwriters, sales agents, selling securityholders, and investment advisers may appear in the amended prospectus, but they do not file the POSASR. Co-registrants (for example, BDC subsidiary guarantors) are listed on the cover page, but the submission remains a single accession.

WKSI eligibility for fund issuers, as adapted in 2020, generally requires (i) current Exchange Act or Form N-2 reporting status with a clean compliance history over the look-back period, (ii) the USD 700 million public common equity float threshold from Rule 405 (or the alternative non-convertible securities test), and (iii) absence of "ineligible issuer" status. A fund that loses WKSI status cannot continue using POSASR and must convert its shelf to the non-automatic regime.

What triggers a record

POSASR is event-driven, not periodic, but several triggers recur on an annual rhythm. Common triggers include:

  • Section 10(a)(3) annual update. Refreshing the prospectus with new audited financial statements and updated narrative disclosure after the fund's fiscal year end. This is the most common driver and produces at least one POSASR per fund per year.
  • Rule 413(b) addition of securities. Registering additional securities of the same class, or adding a new class, to the existing automatic shelf.
  • Material changes to investment objectives, strategies, fee structure, leverage program, distribution policy, risk factors, or management.
  • Updated Form N-2 fee table disclosure (annual expenses, interest on borrowings, preferred dividends, acquired fund fees and expenses).
  • Selling securityholder changes for resale registrations carried on the shelf.
  • Newly incorporated Exchange Act reports or revised exhibits (underwriting agreements, counsel opinions, consents, ATM sales agreements).

Under Securities Act Rule 462(e), a POSASR filed by a WKSI fund becomes effective immediately upon filing, with no SEC staff declaration required. This immediate effectiveness is the operative feature that distinguishes the POSASR submission type from other Form N-2 post-effective amendments.

Regulatory framework

POSASR sits at the intersection of three regimes:

  • Securities Act of 1933. Rule 415 authorizes delayed and continuous shelf offerings; Rule 405 defines WKSI; Rule 462(e) provides immediate effectiveness for WKSI automatic shelf amendments; Rule 413(b) permits registration of additional securities through a post-effective amendment; and Rule 415(a)(5) caps shelf life at three years.
  • Form N-2. General Instruction A.2 limits the form to closed-end management companies and BDCs. General Instruction B sets out the shelf and automatic shelf mechanics for these issuers, including the post-effective amendment process that POSASR implements.
  • Securities Offering Reform for Closed-End Funds (Release 33-10771, April 2020). This rulemaking extended WKSI status, automatic shelf registration, immediate effectiveness, and free writing prospectus eligibility to qualifying BDCs and closed-end funds. EDGAR Release 20.4 (February 2021) implemented the rulemaking by introducing the N-2 ASR and N-2 POSASR submission types, which is why the dataset begins in early 2021.

Important distinctions

  • POSASR vs POS 8C. Closed-end funds and BDCs that are not WKSIs, or whose shelf is non-automatic, file post-effective amendments as POS 8C under Section 8(c). Those amendments require SEC action and do not benefit from Rule 462(e) immediate effectiveness.
  • POSASR vs POSEX. POSEX is filed solely to add exhibits under Rule 462(d) and does not amend prospectus disclosure.
  • POSASR vs Rule 486 amendments. Interval funds and certain other closed-end funds use Rule 486 (POS 486APP, POS 486BPOS, POS 486IMM) for routine post-effective amendments. Rule 486 is a separate regime from automatic shelf and is not interchangeable with POSASR.
  • Fund POSASR vs corporate POSASR. The submission code "POSASR" is shared with operating-company automatic shelf amendments on Form S-3ASR or F-3ASR. This dataset contains only fund filings amending Form N-2 ASR registration statements; open-end funds (Form N-1A), unit investment trusts (Form N-8B-2), and operating companies are out of scope.

How This Dataset Differs From Similar Datasets or Filings

Form N-2 POSASR sits at a narrow intersection: post-effective amendments to automatic shelf registrations on Form N-2, filed by WKSI closed-end funds and BDCs. Confusion almost always arises along three axes — the underlying form (N-2 vs S-3), the shelf type (automatic vs traditional), and the filing's posture (pre-effective, post-effective, or prospectus-level). The comparisons below are organized around those axes.

Form POS 8C — the substantive twin

POS 8C is the comparison most likely to be conflated with N-2 POSASR. Both are post-effective amendments to Form N-2 covering closed-end funds and BDCs, and the document content (updated prospectus, refreshed financials, new exhibits) can look nearly identical.

The boundary is the shelf regime, not the content:

  • POS 8C amends a non-automatic N-2 shelf (filer is not a WKSI, or did not elect ASR treatment). Effectiveness is staff-controlled under Section 8(c) — typically requires an effectiveness order or acceleration request.
  • N-2 POSASR amends an automatic N-2 shelf. Effectiveness is immediate on filing under Rule 462(e).

EDGAR-feed signals that distinguish them: the literal submission-type string (POS 8C vs N-2 POSASR); the form type of the parent filing being amended (N-2 vs N-2 ASR); and the absence/presence of a downstream EFFECT notice. WKSI status of the registrant is the underlying economic driver.

Form N-2 ASR — the parent filing

The N-2 ASR is what a POSASR amends. ASR is the originating automatic shelf registration permitted by General Instruction A.2 of Form N-2 for WKSI funds; it goes effective on filing without staff review. POSASR is its amendment stream — never originating, narrower in scope, and used to keep the shelf current (Section 10(a)(3) refreshes, fundamental changes, adding classes of securities, exhibit updates).

Feed signal: ASR filings appear once per shelf cycle and define capacity; POSASRs appear repeatedly against that same file number.

Form N-2 MEF — Rule 462(b) capacity bumps

Both MEF and POSASR are immediately effective and follow-on, which causes confusion. The difference is mechanism and scope:

  • N-2 MEF is a one-shot Rule 462(b) registration of up to 20% additional securities of the same class already on the effective N-2, tied to a specific takedown that has outgrown the registered amount. Filings are short and mechanical.
  • N-2 POSASR is a continuous-amendment vehicle for any post-effective change to an automatic shelf — financial refreshes, new classes, base prospectus changes, exhibits.

Feed signal: MEF filings are short, single-purpose, and reference the specific class being topped up; POSASRs typically carry full or partial restated prospectuses.

Form N-2/A — pre-effective amendments

N-2/A is the pre-effective amendment used to respond to staff comments before a Form N-2 goes effective. The hard line vs POSASR is timing relative to effectiveness: N-2/A is filed before; POSASR is filed after. N-2/A is overwhelmingly associated with the staff-reviewed N-2 track; POSASR is exclusive to the WKSI ASR track that bypasses pre-effective review entirely. In a registration timeline, N-2/A clusters appear in the review window and disappear at effectiveness; POSASR only begins after effectiveness.

Form POSEX — exhibits-only amendments

POSEX is a post-effective amendment used only to add or update exhibits (e.g., underwriting agreement, legality opinion). It cannot alter prospectus disclosure. POSASR is broader: it can carry exhibits, but also full updated disclosure, new financial statements, additional classes, or take-down term changes. If exhibits are the sole purpose, registrants typically file POSEX rather than POSASR.

Feed signal: POSEX filings rarely include a primary prospectus document — the package is dominated by EX-99.(x) attachments. POSASRs frequently include a primary N-2 POSASR document plus exhibits.

Operating-company POSASR (S-3 ASR ecosystem)

EDGAR also uses the submission-type code POSASR (without the N-2 prefix) for post-effective amendments to Form S-3 automatic shelves filed by WKSI operating issuers. The structural logic — WKSI, immediate effectiveness, post-effective amendment to an automatic shelf — is identical, but everything else differs:

  • Underlying form: S-3 vs N-2.
  • Filer population: corporate operating issuers vs registered closed-end funds and BDCs.
  • Disclosure framework: Securities Act only vs Securities Act plus Investment Company Act items (senior securities table, N-2 fee table, BDC-specific items).

Critical filtering rule: dataset construction must key on the literal submission type N-2 POSASR, not the generic POSASR. Filtering on POSASR alone will sweep in the entire S-3 universe.

Form 497 / 497AD — prospectus-level filings

Rule 497 filings (497, 497AD, 497K, 497J) are how investment companies deliver prospectuses, prospectus supplements, stickers, and advertising materials after the registration is effective. The relationship to POSASR is complementary:

  • POSASR amends the registration statement itself — changes legal capacity, base disclosure, or exhibits.
  • 497 delivers the prospectus or supplement to investors for a specific takedown, sticker correction, or marketing piece, without modifying the underlying registration.

A live N-2 shelf typically generates a steady stream of 497 filings between sparser POSASR amendments. Researchers reconstructing offering activity need both. Feed signal: 497 filings name the prospectus or supplement; POSASR filings include a primary form document with cover page, signatures, and Part C.

Form N-CSR / N-CSRS — periodic shareholder reports

N-CSR (annual) and N-CSRS (semi-annual) are periodic Investment Company Act reports — audited or unaudited financial statements and management discussion. They share the registrant population with N-2 POSASR and the financial statements in a POSASR often align with the most recent N-CSR, but the function is unrelated:

  • N-CSR/N-CSRS are periodic, fiscal-period-driven, and never register securities.
  • N-2 POSASR is event-driven, Securities Act-driven, and exists to update an active securities registration.

Boundary summary

Form N-2 POSASR is uniquely defined by the intersection of five conditions, all of which must hold:

  1. Registrant is a closed-end fund or BDC (not an operating issuer — rules out S-3 POSASR).
  2. Registrant is a WKSI on the automatic shelf track (rules out POS 8C).
  3. The underlying registration is already effective (rules out N-2/A).
  4. The filing amends the registration statement itself (rules out 497 variants and N-CSR/N-CSRS).
  5. The filing scope is broader than exhibits-only and not constrained to a Rule 462(b) capacity bump (rules out POSEX and N-2 MEF).

The clean dataset filter is the literal EDGAR submission-type string N-2 POSASR (introduced in EDGAR Release 20.4, available from February 2021 onward). Related streams — N-2, N-2 ASR, N-2 MEF, N-2/A, POS 8C, POSEX, Form 497 variants, and N-CSR/N-CSRS — complement this dataset for full-lifecycle reconstruction of a fund's registration and offering activity, but none substitutes for the specific population of post-effective amendments to automatic N-2 shelves that N-2 POSASR captures.

Who Uses This Dataset

The user base is narrow and workflow-driven: each role targets specific sections of the amended prospectus, the fee and senior-securities tables, or the exhibits.

Investment-management and securities counsel

Outside counsel advising CEF and BDC issuers use the dataset as a precedent library when drafting POSASRs. They red-line peer cover pages, General Instruction B compliance language, plan-of-distribution sections, and incorporation-by-reference statements, and they pull legal-opinion exhibits (typically Exhibit (l)) and consents to build exhibit checklists. POSASR is the right source rather than the original N-2 because counsel need to see what registrants actually refile in amendments versus carry forward.

Fund compliance and registration officers

In-house disclosure and registration teams at fund complexes track how peers update shelves between takedowns. They mine amended risk factors, leverage and asset-coverage disclosure, conflicts-of-interest sections, and fee-and-expense tables to benchmark their own next amendment. Filing-date and CIK metadata feed peer-refresh calendars. POSASR specifically captures mid-shelf-life changes that N-2 and N-2/A do not.

Equity and debt capital markets bankers

Underwriting desks covering BDC and CEF takedowns use POSASR to confirm an issuer's automatic shelf is current and Instruction B-eligible before launching a deal. ECM reviews amended share-class disclosure, ATM program parameters, dilution language, and updated fee tables for common-stock takedowns; DCM focuses on the senior-securities table, indenture exhibits, asset-coverage covenants, and rate or refinancing risk factors for baby-bond and institutional note structures. POSASR is the trigger that signals shelf readiness, distinct from the underlying N-2.

Buy-side BDC and CEF analysts

Credit and equity analysts on dedicated BDC/CEF desks update coverage when an issuer files a POSASR. Credit analysts read the senior-securities coverage table, leverage limits, non-accrual and PIK disclosure, and concentration language. Equity analysts pull the management fee, incentive fee, total annual expenses, and any revised investment-strategy text to refresh NII and dividend-coverage models ahead of takedowns. POSASR carries the current fee and leverage parameters that subsequent prospectus supplements assume.

Closed-end fund arbitrage and fund-of-funds desks

Discount/NAV and CEF fund-of-funds desks use POSASR to anticipate dilution and supply overhang. They focus on the amended cover-page aggregate offering amount, ATM mechanics, share-issuance terms, and any language on issuance below NAV under 1940 Act constraints. The workflow drives position sizing and hedge ratios when new common or preferred capacity comes online.

Issuer IR and treasury teams

IR and treasury staff at CEF and BDC complexes benchmark peer POSASRs before their own amendments and investor days. They compare cover-page presentation, plan-of-distribution language, ATM disclosure, and the format of risk-factor updates. Filing-date metadata flags when comparable issuers refresh, helping anticipate questions from holders and rating analysts.

Regulatory and academic researchers

Regulator staff and researchers in asset management and corporate finance use the dataset to study automatic-shelf adoption among investment-company WKSIs. Because POSASR was introduced via EDGAR Release 20.4 and the dataset begins in February 2021, it offers a clean panel for measuring amendment cadence, takedown pacing, and longitudinal changes in fee structure and risk-factor catalogs. CIK and form-type metadata support issuer-level panels that the broader N-2 universe cannot isolate.

Data and fintech engineers

Engineers at filing-data vendors ingest POSASR into EDGAR pipelines that power prospectus-comparison tools, fee-table extractors, and shelf-tracking products. They wire metadata.json (accession, CIK, filing date, form type) into normalized schemas and parse the primary document and exhibit list for diff engines that surface changes across successive amendments. The dataset's tight scope makes it a clean test bed before scaling to full N-2 and N-2/A populations.

Quant and NLP researchers

Systematic shops use POSASR as a structured corpus for topic models, embedding similarity, and risk-factor classification on investment-company language. Extracted fee tables and senior-securities tables feed factor models incorporating cost and leverage variables. POSASR offers a homogeneous WKSI CEF/BDC slice rather than the noisier full N-2 set.

LLM and RAG developers

Teams building retrieval-augmented assistants for fund-management workflows chunk the amended prospectus and exhibits, embed them with CIK, filing-date, and form-type filters, and serve them into legal-research and analyst tools answering queries on leverage limits, ATM mechanics, and incentive-fee waterfalls grounded in current amended language.

Specific Use Cases

The use cases below are anchored in concrete record contents (metadata.json fields, the primary N-2 POSASR HTML body, and EX-99.(x) exhibits) and the post-effective, automatic-shelf scope that distinguishes POSASR from POS 8C, POSEX, MEF, and 497.

1. Building a BDC and CEF shelf-readiness monitor for ECM and DCM desks

Equity and debt capital markets bankers covering BDCs and listed closed-end funds run a daily ingest keyed on formType == "N-2 POSASR" and filedAt, joined to the issuer through entities[].cik and entities[].fileNo (333-). For each new POSASR, they read the cover page from the primary document for the updated aggregate offering amount and the plan-of-distribution section for at-the-market (ATM) agent and underwriter language. The output is a refreshed shelf-status board flagging which issuers can launch a takedown immediately under Rule 462(e), and which have just renewed capacity for follow-on common or baby-bond deals.

2. Drafting precedent library for fund counsel preparing the next POSASR

Outside counsel at investment-management practices index the primary N-2 POSASR HTML and the EX-99.(L) opinion-and-consent and EX-99.(N) auditor-consent exhibits across recent peer filings. When drafting a client's amendment, they red-line cover pages, General Instruction B legends, incorporation-by-reference statements, and the legality opinion against the freshest peer set. The output is an exhibit checklist plus draft language for the cover, signature page, and counsel opinion, sourced from filings actually accepted by EDGAR under the WKSI track rather than from older N-2 or N-2/A precedents.

3. Fee-table and senior-securities extraction for BDC credit and equity models

Buy-side BDC analysts parse the fee-and-expense table, hypothetical-investment expense example, and senior-securities coverage table from the primary document on each POSASR. Management fee, incentive fee, total annual expenses, and asset-coverage ratios feed NII, dividend-coverage, and leverage-headroom models. Because POSASR carries the current fee-table baseline that subsequent 497 prospectus supplements assume, the workflow re-anchors models the day amendments hit, ahead of the next takedown.

4. Diff engine for risk-factor and strategy drift across successive amendments

Fintech and data-vendor engineers chain POSASRs by entities[].cik and entities[].fileNo, then diff the risk-factor narrative, principal-strategy section, and leverage/asset-coverage disclosure between consecutive primary documents for the same shelf. The output is a change-log feed surfacing newly added risks (for example, valuation of Level 3 assets, RIC-qualification stress, BDC non-accrual language) that buy-side analysts and compliance teams subscribe to. The clean POSASR-only filter avoids the noise of pre-effective N-2/A clusters and exhibits-only POSEX filings.

5. CEF arbitrage dilution monitoring for ATM and below-NAV issuance

Closed-end fund arbitrage and fund-of-funds desks watch each POSASR for cover-page aggregate offering amounts, ATM mechanics, and any language on issuance below NAV under 1940 Act constraints. They size discount/NAV positions and hedge ratios based on the new common or preferred capacity disclosed in the amended plan-of-distribution and description-of-securities sections. The trigger is the POSASR filedAt timestamp; without it, supply overhang would only become visible at the 497 supplement stage, after the trade window has narrowed.

6. RAG assistants for fund leverage, ATM, and incentive-fee questions

LLM and RAG developers chunk the amended prospectus body and exhibits, attach accessionNo, entities[].cik, filedAt, and documentFormatFiles[].type as filter metadata, and serve the corpus into analyst and counsel-facing assistants. Queries such as "current asset-coverage covenant for issuer X" or "current ATM agent and commission for fund Y" resolve against the most recent POSASR's restated text, with linkToFilingDetails cited back to the user. The narrow WKSI CEF/BDC scope keeps retrieval grounded in actually-effective amendments instead of stale base prospectuses.

Compliance teams and researchers extract EX-99.(N) and EX-99.(L) from every POSASR to build a panel of which audit firms and law firms sign current consents for each WKSI fund complex. The exhibits are pulled by documentFormatFiles[].type matching "EX-99.(N)" or "EX-99.(L)", parsed for firm name and signing office, and joined to entities[].cik. The output is a service-provider league table and an early-warning signal when an issuer changes auditors or counsel between amendments.

8. Longitudinal panel of automatic-shelf adoption among investment-company WKSIs

Academic and regulator researchers build a CIK-by-month panel from formType, filedAt, effectivenessDate, and entities[].cik to study amendment cadence, fee-structure drift, and the diffusion of automatic-shelf use across CEFs and BDCs since EDGAR Release 20.4 in February 2021. Because POSASR is uniquely the post-effective amendment to an automatic N-2 shelf, the panel cleanly isolates the WKSI population that POS 8C, N-2/A, MEF, and 497 cannot, supporting event studies on Rule 462(e) takedowns and on rule changes to Item 25 fee-table presentation.

9. Filing-fee table extraction for shelf-capacity accounting

Treasury, IR, and capital-markets analytics teams pull the EX-FILING FEES / EX-99.(s) calculation-of-filing-fee exhibit (when present) to track registered-but-unsold capacity, paid filing fees, and Rule 457 offsets across the shelf life. Joined with N-2 ASR origination and N-2 MEF capacity bumps for the same fileNo, the result is a per-issuer shelf-capacity ledger that ECM uses to right-size the next takedown announcement and that IR uses to answer rating-analyst questions on remaining authorized capacity.

Dataset Access

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

This endpoint returns the dataset's metadata, the download URL for the full archive, and the list of all available container files with per-container size, record count, and last-updated timestamp. Use it to programmatically discover which yearly or monthly ZIP archives have been refreshed in the most recent run, so a downstream pipeline can pull only the containers that changed instead of re-downloading the entire dataset. This endpoint does not require an API key.

Example response:

Example
1 {
2 "datasetId": "1f13365b-9ae0-6a77-8d25-37d05e732ada",
3 "datasetDownloadUrl": "https://api.sec-api.io/datasets/form-n2-posasr-files.zip",
4 "name": "Form N-2 POSASR Files Dataset",
5 "updatedAt": "2026-04-28T02:51:19.000Z",
6 "earliestSampleDate": "2024-12-23",
7 "totalRecords": 33,
8 "totalSize": 580023,
9 "formTypes": ["N-2 POSASR"],
10 "containerFormat": "ZIP",
11 "fileTypes": ["HTML", "JSON"],
12 "containers": [
13 {
14 "downloadUrl": "https://api.sec-api.io/datasets/form-n2-posasr-files/2026/2026-03.zip",
15 "key": "2026/2026-03.zip",
16 "size": 48217,
17 "records": 3,
18 "updatedAt": "2026-03-31T22:14:08.000Z"
19 }
20 ]
21 }

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

Downloads the complete dataset as a single ZIP archive. The full archive can be retrieved in one request and re-downloaded periodically. This endpoint requires an API key.

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

Each container in the containers array can be downloaded individually using its downloadUrl. Containers are organized as year-level archives (for example 2024.zip, 2025.zip) for fully closed periods and as year-month archives (for example 2026/2026-03.zip) for the current year. Inside every ZIP, records are laid out as one folder per filing, named by accession number, containing a metadata.json file with structured filing data and the SGML-wrapped HTML documents from the original submission. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers EDGAR submissions of form type N-2 POSASR — post-effective amendments to automatic shelf registration statements filed on Form N-2 by WKSI closed-end funds and BDCs. The literal EDGAR submission-type string N-2 POSASR is the canonical filter; the generic POSASR code without the N-2 prefix corresponds to operating-company S-3 amendments and is out of scope.

What does one record in the Form N-2 POSASR Files dataset represent?

One record is a single accession-numbered EDGAR submission of form type N-2 POSASR, materialized on disk as a folder named with the accession number (hyphens stripped). Each folder contains a metadata.json capturing EDGAR's structured filing header and the original SGML-wrapped .htm documents — the primary N-2 POSASR document plus its EX-99.(x) exhibits.

Who is required to file Form N-2 POSASR?

The legal filer is the registrant: a closed-end management investment company or a business development company that maintains an effective Form N-2 automatic shelf registration and qualifies as a WKSI under Rule 405 at the time of filing. Underwriters, sales agents, and selling securityholders may appear in the amended prospectus but do not file the POSASR themselves.

What time period does the Form N-2 POSASR Files dataset cover?

Coverage begins on February 1, 2021, when EDGAR Release 20.4 introduced the dedicated N-2 POSASR submission type alongside the 2020 Securities Offering Reform for Closed-End Funds. Before that date, post-effective amendments to N-2 automatic shelves were filed under generic post-effective-amendment codes and are not separately identifiable as POSASR-on-N-2.

When does an N-2 POSASR become effective?

Under Securities Act Rule 462(e), a POSASR filed by a WKSI fund becomes effective immediately upon filing, with no SEC staff declaration required. As a result, effectivenessDate in metadata.json ordinarily equals the calendar date of filedAt.

How does this dataset differ from Form POS 8C?

Both POS 8C and N-2 POSASR are post-effective amendments to Form N-2 covering closed-end funds and BDCs, and the document content can look nearly identical. The boundary is the shelf regime: POS 8C amends a non-automatic N-2 shelf and requires staff-controlled effectiveness under Section 8(c), while N-2 POSASR amends an automatic N-2 shelf filed by a WKSI and is immediately effective under Rule 462(e).

What file format is the dataset distributed in?

The dataset is delivered as ZIP archives organized by calendar year and year-month, addressed at paths of the form YYYY/YYYY-MM.zip. Inside each archive, every accession folder contains a metadata.json (JSON) and one or more .htm files wrapped in EDGAR's standard SGML envelope; GRAPHIC image binaries and the consolidated complete-submission .txt SGML bundle are referenced in metadata.json but not bundled locally.