Form N14EL24 Files Dataset

The Form N14EL24 Files Dataset is a closed historical archive of registration statements filed on EDGAR under the submission types N14EL24 and N14EL24/A — the variant of Form N-14 used by open-end management investment companies, unit investment trusts, and certain other registered investment companies to register securities issued in fund-to-fund mergers, consolidations, and other Rule 145 reorganizations while simultaneously declaring an election under Rule 24f-2 of the Investment Company Act of 1940 to register an indefinite number of shares. Each record represents one EDGAR submission identified by accession number, packaged as a directory containing a structured metadata.json and one or more plain-text document-N.txt files for the registration statement and its exhibits. The dataset spans the full active life of the submission type, from January 1994 — when EDGAR opened to investment-company filings — through the form's discontinuation in January 1998 under EDGAR Release 5.40, after rule amendments made the Rule 24f-2 election automatic for eligible registrants. Records are distributed as monthly ZIP containers organized by year, with TXT and JSON file types inside.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset packages every EDGAR submission filed under the N14EL24 and N14EL24/A form types across the closed January 1994 to January 1998 window. The underlying form, Form N-14, is the Securities Act of 1933 registration form used by open-end management investment companies (mutual funds), closed-end funds, and unit investment trusts to register securities issued in connection with business-combination transactions — typically fund-to-fund mergers, reorganizations into a master/feeder structure, conversions of unit investment trusts, and other reorganizations governed by Rule 145 of the Securities Act. The submission type N14EL24 is the Form N-14 variant that additionally carries an explicit declaration of election under Rule 24f-2 of the Investment Company Act of 1940, which historically allowed an open-end fund or UIT to register an indefinite number of shares while paying registration fees on the basis of net sales after the close of the fiscal year. The /A suffix denotes a pre-effective amendment or post-effective amendment to a previously filed N14EL24, used to update the prospectus/proxy, refile or substitute exhibits, respond to staff comments, or correct prior submissions.

In substance, a Form N-14 functions as a hybrid document: it is simultaneously a Securities Act registration statement for the new shares to be issued by the acquiring fund and, in most fund-merger transactions, a proxy statement soliciting target-fund shareholder approval of the reorganization. It therefore typically takes the form of a combined "Prospectus/Proxy Statement," accompanied by a Statement of Additional Information (SAI) that is either bound in or incorporated by reference, the financial statements of the acquiring and target funds, and the legal and tax opinions required by the form's exhibit instructions.

The N14EL24 submission type was retired effective January 1998 with EDGAR Release 5.40, after rule amendments rendered the Rule 24f-2 election automatic for all eligible registered investment companies; thereafter, business-combination registration statements migrated to the plain N-14 and N-14/A submission types without the explicit election declaration. The dataset is distributed as a ZIP container format with TXT and JSON file types, and records are packaged into monthly ZIP archives organized as <year>/<year>-<month>.zip.

Content Structure of a Single Record

One record in the Form N14EL24 Files Dataset is a single registration-statement submission filed on EDGAR under the form type N14EL24 or its amendment variant N14EL24/A, identified by its SEC accession number. On disk, each record materializes as a directory whose name is the 18-digit accession number with hyphens removed (for example, accession 0000091155-97-000443 becomes the folder 000009115597000443). Inside that directory sits exactly one metadata.json describing the EDGAR submission header and document inventory, plus one or more document-N.txt files holding the plain-text bodies of the constituent EDGAR documents in the order they were submitted, where N is the EDGAR <SEQUENCE> number assigned to that document. The accession-number folder is the natural primary key.

A record has two layers: a structured metadata layer and an unstructured document-bodies layer.

Structured layer: metadata.json

metadata.json is a single JSON object that mirrors the EDGAR submission header and tells the reader how to interpret the sibling document-N.txt files. Its principal fields are:

• formType — either "N14EL24" or "N14EL24/A".
• accessionNo — canonical hyphenated accession number (e.g. "0000091155-97-000443").
• filedAt — ISO-8601 filing timestamp with the EDGAR Eastern-time offset.
• description — human-readable form description, annotated with [Amend] for /A variants.
• linkToFilingDetails, linkToTxt, linkToHtml — direct URLs back to the EDGAR Archives for the issuer's CIK directory, the consolidated submission text file, and the EDGAR index page.
• linkToXbrl — present in the schema but always empty for this form type.
• documentFormatFiles — an ordered array describing each constituent document; each entry carries sequence (matching the document-N.txt suffix), size (raw byte count from EDGAR), type (the EDGAR document or exhibit code such as N14EL24, EX-99.11, EX-99.12, EX-99.14.A, EX-99.14.B, EX-99.17), description, and a documentUrl. A trailing entry with sequence: " " and description: "Complete submission text file" describes the consolidated .txt submission on EDGAR rather than a separate body file in the archive.
• entities — array of parties on the filing. The registrant is flagged as (Filer) in companyName, and each entity carries cik, companyName, irsNo, fileNo (the 333- or 33- Securities Act file number assigned to the registration), stateOfIncorporation, fiscalYearEnd (MMDD), act (typically "33" for the Securities Act of 1933), sic, filmNo, and type.
• id — 32-character hex content hash used as the dataset's internal record identifier.
• seriesAndClassesContractsInformation — array reserved for the EDGAR series/class structure introduced after 2006; for 1990s N14EL24 submissions it is essentially always empty.
• dataFiles — array reserved for XBRL-era structured-data attachments; always empty for this form type.

