Form 40-OIP Files Dataset

The Form 40-OIP Files Dataset is a complete corpus of EDGAR submissions filed on Form 40-OIP and Form 40-OIP/A — applications for exemptive relief, no-action, or interpretive relief under the Investment Company Act of 1940 routed to the SEC's Division of Investment Management Office of Insurance Products (OIP). One record represents a single EDGAR submission identified by its 18-digit accession number, packaging both the structured submission metadata and the substantive application document exactly as filed. Applications are submitted by life insurers, their registered separate accounts, principal underwriters, and affiliated investment advisers, most often to obtain a Commission order permitting a portfolio substitution inside a variable annuity or variable life separate account. The dataset begins on 2008-10-01, when 40-OIP was introduced as a distinct EDGAR form code, and is refreshed as new applications and amendments are accepted by EDGAR. Records are distributed as monthly ZIP containers holding HTML, JSON, TXT, and PDF files.

Dataset APIs

Dataset Files

What This Dataset Contains

Form 40-OIP filings contain applications submitted under the Investment Company Act of 1940 and reviewed by the SEC's Office of Insurance Products. These applications typically seek exemptive relief for transactions involving variable insurance contracts — most commonly portfolio substitutions within separate accounts offered by insurance companies — and are filed pursuant to combinations of Section 6(c), Section 17(b), Section 26(c), and Rule 17d-1 of the Act. The dataset includes all Form 40-OIP and Form 40-OIP/A filings submitted to EDGAR from October 2008 to the present; Form 40-OIP/A filings represent amendments to previously filed applications.

For each accession number, the dataset includes a metadata.json file describing the EDGAR header along with every non-image document attachment from the original EDGAR submission. Each application typically contains a description of the proposed transaction, the statutory basis for exemptive relief, representations regarding the impact on contract holders, legal analysis supporting the application, and any conditions the applicants propose to satisfy. Records are grouped on disk by filing month inside per-month YYYY-MM/ folders unzipped from the corresponding monthly ZIP archive, with HTML as the dominant format for the application body and JSON reserved for metadata.json.

Content Structure of a Single Record

What one record represents

One record in the Form 40-OIP Files Dataset is a single EDGAR submission of either Form 40-OIP (an original application) or Form 40-OIP/A (an amendment), identified by an 18-digit zero-padded SEC accession number. The unit of granularity is the accession folder: a directory whose name is the dashless accession number, holding one metadata.json describing the EDGAR submission header and one or more document files reproduced from the original EDGAR upload. A record therefore packages both the structured submission metadata and the substantive application text exactly as filed, with image attachments omitted. Records are grouped on disk by filing month inside per-month YYYY-MM/ folders unzipped from the corresponding monthly ZIP archive.

What the underlying filing is

Form 40-OIP is the EDGAR form code for an application for exemptive, no-action, or interpretive relief under the Investment Company Act of 1940 that is routed to the Division of Investment Management's Office of Insurance Products (the "OIP" suffix). The form is overwhelmingly used by life insurance companies and their separate accounts to seek transactional relief affecting variable annuity and variable life contracts — most commonly orders permitting the substitution of one underlying investment-fund interest held by a separate account for another (a "portfolio substitution") and, in conjunction, relief from the affiliated-transaction prohibitions where the substitute fund is affiliated with the insurer. Applications are typically filed under combinations of Section 6(c) (general exemptive authority), Section 17(b) (relief from Section 17(a) affiliated-transaction prohibitions), Section 26(c) (substitution of separate-account investments), and Rule 17d-1 (joint-transaction relief). Each application requests a Commission order that, once issued, lets the named insurer execute the proposed transaction subject to the conditions agreed to in the application.

The form is filed as a free-form legal application rather than a fixed-format schedule. It is administrative in nature: there are no required financial statements and no scheduled tables of holdings. The entire substantive content is the application narrative itself — a cover sheet, numbered sections of legal and factual argument, representations, proposed conditions, and signatures. A 40-OIP/A is a successive amendment to a previously filed application under the same SEC file number in the 812- series assigned to 1940 Act applications; each amendment conventionally restates and supersedes the prior version, so a single application docket can produce an original 40-OIP record followed by a chain of 40-OIP/A records that carry the prior text forward with insertions, deletions, and revised conditions.

Content layers inside an accession folder

An accession folder always contains two content layers:

1. metadata.json — a flat JSON object reproducing the EDGAR submission header: form type, accession number, filed timestamp, applicant entities, file numbers, document inventory, and links back to the live filing on sec.gov. This file is always present and always named metadata.json.
2. EDGAR document files — one or more attachments registered with the original submission, written to disk under the filer-chosen filenames (for example 40iopafourthamendment.htm). The primary document is the application itself, normally a single HTML file. Additional attachments may include exhibits or supporting text/PDF documents. Image attachments referenced by EDGAR are intentionally omitted from the dataset; they remain enumerated in the metadata but are not present on disk.

