Form DEFM14A Files Dataset

The Form DEFM14A Files Dataset is a corpus of definitive merger-proxy submissions filed on EDGAR under form code DEFM14A — the Schedule 14A proxy statement that public-company registrants must deliver to security holders when soliciting a vote on a merger, consolidation, sale of substantially all assets, or other business combination. One record represents one EDGAR submission, identified by accession number, and bundles a normalized JSON metadata object together with every textual document EDGAR recorded for the submission (the proxy statement itself plus any annexes or exhibits filed as TXT, HTML, or PDF). Filers are Exchange Act registrants subject to Section 14(a) — typically the target company, the acquirer, or both, plus SPACs in de-SPAC business combinations. The dataset covers filings from January 1, 1994 through the present and is distributed as monthly ZIP containers keyed YYYY/YYYY-MM.zip.

Dataset APIs

Dataset Files

What This Dataset Contains

DEFM14A is the EDGAR form code for a definitive proxy statement filed under Section 14(a) of the Securities Exchange Act of 1934 and Regulation 14A, where the proxy materials relate to a merger, consolidation, acquisition, or similar business combination requiring security-holder approval. The "M" suffix distinguishes the merger-related definitive proxy from the ordinary annual-meeting definitive proxy (DEF 14A). A DEFM14A is filed no later than the date the materials are first sent or given to security holders, and is typically preceded by a preliminary version (PREM14A) and frequently accompanied or followed by transaction filings on Schedule 13E-3 (going-private transactions), Form S-4 (registration of consideration shares), Rule 425 prospectuses, additional soliciting material on DEFA14A, and 8-K disclosures.

The substantive content is governed by Schedule 14A, in particular the Item 14 "Mergers, Consolidations, Acquisitions, and Similar Matters" disclosure framework, which incorporates by reference parts of Form S-4. Because the proxy is the legal solicitation document for the vote, it is comprehensive: it must describe the proposed transaction, its terms and conditions, the background and reasons for the transaction, opinions of financial advisors, risk factors, dissenters' or appraisal rights, voting mechanics, the recommendation of the board, and frequently the full text of the merger agreement and fairness opinion as annexes.

The dataset packages each submission's metadata plus every textual document component as TXT, HTML, JSON, or PDF; image binaries (logos, signature scans, photographs, proxy-card scans) listed under the EDGAR GRAPHIC document type are intentionally excluded. Coverage runs from January 1, 1994 — the start of systematic EDGAR electronic capture for these filings — through the most recent monthly refresh. The container format is ZIP, organized as one ZIP per calendar month under the key pattern YYYY/YYYY-MM.zip.

Content Structure of a Single Record

What one record is

One record is a single definitive merger-proxy submission filed on EDGAR under form code DEFM14A, identified by its EDGAR accession number. On disk the record is one folder named with the 18-digit accession number stripped of dashes (for example 000119312525151902 for accession 0001193125-25-151902). The folder holds a normalized JSON metadata object plus the as-filed text/markup of every textual document EDGAR recorded for the submission — the proxy statement itself and any annexes, exhibits, or supporting attachments that exist as TXT, HTML, or PDF. Image binaries (logos, signature scans, photographs, proxy-card scans) and any other GRAPHIC items in the EDGAR document inventory are deliberately excluded.

A record therefore captures one transaction-specific definitive proxy as filed — the package the registrant first sent to security holders to solicit votes on a proposed merger, consolidation, acquisition, or similar business combination — together with a structured header describing who filed it, when, under which file numbers, and which documents were originally part of the submission.

On-disk structure of one record

Each accession folder contains:

• metadata.json — a single normalized JSON object describing the EDGAR submission. Always present.
• One primary DEFM14A document — an .htm file in modern filings or a .txt file in legacy filings, carrying the full proxy statement inside EDGAR's SGML document envelope.
• Zero or more additional textual documents corresponding to annexes or exhibits enumerated by EDGAR for the submission — typically further .htm files for separately filed exhibits and occasionally .pdf for documents the registrant chose to file as PDF (for example, fairness opinions reproduced from advisor letterhead).

The file-types found in the dataset are TXT, JSON, HTML, and PDF. Image binaries (.jpg, .gif, .png) listed under EDGAR's GRAPHIC document type are intentionally omitted, even when the proxy's HTML body references them via relative <img src="…"> tags. Container packaging is one ZIP per calendar month keyed YYYY/YYYY-MM.zip, with the month folder holding one sub-folder per accession; the record itself is the accession folder, not the monthly container.

File-naming conventions

Accession folder names are 18-digit numeric strings (the dashed accession number with dashes removed). Textual document filenames are set by the filer's filing agent and follow that agent's house style. Common patterns include:

• RR Donnelley: dNNNNNN<form>.htm (e.g., d928340ddefm14a.htm).
• Toppan Merrill: tmNNNNNNN-N_<form>.htm (e.g., tm2517868-1_defm14a.htm).
• Broadridge / NYSE filing tools: nyNNNNNNNNxN_<form>.htm (e.g., ny20050852x1_defm14a.htm).
• EdgarAgents: eaNNNNNNN-NN.htm (e.g., ea0233554-09.htm).

Filenames are not authoritative for content type. The SGML <TYPE> tag inside each document carries the canonical EDGAR document type, while metadata.json provides the normalized record-level type.