Unstructured layer: document-N.txt

Each document-N.txt holds the body of one EDGAR document with the SGML submission envelope already removed. The original <DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, and <TEXT> wrapper tags have been stripped; the EDGAR <TYPE> for each file is recovered by joining its sequence number against documentFormatFiles[].type. The file at document-1.txt is always the primary submission (the Form N-14 registration statement itself); higher-numbered files are exhibits in EDGAR sequence order.

The bodies are 1990s EDGAR ASCII: fixed-width typewriter text hard-wrapped near column 80, with horizontal rules drawn from ----- and ===== characters, and with embedded legacy EDGAR financial-table markup tags such as <TABLE>, <CAPTION>, <S>, and <C> appearing inline inside fee tables, capitalization tables, financial-highlights blocks, and signature blocks. These embedded tags are content rather than envelope and are preserved verbatim inside the document bodies.

The file types found in the dataset are TXT and JSON: the TXT files are the document bodies, and the JSON file is metadata.json.

Component-by-component breakdown of the underlying filing

document-1.txt is the registration statement on Form N-14 itself and is structured in roughly the following order.

1. Facing page / cover page. Identifies the registrant, the SEC file number on the Securities Act registration (the 333- prefix series for post-1995 filings, the legacy 33- series for older ones), the registrant's address, the name and address of the agent for service, the approximate date of the proposed public offering, and the title of the securities being registered.

2. Rule 24f-2 declaration of election. A short statement, characteristic of this submission type, in which the registrant declares its election under Rule 24f-2 of the Investment Company Act of 1940 to register an indefinite number of securities. This declaration is the structural feature that distinguishes N14EL24 from a plain N-14.

3. Calculation of registration fee table. A tabular block listing the title of each class of securities being registered, amount being registered, proposed maximum offering price per unit, proposed maximum aggregate offering price, and the registration fee. Under the Rule 24f-2 election the amount and price columns are typically annotated with footnotes describing the indefinite-shares mechanism. Rendered using the embedded <TABLE>/<S>/<C> markup.

4. Cross-reference sheet. A required Form N-14 element that maps each numbered Item of Form N-14 (Items 1 through 17, organized into Part A — Information Required in the Prospectus, Part B — Information Required in a Statement of Additional Information, and Part C — Other Information) to the corresponding caption or location in the prospectus/proxy statement. It serves as a navigational index for the SEC staff and for sophisticated readers, and is the canonical bridge between Form N-14's item numbering and the prose of the combined prospectus/proxy.

5. Letter to shareholders. A cover letter from the target fund's board or president addressed to the target-fund shareholders, describing the proposed transaction in plain language and recommending approval.

6. Notice of special meeting of shareholders. Formal notice setting the meeting date, time, location, record date, and matters to be voted upon — typically the approval of the Agreement and Plan of Reorganization and any related proposals.

7. Combined Prospectus and Proxy Statement (Part A — Items 1–6). The substantive disclosure document. Typical sections include: a Q&A or summary; a comparison fee table contrasting current and pro forma expenses for the acquiring and target funds; the proposal description; the reasons for the reorganization and the board's considerations; the terms of the Agreement and Plan of Reorganization (exchange ratio, valuation methodology, assumed liabilities, conditions to closing); federal income tax consequences (referencing the Section 368(a) reorganization opinion); comparison of investment objectives, principal investment strategies, and principal risks of the two funds; comparison of fundamental and non-fundamental investment policies; comparison of management, advisory fees, and distribution arrangements; comparison of shareholder services and purchase, redemption, and exchange procedures; capitalization tables before and after the reorganization on a pro forma basis; voting information, including required vote, quorum, and proxy solicitation costs; and information about ownership of fund shares by 5% holders and management.

8. Statement of Additional Information (Part B — Items 7–14). Either bound directly into the document or incorporated by reference. Where included, it provides additional detail on investment policies, management, brokerage allocation, portfolio holdings, and the historical financial information of both the acquiring and target funds.

9. Other Information (Part C — Items 15–17). Lists the exhibits filed with the registration statement (cross-referencing each by exhibit number), the undertakings (Rule 145(c) undertakings, indemnification undertakings, undertakings to deliver an opinion of counsel as to tax matters at closing), and similar non-prospectus content.

10. Signature pages. Signed by the registrant, the principal executive officer, the principal financial and accounting officer, and a majority of the trustees or directors, in compliance with Section 6(a) of the Securities Act. Signature blocks are commonly rendered using the embedded <TABLE>/<S>/<C> markup to keep names and titles aligned in fixed-width text.

11. Financial statements and pro forma financial information. Either embedded directly in the primary submission or filed as exhibits. Typical components are the audited financial statements of both the acquiring and target funds (statements of assets and liabilities, statements of operations, statements of changes in net assets, schedules of investments, financial highlights, and notes), pro forma combined financial statements giving effect to the reorganization, and the related auditor's consent (filed separately as an exhibit).

The remaining document-N.txt files in the record are the exhibits, in EDGAR sequence order. Exhibit numbering follows the table of exhibits set out in Item 16 of Part C of Form N-14, which assigns each exhibit class a fixed integer (charter; by-laws; voting trust agreement; instruments defining rights of security holders; agreement and plan of reorganization; advisory contracts; underwriting contracts; bonus, profit-sharing, pension or similar plans; custodian agreements; opinion and consent of counsel as to legality; opinion and consent of counsel on tax matters; other material contracts; other opinions and consents; financial statements omitted from Item 14; powers of attorney; form of proxy; and so on). The EDGAR <TYPE> codes such as EX-99.11, EX-99.12, and EX-99.14.A mirror this scheme directly, with letter suffixes (.A, .B, ...) used to distinguish multiple exhibits filed under the same item number. The exhibits commonly observed and their roles are:

