Form 486APOS Files Dataset

The Form 486APOS Files Dataset is a corpus of post-effective amendments filed under Rule 486(a) of the Securities Act of 1933 by registered closed-end management investment companies and business development companies (BDCs) that conduct continuous offerings under Rule 415(a)(1)(ix) or make periodic repurchase offers under Rule 23c-3. Each record is one Form 486APOS submission to EDGAR, identified by accession number and packaged as a self-contained folder containing a metadata.json summary plus the textual filing documents shipped verbatim from EDGAR — the SGML-wrapped HTML body of the amendment plus any narrative or legal exhibits attached to it. The filer of record is always the fund or BDC entity itself, signed on its behalf by its officers and trustees. Under Rule 486(a), these amendments become effective on the sixtieth day after filing unless a later date is designated by the registrant. The dataset covers all Form 486APOS filings submitted to EDGAR from February 1994 onward, distributed as monthly ZIP containers holding TXT, JSON, and HTML files.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset captures every Form 486APOS submission filed to EDGAR — the post-effective amendment vehicle authorized by Rule 486(a) for closed-end management investment companies and BDCs running continuous offerings or periodic repurchase offers. The "(a)" branch of Rule 486 is used when the amendment introduces material changes that require staff review; the filing becomes effective on the sixtieth day after submission unless the registrant designates a later date or the Commission orders otherwise. The parallel Form 486BPOS, filed under Rule 486(b), takes effect immediately and is a separate dataset.

Because these registrants are dual-registered, a 486APOS is filed against both a Securities Act registration statement (almost always on Form N-2) and an Investment Company Act registration. As a result, a single 486APOS may amend the prospectus, the Statement of Additional Information, fee tables, financial highlights, investment-objective and strategy disclosures, risk-factor narratives, and the exhibit set hanging off the underlying N-2. The dataset covers the entire 486APOS filer population from February 1994 to the present and is distributed as monthly ZIP containers; the file types found across the dataset are TXT, JSON, and HTML.

Content Structure of a Single Record

What one record represents

A single record is one Form 486APOS submission to EDGAR, identified by its accession number and packaged as a self-contained folder. Each folder bundles a metadata.json summary of the EDGAR submission together with the textual filing documents shipped verbatim from EDGAR — the SGML-wrapped HTML body of the post-effective amendment plus any narrative or legal exhibits attached to it. Image files referenced inside the original submission (GIF, JPG, and similar) are intentionally omitted from the on-disk payload, although their URLs remain enumerated in metadata.json.

The unit of observation is therefore the full filing-package level — one accession, one folder — not an individual exhibit, an extracted item, or an event-level row. Each record corresponds one-to-one with an entry in EDGAR's filing index for Form 486APOS submissions.

What the underlying filing is

Internally, the amendment is organized exactly like the registration statement it amends: cover sheet, fee calculation, optional cross-reference sheet, prospectus (Part A), Statement of Additional Information (Part B), Other Information (Part C), signatures, and exhibits.

Container and folder layout

Records are organized into monthly ZIP containers under the path <datasetIdInUrl>/<year>/<year>-<month>.zip. A decompressed ZIP contains a single top-level directory named for the year-month (for example 2025-11/). Inside that directory, every accession in the month occupies its own subdirectory whose name is the eighteen-digit accession number with hyphens stripped (for example 000158064225007437). The hyphenated canonical form (0001580642-25-007437) is preserved inside metadata.json, so any join between folder names and metadata identifiers must normalize the punctuation.

Within an accession folder two kinds of files appear:

1. metadata.json — always present, a flat JSON summary of the EDGAR submission.
2. One or more textual filing documents — the HTM/HTML body of the 486APOS itself, occasionally accompanied by TXT companion documents and any textual exhibits attached to the original submission.

Filing-document filenames are taken verbatim from EDGAR and are short, filer-supplied slugs (for example cpsif_486a.htm). Image attachments referenced in the EDGAR submission are excluded from the on-disk payload, and the redundant complete-submission TXT bundle is also not shipped per accession even when listed in the metadata document inventory.

metadata.json contents

The metadata file is a flat JSON object whose meaningful fields are:

• formType — fixed at "486APOS" for every record.
• accessionNo — canonical EDGAR accession number with hyphens.
• id — internal hex record identifier.
• description — human-readable form description, typically "Form 486APOS - Post-effective amendment [Rule 485(a)]" or the equivalent 486(a) phrasing.
• filedAt — ISO-8601 acceptance timestamp with timezone offset.
• linkToFilingDetails — direct URL to the primary filing document on sec.gov/Archives/edgar/....
• linkToTxt — URL to the complete-submission TXT bundle on EDGAR.
• linkToHtml — URL to the EDGAR -index.htm filing index page.
• linkToXbrl — URL to XBRL data when present; an empty string otherwise.
• documentFormatFiles — array of every document attached to the original EDGAR submission, with sequence, size, documentUrl, description, and type per entry. This array is a superset of what is shipped on disk because it also enumerates GRAPHIC items and the complete-submission placeholder.
• dataFiles — array of structured-data attachments (XBRL/XML); commonly empty for 486APOS but populated when iXBRL cover-page or financial-highlights tagging applies under the 2020 Form N-2 reform.
• seriesAndClassesContractsInformation — array of fund series-and-class identifiers when EDGAR has populated them; frequently empty.
• entities — array of filer entities. Each entity row carries cik, companyName with a parenthetical role suffix such as "(Filer)", act (the Act under which the filing is made — "33" for the Securities Act, "40" for the Investment Company Act), fileNo (the SEC file number under that Act, for example a 333--prefixed number under the 33 Act and an 811--prefixed number under the 40 Act), filmNo (the EDGAR film number for the acceptance), type (set to "486APOS"), fiscalYearEnd as an MMDD string, stateOfIncorporation as a two-letter code, and irsNo.

Because a 486APOS is filed against both registration statements, the same CIK typically appears twice in entities — once with act: "33" and its associated 333-prefixed file number, and once with act: "40" and its 811-prefixed file number — each row carrying its own filmNo. This duplication is structural, not erroneous; joins to issuer master data should use cik.

Empty arrays and empty strings (for example seriesAndClassesContractsInformation, dataFiles, linkToXbrl) are preserved rather than omitted, so the JSON shape is stable across records.

The filing document itself

The primary filing document is not pure HTML. Each document is wrapped in EDGAR's SGML envelope and begins with header pseudo-tags before opening the HTML body:

          1
          <DOCUMENT>
        

          2
          <TYPE>486APOS
        

          3
          <SEQUENCE>1
        

          4
          <FILENAME>cpsif_486a.htm
        

          5
          <DESCRIPTION>486APOS
        

          6
          <TEXT>
        

          7
          <HTML>...</HTML>
        

          8
          </TEXT>
        

          9
          </DOCUMENT>
        

The <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, and <TEXT> lines are EDGAR document-level metadata; the body between <TEXT> and </TEXT> is the actual amendment. Parsers that feed the body to an HTML engine must strip this envelope first. The HTML body is heavily styled with inline style declarations on nearly every element, reflecting the word-processor origins typical of investment-company prospectus drafting.

Section-by-section anatomy of the body

Reading the body in document order, a typical 486APOS contains the following components, mirroring the underlying Form N-2:

1. Cover page (facing sheet of Form N-2). Names the registrant, gives the principal executive office, lists the agent for service of process, identifies counsel and (where applicable) the trustee, and presents the file numbers under both the Securities Act (333-…) and the Investment Company Act (811-…). Carries the post-effective amendment number, the boxes selecting Rule 486(a), 486(b), 485(a), or 485(b), and the boxes indicating reliance on Rule 415(a)(1)(ix) for continuous offerings or Rule 23c-3 for periodic repurchase offers.
2. Calculation of Registration Fee table. When applicable, the N-2 facing-sheet fee table identifying titles of securities, amounts being registered, proposed maximum offering price per unit, proposed maximum aggregate offering price, amount of registration fee, and the rule reliance noted.
3. Cross-reference sheet. Optional mapping of N-2 line items to the location of the corresponding disclosure inside the prospectus and SAI, where the registrant has chosen to provide one.
4. Prospectus (Part A of N-2). The principal selling document. Contains a prospectus summary; the fee table and expense example; financial highlights; sections on the fund's organization, investment objectives, principal investment strategies, principal risks, and management (including adviser and sub-adviser disclosure); purchase, repurchase, and pricing-of-shares mechanics (including Rule 23c-3 repurchase-offer terms — pricing date, repurchase request deadline, notification mechanics — for interval funds); distribution policy; dividend reinvestment plan; taxation; and description of capital structure. Risk-factor narratives are typically the most heavily updated component in a 486APOS.
5. Statement of Additional Information (Part B of N-2). A more technical disclosure document covering history and organization of the fund, additional investment policies and limits, board of trustees and officers (with biographical and compensation tables), control persons and principal holders of securities, investment advisory and other services, brokerage allocation, capital structure, expanded purchase/redemption/pricing detail, expanded taxation detail, financial statements when required, and counsel and auditor identification.
6. Part C — Other Information. Includes the exhibit index, persons controlled by or under common control with the registrant, indemnification disclosure, business and other connections of the investment adviser, principal underwriters, location of accounts and records, management services not described elsewhere, and the registrant's undertakings (including Rule 486(a) and Rule 415 undertakings where required).
7. Signatures. Conformed signature block executed pursuant to the Securities Act and the Investment Company Act, listing the registrant, the principal executive officer, principal financial officer, and the trustees, often accompanied by powers of attorney.
8. Exhibits. Filed inline as additional <DOCUMENT> blocks within the same submission. Typical N-2 exhibit categories under Item 25 include the declaration of trust or articles of incorporation and amendments; bylaws; voting trust agreements; instruments defining the rights of security holders; investment advisory contracts; underwriting contracts; bonus, profit-sharing, pension, or similar contracts; custodian and shareholder-services agreements; opinion and consent of counsel as to legality of securities; consent of the independent registered public accounting firm; financial statements omitted from the prospectus; the code of ethics required under Rule 17j-1; and any other exhibits required by Item 25 of Form N-2.

Included content

For each accession, the dataset record includes the structured metadata.json summary and every textual document in the EDGAR submission — the 486APOS HTML body plus any HTM, HTML, or TXT exhibit documents filed alongside it. Filenames, internal SGML headers, and inline styling are preserved exactly as they appeared on EDGAR, so the textual document content is byte-faithful within that scope.

Excluded or separate content

Three classes of content are not shipped on disk per accession:

• Image attachments. GRAPHIC entries in documentFormatFiles (typically GIF and JPG files used for fund logos, signature images, charts, or scanned exhibits) are intentionally excluded, although their URLs and metadata remain enumerated in documentFormatFiles so the original EDGAR locations stay discoverable.
• The complete-submission TXT bundle. EDGAR provides a single concatenated .txt of the entire submission as a sibling artifact; this is not duplicated locally, but linkToTxt in the metadata points at it.
• Cross-filing materials. Items incorporated by reference to prior registration statements, annual reports on Form N-CSR, or earlier post-effective amendments are not pulled into the record; only documents physically attached to this specific 486APOS submission are present. Reconstructing the full effective registration statement requires walking incorporation-by-reference pointers across filings.

Format evolution over time

The textual filing format has tracked EDGAR's broader transitions. Through the mid- to late-1990s, 486APOS filings were submitted as plain ASCII text inside the SGML <DOCUMENT> envelope, with tabular content rendered using fixed-width spacing. Beginning in the late 1990s and dominant by the early 2000s, filers shifted to HTML inside the same SGML envelope, enabling proper tables, fonts, and inline styling; this remains the prevailing format. The SGML wrapper itself has been preserved throughout, with <DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, and <TEXT> pseudo-tags delimiting each document regardless of the body format.

The underlying disclosure framework has also evolved. The 1998 plain-English rules and successive Form N-2 modernizations reshaped prospectus organization and risk-factor presentation. Closed-end fund risk-disclosure expectations expanded through the 2000s, particularly around leverage, derivatives, and illiquid investments. Rule 23c-3 repurchase-offer disclosure became a stable feature of interval-fund 486APOS amendments as interval funds proliferated in the 2010s. The 2020 amendments to Form N-2 (Securities Offering Reform for closed-end funds and BDCs) introduced WKSI-style shelf-offering practices, new prospectus-supplement mechanics, and structured-data tagging requirements for cover-page items, fee-table elements, and financial-highlights values. Under that regime, iXBRL tags appear inline in the HTML body rather than as separate XBRL data files, and linkToXbrl and dataFiles are populated when the structured-data layer is present; for filings predating the phase-in, those slots are empty.

Interpretation and extraction notes