The file-types found in the dataset are HTML, JSON, TXT, and PDF, with HTML being the dominant format for the application body and JSON reserved for metadata.json. There is no XBRL or Financial_Report.xlsx content because 40-OIP submissions do not carry structured financial data — these artefacts are absent because they were never filed, not because they were stripped.

Each substantive document retains the EDGAR SGML submission envelope wrapping its inner HTML or text body. The envelope exposes the four header tags assigned at submission time — <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION> — followed by <TEXT>...</TEXT> containing the actual <html>...</html> (or plain text) document, terminated by </DOCUMENT>. Parsers expecting pure HTML must strip this SGML wrapper before tokenizing the body.

The metadata.json shape

metadata.json is a flat object whose keys describe the EDGAR submission as a whole, not the application's legal content. The fields that carry intentional, documented meaning are:

• formType — 40-OIP for an original application or 40-OIP/A for an amendment.
• accessionNo — the canonical dashed accession number (e.g., 0001061128-18-000064); the folder name is the dashless variant of the same identifier.
• filedAt — ISO 8601 timestamp with timezone offset indicating when EDGAR accepted the submission.
• description — short human-readable form description from the EDGAR header.
• linkToFilingDetails — URL to the primary application document on sec.gov.
• linkToTxt — URL to the full .txt SGML submission on sec.gov.
• linkToHtml — URL to the EDGAR <accession>-index.htm filing landing page.
• linkToXbrl — empty string for these filings, because 40-OIP applications do not include XBRL exhibits.
• documentFormatFiles — array of submission attachments. Each element carries sequence (1, 2, 3 ... ordering inside the submission), size (bytes, as a string), documentUrl (sec.gov URL), description, and type (the EDGAR document type code, such as 40-OIP, 40-OIP/A, GRAPHIC, or blank for the complete-submission text file). Image attachments continue to appear here as references even though they are not stored on disk.
• entities — array of filer and co-filer entries. Each entry has cik, companyName (often suffixed with role such as (Filer)), type, act (40 for the Investment Company Act), fileNo (the 812-XXXXX 1940 Act application docket number), filmNo, irsNo, fiscalYearEnd, and stateOfIncorporation. The array is variable-length and is the most informative structural feature of 40-OIP metadata: applications nearly always list multiple co-applicants — typically the insurance carrier together with each separate account that will execute the proposed transaction, and sometimes affiliates such as a depositor, an affiliated investment adviser, or a principal underwriter.
• seriesAndClassesContractsInformation — array of fund-series and contract-class entries; usually empty on 40-OIP filings.
• dataFiles — array of supplementary structured data files; typically empty.
• id — opaque 32-character hex identifier assigned to the record within the dataset distribution.

The application document — section-by-section

The HTML (or, in older filings, text) document carrying the application is the substantive record. Although phrasing and section numbering are filer-chosen rather than dictated by a Commission-prescribed format, 40-OIP applications follow a stable internal structure that mirrors the standard 1940 Act exemptive-application format. From top to bottom, a typical document contains:

• Caption / cover sheet. A formal Commission caption block: "UNITED STATES SECURITIES AND EXCHANGE COMMISSION", "In the Matter of [Insurance Company] et al.", the application file number (File No. 812-XXXXX), and a header identifying the form (e.g., "APPLICATION FOR AN ORDER PURSUANT TO SECTION 26(c)..."). The cover also lists each applicant's address, the name and contact details of counsel for service, the date of the application or amendment, and — on 40-OIP/A filings — a sequence label such as "First Amendment" or "Fourth Amendment to and Restatement of the Application".
• Statement of applicants. A short paragraph identifying each applicant by legal name, jurisdiction of incorporation/organization, and role (insurance company depositor, separate account, affiliated fund, investment adviser, principal underwriter).
• Summary of application / requested order. A precise statement of the relief sought, naming the statutory provisions invoked (commonly Section 26(c) for the substitution itself, Section 17(b) and Rule 17d-1 for related affiliated-transaction relief, and Section 6(c) as a residual exemptive vehicle), and summarizing what the applicants will be permitted to do if the order issues.
• Description of applicants. Detailed factual background on each entity — the insurer's regulatory status, the separate accounts' structure as registered unit investment trusts under the 1940 Act, the variable annuity and variable life contracts the separate accounts fund, and the existing and replacement underlying funds with their investment objectives, advisers, fee structures, and assets under management.
• Description of the proposed transaction. A narrative explanation of the substitution or other transaction: the existing investments to be redeemed, the replacement investments to be purchased, the mechanics and timing of the substitution, the in-kind or cash treatment of fund interests, and the notice and free-transfer election rights provided to contract owners.
• Statutory basis / legal analysis. Section-by-section legal argument explaining why the requested order is "necessary or appropriate in the public interest and consistent with the protection of investors and the purposes fairly intended by the policy and provisions of the [Investment Company] Act." Each statutory hook (26(c), 17(b), 6(c), Rule 17d-1) is addressed in turn, with citations to prior Commission orders and Division precedent that have granted comparable relief.
• Representations. A numbered list of factual representations the applicants make to the Commission — most importantly that contract owners will not bear costs of the substitution, that the substitution will not result in higher fees, that fund performance and investment objectives are substantially similar, and that contract owners will receive prospectuses, advance notice, and a free transfer right for a defined window after the transaction.
• Proposed conditions. A numbered list of conditions the applicants agree to be bound by as a precondition to the Commission's order. These typically codify the representations into binding undertakings (e.g., "the substitution will be effected at net asset value", "any expenses will be borne by [insurer] and not the contract owners", "for two years following the substitution, the insurer will not increase total separate-account charges").
• Procedural / authorization recitals. Statements regarding the corporate authorizations of each applicant and verifications by officers or counsel.
• Signatures and verifications. Authorized signatures by an officer of each applicant, verified affidavits attesting to the truth of the factual representations, and the date of execution.
• Attached exhibits. Resolutions of the boards of directors of each applicant authorizing the filing, opinions of counsel, and verifications. These are commonly inlined in the same document rather than filed as separate EDGAR exhibits.