Component-by-component breakdown

metadata.json

metadata.json is one JSON object per submission. Top-level fields:

• formType — always "DEFM14A".
• accessionNo — dashed EDGAR accession (e.g., "0001193125-25-151902"); the canonical primary key.
• filedAt — ISO-8601 timestamp with timezone offset reflecting EDGAR acceptance time (e.g., "2025-06-30T06:08:37-04:00").
• description — boilerplate label "Form DEFM14A - Definitive proxy statement relating to merger or acquisition".
• linkToFilingDetails — direct URL of the primary HTM proxy document on sec.gov/Archives/edgar/....
• linkToTxt — URL of the full SGML submission text file on EDGAR.
• linkToHtml — URL of EDGAR's -index.htm landing page for the accession.
• linkToXbrl — empty string (Schedule 14A proxy materials carry no XBRL).
• id — 32-character hex internal record identifier.
• documentFormatFiles — array enumerating every document EDGAR lists for the submission, regardless of whether the dataset packages the binary on disk. Each element carries:
  • sequence — string ordinal; "1" is the primary proxy statement, "2", "3", … are additional documents and graphics; the trailing element uses a single space " " and points to the complete .txt submission.
  • size — byte count as a string.
  • documentUrl — absolute URL to the file on EDGAR.
  • type — EDGAR document type ("DEFM14A", "GRAPHIC", blank for the complete-submission wrapper, occasionally "EX-99.x" for separately filed exhibits).
  • description — human-readable label ("DEFM14A", "GRAPHIC", "PROXY STATEMENT", "Complete submission text file"); sometimes omitted on graphic items.
• dataFiles — array reserved for structured data attachments; empty for DEFM14A because no XBRL or related structured data is filed with proxy statements.
• seriesAndClassesContractsInformation — array reserved for the EDGAR series/class contract block used by registered investment companies; for operating-company merger proxies it is empty.
• entities — array of entity objects, one per filer, co-filer, or subject company on the EDGAR header. Operating-company merger proxies frequently have a single entity (the registrant); transactions in which both parties co-file produce multiple entries. Each entity object carries:
  • companyName — display name with the role label in parentheses (e.g., "Vigil Neuroscience, Inc. (Filer)", "… (Subject Company)").
  • cik — Central Index Key as numeric string.
  • irsNo — Employer Identification Number; "000000000" when not provided.
  • fileNo — SEC file number (e.g., "001-12607").
  • filmNo — EDGAR film number for the submission.
  • act — Securities Exchange Act identifier, typically "34".
  • type — form type associated with this entity for the submission ("DEFM14A").
  • sic — SIC code with industry label appended; HTML-entity-escaped where the label contains ampersands (e.g., "3714 Motor Vehicle Parts & Accessories").
  • stateOfIncorporation — two-letter state or country code ("DE", "OH", "MA", "E9" for Cayman, and similar); occasionally absent.
  • fiscalYearEnd — four-digit MMDD string (e.g., "1231", "0630").
  • tickers — array of ticker symbols associated with the registrant; one to several entries are common.

The entities array is the structural anchor that links each record to the parties of the underlying transaction (acquirer, target, parent, holding vehicle) when the EDGAR header captures more than one filer.

The primary DEFM14A document (SGML envelope)

The primary document on disk is wrapped in EDGAR's SGML envelope, which prefixes the HTML or plain-text body with structured tags identifying the document role within the submission:

          1
          <DOCUMENT>
        

          2
          <TYPE>DEFM14A
        

          3
          <SEQUENCE>1
        

          4
          <FILENAME>d928340ddefm14a.htm
        

          5
          <DESCRIPTION>DEFM14A
        

          6
          <TEXT>
        

          7
          <HTML><HEAD><TITLE>DEFM14A</TITLE></HEAD>
        

          8
           <BODY ...>
        

          9
             ... full proxy statement ...
        

          10
           </BODY></HTML>
        

          11
          </TEXT>
        

          12
          </DOCUMENT>
        

Inside the <TEXT> block the body is a complete HTML rendering of the proxy statement. Section ordering varies modestly by issuer and filing-agent template, but the canonical sequence is:

1. Cover page — issuer name, principal executive office address, date materials are first sent, and the SEC-prescribed cover-page legends required by Schedule 14A (including the "neither the SEC nor any state securities commission" legend and, where consideration is securities, the appropriate offering-related legends).
2. Letter to shareholders — signed by the chair or CEO, summarizing the transaction at a high level and urging a vote.
3. Notice of special meeting — date, time, location, virtual-meeting access details, record date, and the matters to be voted on.
4. Table of contents and a glossary or index of defined terms used throughout.
5. Summary term sheet — high-level digest of the parties, transaction structure (cash, stock, mixed consideration, exchange ratio), key financial terms, headline conditions, and expected closing timing.
6. Questions and answers — plain-language Q&A on transaction mechanics and voting procedures.
7. Risk factors — transaction-specific and combined-company risks, often supplemented by reference to the parties' Exchange Act filings.
8. The merger — the principal substantive section. Sub-sections typically cover the background of the merger (chronology of negotiations), the registrant's reasons for the merger, the recommendation of the board of directors, opinions of financial advisors (with the analyses summarized and the full opinion attached as an annex), interests of directors and executive officers in the merger (including the golden parachute compensation table required by Item 402(t) of Regulation S-K), regulatory approvals, accounting treatment, financing of the transaction, and material U.S. federal income tax consequences.
9. The merger agreement — narrative description of the operative agreement: representations and warranties, interim operating covenants, no-shop and fiduciary-out provisions, conditions to closing, termination rights, and termination fees.
10. Other agreements — voting and support agreements, lock-ups, sponsor arrangements, and related ancillary instruments.
11. Information about the parties — descriptions of acquirer, target, and any newly formed merger-sub or holding vehicles.
12. Appraisal/dissenters' rights — statutory rights and procedures, often state-specific (most commonly DGCL Section 262 for Delaware targets).
13. Proposals and voting procedures — record date, quorum, vote required, treatment of broker non-votes and abstentions, methods of voting, and revocation mechanics; for SPAC business combinations this section also covers redemption procedures.
14. Where you can find more information — references to documents incorporated by reference from the parties' Exchange Act filings.
15. Annexes — most commonly Annex A (the merger agreement), Annex B (the fairness opinion), and additional annexes for voting/support agreements, charter or bylaw amendments, and the text of relevant appraisal-rights statutes.

Document sizes vary substantially with transaction complexity, ranging from low single-digit megabytes for simple bolt-on acquisitions to well over ten megabytes for SPAC business combinations whose proxies double as registration-style disclosure documents.

Additional documents in the submission

When the registrant files annexes or exhibits as separate EDGAR documents rather than embedding them inline, those documents appear as additional .htm, .txt, or .pdf files in the same accession folder, each carrying its own SGML wrapper with its own <TYPE>, <SEQUENCE>, <FILENAME>, and <DESCRIPTION> tags. In current practice many merger proxies present all annexes as inline HTML within the primary document, so the accession folder commonly contains only metadata.json and the single primary proxy document.

Included content

Each record packages the structured submission metadata plus every textual document component of the EDGAR submission as TXT, HTML, or PDF — i.e., the proxy statement itself and any annexes or exhibits filed in those formats. The metadata file additionally enumerates the complete original document inventory, including documents that exist on EDGAR but are not packaged on disk, allowing the original submission to be reconstructed by URL when needed.

Excluded content

The dataset omits image binaries (.jpg, .gif, .png) and any other graphic exhibits listed under the EDGAR GRAPHIC document type. These are commonly corporate logos, signature scans, executive photographs, and proxy-card scans. The HTML body of the proxy frequently references them via relative <img src="…"> URLs; those references will not resolve from the unpacked archive alone, but each excluded graphic remains discoverable through its documentUrl in documentFormatFiles. Documents filed under separate accession numbers — such as a related S-4, Rule 425 communications, Schedule 13E-3, additional soliciting material on DEFA14A, or follow-on 8-Ks — are not part of this record; each is its own EDGAR submission with its own accession.

Changes in required content over time

The Schedule 14A framework that governs DEFM14A content has evolved meaningfully across the dataset's coverage window of January 1994 to the present:

• Through the 1990s and early 2000s, merger proxies followed Item 14 of Schedule 14A largely as originally promulgated, with disclosure heavily cross-referenced to Form S-4 where stock consideration was offered.
• Sarbanes-Oxley (2002) and subsequent SEC rulemaking expanded internal-control and audit-committee disclosures, which sometimes flow into pro-forma combined-company disclosures inside the proxy.
• The Dodd-Frank Wall Street Reform and Consumer Protection Act (2010) added Section 14A of the Exchange Act, which created the requirement for a non-binding shareholder advisory vote on "golden parachute" compensation in connection with merger transactions and the tabular disclosure of named-executive-officer change-in-control compensation under Item 402(t) of Regulation S-K. From 2011 onward, modern DEFM14A filings routinely contain that golden parachute compensation table and the corresponding advisory-vote proposal.
• SEC amendments to proxy rules over the period — including changes to the cover-page legend, the universal proxy rule (effective for contested elections in 2022, occasionally relevant when a contested vote intersects with a merger vote), and disclosure modernization releases — have shifted the precise wording and ordering of cover-page and voting-mechanics sections without altering the broad architecture of the document.
• SPAC business-combination practice from the late 2010s onward produced an increasingly common DEFM14A sub-pattern in which the proxy doubles as the disclosure document for de-SPAC transactions, often including target-company audited financial statements, MD&A, and projections-related disclosures responsive to the SEC's 2024 SPAC final rule, all packaged inside the single primary HTM document.

Changes in data format over time

The presentation format of the underlying filing has shifted substantially across EDGAR eras, and that shift is visible in the record contents:

• Filings from 1994 through the late 1990s were typically submitted as plain-text ASCII inside the SGML envelope, with the entire proxy delivered as one or more .txt documents. Tables in those filings are rendered as fixed-width ASCII art, and graphics were referenced through <TYPE>GRAPHIC stub documents in uuencoded form, which are absent from this dataset.
• HTML filing was permitted by EDGAR Release 7.0 in 1999 and effectively universal by the mid-2000s, replacing the ASCII presentation with .htm documents containing rich typography, embedded tables, signed-letter facsimiles, and inline styling. Modern records overwhelmingly take this form: a single large .htm primary document carrying the entire proxy and its annexes.
• PDF inclusion is permitted as an unofficial copy of certain documents and occasionally appears for fairness opinions reproduced on advisor letterhead or for technical exhibits whose layout the filer wished to preserve.

