Form 497J Files Dataset

The Form 497J Files Dataset is a complete, accession-level collection of every Form 497J certification filed on EDGAR by registered investment companies from January 1994 to the present. One record corresponds to one EDGAR submission of form type 497J — a short certification, filed under paragraph (j) of Securities Act Rule 497, by which a registrant attests that the definitive prospectus materials most recently filed under Rule 497(a)–(f) have not changed and therefore do not need to be refiled. The underlying filings are made by open-end mutual funds and ETFs on Form N-1A, closed-end funds on Form N-2, and Unit Investment Trusts on Form S-6. Each record bundles a structured metadata.json manifest with the primary certification document (HTML or plain-text SGML), packaged inside monthly ZIP containers keyed <year>/<year>-<month>.zip.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset captures every Form 497J submission accepted by EDGAR since the earliest sample date of January 1, 1994. Form 497J is not a prospectus and is not a disclosure document. It is an administrative certification letter — typically one to three kilobytes of text — by which a registered investment company represents to the Commission that no substantive changes have occurred in the definitive prospectus materials it most recently filed, and therefore that a fresh Rule 497(a)–(f) filing is not required for the upcoming statutory window. The letter is transmitted "Via EDGAR", addressed to the Filing Desk of the Securities and Exchange Commission at 100 F Street NE, Washington DC 20549, and signed by counsel or by an officer of the registrant.

The dataset covers the entire Form 497J filer population across the regime — open-end mutual funds and ETFs, closed-end funds (including interval funds and tender offer funds), and Unit Investment Trusts. For each accession number, the dataset includes a normalized JSON metadata object plus the primary 497J certification document as served by EDGAR, with its SGML document envelope preserved verbatim. Image assets that accompanied the original submission (letterhead graphics, logos) and the aggregate complete-submission .txt bundle are deliberately excluded from the record folder but remain referenced by URL in the metadata manifest.

The distribution format is a ZIP container hierarchy. The top-level archive decomposes into monthly sub-archives, each of which holds one sub-folder per accession number. File types encountered across the dataset are TXT, JSON, HTML, and PDF, though in practice the vast majority of filings resolve to either an .htm or .txt certification plus the metadata.json manifest.

Content Structure of a Single Record

What one record represents

A single record in the Form 497J Files Dataset corresponds to exactly one EDGAR submission of form type 497J — a certification by a registered investment company, filed pursuant to paragraph (j) of Rule 497 under the Securities Act of 1933, attesting that the definitive prospectus (and, for open-end funds, statement of additional information) most recently filed as a post-effective amendment would not have differed from what the registrant would otherwise have been required to file under paragraphs (a), (b), (c), (d), (e), or (f) of the same rule. In dataset terms, one record is one accession number.

Physically, one record is one sub-folder inside a monthly ZIP container, named after the 18-digit accession number with dashes stripped (for example, 000199937125008558/ for accession 0001999371-25-008558). The folder bundles a metadata.json object and the primary 497J certification document as filed on EDGAR. Image files that may have accompanied the original submission (letterhead graphics, logos) are deliberately excluded, and the aggregate complete-submission .txt bundle is not re-extracted into the record folder either, though both remain referenced by URL in the metadata.

The monthly ZIP containers are keyed <year>/<year>-<month>.zip. Inside each archive, a single top-level directory named after the month key (for example, 2025-06/) holds every accession folder as a sibling. In the normal case, each accession folder contains exactly two files: metadata.json and one certification document whose filename is filer-specific and whose extension is either .htm (HTML) or .txt (plain-text SGML-wrapped letter).

What the underlying filing is

Form 497J is a short free-form certification letter by which an investment company represents to the Commission that no substantive changes have occurred in the definitive prospectus materials it most recently filed. Because the letter is administrative rather than disclosure-bearing, it carries no financial statements, no risk factors, and no fund holdings. The informational payload is almost entirely bibliographic: it identifies the registrant, the series or portfolios being covered, the registration statement and post-effective amendment being certified, the accession number and filing date of that prior amendment, the Rule 497 sub-paragraph under which the earlier filing would otherwise have been made, and the signer.

Two Rule 497 sub-paragraphs are typically cited inside the certification body and together cover the bulk of the population. Rule 497(c) is referenced for open-end mutual funds and ETFs amending registration statements on Form N-1A and for closed-end funds on Form N-2. Rule 497(b) is referenced for Unit Investment Trusts amending on Form S-6. The sub-rule cited inside the letter is therefore a reliable signal of the product family behind the filing, even though both use the same EDGAR form type code 497J.

