Form N-23C-1 Files Dataset

The Form N-23C-1 Files Dataset is a complete EDGAR collection of Form N-23C-1 and Form N-23C-1/A submissions — the notices that registered closed-end management investment companies file under Rule 23c-1 of the Investment Company Act of 1940 to report purchases of their own outstanding securities during a prior calendar month. One record corresponds to one EDGAR accession: a single notice covering one closed-end fund's repurchase activity for one calendar month, including transaction dates, share counts, prices, asset coverage at the time of purchase, and counterparties. Filings are made by registered closed-end funds acting as the issuer of the repurchased securities; sponsors of open-end funds, ETFs, UITs, and operating companies do not appear in this dataset. Coverage begins with EDGAR's earliest N-23C-1 submissions in August 1994 and continues to the present, with records delivered as monthly ZIP containers built from EDGAR's TXT, JSON, and HTML artifacts.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset captures every EDGAR submission of Form N-23C-1 and its amendment Form N-23C-1/A, the statutory notice that a registered closed-end management investment companies submits when it has repurchased — or intends to call or redeem — securities of which it is the issuer. Form N-23C-1 is the operative reporting vehicle for Rule 23c-1 of the Investment Company Act of 1940, which conditions the circumstances under which a closed-end fund may purchase its own outstanding shares. The N-23C-1/A variant is used to correct or supplement a previously transmitted notice. The substantive content of each filing is narrow and standardized: registrant identity, the class and par value of the security being repurchased, the date(s) of repurchase, the number of shares, the price paid per share, the approximate asset value or asset coverage per share at the time of purchase, and the identity of the seller or seller's broker. In effect, each filing is a one-page transactional disclosure carrying a small schedule of purchases rather than a narrative or financial-statement filing.

The dataset spans August 1994 to the present and covers the entire filer population of registered closed-end management investment companies that report repurchases under Rule 23c-1. The form has remained low volume across this window, so per-record content is shallow but historically continuous. Records are packaged for distribution as monthly ZIP archives keyed <year>/<year>-<month>.zip (for example 2004/2004-09.zip); each monthly archive unpacks to a sibling directory holding one accession number sub-folder per filing. The file types found inside containers are TXT, JSON, and HTML — quantitative content lives only as text or HTML inside the primary document, never as a separately tagged data file, because Form N-23C-1 is not an XBRL-tagged form.

Content Structure of a Single Record

What one record represents

One record in the Form N-23C-1 Files Dataset corresponds to a single EDGAR submission of Form N-23C-1 or its amendment Form N-23C-1/A — that is, one accession number filed by a registered closed-end management investment company giving notice, under Rule 23c-1 of the Investment Company Act of 1940, of purchases it has made of its own outstanding securities during a prior calendar month. The record unit is the filing, not the transaction: a single N-23C-1 may report multiple repurchase transactions in one schedule, but all of them roll up into one accession-number record.

On disk, each record materializes as a folder whose name is the EDGAR accession number with the dashes removed (an 18-digit string such as 000116923204004839). The folder contains a metadata.json header file plus the original EDGAR submission documents for the filing, excluding image files. Because Form N-23C-1 is operationally minimal — a short notice with a small schedule — most records contain only two artifacts: the metadata.json and a single primary form document.

Two structural layers

Each record has two structural layers:

1. A JSON metadata header (metadata.json) derived from the EDGAR submission header, capturing form type, accession identifiers, dates, filer/entity descriptors, and a manifest of constituent documents.
2. The primary N-23C-1 document itself, wrapped in EDGAR's SGML <DOCUMENT> container, holding either fixed-width ASCII text or HTML inside the wrapper. The form body inside the wrapper carries the notice heading, registrant identification, the tabular schedule of purchases, an optional REMARKS block, and a signature block.

Additional exhibit documents may appear alongside the primary document when filers attach them, though for this form type they are rare; image-type exhibits are excluded by the dataset. The documentFormatFiles array in metadata.json enumerates the constituent documents and also references EDGAR-side aggregates (notably the "Complete submission text file") whose URLs are listed in metadata but are not materialized as separate files inside the folder.

