Form U-12-IA Files Dataset

The Form U-12-IA Files Dataset is a closed historical archive of SEC advocacy-disclosure filings made under Section 12(i) of the Public Utility Holding Company Act of 1935 (PUHCA 1935). One record is one EDGAR accession on Form U-12-IA (initial statement) or Form U-12-IA/A (amendment) — a short, self-contained statement filed in the filer's own name by a natural person or firm retained by a registered holding-company system to conduct advocacy before legislative bodies, regulatory commissions, or executive officials. The dataset covers EDGAR-era filings from January 1999 through February 8, 2006, the day PUHCA 1935 was repealed by the Energy Policy Act of 2005, and no Form U-12-IA filings exist after that date. Records are distributed as a master ZIP partitioned by filing month, with each accession packaged as its own folder containing a normalized metadata.json and the primary form document with its SGML <DOCUMENT> wrapper intact.

Update Frequency
Daily
Updated at
2026-04-16
Earliest Sample Date
1999-01-01
Total Size
80.4 KB
Total Records
30
Container Format
ZIP
Content Types
TXT, JSON, HTML
Form Types
U-12-IA, U-12-IA/A

Dataset APIs

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:

Dataset Files

16 files · 80.4 KB
Download All
2005-09.zip7.1 KB2 records
2005-07.zip8.7 KB3 records
2004-10.zip2.9 KB1 records
2004-09.zip2.2 KB1 records
2004-06.zip5.9 KB2 records
2004-03.zip2.8 KB1 records
2004-02.zip2.3 KB1 records
2003-11.zip5.2 KB2 records
2002-05.zip5.5 KB2 records
2002-01.zip2.6 KB1 records
2001-03.zip2.7 KB1 records
2001-01.zip4.8 KB2 records
2000-10.zip14.2 KB6 records
2000-05.zip2.2 KB1 records
1999-03.zip4.9 KB1 records
1999-01.zip6.5 KB3 records

What This Dataset Contains

The dataset assembles every Form U-12-IA and Form U-12-IA/A accession accepted on EDGAR between January 1999 and February 8, 2006. Form U-12-IA was a brief, single-purpose disclosure prescribed by the SEC under PUHCA 1935. Section 12(i) required any person — typically outside counsel, a lobbyist, or an in-house government-relations employee — engaged by a registered holding company or one of its subsidiaries to publicly disclose advocacy activity conducted on the system's behalf before legislative bodies, regulatory agencies, and executive officials. The form is therefore a transparency filing, not a financial filing: it identifies the advocate, the people working under that advocate, the registered holding-company system on whose behalf the work was done, the employing subsidiary, the forum addressed, the compensation received and to be received, and the out-of-pocket expenses incurred.

The form's body is a fixed six-item structure driven directly by the regulatory text. The Energy Policy Act of 2005 repealed PUHCA 1935 effective February 8, 2006, and the dataset has a hard cutoff there. The "/A" amendment variant is structurally identical to an initial filing; it carries the same six items and is used to correct, supplement, or update a previously filed statement. The file types present in the dataset are TXT, JSON, and HTML, with plain-text TXT documents dominant across the entire 1999 – 2006 window and a small minority of HTML documents in the later years.

Content Structure of a Single Record

What one record represents

One record is one EDGAR accession on Form U-12-IA (initial statement) or Form U-12-IA/A (amendment) — a single disclosure filed under Section 12(i) of PUHCA 1935 by a person retained or employed to conduct advocacy before legislative bodies, regulatory commissions, or executive officials on behalf of a registered holding-company system. The record unit is the accession: every distinct EDGAR accession on either form type appears exactly once, packaged as its own folder that bundles the primary form document with a normalized JSON metadata record. Each record is a short, self-contained statement tying one filer (the advocate) to one registered system, one employing operating company, one venue of advocacy, and one calendar period of compensation and expense.

Container layout and record packaging

The dataset is distributed as a master ZIP. Inside, records are partitioned by filing month: a top-level YYYY/ directory exists for each calendar year, and within each year directory there is one YYYY-MM.zip per month containing the accessions whose filedAt falls in that month. Decompressing a monthly ZIP yields a YYYY-MM/ directory under which every accession appears as its own subfolder named with the 18-digit numeric form of the accession number (dashes stripped) — so accession 0001216383-04-000002 becomes folder 000121638304000002/. Because filing volume on this form is very low, many monthly ZIPs hold only one or two accession folders, and many calendar months have no archive at all.