Interpretation notes

• The accession number is the unambiguous primary key for a record. The dashed form appears in accessionNo; the dashless 18-digit form is used as the on-disk folder name.
• documentFormatFiles describes the original EDGAR submission inventory, not the on-disk contents of the record. Entries with type of GRAPHIC and the trailing Complete submission text file entry are listed for fidelity but are not packaged in the ZIP. To determine which files actually exist on disk, intersect the inventory with the file-types TXT, HTML, JSON, and PDF; image entries are systematically absent.
• The SGML envelope around each document carries the canonical document type (<TYPE>DEFM14A, <TYPE>EX-99.1, etc.) along with the original EDGAR-assigned <SEQUENCE> and <FILENAME>. Extraction routines that strip the envelope to reach the HTML body should preserve those header tags as document-level metadata.
• Many merger proxies incorporate substantial portions of the parties' Exchange Act filings by reference rather than reproducing them. The "Where you can find more information" section identifies these incorporated documents; they are not embedded in the record and must be retrieved from the parties' separate EDGAR filings if required.
• The entities array reflects the EDGAR header at the time of filing. Single-filer transactions show only the registrant; co-filed transactions show multiple entities with role suffixes such as (Filer) and (Subject Company) on companyName. Tickers and SIC codes describe the registrant entities, not the transaction.
• Inline <img> references inside the HTML body resolve against EDGAR-relative paths and will not display from the unpacked archive because graphic binaries are excluded; this affects rendered fidelity but not textual content.
• Amendments to a definitive merger proxy are filed under DEFM14A/A and are distinct EDGAR submissions; this dataset's form-type filter targets DEFM14A, so amendments and supplementary DEFA14A additional-soliciting-material filings live outside the record set.
• For machine extraction, the most reliable narrative target is the body of the primary .htm document inside the SGML envelope; section boundaries are best located via heading text ("Background of the Merger", "Opinion of …", "The Merger Agreement", "Annex A") rather than by structural HTML tags, because filing-agent templates differ in their use of <h1>–<h6>, table-of-contents anchors, and styled <p> headers.

Who Files or Publishes This Dataset, and When

Who files the record

The filer is the Exchange Act registrant whose security holders are being solicited to vote on a merger, consolidation, sale of substantially all assets, or comparable business combination. "DEFM14A" is not a separate form type but a Schedule 14A submission tagged as both definitive ("DEF") and merger-related ("M").

Eligible filers are companies subject to the proxy rules under Section 14(a) of the Securities Exchange Act of 1934, meaning issuers with a class of securities registered under Section 12(b) (exchange-listed) or Section 12(g). Typical filer profiles:

• Target companies in third-party acquisitions. Target-only DEFM14A filings dominate when consideration is all cash, because no acquirer vote or share registration is required.
• Acquirer companies filing standalone DEFM14As when their own shareholders must approve the deal — most commonly to authorize share issuances exceeding the 20% threshold under NYSE Listed Company Manual Section 312.03 or Nasdaq Rule 5635, or because the acquirer is itself a constituent corporation in a statutory merger requiring a parent-level vote (e.g., DGCL Section 251).
• Both target and acquirer filing separate DEFM14As on their respective CIKs for the same all-cash transaction when each side's holders must vote. Researchers should expect two records in those cases.
• Special purpose acquisition companies (SPACs) filing in connection with a de-SPAC business combination, which requires SPAC public-shareholder approval and includes redemption mechanics specific to SPAC structures.
• Closed-end funds, BDCs, and registered investment companies in the rare cases where a merger is structured outside the Form N-14 regime; most fund-on-fund mergers use N-14 instead.

Foreign private issuers are excluded: Rule 3a12-3(b) exempts them from Regulation 14A, and they furnish solicitation materials on Form 6-K instead.

The filer is always the registrant being solicited. Counterparties prominently named inside the document — the acquirer in a target-only filing, financial advisors delivering fairness opinions, controlling shareholders signing voting agreements — are not filers of this record.

When the record is created or required

DEFM14A filing is event-driven and follows a fixed sequence:

1. Definitive transaction agreement is signed (merger, share purchase, asset purchase, or scheme of arrangement) and the board approves it.
2. A shareholder vote is determined to be required under state corporate law (e.g., DGCL Section 251 for Delaware mergers, DGCL Section 271 for asset sales), the registrant's charter or bylaws, or exchange listing rules (NYSE 312.03; Nasdaq 5635).
3. PREM14A is filed first. Because merger and acquisition matters are not within the routine-matter exemption of Rule 14a-6(a), the registrant must file a preliminary merger proxy and wait at least 10 calendar days before mailing definitive materials, unless the staff indicates earlier non-review.
4. Staff comments are resolved through PRER14A amendments, which in practice extends the gap between PREM14A and DEFM14A from several weeks to several months.
5. DEFM14A is filed no later than the date the definitive proxy is first sent to security holders, per Rule 14a-6(b). On EDGAR this is effectively same-day with the start of mailing.