• Two entity rows per filing are normal. Dual registration under the 1933 Act and the 1940 Act produces one entities row per Act, each with its own file number and film number. Issuer joins should be done on cik, not on row count.
• documentFormatFiles is a superset of on-disk files. Tooling that pairs metadata entries with local files must filter out GRAPHIC entries and the complete-submission TXT placeholder before joining; otherwise it will appear that some files are missing.
• Accession folder name versus accession number. The directory name is the eighteen-digit accession number with hyphens stripped, while metadata stores the canonical hyphenated form; cross-references must normalize the punctuation.
• SGML envelope must be stripped before HTML parsing. The leading lines from <DOCUMENT> through <TEXT> and the trailing </TEXT></DOCUMENT> are not valid HTML and must be removed before the body is fed to an HTML parser.
• Incorporation by reference is pervasive. Closed-end fund and BDC registrants frequently incorporate prior exhibits, financial statements, and policy language by reference to earlier filings; the 486APOS record contains only documents physically attached to the current amendment.
• 486APOS versus 486BPOS. The "(a)" suffix indicates material changes requiring staff review under Rule 486(a), with effectiveness on day sixty; 486BPOS filings under Rule 486(b) are immediately effective and reside in a separate dataset.
• Heavy inline styling. HTML bodies typically carry inline style declarations on nearly every element. Text-extraction pipelines should strip styling but preserve table structure and section anchors so prospectus, SAI, Part C, and exhibit boundaries remain identifiable.
• iXBRL tags only in 2020-reform filings. For 486APOS amendments filed under the modernized N-2 regime, structured-data tags are embedded in the HTML body itself; consumers extracting tagged cover-page or financial-highlights values must run an iXBRL-aware parser rather than expecting separate XBRL instance documents.

Who Files or Publishes This Dataset, and When

Each record corresponds to one Form 486APOS submission to EDGAR: a post-effective amendment to a previously effective registration statement (typically Form N-2), filed under Rule 486(a) of the Securities Act of 1933. The filer is always the registered investment company itself; its officers and trustees/directors sign on its behalf.

Who files

Form 486APOS is available only to a narrow class of registrants:

• Registered closed-end management investment companies that make periodic repurchase offers under Rule 23c-3 (interval funds) or register securities for continuous or delayed offerings under Rule 415(a)(1)(ix).
• Business development companies (BDCs) elected under Section 54 of the Investment Company Act of 1940 that conduct continuous offerings or periodic repurchase offers.

The filer of record is the fund or BDC entity. Its investment adviser, principal underwriter, custodian, and other service providers are described in the prospectus but are not the registrant.

What triggers a 486APOS filing

486APOS is the "(a)" path under Rule 486, used for post-effective amendments that are not eligible for immediate effectiveness under Rule 486(b). A registrant files on this form when the amendment includes:

• Material changes to investment objectives, strategies, principal risks, fee structure, or other substantive disclosure,
• Changes outside the limited categories Rule 486(b) treats as eligible for self-certified immediate effectiveness, or
• Any change for which the registrant prefers (or needs) staff review and a delayed effective date.

Routine annual updates limited to refreshed financials, fee tables, and other non-material conforming changes typically go on 486BPOS instead.

Timing and effectiveness

Under Rule 486(a), a 486APOS becomes effective automatically on the sixtieth day after filing, unless the registrant designates a later date on the cover or files a delaying amendment. During that window, SEC Division of Investment Management staff may issue comments; registrants respond by correspondence and, if needed, by additional pre- or post-effective amendments. A registrant often follows up a comment-cleared 486APOS with a 486BPOS or a Rule 497 prospectus filing to put the final disclosure into use.

The form itself imposes no fixed cadence. In practice, eligible funds file at least one annual post-effective amendment after fiscal year-end to keep the registration current, plus interim amendments triggered by strategy changes, new share classes, fee restructurings, board actions, or regulatory developments.

Important distinctions