Each accession folder contains two kinds of artifact:

  • metadata.json — the normalized filing record, always present.
  • The primary form document extracted from the EDGAR submission. Filenames are filer-chosen and vary: common names include u12-1a.txt, u-12ia.txt, u12ia.txt, form.txt, and, in a small number of later filings, .htm/.html equivalents. When a submission carried additional non-image documents (cover letters, corrected pages on amendments), they appear alongside the primary form and are enumerated in the metadata. Image binaries (GIF, JPG) that may have been part of the original submission are excluded by the dataset producer.

Shape of metadata.json

metadata.json is a flat JSON object carrying the standard SEC filing-record fields. The fields that appear consistently for U-12-IA records:

  • formType"U-12-IA" for an initial statement or "U-12-IA/A" for an amendment.
  • accessionNo — the canonical hyphenated EDGAR accession identifier.
  • filedAt — ISO-8601 filing timestamp with a US Eastern timezone offset, reflecting EDGAR's acceptance clock.
  • description — the EDGAR human-readable form description, e.g. "Form U-12-IA - Statement by holding company employee [Section 12(i)]".
  • linkToFilingDetails — absolute URL to the primary submission document under sec.gov/Archives/edgar/data/....
  • linkToTxt — absolute URL to the full SGML submission text (the complete <SEC-DOCUMENT> wrapper with all <DOCUMENT> blocks concatenated).
  • linkToHtml — absolute URL to the EDGAR filing-index HTML page (-index.htm).
  • linkToXbrl — empty; Form U-12-IA was never tagged in XBRL.
  • documentFormatFiles — array of objects, one per document in the submission. Each entry carries sequence ("1" for the primary form), size (byte size as a string), documentUrl, type (form-type string for the primary doc; blank for the complete-submission wrapper), and an optional description such as "Complete submission text file".
  • entities — array of party objects describing each participant captured in the EDGAR submission header. Each entity provides cik (10-digit zero-padded), companyName with a role suffix in parentheses such as "(Filed by)" or "(Subject)", and irsNo (EIN). Subject entities additionally carry act ("35", the 1935 Act), fileNo (the SEC file number under that Act, e.g. "012-00168"), type (form type), and filmNo (the EDGAR film number assigned at acceptance).
  • id — opaque 32-character hex identifier assigned by the dataset producer.
  • dataFiles — array of structured-data exhibits; empty for every U-12-IA filing.

The entities array is the primary structured surface for the filer-versus-system distinction: the Filed-by entity is the advocate (often an outside law or lobbying firm), and the Subject entity is the PUHCA-registered parent system. The specific operating subsidiary that engaged the filer is not separately structured in metadata; it appears only inside Item 4 of the form body.

SGML document envelope

The primary document inside each accession folder is the inner <TEXT> body of an EDGAR SGML <DOCUMENT> block, with the wrapper tags retained. A typical primary file therefore opens with the standard EDGAR document-level header:

1 <DOCUMENT>
2 <TYPE>U-12-IA
3 <SEQUENCE>1
4 <FILENAME>u12-1a.txt
5 <TEXT>
6 UNITED STATES OF AMERICA
7 SECURITIES AND EXCHANGE COMMISSION
8 Washington, D.C. 20549
9
10 FORM U-12 (I)-A
11 ...
12 </TEXT>
13 </DOCUMENT>

<TYPE> carries the form type (U-12-IA or U-12-IA/A); <SEQUENCE>1 marks the primary document within the submission; <FILENAME> carries the filer-chosen on-disk name; and <TEXT> opens the narrative body of the form. The outer submission envelope — <SEC-DOCUMENT>, the parsed <SEC-HEADER> block, the <ACCEPTANCE-DATETIME> line, and the concatenation of all <DOCUMENT> blocks — is not extracted into the accession folder but remains addressable through linkToTxt. The dataset thus separates the form-level document (in the folder) from the full submission envelope (reached by URL).

The six-item body of Form U-12-IA

Beneath the SGML wrapper and the printed "United States of America / Securities and Exchange Commission / Washington, D.C. 20549" heading, every record presents the same six numbered items, in the same fixed order, with the same internal subdivisions. The body is overwhelmingly narrative prose with small embedded fixed-width tables for compensation and expense reporting.

Item 1 — Name and business address of the person filing the statement. A single name-and-address block for the natural person submitting the statement. In practice this is almost always an attorney or government-relations professional at an outside law or lobbying firm retained by the registered system, frequently with a Washington, D.C. business address reflecting the federal regulatory focus of the activity.

Item 2 — Persons through whom the activities were conducted. An itemized list of additional individuals — typically associates, partners, or specialists at the same firm — who worked under the filer's direction on the advocacy disclosed in Item 4. Each entry repeats the firm's business address. When no such persons exist, the item is answered None.