• EX-99.11 — Opinion and consent of counsel as to legality. A short legal opinion (typically tens to low hundreds of lines) from counsel to the acquiring fund, opining that the shares being registered, when issued in accordance with the Agreement and Plan of Reorganization, will be legally issued, fully paid, and non-assessable, together with the firm's consent to the use of its opinion and to references to the firm in the prospectus.
• EX-99.12 — Tax opinion. A "should" or "will" opinion from tax counsel addressing the federal income tax consequences of the reorganization to the funds and their shareholders, typically opining that the transaction will qualify as a reorganization under Section 368(a) of the Internal Revenue Code, that no gain or loss will be recognized by either fund or by the shareholders on the exchange of shares, and that the shareholders' tax basis and holding period will carry over. In practice this exhibit is sometimes filed as a form of opinion at the registration stage and is then re-filed in final form on closing pursuant to the undertakings in Part C.
• EX-99.13 — Other material contracts. When present, captures advisory, distribution, sub-advisory, or shareholder-services agreements not previously filed.
• EX-99.14, EX-99.14.A, EX-99.14.B — Other opinions and consents. Used for state-law counsel opinions (for example, Massachusetts business-trust counsel opining on matters of state law), supplemental consent letters from independent accountants, and other ancillary opinions and consents required by the form.
• EX-99.16 — Powers of attorney. Authorizing officers and trustees to execute amendments to the registration statement.
• EX-99.17 — Form of proxy card / additional exhibits. When filed in the submission rather than separately, the form of proxy card distributed to target-fund shareholders, plus any additional financial-data schedules or supplementary exhibits.

Document sizes within a record are heavily skewed: the registration statement (document-1.txt) frequently runs to thousands of lines of ASCII text (a typical fund-merger N-14 prospectus/proxy is several hundred kilobytes), while individual exhibit opinions are commonly 25 to 150 lines. Single-document records — those consisting only of document-1.txt — also occur and represent submissions in which all exhibits were incorporated by reference to prior filings.

Included content

Each record packages the EDGAR header for the filing in metadata.json together with the full text of every non-image document submitted under that accession number. Concretely, a record contains:

• the structured EDGAR header, document inventory, and entity table in metadata.json;
• the body of the primary registration statement (document-1.txt), including the cover page, Rule 24f-2 election, fee table, cross-reference sheet, prospectus/proxy statement, SAI text where bound in, Part C content, signature pages, and any embedded financial statements;
• the body of every exhibit submitted with the filing as a separate EDGAR document — legal opinions, tax opinions, accountant consents, the agreement and plan of reorganization (where filed as a separate exhibit rather than embedded), forms of proxy, powers of attorney, and any supplementary financial schedules.

Excluded or separate content

• Image files. GIFs, JPGs, and similar binary graphics referenced inside the original EDGAR submission are deliberately excluded. The corresponding documentFormatFiles entries may still appear in metadata.json, but no document-N.txt body is materialized for them.
• Consolidated submission .txt. The trailing documentFormatFiles entry with sequence: " " and description: "Complete submission text file" describes the consolidated .txt submission as hosted on EDGAR; that consolidated file is referenced by URL via linkToTxt but is not stored separately in the ZIP, since its content is already represented by the per-document document-N.txt files.
• SGML envelope tags. The <DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, and <TEXT> wrapper tags that originally framed each document inside the consolidated EDGAR submission have been stripped from the document bodies; the equivalent information is preserved in structured form inside metadata.json -> documentFormatFiles.
• Incorporated-by-reference material. Disclosure incorporated by reference rather than physically filed — for example, the acquiring fund's existing Form N-1A prospectus or SAI, or audited financial statements previously included in an annual report on Form N-SAR or N-30D — is not bundled into the record. Only the documents physically transmitted under the N14EL24 accession number are present. Recovery of incorporated material requires following the file-number references and CIK identifiers in metadata.json to other EDGAR filings.

Changes in required content and structure over time

Across the form's active life from January 1994 to January 1998 the body of Form N-14 itself was relatively stable: the seventeen-Item, three-Part structure (Parts A, B, and C with Items 1–17) was already in place from the form's adoption, and the principal disclosure components — cover page, cross-reference sheet, prospectus/proxy statement, SAI, exhibit list, undertakings, and signatures — remained recognizable throughout. Two structural drivers nevertheless affected the contents of N14EL24 records over this window:

• Securities Act file-number transition. Earlier filings carried legacy 33- series file numbers, while later filings carry 333- series numbers issued under EDGAR's modernized registration infrastructure. This is reflected both in the fileNo field of metadata.json -> entities and on the cover page of document-1.txt.
• Discontinuation of the explicit Rule 24f-2 election. The N14EL24 submission type itself was retired in January 1998 under EDGAR Release 5.40 because rule amendments made the Rule 24f-2 election automatic for all eligible registered investment companies. Inside the records this means the explicit Rule 24f-2 declaration on the cover/facing page of document-1.txt and the indefinite-shares footnotes in the fee table reflect a disclosure regime that ceased to be required after the form's retirement. The underlying business-combination registration content carried forward to the plain N-14 submission type without it.