Two content layers

Each record has two content layers stacked on top of the EDGAR submission:

1. A structured metadata layer — the metadata.json file — that normalizes the EDGAR submission header and filing index into a single JSON object. This layer carries the registrant identifiers, accession and timestamp information, the per-file manifest of the original submission, and, where applicable, the EDGAR series-and-class enumeration for series trusts.
2. A document layer — the certification letter itself — that carries the legal substance. The letter always sits inside an EDGAR SGML document envelope (<DOCUMENT><TYPE>497J<SEQUENCE>1<FILENAME>...<DESCRIPTION>...<TEXT> ... </TEXT></DOCUMENT>), regardless of whether the inner body is HTML markup or fixed-width plain text. Consumers parsing the body reliably begin by stripping this wrapper.

The two layers are complementary: the metadata layer is machine-structured and stable across filers, while the document layer is narrative and filer-specific in formatting but highly templated in content.

metadata.json

A single JSON object per record with a consistent top-level shape. The fields found in the dataset are:

• formType — always the literal string "497J".
• accessionNo — the dashed 18-character EDGAR accession number (e.g. "0001999371-25-008558").
• effectivenessDate — the effectiveness date of the certification, in YYYY-MM-DD form.
• filedAt — the EDGAR acceptance timestamp as an ISO 8601 string with timezone offset.
• description — a fixed dataset-level label, "Form 497J - Certification of no change in definitive materials", applied uniformly across records and not sourced from EDGAR.
• linkToFilingDetails — direct URL to the primary 497J document on sec.gov.
• linkToTxt — URL of the full EDGAR submission .txt bundle.
• linkToHtml — URL of the EDGAR filing index page (*-index.htm).
• linkToXbrl — empty string for this form type.
• documentFormatFiles — an array mirroring the EDGAR filing index, one element per file in the original submission.
• dataFiles — empty array for this form type.
• entities — an array of one or more registrant/co-registrant entity objects.
• seriesAndClassesContractsInformation — an array enumerating fund series and their classes/contracts when the filer is a series trust; may be empty.
• id — a 32-character hexadecimal internal dataset record identifier.

Each element of documentFormatFiles is a flat object with sequence (string, "1" for the primary document, or a single space for the complete-submission text bundle), type (EDGAR document type such as "497J", "GRAPHIC", or a space for the aggregate submission), description (human label such as "CERTIFICATION OF NO CHANGE", "DEFINITIVE LETTER", "497J", "GRAPHIC", or "Complete submission text file"), documentUrl (direct asset link), and size (byte count as a string). The primary 497J asset is reliably identified by type == "497J" and sequence == "1".

Each element of entities carries the filer identifier block as parsed from the EDGAR header: cik (unpadded digit string), companyName with role in parentheses (e.g. "Tema ETF Trust (Filer)"), type (the form code), fileNo (1933 Act file number, typically in the 333- series), filmNo (SEC film number), act (the registration Act, usually "33"), irsNo (IRS employer identification number, often "000000000" when not populated), fiscalYearEnd in MMDD form, stateOfIncorporation as a two-letter code, and, for certain ETF registrants, an optional tickers array.

Each element of seriesAndClassesContractsInformation, when present, describes one fund series with series (the EDGAR series identifier S + nine digits), name (series display name), and an inner classesContracts array of class/contract objects, each bearing classContract (the EDGAR class identifier C + nine digits), name, and an optional ticker. For non-series filers — closed-end funds, single-series trusts, and Unit Investment Trusts such as the numbered First Trust portfolios — this array is empty.

The primary 497J document

The certification document is delivered inside a standard EDGAR SGML envelope that opens with <DOCUMENT>, declares <TYPE>497J, a <SEQUENCE> of 1, the source <FILENAME>, and a <DESCRIPTION> (most commonly CERTIFICATION OF NO CHANGE, DEFINITIVE LETTER, or simply 497J), and then wraps the body inside a <TEXT> block that either contains HTML markup or plain text. The envelope closes with </TEXT></DOCUMENT>.

The body itself follows a consistent letter format, with modest stylistic variation across filer agents but near-identical substantive content:

1. A dateline plus a transmission notation ("Via EDGAR").
2. An addressee block naming the Securities and Exchange Commission at 100 F Street NE, Washington DC 20549, typically addressed to the Filing Desk or the Division of Investment Management.
3. A Re: line identifying the registrant and citing the 1933 Act and, where applicable, 1940 Act file numbers.
4. The Rule 497(j) operative sentence, which names the post-effective amendment being certified and states that its prospectus (and, for open-end funds, statement of additional information) "would not have differed from" the materials that would otherwise have been filed under Rule 497(c) — or, for UITs, Rule 497(b).
5. An explicit cross-reference to the underlying post-effective amendment: the accession number of that amendment, its filing date, and the form on which it was filed (commonly Form N-1A, Form N-2, or Form S-6).
6. A signature block in /s/ style giving the signer's name and title (most often counsel, an Assistant Secretary, or a Vice President of the sponsor).

Letterhead graphics embedded in the HTML flavor appear as <img> references pointing to companion files that existed in the original EDGAR submission but are not retained in the dataset folder; the documentFormatFiles manifest still lists them with type == "GRAPHIC" and preserves their original documentUrl values.

Filename conventions for the primary 497J document are filer-specific rather than dataset-normalized. Common patterns include d<hash>d497j.htm from the Donnelley filer-agent lineage, tm<id>_497j.htm from Toppan Merrill, in-house forms such as <fundname>-497j_<date>.htm or <ticker>-cover.htm, and j497.txt for fixed-width plain-text letters used by high-volume UIT bulk filers. Consumers should not match the primary document by filename; they should resolve it through the documentFormatFiles entry with type == "497J" and sequence == "1", or follow linkToFilingDetails.

Included content

Each record folder reliably includes the metadata.json structured object and the primary 497J certification document as served by EDGAR, with its SGML envelope preserved verbatim. The metadata carries the full filer identification block, the complete per-file manifest of the original EDGAR submission (including entries for files not physically extracted, such as graphics and the aggregate .txt bundle), the structured series/class enumeration for series trusts, and the full set of canonical links back to sec.gov (filing details page, filing index page, and complete submission text). The letter preserves all textual substance — signatures, file numbers, amendment accession references, and the sub-paragraph citation — that makes the certification legally interpretable.

Excluded or separate content

Image assets that accompanied the original EDGAR submission (letterhead .jpg files, logos) are excluded from the record folder, as is the aggregate complete-submission .txt bundle. Their existence is not erased: each excluded file remains represented as an entry in documentFormatFiles with its own type, description, size, and documentUrl, so the manifest is complete even where the asset itself is not retrieved. Because Form 497J is not a disclosure document, there are no structured exhibits, no financial data files, and no structured financial data attachments to include or exclude — dataFiles is empty and linkToXbrl is blank as a consequence of the form type, not of any dataset-side trimming.

The underlying definitive prospectus materials being certified are not part of a 497J record. Those materials are the prior post-effective amendment (and any prior Rule 497(a)–(f) filing) referenced inside the letter, and they live under different accession numbers and different EDGAR form types (N-1A/A, N-2/A, S-6, 497, 497K, etc.). The 497J record only carries the certification and its metadata, pointing to those prior materials by accession number and filing date rather than republishing them.

Changes in required content or structure over time

Rule 497(j) has been a stable part of Regulation C since well before EDGAR's electronic-filing era began in 1994, and the certification has remained administrative and bibliographic throughout. The dataset spans filings from January 1994 to the present, and the content of a 497J letter in 1994 and in 2025 is substantively the same: identification of the registrant, identification of the post-effective amendment, and the certification sentence. The population mix has shifted gradually — ETFs on Form N-1A have grown to dominate the modern flow, whereas the 1990s population leaned more heavily on traditional open-end mutual funds and Unit Investment Trusts — but the required content of the individual letter has not changed materially, and no Commission rulemaking has introduced new mandatory sections or disclosures inside a 497J. Because the form is not a disclosure vehicle, the layered expansion of governance, risk-factor, compensation, and structured-data requirements that reshaped substantive investment-company filings over the same period did not propagate into 497J content.

Changes in data format over time