Item 3 — Registered holding-company system involved. Names the PUHCA-registered parent on whose behalf the activities were conducted. This is the system-level identification; the specific operating subsidiary that engaged the filer appears in Item 4. Registered systems appearing across the dataset include parents such as American Electric Power, Southern Company, Entergy, and similarly registered systems active before 2006.

Item 4 — Employing company, bodies before whom matters were advocated, and description of activities. The substantive disclosure of the form. Item 4 ties together (a) the operating subsidiary or affiliate that employed or retained the filer, (b) the legislative, regulatory, or executive forum addressed — overwhelmingly the Federal Energy Regulatory Commission, with occasional state public utility commissions, Congressional committees, or specific named dockets — and (c) a concise description of the work, such as legal advice in an identified FERC proceeding, rate-case representation, or lobbying on pending legislation. Where non-routine expenses were anticipated, Item 4 also flags that expectation.

Item 5 — Compensation received and to be received; division of compensation. Item 5(a) is rendered as a small fixed-width text table whose columns identify the recipient, the amount already received (typically a dollar figure accrued through a stated date), the amount to be received (often "not fixed" or estimated), and the payer (the employing subsidiary from Item 4). Item 5(b) is a short narrative line naming any person with whom the filer has divided or will divide compensation; in practice this is almost always None.

Item 6 — Routine and itemized expenses. Subdivided into Item 6(a) total routine expenses — a single dollar figure capturing photocopying, telephone, filing fees, ordinary travel, and similar items — and Item 6(b) itemized list of all other expenses, a line-by-line accounting of any non-routine expenditures (frequently None.). The amounts disclosed here are small (typically in the hundreds of dollars) and cover only out-of-pocket costs, not compensation, which is captured in Item 5.

The document closes with a Date: line and a /s/ <Name> signature line re-identifying the filer named in Item 1.

What the dataset record includes

For every U-12-IA and U-12-IA/A accession accepted on EDGAR between January 1999 and February 2006, the dataset includes the accession folder containing metadata.json and the primary form document with its SGML <DOCUMENT> wrapper intact. When the submission carried more than one document — for example, a cover letter or a corrected page attached to an amendment — those additional non-image documents are included alongside the primary form and enumerated in documentFormatFiles.

What is excluded or structurally separate

Image attachments (GIF, JPG, and similar binaries) that may have been part of the original EDGAR submission are excluded by the dataset producer. The outer SGML submission envelope — the <SEC-DOCUMENT> wrapper, the parsed <SEC-HEADER> block, and the concatenation of all <DOCUMENT> blocks — is not extracted into the per-accession folder; it remains available at the URL recorded in linkToTxt. The EDGAR filing-index HTML page is likewise not extracted; it is referenced by linkToHtml. No XBRL or structured-exhibit artifacts are present because Form U-12-IA never carried such attachments.

Changes in required content and structure over time

The six-item body is fixed by Section 12(i) of PUHCA 1935 and its implementing rule, and the SEC did not materially revise the form during the EDGAR-electronic window covered here. Every record from January 1999 through the form's February 8, 2006 discontinuation follows the same six-item layout with the same item headings and the same internal subdivision of Items 5 and 6. The only meaningful content distinction across the dataset is between an initial filing (U-12-IA) and an amendment (U-12-IA/A): an amendment carries the same six-item structure and typically restates the prior statement's text with amended figures or language substituted. Amendments do not redline the original; they restate the items as amended and are tied to the original only implicitly, by filer identity, system identity, and the calendar period covered.

Changes in data format over time

Across the seven-year span, the primary documents are overwhelmingly plain ASCII text wrapped in the standard EDGAR SGML <DOCUMENT> envelope, with fixed-width formatting used for the Item 5 compensation table and the Item 6(b) itemized-expense block. Beginning in the early 2000s a small number of filers migrated to HTML for the primary document, mirroring the broader EDGAR shift away from plain text for narrative forms; these HTML documents carry the same six-item structure and remain wrapped in the SGML <DOCUMENT> envelope with <TYPE>U-12-IA and an .htm/.html filename. The dataset preserves whichever format the filer submitted, without reflowing or converting.