The series-and-classes EDGAR metadata structure (seriesAndClassesContractsInformation) post-dates the lifetime of N14EL24 and is therefore essentially always empty for these records, even though the field is present in the schema.

Changes in data format over time

Throughout the 1994–1998 window EDGAR transmitted investment-company registration statements as ASCII text inside an SGML submission envelope, and that is the format reflected in the document bodies of this dataset. There is no HTML era for N14EL24 — HTML filings on EDGAR became permissible only after the form was discontinued — so every document-N.txt in the dataset is fixed-width ASCII with embedded legacy <TABLE>/<CAPTION>/<S>/<C> table markup. The linkToXbrl and dataFiles fields in metadata.json are present in the schema but always empty.

Interpretation notes

Several practical points matter for downstream consumption.

• Reconstructing a filing. Read metadata.json for the accession number, form type, filing timestamp, and ordered documentFormatFiles list; then for each entry whose sequence is a digit, open document-<sequence>.txt, treating the EDGAR <TYPE> and declared size as the metadata for that body file. The trailing entry with sequence: " " is a pointer to the EDGAR-hosted consolidated submission, not a local file.
• Document type recovery. Because the <DOCUMENT> envelope tags have been stripped, the only way to know the EDGAR <TYPE> of a given document-N.txt is via the documentFormatFiles[].type field keyed on the matching sequence. The document bodies themselves do not carry their own type label.
• Amendments are independent records. N14EL24/A records are independent submissions with their own accession numbers, document inventories, and bodies; they are not deltas on the original. The description field in metadata.json is annotated with [Amend] for amendments. To assemble the full state of a registration as ultimately effective, all N14EL24 and N14EL24/A filings sharing the same fileNo must be read in chronological order.
• Embedded markup is content, not envelope. The <TABLE>, <CAPTION>, <S>, and <C> tags inside the document bodies are the legacy EDGAR financial-table markup used inside fee tables, capitalization tables, financial highlights, and signature blocks. They should not be treated as SGML envelope and should not be stripped during text extraction; doing so destroys the column structure of the affected tables.
• Heavy use of incorporation by reference. N-14 disclosure makes extensive use of incorporation by reference — the acquiring fund's existing prospectus and SAI, prior audited financial statements, and previously filed exhibits are commonly referenced rather than refiled. A record therefore does not always contain every piece of substantive disclosure relied on; complete reconstruction may require resolving cross-references to other EDGAR filings of the same registrant via the CIK and file-number identifiers in metadata.json.
• Fixed-width ASCII extraction. Because the bodies are hard-wrapped near column 80, prose extraction generally requires reflow logic that joins continuation lines. Tabular content, by contrast, depends on column position and must be parsed differently — typically using the embedded table-markup tags or column-aware parsing inside <TABLE> regions.
• Two-fund framing. A single N14EL24 record routinely describes two (and occasionally more) investment companies — the acquiring fund and the target fund(s) — but the EDGAR header lists only the registrant (the acquiring fund) as filer. Identifying the target fund(s) and their CIKs typically requires reading the body text of document-1.txt rather than relying on metadata.json -> entities alone.

Who Files or Publishes This Dataset, and When

Each N14EL24 record is a registration statement on Form N-14 filed on EDGAR by the acquiring or surviving registered investment company in a fund-level business combination, paired with a declaration of election to register an indefinite number of securities under Section 24(f) of the Investment Company Act of 1940 and Rule 24f-2 thereunder. The filer is the issuer of the new shares — not the disappearing fund, the adviser, the distributor, or the sponsor.

Filer population

Eligible filers were entities permitted to make the Rule 24f-2 election:

• Open-end management investment companies (mutual funds), including individual series of series trusts, registered under the 1940 Act and offering redeemable securities continuously.
• Unit investment trusts registered under the 1940 Act issuing redeemable units in a reorganization or substitution.
• Series and master/feeder structures, where the registrant is the specific series or feeder issuing shares, even if the legal entity houses many other series.
• A small number of business development companies and other registered closed-end-style entities to the limited extent they qualified for the indefinite-registration election.

Not in the population: operating-company issuers (Form S-4), insurance separate accounts (Forms N-3/N-4/N-6), foreign funds not registered under the 1940 Act, and registered funds that filed plain Form N-14 to register a definite dollar amount of shares without electing under Rule 24f-2.

The registrant is always the issuer of the new securities. In a "merger of Fund A into Fund B," Fund B is the N14EL24 filer; Fund A is a transaction party and proxy solicitor but not the registrant.

Triggering events

A record is generated whenever a registered fund undertakes a transaction that constitutes an offer or sale of its securities under Section 5 of the Securities Act of 1933 and elects indefinite registration at the time of filing. Under Rule 145, the following transactions are deemed offers and sales to the security holders of the disappearing or transferring fund:

• Statutory mergers or consolidations of two or more registered funds, with shares of the surviving fund issued to shareholders of the disappearing fund.
• Reorganizations in which one fund acquires substantially all assets of another in exchange for shares plus assumption of stated liabilities, typically followed by liquidation of the acquired fund.
• Asset transfers between affiliated funds in the same complex, including share-class restructurings and cross-trust reorganizations.
• Exchange offers structured as fund-level combinations, where holders of one fund's securities receive securities of another.

Form N-14 is the prescribed registration form for these investment-company transactions; the "EL24" suffix marked filings that simultaneously declared the Rule 24f-2 election.