Format evolution is modest and follows the general EDGAR trajectory rather than a 497J-specific arc. In the ASCII/SGML era of the 1990s and early 2000s, 497J letters were submitted as plain-text files wrapped in the EDGAR <DOCUMENT> envelope; the plain-text flavor is still actively used today by high-volume bulk filers such as the First Trust UIT complex, whose letters arrive as fixed-width j497.txt files with a boilerplate body in which only the trust identifier, file number, and amendment date vary from one filing to the next. HTML-bodied 497J letters became the norm as EDGAR broadened HTML support, and today most filings arrive as .htm documents produced by filer agents such as Donnelley or Toppan Merrill, while smaller filers use in-house filename conventions. Across both flavors the SGML document envelope remains unchanged, which makes envelope-stripping a reliable first step regardless of filing vintage.

Interpretation notes

Several nuances matter for downstream use.

• Resolving the primary asset. The certification document should be located through documentFormatFiles[] by matching type == "497J" and sequence == "1", or by following linkToFilingDetails. Filenames are filer-specific and should not be treated as a primary key.
• Coverage of multiple series under one accession. A single 497J can certify an entire fund family at once. When seriesAndClassesContractsInformation is populated it is the authoritative enumeration of covered products, and the number of distinct series identifiers under one accession can be substantial. For non-series filers the array is empty, and coverage is implied by the single entities[] registrant.
• Sub-rule citation lives in the narrative. The operative sub-paragraph of Rule 497 cited inside the letter body (497(b) versus 497(c)) is not exposed as a structured metadata field and must be read out of the text; it is, however, a strong signal of the underlying registration form (N-1A/N-2 versus S-6).
• Two description fields, two sources. The top-level description inside metadata.json is a fixed dataset-level label. The EDGAR-sourced description of each filed asset is carried separately inside each entry of documentFormatFiles.
• Manifest completeness versus extraction. Letterhead graphics and the aggregate submission text file are represented in documentFormatFiles but not extracted to disk. Consumers who need the complete original submission must fetch it via linkToTxt rather than expect it in the record folder.
• Envelope-stripping before parsing. Whether the body is HTML or plain text, the <DOCUMENT>...<TEXT> ... </TEXT></DOCUMENT> wrapper is always present and should be removed before any body-level parsing or text-extraction pass.

Who Files or Publishes This Dataset, and When

Who files Form 497J

Each record in this dataset is a Form 497J submission to EDGAR by a registered investment company acting as a Securities Act registrant. The filer population is narrow: only issuers that maintain an effective Securities Act of 1933 registration statement and are regulated under the Investment Company Act of 1940 have occasion to file under Rule 497, and therefore under paragraph (j).

The filer classes are:

• Open-end management investment companies (mutual funds) registered on Form N-1A. These are the dominant users of Rule 497 and of 497J, because they maintain continuously effective registration statements updated at least annually.
• Exchange-traded funds (ETFs) organized as open-end funds and registered on Form N-1A, using the same Rule 497 regime as mutual funds.
• Closed-end management investment companies registered on Form N-2 that conduct continuous or delayed offerings (including interval funds and tender offer funds).
• Unit investment trusts (UITs) registered on Form S-6 offering units on a continuous basis.

The legal filer is the registrant itself (the trust or corporation), signing through authorized officers or filing agents. A single 497J frequently covers multiple series or classes, because Rule 497 operates at the registrant level. Advisers, distributors, transfer agents, and shareholders are not the filing party.

Operating companies, foreign private issuers, business development companies reporting solely under the Exchange Act, and private funds relying on Section 3(c)(1) or 3(c)(7) exclusions do not use Form 497J.

Regulatory framework

Form 497J is the EDGAR submission type used to make filings under Securities Act Rule 497(j), codified at 17 CFR 230.497(j). Rule 497 as a whole governs investment company post-effective prospectus filings:

• paragraphs (a)–(c) require filing of definitive prospectuses and Statements of Additional Information after effectiveness of the registration statement or a post-effective amendment;
• paragraph (d) covers supplemental or "stickered" prospectuses amending a previously filed prospectus;
• paragraphs (e)–(f) address advertising and supplemental sales literature deemed a prospectus.

Rule 497(j) permits a registrant to satisfy a Rule 497(a)–(f) filing obligation by submitting a short certification that the form of prospectus used (or to be used) does not differ from the definitive version already on file. Form 497J is the administrative vehicle for that certification; it attests to the absence of change rather than transmitting disclosure.

497J is typically used in coordination with post-effective amendments filed under Rule 485 (open-end funds and ETFs on Form N-1A) and Rule 486 (closed-end interval funds on Form N-2). Where the definitive prospectus resulting from a Rule 485(b) or Rule 486(b) amendment is identical to what is already on file, Rule 497(j) allows a certification in place of refiling the full prospectus.

