Form 486BPOS Files Dataset

The Form 486BPOS Files dataset is a complete archive of post-effective amendments to registration statements filed on EDGAR by registered closed-end management investment companies and business development companies (BDCs) under Rule 486(b) of the Securities Act of 1933. Each record is a single EDGAR submission of Form 486BPOS — a refreshed Form N-2 registration statement (cover page, prospectus, statement of additional information, and exhibits) — packaged as a self-contained accession-level folder with the registrant-supplied documents and a normalized metadata.json sidecar parsed from the SGML submission header. These amendments become effective immediately upon filing or on a registrant-designated date within thirty days, and are used to register additional shares, roll forward audited financial statements, refresh fee tables, or make non-material disclosure updates. The dataset covers all Form 486BPOS filings from April 1994, when EDGAR began accepting these submissions electronically following adoption of Rule 486, through the present, and is distributed as monthly ZIP containers carrying TXT, JSON, and HTML files.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset captures every Form 486BPOS filing accepted by EDGAR since April 1994. Form 486BPOS is a post-effective amendment to a registration statement filed by a closed-end management investment company or a business development company under Rule 486(b) of the Securities Act of 1933. The "B" in the form code refers to Rule 486(b), which permits these amendments to become effective immediately upon filing or on a registrant-designated date within thirty days, provided the changes are confined to the rule's permitted purposes: registering additional shares, updating financial statements, reflecting changes that the registrant certifies are not material, or making other non-material amendments to the prospectus and statement of additional information.

Substantively, the amendment is a refreshed registration statement on Form N-2 (the long-form registration form for closed-end funds and BDCs). It carries forward the full Form N-2 information architecture — cover page, prospectus, statement of additional information (SAI), and exhibits — but is filed against a previously effective registration, typically to roll forward the audited financial statements, restate the fee table, update portfolio-management or investment-policy disclosures, or register additional shares pursuant to a continuous offering, dividend reinvestment plan, or shelf takedown. Because Rule 486(b) limits permissible changes to non-material updates and enumerated administrative items, the document is functionally an annual or interim refresh rather than a fundamental restatement.

The submission is dual-tracked under both the Securities Act of 1933 (registration of securities, file-number prefix 333-) and, for the registrant entity itself, the Investment Company Act of 1940 (file-number prefix 811-). Both file numbers and both Act codes typically appear in the entity block of the metadata. The dataset is distributed as monthly ZIP containers grouped by filing/effectiveness date; inside each archive a single YYYY-MM/ folder sits at the root and each filing lives in its own subfolder named with the dash-stripped accession number (for example, 0001104659-25-093946 becomes 000110465925093946). Document filenames inside the folder are preserved exactly as the registrant submitted them.

Content Structure of a Single Record

One record in the Form 486BPOS Files dataset is a single EDGAR submission of Form 486BPOS, identified by its accession number and packaged as a self-contained accession-level folder. The record is a faithful, accession-level mirror of the post-effective amendment as it sits on EDGAR, minus image attachments and standalone XBRL technical files, plus a parsed metadata sidecar.

Each record consists of two structural layers:

1. A metadata.json file at the root of the accession folder, a normalized projection of the EDGAR <SEC-HEADER> envelope enriched with direct URLs back to the canonical documents on sec.gov.
2. The set of HTML documents the registrant filed: the primary 486BPOS document (an inline-XBRL prospectus/registration statement) and one or more exhibit documents (each an SGML-wrapped HTML fragment).

Image files (the GRAPHIC document type on EDGAR) and the standalone XBRL technical files — the EX-101.SCH taxonomy schema, the EX-101.DEF, EX-101.LAB, and EX-101.PRE linkbases, and the extracted *_htm.xml instance — are not packaged inside the record folder. They are listed by URL in metadata.json but excluded from the ZIP payload, because images are excluded by dataset policy and the inline-XBRL facts are already embedded in the primary HTM document.

metadata.json

The metadata.json file carries the parsed submission header and a structured manifest of all documents filed under the accession. Recurring fields:

• formType — always "486BPOS".
• accessionNo — the dashed EDGAR accession number.
• effectivenessDate — the YYYY-MM-DD date on which the post-effective amendment becomes effective. For Rule 486(b) filings this is normally the filing date itself or a registrant-designated date within thirty days.
• filedAt — ISO-8601 timestamp with timezone offset for EDGAR receipt.
• description — the human-readable form name, typically "Form 486BPOS - Post-effective amendment [Rule 485(b)]".
• linkToFilingDetails — URL to the primary 486BPOS document on sec.gov, often surfaced through the inline-XBRL viewer (ix?doc=).
• linkToTxt — URL to the complete SGML submission .txt file on EDGAR.
• linkToHtml — URL to the EDGAR filing-index page.
• linkToXbrl — URL to a separate XBRL instance when one exists; commonly empty because 486BPOS uses inline XBRL embedded in the primary HTM.
• id — an opaque hex identifier for the record.
• documentFormatFiles[] — one entry per registrant-attached document, with sequence, size in bytes (as a string), type (the SGML <TYPE> value, such as 486BPOS, EX-99.(L)(2), EX-99.(N)(1), EX-99.25, or GRAPHIC), description, and documentUrl. The trailing entry, with empty type and sequence, points at the complete .txt submission.
• dataFiles[] — entries for the XBRL technical files associated with the submission: EX-101.SCH (taxonomy schema), EX-101.DEF (definition linkbase), EX-101.LAB (label linkbase), EX-101.PRE (presentation linkbase), and the extracted XML instance (*_htm.xml). Same field shape as documentFormatFiles[].
• entities[] — one entry per filer/registrant role on the submission, each carrying companyName (with role suffix such as (Filer)), cik, fileNo, irsNo, fiscalYearEnd (MMDD), stateOfIncorporation, act (the relevant federal act number, typically "33" or "40"), type (the entity-level form type), filmNo, and an optional tickers[] array. Closed-end funds and BDCs typically appear with two entries — one under the 1940 Act with an 811-… file number, and one under the 1933 Act with a 333-… registration number.
• seriesAndClassesContractsInformation[] — populated only when the submission supplies EDGAR series/class metadata; otherwise an empty array.

Primary 486BPOS document (inline-XBRL HTML)