Regulatory framework

• Securities Act Section 5 requires registration of the deemed offers and sales identified by Rule 145.
• Securities Act Section 8 governs effectiveness — through staff review and acceleration, or automatic effectiveness after the statutory waiting period.
• Rule 488 under the Securities Act allows qualifying N-14 registration statements to become effective automatically on the 30th day after filing, giving fund mergers a predictable closing schedule absent staff review.
• Investment Company Act Section 24(f) and Rule 24f-2 historically permitted open-end funds and UITs to register an indefinite number of shares by filing a declaration of election, with fees paid retroactively via the annual Rule 24f-2 notice (later Form 24F-2) keyed to net sales.
• Section 20(a) of the 1940 Act and Section 14(a) of the Securities Exchange Act of 1934 govern proxy solicitation when the target fund's shareholders vote on the combination. The acquiring fund's prospectus and the target fund's proxy statement are typically combined in a single document delivered to target-fund shareholders.

Timing logic

N14EL24 was filed in advance of closing, with timing driven by:

• Section 8 effectiveness mechanics, including Rule 488's automatic effectiveness on the 30th day after filing for qualifying transactions.
• The target fund's shareholder meeting calendar, since the combined prospectus/proxy must be cleared for record date and mailing, and effectiveness must precede issuance of new shares at closing.
• The Rule 24f-2 election, a one-time declaration inside the registration statement; the resulting fee obligation was deferred to the annual Rule 24f-2 Notice tied to the registrant's fiscal year end.

Lifetime of the submission type

• January 1994 — N14EL24 enters the EDGAR taxonomy as mandatory EDGAR filing for investment-company registration statements begins. Earlier paper filings of the same character are not in this dataset.
• 1997 — The SEC amends Rule 24f-2 to make indefinite registration automatic for all eligible registered investment companies, eliminating the affirmative election in individual registration statements.
• January 1998 — EDGAR Release 5.40 retires the dedicated N14EL24 and N14EL24/A submission types. From that point forward, fund business-combination registration statements migrate to plain N-14 and N-14/A, which carry indefinite-registration treatment automatically.

The dataset therefore captures a closed historical window from January 1994 through January 1998.

Amendments (N14EL24/A)

An N14EL24/A is filed by the same registrant (same CIK and registration file number) that filed the original N14EL24 and carries forward the Rule 24f-2 election. Amendments split into:

• Pre-effective amendments — the dominant category, filed before the registration statement is declared or becomes automatically effective. Typical purposes: responding to staff comments, refreshing financial statements, conforming proxy disclosure to a finalized meeting date, restating fee tables, correcting errors.
• Post-effective amendments — filed after effectiveness to update the prospectus, reflect material changes before closing, or extend registration to additional contingencies. Less common, because N-14 registrations support a discrete transaction whose closing usually follows shortly after effectiveness.

Important distinctions

• Filer vs. transaction party. The acquiring/surviving fund is the registrant; the disappearing fund appears inside the filing as transaction and proxy disclosure, not as co-registrant, except in unusual two-issuer structures.
• Form N-14 vs. Form S-4. S-4 is the operating-company business-combination form; investment companies use N-14, so N14EL24 covers only fund-level deals.
• N14EL24 vs. plain N-14 (1994–1998). Within the window, a registrant could either register a definite dollar amount on plain N-14 or elect indefinite registration under Rule 24f-2 on N14EL24. The 1997 amendments collapsed the distinction; only plain N-14 remained.
• Election vs. fee payment. N14EL24 declared indefinite registration; it did not pay fees. Fees were paid later through the annual Rule 24f-2 notice (now Form 24F-2NT) keyed to net sales.
• Insurance separate accounts. Variable annuity and variable life separate accounts use Forms N-3, N-4, or N-6 and generally do not use Form N-14 at the separate-account level, although the underlying funds they invest in may.
• Foreign and unregistered funds. Funds not registered under the 1940 Act do not file Form N-14 and are absent from this population.
• Closed-end funds. Closed-end management companies had more limited Rule 24f-2 access; their mergers in this period more often appeared on plain N-14 than on N14EL24.

How This Dataset Differs From Similar Datasets or Filings

Form N14EL24 sits at the intersection of three regimes: Securities Act registration of fund shares, Investment Company Act registration, and the now-defunct Rule 24f-2 indefinite-share election. Because the submission type was retired in January 1998 under EDGAR Release 5.40, the most useful comparisons are contemporaneous fund-merger filings from the 1990s and the later filings that absorbed its functions.

Plain Form N-14

Form N-14 is the parent registration statement for fund mergers, consolidations, and reorganizations filed by open-end funds, UITs, and certain other registered investment companies. N14EL24 is functionally a subset, distinguished only by an explicit Rule 24f-2 election to register an indefinite number of shares. After Release 5.40 made that election automatic for eligible registrants in January 1998, N14EL24 was retired and all subsequent fund-merger registrations route through plain N-14. Document content is otherwise nearly identical (combined proxy/prospectus, financials of the merging funds, terms of combination, exhibits). A full historical view of fund mergers requires both: N14EL24 for 1994 through January 1998 filers making the explicit election, and plain N-14 for the broader timeline.

Form N-14 8C (closed-end funds)

N-14 8C is the closed-end-fund analogue, filed under Section 8(c) of the Investment Company Act for closed-end business combinations. N14EL24 was used only by open-end funds and UITs, because the 24f-2 indefinite-share election applies to continuous offerings; closed-end funds, which issue a fixed number of shares, never made the election. Closed-end reorganizations appear only in N-14 8C and its variants.