• 486APOS vs. 486BPOS. Same filer population; different procedural track. 486APOS uses Rule 486(a)'s 60-day reviewable effectiveness; 486BPOS uses Rule 486(b)'s immediate effectiveness for enumerated non-material changes.
• 485APOS vs. 486APOS. Open-end mutual funds, insurance-product separate accounts, and unit investment trusts file under Rule 485 (Forms 485APOS / 485BPOS). The 486 series is reserved for closed-end funds and BDCs that meet the Rule 486 eligibility conditions.
• Initial registration vs. amendment. A new closed-end fund or BDC registers on Form N-2 itself, not on 486APOS. 486APOS exists only as an amendment to an already-effective N-2.
• Closed-end funds outside Rule 486. Conventional closed-end funds doing a one-time IPO and exchange listing do not conduct Rule 415(a)(1)(ix) continuous offerings or Rule 23c-3 repurchase offers, cannot rely on Rule 486, and amend under the general post-effective amendment regime instead.
• Successive amendments. Registrants may file multiple 486APOS submissions on the same registration statement to address staff comments; each is a separate accession number and a separate record in the dataset.
• Operating-company issuers. Exchange Act operating companies do not use Form 486APOS at all.

How This Dataset Differs From Similar Datasets or Filings

Form 486APOS occupies a narrow regulatory niche, and the most informative comparisons are with the sibling 486BPOS, the parallel 485 amendments for open-end funds, the underlying N-2 registration, the definitive 497 prospectus filings, the operating-company POS AM, and the certified shareholder report N-CSR. Each overlaps along one axis (filer, trigger, or content) and diverges on another.

Form 486BPOS — Rule 486(b) post-effective amendments

The closest neighbor. Same filer population, same registration form (N-2), same prospectus and SAI being updated. The split is mechanical and substantive:

• Form 486BPOS becomes effective immediately (or on a designated date) and is limited to the non-material updates enumerated in Rule 486(b): annual financial refreshes, completed-period fee table changes, and similar housekeeping.
• 486APOS becomes effective only on the sixtieth day after filing because it carries material changes outside the 486(b) safe harbor — new strategies, additional share classes, or other substantive prospectus revisions, often subject to staff comment.

486APOS is the dataset for tracking material strategy or structural changes; 486BPOS is the high-volume, routine annual-update stream.

Forms 485APOS and 485BPOS — Rule 485 amendments for open-end funds

The 485 family is the open-end analogue and mirrors Rule 486 mechanics (485(a) delayed effectiveness on day 75; 485(b) immediate). The decisive differences are filer universe and registration form: 485 amendments amend N-1A filings by open-end mutual funds and ETFs; 486 amendments amend N-2 filings by closed-end funds and BDCs. Disclosure content reflects this — 485 emphasizes daily redeemability, share-class breakpoints, and ETF mechanics; 486APOS emphasizes Rule 23c-3 repurchase terms, leverage, premium/discount risk, and senior-security coverage. The two datasets cover disjoint issuer populations despite the parallel naming.

Form N-2 — initial closed-end fund registration statement

The base document that 486APOS amends. N-2 establishes the initial registration with the original prospectus, SAI, and full exhibit set. 486APOS is narrower on two axes: it is an amendment rather than an initial filing, and it is filed only by N-2 registrants already running continuous or periodic-repurchase offerings. A complete documentary history of a closed-end fund's offering disclosures requires the original N-2 plus the chain of subsequent 486APOS and 486BPOS amendments, since amendments typically supersede portions of the prior prospectus rather than restate it in full.

Form 497 — definitive prospectus filings

497 delivers the definitive prospectus or supplement under Rule 497 (including 497K summaries and 497AD advertising). The relationship to 486APOS is sequential: 486APOS amends the registration statement; 497 transmits the definitive prospectus that results from effectiveness of that amendment. 497 filings are shorter, more frequent, and exclude exhibits, signature pages, and the full registration package. To see what disclosure investors actually received, use 497; to see the underlying registration-statement changes, use 486APOS.

POS AM — general post-effective amendment

POS AM is the operating-company analogue, used to amend S-1, S-3, S-4, S-11, F-1, and F-3 registrations. It shares the "post-effective amendment" label with 486APOS but otherwise diverges completely: different regulatory regime (general Securities Act rules rather than the investment-company-specific Rule 486), different issuer universe (operating companies, not investment companies), and different content (business descriptions, MD&A, operating-company financials versus fund fee tables, investment objectives, financial highlights, and Rule 23c-3 mechanics). POS AM and 486APOS partition the post-effective amendment universe between operating issuers and closed-end investment companies.

Form N-CSR — certified shareholder report

Same issuers, different document. N-CSR is the semi-annual shareholder report containing audited or unaudited financials, schedules of investments, and management discussion of performance — backward-looking financial reporting. 486APOS is forward-looking offering disclosure: prospectus text, fee tables, strategies, and risk factors. The two are complements, not substitutes: N-CSR shows what the fund held and earned; 486APOS shows what it tells prospective investors before they buy.