Differences between 40-OIP and 40-OIP/A records

Structurally, an original 40-OIP and an amendment 40-OIP/A look almost identical inside the dataset: the same accession-folder layout, the same metadata.json shape, and the same kind of HTML application body. The substantive differences live in the content rather than the schema:

• The formType field carries 40-OIP versus 40-OIP/A, and the SGML envelope of the primary document carries the same value in its <TYPE> tag. The <DESCRIPTION> line on amendments typically reads as a numbered amendment ("FIRST AMENDMENT", "FOURTH AMENDMENT", etc.).
• Amendments share the same 812- file number as the original application; this fileNo value is therefore stable across the chain of records that constitute one application docket, while accessionNo differs for each submission in the chain.
• A 40-OIP/A document conventionally restates the entire application as amended rather than providing a redline; the cover page indicates "Amendment to and Restatement of the Application", and the body contains the full text incorporating the revisions. As a consequence, the latest amendment in an application chain is the operative document, while earlier records preserve the historical state.
• Amendments typically add or revise the proposed conditions and representations in response to Staff comments, refine the description of the transaction, supply additional precedent in the legal analysis, or update factual data such as fund assets and recent performance. They do not normally remove the cover sheet, statutory basis, representations, or signatures sections.
• The entities array can change across amendments when applicants are added or removed (for example when a newly created separate account is brought into the substitution).

Included content

For each accession number, the dataset includes metadata.json and every non-image document attachment from the original EDGAR submission. The application body is reproduced under the filer's original filename, wrapped in the EDGAR SGML envelope so that the filer-registered <TYPE>, <SEQUENCE>, <FILENAME>, and <DESCRIPTION> headers are preserved. Multi-document filings (for example an application HTML plus an exhibit text or PDF file) are reproduced with each component as a sibling file inside the accession folder. The folder naming convention — YYYY-MM/<18-digit-accession>/ — and the fixed metadata.json filename are uniform across the entire corpus from October 2008 onward.

Excluded or separate content

Image attachments (chiefly .jpg and similar graphic files registered as GRAPHIC in the EDGAR document inventory) are excluded from the local archive. They remain enumerated in metadata.documentFormatFiles and can be retrieved individually from the documentUrl on sec.gov, but they are not present on disk. Because 40-OIP filings carry no XBRL, no inline-XBRL, and no Financial_Report.xlsx, those structured-data artefacts are likewise absent. The Commission's eventual order responding to the application is a separate Investment Company Act release issued under the same 812-XXXXX docket and is not part of any 40-OIP record; orders are published in the SEC's release stream rather than as EDGAR filings on the applicants' docket.

Structural evolution from 2008 to present

Form 40-OIP was introduced as a distinct EDGAR submission type in 2008 to route Office of Insurance Products applications onto a dedicated form code; the dataset's coverage begins in October 2008, corresponding to the form's debut on EDGAR. Across the full window from 2008 to the present, the high-level anatomy of a record has been stable: the same cover-sheet conventions, the same statutory-relief framework under Sections 6(c)/17(b)/26(c) and Rule 17d-1, the same representations-and-conditions structure, and the same metadata fields. Material changes over time have been incremental rather than structural:

• The corpus is filed almost entirely in HTML inside the EDGAR SGML envelope, with occasional plain-text or PDF supporting attachments. There is no ASCII-only era specific to 40-OIP because the form post-dates the full EDGAR HTML transition.
• Conditions and representations have grown more standardized over time as Staff practice in the substitution area has converged. Later filings tend to incorporate by reference the conditions adopted in earlier orders, and the proposed-conditions sections have lengthened accordingly.
• Co-applicant rosters in the entities array have widened in recent years as insurers consolidate multiple separate accounts and product platforms into single applications, so newer records commonly enumerate more entities than older ones.