Form S-4 (operating-company business combinations)

S-4 registers shares issued in operating-company mergers, acquisitions, exchange offers, and recapitalizations. Disclosure follows Regulation S-K and Article 11 of Regulation S-X: MD&A, business description, executive compensation, pro forma financials, competitive position. N14EL24 disclosure follows the fund regime: investment objectives, portfolio policies, advisory fees, expense ratios, and Investment Company Act compliance. Filer populations do not overlap; S-4 issuers are not registered investment companies.

Forms N-1A, N-2, N-3, N-4 (initial and ongoing fund registration)

These register a fund's continuous offering: N-1A for open-end mutual funds, N-2 for closed-end funds, N-3 for variable-annuity separate accounts organized as management companies, N-4 for variable-annuity separate accounts organized as UITs. They are operational and ongoing, updated for normal-course offering. N14EL24 is event-driven, filed once in connection with a specific business combination to register the acquirer shares issued to target-fund shareholders. Use N-1A through N-4 for standing prospectuses, fee tables, and SAIs; use N14EL24 (or post-1998 plain N-14) for the merger event itself.

Rule 24f-2 Notice (Form 24F-2NT)

Rule 24f-2 historically required two separate steps. First, an election to register an indefinite number of shares (embedded in N14EL24 and in equivalent annotations on N-1A through N-4). Second, a periodic notice reporting actual shares sold and the registration fee due, originally Form 24F-2 and now filed electronically as 24F-2NT. N14EL24 contains the election only; 24F-2NT contains the after-the-fact share-sale counts and fee remittance. After January 1998 the election step disappeared from individual filings, but 24F-2NT continues as the annual fee-payment notice. The two are not interchangeable: N14EL24 holds no share-sale or fee-accounting data.

Form N-14AE and other N-14 submission variants

EDGAR uses several submission-type codes within the N-14 family (N-14, N-14/A, N14EL24, N14EL24/A, and in some periods N-14AE for filings requesting acceleration or carrying other procedural attributes). These codes route filings through different review paths but rest on the same underlying Form N-14. The N14EL24 dataset is bounded strictly by submission-type code and excludes filings tagged as plain N-14 or other variants, even when they describe substantively similar transactions in the same window. Reconstructing the full 1994 through 1998 fund-merger record requires combining multiple N-14 submission types.

DEF 14A and PRE 14A (proxy statements)

Fund mergers typically require shareholder approval, so the target fund files preliminary and definitive proxy statements under the Exchange Act proxy rules. These contain the board recommendation, merger agreement, rationale, fairness considerations, and voting mechanics from the target's perspective. N14EL24 is filed by the acquirer to register the new shares under the Securities Act. The same transaction often produces both filings, frequently using a combined proxy/prospectus incorporated by reference, but N14EL24 captures the registration statement, not standalone proxy materials. A complete transactional record pairs N14EL24 with the target's 14A filings, including DEF 14A and PRE 14A submissions.

Form 497 (filed prospectuses and supplements)

Form 497 (and 497K, 497J, etc.) is the vehicle for definitive prospectuses, SAIs, and supplements filed under Rule 497 of the Securities Act for a fund's continuous offering. It is operational and periodic, not transaction-specific. While an N14EL24 filing usually contains a prospectus or combined proxy/prospectus inside the registration statement, Form 497 holds the standalone, point-in-time prospectus content for ordinary operations. Use 497 for a fund's prospectus on a given date; use N14EL24 for the prospectus describing a specific 1994 through January 1998 merger.

Boundary Clarification

Form N14EL24 is distinctive on three axes simultaneously: it is event-driven (a specific business combination), fund-type-specific (open-end management investment companies and UITs only), and procedurally bounded (the explicit Rule 24f-2 election) by a feature retired in January 1998 under EDGAR Release 5.40. Plain N-14 is the natural continuation; N-14 8C is the closed-end counterpart; S-4 is the operating-company analogue; N-1A through N-4 are the steady-state registration forms; 24F-2NT is the surviving periodic fee notice; proxy statements and Form 497 surround the same transactions from different filer perspectives or for different document types. None substitutes directly within the 1994 through January 1998 window: N14EL24 is the cleanest finite cut of fund-merger registration statements that explicitly invoked Rule 24f-2.

Who Uses This Dataset

Because N14EL24 is a closed historical archive of 1994 to 1998 investment-company merger registration statements, it is not used for live monitoring. It functions as a precedent library, lineage source, and training corpus for the groups below.

Fund counsel and registered-investment-company regulatory lawyers

Used as a drafting precedent library for current N-14 transactions. Lawyers pull Part A combined proxy-prospectuses to model the "Reasons for the Reorganization," investment-objective and fee comparisons, Section 368(a) tax-treatment language, and capitalization and pro forma sections. Part B is mined for SAI merger mechanics; Part C confirms the standard exhibit set, with EX-99.11 (legality opinion) and EX-99.12 (tax opinion) reused as templates. Most useful when reorganizing funds whose original organizational documents date to the same era.

Corporate-actions and fund-data engineering teams