Boundary summary

Form 486APOS is defined by the intersection of three constraints no other dataset shares: a post-effective amendment (not an initial registration, definitive prospectus, or periodic report), filed under Rule 486(a) with sixty-day delayed effectiveness (not the immediate effectiveness of 486BPOS), by closed-end funds and BDCs running continuous or periodic-repurchase offerings (not open-end funds, ETFs, or operating companies). Shift any one axis and a different dataset applies: rule subsection -> 486BPOS; issuer type -> 485APOS/485BPOS; initial registration -> N-2; delivered prospectus -> 497; operating-company amendment -> POS AM; periodic financial reporting -> N-CSR. 486APOS is the material-change amendment layer for continuously offered closed-end funds and BDCs, sitting between the initial N-2 and the routine 486BPOS updates that follow.

Who Uses This Dataset

The audience for the Form 486APOS Files Dataset is narrow and section-specific: most users read fee tables, repurchase mechanics, fundamental policies, exhibits, or the 486(a) cover-page mechanics rather than the full document.

Fund compliance officers and CCOs

Compliance teams at closed-end funds and BDCs monitor their own and peer amendments to judge when a change requires 486(a) versus immediate-effective 486(b). They focus on cover-page designations, the description of material changes, the sixty-day effectiveness window, and SAI updates touching fundamental policies, concentration, and 1940 Act items. Used for compliance calendars, internal training, and peer benchmarking of non-ministerial change descriptions.

Fund counsel and securities attorneys

Outside fund counsel and in-house securities lawyers use 486APOS filings as drafting precedent for changes to investment objectives, leverage policies, fundamental restrictions, Rule 23c-3 repurchase terms, distribution arrangements, and risk factors. They also check exhibit packages — advisory and distribution agreements, custody documents, opinions, consents — when assembling filings or responding to staff comments.

Fund administrators and registration paralegals

Administrators and paralegals managing EDGAR submissions use prior 486APOS packages to model their own. They reference cover-page tagging, exhibit indexing, and the structure of prospectus and SAI updates to build filing checklists and track effective-date designations during the sixty-day review window.

Closed-end and BDC product development teams

Product teams designing non-listed closed-end funds, interval funds, tender-offer funds, and non-traded BDCs study competitor disclosure architecture: stated objectives, target allocation, leverage limits, repurchase frequency and pricing, distribution and shareholder servicing fees, and multi-class share arrangements. Used for product positioning, term-sheet drafting, and competitive feature mapping.

Fee and expense analysts

Expense analysts track how management fees, BDC incentive fees (hurdle rates, catch-up, capital-gains components), acquired fund fees, interest on leverage, and 12b-1 fees evolve across amendments. The updated fee tables, expense examples, and financial highlights feed expense benchmarking, fee compression studies, and total-cost models that include leverage drag.

Fund-of-funds and multi-manager due diligence

Due diligence analysts at fund-of-funds platforms, OCIO programs, and multi-manager allocators monitor underlying closed-end and interval-fund holdings for changes to investment policies, key-person provisions, valuation procedures, liquidity sleeves, and repurchase terms — any of which can trigger re-underwriting. Output: monitoring memos, watchlist updates, and redeem/hold/upsize calls.

RIA and wealth research teams

Wealth-management research desks allocating to non-listed closed-end funds, interval funds, and non-traded BDCs track changes affecting suitability: risk factors, fee tables, distribution and return-of-capital disclosures, repurchase mechanics, and share-class or sales-load changes. Used for approved-product-list maintenance, suitability documentation, and client communications.

Fund data vendors and analytics providers

Research teams at fund data providers ingest 486APOS filings to refresh product databases between annual updates, extracting fee schedules, strategy classifications, repurchase frequencies, leverage caps, and distribution policies into standardized taxonomies for screeners and profile pages.

Regulatory and policy analysts

Analysts at regulators, SROs, and policy research groups study how the 486(a)/486(b) framework is used in practice — invocation rates, types of changes described, and interaction with continuous offerings and Rule 23c-3 programs — to support rule-effectiveness reviews and amendment-frequency studies.

Academic researchers

