Form 486BXT Files Dataset

The Form 486BXT Files Dataset packages every EDGAR submission of Form 486BXT — the post-effective amendment filed under Securities Act Rule 486(b)(1)(iii) by registered closed-end management investment companies and business development companies (BDCs) to designate a new effective date for an earlier Rule 486(a) post-effective amendment. Each record represents one complete EDGAR submission, identified by its 18-digit accession number and packaged as a per-filing folder containing a metadata.json descriptor plus the HTML/HTM document(s) extracted from the original submission. The filer of record is always the registrant itself — a closed-end fund or BDC with an effective Form N-2 registration statement covering a continuous offering or delayed offering under Rule 415. The dataset begins in May 2018 and continues to the present, delivered as monthly ZIP archives with file types limited to HTML/HTM exhibits and JSON metadata.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset captures Form 486BXT filings as they appear on EDGAR. Form 486BXT is a post-effective amendment filed under Securities Act Rule 486(b)(1)(iii) by registered closed-end management investment companies and BDCs that conduct delayed or continuous offerings under Rule 415. Its narrow administrative purpose is to designate a new effective date for a post-effective amendment that the registrant previously filed under Rule 486(a). In substance, the filing points back at an earlier Rule 486(a) post-effective amendment and tells the Commission when that earlier amendment is to be deemed effective.