Used to reconstruct mid-1990s fund consolidation history that pre-dates many commercial fund-database backfills. Teams parse metadata.json (CIK, accession, filed date, document inventory) to enumerate filings, then extract target/acquiring fund pairs, share-class mappings, exchange ratios, and effective dates from Part A. Pro forma combined financials resolve share-conversion ratios needed to stitch post-merger NAV series to pre-merger histories. Output feeds survivorship-bias corrections, AUM lineage chains, and performance-record continuity rules.

Academic researchers in financial economics

Used as a primary-source archive for studies of the 1990s mutual-fund consolidation wave. Part A "Reasons for the Reorganization" and "Comparison of Fees and Expenses" sections supply consistent fields for empirical work: pre-merger size, expense ratios before and after, board rationale, and negotiated terms. Part B contributes historical performance and policy disclosures; Part C exhibits document advisory and distribution-agreement assignments. The bounded population of filings supports event-study and cross-sectional designs.

Product-development and regulatory consultants

Used to study how the Rule 24f-2 election paragraph, indefinite-share declarations, and fee-table formats were drafted before the rule's automatic-election era. Focus is on the Part A cover page, election paragraph, and fee-table front matter. Referenced when evaluating disclosure approaches for investment-policy changes, sub-adviser additions, and 12b-1 plan modifications triggered by a reorganization.

Fund-complex compliance teams and CCOs

Used to retrieve prior filings under the same CIK or sponsor lineage when scoping a current reorganization. Compliance staff compare Section 15(c) board-approval recitals, Rule 17a-8 affiliate-merger representations, and EX-99.12 tax-opinion qualifications across the family's history. Part B SAI text is checked to validate that legacy disclosures were properly carried forward, modified, or retired across successive reorganizations.

Securities litigators and expert witnesses

Used to retrieve the original disclosures shareholders received in mid-1990s mergers. The Part A narrative on board rationale, projected expense reductions, and surviving-fund risk factors, together with merging-fund financial statements and pro formas, is tested against later outcomes. The agreement and plan of reorganization, fairness analyses, and EX-99.12 tax opinions are cited as contemporaneous representations in fiduciary-duty and ERISA matters.

Legal and financial NLP data-science teams

Used as a stylistically homogeneous corpus for training and evaluation. The narrow form scope supports tasks such as extracting target/acquiring fund pairs, classifying reorganization types, identifying Section 368(a) tax-free clauses, parsing exchange ratios from prospectus tables, and detecting Rule 24f-2 election paragraphs. metadata.json provides accession-level joins for retrieval-augmented systems and entity-resolution benchmarks that must reconcile pre-1998 fund identities with modern identifiers.

Transfer agents and fund-administration archival teams

Used to support historical shareholder inquiries, tax-basis reconstruction, and audit work on long-held positions whose cost basis traces through 1990s reorganizations. They rely on Part A exchange-ratio and effective-date disclosures, the agreement and plan of reorganization in Part C, and EX-99.12 tax opinions to substantiate carryover-basis treatment.

Proxy-solicitation and shareholder-communications archivists

Used for EX-99.17 form-of-proxy templates and the Part A proxy-statement portion of the combined document. Reference points include record-date language, voting-standard recitals, broker non-vote treatment, and adjournment provisions, supporting current proxy drafting for affiliated and third-party fund reorganizations.

Synthesis

The dataset is narrow in form scope but serves a defined set of users: fund counsel drafting precedents, fund-data teams reconstructing merger lineage, academics studying 1990s consolidation, compliance and product teams comparing historical disclosure, litigators retrieving contemporaneous representations, NLP teams building training corpora, fund administrators supporting cost-basis work, and proxy archivists referencing form-of-proxy templates. Each draws on a different combination of metadata.json, Part A, Part B, Part C exhibits (notably EX-99.11, EX-99.12, EX-99.17), and the merging funds' financial statements, which is why the closed 1994 to 1998 archive remains a working reference rather than a static curiosity.

Specific Use Cases

The use cases below are concrete workflows that draw on specific record components of the Form N14EL24 Files Dataset.

Building a 1994–1998 fund-merger lineage table

A corporate-actions data engineer iterates every record's metadata.json, joins the registrant CIK and fileNo from the entities array against the accessionNo and filedAt timestamp, then parses the Part A combined proxy/prospectus in document-1.txt to extract acquiring fund, target fund(s), exchange ratios, valuation date, and effective date. Pro forma capitalization tables and the Agreement and Plan of Reorganization (commonly in EX-99.4 or embedded in Part A) supply the share-conversion factors. Output is a survivorship-bias-aware lineage table that splices pre-merger NAV and AUM series onto surviving-fund identifiers.

Drafting precedent library for current N-14 reorganizations

Fund counsel preparing a current reorganization queries the dataset by SIC, state of incorporation, and fund-family CIK to pull comparable Part A "Reasons for the Reorganization," "Comparison of Fees and Expenses," and Section 368(a) tax-discussion sections, plus the matching EX-99.11 legality opinion and EX-99.12 tax opinion. The EX-99.17 form-of-proxy is reused as a voting-mechanics template. The output is a redlineable precedent pack tied to filings made under the same fund family or trust form.

Tax-basis substantiation for legacy shareholder positions

A transfer-agent or fund-administration archival team responds to a cost-basis inquiry on shares received in a 1990s reorganization by locating the matching N14EL24 record by acquiring-fund CIK and effective date, extracting the exchange ratio and tax-treatment language from Part A, and pulling the EX-99.12 tax opinion's Section 368(a) qualifications. The output is a documentation packet establishing carryover basis and holding period for IRS-defensible cost-basis statements.

NLP corpus for fund-merger information extraction