Interpretation and extraction notes

Several practical nuances matter when working with these records:

• Amendment chains. Because each 40-OIP/A fully restates the application, joining records by fileNo (the 812-XXXXX docket number) yields the complete amendment chain for one application; only the latest record reflects the final position before the Commission acts.
• SGML envelope. The <DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, and <TEXT> tags wrapping the inner HTML body are not valid HTML and must be stripped before applying standard HTML parsers.
• Missing graphics. Image references inside the HTML body may resolve to filenames listed in documentFormatFiles but absent from disk; downstream renderers should fall back to the documentUrl on sec.gov when graphics matter.
• Identifying applicants. The variable-length entities array is the principal place where applicant identity is captured in structured form; the application's caption ("In the Matter of...") usually agrees with this list but is free-form text.
• Identifier semantics. The 812- file number is shared across an entire application chain and across all co-applicants on a single application, so it is not unique per record. accessionNo is the only field guaranteed to identify a single submission.
• Free-form numbering. The substantive legal sections — statutory basis, representations, and proposed conditions — are written in free-form prose with numbering chosen by the filer; reliable extraction of individual conditions requires document-aware parsing rather than fixed-position rules.
• Order not included. The Commission's notice of application and final exemptive order are published outside this dataset; the 40-OIP record captures only the applicants' submission, not the regulatory response.

Who Files or Publishes This Dataset, and When

Who files the record

A Form 40-OIP record is an application for an SEC exemptive order submitted on EDGAR by a coordinated group of co-applicants in the variable insurance product chain. The 40-OIP form type (rather than the more general Form 40-APP) routes the application to the Division of Investment Management's Office of Insurance Products, which has subject-matter jurisdiction over variable annuity and variable life products.

Typical co-applicants include:

• Insurance companies issuing variable annuity and variable life contracts, acting as depositors of registered separate accounts.
• Insurance company separate accounts registered under the 1940 Act, usually as unit investment trusts and occasionally as management investment companies.
• Principal underwriters and broker-dealer affiliates distributing the variable contracts.
• Investment advisers to the underlying funds, where relief involves fund-of-funds investments, manager-of-managers structures, or affiliated substitutions.
• Underlying registered funds whose shares are held by the separate accounts, when the relief reaches transactions with those funds.

The EDGAR submission is made on behalf of the entire applicant group. Each co-applicant is named in the application body and is typically mapped to its own CIK on the filing header, even though one entity (usually the lead insurer) appears as filer of record.

When the record is created

Filing is event-driven, not periodic. A 40-OIP is triggered when applicants propose a transaction that, absent Commission relief, would conflict with a substantive provision of the 1940 Act applicable to separate accounts or to the funds underlying their variable contracts. Common triggers and the statutory hooks invoked:

• Portfolio substitutions in variable contracts, where the depositor proposes to replace one underlying fund's shares with another's. Section 26(c) requires prior Commission approval for any such substitution by the depositor of a registered UIT. This is the dominant trigger in the dataset.
• Affiliated transactions (in-kind transfers, cross-trades, mergers) among separate accounts, the insurer's general account, and underlying funds, requiring relief under Section 17(b) from the Section 17(a) prohibitions, or under Section 17(d) and Rule 17d-1 for joint arrangements.
• Fund-of-funds and manager-of-managers structures offered through variable products, requiring Section 6(c) relief to permit investments above statutory limits or sub-adviser changes without contract-owner votes.
• Exchange offers accompanying substitutions, implicating Section 11, which governs offers of exchange between registered investment companies.
• Other novel structures in variable contracts (charge structures, asset transfers between separate accounts) requiring tailored relief, generally anchored on Section 6(c).

Section 6(c) is the workhorse exemptive provision and is cited in nearly every application alongside the more specific section invoked.

The application / Notice / Order lifecycle

The 40-OIP filing is the initial step in a multi-stage administrative process. Only steps 1 and 2 produce records in this dataset.

1. Application (Form 40-OIP). Applicants submit the application, including factual statement, legal analysis, contract-owner protections, proposed conditions, and signed verifications.
2. Amendments (Form 40-OIP/A). Office of Insurance Products staff issue comments; applicants respond by filing one or more amendments restating facts, refining legal analysis, or adjusting conditions. Multiple rounds are normal.
3. Notice of Application. When staff are satisfied, the Commission publishes a Notice giving interested persons an opportunity to request a hearing.
4. Order. Absent a hearing request (the typical outcome), the Commission issues an Order granting the relief, generally in the form attached to the Notice.

Notices and Orders are separate Commission releases and are not filed on EDGAR as 40-OIP records.

Amendments (Form 40-OIP/A)

Each 40-OIP/A is a self-contained restated application by the same applicant group. Amendments are triggered by:

• staff comments during review;
• applicant-driven updates (added co-applicants, revised funds in a substitution, updated financial data, adjusted conditions);
• changed circumstances (corporate reorganization of an applicant, change of adviser);
• final pre-Notice clean-up of the application that the Commission Notice will be based on.

Timing

There is no statutory deadline. Timing is set by the applicants' transaction calendar and the pace of staff review. Substitution applications are typically filed several months ahead of the proposed effective date to accommodate amendment cycles and the Notice/Order sequence. Once an Order issues, applicants must implement within the period and conditions it specifies.

Important distinctions

• 40-OIP vs. 40-APP. Both are 1940 Act applications for orders. 40-APP covers applications routed elsewhere in the Division (ETF relief, non-insurance fund-of-funds, ordinary joint-transaction relief). 40-OIP signals routing to the Office of Insurance Products and is concentrated in variable insurance matters.
• 40-OIP vs. registration forms (N-1A, N-3, N-4, N-6, N-14). Registration and merger forms disclose products to investors; 40-OIP seeks exemptive relief. A single transaction often produces both: a 40-OIP for the order and concurrent N-4 or N-6 amendments to update contract-owner disclosure.
• 40-OIP vs. specialized 1940 Act application forms (40-6B, 40-8F-2, 40-17F-2, etc.). The 40-OIP designation reflects office routing, not the specific statutory provision invoked; one application typically cites several sections (most often 6(c) plus 17(b) and/or 26(c)).
• Applicant vs. EDGAR filer. The Order, when granted, runs to all named co-applicants and to persons described as eligible to rely on it, even though the EDGAR header may list only the lead insurer as filer.
• Dataset coverage. Records begin October 2008, when EDGAR began accepting filings under the 40-OIP form type. Earlier insurance-product applications were submitted under predecessor or general application types and are outside this dataset. Notices of Application and Commission Orders are excluded; image files are excluded; all other submitted documents (HTML, TXT, PDF) and metadata are included.

How This Dataset Differs From Similar Datasets or Filings

Form 40-OIP occupies a narrow slot: applications for exemptive relief under the Investment Company Act of 1940 routed to the Division of Investment Management's Office of Insurance Products (OIP). Several nearby filing types share its statutory base, its filer population, or its product universe, but each differs in the relief sought, the reviewing office, or the underlying disclosure regime. The most useful comparisons are: Form 40-APP (the general 1940 Act application), the variable-insurance registration statements (Form N-3, Form N-4, Form N-6) and underlying-fund Form N-1A, and Form N-14 for fund-level reorganizations. Forms Form 40-6B, Form 40-8B25, Form 40-17F1, and Form 40-17F2 share the "40-" prefix but address unrelated regimes.

Form 40-APP — general 1940 Act exemptive applications

Same legal mechanic as 40-OIP: an applicant cites Section 6(c), 17(b), 17(d), Section 12(d)(1), or another provision and asks the Commission for an exemptive order, often with conditions. The split is jurisdictional. 40-APP is reviewed by the Chief Counsel's Office and other Investment Management branches and covers ETF orders, fund-of-funds, co-investment, affiliated-transaction, and joint-transaction relief. 40-OIP is the routing form when the relief concerns variable insurance contracts — typically portfolio substitutions in separate accounts under Section 26(c) or mixed-and-shared funding orders. Choose 40-APP for fund-industry relief outside the insurance context; choose 40-OIP for insurance-product relief. The two datasets are complementary and rarely substitutable.

Forms N-3, N-4, N-6 — variable-contract registration statements

Same filer population (insurance company separate accounts) and same product universe (variable annuities and variable life), but a different legal function. N-3 registers separate accounts organized as management investment companies; N-4 registers UIT-form separate accounts offering variable annuities; N-6 registers separate accounts offering variable life. These are Securities Act registration statements describing fees, investment options, riders, surrender charges, and tax treatment to contract purchasers. 40-OIP requests Commission permission for a transaction the issuer cannot otherwise consummate (most often a substitution of one underlying fund for another inside the separate account). A substitution order under 40-OIP is typically followed by post-effective amendments to the related N-3/N-4/N-6. To trace a single substitution event end-to-end, both datasets are usually required: 40-OIP for the legal basis and conditions, N-3/N-4/N-6 for the resulting prospectus disclosure to contract holders.

Form N-1A — underlying mutual fund registration

N-1A registers the open-end mutual funds that frequently serve as the investment options inside variable contracts. Overlap with 40-OIP is indirect: a Section 26(c)/17(b) substitution typically replaces one N-1A-registered fund with another inside a separate account. N-1A contains no exemptive analysis. Use N-1A to study the underlying fund options affected by a substitution; use 40-OIP to study the substitution mechanic itself.

Form N-14 — registered investment company reorganizations