Researchers working on closed-end fund discounts, BDC capital structure, interval fund growth, and disclosure quality use the corpus running back to 1994 to mine prospectus and SAI text for changes in objectives, leverage language, fees, and risk disclosures, typically paired with returns or flows.

Forensic accountants and litigation-support analysts

In fund-related disputes, forensic accountants reconstruct what was disclosed and when, focusing on financial highlights, fee tables, level-3 valuation disclosures, and risk-factor amendments. Output: expert reports, damages calculations, and disclosure timelines.

LLM and RAG developers

Teams building retrieval systems for fund documents use the dataset to benchmark extraction of fund-specific entities (advisers, custodians, distributors), numerical fields (fees, hurdle rates, repurchase percentages), and policy language across a constrained but professionally relevant filing type.

Summary

The dataset functions as a shared reference layer for the legal, compliance, administrative, product, and research roles surrounding continuous-offering closed-end funds, interval funds, and BDCs, with each role concentrating on a different section of the filing.

Specific Use Cases

The following workflows show how legal, compliance, product, and research teams put Form 486APOS records to work. Each use case names the operator, the question being answered, and the specific parts of the filing package consumed.

• Tracking interval-fund repurchase-term changes for re-underwriting decisions. Fund-of-funds due diligence analysts monitor incoming 486APOS amendments from interval funds on their watchlist and diff the Rule 23c-3 disclosures in Part A — repurchase frequency, repurchase request deadline, pricing date, notification mechanics, and the 5–25% repurchase-offer percentage — against the prior prospectus. Material loosening of liquidity terms triggers a re-underwriting memo and a redeem/hold/upsize recommendation. The entities[].cik and filedAt fields in metadata.json drive the watchlist join and the sixty-day effectiveness countdown.

• Building a fee-table panel for closed-end fund and BDC expense benchmarking. Fee and expense analysts extract the prospectus fee table and expense example from each 486APOS HTML body, plus the BDC incentive-fee mechanics (hurdle rate, catch-up, capital-gains component) and the interest-on-leverage line, and stack them by cik and filedAt into a longitudinal panel. Output feeds fee-compression studies, peer benchmarking decks, and total-cost models that account for leverage drag. iXBRL tags embedded inline under the 2020 N-2 reform are used where present to avoid re-parsing free-form HTML tables.

• Drafting precedent search for fund counsel responding to staff comments. Outside fund counsel filing a 486APOS for a new strategy or revised fundamental policy queries the corpus for prior amendments by similarly situated registrants, pulling the SAI fundamental-policy section, the cover-page 486(a) box selections, and Item 25 exhibits (advisory contracts, distribution agreements, opinions and consents) from the matching accession folders. The documentFormatFiles array is filtered to non-GRAPHIC entries to locate exhibit attachments on disk for clause-level borrowing.

• Maintaining fund-database product profiles between annual updates. Fund data vendors run a monthly ingest over each <year>-<month>.zip container, parse metadata.json for formType, accessionNo, entities[].cik, and entities[].fileNo, and refresh strategy classifications, leverage caps, repurchase percentages, distribution policies, and share-class line-ups by extracting the relevant prospectus sections from the HTML body. Updated values flow into screener taxonomies and fund profile pages without waiting for the next 486BPOS annual filing.

• Reconstructing disclosure timelines for fund-related litigation. Forensic accountants supporting plaintiff or defense work assemble a dated sequence of what investors were told and when by chaining the fund's 486APOS amendments using filedAt plus the sixty-day effectiveness lag, then pulling financial highlights, level-3 valuation language, and risk-factor narratives from each Part A and Part B. The resulting timeline anchors damages calculations and expert reports tied to specific disclosure events.

• Building an RAG benchmark for fund-prospectus question answering. LLM teams use the constrained 486APOS corpus to benchmark retrieval over fund-specific entities (adviser, sub-adviser, custodian, distributor), numerical fields (management fees, hurdle rates, repurchase percentages, leverage limits), and policy clauses. The fixed metadata.json schema, stable section ordering inherited from Form N-2, and SGML-wrapped HTML body provide consistent ground-truth anchors for evaluation harnesses.

• Studying 486(a) versus 486(b) invocation patterns for rule-effectiveness review. Regulatory and policy analysts aggregate the cover-page Rule 486(a)/486(b) box selections and the human-readable change descriptions across formType: "486APOS" records, joined to the same registrants' 486BPOS filings, to measure how often material-change amendments are used, what categories of changes they describe, and how the sixty-day staff-review window interacts with continuous offerings under Rule 415(a)(1)(ix).