A legal-NLP team uses the dataset as a stylistically homogeneous training corpus. Tasks include: target/acquiring-fund pair extraction grounded against the registrant flagged in metadata.json -> entities, exchange-ratio parsing from <TABLE>/<S>/<C> capitalization blocks in Part A, classification of Section 368(a) clauses in EX-99.12, and detection of Rule 24f-2 election paragraphs on the document-1.txt cover page. The dataset's bounded form scope and uniform 1990s ASCII formatting yield a clean evaluation set; metadata.json accession-level identifiers anchor retrieval-augmented benchmarks.

Litigation discovery and contemporaneous-disclosure retrieval

Securities litigators and expert witnesses retrieving what shareholders actually received in a mid-1990s merger pull the Part A board-rationale narrative, projected expense-reduction tables, and surviving-fund risk discussion from document-1.txt, together with the merging funds' embedded or exhibited financial statements and the Agreement and Plan of Reorganization. EX-99.12 is cited verbatim for the tax representations made at filing. Output is an exhibit set of contemporaneous disclosures usable in fiduciary-duty, ERISA, or Section 11 proceedings.

Drafting-history study of the Rule 24f-2 election paragraph

Regulatory consultants and academic researchers studying disclosure evolution before EDGAR Release 5.40 isolate the Rule 24f-2 election paragraph and the indefinite-shares footnotes on the registration-fee table from the cover-page region of document-1.txt across the full 1994–January 1998 window. Filtering by formType and filedAt and clustering paragraph variants produces a longitudinal map of how the explicit-election language was drafted in the years before it became automatic, useful as background in current rulemaking comments and in compliance training material.

Dataset Access

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

This endpoint returns the dataset's metadata, including its name, description, last updated timestamp, earliest sample date (1994-01-01), total record count, total size in bytes, covered form types (N14EL24 and N14EL24/A), container format (ZIP), and file types (TXT and JSON). It also returns the download URL for the full dataset and the list of individual container files with per-container metadata such as size, record count, last updated timestamp, and download URL. Use this endpoint to monitor which containers were updated in the most recent refresh run and to decide which containers to download on a daily basis.

This endpoint does not require an API key.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-69ea-81f7-641caa4564b1",
        

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

          4
            "name": "Form N14EL24 Files Dataset",
        

          5
            "updatedAt": "2026-04-15T18:12:04.889Z",
        

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

          7
            "totalRecords": 1658,
        

          8
            "totalSize": 40110018,
        

          9
            "formTypes": ["N14EL24", "N14EL24/A"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

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

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

          16
                "size": 1382112,
        

          17
                "records": 12,
        

          18
                "updatedAt": "2026-04-15T18:12:04.889Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

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

Downloads the complete dataset as a single ZIP archive containing all containers. This endpoint requires an API key.

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

Downloads one individual monthly container instead of the full dataset, which is useful for incremental updates. Container paths are listed under the containers array in the dataset index JSON. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers EDGAR submissions filed under the form types N14EL24 and its amendment variant N14EL24/A. These are the variant of Form N-14 — the Securities Act of 1933 registration form for fund-level business combinations — that additionally carried an explicit declaration of election under Rule 24f-2 of the Investment Company Act of 1940 to register an indefinite number of shares.

What does one record in this dataset represent?

One record represents a single registration-statement submission filed on EDGAR under N14EL24 or N14EL24/A, identified by its SEC accession number. On disk, each record is a directory named with the 18-digit accession number (hyphens removed) containing one metadata.json (the EDGAR submission header and document inventory) and one or more document-N.txt files holding the plain-text bodies of the constituent EDGAR documents in submission order.

Who is required to file this form?

The filer is the acquiring or surviving registered investment company that issues the new shares in a fund-level business combination — typically an open-end management investment company (mutual fund), a unit investment trust, or a series or feeder within those structures, registered under the Investment Company Act of 1940. The disappearing fund, adviser, distributor, and sponsor are not the registrant.

What time period does the dataset cover?

The dataset captures the full active life of the submission type, from January 1994 — when EDGAR opened to investment-company filings — through the form's discontinuation in January 1998 under EDGAR Release 5.40. After January 1998, fund business-combination registration statements migrated to plain N-14 and N-14/A because rule amendments made the Rule 24f-2 election automatic for eligible registrants.

What file format is the dataset distributed in?

Records are packaged into monthly ZIP archives organized as <year>/<year>-<month>.zip. The file types inside are TXT (the document bodies in fixed-width 1990s EDGAR ASCII, with embedded <TABLE>/<CAPTION>/<S>/<C> financial-table markup preserved verbatim) and JSON (the per-record metadata.json).

How does this dataset differ from plain Form N-14?

Plain Form N-14 is the parent registration statement for fund mergers and reorganizations. N14EL24 is functionally a subset, distinguished only by an explicit Rule 24f-2 election to register an indefinite number of shares. Document content is otherwise nearly identical. After EDGAR Release 5.40 retired N14EL24 in January 1998, all subsequent fund-merger registrations route through plain N-14, so a complete historical view of fund mergers requires both datasets.

Are amendments stored as deltas on the original filing?

No. N14EL24/A records are independent submissions with their own accession numbers, document inventories, and bodies — they are not deltas on the original. To assemble the full state of a registration as ultimately effective, all N14EL24 and N14EL24/A filings sharing the same fileNo must be read in chronological order. The description field in metadata.json is annotated with [Amend] for amendments.