Interpretation notes

  • Filer versus system versus employing company. Three distinct parties must be distinguished. The Filed-by entity in entities and Item 1 identify the natural person (and the firm) making the disclosure. The Subject entity and Item 3 identify the PUHCA-registered parent system. The operating subsidiary that actually retained the filer is named only inside Item 4's narrative paragraph and is not separately structured in metadata; extracting it requires parsing the Item 4 prose.
  • Fixed-format tables. Item 5's compensation table and Item 6's expense disclosures are rendered as plain-text fixed-width layouts in TXT filings. Column alignment depends on monospaced rendering; whitespace-token splitting will work but is sensitive to filer-specific spacing, and small numeric columns ("amount received", "amount to be received") frequently contain words such as None, -0-, or not fixed rather than figures.
  • None. as a substantive answer. Items 2, 5(b), and 6(b) are very frequently answered None. This is a positive disclosure (no co-workers, no compensation-sharing, no non-routine expenses) and should not be treated as missing data.
  • Amendment linkage. U-12-IA/A records carry no machine-readable pointer to the prior statement they amend; the relationship must be reconstructed from filer identity, registered-system identity, and the calendar period referenced in Items 5 and 6.
  • Venue concentration. The "persons or bodies before whom matters were advocated" in Item 4 is overwhelmingly the Federal Energy Regulatory Commission, reflecting the energy-sector composition of PUHCA-registered systems. State public utility commissions and Congressional committees appear less frequently. This is a property of the underlying filer population, not of the dataset selection.
  • SGML wrapper retention. Because the primary document retains its <DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, and <TEXT> tags, naive full-text search will hit both wrapper tokens and the form body; consumers typically strip the wrapper to the <TEXT>...</TEXT> interior before tokenizing or indexing.

Who Files or Publishes This Dataset, and When

Who files the record

The filer of a Form U-12-IA is the person — natural or corporate — employed or retained by a registered public utility holding company or any of its subsidiary companies to engage in advocacy before legislative, regulatory, or executive officials on matters affecting the registered system. The statement is filed in that person's own name. The filer is not the holding company. The registered system is identified inside the filing as the party that employed or retained the filer; it is not the registrant on the form.

Filing population

"Person" is read broadly and includes:

  • in-house lobbyists, government affairs officers, and attorneys employed by a registered holding company or subsidiary;
  • outside law firms, lobbying firms, consultants, and public affairs firms retained by the system;
  • trade associations and individual representatives whose covered work is funded by registered systems.

Throughout the EDGAR era of the form (1999 through early 2006), the universe of registered holding companies was a small, defined set of multi-state electric and gas systems and their utility, service company, and non-utility subsidiaries. Persons performing comparable work for utilities exempt under former Section 3 of PUHCA 1935, or for non-PUHCA clients, did not file Form U-12-IA for that work.

Triggering event

The filing obligation is activity-driven. It is triggered when, during the filer's fiscal year, the filer — while employed or retained by a registered holding company system — engages in any of the following on matters affecting that system:

  • appearances, testimony, or written submissions before Congress or a state legislature (or any committee thereof);
  • appearances, testimony, or submissions before the SEC, FERC, or a state public utility or public service commission;
  • communications with federal or state executive branch officials or their staffs on pending legislative, rulemaking, licensing, rate, or policy matters.

If no covered activity occurred in a given fiscal year, no Form U-12-IA was required from that person for that year.

Timing and frequency

Form U-12-IA is an annual statement keyed to the filer's fiscal year. Each statement covers a single fiscal year and is due within 60 days after the close of that fiscal year. A separate annual statement is filed for each fiscal year in which covered activity occurred. Each filing identifies the filer, the registered system that employed or retained the filer, the advocacy undertaken, the bodies or officials addressed, compensation received, and an itemization of related expenses.

Statutory and regulatory basis

Form U-12-IA was prescribed under Section 12(i) of the Public Utility Holding Company Act of 1935 (15 U.S.C. Section 79l(i)) and the SEC's implementing Rule 62 (17 CFR Section 250.62) under Part 250 of the PUHCA rules. Section 12(i) directed the SEC to require statements from persons retained by registered systems concerning their advocacy activities, so that influence on legislatures, agencies, and officials in connection with those systems could be monitored. The form was a stand-alone PUHCA filing. It did not arise under the Securities Act of 1933, the Exchange Act of 1934, the Investment Company Act of 1940, or the Advisers Act of 1940.

Amendments (Form U-12-IA/A)

A Form U-12-IA/A is filed by the same person who filed the underlying Form U-12-IA, to correct, supplement, or update a prior annual statement (for example, to revise compensation figures, add omitted activities, or attach missing exhibits). An amendment relates back to the originally covered fiscal year and does not open a new reporting period.

Wind-down on PUHCA repeal