metadata.json

metadata.json is a flat JSON object holding the parsed EDGAR submission header for the accession. The fields most relevant to interpreting a single record are:

• formType — "N-23C-1" for original notices, "N-23C-1/A" for amendments.
• accessionNo — the canonical dashed accession number (e.g. "0001169232-04-004839"); the host folder is the same string with dashes removed.
• filedAt — ISO 8601 timestamp with timezone, marking the moment EDGAR accepted the submission.
• periodOfReport — the calendar month-end (e.g. "2004-07-31") for which repurchases are being reported. This is the as-of date for the schedule of purchases and typically precedes filedAt by several weeks.
• description — the human-readable form description, e.g. "Form N-23C-1 - Reports by closed-end investment companies of purchase of their own securities".
• linkToFilingDetails, linkToTxt, linkToHtml — URLs into www.sec.gov for the primary document, the EDGAR aggregate submission text file, and the EDGAR filing-index HTML page.
• linkToXbrl — present but empty; Form N-23C-1 has never been an XBRL-tagged form.
• documentFormatFiles — an array of objects, each with sequence, size (bytes as a string), documentUrl, description, and type. The primary form document is listed at sequence: "1", while the EDGAR full-submission text aggregate often appears as a second entry with a blank type and blank sequence.
• dataFiles — an array, empty for this form type because no XBRL or other structured data files are associated with N-23C-1.
• entities — an array of filer/co-filer objects derived from the EDGAR header. Each entity carries companyName (with a role suffix such as (Filer)), zero-padded ten-digit CIK, IRS number, fileNo (the SEC file number, typically beginning with the 817- series prefix that designates closed-end investment companies), fiscalYearEnd as an MMDD string, act ("40" for the Investment Company Act of 1940, the statutory basis of the form), filmNo (the EDGAR film number), and type (the form type repeated for that filer role).
• id — an internal hash identifier for the record.

The primary N-23C-1 document

The primary document is delivered as a file whose extension is typically .txt but whose contents are an EDGAR SGML <DOCUMENT> wrapper. The wrapper has a stable shape:

          1
          <DOCUMENT>
        

          2
          <TYPE>N-23C-1
        

          3
          <SEQUENCE>1
        

          4
          <FILENAME>d60672_n23c1.txt
        

          5
          <DESCRIPTION>FORM N-23C-1
        

          6
          <TEXT>
        

          7
          ... form body ...
        

          8
          </TEXT>
        

          9
          </DOCUMENT>
        

<TYPE> echoes the form type, <SEQUENCE> is the position of this document within the submission, <FILENAME> and <DESCRIPTION> identify the document, and <TEXT> brackets the form body. Inside <TEXT>, the body is laid out in fixed-width ASCII (or, for more recent filings, HTML) and ordinarily contains the following blocks in order:

1. Form heading and statutory citation. A header that names the form and cites Rule 23c-1 under the Investment Company Act of 1940.
2. Reporting period line. A line of the form REPORT FOR CALENDAR MONTH ENDING <date>, whose date matches metadata.periodOfReport.
3. Registrant identification block. The registrant's legal name and, in many filings, its address and SEC registration number, presented as a centered typographic block.
4. Schedule of purchases. A tabular schedule listing each repurchase transaction. Columns conventionally are (a) transaction date, (b) security identification — class and par value, (c) number of shares purchased, (d) price per share, (e) approximate asset value or asset coverage per share at the time of purchase, and (f) name of the seller or seller's broker. In the SGML/ASCII era the table is delimited with EDGAR's pseudo-table markers <TABLE>, <CAPTION>, <S>, and <C>; these are typesetting hints, not real HTML tables, and must be parsed as fixed-width text.
5. REMARKS block. A free-text REMARKS: paragraph, often empty, used by filers to explain context such as the source of authority for the purchases or a reference to a prior board action.
6. Signature block. The registrant's name reiterated, a statement date, and a signer line carrying /s/ <name> together with the signer's printed name and title (typically an officer such as the Secretary or Treasurer).