The triggering event for the record itself is the commencement of the definitive proxy solicitation — the moment proxy cards and the definitive proxy statement are first transmitted to shareholders of record. Schedule 14A Item 14 ("Mergers, consolidations, acquisitions and similar matters") sets the substantive disclosure scope: transaction terms, background, reasons, accounting and tax treatment, regulatory approvals, appraisal rights, fairness opinions, and historical and pro forma financials. Rule 14a-9 imposes the antifraud standard on every statement made. Rule 14a-12 governs earlier transaction communications, which surface as DEFA14A or PRER14A submissions in the same docket and are not part of this dataset.

After mailing, material developments (revised consideration, new fairness opinion, litigation-driven supplemental disclosures, changed meeting date) trigger a DEFM14A amendment or supplemental DEFA14A.

Earliest availability

Section 14(a) and merger-specific proxy disclosure have applied continuously since 1934, but systematic electronic capture begins with the phased EDGAR mandate of the early 1990s. This dataset starts January 1, 1994; pre-1994 merger proxies exist only as paper filings in SEC archives.

How This Dataset Differs From Similar Datasets or Filings

DEFM14A sits at the intersection of two universes: the Section 14(a) proxy-solicitation family and the broader set of M&A disclosure documents triggered by shareholder votes, securities issuance, tender offers, or going-private analysis. The comparisons below explain when DEFM14A is the right primary source and when a neighboring dataset fits better.

DEFM14A vs. PREM14A (preliminary merger proxy)

PREM14A is the staff-review draft of the same merger proxy filed under Rule 14a-6 before solicitation begins. DEFM14A is the version actually mailed to shareholders. Use PREM14A to study comment-letter cycles, deal-term evolution, or pre-clearance redlines; use DEFM14A for the legally operative solicitation record and the terms shareholders voted on.

DEFM14A vs. DEF 14A (definitive non-merger proxy)

Both satisfy Schedule 14A, but DEF 14A covers routine annual-meeting matters (director elections, say-on-pay, equity plans, auditor ratification) and omits Item 14 merger disclosure. Use DEF 14A for governance and compensation analysis; use DEFM14A for transaction rationale, valuation, fairness opinions, and merger agreement content.

DEFM14A vs. PRE 14A (preliminary non-merger proxy)

PRE 14A is the staff-review draft of DEF 14A, used when contested or non-routine non-merger items appear. It does not include Item 14 merger disclosure and is not a substitute for PREM14A or DEFM14A when the meeting concerns a business combination.

DEFM14A vs. DEFA14A (additional soliciting materials)

DEFA14A captures supplemental solicitation pieces filed under Rule 14a-6(b) after the definitive proxy: investor decks, press releases, ISS/Glass Lewis rebuttals, supplemental Q&A, litigation-driven supplemental disclosures. It augments but never replaces the DEFM14A. Use DEFA14A for the running solicitation campaign and post-mailing updates; use DEFM14A for the full transaction terms and complete proxy record.

DEFM14A vs. DEFR14A / PRER14A (revised proxies)

DEFR14A and PRER14A are full reissues used when restated financials, materially amended deal terms, or extensive staff revisions force the document to be republished rather than supplemented. They are rare and supersede sections of the original. To reconstruct the final disclosure record for a revised deal, pair the DEFM14A with any subsequent DEFR14A; the DEFM14A dataset alone will not contain revisions filed under a different submission type.

DEFM14A vs. Form S-4 (registration statement for business combinations)

S-4 is the acquirer's Securities Act registration statement for new securities issued as deal consideration. In stock and mixed-consideration deals, the S-4 is typically combined with the target's proxy into a joint proxy statement/prospectus, so background, fairness opinions, and merger agreement content overlap heavily. Three differences matter: S-4 is filed by the acquirer/issuer (DEFM14A by the target); S-4 governs Securities Act registration (DEFM14A governs Exchange Act proxy solicitation); S-4 carries acquirer-side disclosure (issuer business, risk factors, capitalization) that DEFM14A standing alone does not. For all-cash deals, no S-4 exists and DEFM14A is the primary document.

DEFM14A vs. Schedule 13E-3 (going-private transactions)

Schedule 13E-3 is required under Rule 13e-3 for management buyouts, controlling-shareholder squeeze-outs, and similar going-private transactions, adding heightened fairness disclosures to unaffiliated shareholders. When a vote is required, issuers typically file a combined Schedule 13E-3/DEFM14A. Use Schedule 13E-3 records to isolate going-private deals; use DEFM14A for the full universe of merger proxies.

DEFM14A vs. Schedule TO / Schedule 14D-9 (tender offer materials)

Schedule TO is filed by a bidder launching a tender offer; Schedule 14D-9 is the target's recommendation response. Pure tender offers involve no proxy solicitation, so no DEFM14A is filed. Two-step deals (tender offer plus back-end merger) may produce a TO/14D-9 pair followed by a DEFM14A or DEFM14C if the back-end merger requires a vote. Use TO/14D-9 for tender-structured deals; use DEFM14A only when a shareholder vote is part of the structure.

DEFM14A vs. Form 425 (deal communications)