The Energy Policy Act of 2005 repealed PUHCA 1935 in its entirety, effective February 8, 2006. Holding-company oversight passed to the Federal Energy Regulatory Commission under the Public Utility Holding Company Act of 2005 (PUHCA 2005), which did not carry forward Section 12(i) or any successor to Form U-12-IA. The SEC's authority to require these statements terminated on the repeal date, and no Form U-12-IA or U-12-IA/A was required for fiscal periods post-dating the repeal. The EDGAR record set closes accordingly in early 2006.

Important distinctions

  • Form U-12-IA is not a substitute for, nor satisfied by, federal lobbying disclosures filed under the Lobbying Disclosure Act of 1995 with the Clerk of the House and the Secretary of the Senate. The two regimes have overlapping but non-identical scope, and a single lobbyist could owe filings under both.
  • Form U-12-IA is distinct from the U-series forms filed by the holding companies and subsidiaries themselves — for example, Form U5S annual reports, Form U-1 transaction applications/declarations, and the various U-series exemption and service-company forms. Those are filed by the entity; U-12-IA is filed by the advocacy-performing person.
  • Persons working for utilities exempt from PUHCA registration, or for non-registered clients, do not file Form U-12-IA even when their work involves legislative or regulatory advocacy. The trigger is tied specifically to registered systems.

How This Dataset Differs From Similar Datasets or Filings

Form U-12-IA sits inside the now-defunct family of EDGAR filings created under PUHCA 1935. The useful comparisons fall into three groups: other U-series PUHCA forms, lobbying-disclosure regimes administered outside the SEC, and the post-PUHCA oversight environment. The single dividing line that distinguishes U-12-IA from every nearby filing is the identity of the filer: U-12-IA is filed by the retained advocate (a natural or corporate person engaged by the system), not by the holding company itself.

PUHCA U-series (same statute, same EDGAR channel, same February 8, 2006 sunset)

  • Form U5S (Annual Report for Registered Holding Companies). Filed by the holding company; reports system-wide finances, intercompany transactions, subsidiary investments, and service-company allocations. Broad, periodic, corporate-financial. U-12-IA is narrow, engagement-triggered, and filed by the retained person.
  • Form U-1 (Application or Declaration). Filed by the holding company or subsidiary to obtain SEC approval for securities issuances, acquisitions, or intra-system financings. Transactional, prospective, approval-seeking. U-12-IA is informational, retrospective, and triggered by completed advocacy services.
  • Form U5B (Registration Statement). One-time filing by which a holding company became "registered" and thereby triggered the U-12-IA obligation for its retained advocates. Foundational and corporate; U-12-IA is recurring per engagement and filed by an individual or firm.
  • Form U-13-1 (Application Regarding Mutual or Subsidiary Service Companies). Concerns intra-system service-company formation and operations approved by the SEC. Subject is internal cost allocation, not external advocacy.
  • Form U-7D (Statement Regarding Mutual Service Agreements). Short statement covering mutual service agreements among system companies. Again intra-system, not advocacy.
  • Form U-9C-3 (Quarterly Report of Service Companies). Periodic, tabular cost-and-allocation report by service companies. U-12-IA is narrative and engagement-driven, identifying the body lobbied and the fees paid.

Across the U-series the pattern is uniform: every other U-form is filed by the holding company or a system entity about its own corporate, transactional, or financial conduct. U-12-IA is the only U-form filed by the retained advocate.

Federal lobbying disclosure (different regulator, different statute)

  • LD-1 and LD-2 under the Lobbying Disclosure Act of 1995. Filed with the Clerk of the U.S. House and the Secretary of the U.S. Senate, not the SEC. LD-1 is the registration; LD-2 is the quarterly activity report. LD filings cover federal lobbying of Congress and covered executive-branch officials across all industries and remain active today. U-12-IA had a narrower filer population (only persons retained by registered PUHCA systems) but a broader venue: it captured advocacy before state legislatures, state public utility commissions, and government officials at any level whose action could affect the system.
  • IRS Form 990 Schedule C (Political Campaign and Lobbying Activities). Annual schedule filed with the IRS by tax-exempt organizations as part of Form 990. Addresses lobbying and political activity for purposes of 501(c) tax-status compliance, with definitions, thresholds, and accounting conventions distinct from PUHCA. The filer population (tax-exempt organizations) does not overlap with U-12-IA's filer population (advocates retained by PUHCA-registered systems).