Other constituent documents

Although documentFormatFiles may list additional entries — most commonly the EDGAR aggregate "Complete submission text file" — these are EDGAR-side artifacts referenced by URL and are not materialized inside the per-record folder. When filers do attach genuine exhibits (uncommon for this form), they appear as additional documents alongside the primary one, subject to the dataset's image-file exclusion.

Included content

Each record includes:

• The structured EDGAR header serialized as metadata.json, with form-type, accession identifiers, timestamps, period of report, entity descriptors (CIK, IRS number, SEC file number, film number, fiscal year end, statutory act code), and the manifest of constituent documents.
• The primary Form N-23C-1 document (or its amendment for N-23C-1/A), preserving the original EDGAR SGML <DOCUMENT> wrapper around either ASCII or HTML form content, including the schedule-of-purchases table and the signature block.
• Any non-image exhibit documents the filer attached to the submission.

Excluded or separate content

The dataset excludes image files from the original EDGAR submission. It does not materialize the EDGAR "Complete submission text file" aggregate as a sibling file inside the folder, even though documentFormatFiles references it and linkToTxt exposes its URL. Because N-23C-1 is not a structured-data form, no XBRL or other machine-readable financial data files are present; linkToXbrl and dataFiles are correspondingly empty.

Stability of required content over time

The substantive content requirements of Form N-23C-1 — registrant identification, class and number of securities repurchased, transaction dates, prices, asset coverage or asset value, and counterparties — have been stable across the August 1994-to-present window covered by the dataset. The form has not accumulated the layered, multi-Item complexity of registrant disclosure forms; it remains a short notice tied directly to Rule 23c-1's substantive conditions on closed-end fund repurchases. Variation across the historical record is therefore largely typographic and incidental: the ordering and labelling of schedule columns, the inclusion or omission of a remarks paragraph, and the form of the signature attestation, rather than structural additions to required content. The amendment variant (N-23C-1/A) appears across the entire window and uses the same internal anatomy as the original, distinguished primarily by formType in metadata.json.

Evolution of presentation format

The presentation format of the primary document has evolved inside the SGML <DOCUMENT> wrapper rather than around it. The earliest filings, from the mid-1990s through the early 2000s, are wrapped plain-text ASCII: the form body inside <TEXT> is fixed-width text, and the schedule of purchases uses EDGAR's pseudo-table markers (<TABLE>, <CAPTION>, <S>, <C>) to typeset columns. More recent filings increasingly carry HTML inside the same <DOCUMENT> wrapper, with the schedule rendered as a true HTML <table> and the form body marked up with HTML paragraphs and styling. The outer SGML wrapper and the metadata.json shape are unchanged across this transition.

Interpretation notes

• The periodOfReport field is the as-of date for the repurchase schedule, not the filing date; the two can differ by weeks. Time-series analyses keyed on when repurchases occurred should use periodOfReport, while latency analyses should compare it to filedAt.
• Because the schedule of purchases is embedded as ASCII or HTML inside the SGML wrapper, per-transaction extraction (date, security, shares, price, asset coverage, seller) requires either fixed-width text-table parsing for older filings or HTML-table parsing for newer ones. There is no canonical structured representation in the dataset.
• entities[].act = "40" is a reliable signal that the filer is reporting under the Investment Company Act of 1940, consistent with the statutory basis of the form. SEC file numbers in this dataset typically begin with the 817- prefix designating closed-end investment companies.
• The accession folder name and metadata.accessionNo differ only by dashes and form a stable join key between on-disk records and EDGAR identifiers.
• Some entries in documentFormatFiles reference URLs (notably the EDGAR aggregate text file) that are not materialized as files inside the folder; consumers should treat the manifest as a superset of the local file set rather than a one-to-one inventory.
• N-23C-1/A amendments do not necessarily restate the full original schedule; treat them as corrective or supplemental notices and resolve amendment chains by linking on registrant CIK and periodOfReport.
• Multiple entities may appear when co-filers, parent registrants, or series/class trusts are involved. Each entity's role is captured in the companyName suffix (e.g. (Filer)), and the closed-end fund itself is typically the entity carrying the 817- series file number.
• The registrant identification block inside the primary document and the entities[].companyName value in metadata.json should agree on the legal name of the filing fund; mismatches usually indicate either a corporate name change between filings or the presence of a parent/series structure where the named filer is not the entity actually conducting the repurchase.