Dataset Access

The Form 486APOS Files Dataset is available through three access methods: a JSON metadata index, a full dataset archive, and individual container downloads. Filings are organized into monthly ZIP containers covering the period from February 1994 onward.

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

This endpoint returns dataset-level metadata (name, description, last updated timestamp, earliest sample date, total records, total size, form types, container format, and content file types) along with the full list of monthly container files. Each container entry includes its size, record count, last updated timestamp, and direct download URL. This endpoint does not require an API key. Polling it on a regular schedule lets you detect which containers were modified in the most recent refresh run, so you can download only the containers that changed.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-69d9-9271-91a36619e3a4",
        

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

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

          5
            "description": "Form 486APOS filings are post-effective amendments to registration statements filed pursuant to Rule 486(a) under the Securities Act of 1933.",
        

          6
            "updatedAt": "2026-04-24T02:57:09.866Z",
        

          7
            "earliestSampleDate": "1994-02-01",
        

          8
            "totalRecords": 1399,
        

          9
            "totalSize": 79804378,
        

          10
            "formTypes": ["486APOS"],
        

          11
            "containerFormat": "ZIP",
        

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

          13
            "containers": [
        

          14
              {
        

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

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

          17
                "size": 1284736,
        

          18
                "records": 12,
        

          19
                "updatedAt": "2026-04-24T02:57:09.866Z"
        

          20
              }
        

          21
            ]
        

          22
          }
        

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

Downloads the complete dataset as a single ZIP archive containing every monthly container. This endpoint requires an API key.

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

Downloads one monthly container ZIP, useful for fetching only a specific period or for incrementally syncing recently updated containers identified through the JSON index. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form 486APOS, the post-effective amendment authorized by Rule 486(a) under the Securities Act of 1933 for registered closed-end management investment companies and business development companies that conduct continuous offerings under Rule 415(a)(1)(ix) or make periodic repurchase offers under Rule 23c-3. It does not include the parallel Rule 486(b) form 486BPOS, which is a separate dataset.

What does one record in this dataset represent?

One record is a single Form 486APOS submission to EDGAR, identified by its accession number and packaged as a self-contained folder. Each folder contains a metadata.json summary plus the textual filing documents — the SGML-wrapped HTML body of the post-effective amendment plus any narrative or legal exhibits attached to it.

Who is required to file Form 486APOS?

Only registered closed-end management investment companies (including interval funds operating under Rule 23c-3) and business development companies elected under Section 54 of the Investment Company Act of 1940 may file on this form, and only when they conduct continuous offerings under Rule 415(a)(1)(ix) or make periodic repurchase offers under Rule 23c-3. The filer of record is always the fund or BDC entity itself; its officers and trustees/directors sign on its behalf.

When does a 486APOS become effective?

Under Rule 486(a), a 486APOS becomes effective automatically on the sixtieth day after filing, unless the registrant designates a later date on the cover or files a delaying amendment. During that window, SEC Division of Investment Management staff may issue comments, and the registrant typically responds by correspondence and, if necessary, by additional amendments.

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

The dataset includes all Form 486APOS filings submitted to EDGAR from February 1994 to the present. Records are distributed as monthly ZIP containers under the path <datasetIdInUrl>/<year>/<year>-<month>.zip, with file types TXT, JSON, and HTML.

How is this dataset different from Form 486BPOS?

Both forms cover the same filer population and the same underlying N-2 registration, but 486APOS is used for material changes that fall outside the Rule 486(b) safe harbor and require staff review with sixty-day delayed effectiveness, while 486BPOS is limited to non-material updates (annual financial refreshes, completed-period fee table changes, similar housekeeping) that take effect immediately. 486APOS is the dataset to use for tracking material strategy or structural changes; 486BPOS is the high-volume, routine annual-update stream.

Are images and incorporated-by-reference materials included?

No. GRAPHIC attachments such as GIF and JPG files are intentionally omitted from the on-disk payload, although their URLs remain enumerated in metadata.json. The complete-submission TXT bundle and any materials incorporated by reference to prior registration statements, N-CSR reports, or earlier amendments are also not duplicated in the record — only documents physically attached to the specific 486APOS submission are present.