Political-activity content inside other SEC filings

  • Form 10-K political-activity narrative. Some issuers discuss political contributions, lobbying expenditures, or related risk factors inside their annual report (risk factors, MD&A, or governance sections). This is voluntary or principles-based corporate disclosure embedded in a much larger periodic filing; the filer is the issuer. U-12-IA is a standalone single-purpose statement by the retained advocate, itemizing the engagement, the bodies before whom matters were presented, and the compensation and expenses. A 10-K may note that a utility holding company engaged in advocacy; U-12-IA names the advocate and accounts for the spending.

Key differences at a glance

  • Filer. U-12-IA is filed by the retained person or firm performing the advocacy, not by the holding company. Every other U-series form, and the 10-K narrative, is filed by the company. LD-1/LD-2 are filed by the lobbying registrant; Schedule C by the exempt organization.
  • Statute and regulator. U-12-IA arose under PUHCA 1935 and was administered by the SEC. LD-1/LD-2 sit under the LDA 1995 and are filed with Congress. Schedule C sits under the Internal Revenue Code and is filed with the IRS.
  • Scope of venue. U-12-IA reached advocacy before any governmental body (state or federal, legislative or regulatory) where the matter affected the system. LD-1/LD-2 are limited to federal lobbying. Schedule C uses tax-law definitions of lobbying and political activity.
  • Timing. U-12-IA is engagement-triggered, with disclosure tied to specific retained advocacy services. U5S, U-9C-3, and 10-K are periodic. U-1 is transactional and prospective.
  • Granularity. U-12-IA itemizes one advocate's engagement, compensation, and expenses. 10-K narratives are aggregated and qualitative. LD-2 aggregates by registrant and issue area.

The absence of a successor SEC form

The Energy Policy Act of 2005 repealed PUHCA 1935 effective February 8, 2006, and transferred residual holding-company oversight to the Federal Energy Regulatory Commission under PUHCA 2005. FERC's regime centers on books-and-records access, cost-allocation review, and merger oversight under the Federal Power Act; it did not import any U-12-IA-equivalent advocacy disclosure, and no successor SEC form was created. The dataset is therefore a closed historical archive running from EDGAR's coverage of these filings in the late 1990s through February 8, 2006, with no continuation in any SEC series. Comparable post-2006 information must be assembled from LD-2 filings, state lobbying registries, and FERC docket materials, none of which is a true substitute.

Boundary summary

U-12-IA is the only SEC dataset that captures, at the level of a specific retained advocate, advocacy performed on behalf of a registered utility holding company system, with itemized compensation and expenses. Other U-series forms cover the same systems but report corporate-side conduct filed by the company. LD-1/LD-2 cover similar activity but live outside the SEC, are limited to federal lobbying, and apply to all industries. IRS Form 990 Schedule C addresses different filers under tax law. Form 10-K may narrate lobbying at a high level but never with per-engagement detail and is filed by the issuer. No SEC or FERC form replaced U-12-IA after PUHCA 2005. What remains distinct is the combination of filer (the retained advocate), subject (advocacy for a registered system), granularity (engagement-level fees and expenses), and window (EDGAR-era filings through February 8, 2006).

Who Uses This Dataset

Because Form U-12-IA was discontinued on PUHCA repeal, the audience for this dataset is researchers, historians, journalists, archivists, and engineers building historical EDGAR corpora rather than active compliance teams.

Energy regulation historians

Academic and independent historians studying PUHCA 1935, the dismantling of registered holding-company systems, and electricity restructuring use the activity descriptions, named legislative and regulatory bodies, and engagement dates to reconstruct lobbying patterns around the Energy Policy Act of 2005 and contemporaneous rulemakings. Output is peer-reviewed articles and dissertation chapters on twentieth-century utility regulation.

Political-economy and lobbying researchers

Scholars studying corporate political activity merge the compensation table and itemized expense schedule with Lobbying Disclosure Act registers to measure disclosure overlap and substitution across regimes. The U-12-IA corpus serves as hand-coded ground truth for utility-sector advocacy in a defined window, used to validate or extend larger lobbying panels.

Law-review authors and energy or administrative-law researchers use the filings to study how the Section 12(i) obligation operated in practice. They compare the named regulatory body, scope-of-matter narrative, and filer-to-system relationship against successor disclosures administered by FERC after 2006. Output is law-review articles and treatise sections on PUHCA's enforcement history.

Investigative and accountability journalists

Reporters covering historical utility-sector influence reconstruct who was paid, how much, and to advocate before which bodies. The compensation table, itemized expenses, filer identity and address, and matter descriptions are joined to contemporaneous dockets and legislative calendars to produce retrospective features and case studies on disclosure reform.

Compliance archivists at successor holding companies

