The Form 485BPOS Files Dataset is a comprehensive archive of every Form 485BPOS filing submitted to EDGAR from January 1994 to the present. Form 485BPOS is a post-effective amendment to a Securities Act registration statement filed under Rule 485(b), the automatic-effectiveness track for non-material amendments, and is the standing vehicle by which open-end mutual funds, insurance-company separate accounts, and certain unit investment trusts keep their prospectuses and statements of additional information current. Each record in the dataset is one complete 485BPOS filing rooted at a single SEC accession number and packaged as a folder containing a metadata.json manifest, the primary inline-XBRL prospectus document, and all non-graphic exhibits (material contracts, legal opinions, auditor consents, 18f-3 plans, and codes of ethics). The dataset ships as monthly ZIP containers covering the full 1994-to-present post-effective amendment corpus for registered investment companies filing under Rule 485(b).
Programmatically retrieve the full list of dataset archive files, download URLs and dataset metadata.
Dataset Index JSON API
Download the entire dataset as a single archive file.
Download Entire Dataset:
Download a single container file (e.g. monthly archive) from the dataset.
Download Single Container:
The dataset packages the complete EDGAR submission associated with every Form 485BPOS filing: the post-effective amendment document itself — almost always an updated mutual fund prospectus and, where applicable, a statement of additional information (SAI) — alongside every non-graphic exhibit filed with the amendment. Form 485BPOS is the post-effective amendment mechanism defined by Rule 485(b) of the Securities Act of 1933, and it is the form under which the overwhelming majority of ongoing mutual-fund disclosure updates are delivered. The dataset covers the entire eligible filer population: open-end management investment companies registered on Form N-1A, insurance-company separate accounts registered on Forms N-3, N-4, and N-6, and unit investment trusts registered on Form S-6, all of which may use Rule 485(b) for automatically effective post-effective amendments.
Time coverage starts January 1994, when the EDGAR phase-in for investment company filings was underway; pre-1994 post-effective amendments exist only in paper form and are outside the corpus. The dataset is distributed as monthly ZIP containers. For each accession number, the archive includes a metadata.json sidecar plus every document from the original EDGAR submission except image files, covering the primary amendment document and any attached exhibits. The file-types found in the dataset are TXT, JSON, HTML, PDF, and XFD, although in practice modern filings consist almost exclusively of HTM/HTML documents plus the JSON manifest; the rarer types appear only for unusual exhibit content and older-era submissions. Each filing typically contains an updated prospectus disclosing fund objectives, investment strategies, risk factors, fee tables, performance data, and portfolio management information as required under the underlying registration statement's instructions.
A single record is one complete Form 485BPOS filing as submitted to EDGAR, rooted at one SEC accession number. Physically, the dataset ships as monthly ZIP containers; inside each container every record is a folder named after the 18-digit accession number with dashes stripped (for example, 000089418925004231 corresponds to accession 0000894189-25-004231). That folder contains a metadata.json sidecar plus the full set of documents from the original EDGAR submission, with image/graphic attachments excluded. One folder equals one filing equals one post-effective amendment event.
A filing/document distinction matters when reading monthly index counts. Per-container record counts frequently equal the number of underlying document files (primary document plus exhibits across all filings), not the number of distinct filings. The canonical record key is the accession folder name (18-digit no-dash form); the canonical in-data identifier is metadata.json.accessionNo (dashed form) or the opaque id hash.
Form 485BPOS is a post-effective amendment to a registration statement filed under Rule 485(b) of the Securities Act of 1933. It is the standing vehicle by which open-end management investment companies — principally mutual fund trusts, variable-contract separate accounts, and unit investment trusts — keep previously effective registration statements current. Under Rule 485(b), qualifying amendments become effective automatically on a designated date provided they do not contain material changes that would trigger staff review; the "POS" suffix denotes post-effective status and the "B" denotes the 485(b) automatic-effectiveness track. Because prospectuses and statements of additional information (SAIs) must be updated at least annually and must also reflect intra-year "sticker" changes (new portfolio managers, new fee arrangements, new share classes, strategy updates, refreshed financial highlights), 485BPOS is the form under which the overwhelming majority of ongoing mutual-fund disclosure updates are delivered.
A 485BPOS almost always amends a registration statement previously filed on Form N-1A (open-end funds), Form N-2 (continuously offered closed-end funds), Form N-3 / Form N-4 / Form N-6 (insurance-company separate accounts offering variable contracts), or Form S-6 (unit investment trusts). The amendment inherits the structural conventions of whichever underlying form registered the securities, and typically delivers an updated prospectus and, where applicable, an updated SAI, accompanied by the lettered exhibits required by that form's instructions.
A record is composed of three logical layers, all present in the same accession folder:
metadata.json describing the accession, filer entities, the registered fund series and share classes, and an inventory of every document associated with the submission (both shipped-local and reference-only)..htm file carrying the updated prospectus and, where applicable, the SAI, encoded as inline-XBRL XHTML with financial facts tagged inline..htm documents, each preserved with the original EDGAR SGML <DOCUMENT> wrapper.Additional artifacts — graphic images, XBRL taxonomy linkbases, and the concatenated EDGAR .txt submission bundle — are enumerated in the manifest but ship by URL reference only; they are not copied into the folder.
The file types found in the dataset are TXT, JSON, HTML, PDF, and XFD. In practice, modern filings consist almost exclusively of HTM/HTML documents plus the JSON sidecar; the rarer types appear only for unusual exhibit content and older-era submissions.
metadata.json — the filing manifestEvery accession folder contains exactly one metadata.json. The manifest carries the following intentional, structured fields:
formType — always the literal "485BPOS" for this dataset.accessionNo — SEC accession number in dashed canonical form, e.g. "0001104659-25-054984".id — a 32-character opaque hexadecimal hash uniquely identifying the record across the dataset.filedAt — ISO-8601 timestamp with timezone marking the moment the submission reached EDGAR.effectivenessDate — date-only string naming the day the post-effective amendment takes effect under Rule 485(b); typically within one to sixty days of filedAt, depending on the designation the filer elected.description — human-readable form label, usually "Form 485BPOS - Post-effective amendment [Rule 485(b)]".linkToFilingDetails — URL to the primary document on EDGAR, frequently wrapped through the /ix?doc= inline-XBRL viewer.linkToHtml — URL to the EDGAR filing-index HTML page.linkToTxt — URL to the concatenated submission .txt bundle on EDGAR.linkToXbrl — usually an empty string for this form type, because XBRL data is embedded inline in the primary XHTML rather than delivered as a standalone instance document.documentFormatFiles — ordered array of document descriptors, one per submitted document. Each descriptor carries sequence (numeric string, with a blank entry for the submission bundle), size in bytes, an absolute documentUrl, a type field carrying the SEC exhibit-type code (e.g. "485BPOS", "EX-99.(I)", "EX-99.B(H)(5)", "GRAPHIC"), and a description. The final element with blank type and sequence: " " consistently points at the <accession>.txt full-submission bundle.dataFiles — array enumerating the XBRL taxonomy attachments that ship with the filing on EDGAR (EX-101.SCH, EX-101.CAL, EX-101.DEF, EX-101.LAB, EX-101.PRE, plus a trailing XML entry pointing at the extracted inline-XBRL instance <...>_htm.xml). Field shape mirrors documentFormatFiles. These files are listed for discoverability but are not copied into the local folder.entities — array of filer-entity records. Each entry carries cik, companyName (often annotated with " (Filer)"), type (mirrors formType), fileNo (the SEC file number, e.g. "811-22980" for an Investment Company Act registration or "333-197427" for a Securities Act registration statement), filmNo, irsNo, act ("33" for Securities Act, "40" for Investment Company Act), and commonly stateOfIncorporation and fiscalYearEnd in MMDD form. It is normal for the same filer to appear twice with different act/fileNo pairs, reflecting the joint 1933-Act and 1940-Act character of a mutual-fund registration amendment — these are not duplicates.seriesAndClassesContractsInformation — array describing every fund series and share class covered by the amendment. Each series object exposes series (SEC series ID such as "S000048360"), name (the fund name), and classesContracts, an array of { ticker, name, classContract } objects in which classContract is the SEC share-class ID (e.g. "C000152733"). A single trust-level 485BPOS commonly covers many series and many tickers — six series and ten to eleven share-class tickers are realistic magnitudes.Treat this manifest as the authoritative index of what the filing is, who filed it, which funds and share classes it covers, and where every document — shipped-local or remote — actually lives.
The document referenced by the sequence: "1" / type: "485BPOS" entry is always a single large .htm file: the updated prospectus (and, where applicable, the SAI) that the amendment delivers. It is encoded as inline-XBRL XHTML, not as an SGML-wrapped HTML body. The first line is an XML declaration; the root <html> element carries the full set of XBRL namespaces — xbrli, xbrldi, ix, ixt, ixt-sec, dei, oef, country, srt — plus a registrant-specific namespace. The <body> opens with an <ix:header> block declaring <ix:hidden> facts (such as dei:AmendmentFlag, dei:DocumentType = 485BPOS, dei:EntityCentralIndexKey), XBRL contexts keyed per share class (for example AsOf<date> and From<date><date>_custom_S...Member_custom_C...Member), and a <link:schemaRef> pointing at the taxonomy .xsd that ships separately on EDGAR.
The visible narrative content mirrors the structure of the underlying registration form (most commonly N-1A):
Numeric financial figures and many structured narrative elements (expense ratios, waiver amounts, performance figures, risk/return summary elements) are wrapped in <ix:nonFraction> and <ix:nonNumeric> tags so they can be extracted programmatically as XBRL facts against the Risk/Return taxonomy (the rr- and oef- namespaces). Primary documents commonly range from a few hundred kilobytes for single-series filings up to several megabytes; 3.5–3.9 MB is typical for multi-series trust-level filings.
Every non-graphic entry in documentFormatFiles with sequence ≥ 2 is a separate .htm exhibit shipped alongside the primary document in the same accession folder. Exhibit .htm files are SGML-wrapped: the EDGAR <DOCUMENT> envelope (with <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, <TEXT>) is preserved around an HTML body. The primary 485BPOS document does not carry this wrapper; exhibits do. A parser must branch on wrapper format when walking the folder.
Exhibit type codes follow the lettered schedule of Form N-1A Item 28 (or the corresponding exhibit schedules of N-2, N-3, N-4, N-6). Frequently observed types include:
EX-99.(H)(x) / EX-99.B(H)(x) — "Other material contracts": expense-limitation agreements, servicing agreements, administration agreements, and related side letters.EX-99.(I) / EX-99.B(I) — opinion and consent of counsel supporting the legality of the securities being registered.EX-99.(J) / EX-99.B(J) — consent of the independent registered public accounting firm.EX-99.B(N) — Rule 18f-3 multiple-class plan describing differential fees and services across classes.EX-99.B(P)(x) — code of ethics for the trust, the adviser, the sub-adviser(s), and the principal underwriter.EDGAR occasionally truncates type labels (for example "EX-99.I LEGAL OPININ"), and the B prefix on exhibit letters is applied inconsistently across filers (EX-99.(I) versus EX-99.B(I)). The reliable way to identify a file's role is through documentFormatFiles[].type and .description in metadata.json — not through filenames. Filenames follow no uniform convention (e.g. ex99i2.htm, tm258749d1_ex99-bxj.htm, angeloak485blegalopinionan.htm, regan_485bpos.htm), so join file-to-role via the manifest.
Each accession folder includes:
metadata.json with the structured fields enumerated above..htm files, covering the full set of lettered exhibits present (material contracts, legal opinion, auditor consent, 18f-3 plan, codes of ethics, and any other lettered exhibits supplied).Because inline-XBRL tags live inside the primary .htm, the tagged numeric and narrative data is preserved in the record even though the separate XBRL instance and linkbases are not shipped locally.
The manifest enumerates several artifacts that are not physically copied into the folder but remain retrievable via the documentUrl fields on EDGAR:
GRAPHIC entries — logos, performance charts rendered as images, and any other embedded graphics. Excluded from the dataset copy by design.sequence: " " entry ending in <accession>.txt. Reachable via linkToTxt.dataFiles entries: the XBRL schema (EX-101.SCH), calculation linkbase (EX-101.CAL), definition linkbase (EX-101.DEF), label linkbase (EX-101.LAB), presentation linkbase (EX-101.PRE), and the extracted inline-XBRL instance <...>_htm.xml. Listed for discoverability but not shipped locally.A downstream consumer that needs the standalone XBRL instance, the taxonomy linkbases, embedded images, or the concatenated SGML submission can fetch them directly from the URLs in the manifest.
Because a 485BPOS's required content tracks the instructions of the underlying form it amends, structural evolution of 485BPOS content is effectively the evolution of Forms N-1A, N-2, N-3, N-4, N-6, and S-6 over time. Several regulatory changes materially shaped what the record looks like:
The lettered exhibit schedule has also grown: new exhibit letters were added to N-1A Item 28 as regulation created new required contracts and plans (for example, Rule 18f-3 plans under EX-99.(N) and code-of-ethics filings under EX-99.(P)), so filings from the 1990s show a shorter exhibit list than those from the 2010s and 2020s.
485BPOS filings have existed continuously on EDGAR since 1994, and their wire format has evolved through three distinguishable eras:
.txt submission containing plain-text prospectus content with the SGML <DOCUMENT>/<TEXT> envelopes around each exhibit. Tables were rendered as fixed-width monospaced ASCII; image exhibits, when present, were uuencoded inside the text stream.<DOCUMENT> envelopes. Graphics became separate GRAPHIC attachments rather than inline ASCII art. The overall submission was still stitched together into a master .txt bundle.<ix:hidden> facts, and <ix:nonFraction> / <ix:nonNumeric> tags embedded directly in the prospectus markup. Exhibits retained the older SGML-wrapped HTML form and did not move to inline XBRL.In modern records, the primary document is inline-XBRL XHTML with no SGML wrapper, while exhibits continue to carry the SGML <DOCUMENT> envelope around a plain HTML body. A parser must expect both wrapper conventions in the same folder.
seriesAndClassesContractsInformation is the authoritative in-filing index linking SEC series IDs, class-contract IDs, fund names, and tickers. Do not infer the set of covered products from the prospectus text alone.entities entries with the same CIK and different act/fileNo pairs are normal, not duplicates — they reflect the dual 1933-Act / 1940-Act registration structure of a mutual fund.id hash and accessionNo are both stable record identifiers. The accession folder name is the 18-digit no-dash form of the accession number.documentFormatFiles[].documentUrl (or its tail filename) against metadata.json. Expect truncated type labels and inconsistent use of the B prefix.effectivenessDate is a scheduled date, not a staff-action date; it generally falls within one to sixty days of filedAt based on the filer's designation.485BPOS and therefore excludes 485APOS, 485BPOS/A, and 497-series filings; downstream analyses that need the full amendment lifecycle must join to those form-type datasets separately.EX-99.(J)) is the visible trace of that incorporation. Consumers seeking complete audited financials must follow the N-CSR reference trail, not the 485BPOS content alone.rr-, oef-, dei-), not the full line-item financial taxonomy used by operating-company 10-K/10-Q filings. Expect fact density around fees, returns, and portfolio turnover rather than a full income statement or balance sheet.Each record in this dataset is a single Form 485BPOS submission to EDGAR: a post-effective amendment to an already-effective Securities Act registration statement, filed by a registered investment company under Rule 485(b). The filer of record is the registrant entity whose registration statement is being amended, not the individual fund or share class. One 485BPOS from a large trust can update the prospectus and statement of additional information (SAI) for many series and classes at once.
The eligible filing population is narrow:
Closed-end funds, BDCs, ETPs organized as grantor trusts or commodity pools, and operating companies are not eligible for Rule 485 and do not file 485BPOS. They update registration statements through post-effective amendments to Form N-2, Form S-1, Form S-3, Form F-1, or similar forms.
Form 485BPOS is filed whenever an eligible registrant needs to update its effective registration statement with changes that do not require SEC staff review. Rule 485(b) grants automatic effectiveness to such amendments. Common triggers:
Rule 485(b) amendments become effective immediately upon filing or on a date the registrant designates in the filing (commonly up to 60 days later). The registrant chooses the effective date; there is generally no Commission declaration of effectiveness. A Rule 485(b) filing must include an officer certification that the amendment contains no disclosures making it ineligible for automatic effectiveness.
For insurance separate accounts, the cadence mirrors the mutual fund cycle but aligns with the separate account's fiscal year and the underlying contract cycle. Because one registrant may encompass dozens or hundreds of series and contracts, a single 485BPOS submission can be very large.
The dataset's digital coverage begins January 1994, when EDGAR phase-in for investment company filings was underway. Rule 485 itself was adopted in 1981, creating the split between Rule 485(a) review amendments and Rule 485(b) automatically effective amendments. Pre-1994 post-effective amendments exist only in paper form and are not part of the EDGAR corpus.
Form 485BPOS sits within the investment company registration regime under the Securities Act of 1933. The most useful comparisons are to the other post-effective amendment types (485APOS, 485BXT), the initial N-series registration forms that 485BPOS amends, and Rule 497 prospectus supplements. Shareholder reports, holdings reports, and proxy-voting filings cover the same funds but a different disclosure dimension entirely.
Form 485APOS. The direct sibling. 485APOS is filed under Rule 485(a) when the amendment contains material changes, triggering an SEC review period (typically 60 or 75 days) before effectiveness. 485BPOS is filed under Rule 485(b) and becomes effective automatically because the changes are non-material or of a type the rule expressly permits (annual updates, performance refreshes, conforming changes). Content structure is nearly identical (prospectus, SAI, exhibits); the distinction is the effectiveness mechanism and whether the changes require staff review.
Form 485BXT. A post-effective amendment filed under Rule 485(b)(1)(iii) solely to redesignate the effective date of a previously filed 485APOS. It is procedural, typically short, and does not carry a full updated prospectus. 485BPOS, by contrast, carries the operative disclosure document.
Initial registration statements: N-1A, N-3, N-4, N-6 (and N-2, S-6). These create the original prospectus and SAI: N-1A for open-end mutual funds and most ETFs, N-3/N-4/N-6 for insurance-company separate accounts, N-2 for closed-end funds, S-6 for unit investment trusts. A 485BPOS is an amendment to an already-effective N-1A, N-3, N-4, or N-6 (closed-end funds and UITs use different amendment mechanics). The initial filing happens once at launch; dozens of 485BPOS filings may follow over a fund's life. Combined, they form the full historical prospectus record.
Form 497 and 497K. Rule 497 filings deliver definitive-form prospectuses, SAIs, and interim supplements ("stickers") between annual amendments; Form 497K is the summary prospectus form under Rule 498. 497 does not amend the registration statement itself, while 485BPOS does. The two are complementary: 485BPOS establishes the annual baseline prospectus, 497 captures mid-year changes (new portfolio managers, fee waiver extensions, added risks). A complete view of a fund's live prospectus on any date generally requires the most recent 485BPOS plus any subsequent 497 stickers.
Form N-CSR / Form N-CSRS. Certified annual and semi-annual shareholder reports containing financial statements, schedules of investments, and performance discussion. Backward-looking and financial; 485BPOS is forward-looking prospectus disclosure (strategies, risks, fees). Same funds, different regime, not substitutes.
Form N-PORT and Form N-MFP. Structured portfolio holdings reports (N-PORT for most registered funds monthly; N-MFP for money market funds monthly). 485BPOS describes investment strategy and principal risks but contains no actual holdings data. Researchers needing portfolio composition must use N-PORT or N-MFP.
Form N-PX. Annual proxy-voting record. Useful alongside 485BPOS only when matching a fund's stated governance policies (found in the SAI) to actual voting behavior.
Form 24F-2NT. Annual fee-reconciliation notice under Rule 24f-2, tied to the same registration statement 485BPOS amends but containing no prospectus content.
Form 485BPOS is the automatically effective, non-material post-effective amendment that delivers the updated prospectus and SAI for already-registered open-end funds and insurance-company separate accounts. It is distinct from 485APOS (material changes, requires staff review), 485BXT (procedural date redesignation), the initial N-series and S-6 filings (one-time registration creation), and 497/497K (interim supplements that do not amend the registration statement). Shareholder reports, holdings reports, proxy-voting reports, and fee-reconciliation notices cover the same registrants but entirely different disclosure content and are not interchangeable with 485BPOS.
Form 485BPOS amendments update mutual fund prospectuses and SAIs on a rolling basis, so the Form 485BPOS Files Dataset draws users across fund legal, operations, compliance, product, distribution, and research functions.
Fund counsel and outside securities lawyers draft and review 485BPOS amendments and benchmark drafting against peer complexes. They compare risk-factor language, principal strategy disclosures, 12b-1 plan terms, fundamental restrictions, derivatives disclosures under Rule 18f-4, and liquidity program descriptions. Historical filings reconstruct the language in effect on a given date for disclosure liability analysis and staff-comment responses.
Administrators service fund boards and track effective prospectus dates, fee schedules, expense limitation agreements, share-class structures, and benchmarks across serviced funds. The fee table, financial highlights, and waiver disclosures drive expense-cap reconciliation, advisory-fee accruals, blue-sky coordination, and distribution of updated prospectuses to transfer agents and intermediaries.
CCOs at advisers and fund complexes reconcile marketing materials, fact sheets, and sales literature against current prospectus and SAI content. They focus on principal strategies, principal risks, fee tables, portfolio manager identification, and concentration policies to support Rule 38a-1 reviews, Rule 482 performance-advertising checks, and verification that sub-adviser changes or strategy shifts moved through the correct amendment mechanism.
Fund accounting teams and external auditors tie disclosed fee tables, expense caps, and financial highlights to booked expenses. Expense examples, expense limitation exhibits, breakpoint schedules, CDSC grids, and distribution-plan terms are central. The 1994-forward archive supports multi-year audits and fund reorganizations.
Product, pricing, and competitive intelligence teams track how peer complexes price share classes, structure breakpoints, and launch new vehicles. They extract fees, minimums, share-class lineups, benchmarks, and strategy language to inform pricing committees, share-class rationalization, Names Rule compliance, target-date glidepath revisions, and active-ETF conversions.
Operations teams at broker-dealers, wirehouses, bank trust platforms, and RIA custodians refresh share-class availability, sales-load schedules, breakpoint rules, redemption fees, and 12b-1 payments from 485BPOS content. The dataset supports prospectus-delivery compliance, FINRA Rule 2341 sales-charge supervision, and platform-level fund eligibility screens.
Commercial fund databases, security-master vendors, and analytics platforms parse 485BPOS filings to maintain structured expense, fee, strategy, benchmark, and portfolio-manager fields at the share-class level. The historical depth supports survivorship-bias-aware backfills used by downstream research tools and retirement recordkeepers.
Finance and law researchers, and buy-side quant groups, study fund fees, share-class proliferation, liquidity and derivatives disclosure, prospectus readability, and manager turnover. Fee tables, principal strategy and risk sections, performance tables, and manager rosters are the main extraction targets, with long-horizon coverage enabling panel studies linking disclosure changes to flows and performance.
Insurance carriers issuing variable annuities and variable life contracts align contract-level prospectuses with the underlying funds offered through separate accounts. Teams track underlying-fund fees, objectives, and principal risks to support menu reviews, multi-manager prospectus assembly, and fund-substitution applications.
Vendors handling electronic delivery, summary prospectus assembly, householding, and fulfillment ingest 485BPOS filings to maintain current document inventories keyed to CIK, series, and class identifiers. Effectiveness dates, summary prospectus availability, and required exhibits drive Rule 498 delivery workflows and investor document portals.
Teams building RAG systems and domain models for fund disclosure use the corpus to fine-tune and evaluate extraction on fee and strategy fields and to power adviser-facing copilots grounded in authoritative fund documents.
The records support operational workflows across fund legal, compliance, product, audit, and data-vendor functions. A few representative use cases:
Building share-class-level fee and expense panels. Parse the inline-XBRL rr- and oef- facts in the primary 485BPOS document together with seriesAndClassesContractsInformation to produce a time series of management fees, 12b-1 fees, acquired-fund fees, waivers, net expense ratios, and expense-cap durations keyed by CIK, series ID, and class-contract ID. Feeds pricing committees, product rationalization work, and academic fee studies.
Reconstructing the live prospectus in effect on any date. Join each 485BPOS effectivenessDate for a given series with subsequent Rule 497 stickers to determine the exact prospectus and SAI language governing a fund on a target date. Supports disclosure-liability analysis, staff-comment responses, and litigation discovery where counsel must prove what was in force when an investor transacted.
Benchmarking peer-complex risk and strategy language. Extract principal strategy, principal risk, and derivatives/liquidity-program sections (Items 4 and 9 of N-1A) across a peer set of trusts, then diff the text to inform drafting of new or revised 485BPOS amendments. Used by fund counsel and product teams when rolling out Rule 18f-4 derivatives disclosures, Names Rule changes, or active-ETF conversions.
Mapping share-class lineups, tickers, and series to CIK. Use seriesAndClassesContractsInformation as the authoritative link between SEC series IDs, class-contract IDs, tickers, and fund names. Reference-data vendors, distribution platforms, and security-master teams use the mapping to maintain share-class availability, sales-load schedules, and breakpoint tables under FINRA Rule 2341 supervision.
Tracking portfolio-manager and adviser-contract changes. Monitor management, sub-adviser, and portfolio-manager sections plus the EX-99.(H) material-contract and advisory-contract exhibits across successive 485BPOS filings for a given registrant to detect adviser terminations, sub-adviser additions, and portfolio-manager turnover. Used by compliance teams verifying that material changes moved through 485APOS where required, and by researchers studying manager turnover.
Auditor-consent and audit-trail extraction. Harvest the EX-99.(J) accountant consent from each filing to build a fund-by-fund auditor history and a year-over-year list of which financial statements were incorporated by reference from N-CSR. Supports auditor-change monitoring and audit-firm market-share analysis.
Training and evaluating fund-disclosure RAG systems. Use the full 485BPOS corpus, with inline-XBRL tags preserved in the primary document, as ground truth for fine-tuning and evaluating extraction of fee-table fields, principal-risk taxonomies, and strategy summaries in adviser-facing copilots and prospectus-question-answering systems.
The dataset can be accessed through a JSON index API that exposes dataset metadata and per-container download URLs, a full archive download, and direct downloads for individual monthly containers.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-485bpos-files.json
This endpoint returns dataset metadata including the name, description, last updated timestamp, earliest sample date, total records and total size, covered form types, container format, and included file types. It also provides the full dataset download URL and the list of individual container files, each with its size, record count, updated timestamp, and download URL. You can poll this endpoint to monitor which containers were refreshed in the most recent run and decide on a day-by-day basis which containers to download. This endpoint does not require an API key.
1
{
2
"datasetId": "1f13365b-9ae0-68e0-b49f-6aad1c1377a7",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-485bpos-files.zip",
4
"name": "Form 485BPOS Files Dataset",
5
"updatedAt": "2026-04-23T02:56:43.063Z",
6
"earliestSampleDate": "1994-01-01",
7
"totalRecords": 1000649,
8
"totalSize": 49486152467,
9
"formTypes": ["485BPOS"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["TXT", "JSON", "HTML", "PDF", "XFD"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-485bpos-files/2026/2026-04.zip",
15
"key": "2026/2026-04.zip",
16
"size": 13818783,
17
"records": 154,
18
"updatedAt": "2026-04-23T02:56:43.063Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-485bpos-files.zip?token=YOUR_API_KEY
Downloads the entire Form 485BPOS Files Dataset as a single ZIP archive containing all monthly containers from January 1994 to the present. This endpoint requires an API key.
Download Single Container: https://api.sec-api.io/datasets/form-485bpos-files/2026/2026-04.zip?token=YOUR_API_KEY
Downloads a single monthly container ZIP instead of the full dataset. Replace the year and month path segments to target a specific month. This endpoint requires an API key.
The dataset covers Form 485BPOS, a post-effective amendment to a Securities Act registration statement filed under Rule 485(b). It is the automatic-effectiveness track for post-effective amendments that do not contain material changes and is the standard mechanism for updating mutual fund prospectuses and statements of additional information.
One record is one complete Form 485BPOS filing rooted at a single SEC accession number. Each record is packaged as a folder (named after the 18-digit accession number with dashes stripped) containing a metadata.json manifest, the primary inline-XBRL prospectus document, and every non-graphic exhibit from the original EDGAR submission.
Form 485BPOS is filed by registered investment companies whose registration statements are eligible for Rule 485: principally open-end management investment companies (mutual funds) registered on Form N-1A, insurance company separate accounts registered on Forms N-3, N-4, or N-6, and certain unit investment trusts registered on Form S-6. Closed-end funds, operating companies, and foreign funds do not file 485BPOS.
Rule 485(b) amendments are most commonly filed as the annual prospectus update required by Section 10(a)(3) of the Securities Act (typically within 60 to 120 days of fiscal year-end), with additional filings triggered by new share classes or series, non-material strategy or fee changes, and post-comment re-filings after a 485APOS. A single large trust can file multiple 485BPOS amendments per year.
The dataset begins January 1994, when the EDGAR phase-in for investment company filings was underway, and extends to the present. Pre-1994 post-effective amendments exist only in paper form and are outside the EDGAR corpus.
The dataset ships as monthly ZIP containers. Inside each container, every record is a folder holding a metadata.json sidecar, the primary 485BPOS document as inline-XBRL XHTML, and exhibit documents as SGML-wrapped .htm files. The file types found in the dataset are TXT, JSON, HTML, PDF, and XFD, though modern filings are almost exclusively HTM/HTML plus JSON.
Both are post-effective amendments under Rule 485, but 485APOS filings (Rule 485(a)) contain material changes and are subject to an SEC staff review window of typically 60 or 75 days before effectiveness, while 485BPOS filings (Rule 485(b)) are automatically effective because the changes are non-material or of a type the rule expressly permits. This dataset is scoped strictly to 485BPOS; consumers who need the full amendment lifecycle, including staff-reviewed amendments and interim 497 stickers, must join to those form-type datasets separately.