Form 425 captures written communications about a business combination filed continuously between announcement and closing — press releases, analyst call transcripts, employee memos, investor decks. These are short communications, not full disclosure documents. Use 425 for the deal communications timeline and public messaging; use DEFM14A for the structured legal disclosure document.

DEFM14A vs. DEFM14C (information statement for mergers without solicitation)

DEFM14C is filed under Section 14(c) and Schedule 14C when no proxies are solicited — typically because a controlling shareholder has already delivered written consent. Substantive content (deal terms, background, fairness opinion, merger agreement) closely mirrors DEFM14A, but it is an information statement, not a vote solicitation. For comprehensive M&A shareholder-action coverage, pair both; for solicited votes only, use DEFM14A and exclude DEFM14C.

DEFM14A vs. 8-K Items 1.01 and 2.01 (signing and closing)

Item 1.01 reports entry into the merger agreement (typically within four business days, with the agreement attached as Exhibit 2.1); Item 2.01 reports closing. These establish the deal timeline and provide the underlying contract but lack the fairness opinion, negotiation background, valuation analysis, and voting mechanics that DEFM14A contains. Use 8-K to identify deals early and pull the merger agreement exhibit; use DEFM14A for the complete shareholder-facing disclosure record.

Boundary summary

DEFM14A is the definitive, target-filed proxy delivered to shareholders for a vote on a merger or acquisition. It is narrower than DEF 14A (mergers only), later than PREM14A (post-staff, post-mailing), fuller than DEFA14A or Form 425 (complete document, not supplemental), and structurally distinct from S-4, Schedule 13E-3, and Schedule TO (different rule, filer role, or transaction structure). It does not cover tender offers without a back-end vote, written-consent transactions (DEFM14C), or acquirer registration disclosure (S-4). For the operative target-company solicitation document — full transaction narrative, fairness opinion, merger agreement annex, voting mechanics, as mailed to shareholders — DEFM14A is the correct primary source.

Who Uses This Dataset

A single DEFM14A bundles deal economics, fairness opinions, projections, the merger agreement, deal-protection covenants, regulatory analysis, and voting mechanics. The professional users below each work specific sections of the same filing.

M&A investment bankers and financial advisors

Coverage and valuation teams at sell-side advisory shops mine the "Opinion of Financial Advisor" section for methodologies actually used in delivered opinions: selected public companies, precedent transactions, DCF inputs, LBO analysis, and implied per-share reference ranges. The "Background of the Merger" feeds process-defensibility advice to boards. Management projections, premium tables, exchange ratios, advisor fee structures, and prior-relationship disclosures populate pitch books and valuation committee memos.

M&A lawyers and deal counsel

Transactional partners and associates use the merger agreement (typically Annex A) as a precedent library. They extract no-shop and no-talk language, fiduciary outs, matching rights, force-the-vote provisions, "Superior Proposal" and "Company MAE" definitions, reverse termination fee asymmetry, ticking fees, and antitrust efforts standards (reasonable best efforts, hell-or-high-water, divestiture caps). Voting and support agreements are reviewed for lock-up percentages and fall-away triggers. The regulatory approvals section calibrates risk-allocation drafting on new mandates.

Risk arbitrage and merger arbitrage analysts

Merger arb desks at hedge funds and proprietary trading groups read the filing on release to populate the spread model. They extract closing conditions, antitrust standards, financing contingencies, required approvals by jurisdiction, MAE carve-outs, end dates, breakup and reverse termination fee dollar amounts, and voting threshold mechanics (majority outstanding vs. votes cast, two-step structures, controller support agreements). These feed closure-probability and downside-payoff calculations driving position sizing, hedging, and pre-vote exit timing.

Activist investors and proxy solicitors

Bumpitrage funds, vote-no campaigners, and hostile bidders preparing topping offers use the proxy to map the contest. They focus on record date, voting deadlines, revocation procedures, broker non-vote treatment, and approval thresholds. The negotiation background reveals which counterparties signed NDAs and which standstills remain in force, indicating whether a topping bid is mechanically possible. Proxy solicitation firms use share counts, retail/institutional splits, and solicitation timing windows from the same sections.

Plaintiffs' securities and stockholder-rights lawyers

Plaintiffs' firms bringing disclosure-adequacy and breach-of-fiduciary-duty claims test the proxy against case-law checklists: completeness of management projections, line-item fairness opinion inputs, banker conflicts and prior counterparty compensation, insider economics, and Item 402(t) golden parachute tables. Identified gaps support demand letters, supplemental-disclosure settlements, mootness fees, and appraisal or post-closing damages actions. Cross-deal review benchmarks "what is normally disclosed."

Corporate development and corporate strategy teams

In-house M&A groups treat the dataset as a sector precedent database. They extract consideration mix (cash, stock, CVRs, election with proration), premiums to unaffected and 30/60/90-day VWAPs, exchange ratio collars, walkaway rights, synergy disclosures, and termination-fee-to-equity-value ratios. The negotiation background informs their own auction design: process breadth, exclusivity timing, go-shop length, and special committee use.

Academic finance and law researchers

Researchers in empirical corporate finance, law and economics, and governance run event studies and large-sample disclosure work: announcement returns, banker conflict effects on outcomes, projection accuracy versus realized performance, golden parachute and 280G gross-up trends, diffusion of specific deal-protection clauses, and post-Corwin cleansing-vote patterns. The 1994-onward span supports multi-decade panels across merger waves and Delaware case-law shifts.