The single document keyed type: "486BPOS" (with sequence: "1") is the post-effective amendment itself. It is authored as inline XBRL: a self-contained .htm file that is simultaneously a human-readable prospectus and a machine-readable XBRL instance. The file opens with an XML prologue and an <html> root that declares the inline XBRL namespace (http://www.xbrl.org/2013/inlineXBRL), the DEI taxonomy (xbrl.sec.gov/dei/...), the closed-end fund taxonomy (xbrl.sec.gov/cef/...), and the relevant US-GAAP namespace. An <ix:header> block follows, carrying <ix:hidden> document-and-entity facts, <ix:references> pointing at the schema reference, and an <ix:resources> block containing xbrli:context and xbrli:unit definitions. The body of the document is the rendered prospectus and SAI, with tagged facts marked up as <ix:nonNumeric>, <ix:nonFraction>, and <ix:footnote> elements interleaved with the visible text.

The narrative content follows the Form N-2 information architecture and typically contains, in order:

• A facing page / cover page identifying the registrant, both file numbers (333-… under the 1933 Act and 811-… under the 1940 Act), the title and amount of securities being registered, the proposed maximum offering price, and the Rule 486(b) checkbox indicating the basis for effectiveness (immediate vs. designated effective date).
• The prospectus, including the summary, the fee table and expense example, the financial highlights, the description of the fund's investment objectives and principal investment strategies, principal risk factors, management of the fund (investment adviser, sub-advisers, and portfolio managers), description of capital structure and the offered shares, distributions and the dividend reinvestment plan, plan of distribution, custody and transfer agency arrangements, and tax disclosures.
• The statement of additional information, expanding on investment policies and restrictions, trustee and officer biographies and compensation, control persons and principal holders, investment advisory and other services, brokerage allocation, portfolio holdings disclosure policies, and additional tax information.
• The financial statements section, frequently incorporated by reference from the registrant's most recent annual report on Form N-CSR but with updated audited or interim figures attached or restated when the amendment exists to bring financials current.
• The Closed-End Fund (cef:) tagged facts required by the SEC's structured-data rules for closed-end fund and BDC registration statements, covering fee-table elements, share-price-history tables, senior-securities tables, and investment-objective disclosures.
• Signature pages for the registrant, its trustees/directors, and its principal officers, followed by the exhibit index referencing each separately filed exhibit.

These primary files are typically several megabytes in size because they embed the full prospectus and SAI together with the XBRL markup.

Exhibit documents (SGML-wrapped HTML)

Every other .htm file in the accession folder is an exhibit. Each exhibit retains the original EDGAR SGML document wrapper at the top of the file:

          1
          <DOCUMENT>
        

          2
          <TYPE>EX-99.(N)(1)
        

          3
          <SEQUENCE>3
        

          4
          <FILENAME>tm2526916d3_ex99-xnx1.htm
        

          5
          <DESCRIPTION>EXHIBIT 99.(N)(1)
        

          6
          <TEXT>
        

          7
          <HTML> ... rendered exhibit body ... </HTML>
        

          8
          </TEXT>
        

          9
          </DOCUMENT>
        

The wrapper preserves the logical document metadata — type, sequence, filename, and description — exactly as EDGAR received it. Beneath the <TEXT> marker is the rendered exhibit as plain HTML, often ending with a signature or attestation block.

The exhibit-type vocabulary on Form 486BPOS follows the Form N-2 exhibit lettering scheme, which uses parenthesized lowercase letters (a)–(s) keyed to specific exhibit categories. Exhibit types found in the dataset include:

• EX-99.(G)(...) — custodian and sub-custodian agreements and amendments.
• EX-99.(L)(...) — opinion and consent of counsel as to the legality of the securities being registered.
• EX-99.(N)(...) — consent of the independent registered public accounting firm authorizing reference to its audit report and use of its name in the prospectus and SAI. These are typically short one-paragraph letters that name the post-effective amendment number and the 333-… file number explicitly.
• EX-99.(R)(...) — codes of ethics adopted by the fund, the adviser, and any sub-advisers under Rule 17j-1 of the 1940 Act.
• EX-99.25 and other 25-series exhibits — supporting documents such as forms of extension request under fund credit facilities or other ancillary filings tied to the fund's continuous-offering machinery.

Each exhibit is structurally independent and self-contained.

Included content

A record contains the parsed metadata.json plus every non-image document the registrant filed under that accession: the primary inline-XBRL 486BPOS HTM document and the full set of exhibit HTM documents.

Excluded or separate content

Two categories of content exist on EDGAR but are not packaged inside the record folder:

• Image files (EDGAR GRAPHIC documents) referenced by the prospectus — fund logos, performance charts, organizational diagrams. These are listed by URL in documentFormatFiles[] but excluded from the ZIP payload by dataset policy.
• The standalone XBRL technical files — the taxonomy schema (EX-101.SCH), the definition, label, and presentation linkbases (EX-101.DEF, EX-101.LAB, EX-101.PRE), and the extracted XBRL instance (*_htm.xml). These are referenced by URL in dataFiles[] but not duplicated inside the ZIP, because the same XBRL facts are already embedded inline in the primary 486BPOS HTM file.

The complete .txt SGML submission envelope (which concatenates all documents) is referenced by URL through linkToTxt but not duplicated inside the folder; the constituent documents are unpacked instead.

Changes in required content over time

Form 486BPOS has retained its core role since the adoption of Rule 486(b) in 1995, but the required content of the underlying Form N-2 registration statement carried by these post-effective amendments has evolved meaningfully:

• The 2020 amendments to the Form N-2 offering process (which streamlined shelf offerings, introduced WKSI-style benefits for closed-end funds and BDCs, and made BDCs eligible to register on Form N-2 and rely on Rule 486(b)) expanded the registrant population in this dataset and reshaped cover-page content and the structure of the fee table.
• The 2020 fund-of-funds rule (Rule 12d1-4) and the derivatives rule (Rule 18f-4) introduced new disclosure expectations that surface in updated risk-factor and investment-policy sections of post-effective amendments filed thereafter.
• The SEC's 2022 adoption of structured-data requirements for closed-end fund and BDC registration statements introduced the cef: taxonomy, requiring the prospectus and SAI to carry inline-XBRL tags for cover-page items, fee-table line items, senior-securities tables, share-price-history tables, and other defined disclosure elements. From the compliance dates of that rule forward, the primary 486BPOS HTM document is consistently authored as inline XBRL with cef:, dei:, and us-gaap: namespaces declared at the root.
• Periodic refreshes of the DEI taxonomy and the Form N-2 instructions have continued to adjust cover-page content, the structure of the fee table, and the use of free-writing prospectuses referenced in the amendment.

Changes in data format over time

Form 486BPOS submissions have moved through three broad presentation eras since 1994:

• An early ASCII/SGML era in which the primary document and exhibits were filed as plain-text documents inside the SGML submission envelope, with tabular content formatted using fixed-width spacing.
• An HTML era beginning in the early 2000s, in which the primary document and exhibits were filed as HTML inside the same SGML wrapper, retaining the <DOCUMENT>/<TYPE>/<SEQUENCE>/<FILENAME>/<DESCRIPTION>/<TEXT> header structure that is still visible in exhibit files today.
• An inline-XBRL era for the primary 486BPOS document, following the SEC's structured-data rule for closed-end fund and BDC registration statements. In this era the principal HTM file is simultaneously a human-readable prospectus and a machine-readable XBRL instance, with iXBRL tags interleaved in the body and an <ix:header> block at the top.

Exhibit documents have remained as SGML-wrapped HTML throughout the HTML and inline-XBRL eras; only the primary 486BPOS document carries inline XBRL.

Interpretation notes

• The metadata.json sidecar is the most reliable place to identify the registrant, its CIK, both file numbers (333-… under the 1933 Act and 811-… under the 1940 Act), the effectiveness date, and the full list of documents that originally accompanied the submission, including those (images and standalone XBRL technical files) that are not bundled into the ZIP.
• A fund will frequently appear under two entities[] records — one for its 1933 Act registration and one for its 1940 Act company-act registration. Both refer to the same legal entity; deduplicate by CIK when modeling the registrant.
• Inline XBRL facts in the primary HTM document are authoritative for cover-page items, fee-table values, and the structured CEF disclosures. Where the same fact appears in narrative form and as an iXBRL tag, the tagged value is the structured representation and is generally more reliable to extract than the surrounding prose.
• Many financial statements referenced in a 486BPOS prospectus are incorporated by reference from the registrant's most recent annual report on Form N-CSR rather than reprinted in full inside the amendment. The narrative will indicate the incorporation rather than reproduce the statements.
• The EX-99.(N) consent letter typically names the post-effective amendment number explicitly (for example, "Post-Effective Amendment No. 12 to the Registration Statement"), which can be used to anchor the amendment in the registrant's series of post-effective filings.
• The Rule 486(b) checkbox on the cover page distinguishes amendments that are immediately effective from those designated to become effective on a date within thirty days; the effectivenessDate field captures the resulting effective date but does not itself indicate whether immediate or delayed effectiveness was elected.
• Exhibit type strings preserve the parenthesized Form N-2 lettering (for example, EX-99.(L)(2), EX-99.(N)(1), EX-99.(G)(5)(A)). The mapping from letter to exhibit category follows the Form N-2 instructions and is stable across the dataset.
• The SGML wrapper preserved at the top of each exhibit file means an extractor must either parse the <DOCUMENT> envelope (to read <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>) or skip past the <TEXT> marker before feeding the body to a standard HTML parser.
• The dataset's monthly partitioning is keyed to the filing/effectiveness month, so locating a record requires knowing the accession month rather than the registrant's fiscal year.

Who Files or Publishes This Dataset, and When

Each record in this dataset is a single Form 486BPOS submission filed on EDGAR by a registered investment company. The filer is the registrant itself, acting through its officers and its board of trustees or directors. The filing population is narrow:

• Registered closed-end management investment companies registered under the Investment Company Act of 1940 with shares registered on Form N-2 under the Securities Act of 1933. In practice this is dominated by interval funds (relying on Section 23(c)(2) and Rule 23c-3) and tender offer funds that conduct continuous or delayed offerings under Rule 415.
• Business development companies (BDCs) that have elected BDC status under Section 54 of the Investment Company Act and that register their securities on Form N-2.

Both categories share the trait that distinguishes them from one-shot issuers: their N-2 registration statements remain alive across multiple offering periods and require periodic updating. Open-end funds and ETFs (Form N-1A registrants), unit investment trusts, and operating-company issuers do not file Form 486BPOS.

What triggers a filing

A Form 486BPOS is filed when a closed-end fund or BDC needs to update an effective N-2 registration statement and the changes qualify for immediate effectiveness under Rule 486(b) of the Securities Act of 1933. Rule 486(b) limits eligible content to enumerated non-material categories. Typical triggers:

• Annual update to incorporate audited financial statements once available, keeping the prospectus and SAI current under Section 10(a)(3) of the Securities Act.
• Registration of additional shares to add capacity to an existing continuous offering.
• Refreshed fee tables, expense ratios, and management fee disclosures reflecting current operating data.
• Non-material revisions to investment objectives, principal strategies, portfolio managers, trustees or directors, or distribution arrangements.
• Designation of a future effective date within thirty days of filing, as permitted by Rule 486(b).

Material changes — a fundamental change in investment policy, a new class of securities raising novel disclosure issues, or any content outside Rule 486(b)'s enumerated categories — cannot ride on 486BPOS and must instead be filed on Form 486APOS under Rule 486(a), which is subject to staff review and delayed effectiveness.

Effectiveness and timing

A 486BPOS becomes effective automatically, either immediately on filing or on a registrant-designated date within thirty days. There is no acceleration request and no Commission action required. Cadence is largely annual, driven by each fund's fiscal year end and the Section 10(a)(3) staleness window, with additional filings made during the year as share capacity or other non-material updates are needed. Active issuers may file several per year. The dataset begins in April 1994, when EDGAR began accepting these filings electronically following adoption of Rule 486.

Regulatory framework

Form 486BPOS sits at the intersection of two regimes:

• Securities Act of 1933: governs the underlying N-2 registration and the effectiveness mechanics of post-effective amendments. Rule 486 was adopted to give continuously offered closed-end funds and BDCs a streamlined updating path comparable to the Rule 485 regime for open-end funds. Rule 486(b) provides automatic effectiveness for amendments confined to enumerated non-material content.
• Investment Company Act of 1940: governs the filer's status as a registered investment company or BDC and the substantive requirements (Section 23(c)(2) repurchase mechanics, Section 18 leverage limits, Section 17 affiliate rules, Section 30 reporting) that the amended disclosure must reflect.

The form itself is a cover-page wrapper; the substantive document is the amended N-2, including the prospectus, statement of additional information, and exhibits. It must be signed by the registrant, its principal executive officer, principal financial officer, principal accounting officer, and a majority of the trustees or directors, with certifications that the amendment contains no material misstatements or omissions and meets the conditions of Rule 486(b).

Important distinctions

• 486BPOS vs. 486APOS: Both are post-effective amendments to a closed-end fund or BDC N-2. 486BPOS is the immediately effective Rule 486(b) version for non-material updates; 486APOS is the staff-reviewed Rule 486(a) version for material changes.
• 486BPOS vs. 485BPOS: 485BPOS is filed by open-end funds and ETFs (Form N-1A) under Rule 485(b); 486BPOS is filed by closed-end funds and BDCs (Form N-2) under Rule 486(b).
• 486BPOS vs. POS 8C and other post-effective amendment types: Closed-end funds amending outside the Rule 486 framework use POS 8C (Section 8(c) of the Securities Act) or other post-effective amendment form types, not 486BPOS.
• Amendments to a 486BPOS: Corrections or further updates are filed as 486BPOS/A.
• Series and master-feeder structures: The registrant on the cover page is the legal entity (trust or corporation), not an individual series or feeder; CIK and filer identification reflect that entity.
• Eligibility conditions: Rule 486(b) is available only to registrants that are current in their Investment Company Act reporting and otherwise meet the rule's conditions. A fund out of compliance must use Rule 486(a) even for an otherwise non-material update.

How This Dataset Differs From Similar Datasets or Filings

Form 486BPOS sits in a narrow corner of the investment-company registration regime: post-effective amendments to Form N-2 registrations filed by closed-end funds and business development companies (BDCs) under Rule 486(b). The most useful comparisons are the other Rule 486 variant, the parallel Rule 485 family used by open-end funds, the Form N-2 lineage that 486BPOS amends, the periodic N-CSR shareholder report, and the general-purpose POS AM amendment.

Form 486APOS

The direct counterpart within Rule 486. Same filers, same underlying N-2, same purpose of amending an effective registration. The split is by rule paragraph: 486APOS is filed under Rule 486(a) for material changes requiring SEC review and a delayed effective date; 486BPOS is filed under Rule 486(b) for non-material updates, share top-ups, and routine annual refreshes that take effect immediately or within thirty days. 486APOS captures substantive policy or structural change; 486BPOS captures the recurring update cycle. The two are complementary, not substitutable.

Form 485BPOS

The open-end fund analogue, filed under Rule 485(b) and amending Form N-1A rather than Form N-2. Filing structure is similar (updated prospectus, SAI, exhibits; immediate or near-immediate effectiveness), but the filer population is disjoint: 485BPOS covers mutual funds and most ETFs and contains no closed-end fund or BDC content. Volume is far higher than 486BPOS, but interval funds, tender-offer funds, listed closed-end funds, and BDCs do not appear there.

Form 485APOS

The material-change variant of 485BPOS, filed under Rule 485(a) by open-end funds. Differs from 486BPOS on both axes (open-end vs. closed-end; material vs. non-material). Useful only as a structural analogue for understanding the A/B distinction; no content overlap.

Form N-2

The initial registration statement that 486BPOS amends. N-2 establishes the baseline (investment objectives, fundamental policies, fee structure, capital structure, board, initial prospectus); 486BPOS supplies subsequent non-material updates. Every 486BPOS exists relative to a previously effective N-2. For longitudinal analysis, N-2 is the initial state and 486BPOS is the running diff.

Form N-2/A

A pre-effective amendment to N-2, used to respond to staff comments or registrant changes before the registration goes effective. 486BPOS is exclusively post-effective. The two occupy adjacent but non-overlapping stages: N-2/A in the pre-effectiveness review phase, 486BPOS in the post-effective maintenance phase.

Form N-CSR

The certified annual or semi-annual shareholder report under the Investment Company Act. Same issuer universe as 486BPOS and superficially overlapping financial content, but a different regime and audience. N-CSR is shareholder-facing periodic reporting: audited or unaudited financials, full schedule of investments, MD&A, proxy voting policies. 486BPOS is a Securities Act registration document aimed at prospective investors: current prospectus, fee tables, risk factors, SAI. Use N-CSR for portfolio holdings and historical performance; use 486BPOS for the offering terms and policies in force at the time of sale.

Form POS AM

The general-purpose post-effective amendment used by operating-company registrants amending S-1, S-3, S-11, or F-series filings, and by investment companies that cannot rely on Rule 485 or Rule 486. Same broad function (amending an effective registration), but outside the Rule 485/486 streamlined framework and without the same automatic effectiveness. For closed-end funds and BDCs operating under Rule 486, 486BPOS replaces POS AM as the routine update mechanism. Filer populations are largely disjoint.

Boundary summary

Form 486BPOS uniquely captures the routine, immediately-effective post-effective amendments of closed-end funds and BDCs operating under Rule 486(b). It is narrower than N-2 (initial registration), distinct from 486APOS (material changes requiring review), separate from 485BPOS/485APOS (open-end fund regime), outside the scope of N-CSR (periodic shareholder reporting), and not interchangeable with POS AM (operating-company amendments). For tracking how a closed-end fund's prospectus, fees, share count, or risk disclosures evolve between the initial N-2 and any material-change 486APOS, 486BPOS is the canonical and only source.

Who Uses This Dataset

The records that matter most across user types are the amended prospectus, the SAI, fee tables, leverage and distribution disclosures, Rule 486(b) certifications, and the exhibit set.

CEF and BDC research analysts

Sell-side and buy-side analysts use 486BPOS as the source for incremental changes between full N-2 cycles. They track financial highlights, modifications to investment objectives and leverage limits, fee waiver expirations, and managed-distribution policy changes to update NII forecasts, share-count and dilution assumptions, and discount-to-NAV models. The SAI is pulled for fundamental policies, concentration limits, and borrowing terms.

Fund-of-fund and wealth-platform diligence teams

Manager-research and product-approval staff at fund-of-funds, wirehouses, RIA platforms, and trust departments use amendments to keep approved-product lists current. They monitor fee-table revisions, expense-cap changes, distribution and servicing arrangements, portfolio-manager bios, and conflict disclosures, flagging items that require investment-committee re-review and refreshing due-diligence files with the latest prospectus and SAI.

CEF and BDC specialty traders and income desks

Discount-capture, arbitrage, and tactical-income desks read 486BPOS to anticipate supply, leverage, and payout changes that move secondary prices. They focus on share-registration amounts on the cover page, senior-securities issuance authority, managed-distribution policy revisions, and rate or credit sensitivity disclosures to position ahead of effective dates that often coincide with shelf takedowns or ATM activity.

Investment-management lawyers and disclosure counsel

Fund counsel use the dataset as a precedent corpus for drafting Rule 486(b)-compliant amendments. They examine 486(b) certification language, cover-page legends, descriptions of non-material changes, Item 3 fee-table formatting, and exhibit lists (legal opinions, accountant consents, amended underwriting agreements) to advise sponsors on whether a contemplated change qualifies for immediate effectiveness or requires a 486(a) filing.

Fund-sponsor compliance officers

CCOs and registration-statement coordinators benchmark their filing cadence and content against peers. They study what other complexes treat as "non-material," timing between board approval and effective date, and the use of post-effective amendments versus annual N-CSR to refresh financials, building defensible filing calendars and board materials.

CEF and BDC ratings analysts

Credit and fund-rating analysts covering BDC debt, CEF preferred shares, and structured fund obligations refresh views using updated leverage and asset-coverage disclosures, investment-policy changes affecting collateral quality, dividend-priority modifications, and debt covenants in exhibits. Output feeds rating committee memos, surveillance, and asset-coverage ratios stress tests.

Fund fee and expense analysts

Specialists benchmarking advisory fees, incentive-fee waterfalls (especially BDCs), interest expense from leverage, acquired-fund fees, and expense-limitation agreements treat the amended fee tables as primary source data for peer-group expense studies and long-run panels tracking fee evolution across amendments.

Regulatory data vendors and financial data engineers

Vendors and in-house engineers ingest 486BPOS filings to maintain prospectus, fee, and policy databases. They use structured metadata (accession number, filer ID, effective date, exhibit index) and the HTML/TXT documents to build diff extractors across successive amendments, normalize fee-table line items, and feed cleaned text into search and RAG pipelines.

Academic researchers in finance, accounting, and law

Researchers studying CEF discounts, BDC leverage cycles, fee dispersion, disclosure readability, and the economics of Rule 486(b) use the archive back to 1994 for event studies, textual-similarity work, and policy analysis on amendment frequency, prospectus language, and secondary-market pricing.

SEC examination, enforcement, and rulemaking staff

Investment-management exam and enforcement staff, along with rule-writing economists, use 486BPOS records to review individual registrants and industry practice. They focus on certifications, consistency between disclosed changes and contemporaneous board or marketing materials, borderline-material uses of 486(b), and repeat-amendment patterns to support sweeps and economic analysis behind potential N-2 and Rule 486 amendments.

LLM and RAG developers for fund documents

Teams building retrieval systems for investment-management workflows use the corpus to chunk and embed prospectus, SAI, and fee-table text, with metadata tags for filer, date, and document type. The dataset supports analyst copilots that summarize amendment-to-amendment changes and surface peer comparisons on fees, leverage, and policy.

Specific Use Cases

The Form 486BPOS Files dataset supports a focused set of workflows around closed-end fund and BDC registration maintenance. Each record exposes the inline-XBRL prospectus, the SAI, the exhibit set, and a metadata.json sidecar with both 333- and 811- file numbers, an effectiveness date, and a full document manifest.

Tracking fee-table evolution across amendments

Pull the inline-XBRL cef: fee-table facts from successive 486BPOS amendments for the same CIK to build a longitudinal panel of advisory fees, incentive-fee waterfalls, interest expense from leverage, acquired-fund fees, and expense-cap waivers. Aligning amendments by effectivenessDate produces a clean per-fund time series that drives peer-expense benchmarking, total-cost-of-ownership comparisons, and dilution adjustments to NII forecasts.

Monitoring share-registration top-ups and shelf capacity

Parse the cover page and cef: cover-page tags to extract the title and amount of securities being registered on each post-effective amendment. Combined with the 333- file number from entities[], this yields a running registration-capacity ledger by fund — used by trading desks to anticipate ATM activity and shelf takedowns, and by analysts modeling potential dilution against current discount-to-NAV.

Building a Rule 486(b) precedent corpus for fund counsel

Index the 486(b) certification language, cover-page legends, and descriptions of non-material changes across the dataset to produce a searchable precedent base. Counsel queries it to find comparable phrasings for borderline changes (managed-distribution-plan tweaks, sub-adviser additions, leverage-limit adjustments) and to decide whether a contemplated update qualifies for immediate effectiveness under 486(b) or must be filed as 486APOS.

Surveillance of BDC and CEF leverage and asset coverage

Extract senior-securities-table facts and updated borrowing, preferred-share, and notes-payable disclosures from the prospectus and SAI to refresh asset-coverage ratios and covenant headroom for rating-committee memos. Custodian and credit-facility exhibits under EX-99.(G) and the 25-series provide the underlying agreement terms for stress tests on BDC debt and CEF preferred shares.

Diff extraction for amendment-to-amendment change detection

Use metadata.json to pair consecutive 486BPOS accessions for the same registrant, then run text and tagged-fact diffs across the primary HTM document to identify changes in investment objectives, principal risk factors, portfolio-manager bios, distribution policy, and fundamental policies. The output feeds analyst alerts, manager-research re-review queues at wealth platforms, and structured change logs in vendor prospectus databases.

Exhibit-driven mapping of fund service providers

Walk documentFormatFiles[] to enumerate EX-99.(G) custodian agreements, EX-99.(L) legality opinions, EX-99.(N) auditor consents, and EX-99.(R) codes of ethics across the dataset. Joining the parsed exhibit headers to the registrant CIK produces a fund-by-fund directory of custodians, outside counsel, audit firms, and adviser/sub-adviser ethics regimes, useful for vendor-market sizing and conflict checks.

RAG and copilot grounding on current offering terms

Chunk the inline-XBRL prospectus and SAI text by Form N-2 section, attach metadata for CIK, ticker, effectivenessDate, and exhibit type, and embed for retrieval. The resulting index powers analyst copilots that answer questions about the fee table, leverage limits, distribution mechanics, and risk language as currently in force at the point of sale, anchored to the specific 486BPOS accession that established each disclosure.

Dataset Access

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

This endpoint returns the dataset's metadata, including the name, description, last update timestamp, earliest sample date, total record count, total size, covered form types, container format, and content file types. It also includes the download URL for the entire dataset and a list of all individual container files with per-container metadata such as size, record count, last updated timestamp, and download URL. The endpoint can be polled regularly to detect which containers were updated in the most recent refresh run, allowing selective downloads of only the containers that changed.

This endpoint does not require an API key.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-698c-8e0c-176adf142aaa",
        

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

          4
            "name": "Form 486BPOS Files Dataset",
        

          5
            "updatedAt": "2026-04-25T02:57:56.179Z",
        

          6
            "earliestSampleDate": "1994-04-01",
        

          7
            "totalRecords": 9459,
        

          8
            "totalSize": 438692772,
        

          9
            "formTypes": ["486BPOS"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

          14
                "downloadUrl": "https://api.sec-api.io/datasets/form-486bpos-files/2026/2026-04.zip",
        

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

          16
                "size": 13818783,
        

          17
                "records": 154,
        

          18
                "updatedAt": "2026-04-25T02:57:56.179Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

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

Downloads the complete dataset, covering all Form 486BPOS filings from April 1994 to the present, as a single ZIP archive. This endpoint requires an API key.

Download Single Container: https://api.sec-api.io/datasets/form-486bpos-files/2026/2026-04.zip?token=YOUR_API_KEY

Downloads a single monthly container file instead of the full dataset, which is useful for incremental updates or when only a specific time range is needed. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form 486BPOS, a post-effective amendment to a Form N-2 registration statement filed under Rule 486(b) of the Securities Act of 1933. The "B" in the form code refers to Rule 486(b), which permits these amendments to become effective immediately upon filing or on a registrant-designated date within thirty days.

What does one record in this dataset represent?

One record is a single EDGAR submission of Form 486BPOS, identified by accession number and packaged as a self-contained accession-level folder. The folder contains the registrant-supplied documents (the primary inline-XBRL 486BPOS HTM file and the exhibit HTM files) plus a normalized metadata.json sidecar parsed from the SGML submission header.

Who is required to file Form 486BPOS?

Form 486BPOS is filed by registered closed-end management investment companies (including interval funds and tender offer funds) and business development companies (BDCs) that have an effective Form N-2 registration statement and need to make non-material updates eligible for immediate effectiveness under Rule 486(b). Open-end funds, ETFs (Form N-1A registrants), unit investment trusts, and operating-company issuers do not file this form.

What time period does the dataset cover?

The dataset covers all Form 486BPOS filings submitted to EDGAR from April 1994 — when EDGAR began accepting these filings electronically following adoption of Rule 486 — through the present, refreshed as new submissions arrive.

What file format is the dataset distributed in?

The dataset is distributed as monthly ZIP containers grouped by filing/effectiveness date. Each container contains accession-level subfolders with TXT, JSON, and HTML files: the primary 486BPOS document is an inline-XBRL HTML file, exhibits are SGML-wrapped HTML, and each accession includes a metadata.json sidecar.

How does this dataset differ from Form 485BPOS?

Form 485BPOS is the open-end fund analogue, filed by mutual funds and most ETFs under Rule 485(b) and amending Form N-1A. Form 486BPOS is filed by closed-end funds and BDCs under Rule 486(b) and amends Form N-2. The filer populations are disjoint: interval funds, tender-offer funds, listed closed-end funds, and BDCs appear only in 486BPOS.

How does Form 486BPOS differ from Form 486APOS?

Both are post-effective amendments to a closed-end fund or BDC's Form N-2 registration. Form 486BPOS is filed under Rule 486(b) for non-material updates (annual financial refreshes, share top-ups, fee-table updates) and becomes effective immediately or within thirty days. Form 486APOS is filed under Rule 486(a) for material changes, is subject to SEC staff review, and has a delayed effective date.

Are images and standalone XBRL technical files included in each record?

No. Image files (EDGAR GRAPHIC documents) and the standalone XBRL technical files (EX-101.SCH, EX-101.DEF, EX-101.LAB, EX-101.PRE, and the extracted *_htm.xml instance) are referenced by URL inside metadata.json but excluded from the ZIP payload. Images are excluded by dataset policy, and the XBRL facts are already embedded inline in the primary 486BPOS HTM document.