Triggering event and timing

Form 497J is event-driven, not periodic. It is triggered whenever the registrant would otherwise be required to file a definitive prospectus under Rule 497(a)–(f), but the form of prospectus being used is unchanged from the version previously filed.

Typical triggers:

• Post-effective amendment taking effect under Rule 485(a), 485(b), or Rule 486, where the resulting definitive prospectus is identical to the version already on file.
• First use of a prospectus following effectiveness. Rule 497(a) requires a definitive prospectus to be filed no later than the fifth business day after first use (or the registration statement's effective date, whichever is later). A 497J certification satisfies this obligation on the same timetable when the document in use is unchanged.
• Annual update cycle. Mutual funds file annual Rule 485(b) amendments; where the resulting definitive prospectus matches the version already filed under Rule 497, the registrant may submit a 497J instead of a full refiling.

Rule 497(j) does not create an independent deadline. The 497J is due on the same schedule as the Rule 497(a)–(f) filing it replaces, most commonly the five-business-day window tied to first use.

Important distinctions

• 497J vs. 497 vs. 497K. A 497 filing carries the actual definitive prospectus or sticker; a 497J carries only the no-change certification; a 497K carries a summary prospectus filed under Rule 498. All three satisfy variants of the same Rule 497 obligation.
• Not available when content changes. If the prospectus has been modified in any respect (sticker updates, supplements, or changes flowing from a Rule 485(a) amendment), Rule 497(j) is unavailable and the registrant must file the actual materials under the applicable Rule 497 paragraph.
• Registrant-level filer of record. The filer is the legal registrant (trust or corporation), even when the certification references many series or share classes.
• Adjacent populations outside the regime. Operating company issuers file definitive prospectuses under Rule 424 (not Rule 497). BDCs that do not maintain a Rule 497-bearing registration statement do not use 497J. Private funds never file 497J because they have no Rule 497 obligation.
• EDGAR coverage. Rule 497(j) predates EDGAR; paper certifications under the same rule existed before electronic filing. Dataset coverage beginning January 1994 reflects the phase-in of mandatory EDGAR filing for investment companies.

How This Dataset Differs From Similar Datasets or Filings

Form 497J sits inside the Rule 497 prospectus-filing family used by registered investment companies, but it plays a narrow, purely administrative role. The sharpest comparisons are to (1) other Rule 497 sub-types that carry actual prospectus content, (2) the Rule 485 and Rule 486 post-effective amendment regimes that update the registration statement itself, (3) Form 24F-2, the other common "status-only" fund filing, and (4) the underlying registration forms (N-1A, N-2, S-6) on which the whole chain rests. In every comparison the same boundary applies: 497J certifies non-change, while nearly every related filing transmits substantive content or effects a registration event.

Form 497 (definitive materials under Rule 497(a)–(f))

Form 497 is the parent of the 497J filing. Submissions under paragraphs (a) through (f) of Rule 497 deliver definitive prospectuses, SAIs, and supplements ("stickers") after a fund's registration statement is effective, and are the authoritative source of current disclosure text. Form 497J, filed under paragraph (j) of the same rule, carries no disclosure content. It is a short certification that the materials most recently filed under (a)–(f) remain accurate, so no new 497 submission is required for the period. Extract prospectus text from 497; treat 497J as a pointer that a prior 497 is still current.

Form 497K (summary prospectus under Rule 498)

Form 497K is the summary prospectus authorized by Rule 498 for open-end funds — a condensed, standardized document covering fees, strategies, risks, performance, managers, and purchase/sale/tax information that may be delivered in lieu of the full statutory prospectus. Like 497(a)–(f), it contains substantive investor-facing content. 497J neither delivers nor updates summary-prospectus content and cannot keep a 497K current if its facts actually change; it only attests that they have not.

Post-effective amendments on 485APOS / 485BPOS / 485BXT (Rule 485)

Rule 485 governs post-effective amendments to Form N-1A registration statements (and certain UITs). 485APOS is filed for SEC staff review before effectiveness; 485BPOS is designed to become effective automatically or on a designated date; 485BXT designates a new effective date. These filings revise the registration statement itself — prospectus, SAI, exhibits, financials. 497J neither amends the registration statement nor restates prospectus content; it is the mirror image, affirming that nothing has changed since the last definitive Rule 497 filing. Use the 485 series to track substantive disclosure updates; use 497J to track non-change attestations.

486APOS / 486BPOS (Rule 486, closed-end interval funds)

Rule 486 is the parallel post-effective amendment regime for eligible closed-end interval funds registered on Form N-2. Like the 485 series, 486 filings are substantive amendments to the registration statement. 497J is not a registration amendment and is not part of the 486 series; the two regimes address different events and do not substitute for each other.

Form 24F-2 (annual notice under Rule 24f-2)

Form 24F-2 is the filing most structurally similar to 497J in cadence and brevity: both are short compliance documents rather than disclosure vehicles. The content is different. 24F-2 is an annual notice under Section 24(f) of the Investment Company Act and Rule 24f-2 reporting aggregate shares sold during the fiscal year, redemption offsets, net sales, and the associated registration-fee calculation. 497J carries no sales data and no fee math; it is a textual certification of prospectus continuity. The two are easy to confuse as "housekeeping" filings but address different statutory obligations.

Form N-1A, N-2, S-6 (underlying registration statements)

These are the foundational registration forms for open-end management companies (N-1A), closed-end management companies (N-2), and UITs issuing redeemable securities (S-6). A 497J filing presupposes a prior N-1A/N-2/S-6 registration and a subsequent 497(a)–(f) filing; the certification is meaningless without that chain. For a full disclosure history, the registration statement is the starting point, 485/486 amendments and 497(a)–(f) filings carry ongoing substantive content, and 497J is an audit-trail marker of non-change between those events.

Other 497 sub-types (497AD, 497VPI, 497VPU)

Within the 497 family, 497AD covers advertising materials filed under Rule 482, while 497VPI and 497VPU are the initial and updating summary prospectuses for variable contracts under Rule 498A. All of these carry substantive content — advertising copy or summary-prospectus text. 497J is the only 497 sub-type that is content-free by design and the only one that references prior 497 filings instead of supplying new disclosure. Exclude 497J from any prospectus- or advertising-text extraction pipeline; target it specifically only when auditing certification cadence.

Key differences at a glance

• Content: 497J is a negative attestation; 497(a)–(f), 497K, 497AD, 497VPI/VPU, 485/486 amendments, and N-1A/N-2/S-6 all transmit substantive disclosure.
• Legal effect: 485/486 filings can change a registration statement; 497J cannot change anything.
• Data shape: 24F-2 produces numeric sales and fee data; 497J produces only a short textual certification.
• Dependency: 497J is only meaningful relative to a prior 497(a)–(f) filing on the same registration.

Form 497J is a compliance checkpoint, not a disclosure document. It cannot substitute for a supplement when facts change, cannot update a summary prospectus, and cannot amend a registration statement. It uniquely represents a fund's affirmative statement that previously filed definitive materials remain accurate, making it the right dataset for questions about filing cadence, compliance behavior, and non-change timelines — and the wrong dataset for any question about the content of fund disclosure.

Who Uses This Dataset

Because Form 497J is a content-free certification — the registrant attests that the previously filed definitive prospectus remains current and that nothing under Rule 497(a)–(f) has changed — the dataset's value is in the metadata envelope (accession number, CIK, filing date, Rule 497(j) cite, and the reference back to the prior definitive materials), not the document body. Users care about timing, sequencing against related 485 and 497 filings, and completeness.

Fund operations and fund accounting teams

Operations groups inside fund complexes and their outsourced administrators track the prospectus lifecycle for every registered series and class. They reconcile each 497J's CIK, accession number, filing date, and prior-materials reference against an internal prospectus calendar covering 485BPOS post-effective amendments, 497(c) supplements, and Rule 497(e) stickers. The dataset confirms the (j) certification was filed, links it to the correct underlying prospectus, and releases downstream printing and transfer-agent workflows that wait on a confirmed "no change" flag before shareholder mailings.

Registration counsel and 1940 Act compliance officers

In-house fund counsel, chief compliance officers, and attorneys at fund administrators and filing agents use the dataset as an authoritative log of Rule 497(j) usage. They audit their own filing history fund-by-fund, verify that every definitive-filing obligation was discharged, and spot cases where a 497J was filed in lieu of a substantive 497 re-filing. Registrant CIK, filing date, and the cross-reference to the prior accession number are the operative fields. They also benchmark (j) cadence and timing against peer complexes.

SEC examiners and enforcement attorneys

Examination and enforcement staff reconstruct the 485 to 497 to 497J sequence for any registrant under review. The dataset supports checks such as: was the 497J filed within the expected window after a post-effective amendment went effective, does the (j) cite correctly reference the prior definitive materials, and are there complexes filing 497J when substantive changes had in fact occurred. The full population back to 1994 lets staff establish cadence baselines, flag late filings, and identify missing certifications.

Fund research firms and market data vendors

Fund research providers, index and benchmark vendors, and prospectus-text feed operators rebuild accurate prospectus timelines for mutual funds, ETFs, closed-end funds, and variable-insurance products. A 497J confirms the prior definitive prospectus was still operative on the certification date, which keeps "prospectus as of" pointers stable instead of triggering a false new-document assumption. CIK, filing date, and the prior accession reference feed document-version mapping tables.

Legal-tech and RegTech vendors

Vendors building fund filing trackers and compliance calendars use the dataset to power deadline monitoring, exception detection, and document-lineage features. The 1994-forward history calibrates expected-cadence models: given a fund's past 485 and 497 pattern, when is a 497J expected and when is its absence an anomaly. Accession-level JSON metadata plus filing date and registrant identifiers is sufficient without any document parsing.

Quantitative and event-study researchers

Academic and buy-side researchers studying fund flows, expense-ratio changes, manager transitions, or prospectus-driven disclosure events use 497J timestamps as clean event boundaries. Because the filing certifies no change, it marks the close of a prospectus period without introducing new information, serving as a control interval against windows bounded by substantive 497 filings. Filing timestamp, CIK, and the prior-accession link drive event-window construction.

Audit and assurance teams

External auditors and internal audit functions serving investment company clients validate Rule 497 compliance end-to-end. During annual testing they pull every 497J filed by the client, tie each to the underlying definitive prospectus, and confirm timely filing, correct prior-materials reference, and appropriate use given no substantive change. The dataset provides an independent source-of-record view that strengthens workpapers supporting Rule 38a-1 program assessments.

Specific Use Cases

The workflows below use the Form 497J accession-level envelope directly — CIK, accession number, filing date, the reference to the prior post-effective amendment, and the Rule 497 sub-paragraph cited in the letter body.

• Closing out a prospectus cycle on a fund-complex calendar. Operations and transfer-agent teams pull every 497J filed by a complex's CIKs in a given quarter, match each record's prior-accession reference to the corresponding 485BPOS or 497(c) entry on the internal prospectus calendar, and release the downstream "no change" flag that gates shareholder mailings and website prospectus-as-of timestamps. The entities[] CIK, effectivenessDate, and the amendment accession cited inside the letter body are the operative fields.

• Auditing Rule 497(j) usage fund-by-fund. Compliance officers and external auditors reconstruct the 485 to 497 to 497J chain for a registrant under review. For each 497J they verify that the cited prior accession resolves to a real post-effective amendment, that the filing date sits inside the expected window after effectiveness, and that the seriesAndClassesContractsInformation enumeration covers every series represented to be unchanged. Gaps and mismatches feed the Rule 38a-1 workpapers.

• Maintaining stable "prospectus as of" pointers in fund-data feeds. Fund research and index vendors use 497J timestamps to keep document-version tables stable: a 497J on a given CIK means the last definitive prospectus remains current on that date, so version pointers are extended rather than bumped. CIK, filing date, and the prior-accession reference are the only fields needed; the document body is ignored.

• Segmenting the population by product family via the in-letter sub-rule cite. Because Rule 497(b) is cited for UITs on Form S-6 and Rule 497(c) for open-end funds and ETFs on N-1A (and closed-end funds on N-2), a one-pass text extraction of the sub-paragraph citation from the envelope-stripped letter body splits the 497J population into UIT versus management-company flows. Combined with the tickers array and the series/class enumeration, this produces a clean product-family breakdown without needing to join against registration-form metadata.

• Event-window construction for prospectus-driven studies. Quantitative researchers use 497J filedAt timestamps as clean non-event boundaries when studying fund flows, expense changes, or manager transitions: the certification explicitly asserts no new information, so 497J dates bracket control intervals between substantive 497(a)–(f) and 485 events. CIK plus timestamp is sufficient; no body parsing is required.

• Detecting missing or late certifications across a 1994-present baseline. RegTech vendors and SEC examiners train expected-cadence models on each registrant's historical 485, 497, and 497J sequence and flag CIKs whose recent pattern breaks the baseline — for example, a post-effective amendment with no subsequent 497 or 497J inside the usual window. The accession-level JSON is enough to drive the anomaly detector; the letter body is only consulted when a flagged case needs manual review.

• Building a bulk-filer behavioral profile for UIT sponsors. High-volume UIT complexes (notably the First Trust portfolios) file fixed-width j497.txt letters with near-identical boilerplate differing only in trust identifier, 1933 Act file number, and amendment date. Grouping records by sponsor CIK and counting 497J filings per month yields a direct measure of UIT series-launch and refresh cadence that is hard to derive cleanly from the 497 stream alone.

Dataset Access

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

This endpoint returns metadata describing the Form 497J Files Dataset, including its name, description, last updated timestamp, earliest sample date (1994-01-01), total record and size counts, form types covered (497J), container format (ZIP), included file types (TXT, JSON, HTML, PDF), the full dataset download URL, and the list of individual container files with per-container size, record count, updated timestamp, and download URL. Use this endpoint to monitor which containers were refreshed in the most recent run and decide on a day-by-day basis which containers to re-download. This endpoint does not require an API key.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-68e4-88ca-7cf09ae57014",
        

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

          4
            "name": "Form 497J Files Dataset",
        

          5
            "updatedAt": "2026-04-23T02:56:53.579Z",
        

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

          7
            "totalRecords": 144349,
        

          8
            "totalSize": 359018658,
        

          9
            "formTypes": ["497J"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

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

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

          16
                "size": 13818783,
        

          17
                "records": 154,
        

          18
                "updatedAt": "2026-04-23T02:56:53.579Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

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

Downloads the complete Form 497J Files Dataset as a single ZIP archive covering all filings from January 1994 through the latest refresh. This endpoint requires an API key.

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

Downloads one monthly container archive, which is useful for incremental updates or for retrieving a specific time range without pulling the full dataset. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form 497J, the EDGAR submission type used by registered investment companies to make filings under Securities Act Rule 497(j) (17 CFR 230.497(j)). A 497J is a short certification that the definitive prospectus materials most recently filed under Rule 497(a)–(f) have not changed.

What does one record in this dataset represent?

One record is one EDGAR submission of form type 497J, identified by its accession number. Physically, each record is a sub-folder inside a monthly ZIP container, holding a normalized metadata.json object plus the primary 497J certification document (HTML or plain-text SGML) as served by EDGAR.

Who is required to file Form 497J?

Only registered investment companies with an effective Securities Act of 1933 registration statement file 497J: open-end mutual funds and ETFs on Form N-1A, closed-end funds on Form N-2 (including interval and tender offer funds), and Unit Investment Trusts on Form S-6. Operating companies, foreign private issuers, BDCs reporting solely under the Exchange Act, and private funds relying on Section 3(c)(1) or 3(c)(7) exclusions do not use Form 497J.

When is a 497J filed?

Form 497J is event-driven rather than periodic. It is filed whenever the registrant would otherwise be required to submit a definitive prospectus under Rule 497(a)–(f) — most commonly following a Rule 485 or Rule 486 post-effective amendment or within the five-business-day window tied to first use — and the form of prospectus actually in use has not changed from the version already on file.

How does this dataset differ from the Form 497 Files Dataset?

Form 497 Files Dataset carries the actual definitive prospectus, Statement of Additional Information, or supplement ("sticker") text and is the authoritative source of current disclosure. Form 497J carries no disclosure content; it is a negative attestation that the most recent 497 filing remains accurate. Use 497 for prospectus text; use 497J for compliance cadence and non-change timelines.

What file formats are inside the dataset?

File types encountered across the dataset are TXT, JSON, HTML, and PDF, delivered inside monthly ZIP containers. In practice, each record folder resolves to a metadata.json manifest plus a single primary certification document that is either an .htm file (most modern filings) or a plain-text .txt file wrapped in an EDGAR SGML <DOCUMENT> envelope (common for high-volume UIT bulk filers such as the First Trust complex).

What time period does the dataset cover?

The dataset covers every Form 497J submission accepted by EDGAR from January 1, 1994 (the earliest sample date, reflecting the phase-in of mandatory EDGAR filing for investment companies) through the most recent refresh, with new filings added on an ongoing basis.