Proxy advisory firms and governance research providers

Proxy advisors issuing M&A vote recommendations build case analyses directly from the filing: process integrity from the background, fairness opinion quality and banker independence, projection and synergy plausibility, deal-protection terms, and change-in-control compensation. Governance data providers ingest the same sections to populate structured deal-terms, board, and executive compensation fields sold to institutional clients.

Financial data, analytics, and AI vendors

Data engineering teams building M&A databases and AI legal/financial products use the dataset as training and reference material. Workflows include NER over parties, advisors, and counsel; extraction of structured deal-term fields (per-share consideration, breakup fees, end dates, MAE carve-outs, regulatory standards) from unstructured prose; clause classification across merger agreements; and fine-tuning language models for retrieval, summarization, and drafting. Full submission contents (including annexes and exhibits) enable clause-level work on the operative document rather than narrative summaries.

Regulators and enforcement staff

Disclosure-review and enforcement staff use historical filings to calibrate review priorities, track the quality of fairness opinion and projection disclosures, and study the evolution of golden parachute and conflicts disclosure under Item 402(t), Item 1015 of Regulation M-A, and Schedule 14A. Patterns are linked to subsequent restatements, deal failures, and enforcement actions. Antitrust staff read regulatory approvals and efforts standards as evidence on clearance-risk structuring; rulemaking teams use the corpus for impact analysis and sweep selection.

Investigative journalists and forensic accountants

Business-investigative reporters and forensic accountants working on related-party deals, going-private transactions, controller squeeze-outs, and SPAC business combinations reconstruct who knew what when. The negotiation background exposes special-committee independence and counterparty contact dates; conflicts disclosures, management equity rollovers, post-close employment arrangements, and golden parachute tables expose insider economics. Cross-checked against prior filings and contemporaneous reporting, these sections support stories on conflicted controllers, aggressive projections, and undisclosed side deals, plus forensic work tied to litigation or regulatory referrals.

Specific Use Cases

The use cases below tie specific DEFM14A sections, annexes, and metadata fields to concrete outputs.

Building a deal-terms database from merger agreement annexes

Parse Annex A of each filing to extract structured fields: per-share consideration, exchange ratios and collars, end dates, breakup and reverse termination fees, no-shop and go-shop windows, fiduciary-out and matching-rights mechanics, MAE carve-outs, and antitrust efforts standards (reasonable best efforts, hell-or-high-water, divestiture caps). The output is a queryable deal-terms table that powers precedent searches, term-sheet calibration, and cross-deal benchmarking. The entities array supplies acquirer/target identity and SIC codes for sector slicing.

Populating merger-arbitrage spread models on filing release

On filedAt, ingest the primary HTM document and pull closing conditions, required regulatory approvals by jurisdiction, financing contingencies, voting thresholds, treatment of broker non-votes, controller support agreements, and dollar-denominated termination fees from "The Merger Agreement", "Regulatory Approvals", and "Proposals and Voting Procedures" sections. These feed closure-probability and downside-payoff inputs that drive position sizing, hedging, and pre-vote exit timing.

Mining fairness opinions for valuation methodology benchmarks

Extract the "Opinion of Financial Advisor" section and the full opinion in Annex B for selected-public-companies sets, precedent-transactions sets, DCF discount-rate and terminal-value assumptions, LBO returns thresholds, and implied per-share reference ranges. Aggregated across the 1994-onward corpus, this supports advisor-by-advisor methodology profiling, valuation committee precedent decks, and academic event studies linking opinion inputs to realized returns.

Disclosure-adequacy review for stockholder litigation

Run the proxy against checklists derived from Delaware case law: completeness of management projections, line-item fairness opinion inputs, banker prior-relationship compensation, insider equity rollovers, and the Item 402(t) golden parachute table. Gaps identified across the "Background of the Merger", "Opinion of Financial Advisor", and "Interests of Directors and Executive Officers" sections support demand letters, supplemental-disclosure settlements, and post-closing damages or appraisal actions.

Process-history reconstruction for investigative and forensic work

Read the "Background of the Merger" chronology together with conflicts disclosures, special-committee composition, NDA and standstill references, and management post-close employment terms to reconstruct who contacted whom and when, which standstills remain in force, and how insider economics evolved. The output supports investigative reporting on conflicted controllers, going-private transactions, and SPAC sponsor arrangements, and forensic-accounting workpapers tied to litigation referrals.

Training and evaluation corpus for legal and financial NLP

Use the full submission contents — primary HTM, annexes, and PDF fairness opinions — as a clause-level training and retrieval corpus. Workflows include named-entity recognition over parties, advisors, and counsel; clause classification across merger agreements; structured extraction of deal-term fields from unstructured prose; and retrieval-augmented generation grounded in the operative document rather than narrative summaries. The 30-year span supports temporal generalization tests across pre- and post-Dodd-Frank disclosure regimes.

Longitudinal study of deal-protection and disclosure evolution

Build multi-decade panels on the diffusion of specific clauses (force-the-vote, two-tier termination fees, ticking fees, hell-or-high-water), the introduction of Item 402(t) golden parachute tables after 2011, and SPAC-era projections disclosure post-2024 SPAC final rule. Time-stamped filedAt and consistent section anchors make the corpus suitable for empirical corporate finance and governance research across merger waves and Delaware case-law shifts.