Both N-14 and 40-OIP can involve replacing one investment vehicle with another, but the regimes are sharply different. N-14 is a Securities Act registration form delivering a combined prospectus/proxy to fund shareholders for a vote on a merger or reorganization. 40-OIP is a 1940 Act exemptive application that asks the Commission to permit a substitution or affiliated transaction; contract holders typically do not vote on a substitution in the same manner. N-14 covers any registered fund reorganization; 40-OIP is restricted to OIP-jurisdiction insurance matters. A fund-level merger affecting an underlying contract option may generate both filings — N-14 at the fund level and 40-OIP at the separate-account level — but neither substitutes for the other.

Adjacent in numbering, unrelated in substance

• Form 40-6B — application under Section 6(b) for categorical exemption of an employees' securities company (in-house investment vehicle for a sponsor's employees). Same broad application structure, but a different statutory hook (categorical, not transactional), different filer population (banks, PE sponsors, law firms — not insurers), and no insurance-product overlap.
• Form 40-8B25 — companion compliance filing within the employees' securities company regime; not an exemptive application and unrelated to variable insurance products.
• Forms 40-17F1 / 40-17F2 — custody compliance filings under Rules 17f-1 and 17f-2, certifying maintenance of fund assets with banks or other approved custodians. Operational and certificatory; not applications, not OIP-reviewed, no relief sought.

40-OIP vs. 40-OIP/A within the dataset

40-OIP/A is an amendment to a pending 40-OIP, not an independent event. Amendments add representations, refine conditions, respond to staff comments, update facts, or attach exhibits requested during review. Treat each accession series as a linked dialogue with OIP staff; the final 40-OIP/A typically reflects the relief actually granted. This differs from registration-statement amendments (e.g., N-4 post-effective amendments), which update offering disclosures over time rather than negotiate a single regulatory outcome.

Boundary summary