Because the underlying registration is for a closed-end fund or BDC, the filing sits at the intersection of two regulatory regimes — the Securities Act of 1933 (which governs the offering of the fund's shares) and the Investment Company Act of 1940 (which governs the issuer as a registered investment company) — and the EDGAR submission reflects this dual registration explicitly throughout both the metadata and the cover page.

The body of the filing is a Form N-2 cover page repurposed as an amendment. It identifies the registrant, declares the post-effective amendment number (for example, "POST-EFFECTIVE AMENDMENT NO. 17"), states the file numbers under both Acts, gives the registrant's principal executive office address, telephone number, agent for service, and copy-to counsel, and includes the standard Rule 415 / dividend reinvestment plan / Rule 486 check-the-box block that designates the rule under which the amendment is filed and the new effective date being claimed. A 486BXT filing may, but need not, carry an updated prospectus or statement of additional information as additional HTM exhibits; many filings consist solely of the cover page that designates the new effective date. The dataset is delivered as monthly ZIP archives named <YYYY>-<MM>.zip whose entries live under a top-level folder of the same stem, with per-accession sub-folders named with all dashes stripped from the EDGAR accession number.

Content Structure of a Single Record

A single record in the Form 486BXT Files Dataset is one complete EDGAR submission of Form 486BXT, identified by its 18-digit accession number. Inside the monthly ZIP, each accession occupies its own sub-folder named with all dashes stripped from the EDGAR accession number (for example, EDGAR accession 0001580642-25-004380 becomes folder 000158064225004380/). One record is therefore the union of all files inside a single accession folder: always metadata.json plus the primary 486BXT HTM, occasionally accompanied by additional HTM exhibits such as an updated prospectus or statement of additional information.

Within the per-accession folder two layers of content coexist:

1. A descriptive metadata layer: metadata.json, a flat JSON object that captures EDGAR header data, the document inventory, filer entity descriptors, and links back to the original submission on www.sec.gov.
2. A document layer: one or more HTM exhibit files extracted from the original EDGAR full-submission text. Each HTM file retains the SGML <DOCUMENT> wrapper that EDGAR places around documents inside its full-submission .txt, so the file is a hybrid SGML-plus-HTML document rather than a pure HTML page.

metadata.json is always present. Every HTML/HTM exhibit referenced by the submission is packaged. Image files (.jpg, .gif, .png) and the EDGAR full-submission .txt wrapper are intentionally omitted even though they remain enumerated in the documentFormatFiles inventory inside metadata.json.

metadata.json — field-by-field anatomy

metadata.json is a flat object that describes the EDGAR submission as a whole and enumerates its constituent documents and filers:

• formType — the EDGAR form code, fixed at "486BXT" for every record in this dataset.
• accessionNo — the dash-formatted 18-digit EDGAR accession number, for example "0001580642-25-004380".
• filedAt — an ISO 8601 timestamp with timezone offset capturing EDGAR's acceptance time, for example "2025-07-21T17:19:18-04:00".
• description — a short EDGAR-supplied description string, often simply "Form 486BXT -".
• id — an opaque 32-character hexadecimal record identifier, for example "3d6519c53e3858df87d71ace95dcccf3".
• linkToFilingDetails — the absolute URL of the primary form document on www.sec.gov, for example https://www.sec.gov/Archives/edgar/data/1897540/000158064225004380/aog_486bxt.htm.
• linkToTxt — the absolute URL of the EDGAR full-submission .txt wrapper for the accession.
• linkToHtml — the absolute URL of the EDGAR submission index page (...-index.htm).
• linkToXbrl — the absolute URL of an XBRL instance, if any. Empty for 486BXT records.
• documentFormatFiles — an array describing every document EDGAR knows about for the submission. Each entry has sequence (string sequence number; "1" for the primary document and a single space " " for the full-submission .txt line), type (the EDGAR exhibit-type label such as "486BXT", blank for the full-submission line), description (a human-readable label such as "486BXT" or "Complete submission text file"), documentUrl (the absolute file URL on www.sec.gov), and size (byte size as a string, for example "30004").
• dataFiles — an array of structured-data attachments (XBRL/XML). Typically an empty array [] for 486BXT records.
• seriesAndClassesContractsInformation — an array of fund series/class identifiers when EDGAR carries them. Typically an empty array [] for 486BXT records.
• entities — an array of one or more filer entity descriptors, discussed below.

The entities[] dual-Act pattern

The entities array is the most informative part of metadata.json for 486BXT records, because it directly encodes the dual-Act registration pattern of closed-end funds and BDCs. Each object contains: companyName (filer name, often suffixed with a role in parentheses such as "AOG Institutional Fund (Filer)"), cik (Central Index Key as a numeric string, e.g. "1897540"), irsNo (IRS employer identification number as a string, often "000000000" when not supplied), fileNo (EDGAR file number tied to the registration), filmNo (EDGAR film number for that specific filing entry), stateOfIncorporation (two-letter state code such as "DE"), fiscalYearEnd (four-digit MMDD fiscal year-end such as "0930"), act (the numeric Securities Act code under which this entity row was filed, typically "33" or "40"), and type (mirrors the top-level formType, i.e. "486BXT").

For a typical 486BXT submission, the same registrant appears more than once in entities — once per Act under which it is registered. AOG Institutional Fund, for example, appears twice in its 2025-07-21 filing: once with act: "40" and fileNo: "811-23764" (the Investment Company Act of 1940 registration, denoted by the 811- file-number prefix) and once with act: "33" and fileNo: "333-265783" (the Securities Act of 1933 registration statement, denoted by the 333- prefix), each with its own filmNo. This duplication is not a data error; it reflects how EDGAR records 486BXT submissions, which simultaneously amend a 1933 Act registration statement and pertain to a 1940 Act-registered investment company. Together, act and the fileNo prefix let downstream consumers separate the two registration views of the same legal entity.

HTM exhibit anatomy and the EDGAR SGML wrapper

The HTM exhibits packaged alongside metadata.json are not pure HTML files. They retain the SGML <DOCUMENT> wrapper that EDGAR places around each constituent document inside the full-submission .txt. The first lines of a primary 486BXT HTM look like:

          1
          <DOCUMENT>
        

          2
          <TYPE>486BXT
        

          3
          <SEQUENCE>1
        

          4
          <FILENAME>aog_486bxt.htm
        

          5
          <DESCRIPTION>486BXT
        

          6
          <TEXT>
        

          7
          <HTML>
        

          8
          <HEAD>
        

          9
          <TITLE></TITLE>
        

          10
          </HEAD>
        

          11
          <BODY>
        

          12
          ... rendered Form N-2 cover and post-effective amendment body ...
        

          13
          </BODY>
        

          14
          </HTML>
        

          15
          </TEXT>
        

          16
          </DOCUMENT>
        

The SGML header lines (<TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>) repeat key fields from documentFormatFiles and identify the document's role within the submission; the inner <HTML>...</HTML> block is the actually rendered cover page or exhibit. Primary form filenames are filer-controlled but conventionally embed 486bxt to flag the form type, for example aog_486bxt.htm for AOG Institutional Fund. When additional exhibits are filed (an updated prospectus, a statement of additional information, exhibits attached to Item 25 of Form N-2 such as legal opinions or consents), each appears as its own SGML-wrapped HTM file inside the same accession folder, with its own <TYPE> (e.g. EX-99, EX-99.1) and <SEQUENCE> value.

Within the <BODY> of the primary document, the rendered content of a 486BXT cover page typically includes:

• the legend "POST-EFFECTIVE AMENDMENT NO. [N]" with both the 1933 Act and 1940 Act file numbers shown side by side;
• the registrant's exact legal name and a SEC-mandated check-the-box of approximate date of proposed public offering;
• principal executive office address and telephone number;
• the name and address of the agent for service of process;
• copy-to addresses for outside counsel;
• the Rule 486(a)/(b) check-the-box block designating the rule under which the filing is made and the new effective date being designated (the operative content of the form);
• the title and class(es) of securities being registered;
• the signatures of the registrant's officers and trustees/directors as required by Form N-2.

When an updated prospectus or statement of additional information is included, the body extends into the full Form N-2 disclosure architecture — investment objective, fees and expenses table, principal risks, management of the fund, distribution arrangements, dividend reinvestment plan, and shareholder information. Otherwise the body terminates with the signature page.

Included content

Each record reliably includes:

• metadata.json with the complete header, document inventory, and filer entity descriptors described above.
• The primary 486BXT HTM document (the Form N-2 cover designating the new effective date).
• Any additional HTML/HTM exhibits filed with the submission, such as updated prospectuses, statements of additional information, or other Form N-2 exhibits supplied in HTML form.

Excluded or separate content

Even though documentFormatFiles enumerates every document EDGAR knows about for the submission, the dataset does not physically package:

• The wrapper full-submission .txt file (<accession>.txt).
• The EDGAR submission index page (<accession>-index.htm).
• Image files referenced inside the HTM exhibits (.jpg, .gif, .png), commonly used for fund logos or signature graphics.
• Any prior post-effective amendments (notably the underlying 486APOS/486BPOS that the 486BXT designates an effective date for); each accession is its own record.
• Amendments to the 486BXT itself (such as 486BXT/A) — they are separate records keyed by their own accession numbers.

Consumers can retrieve the omitted EDGAR artifacts via the URLs preserved in linkToTxt, linkToHtml, and the per-document documentUrl entries inside documentFormatFiles. Because images are excluded, HTM files containing <img> references will render with broken image placeholders unless the corresponding image is fetched independently from www.sec.gov.

Data format notes

The file-types found in the dataset are HTML/HTM and JSON. There is no plain-text or PDF rendition of the form inside the package, no XBRL instance, and no image content. Within the HTM files the SGML wrapper is a deterministic, parser-friendly preamble: the <TYPE>, <SEQUENCE>, <FILENAME>, and <DESCRIPTION> tags can be read directly without HTML parsing, and the inner <HTML> block can be handed to a standard HTML parser once the SGML preamble and trailing </TEXT></DOCUMENT> markers are stripped. The JSON metadata is UTF-8, flat at the top level, with two nested arrays of objects (documentFormatFiles and entities) and two arrays that are typically empty for this form (dataFiles, seriesAndClassesContractsInformation).

Coverage and structural stability

The dataset begins in May 2018 and continues to the present. Form 486BXT is a stable EDGAR form code; its required content and the structure of its EDGAR submissions have not undergone substantive regulatory restructuring during the covered period. The principal disclosure-content evolution affecting 486BXT filings during the dataset window is the SEC's 2020 adoption of expanded Form N-2 disclosure and structured-data requirements for closed-end funds and BDCs (Securities Offering Reform for Closed-End Investment Companies, Release No. 33-10771). That rulemaking enlarged the prospectus and SAI content that closed-end funds may include or update through post-effective amendments. In practice, however, 486BXT records in this dataset overwhelmingly carry no structured XBRL payload — the form is a designation filing, and linkToXbrl is empty and dataFiles is [] for typical records.

The packaging itself has been stable across the covered period. Records are delivered in monthly ZIP archives, every accession folder uses the dash-stripped 18-digit naming convention, and metadata.json keeps the same flat schema. The HTM exhibits have throughout been delivered with the EDGAR SGML <DOCUMENT> wrapper preserved around an inner HTML body.

Interpretation and extraction notes

Several nuances matter when working with these records.

• 486BXT is a designation filing rather than a substantive amendment. The amended disclosures normally live in the earlier Rule 486(a) post-effective amendment (typically a 486APOS) that the 486BXT references. The 486BXT record will state the new effective date and identify the registrant, but reconstructing the full amended prospectus usually requires following the registrant's prior 486APOS/486BPOS filing chain via the same CIK and 333- file number.

• The entities array's per-Act duplication is not multiple distinct filers. Group the entries by cik; the act value ("33" versus "40") and the fileNo prefix ("333-..." versus "811-...") identify which registration is being touched. Counting unique filers without de-duplication will overstate the number of entities involved.

• The document inventory describes the original EDGAR submission, not the on-disk record. Code that walks documentFormatFiles and expects every listed file on disk will miss this: image files and the .txt wrapper are listed but excluded by design. Code that walks the directory directly will see only the HTM exhibits plus metadata.json.

• Primary-document filenames are not standardized. They are filer-controlled and only conventionally include the substring 486bxt. To identify the primary form document programmatically, prefer the documentFormatFiles entry with sequence == "1" (or whose type equals "486BXT"), then match its documentUrl basename to the file on disk.

• Signatures are HTML content, not structured fields. Officers' and trustees'/directors' signatures appear at the end of the primary document's HTML body. They are not represented in metadata.json; extracting signers requires HTML parsing of the body.

• Amendments and the underlying 486(a) post-effective amendment live in separate records. A 486BXT/A or the prior 486APOS/486BPOS that the 486BXT activates each occupies its own accession-keyed record; relating them requires linking by registrant CIK, file number, and filedAt proximity.

• Inline XBRL coverage is form-specific. Although closed-end fund prospectus disclosures are subject to inline XBRL tagging requirements under Release No. 33-10771, a 486BXT itself is rarely the vehicle that carries the tagged prospectus — that tagging typically appears with the underlying 486APOS/486BPOS. Expect linkToXbrl == "" and dataFiles == [] for the vast majority of records in this dataset.

Who Files or Publishes This Dataset, and When

The filer of record is the registrant itself: a registered closed-end management investment company or a business development company (BDC) that has an effective Form N-2 registration statement covering a continuous or delayed offering under Securities Act Rule 415.

Eligible filers fall into two groups:

• Registered closed-end management investment companies, including:

  • interval funds (closed-end funds conducting periodic repurchase offers under Rule 23c-3 of the Investment Company Act of 1940)
  • tender offer funds that offer shares continuously
  • non-listed closed-end funds in continuous public offerings
  • listed closed-end funds operating shelf programs under Rule 415

• Business development companies electing to be regulated under Sections 55 through 65 of the Investment Company Act, both non-traded BDCs in continuous offerings and listed BDCs running Rule 415 shelves.

The registrant signs the form through its principal executive officer, principal financial officer, and a majority of its directors or trustees, generally via powers of attorney. Service providers named in the prospectus (investment adviser, sub-adviser, distributor, transfer agent) are described in the disclosure but are not filers.

When the record is created or required

Form 486BXT is event-driven, not periodic. There is no calendar deadline. A record is created only when the registrant elects to fix the effective date of an earlier post-effective amendment it filed under Rule 486(a).

The trigger sequence:

1. The fund or BDC has an effective Form N-2 registration statement covering a Rule 415 continuous or delayed offering.
2. The registrant files a post-effective amendment under Rule 486(a) (EDGAR code 486APOS) on a delayed-effectiveness track, typically the 60th day after filing.
3. The registrant decides it wants that 486APOS to become effective on a different date — to accelerate updated disclosure into the market, to align with an interval fund repurchase cycle or a quarterly pricing date, or to defer effectiveness pending Staff comment resolution.
4. The registrant files Form 486BXT under Rule 486(b)(1)(iii) to designate the new effective date for the predicate 486APOS.

Timing is bounded by the rule rather than by a deadline:

• The 486BXT must reference a prior 486APOS by the same registrant in the same registration chain.
• It must be filed early enough that the designated effective date remains permissible under Rule 486(b)(1)(iii) — in practice, before the 486APOS would otherwise auto-effect under Rule 486(a).
• The registrant must remain eligible under Rule 486(b), meaning the amendment cannot contain disclosure changes that fall outside Rule 486(b)'s permitted scope.

Because Form 486BXT is itself a Rule 486(b) filing, it takes effect on filing or on the designated date under Rule 486(b), and the predicate 486APOS becomes effective on that designated date. Substantive prospectus changes are usually carried in the 486APOS; the 486BXT is a short procedural amendment, though a conforming prospectus or SAI may be attached. A given registrant may file no 486BXTs in a year or several across separate registration cycles, reflecting the opt-in, event-based nature of the form.

Important distinctions

• 486BXT vs. 486APOS. Form 486APOS is the substantive Rule 486(a) post-effective amendment with delayed automatic effectiveness. 486BXT is the Rule 486(b)(1)(iii) follow-on that designates 486APOS's effective date. A 486BXT cannot exist without a predicate 486APOS.
• 486BXT vs. 486BPOS. Form 486BPOS is the general Rule 486(b)(1) immediate-effectiveness amendment (additional shares of the same class, financial statement updates, non-material changes). 486BXT is the narrower Rule 486(b)(1)(iii) variant used only to fix the effective date of a prior 486APOS.
• 486-series vs. 485-series. Open-end mutual funds, ETFs on Form N-1A, and insurance-company separate accounts on Forms N-4/N-6 use the Rule 485 regime (485APOS, 485BPOS, 485BXT). Closed-end funds and BDCs use the Rule 486 regime. A filer appearing in this dataset is, by submission code alone, a closed-end fund or BDC.
• Operating companies are excluded. Non-investment-company issuers amend registration statements under Securities Act Rule 462 or ordinary Section 8 mechanics, not under Rule 486.
• Listed status is not the determinant. Both listed and non-listed closed-end funds may use Rule 486 if they conduct continuous or delayed offerings under Rule 415; what matters is investment-company classification plus offering posture.
• Registrant vs. series. The filer is the registrant entity (the fund, BDC, or master trust). For multi-series trusts, the filing is made at the registrant level even when the prospectus update concerns one series.
• Disclosed parties are not filers. Advisers, sub-advisers, sponsors, underwriters, and portfolio managers described in the prospectus are not the filing party; the registrant is.

Regulatory framework

• Securities Act of 1933. Form 486BXT amends a Securities Act registration statement (Form N-2) and operates under Securities Act Rule 486, which gives qualifying closed-end funds and BDCs an effectiveness regime parallel to Rule 485 for open-end funds.
• Investment Company Act of 1940. Eligibility to use Rule 486 depends on the registrant's status as a registered closed-end management investment company (with interval fund eligibility under Rule 23c-3) or as a BDC regulated under Sections 55-65. Form N-2 is a joint Securities Act / Investment Company Act form.
• Securities Act Rule 415. The continuous or delayed offering posture that makes Rule 486 relevant rests on Rule 415 shelf-registration authority.
• Regulation S-T and EDGAR filing rules. Govern the electronic submission and the dedicated submission code "486BXT" for filings made under Rule 486(b)(1)(iii).

How This Dataset Differs From Similar Datasets or Filings

Form 486BXT sits in a narrow corner of the closed-end fund and BDC registration ecosystem. Its closest neighbors are the other Rule 486 post-effective amendments, the open-end analog under Rule 485, the underlying N-2 registration statement, and prospectus filings under Rule 497. The distinctions turn on which Securities Act rule is invoked, whether the filing carries substantive disclosure, and which fund type files it.

Closest related filings

Form 486APOS (Rule 486(a)) The substantive companion to 486BXT. Filed by the same closed-end fund and BDC population, 486APOS introduces material changes (new investment strategies, fundamental policy changes, other staff-review items) and does not become effective automatically. 486BXT carries no new disclosure; it exists to designate the effective date of a previously filed 486APOS. The two are typically paired in the same filing chain.

Form 486BPOS (Rule 486(b)(1)) The immediate-effectiveness amendment for routine annual updates, financial statement refreshes, and other non-material changes. Both 486BPOS and 486BXT rely on Rule 486(b) and skip staff review, but 486BPOS is content-bearing and effective on its own terms, while 486BXT is purely a date-designation filing tied to a pending 486APOS.

Form 485BXT (Rule 485(b)(1)(iii)) The structural twin in the open-end world. Mechanics are nearly identical, but 485BXT amends Form N-1A, N-3, N-4, or N-6 filings by open-end funds, UITs, and variable products. 486BXT amends Form N-2 filings by closed-end funds and BDCs. Neither dataset substitutes for the other; covering all date-designation amendments requires both.

Form N-2 and N-2/A The underlying registration statement and its pre-effective amendment carry the full substantive content: investment objectives, fees, risks, governance, financials. 486BXT presupposes an effective N-2 already exists and only manages effective-date logistics for a downstream post-effective amendment. Substantive research starts with N-2; timeline and effectiveness research uses 486BXT.

Form 497 prospectus filings Filed under Rule 497 to deliver definitive prospectuses and supplements during a continuous offering. 497 filings are prospectus deliveries, not registration-statement amendments, and do not change a registration statement's effective date. 486BXT is a registration-statement amendment whose only function is to set that effective date. A continuously offered fund typically generates both over time.

Rule 486(a) versus Rule 486(b)

The 486 family splits cleanly along this boundary. Rule 486(a) covers material changes requiring staff review and a designated effective date; Rule 486(b) covers routine or non-material changes that go effective automatically. 486BXT sits at the seam: it is filed under Rule 486(b)(1)(iii), but its sole job is to designate a new effective date for a pending 486(a) amendment, usually after staff review concludes or the fund revises the underlying filing.

Boundary summary

Form 486BXT is narrowly defined along three axes: filer type (closed-end funds and BDCs), legal mechanism (Rule 486(b)(1)(iii) date designation), and function (effective-date management for a 486(a) amendment). It is not interchangeable with 486APOS or 486BPOS, both of which carry substantive content; not equivalent to 485BXT, which serves the open-end universe; not a registration statement like N-2; and not a prospectus filing like 497. Its analytic value is precise: it pins down when a previously filed 486(a) amendment actually goes live, an event that cannot be reconstructed from neighboring datasets alone.

Who Uses This Dataset

The Form 486BXT Files Dataset serves a tight set of fund-industry roles, each anchored to specific record elements: the designated effective date, the predicate Rule 486(a) reference, the registrant CIK, series and class identifiers, the attached prospectus and SAI exhibits, and the JSON metadata.

Fund Compliance Officers

CCOs and compliance analysts at closed-end fund and BDC complexes use the dataset to verify that their own filings, and peers', follow Rule 486 sequencing correctly. They check the timing chain between the underlying 486(a) amendment and the 486BXT designation, the CIK and series identifiers, and cover-page recitals. Output: filing-control checklists, internal audits, and evidence files showing the registrant used the designated-effective-date mechanic rather than automatic 486(b) effectiveness.

Fund Counsel and 1940 Act Lawyers

Securities counsel advising closed-end funds, interval funds, tender-offer funds, and non-listed BDCs build precedent libraries from the dataset. They mine cover-page recitals, the predicate 486(a) reference, and explanatory notes for invocation language, and study the prospectus and SAI exhibits to benchmark continuous-offering disclosure across sponsors. Supports drafting, comment-response strategy, and filing-convention benchmarking.

Fund Treasurers and Fund Accountants

Treasury and fund accounting teams align internal NAV, distribution, and offering calendars with the legally designated effective date. They consume the new effective date, CIK, and series-level identifiers to update share-class registers, continuous-offering authorization windows, and prospectus-version pointers in accounting systems.

Transfer Agents and Fund Administrators

Transfer agents and administrators servicing closed-end funds and BDCs refresh books-and-records to reflect which prospectus and SAI versions are currently effective per share class. They rely on accession numbers, effective-date metadata, and the prospectus and SAI exhibits to drive subscription fulfillment, investor delivery, blue-sky tracking, and cutover between superseded and current offering documents.

Prospectus Operations and Filing-Ops Teams

In-house prospectus-of-record groups and outsourced filing-ops vendors maintain registries linking each effective prospectus and SAI to its registration statement and post-effective amendment. The 486BXT submission is the event that crystallizes effectiveness, so these teams parse JSON metadata and exhibit indices to keep version-control systems and EDGAR audit trails complete.

Product Strategy and Competitive Intelligence

Product teams at asset managers track when competitors refresh prospectuses, fee structures, investment policies, or distribution terms via the 486(a)/486BXT path. They watch registrant identity, the new effective date, and substantive amendments in the attached prospectus or SAI to time launches, benchmark fees, and adjust distribution strategy.

Transaction Diligence Teams

Diligence counsel and bankers on acquisitions of fund sponsors, BDC managers, or interval-fund platforms use the dataset to reconstruct registration histories of target funds. The 486BXT chain of effectiveness underpins reps and warranties about registration status and confirms target offering documents were properly effective on relevant dates.

Academic and Industry Researchers

Researchers studying closed-end funds, BDCs, and the growth of interval and non-listed structures use the dataset as a time series of effective-date events. CIK and date metadata support studies of prospectus-refresh cadence, product-type filing patterns, and use of 486 versus alternative paths, with coverage from May 2018 forward.

RegTech and Filing-Analytics Vendors

Vendors building fund-industry analytics ingest the JSON metadata for accession-level normalization and the HTML exhibits for text extraction, classification, and exhibit linking. Powers alerting, prospectus-versioning tools, 486-usage dashboards, and audit-trail products sold to fund compliance and operations teams.

Distribution and Wholesaling Compliance

Compliance staff supporting wholesalers and broker-dealer distribution of closed-end funds and BDCs confirm that selling activity is backed by a currently effective prospectus. They use the new effective date and the attached prospectus exhibit to keep marketing-review systems, sales supervision, and subscription documents aligned to the right prospectus and SAI version.

LLM and RAG Engineering Teams

Engineers building retrieval systems for fund counsel, compliance, and product users treat 486BXT filings as a clean, rule-specific corpus. The dataset supports classifiers that separate 486(a), 486(b), and 486BXT filings; QA over prospectus and SAI exhibits; and knowledge graphs keyed on effective-date events.

Specific Use Cases

Form 486BXT records are date-designation filings for closed-end fund and BDC post-effective amendments. The dataset is most useful where a precise effective-date timestamp, a registrant CIK, and the attached prospectus or SAI exhibits drive a downstream workflow.

Reconstructing 486(a) to 486BXT effectiveness chains

Fund counsel and compliance teams pair each 486BXT record with the registrant's prior 486APOS using shared CIK and the 333- file number from entities[], then use filedAt as the designated effective date for the predicate amendment. Output: a per-fund timeline of when each 486(a) amendment actually went live, used for SEC comment-response files and Rule 486 sequencing audits.

Driving prospectus-of-record version cutovers

Transfer agents and prospectus-ops teams ingest each new accession to flip the active prospectus and SAI for a closed-end fund or BDC share class. They parse documentFormatFiles for HTM exhibits beyond the cover (updated prospectus, SAI), match share-class identifiers to internal records, and schedule the cutover for subscription fulfillment, blue-sky tracking, and investor delivery on the filedAt date.

Building a closed-end fund and BDC effective-date alerting feed

RegTech vendors and product-strategy teams stream the monthly ZIPs into a watchlist keyed on competitor CIKs. Filtering on formType == "486BXT" and extracting filedAt, registrant name, and any attached prospectus exhibit produces alerts when a peer refreshes fees, distribution terms, or investment policies through the 486(a) path — feeding fee benchmarking dashboards and launch-timing models.

Continuous-offering authorization windows for fund treasury

Fund treasurers and accountants extract the designated effective date and the registrant's 811- (1940 Act) and 333- (1933 Act) file numbers from entities[] to update offering-window flags in NAV and distribution systems. The output is an authoritative internal calendar of when continuously offered shares may be sold against a refreshed prospectus.

Fund-sponsor M&A registration diligence

Diligence counsel on acquisitions of closed-end fund sponsors, interval-fund platforms, or non-listed BDC managers walk a target's full 486BXT history by CIK to confirm each post-effective amendment was properly designated effective. The accession-level metadata plus signed cover pages support reps and warranties about registration status and produce a timeline exhibit for the purchase agreement disclosure schedules.

Precedent libraries for Rule 486(b)(1)(iii) cover-page language

Securities counsel mine the primary HTM bodies across many filers to extract Rule 486 check-the-box recitals, agent-for-service blocks, and copy-to counsel patterns. The result is a precedent bank of invocation language for drafting new 486BXT covers and benchmarking how peer sponsors phrase the designation of a new effective date.

Training rule-specific classifiers and RAG corpora

LLM engineering teams use the dataset as a clean, single-form corpus to train classifiers that separate 486APOS, 486BPOS, and 486BXT filings, and to build retrieval indexes scoped to closed-end fund effective-date events. The SGML <TYPE> header plus metadata.json give deterministic labels; the inner HTML body supplies the text for embedding and QA over prospectus and SAI exhibits when present.

Dataset Access

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

This endpoint returns dataset metadata including the dataset name, description, last updated timestamp, earliest sample date (2018-05-01), total records, total size, covered form types (486BXT), container format (ZIP), and file types (HTML, JSON). It also returns the full dataset download URL and a list of all individual container files with per-container metadata such as size, record count, updated timestamp, and a direct download URL. Use this endpoint to monitor which containers have changed in the most recent refresh and decide which container files to re-download on a daily basis. This endpoint does not require an API key.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-69fe-be3f-86e7055c4310",
        

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

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

          5
            "updatedAt": "2026-04-28T02:58:06.736Z",
        

          6
            "earliestSampleDate": "2018-05-01",
        

          7
            "totalRecords": 154,
        

          8
            "totalSize": 905822,
        

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

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

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

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

          16
                "size": 18432,
        

          17
                "records": 3,
        

          18
                "updatedAt": "2026-04-28T02:58:06.736Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

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

Downloads the complete Form 486BXT Files Dataset as a single ZIP archive containing all monthly container files from May 2018 to the present. This endpoint requires an API key.

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

Downloads one individual monthly container file instead of the full dataset, which is useful for incremental updates or retrieving filings from a specific month. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form 486BXT, the post-effective amendment filed under Securities Act Rule 486(b)(1)(iii) by registered closed-end management investment companies and business development companies. Its sole administrative purpose is to designate a new effective date for an earlier post-effective amendment that the registrant filed under Rule 486(a).

What does one record in this dataset represent?

One record is a single complete EDGAR submission of Form 486BXT, identified by an 18-digit accession number. Each record is a per-accession folder containing a metadata.json descriptor plus the primary 486BXT HTM document and any additional HTM exhibits (such as an updated prospectus or statement of additional information) that were filed with the submission.

Who is required to file Form 486BXT?

The filer is always the registrant — a registered closed-end management investment company (including interval funds, tender offer funds, and non-listed and listed closed-end funds running Rule 415 shelves) or a business development company regulated under Sections 55-65 of the Investment Company Act of 1940. Investment advisers, distributors, and other service providers named in the prospectus are not filers.

How does Form 486BXT differ from Form 486APOS and Form 486BPOS?

486APOS is the substantive Rule 486(a) post-effective amendment with delayed automatic effectiveness; 486BPOS is the Rule 486(b) immediate-effectiveness amendment for routine non-material updates. 486BXT carries no new disclosure of its own — it is filed under Rule 486(b)(1)(iii) only to designate the effective date for a previously filed 486APOS, and cannot exist without that predicate filing.

What time period does the dataset cover?

The dataset begins on 2018-05-01 and continues to the present, with new filings added as they appear on EDGAR. Form 486BXT is event-driven, so a given registrant may file no 486BXTs in a year or several across separate registration cycles.

What file format is the dataset distributed in?

The dataset is delivered as monthly ZIP archives named <YYYY>-<MM>.zip. Inside each archive, every accession occupies its own folder containing metadata.json and one or more HTM exhibit files; file types are limited to HTML/HTM and JSON. The HTM exhibits retain the EDGAR SGML <DOCUMENT> wrapper around an inner HTML body.

Why does the same registrant appear more than once in entities[]?

The duplication encodes the dual-Act registration of closed-end funds and BDCs: the same legal entity is registered under both the Securities Act of 1933 (with a 333- file number and act: "33") and the Investment Company Act of 1940 (with an 811- file number and act: "40"). To count unique filers, group entities[] rows by cik rather than treating each row as a distinct entity.