Dataset Access

The Form DEFM14A Files Dataset is distributed through the SEC API datasets endpoint. There are three access patterns: fetching the dataset index JSON, downloading the full archive, and downloading individual monthly containers. All download requests must be authenticated with your sec-api.io API key, passed either as a token query parameter or in an Authorization header.

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

This endpoint returns the dataset metadata and the list of all monthly ZIP containers. It does not require an API key, which makes it suitable for polling on a schedule to detect newly refreshed containers and decide which months to re-download. The response includes the datasetId, name, updatedAt, earliestSampleDate, totalRecords, totalSize, formTypes, containerFormat, fileTypes, the full-archive datasetDownloadUrl, and a containers array where each entry carries a per-container key, size, records, updatedAt, and downloadUrl.

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-6942-a17a-eb4bf7410f67",
        

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

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

          5
            "updatedAt": "2026-05-06T02:49:34.291Z",
        

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

          7
            "totalRecords": 7146,
        

          8
            "totalSize": 2095756462,
        

          9
            "formTypes": ["DEFM14A"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

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

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

          16
                "size": 13818783,
        

          17
                "records": 12,
        

          18
                "updatedAt": "2026-05-06T02:49:34.291Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

Fetch it with:

curl -s https://api.sec-api.io/datasets/form-defm14a-files.json

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

Use this URL to pull the full dataset as a single ZIP archive in one request. This is the simplest option for a one-time bulk load and covers all filings from January 1994 to the most recent refresh. Requires a valid API key.

curl -L -o form-defm14a-files.zip "https://api.sec-api.io/datasets/form-defm14a-files.zip?token=YOUR_API_KEY"

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

Each container is a monthly ZIP file referenced under containers[].downloadUrl in the index JSON. Iterate over that list to download only the months you need, which is the recommended pattern for incremental processing or daily refresh pipelines that compare each container's updatedAt against your last-seen timestamp. Requires a valid API key.

curl -L -o 2026-04.zip "https://api.sec-api.io/datasets/form-defm14a-files/2026/2026-04.zip?token=YOUR_API_KEY"

Container Layout After Extraction

Each container is a ZIP archive. After extraction, filings are organized by accession number, and each accession folder contains a metadata.json file describing the filing alongside the original SGML-wrapped EDGAR documents. File types present include TXT, JSON, HTML, and PDF; image files are excluded from the dataset.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers EDGAR form code DEFM14A — the definitive proxy statement filed under Section 14(a) of the Securities Exchange Act of 1934 and Schedule 14A when the proxy materials relate to a merger, consolidation, acquisition, or similar business combination requiring security-holder approval. The "M" suffix distinguishes it from the ordinary annual-meeting definitive proxy (DEF 14A).

What does one record in this dataset represent?

One record is a single DEFM14A submission on EDGAR, identified by accession number, packaged as one folder named with the 18-digit dashless accession number. The folder contains a metadata.json describing the submission plus every textual document EDGAR recorded for it — the primary proxy statement and any annexes or exhibits filed as TXT, HTML, or PDF.

Who is required to file Form DEFM14A?

Exchange Act registrants subject to the Section 14(a) proxy rules — typically target companies in third-party acquisitions, acquirers seeking shareholder approval for share issuances or statutory merger votes, both sides of all-cash deals where each set of holders must vote, and SPACs in de-SPAC business combinations. Foreign private issuers are exempt under Rule 3a12-3(b) and instead furnish solicitation materials on Form 6-K.

What time period does the dataset cover?

The dataset starts on January 1, 1994 — the start of systematic EDGAR electronic capture for these filings — and runs through the most recent monthly refresh. Pre-1994 merger proxies exist only as paper filings in SEC archives and are not part of this dataset.

What file format is the dataset distributed in?

The dataset is distributed as ZIP containers, one per calendar month under the key pattern YYYY/YYYY-MM.zip. Inside each container, filings are organized by accession folder. File types present include TXT, JSON, HTML, and PDF; image binaries (.jpg, .gif, .png) listed under EDGAR's GRAPHIC document type are intentionally excluded.

How does this dataset differ from the DEF 14A dataset?

DEF 14A covers routine annual-meeting proxies — director elections, say-on-pay, equity plans, auditor ratification — and omits Item 14 merger disclosure. DEFM14A is reserved for merger or acquisition matters and contains the transaction terms, background of negotiations, fairness opinions, the merger agreement (typically as Annex A), and the corresponding voting mechanics. Use DEF 14A for governance and compensation analysis; use DEFM14A for transaction-specific disclosure.

Are amendments and additional soliciting materials included?

No. Amendments to a definitive merger proxy are filed under DEFM14A/A, and post-mailing supplemental solicitations (investor decks, press releases, supplemental disclosures) are filed as DEFA14A. Both are distinct EDGAR submissions with their own accession numbers and live outside this dataset's form-type filter, which targets DEFM14A only. Related filings such as Form S-4, Schedule 13E-3, Rule 425 communications, and follow-on 8-Ks are likewise separate EDGAR submissions and are not packaged into DEFM14A records.