Records staff at entities descended from PUHCA-registered systems consult these filings as institutional memory when responding to FERC inquiries, internal audits, or document-retention obligations reaching pre-2006. The filer name, holding-company system identifier, and itemized expense schedule are the load-bearing fields.

Data engineers building EDGAR historical corpora

Engineers preserving discontinued form types use the per-accession metadata.json (form type, filing date, accession number, filer CIK) and the original TXT and HTML submissions to populate the U-12-IA / U-12-IA/A slice of complete EDGAR archives. The dataset supports provenance-tracked corpora and cross-form retrieval indexes.

Retrieval and LLM developers covering regulatory history

Teams building RAG systems over the full EDGAR form catalog ingest the narrative activity and body descriptions as unstructured text and the metadata.json fields for filtering by date, filer, and original-versus-amendment variant. Including U-12-IA closes a small but real coverage gap for PUHCA-era questions.

Specific Use Cases

Reconstructing pre-EPAct 2005 utility lobbying around PUHCA repeal

Energy-regulation historians read Item 4 narratives and the named regulatory or legislative body (overwhelmingly FERC, with occasional state PUCs and Congressional committees) alongside the filing date to map which registered systems retained which outside counsel as PUHCA 1935 moved toward repeal. The filer identity from Item 1, the Item 3 registered holding company system (American Electric Power, Southern Company, Entergy, and peers), and the matter description in Item 4 are joined to contemporaneous FERC dockets and Energy Policy Act legislative history to produce timeline chapters in dissertations and journal articles.

Building the U-12-IA / U-12-IA/A slice of a complete EDGAR archive

Data engineers maintaining provenance-tracked EDGAR corpora ingest the per-accession folder, the metadata.json fields (formType, accessionNo, filedAt, entities, documentFormatFiles), and the original TXT or HTML primary documents with their SGML <DOCUMENT> wrappers intact. The dataset closes a discontinued-form coverage gap so cross-form retrieval indexes and RAG systems answer PUHCA-era questions without missing the advocate-side disclosures.

Benchmarking pre-2006 disclosure shape against modern lobbying registers

Political-economy researchers parse the Item 5 compensation table (recipient, amount received, amount to be received, payer) and the Item 6(a) routine-expense total plus the Item 6(b) itemized non-routine expenses, then merge those figures against LD-2 quarterly reports and state lobbying registries for the same firms and years. The result is a hand-coded ground-truth panel measuring disclosure overlap, substitution, and venue coverage across PUHCA, the Lobbying Disclosure Act, and state regimes.

Law-review authors use the filer-to-system relationship in the entities array (Filed-by advocate versus Subject registered parent) together with the Item 4 employing-subsidiary narrative to study how Section 12(i)'s "person retained or employed" standard was applied in practice across the EDGAR-electronic window. Comparing the consistent six-item body across initial filings and U-12-IA/A amendments supports treatise sections on PUHCA's terminal enforcement record and the absence of any SEC or FERC successor form.

Investigative reconstruction of paid advocacy at named utilities

Accountability journalists working retrospectives on utility-sector influence pull the filer name and Washington business address from Item 1, the persons-working-under listed in Item 2, the named regulatory or legislative body from Item 4, and the dollar figures in the Item 5 compensation table to answer who was paid how much to advocate before which body on behalf of which registered system. The output is a per-engagement ledger that anchors case studies on disclosure reform.

Archival reference for successor holding-company records staff

Compliance archivists at entities descended from registered systems consult specific accessions when FERC inquiries, internal audits, or pre-2006 retention obligations reference a particular engagement. The Item 3 system identifier, the Item 4 employing operating company, the Item 6(b) itemized expense lines, and the fileNo and filmNo carried on the Subject entity are the load-bearing fields for matching the filing to internal records.

Dataset Access

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

This endpoint returns the dataset's metadata, including its name, description, last updated timestamp, earliest sample date, total record count and total size, the form types covered (U-12-IA and U-12-IA/A), the container format (ZIP), and the file types included (TXT, JSON, HTML). It also returns the full dataset download URL and a list of container files, each with its own download URL, size, record count, and last updated timestamp. Because the dataset covers a discontinued form (PUHCA 1935 was repealed in February 2006), the container list is stable, but the index can still be polled to detect any backfill or correction updates to specific containers. No API key is required for this endpoint.