Who Files or Publishes This Dataset, and When

Who files

Form N-23C-1 is filed by registered closed-end management investment companies acting as the issuer of the securities being repurchased. The filer population is narrow:

• The filer is registered with the SEC under the Investment Company Act of 1940 (typically carrying an SEC file number with the 817- closed-end series prefix; entities[].act is "40" in the metadata).
• It must be of the closed-end type — a management company whose shares are not continuously redeemable. Closed-end funds usually list common stock on an exchange and may also have preferred shares or other senior securities outstanding.
• The filing concerns the fund's purchase of its own outstanding securities, not transactions in portfolio holdings.

The following are outside the N-23C-1 filer population:

• Open-end funds (mutual funds) and UITs — different structural regime; do not file N-23C-1.
• Business development companies (BDCs) — closed-end-style entities but subject to a distinct framework under Sections 55–65 of the Act.
• ETFs — open-end or UIT structure; creation/redemption activity is not reported on N-23C-1.
• Operating companies (10-K/10-Q filers) — issuer repurchases are disclosed under Item 703 of Regulation S-K and, where applicable, under Schedule TO; the Investment Company Act regime does not apply.
• Security holders of an N-23C-1 filer — they are recipients of the underlying repurchase activity, not filers.

What triggers a record

The filing is transaction-driven but reported on a monthly cadence. The trigger is the closed-end fund's purchase of its own outstanding securities during a calendar month under conditions governed by Rule 23c-1. The report covers that calendar month and is filed shortly afterward.

Each Form N-23C-1 carries:

• the calendar month-end period of report (metadata.periodOfReport);
• a schedule of repurchase transactions for that month — transaction date, class and par value of the security, shares purchased, price per share, approximate asset coverage or asset value per share at the time of purchase, and the seller (or seller's broker);
• registrant identification and an officer signature.

An N-23C-1/A is filed to correct or supplement a previously transmitted notice (for example, when reported transaction details change or were misstated). It carries the same anatomy as the original and is treated as a separate accession.

If a closed-end fund makes no repurchases in a given month, it does not file. The form is therefore episodic across the calendar — present only in months containing reportable repurchase activity — and the overall dataset is low volume.

Regulatory framework

The obligation flows from the Investment Company Act of 1940:

• Section 23(c) restricts a registered closed-end company from purchasing securities of which it is the issuer except (1) on a securities exchange or other open market subject to SEC rules, (2) pursuant to tenders made to all holders of the affected class, or (3) under other circumstances the Commission permits by rule or order.
• Rule 23c-1 (17 CFR 270.23c-1) implements the third prong, prescribing the conditions under which a closed-end fund may repurchase its own securities outside an exchange transaction or formal tender offer, including a reporting obligation to the Commission.
• Form N-23C-1 is the prescribed notice used to satisfy that reporting obligation; its EDGAR description reads "Reports by closed-end investment companies of purchase of their own securities."

The form sits in the Investment Company Act notice family (Forms N-x), distinct from registration forms (N-1A, Form N-2, N-14), periodic reports (Form N-CSR, Form N-PORT, N-CEN), and tender-offer filings (Schedule TO-I).

Timing and cadence

• No fixed periodic cadence. The form is required only for months in which the fund actually repurchased its own securities under Rule 23c-1; funds with no such activity file nothing.
• periodOfReport is the calendar month-end covered by the schedule.
• filedAt is the EDGAR acceptance timestamp, typically days to weeks after periodOfReport. Latency analyses should compare the two fields.
• Some closed-end funds never file an N-23C-1; others (for example, funds with regular preferred-share or term-debt buyback activity) file repeatedly.

Important distinctions

• N-23C-1 vs. N-23C-2. Form N-23C-2 is the advance notice a closed-end fund gives to holders of an affected class of its intent to call or redeem under Rule 23c-2. N-23C-1 reports completed repurchases to the SEC under Rule 23c-1; the two address different procedural pathways within Section 23(c) of the Investment Company Act of 1940.
• N-23C-1 vs. N-23C-3 / interval funds. Closed-end interval funds make periodic repurchase offers under Rule 23c-3 and disclose them through Form N-23C-3 (and prospectus/SAI disclosure), not N-23C-1.
• N-23C-1 vs. issuer tender offers. A closed-end fund running a formal issuer tender offer files under the Williams Act framework on Schedule TO-I, not Form N-23C-1.
• N-23C-1 vs. open-market exchange repurchases. Repurchases executed on a national securities exchange under the Section 23(c)(1) prong are a separate permissible channel; they may not require an N-23C-1 notice even though they share the underlying statutory section.
• Filer vs. seller. The filer is the closed-end fund (the issuer-purchaser). The seller named in the schedule — often a broker or the broker's customer — is a counterparty, not a filer.
• Co-filers / series structures. When multiple entities appear in metadata, the closed-end fund itself is the registrant carrying the 817- SEC file number; the others are typically related parent or series entities, not independent filers.
• Operating-company analogs. A non-investment-company issuer buying back its own shares does not use Form N-23C-1; its repurchase disclosure lives in Exchange Act periodic reports and, for tender offers, in Schedule TO. The N-23C-1 record type itself is a reliable marker that the filer is a registered closed-end investment company acting under the Investment Company Act repurchase regime.

How This Dataset Differs From Similar Datasets or Filings

Form N-23C-1 is a narrow, post-trade notice — a registered closed-end fund's monthly report of repurchases of its own outstanding securities under Rule 23c-1. Because several adjacent regimes touch the same economic activity (a fund or operating issuer acquiring its own securities), confusion is most likely with the other Section 23 rules, with the issuer tender-offer regime, with periodic fund reporting, and with operating-company buyback disclosure. Each covers a slice of the same territory under a different trigger, filer population, or content depth.

Form N-23C-2 — Notice of Intent to Repurchase

Filed by closed-end funds under Rule 23c-2 to give shareholders advance notice (typically at least 30 days) of an intent to repurchase. This is the closest sibling and the most common source of confusion.

• N-23C-1 is retrospective: a monthly report of repurchases already made.
• N-23C-2 is prospective: a shareholder-directed notice before any repurchase occurs.

They are complements across the timeline of the same activity, not substitutes.

Form N-23C-3 — Notice of Repurchase Offer by Interval Funds

Filed by interval funds under Rule 23c-3 to document each recurring repurchase offer.

• N-23C-3 records the operation of a permanent, structural repurchase program built into the fund's design, filed every cycle.
• N-23C-1 records discrete, post-trade repurchases by any closed-end fund, with no requirement of recurrence.

Mixing the two conflates routine interval-fund liquidity mechanics with general closed-end repurchase reporting.

Schedule TO-I — Issuer Tender Offers

Filed under Rule 13e-4 of the Exchange Act when an issuer (including some closed-end funds) conducts a formal tender offer for its own securities.

• TO-I is heavy: offer terms, financing, source of funds, purpose, post-offer plans, offer-to-purchase and letter-of-transmittal exhibits.
• N-23C-1 is light: a short monthly schedule of transactions (date, class, shares, price, asset coverage, counterparty).

When a closed-end fund repurchases via tender mechanics, TO-I is the principal disclosure; N-23C-1 may still pick up the executed transactions in the monthly report, but it is not the offer document.

Form N-CSR — Certified Shareholder Reports

Semi-annual and annual shareholder reports of registered management investment companies.

• N-CSR is periodic and aggregated: repurchase activity appears narratively or inside financial statements, alongside the full portfolio and operating picture.
• N-23C-1 is monthly and transaction-level: a per-purchase schedule with no financial-statement context.

Use N-CSR to confirm aggregate effects after the fact; use N-23C-1 to recover the per-transaction record.

Form N-2 — Closed-End Fund Registration Statement

The registration form establishing the closed-end fund and the terms of its securities, including any call or redemption rights.

• N-2 describes the contractual rights under which a security may be repurchased, called, or redeemed.
• N-23C-1 reports the actual execution of repurchases month by month.

They sit at opposite ends of the lifecycle of the same security.

Form 8-K and Rule 10b-18 buyback disclosure (10-Q / 10-K)

The operating-company analogues of buyback reporting. Form 8-K captures event-driven repurchase announcements; the tabular Rule 10b-18 disclosure in 10-Q and 10-K reports executed open-market repurchases period by period.

• Filer populations are essentially disjoint: operating issuers (Exchange Act) on one side, registered investment companies (Investment Company Act, Section 23) on the other.
• A complete cross-asset view of issuer buybacks requires combining both regimes; neither dataset alone covers both populations.

Form N-PORT

Monthly portfolio holdings report for registered management investment companies.

• N-PORT describes what a fund holds (the asset side).
• N-23C-1 describes what a fund is doing on its own capital structure (the liability/equity side).

The two are often co-located in research workflows for closed-end funds but answer different questions and rarely substitute.

Boundary summary

Form N-23C-1 is the only EDGAR record type whose specific purpose is the monthly post-trade reporting of closed-end fund repurchases of their own securities under Rule 23c-1. It is:

• narrower than N-23C-2 (which is prospective, not retrospective),
• narrower than N-23C-3 (which is interval-fund-specific and recurring),
• narrower than Schedule TO-I (which is a full tender-offer disclosure, not a monthly schedule),
• distinct from N-CSR and N-PORT (which are periodic and either aggregated or asset-side), and
• distinct from 8-K / 10b-18 disclosure (which covers a different filer population under a different statute).

Its uniqueness lies in the combination of three attributes that no other dataset shares: transaction-level granularity, the closed-end fund filer population, and the Rule 23c-1 monthly-reporting trigger covering filings from August 1994 to the present. Related datasets fill in adjacent context (N-2 for the underlying terms, N-23C-2 and N-23C-3 for sibling repurchase regimes, N-CSR for periodic narrative, TO-I where tender mechanics apply), but none substitutes for N-23C-1 when the research question concerns who repurchased what, when, at what price, and from whom under Rule 23c-1.

Who Uses This Dataset

The Form N-23C-1 Files Dataset has a narrow but well-defined professional audience built around closed-end fund leverage, preferred stock, and event-driven trading. Each user community keys on a specific subset of the record — class, price, date, terms, registrant, amendment status — tied to a concrete closed-end fund capital-structure workflow.

Closed-end fund analysts

Analysts covering closed-end funds at asset managers, wealth platforms, and research desks track every announced call of fund-issued leverage instruments such as auction-rate preferred, variable-rate demand preferred, and term preferred. They key on registrant, class, share count, redemption price, and call date to update leverage models, recalculate asset-coverage ratios, and revise expense projections after the instrument leaves the capital structure.

Preferred-stock and fixed-income analysts

Analysts covering preferred stock and fund-issued leverage treat each filing as a call signal on an outstanding series. They focus on the call date, redemption price relative to liquidation preference, and partial-redemption mechanics to manage call risk, refresh yield-to-call and yield-to-worst figures, and anticipate the next tranche in a serial call schedule.

Event-driven and relative-value traders

Capital-structure desks trading closed-end fund preferreds and commons use the filings to price announced calls. They focus on call date, redemption price, full-versus-partial status, and pro-rata mechanics to construct trades around the gap to redemption price and to model the impact of de-leveraging on the discount-to-NAV of the common.

Fund compliance and operations teams

Compliance and operations staff at fund advisers use the dataset both as a drafting reference and as a peer benchmark for Rule 23c-1 notices. They study how peers describe class, basis for redemption, and attached conditions, and feed that into filing templates, internal checklists, and audit trails covering repurchases across a fund complex.

Investment company legal counsel

In-house and outside fund counsel use the dataset to draft and review Rule 23c-1 notices, compare drafting conventions, and study how N-23C-1/A amendments are used to correct prior filings. They focus on terms-and-conditions language, class descriptions, partial-call treatment, and cross-references to charter and Investment Company Act provisions.

Fund administrators, transfer agents, and paying agents

Service providers to closed-end funds use the filings to confirm operational details: affected class, share count, record date, call date, redemption price per share, and payment conditions. The records drive coordination with depositaries, payment scheduling, and post-call share-register reconciliation. Amendments matter because they often carry operational corrections that must flow into shareholder records.

Academic researchers in finance

Researchers studying the closed-end fund discount, leverage cycles, and capital-structure choices at registered investment companies combine the filings with NAV histories, market prices, and fund characteristics. They use registrant CIK, class, redemption schedule, price, and timing to test how announced calls affect discount dynamics and subsequent leverage decisions.

Regulatory examination and enforcement staff

Examination staff use the dataset to test whether registrants met the procedural and substantive conditions of Rule 23c-1. They focus on notice timing relative to call date, completeness of class and terms descriptions, consistency between original notices and amendments, and alignment between announced and executed terms across a complex.

Data vendors and dataset engineering teams

Corporate-action and reference-data teams normalize the filings into redemption calendars, call-risk feeds, and fund-leverage tables. Extraction focuses on registrant CIK, class, redemption price, call date, and amendment status, with output consumed by order-management and portfolio-accounting systems.

LLM and RAG developers

Teams building retrieval systems for fund research and corporate-action monitoring use the JSON metadata, HTML and TXT bodies, and amendment linkages as a source corpus. The records train redemption-event classifiers, price-and-date extraction pipelines, and grounded question-answering over a registrant's repurchase history.

Specific Use Cases

The Form N-23C-1 Files Dataset supports a narrow but concrete set of workflows around closed-end fund repurchases reported under Rule 23c-1. The use cases below tie directly to fields present in each record: registrant CIK, class and par value, transaction date, share count, price per share, asset coverage or asset value at the time of purchase, seller or broker identity, and the periodOfReport month-end.

1. Building a per-fund monthly repurchase time series

Extract every transaction row from the schedule-of-purchases table in the primary document and key it to entities[].cik plus periodOfReport. The result is a long-format table of repurchase dates, classes, share counts, and prices per fund. This feeds closed-end fund leverage models, share-count rollforwards, and historical buyback intensity studies across the August 1994 to present window.

2. Tracking asset-coverage compliance around 1940 Act thresholds

Pull the asset-coverage or asset-value-per-share column from the schedule together with the transaction date and class. Joined to the registrant's preferred-stock and senior-security disclosures from N-2 and N-CSR, this supports monitoring of Section 18 asset-coverage ratios at the moment of each repurchase and flags filings where repurchases cluster near regulatory minima.

3. Reconstructing serial preferred-stock call schedules

Filter records by class identification (auction-rate, variable-rate demand, or term preferred) and order by periodOfReport. The resulting call sequence per registrant CIK drives yield-to-call and yield-to-worst recalculations for fixed-income desks and lets preferred-stock analysts anticipate the next tranche in a multi-step redemption program.

4. Resolving amendment chains to get clean per-month repurchase records

Group N-23C-1 and N-23C-1/A filings by registrant CIK and periodOfReport, then reconcile the schedules so that the latest amendment supersedes prior notices for the same month. This produces a corrected monthly repurchase ledger suitable for use as a reference feed by corporate-action and portfolio-accounting systems.

5. Measuring filing latency between repurchase month and EDGAR submission

Compare periodOfReport to filedAt per accession to compute the lag between the reported calendar month and the notice's arrival on EDGAR. Aggregated by registrant or fund complex, this supports examination workflows checking timeliness of Rule 23c-1 notices and surfaces complexes with chronic late filing.

6. Counterparty and broker concentration analysis

Parse the seller or seller's-broker column from the schedule across the full dataset. Aggregating by counterparty name reveals which dealers most often face closed-end funds in repurchase transactions, supporting best-execution review by fund compliance teams and counterparty-concentration screens for examiners.

7. Training extraction models for fixed-width and HTML repurchase schedules

Use the paired metadata.json (form type, period, registrant) and primary document (SGML-wrapped ASCII pre-2000s, HTML in recent filings) as supervised input for table-extraction and event-classification models. The stable schedule columns — date, class, shares, price, asset coverage, seller — across a thirty-year span provide a controlled corpus for redemption-event classifiers and grounded question-answering over a registrant's repurchase history.

Dataset Access

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

This endpoint returns metadata describing the Form N-23C-1 Files Dataset, including its name, description, last update timestamp, earliest sample date (1994-08-01), total record and size counts, form types covered (N-23C-1 and N-23C-1/A), the container format (ZIP), and the file types contained within each container (TXT, JSON, HTML). It also includes the full dataset download URL and a list of individual container files with per-container metadata such as size, record count, updated timestamp, and a direct download URL. Use this endpoint to monitor which containers were updated in the most recent refresh run and decide which containers to re-download on a day-by-day basis. This endpoint does not require an API key.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-69a3-a744-b0db13f689b0",
        

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

          4
            "name": "Form N-23C-1 Files Dataset",
        

          5
            "updatedAt": "2026-04-15T12:05:28.524Z",
        

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

          7
            "totalRecords": 952,
        

          8
            "totalSize": 3493169,
        

          9
            "formTypes": ["N-23C-1", "N-23C-1/A"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

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

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

          16
                "size": 13818,
        

          17
                "records": 4,
        

          18
                "updatedAt": "2026-04-15T12:05:28.524Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

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

Downloads the complete Form N-23C-1 Files Dataset as a single ZIP archive containing all monthly container files from August 1994 to present. This endpoint requires an API key.

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

Downloads one individual monthly container archive instead of the full dataset. Replace the year and month segments with the container key returned by the dataset index JSON API to retrieve a different month. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form N-23C-1 and its amendment Form N-23C-1/A — the EDGAR notices that registered closed-end management investment companies submit under Rule 23c-1 of the Investment Company Act of 1940 to report purchases of their own outstanding securities during a prior calendar month.

What does one record in this dataset represent?

One record corresponds to a single EDGAR accession number — one Form N-23C-1 or N-23C-1/A submission filed by a closed-end fund for one calendar month of repurchase activity. A single filing may report multiple repurchase transactions in its schedule, but all of them roll up into the same accession-number record.

Who is required to file Form N-23C-1?

Registered closed-end management investment companies that purchase their own outstanding securities under Rule 23c-1, acting as the issuer of those securities. Open-end mutual funds, ETFs, UITs, business development companies, and operating companies do not file this form; their issuer repurchases are reported under different regimes.

When is a filing triggered and how often do records appear?

The filing is transaction-driven but reported on a monthly cadence. A closed-end fund files a Form N-23C-1 only for calendar months in which it actually repurchased its own securities under Rule 23c-1; if no such purchases occur in a month, no filing is made, which is why the dataset is episodic across the calendar.

How does this dataset differ from Form N-23C-2 and Form N-23C-3?

N-23C-1 is retrospective monthly reporting of repurchases already made under Rule 23c-1. N-23C-2 is a prospective shareholder notice of intent to call or redeem under Rule 23c-2. N-23C-3 is interval-fund-specific and documents recurring repurchase offers under Rule 23c-3. The three address different procedural pathways within Section 23(c) of the Investment Company Act of 1940.

What file formats are in each record?

Each accession folder contains a metadata.json header derived from the EDGAR submission header, plus the primary form document delivered as an EDGAR SGML <DOCUMENT> wrapper around either fixed-width ASCII text (in older filings) or HTML (in more recent filings). The dataset's file types are TXT, JSON, and HTML; image files and XBRL data files are not included because Form N-23C-1 is not an XBRL-tagged form.

What time period does the dataset cover?

The dataset covers Form N-23C-1 filings from August 1994 — the earliest EDGAR sample date — to the present, with records packaged as monthly ZIP containers keyed <year>/<year>-<month>.zip.