Form 40-OIP is the narrowest application form in this group: 1940 Act exemptive relief, variable-insurance subject matter, OIP review. It is not interchangeable with 40-APP (all other 1940 Act exemptive applications), with N-3/N-4/N-6 (Securities Act registration of the contracts themselves, no exemptive analysis), with N-1A (underlying fund registration), or with N-14 (fund-level reorganization registration). It is unrelated to 40-6B/40-8B25 (employees' securities companies) and 40-17F1/40-17F2 (custody compliance). For any question about the legal mechanics of variable-insurance portfolio substitutions, mixed-and-shared funding orders, or other OIP relief, 40-OIP is the primary source; the nearby datasets supply product context, non-insurance comparators, or downstream disclosure, but cannot replace the application itself.

Who Uses This Dataset

The users of the Form 40-OIP Files Dataset are concentrated: lawyers and compliance staff who draft, prosecute, and monitor exemptive-relief orders for variable insurance products, plus a smaller set of researchers and tooling teams.

1940 Act exemptive-relief counsel

Outside counsel preparing applications use the dataset as their primary precedent corpus. They mine prior filings for statutory analysis, accepted condition language, and representations on contract-holder impact. Amendments (40-OIP/A) matter most because they expose where staff pushed back and how applicants tightened conditions. The dataset feeds application drafting, comment-letter responses, and scoping advice on likely conditions.

In-house insurance regulatory and product counsel

Counsel at life insurers and separate-account sponsors use the corpus when planning a substitution, a new contract feature, or a separate-account restructuring. They focus on Section 26(c) substitution mechanics, Section 17(b) cross-transaction analysis, and the conditions section, since accepted condition wording is reused with light adaptation. Output: drafting precedent files, internal memos comparing intended structures to prior orders, and decisions on stand-alone versus multi-applicant filings.

Separate-account compliance officers

Compliance leads for variable annuity and variable life separate accounts map operational obligations to the conditions in granted orders: contract-holder notice requirements, expense caps, board-oversight commitments, and post-substitution monitoring. They use their own employer's filings as the authoritative record of what was promised, and peer filings to anticipate where staff expectations are heading. Output: control design, audit checklists, and substituted-fund monitoring certifications.

Variable annuity and variable life product managers

Product managers study the replaced-fund/replacement-fund pairs, the rationale offered (cost, performance, strategy fit, fund mergers), and projected fee impact on contract holders. The dataset supports sub-account lineup rationalization, product-roadmap decisions, and competitive analysis of how peer carriers reposition separate-account menus.

Transaction lawyers running portfolio substitutions

Lawyers executing the mechanics of a substitution pull the operative template: order of operations, redemption and contribution timing, valuation procedures, expense allocation between insurer and contract holders, and grandfathered fee arrangements. They focus on procedural representations and conditions preserving unitholder economics. Output: transaction documents, the substitution timeline, and coordination with affiliated and unaffiliated underlying fund advisers.

Broker-dealer counsel for variable contract distribution

Counsel for affiliated broker-dealers distributing variable contracts use the dataset to align selling-agreement obligations, prospectus supplements, and registered-representative communications with the substitution disclosures. They focus on contract-holder communication conditions and suitability representations. Output: supervisory procedure updates and distribution-side compliance reviews tied to substitution events.

Fund administrators executing substitutions

Administrators and accounting providers for the underlying funds use the application record to plan execution: trading mechanics, in-kind versus cash treatment, valuation conventions, and committed timing windows. Output: operational playbooks, NAV-strike planning around substitution dates, and reconciliation between the insurer's separate accounts and the fund administrator.

M&A diligence teams at insurers and reinsurers

Diligence teams evaluating block transactions, reinsurance treaties, or platform acquisitions touching variable insurance liabilities map a target's exemptive-relief footprint: which orders are in force, which conditions remain binding, and whether post-substitution monitoring obligations need to be priced or carved out. Output: diligence checklists, reps-and-warranties drafting, and post-closing integration plans that continue to honor outstanding conditions.

Academic researchers in insurance and 1940 Act regulation

Researchers use the dataset because it covers the full population of 40-OIP filings since October 2008. They focus on applicant identity, filing frequency by carrier and counsel, statutory provisions invoked, the evolution of standard conditions, and time-to-order patterns visible through amendments. Output: empirical work on regulatory drift, the substitution mechanism as a corporate-law instrument, and longitudinal studies of staff expectations across administrations.

Regtech and compliance-data vendors

Vendors building regulatory-content products for insurers and asset managers use the dataset as a structured corpus for precedent-search and condition-comparison features. They extract applicant names, statutory citations, transaction types, fund pairs, and condition language, and rely on amendment chains to surface staff-driven edits. Output: faceted precedent search, alerts on new filings naming a fund family or carrier, and dashboards on filing volume and topics.

AI/ML engineers building legal drafting and retrieval tools

Teams building RAG and document-drafting tools for legal and compliance users treat the corpus as a domain-specific training and retrieval set. They target the representations, legal analysis, and conditions sections, where recurring boilerplate and case-specific reasoning live. Output: embedding indexes for precedent search, evaluation sets for legal-summarization models, and prototypes that propose draft conditions or statutory analyses based on the closest historical analogues.

Specific Use Cases

The Form 40-OIP corpus concentrates the full precedent for variable-insurance exemptive relief into a focused set of applications and amendments. The use cases below reflect how legal, compliance, product, and tooling teams actually work the records.

1. Precedent search across portfolio substitutions

Counsel preparing a Section 26(c) substitution application query the corpus by replaced-fund and replacement-fund identity, statutory provisions invoked (6(c), 17(b), 26(c), Rule 17d-1), and the carrier's identity in the entities array. Hits surface comparable prior orders whose representations and conditions can be cited and adapted. The output is a precedent table feeding the statutory-basis section of a new application, plus a shortlist of analogous dockets to cite to staff.

2. Condition-language reuse and redline mining across amendment chains

Joining records on 812-XXXXX fileNo reconstructs each application docket as an ordered chain of 40-OIP -> 40-OIP/A -> 40-OIP/A submissions. Diffing the proposed-conditions and representations sections across that chain exposes exactly where staff comments tightened expense caps, notice periods, board-oversight commitments, or two-year fee-cap windows. In-house and outside counsel use these diffs to populate condition libraries and to predict the conditions a new filing will likely carry by the time an order issues.

3. RAG and legal-AI training corpora for exemptive drafting

ML teams building drafting and retrieval tools strip the EDGAR SGML envelope from each application HTML, segment the document by its conventional sections (cover, statement of applicants, requested order, statutory basis, representations, conditions, signatures), and index the segments for retrieval. The corpus serves as a domain-specific embedding set for precedent search, an evaluation set for clause-level summarization, and a fine-tuning source for models that propose draft conditions conditioned on a target transaction description.

4. Regulatory-pattern dashboards for insurance-product regtech

Vendors and internal regulatory-affairs teams aggregate metadata.json across the corpus to build dashboards on filing volume by carrier, counsel, and statutory hook, time-to-final-amendment per docket, and the spread of co-applicants per filing. Combined with extracted condition text, these dashboards surface trends such as the standardization of fee-cap windows, broader co-applicant rosters as carriers consolidate platforms, and shifts in staff appetite across administrations.

5. M&A and reinsurance due diligence on exemptive-relief footprints

Diligence teams reviewing a block transaction or platform acquisition pull every 40-OIP and 40-OIP/A naming the target insurer or its separate accounts via the entities[].cik and companyName fields. They reconstruct the in-force orders, extract the conditions that remain binding (post-substitution monitoring, expense allocation, contract-holder notice mechanics), and flag obligations the buyer will inherit. The output is a reps-and-warranties schedule of outstanding orders and a post-closing compliance plan that honors each order's conditions.

6. Substitution execution playbooks for fund administrators and transaction lawyers

Operations counsel and fund administrators preparing to execute a substitution extract the procedural representations from the operative (latest) 40-OIP/A: redemption and contribution sequencing, in-kind versus cash treatment, NAV-strike conventions, free-transfer windows for contract owners, and expense allocation between insurer and contract holders. These extracts feed the transaction timeline, NAV-strike planning, and reconciliation procedures between separate accounts and the underlying fund administrator on the execution date.

Dataset Access

The dataset is available through three access methods: a JSON metadata endpoint, a full archive download, and per-container monthly ZIP downloads. Filings are organized into monthly ZIP containers covering submissions from October 2008 to the present, grouped by year and month.

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

This endpoint returns dataset-level metadata (name, description, last update timestamp, earliest sample date, total record count, total size, covered form types, container format, and file types) along with the full list of monthly container files. Each container entry includes its size, record count, last updated timestamp, and direct download URL. This endpoint does not require an API key and can be polled to detect which containers have changed in the most recent refresh, allowing incremental downloads instead of refetching the whole archive.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-6996-9eda-846fc9df2645",
        

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

          4
            "name": "Form 40-OIP Files Dataset",
        

          5
            "updatedAt": "2026-04-15T11:59:16.363Z",
        

          6
            "earliestSampleDate": "2008-10-01",
        

          7
            "totalRecords": 288,
        

          8
            "totalSize": 16794453,
        

          9
            "formTypes": ["40-OIP", "40-OIP/A"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

          14
                "downloadUrl": "https://api.sec-api.io/datasets/form-40oip-files/2026/2026-03.zip",
        

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

          16
                "size": 412874,
        

          17
                "records": 4,
        

          18
                "updatedAt": "2026-04-15T11:59:16.363Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

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

Downloads the complete dataset as a single ZIP archive containing every monthly container. This endpoint requires authentication via your SEC API key passed as the token query parameter.

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

Downloads one monthly container ZIP, organized by YYYY/YYYY-MM.zip. Each container holds the metadata file and all submission documents (excluding images) for filings accepted by EDGAR in that month. This endpoint requires authentication via your SEC API key.

Frequently Asked Questions

What forms does this dataset cover?

The dataset covers Form 40-OIP, an application for exemptive, no-action, or interpretive relief under the Investment Company Act of 1940 routed to the SEC's Office of Insurance Products, and Form 40-OIP/A, which is an amendment to a previously filed 40-OIP application.

What does one record in this dataset represent?

One record is a single EDGAR submission of either Form 40-OIP or Form 40-OIP/A, identified by an 18-digit zero-padded SEC accession number. Each record is an accession folder containing one metadata.json describing the EDGAR submission header and one or more document files reproduced from the original EDGAR upload, with image attachments omitted.

Who files Form 40-OIP?

Applications are filed on behalf of a coordinated group of co-applicants in the variable insurance product chain — most commonly life insurance companies acting as depositors, their registered separate accounts, principal underwriters and broker-dealer affiliates, investment advisers to the underlying funds, and the underlying registered funds themselves. The lead insurer typically appears as filer of record on the EDGAR header, while every co-applicant is enumerated in the entities array and in the application body.

When are Form 40-OIP filings triggered?

Filing is event-driven, not periodic. A 40-OIP is triggered whenever applicants propose a transaction that would otherwise conflict with the 1940 Act — most often a portfolio substitution under Section 26(c), an affiliated transaction requiring relief under Section 17(b) or Rule 17d-1, a fund-of-funds or manager-of-managers structure under Section 6(c), or a related exchange offer under Section 11.

What time period does the dataset cover?

The dataset begins on 2008-10-01 — the month Form 40-OIP was introduced as a distinct EDGAR submission type to route Office of Insurance Products applications onto a dedicated form code — and runs through the current refresh date. Earlier insurance-product applications were submitted under predecessor or general application types and are outside the scope of this dataset.

What file formats are inside each record?

Each accession folder contains a metadata.json file plus one or more EDGAR document attachments. File types found in the dataset are HTML (the dominant format for the application body), JSON (reserved for metadata.json), TXT, and PDF. Image attachments registered as GRAPHIC in the EDGAR document inventory are excluded from the local archive but remain enumerated in metadata.documentFormatFiles.

How does this dataset differ from Form 40-APP?

Both 40-OIP and 40-APP are 1940 Act applications for exemptive orders citing provisions such as Section 6(c), 17(b), or 17(d). The split is jurisdictional: 40-APP is reviewed by the Chief Counsel's Office and other Investment Management branches and covers ETF orders, fund-of-funds, co-investment, and joint-transaction relief outside the insurance context, while 40-OIP signals routing to the Office of Insurance Products and is concentrated in variable annuity and variable life matters such as portfolio substitutions under Section 26(c).

How are amendments (40-OIP/A) related to the original 40-OIP?

Each 40-OIP/A is a self-contained restated application by the same applicant group, sharing the same 812-XXXXX file number as the original. Amendments respond to staff comments, refine conditions, update facts, or add co-applicants; the latest amendment in the chain is the operative document. Joining records by fileNo reconstructs the complete amendment chain for one application.