Example
1 {
2 "datasetId": "1f13365b-9ae0-6a44-87f6-1b7826759308",
3 "datasetDownloadUrl": "https://api.sec-api.io/datasets/form-u12ia-files.zip",
4 "name": "Form U-12-IA Files Dataset",
5 "updatedAt": "2026-04-16T08:40:55.169Z",
6 "earliestSampleDate": "1999-01-01",
7 "totalRecords": 30,
8 "totalSize": 80388,
9 "formTypes": ["U-12-IA", "U-12-IA/A"],
10 "containerFormat": "ZIP",
11 "fileTypes": ["TXT", "JSON", "HTML"],
12 "containers": [
13 {
14 "downloadUrl": "https://api.sec-api.io/datasets/form-u12ia-files/2005/2005-12.zip",
15 "key": "2005/2005-12.zip",
16 "size": 6420,
17 "records": 2,
18 "updatedAt": "2026-04-16T08:40:55.169Z"
19 }
20 ]
21 }

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

The entire dataset is available as a single ZIP archive. Because the form was discontinued in 2006 and the corpus is small, the full archive is compact and a one-shot download of the complete dataset is trivial in nearly any environment. This endpoint requires an API key.

Download Single Container: https://api.sec-api.io/datasets/form-u12ia-files/2005/2005-12.zip?token=YOUR_API_KEY

Individual monthly container ZIPs can be downloaded directly using the container keys returned by the dataset index. This is useful when you only need filings from a specific month or year within the 1999 to early 2006 window. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form U-12-IA (initial statement) and Form U-12-IA/A (amendment), the advocacy-disclosure filings prescribed by the SEC under Section 12(i) of the Public Utility Holding Company Act of 1935 and the SEC's implementing Rule 62 (17 CFR Section 250.62). The amendment variant is structurally identical to an initial filing and carries the same six-item body.

What does one record in this dataset represent?

One record is one EDGAR accession on Form U-12-IA or Form U-12-IA/A, packaged as its own folder containing a normalized metadata.json and the primary form document with its SGML <DOCUMENT> wrapper intact. Each record ties one filer (the retained advocate) to one registered holding-company system, one employing operating subsidiary, one venue of advocacy, and one calendar period of compensation and expense.

Who was required to file Form U-12-IA?

The filer was the person — natural or corporate — employed or retained by a registered public utility holding company or any of its subsidiaries to engage in advocacy before legislative, regulatory, or executive officials on matters affecting the registered system. This included in-house lobbyists and attorneys, outside law and lobbying firms, public affairs firms, and trade associations whose covered work was funded by registered systems. The filer was not the holding company itself; the registered system is identified inside the filing as the party that employed or retained the filer.

What time period does the dataset cover?

The dataset spans EDGAR-era filings from January 1999 through February 8, 2006, the date the Energy Policy Act of 2005 repealed PUHCA 1935 in its entirety. No Form U-12-IA filings exist after that date, and the dataset has a hard cutoff there. The corpus is a closed historical archive with no continuation in any SEC series.

Why are there no Form U-12-IA filings after February 2006?

The Energy Policy Act of 2005 repealed PUHCA 1935 effective February 8, 2006, and the SEC's authority to require these statements terminated on that date. Holding-company oversight passed to the Federal Energy Regulatory Commission under PUHCA 2005, which did not carry forward Section 12(i) or any successor to Form U-12-IA, and no replacement SEC form was created.

What file formats are in the dataset?

The file types present in the dataset are TXT, JSON, and HTML, distributed inside ZIP containers. Plain-text TXT documents dominate the entire 1999 – 2006 window, with a small minority of HTML primary documents in the later years; every primary document retains its EDGAR SGML <DOCUMENT> wrapper. metadata.json is a flat JSON object carrying the standard SEC filing-record fields. No XBRL is present — Form U-12-IA was never tagged in XBRL.

How is this dataset different from Lobbying Disclosure Act filings (LD-1/LD-2)?

LD-1 and LD-2 are filed with the Clerk of the U.S. House and the Secretary of the U.S. Senate under the Lobbying Disclosure Act of 1995, not the SEC, and cover federal lobbying across all industries. Form U-12-IA was administered by the SEC under PUHCA 1935 and had a narrower filer population (only persons retained by registered PUHCA holding-company systems) but a broader venue, reaching advocacy before state legislatures, state public utility commissions, and government officials at any level whose action could affect the system. A single lobbyist could owe filings under both regimes.

How are records organized inside the master ZIP?

Records are partitioned by filing month. A top-level YYYY/ directory exists for each calendar year, and within each year directory there is one YYYY-MM.zip per month containing the accessions whose filedAt falls in that month. Decompressing a monthly ZIP yields a YYYY-MM/ directory in which every accession appears as its own subfolder named with the 18-digit numeric form of the accession number (dashes stripped) — so accession 0001216383-04-000002 becomes folder 000121638304000002/.