The Form N-VP Files Dataset collects every Form N-VP and Form N-VP/A submission disseminated on EDGAR, captured at the granularity of one EDGAR accession number. A single record is one website-availability notice filed under Rule 30e-3 of the Investment Company Act of 1940, paired with the structured EDGAR submission metadata that describes it. Form N-VP is filed by insurance company separate accounts that issue variable annuity and variable life insurance contracts; it is the notice an account files to satisfy its annual and semi-annual shareholder-report delivery obligation by posting those reports to a website and notifying contract owners, rather than mailing paper. Each record contains the original HTML notice — identifying the separate account, the underlying fund, the report-availability website, the Rule 30e-3 legend, and free paper-copy instructions — together with a metadata.json descriptor carrying form type, filer identity, and series-and-contract structure. The dataset begins in April 2021, the first month EDGAR accepted Form N-VP after its introduction in EDGAR Release 20.3, and extends to the present.
Programmatically retrieve the full list of dataset archive files, download URLs and dataset metadata.
Dataset Index JSON API
Download the entire dataset as a single archive file.
Download Entire Dataset:
Download a single container file (e.g. monthly archive) from the dataset.
Download Single Container:
The Form N-VP Files Dataset is built from notice documents, not disclosure reports. Form N-VP operationalizes Rule 30e-3 under the Investment Company Act of 1940, adopted in SEC Release 33-10765, as applied to the insurance company separate accounts that issue variable annuity and variable life insurance contracts. Rule 30e-3 permits such a fund to satisfy its obligation to transmit annual and semi-annual shareholder reports by posting those reports to a publicly accessible website and notifying contract owners of their availability, in lieu of mailing paper copies. Form N-VP is the vehicle through which that website-availability notice reaches the SEC and the public record, and this dataset captures the full population of those notices and their amendments.
Because the substantive financial content — the actual shareholder reports — resides on a website rather than inside the form, the body of an N-VP filing is short and notice-oriented. It identifies the parties, directs contract owners to where the reports can be found, carries the legend explaining the website-availability arrangement, and tells contract owners how to request free paper copies. A Form N-VP/A is an amendment to a previously filed N-VP notice; in practice the amendments in this dataset frequently function as prospectus or notice supplements that disclose a discrete change affecting the contracts — a variable investment option closing to new investment, fund renamings, or adviser and subadviser changes — layered onto the underlying Rule 30e-3 notice structure.
The dataset covers both N-VP original notices and N-VP/A amendments across the entire filer population from April 2021 onward. Records are packaged into monthly ZIP archives partitioned by filing date as YYYY/YYYY-MM.zip; each monthly archive expands to a YYYY-MM/ directory whose direct children are the accession-number folders for the filings disseminated in that month. The document file types found in the dataset are HTML (the notice body), JSON (the metadata), and PDF.
A single record in this dataset is one complete Form N-VP or Form N-VP/A submission as disseminated on EDGAR, captured at the granularity of one EDGAR accession number. Physically, each record is a folder named for the 18-digit accession number with its dashes removed (for example 000119312525330413, corresponding to accession 0001193125-25-330413). The folder holds two kinds of content: a single metadata.json describing the submission, and the original submission document or documents — almost always one HTML notice — preserved as disseminated by EDGAR, with embedded and attached image files removed. A record is therefore both the structured metadata view of the filing and the underlying notice text, paired under one accession identifier.
Each record is organized into two layers stacked under the accession folder:
Metadata layer — a single metadata.json file that captures the EDGAR submission header in structured form: form type, accession number, timestamps, the filer (separate account) identity, the underlying series-and-contract structure, and an enumerated list of the documents in the submission.
Document layer — the primary N-VP notice, an HTML file wrapped in EDGAR's SGML <DOCUMENT> envelope. N-VP submissions are typically single-document; where a submission carries additional non-image documents, they sit alongside the primary notice.
The two layers are bound by the document list inside metadata.json: each document recorded under documentFormatFiles[] carries a documentUrl whose basename matches a file physically present in the folder. File naming is filer-specific — some filing agents use structured stems such as d17428dnvpa.htm, others use descriptive names such as prefadvmacquariefundchngsupp.htm — but the metadata always points to the file on disk.
metadata.json submission descriptorThis file is the structured spine of the record and is present exactly once per folder. Its top-level fields describe the submission as a whole:
formType — N-VP for an original notice or N-VP/A for an amendment.accessionNo — the EDGAR accession number in canonical dashed form (e.g. 0001193125-25-330413).filedAt — the submission timestamp, including timezone offset.effectivenessDate — the date the filing became effective.description — a short human-readable label, such as Form N-VP/A - [Amend].linkToFilingDetails, linkToTxt, linkToHtml — URLs to, respectively, the primary document on sec.gov, the complete SGML submission text file, and the EDGAR filing index page.linkToXbrl — present in the schema but empty, since Form N-VP carries no XBRL data.id — an internal record identifier.Three nested blocks carry most of the interpretive value:
documentFormatFiles[] enumerates every document in the submission. Each entry records a sequence number, a size in bytes (as a string), the documentUrl, a description, and a type. The primary N-VP notice is sequence: "1". The final entry is the complete submission text file — the full SGML wrapper for the entire accession — carried with a blank type. A companion dataFiles[] array exists for additional data files but is empty for these notices.
entities[] identifies the filer, the insurance company separate account that is the registrant. Each entry carries the companyName (suffixed (Filer), e.g. SEPARATE ACCOUNT A (Filer)), the EDGAR cik, the SEC fileNo (e.g. 333-137052), the act under which the filing is made (e.g. 33 for the Securities Act), the entity-level type (the form type), stateOfIncorporation (e.g. NY, DE, occasionally absent), fiscalYearEnd as MMDD, irsNo, and filmNo. This block answers who the separate account behind the notice is.
seriesAndClassesContractsInformation[] ties the notice to the registered investment company's internal structure. Each entry names a series by its EDGAR series identifier (e.g. S000009119) and name, and lists classesContracts[], each with a classContract identifier (e.g. C000043354) and a name that is typically the variable annuity or variable life product (for example EQUI-VEST At Retirement or PREFERRED ADVANTAGE VARIABLE ANNUITY). This block answers which contracts and products the notice covers.
The substantive content of the record is the HTML notice, stored inside EDGAR's SGML <DOCUMENT> wrapper. The wrapper header carries <TYPE> (e.g. N-VP/A), <SEQUENCE>, <FILENAME>, and <DESCRIPTION> fields, and the <TEXT> block holds the full HTML body. The wrapper is metadata about the document; the HTML inside is the contract-owner notice itself.
The HTML body is short, narrative, and contract-owner-facing. It typically contains:
The content is predominantly narrative legal-and-administrative text. Tabular structure appears only incidentally — most often as fund-name or adviser/subadviser change tables in supplement-style amendments — rather than as standardized financial tables.
Each record includes the structured metadata.json descriptor and the complete set of non-image documents from the original EDGAR submission, with filenames preserved as filed. For the overwhelming majority of N-VP submissions this means the primary HTML notice plus its metadata. The document file types found in the dataset are HTML, JSON (the metadata), and PDF; PDF appears when a filer submitted a notice or attachment in that format, though HTML is the dominant body format.
Image files embedded in or attached to the original submission are excluded. The actual annual and semi-annual shareholder reports are not part of the filing at all — by the design of Rule 30e-3 those reports live on the separate account's website, and the N-VP notice references them only by URL, so they are present in no record. The complete SGML submission text file is referenced by linkToTxt in the metadata and is the source from which the wrapped document is drawn, rather than a separate body document.
Form N-VP is a recent form, introduced through EDGAR Release 20.3 and accepted beginning in 2021, well into the era of HTML and structured EDGAR submissions. There is consequently no ASCII or legacy-format era to account for: notices have been filed as HTML wrapped in SGML from the start, and the metadata schema, series-and-contract tagging, and accession-folder packaging have been consistent across the dataset's span. The only recurring structural variation is between original N-VP notices and N-VP/A amendments, the latter more likely to read as substantive prospectus or notice supplements with disclosed contract changes than as bare availability notices.
accessionNo in the metadata; the two are the same identifier in different notations.documentFormatFiles[] is the authoritative bridge between metadata and files: match its documentUrl basenames to the files on disk, and treat the trailing blank-type entry as the complete submission text file rather than a distinct content document.N-VP/A records are amendments and are best read in relation to a prior notice for the same separate account and contracts; seriesAndClassesContractsInformation[] is the most reliable key for grouping a notice with the products and series it concerns.metadata.json, while the disclosed change, website URL, legend, and paper-copy instructions must be parsed from the narrative HTML body.Each record in this dataset is one Form N-VP (or Form N-VP/A) notice filed on EDGAR by an insurance company separate account that issues variable annuity or variable life insurance contracts. The separate account is an investment company registered under the Investment Company Act of 1940; it is the registrant and obligated filer, typically filing under its sponsoring life insurer's central registration. Form N-VP is a short, administrative notice. It does not contain a shareholder report or financial statements. It is the document an issuer files to invoke the website-delivery option under Rule 30e-3, signaling that the account's annual or semi-annual shareholder reports are available online rather than mailed in paper.
Three parties should be kept distinct:
Separate accounts filing N-VP are generally registered on:
The trigger is procedural, not periodic-financial and not event-driven in the corporate-event sense. Under Section 30(e) of the 1940 Act and Rules 30e-1 and 30e-2, an investment company must transmit annual and semi-annual reports to its shareholders — here, contract owners. Rule 30e-3 lets the issuer satisfy that duty instead by posting the reports to a website and providing a short notice of availability, provided conditions are met: continuous online availability of current and prior reports, free paper copies on request, and proper notice.
When a separate account relies on this website-availability method, it must file the notice as Form N-VP. The filing is therefore a recurring consequence of relying on the rule for a given reporting period. Its cadence tracks the annual and semi-annual report cycle of the account and its underlying funds, not a single fixed statutory deadline, and it recurs each period the issuer continues to rely on Rule 30e-3. Each notice typically identifies the separate account and the underlying registered investment company, gives the website address for the reports, reproduces the legend telling contract owners the reports are available online, and explains how to request free paper copies.
Form N-VP/A records amend a previously filed N-VP — for example, to correct a website address, legend, or account/fund identification. An amendment supplements an existing notice rather than representing a new reliance event. EDGAR began accepting Form N-VP in 2021, consistent with the Rule 30e-3 compliance timeline for variable-contract issuers; the dataset's earliest records date to April 2021. The form was created to operationalize Rule 30e-3 for separate accounts (adopting release Rel. No. 33-10765; implemented on EDGAR via EDGAR Release 20.3) and has existed only as an electronic submission, so there is no pre-EDGAR analog.
Form N-VP occupies a narrow, easily misread corner of Investment Company Act reporting. It is not a financial report, a holdings disclosure, or a registration statement. It is a short notice filing that variable annuity and variable life insurance separate accounts use to satisfy shareholder-report delivery obligations under Rule 30e-3. The datasets most likely to be confused with it cluster in three groups: the delivery regime N-VP plugs into (Rule 30e-3 vs. Rule 30e-1, and the historical Form N-30D), the substantive periodic reports N-VP merely points to (N-CSR, N-PORT, N-CEN, N-PX), and the variable-contract registration statements (N-4, N-6) for the products behind the same separate accounts.
The most important comparison is to a regime, not a form. Rule 30e-1 is the baseline obligation: a registered investment company must transmit annual and semi-annual shareholder reports to shareholders, historically as mailed paper. Rule 30e-3 is the alternative "notice and access" method that satisfies the same obligation by posting reports online and sending a brief notice instead of the full document.
Form N-VP is the EDGAR-filed embodiment of the Rule 30e-3 notice path for variable-contract separate accounts. It does not replace the report; it identifies where the report is posted and how contract owners can demand paper for free. The boundary is strict: N-VP confirms that delivery occurred and by what method, but carries none of the financial content Rule 30e-1 delivery would have placed in front of a shareholder.
Form N-CSR is the certified shareholder report: audited annual and unaudited semi-annual financial statements, the schedule of investments, management discussion, and officer certifications. This is the substantive content Rule 30e-3 makes available on a website.
N-VP and N-CSR are complementary, not interchangeable. N-CSR is rich, periodic, financially detailed, and certified; N-VP is thin, notice-cycle-tied, and carries no financial statements. To read what a contract owner could have seen, go to N-CSR; to confirm that a separate account used website availability to deliver it, go to N-VP. Neither substitutes for the other.
N-30D was the legacy filing for funds' semi-annual and annual shareholder reports before that role moved to N-CSR in 2003. It fills the historical "report" slot N-CSR now occupies, and some long-horizon datasets still reference it.
The contrast with N-VP mirrors the N-CSR contrast, with a temporal twist: N-30D was report-bearing, while N-VP is notice-only and arrived nearly two decades later (filings accepted from 2021 under Release 33-10765 and EDGAR Release 20.3). There is no lineage between them; N-VP did not evolve from N-30D, and treating it as a modern N-30D inverts the point, since N-30D carried the financial report and N-VP deliberately does not.
Form N-PORT is the structured (XML) portfolio-holdings report that registered management investment companies file monthly, with position-level valuation and risk data. It is granular and machine-readable.
N-PORT is N-VP's opposite on nearly every axis: periodic rather than notice-triggered, holdings-level rather than delivery-level, structured data rather than a short legend, and focused on what the fund owns rather than how reports reach contract owners. To analyze the assets behind a contract's investment options, use N-PORT; N-VP says nothing about holdings.
Form N-CEN is the annual structured "census" in which a registered investment company reports operational facts: organizational data, service providers, securities issued, and related registration-adjacent details. It replaced Form N-SAR.
N-CEN and N-VP overlap only in being fund-filed and administrative. But N-CEN is a comprehensive, periodic, structured snapshot of an entire fiscal year, while N-VP is a non-periodic notice tied to a specific report-availability cycle. N-CEN can show whether a fund elected the Rule 30e-3 approach at a census level; N-VP is the operational artifact of actually exercising that election for a given report.
Forms N-4 (variable annuity) and N-6 (variable life) are the registration statements and prospectuses for exactly the products whose separate accounts file N-VP. They describe the contract: investment options, fees and charges, death benefits, surrender provisions, and separate-account operation.
This is the closest comparison on the issuer/product axis, since N-4/N-6 and N-VP concern the same separate accounts and contracts. The difference is purpose and lifecycle stage. N-4 and N-6 are foundational, prospectus-grade documents filed to register and offer the product and amended to keep disclosure current; N-VP is an incidental, recurring notice filed during the product's operating life solely to mechanize report delivery. To understand the product, read N-4/N-6; to track report-delivery mechanics for its separate accounts, use N-VP.
Form N-VP is defined by what it omits. It is the only filing in this group whose purpose is to point to a report rather than to be one. Its closest functional sibling is the Rule 30e-3 regime it implements; its closest content-bearing counterpart is N-CSR; its closest product counterpart is the N-4/N-6 family. The practical boundaries:
Related datasets supply the substance N-VP references, but none substitutes for it as a record of the Rule 30e-3 delivery mechanism for variable annuity and variable life separate accounts.
Because each Form N-VP filing links a named separate account, an underlying registered fund, a report-availability URL, the required Rule 30e-3 legend, and paper-copy request instructions, the dataset is useful to a focused set of compliance, administration, legal, data, and strategy functions across the variable-insurance market.
Compliance officers for variable annuity and variable life products use the dataset to confirm the Rule 30e-3 notice obligation was met for each separate account they oversee. They reconcile the separate-account name, underlying fund, and filing and amendment dates against their internal delivery calendar to surface gaps where a product line was expected to be covered but no notice appears. The output supports audit trails and exam readiness: demonstrating that each website-delivery election was perfected on time. N-VP/A amendments matter because they signal corrections to the account name, fund, or report website that delivery representations must track.
Administrators and transfer agents servicing insurance-dedicated funds use the notice operationally. They focus on the website address, legend language, and paper-copy request instructions, the customer-facing elements they must keep synchronized with fulfillment vendors and their own systems. They verify that the published URL resolves to live, current reports, that fee-free paper requests are honored as stated, and that account and fund names match the entities they administer. This drives delivery-cycle controls, vendor oversight, and exception handling when a posted report goes missing.
Counsel advising insurers and their separate accounts use the dataset to draft and benchmark N-VP notices. They compare their legend text, report-availability description, and paper-copy instructions against the conventions in peer filings to confirm the notice meets Rule 30e-3 conditions. Filing and amendment history shows when an election was made, modified, or restated, which matters for assessing whether delivery obligations were continuously satisfied. The result feeds drafting templates and defensible records around the election.
Filing agents and in-house EDGAR staff who prepare N-VP and N-VP/A submissions use prior filings as a reference for form usage, header tagging, and entity naming. They check how separate accounts and underlying funds are associated to format new submissions consistently, resolve which entity files for a given product structure, and model amendment practice. This reduces rejected or miscoded filings across a filer's family of accounts.
Teams building filing-monitoring and regulatory data products treat the full N-VP and N-VP/A population from April 2021 forward as a clean, bounded corpus to parse and link. They extract the separate-account name, underlying fund, report URL, and filing dates into structured records, join them to broader entity and product reference data, and expose Rule 30e-3 elections to programmatic queries. The bounded set supports extraction pipelines, URL-field validation, deduplication of amendments against originals, and alerting when a tracked filer files a new notice.
Researchers studying disclosure delivery use the complete record to measure how broadly and quickly insurers adopted the website option for variable products, analyzing filing volume and timing, the distribution of accounts and funds adopting the election, and amendment frequency as a proxy for revised delivery practice. Product-strategy and competitive-intelligence analysts at insurers watch the same fields for peer activity: a new N-VP signaling a move to website delivery, or an amendment revealing a renamed account, changed underlying fund, or updated report site, each a marker of product launches, restructurings, or platform changes.
Form N-VP is single-purpose, but its contents sit at the intersection of compliance evidence, customer-facing disclosure, entity identification, and product strategy. Compliance, administration, transfer-agent, and legal teams confirm and document the website-delivery election; filing agents and data engineers prepare and structure the filings; researchers and strategy analysts measure and monitor adoption across the variable-insurance market.
Form N-VP records pair structured submission metadata with a short, contract-owner-facing Rule 30e-3 notice. The use cases below draw on the parts of the record that carry signal: the filer and series-and-contract identifiers in metadata.json, the filing and amendment dates, and the website URL, legend, and paper-copy instructions in the HTML body.
Reconcile website-delivery elections against a coverage calendar. Compliance teams join the entities[] separate-account name and seriesAndClassesContractsInformation[] contract identifiers to their internal list of variable annuity and variable life product lines, then check filedAt and effectivenessDate against expected delivery cycles. The output is an exception list of product lines where a Rule 30e-3 notice was expected but no N-VP record appears, plus a dated audit trail for exam readiness.
Track amendments as product-change signals. N-VP/A records frequently function as prospectus or notice supplements. Filtering on formType = N-VP/A and parsing the HTML body surfaces discrete contract events — an investment option closing to new investment, fund renamings, or adviser and subadviser changes. Analysts use this to flag account renamings, changed underlying funds, or updated report sites as markers of product restructurings and platform changes.
Validate the report-availability URL. Administrators and transfer agents extract the website address, legend text, and paper-copy request instructions from each notice body, then verify that the published URL resolves to live, current annual and semi-annual reports and that the named account and fund match the entities they service. This drives vendor oversight and exception handling when a posted report goes missing.
Benchmark notice language across peer filings. Disclosure counsel compare their legend wording, report-availability description, and paper-copy instructions against the conventions in other filers' notices to confirm a draft meets Rule 30e-3 conditions. The cross-filing comparison feeds reusable drafting templates and a defensible record of the election.
Build a structured Rule 30e-3 election corpus. Data engineering teams parse the full N-VP and N-VP/A population from April 2021 forward, extracting separate-account name, underlying series and contracts, report URL, and filing dates into linkable records keyed by accessionNo and CIK. They deduplicate amendments against originals, validate URL fields, and emit alerts when a tracked filer submits a new notice.
Measure adoption of website delivery across the variable-insurance market. Researchers aggregate filing volume, timing, and the distribution of separate accounts and funds electing notice-and-access, using amendment frequency as a proxy for revised delivery practice. This quantifies how broadly and quickly insurers moved variable products to the website option after the form's 2021 introduction.
The Form N-VP Files Dataset can be accessed programmatically through the dataset index JSON API or downloaded directly as a full archive or as individual monthly container files.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-nvp-files.json
This endpoint returns the dataset metadata, the download URL for the entire dataset, and the list of all container files. The metadata includes the dataset name, description, last updated timestamp, earliest sample date, total records, total size, form types covered, container format (ZIP), and content file types (HTML, JSON, PDF). For each container, it provides the partition key, size, record count, last updated timestamp, and download URL. You can poll this endpoint daily to determine which containers changed in the most recent refresh run and then download only those partitions. This endpoint does not require an API key.
1
{
2
"datasetId": "1f13365b-9ae0-6975-bfb3-35108dd56e01",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-nvp-files.zip",
4
"name": "Form N-VP Files Dataset",
5
"updatedAt": "2026-03-21T02:51:19.000Z",
6
"earliestSampleDate": "2024-11-01",
7
"totalRecords": 3642,
8
"totalSize": 35875742,
9
"formTypes": ["N-VP", "N-VP/A"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["HTML", "JSON", "PDF"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-nvp-files/2026/2026-03.zip",
15
"key": "2026/2026-03.zip",
16
"size": 1382878,
17
"records": 154,
18
"updatedAt": "2026-03-21T02:51:19.000Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-nvp-files.zip?token=YOUR_API_KEY
Downloads the complete dataset as a single ZIP archive containing all container files. This endpoint requires an API key.
Download Single Container: https://api.sec-api.io/datasets/form-nvp-files/2026/2026-03.zip?token=YOUR_API_KEY
Downloads one individual monthly container instead of the full dataset. Containers are partitioned as YYYY/YYYY-MM.zip; use the keys and download URLs listed in the index JSON's containers array to target a specific month. This endpoint requires an API key.
The dataset covers Form N-VP and its amendment, Form N-VP/A — the website-availability notice that insurance company separate accounts file under Rule 30e-3 of the Investment Company Act of 1940 for variable annuity and variable life insurance contracts.
One record is a single Form N-VP or N-VP/A submission as disseminated on EDGAR, captured at one accession number. It is stored as a folder containing a metadata.json descriptor and the original notice document, almost always one HTML file, with embedded images removed.
The filer is the insurance company separate account that issues the variable annuity or variable life contracts and is registered as an investment company under the 1940 Act — not the underlying portfolio fund and not the contract owner. These accounts are generally registered on Forms N-3, N-4, or N-6.
No. By the design of Rule 30e-3, the annual and semi-annual shareholder reports live on the separate account's website, and the N-VP notice references them only by URL. The substantive financial reports are filed separately under the N-CSR regime.
The dataset begins in April 2021, the first month EDGAR accepted Form N-VP following its introduction in EDGAR Release 20.3, and extends to the present. There is no pre-EDGAR or legacy-format era, since the form has existed only as an electronic HTML submission.
Records are packaged into monthly ZIP archives partitioned by filing date as YYYY/YYYY-MM.zip. Within each record, the content file types are HTML (the notice body), JSON (the metadata), and PDF.
N-CSR is the certified shareholder report containing audited financial statements, the schedule of investments, and officer certifications — the substantive content Rule 30e-3 makes available online. Form N-VP carries none of that financial content; it is the thin notice that confirms website availability and tells contract owners where to find the report and how to request free paper copies.