Form U-12-IB Files Dataset

The Form U-12-IB Files Dataset is a closed historical corpus of EDGAR-filed three-year statements submitted on Form U-12-IB and Form U-12-IB/A under Section 12(i) of the Public Utility Holding Company Act of 1935 (PUHCA 1935) and its implementing Rule 71(b). One record corresponds to one EDGAR accession — a packaged accession folder containing a metadata.json header projection and the original SGML-wrapped form body — disclosing a person or firm regularly employed or retained by a registered holding-company system on the routine-expense terms permitted by Rule 71(b). Filers are the engaged professionals and firms (outside counsel, accountants, consultants, engineers, tax advisers) rather than the holding companies themselves. The dataset begins with EDGAR's 1994 phase-in for PUHCA-related forms and closes at the discontinuation of the form following the Energy Policy Act of 2005, which repealed PUHCA 1935 effective February 8, 2006. Containers are distributed as ZIP archives, with body documents in TXT, HTML, or PDF and headers in JSON.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset captures the public face of every Form U-12-IB and U-12-IB/A submission accepted by EDGAR during the lifetime of the filing series. Form U-12-IB (printed on the form itself as "FORM U-12(I)-B") is the three-year compensation and engagement statement required of any natural person or firm regularly employed or retained by a registered holding company, or by a subsidiary of one, where the engagement is limited to the routine-expense scope defined in Rule 71(b) under PUHCA 1935. The statutory purpose was to put on the public record (i) the identity of the retained person or firm, (ii) the holding-company system being served, (iii) the nature of the services rendered or to be rendered, and (iv) the compensation actually received and prospectively expected over a defined three-year period — so the Commission could monitor compliance with the routine-expense exemption without requiring a separate U-12-IA application for each individual engagement.

The two form types covered, U-12-IB and U-12-IB/A, share an identical layout and an identical six-item form template; the /A suffix denotes an amendment to a previously filed three-year statement. Coverage runs from 1994 through early 2006; there is no pre-EDGAR coverage and no new records have been added since PUHCA 1935 was repealed. The dataset is distributed as ZIP container archives and bundles file types TXT, JSON, HTML, and PDF, with plain ASCII text inside EDGAR's <DOCUMENT> envelope as the dominant body format. Image attachments are stripped during dataset construction; everything else from the public submission is retained.

Content Structure of a Single Record

What one record represents

One record in the Form U-12-IB Files Dataset is a single EDGAR accession submitted on Form U-12-IB or Form U-12-IB/A. On disk, the record is materialized as one accession folder, named after the 18-digit dash-stripped accession number, that bundles a metadata.json header summary with the original EDGAR-submitted document(s) constituting the filing body. Image attachments are stripped; everything else from the public submission is retained.

Because the body is short, /A amendments typically restate every item in full rather than diff against the original, so an amendment record is generally interpretable standalone. The filing itself is short, narrative, and tabular only in its compensation schedule. It carries no audited financial statements, no periodic-report content, and no transactional disclosures; its scope is intentionally narrow and tied to a now-repealed statute.

Content layers of a single record

Each accession folder contains two structural layers:

1. A header/manifest layer expressed as metadata.json, which projects the EDGAR submission header into JSON and resolves document URLs.
2. A body layer expressed as the original-submission document(s) — in practice, almost always a single .txt file containing the SGML-wrapped form body. The file types found in the dataset are TXT, JSON, HTML, and PDF, but for this form the dominant body format is plain ASCII text inside EDGAR's <DOCUMENT> envelope; HTML and PDF body documents are marginal and image attachments are excluded outright.

The accession folder, not any single file inside it, is the unit of record. Body-document filenames follow filer-chosen ad-hoc conventions (e.g. mv6-29_u12ba.txt) rather than a standardized scheme, so the canonical way to enumerate body documents is through metadata.json -> documentFormatFiles[].documentUrl and, secondarily, the SGML <FILENAME> tag inside each <DOCUMENT> block.

The metadata.json header

metadata.json is a single JSON object that mirrors the EDGAR submission header and resolves document links. Its meaningful fields are:

• formType — either U-12-IB or U-12-IB/A.
• accessionNo — the 18-character dashed EDGAR accession number.
• filedAt — the EDGAR acceptance timestamp as an ISO-8601 string with timezone offset.
• description — the EDGAR-supplied human-readable form label, for example Form U-12-IB/A - Three-year statement by holding company employee [Section 12(i)]: [Amend].
• linkToFilingDetails — URL to the primary document on sec.gov/Archives.
• linkToTxt — URL to the full concatenated submission .txt on EDGAR.
• linkToHtml — URL to the EDGAR filing-index page.
• linkToXbrl — empty for this form; U-12-IB predates and was never brought into the structured-tagging regime.
• dataFiles — an empty array; the form carries no structured exhibits.
• documentFormatFiles — an array of per-document descriptors. Each entry carries sequence, size (bytes, as a string), documentUrl, type, and an optional description. The "complete submission text file" entry (the concatenated .txt) appears alongside individual document entries.
• entities — an array describing each party named in the EDGAR header. Each entity carries cik (CIK, 10-digit zero-padded), companyName ending in a parenthetical role suffix, type (the per-entity form type), fiscalYearEnd (MMDD), stateOfIncorporation, sic (SIC, frequently with the descriptive label appended), irsNo, fileNo, act (the governing statute code, 35 for PUHCA 1935), and filmNo.
• id — an opaque dataset-level record identifier.

The role suffix on entities[].companyName is the canonical filer-vs-subject discriminator:

• (Filed by) — the retained person or firm submitting the statement. Typically a natural person, a law firm, an accounting firm, or a consultancy. These rows commonly omit act, fileNo, irsNo, and filmNo because the filer itself is not a registered entity under PUHCA.
• (Subject) — the PUHCA-registered holding company (or subsidiary) being served. These rows generally carry the full identifier set, including act = 35 and a PUHCA fileNo of the 070-NNNNN family.

A typical record contains exactly one (Filed by) entity paired with one or more (Subject) entities; multi-subject records are normal and reflect a single retained firm serving several PUHCA systems simultaneously. The entities array, not any single subject field, is the source of truth for the served-system relationship.

The form body and its six numbered items

The body document is wrapped in EDGAR's SGML envelope with <DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, and <TEXT> tags around the form contents. Inside <TEXT>, the form is rendered as monospaced ASCII pages separated by <PAGE> markers, with the compensation schedule expressed as an SGML <TABLE> block using <CAPTION>, <S>, and <C> column tags.

The body opens with a fixed cover block: the issuing authority ("SECURITIES AND EXCHANGE COMMISSION, Washington, D.C."), the form designation "FORM U-12(I)-B (THREE-YEAR STATEMENT)", an optional "AMENDMENT NO. n" line on /A filings, the three-year reporting window (e.g. "Three year period ending December 31, 2006"), and the statutory caption tying the statement back to Section 12(i) of PUHCA 1935 and Rule 71(b) thereunder.

Below the cover, the form follows a strict six-item template:

1. Name and business address of the person filing. The filer's full legal name (for an individual or for a firm such as a law partnership), street address, city, state, and ZIP. Multi-office firms commonly list a principal office plus the subsidiary office addresses involved in the engagement.
2. Persons through whom the undersigned proposes to act. Where the filer is a firm rather than a single natural person, the named partners, attorneys, or professionals who actually perform the services, typically broken out by office. This item supplies the underlying human counterparties for the statutory exemption.
3. Registered holding companies and/or subsidiaries served. The PUHCA-registered holding company or system for which the filer is engaged, frequently phrased as "X Corp and its subsidiaries". This item ties the filing to a specific registered system and, in combination with the (Subject) entries in metadata.json, is the principal join key against the universe of PUHCA-registered holding companies.
4. Position held or nature of services rendered or to be rendered. A brief narrative description of the engagement — for example, general legal advice and counseling on PUHCA 1935, Federal Power Act, or energy-legislation matters; tax advisory work; consulting; or accounting services. The content is qualitative, not transactional.
5. Compensation. A tabular schedule with columns typically captioned Name of recipient, Received (compensation already received over the period to date), To be received (estimated remaining compensation through the end of the three-year period), and Person or company from whom received (the paying entity within the holding-company system). In a substantial share of filings, individual dollar amounts are masked with an asterisk and footnoted to "Exhibit A, submitted under a request for confidential treatment pursuant to Rule 104"; under that mechanic the actual dollar figures are filed separately and withheld from the public record, so the asterisks remain in the body text but the underlying numeric amounts are absent from the dataset.
6. Expenses. Itemized routine expenses falling within Rule 71(b), or, more commonly, an explicit negative statement such as "(b) No other expenses." This item enforces the routine-expense ceiling that justifies use of U-12-IB rather than a more burdensome exemption application.

The body closes with a dated, typed signature block in the form Date: <date> By: /s/ <signer name>, optionally with the signer's title where the filer is a firm rather than an individual.

The Exhibit A / Rule 104 mechanic

Form U-12-IB has a built-in confidential-treatment pathway for the compensation schedule. Where the filer or the served holding company prefers not to disclose individual dollar amounts publicly, Item 5 cells are filled with asterisks and a footnote points to "Exhibit A", which is submitted to the Commission under a request for confidential treatment pursuant to Rule 104 under PUHCA. The Exhibit A document itself is not part of the public submission, is not transmitted through the normal EDGAR document stream, and is therefore not present in the dataset under any record. The dataset captures only what was filed publicly: the form body with its asterisked compensation cells. Downstream consumers should treat asterisked Item 5 cells as deliberately withheld figures (filed but suppressed at the source), not as zeros, nulls, or data-quality artifacts.

Included content

Each record packages the public face of the filing in full:

• The complete EDGAR header projected as metadata.json, including all named entities with their CIKs, role suffixes, and identifying codes; the form-type label; the acceptance timestamp; and the resolved document URLs.
• The full primary body text, preserving the EDGAR SGML wrapper, <PAGE> pagination, the cover block, all six numbered items, the SGML compensation <TABLE>, and the signature block.
• Any additional non-image documents that accompanied the original submission, enumerated through documentFormatFiles.

Excluded or separate content

• Image attachments are stripped from each accession folder per the dataset's construction rules. References to such images may still appear in the body text, but the image bytes are not included.
• Exhibit A confidential compensation schedules filed under Rule 104 are not part of the public submission and are therefore not part of the dataset; the underlying dollar figures behind asterisked cells remain unavailable at the source.
• Linked filings — the original U-12-IB that an /A amendment modifies, sibling U-12-IB filings by other employees of the same holding company, related U-12-IA exemption applications, or the registered holding company's own PUHCA filings — live in their own accessions and are not embedded.

Stability of the form across the 1994-2005 window

The Form U-12-IB template is unusually stable across the dataset's lifetime. The statute and rules that defined it (Section 12(i) of PUHCA 1935, Rule 71(b), and the Rule 104 confidential-treatment mechanic for Exhibit A) did not undergo redesign during the EDGAR era for this exemption pathway, so the six-item structure, the cover-page caption, and the compensation-table layout remain effectively unchanged from the earliest 1994 filings through the last filings in 2005-2006.

The principal historical event in the corpus is therefore not a redesign of the form but its discontinuation. The Energy Policy Act of 2005, signed into law in August 2005, repealed PUHCA 1935 effective February 8, 2006 and replaced it with PUHCA 2005 administered primarily by FERC rather than the SEC. With the statutory basis for Section 12(i) removed, Form U-12-IB and its /A counterpart were discontinued; the corpus has a clear trailing tail of late three-year statements and final amendments through late 2005 and into early 2006, after which no new records appear.

Source-file presentation is also stable. Filings are submitted as plain ASCII inside EDGAR's SGML <DOCUMENT> envelope, with <PAGE> markers and an SGML <TABLE> for the compensation schedule. The form did not transition to HTML-as-primary or to any structured-tagging regime before being discontinued, so there is no inline-XBRL or iXBRL era to describe for this form. The JSON layer (metadata.json) is a dataset-level packaging artifact, not a change in source-file format.

U-12-IB versus U-12-IB/A

The only intra-corpus content distinction is between original U-12-IB filings and U-12-IB/A amendments:

• U-12-IB records present the three-year statement for the first time for a given filer-system-period triple.
• U-12-IB/A records amend a previously filed statement. They use the same six-item template, add an "AMENDMENT NO. n" line beneath the form designation on the cover, and typically restate every item rather than presenting a delta. As a consequence, an /A record is generally analyzable on its own without reconstructing it against the original.

The amendment relationship is not embedded in metadata.json as a structured back-reference; the link to the original filing, where present at all, lives in narrative form (e.g. references to the prior accession date or amendment number) inside the body.

Interpretation and extraction notes

• Accession folder is the unit. Treat the 18-digit accession folder as the record boundary; do not assume any larger grouping equals one filing.
• Filenames are filer-chosen. Body-document filenames follow ad-hoc filer conventions and should not be guessed. Enumerate documents through documentFormatFiles[].documentUrl, and fall back to the SGML <FILENAME> tag inside the body if needed.
• Role suffixes encode position in the filing. The parenthetical on entities[].companyName ((Filed by) vs (Subject)) is the canonical filer-vs-subject discriminator. Expect act, fileNo, irsNo, and filmNo to be populated mainly on (Subject) rows; missing values on (Filed by) rows are normal, not data loss.
• Multiple subjects are normal. A single retained firm frequently serves several PUHCA systems concurrently, producing several (Subject) rows in one record.
• Confidential-treatment placeholders. Asterisks in the Item 5 compensation column signal Rule 104 confidential treatment via Exhibit A, not data quality issues. Treat such cells as withheld at source.
• Period of report is in the cover text. The "Three year period ending <date>" line on the cover defines the authoritative reporting window; it is not duplicated as a structured field in metadata.json, so accurate period extraction requires parsing the body.
• HTML-entity leakage in headers. SIC descriptions inherited from the EDGAR header retain encoded sequences such as &; consumers rendering or string-matching these should unescape them.
• SGML, not HTML. The body is SGML-flavored ASCII inside <DOCUMENT>, with <PAGE> and <TABLE> constructs that resemble but are not strict HTML. Parsers expecting well-formed HTML will need to handle these as text or as SGML.
• Amendments are full restatements. Because the body is short, /A filings typically reproduce every item, so an amendment can be analyzed standalone without joining back to the original U-12-IB.

Who Files or Publishes This Dataset, and When

Who files the record

Each record corresponds to a Form U-12-IB or U-12-IB/A submission filed on EDGAR by a person regularly employed or retained by a registered public utility holding company, or by a subsidiary of one, on terms that fit within the "routine expenses" category of Rule 71(b) under PUHCA 1935. The disclosing party is the engaged professional or firm, not the holding company. The registered holding company is named in the filing as the employer or retaining entity, but the reporting obligation runs against the individual or firm providing the services.

Filer population

The reporting population was limited to persons whose engagement with a registered holding-company system fell within the narrow category defined by Section 12(i) and Rule 71(b). In practice this included:

• outside counsel and law firms providing legal services to the system
• accountants, auditors, and tax advisers retained on a recurring basis
• engineers, technical consultants, and management consultants engaged for studies, rate work, or operational matters
• lobbyists and government-relations professionals appearing before legislative or administrative bodies
• financial advisers and similar professionals whose engagement contemplated only routine incidental expenses (travel, communications, clerical)

The form was reserved for engagements modest enough in fee structure and ordinary enough in expense profile to fit the Rule 71(b) carve-out. Retentions involving substantial or non-routine compensation, transaction-contingent fees, or unusual expense reimbursement fell outside Rule 71(b) and were handled through other PUHCA filings or Commission applications.

The relevant holding companies were the integrated and combination electric and gas systems registered with the SEC under PUHCA 1935 — a defined and bounded set of multi-state utility holding companies subject to the Act's registration regime.

Triggering event and reporting cadence

Form U-12-IB is the "three-year statement" contemplated by Rule 71(b). The obligation is tied to the existence of an ongoing qualifying engagement: while a person remained regularly employed or retained by a registered holding-company system on Rule 71(b) terms, that person was required to file a statement covering a three-year reporting period, describing the relationship, the services rendered, compensation actually received, and reasonably estimated compensation going forward.

A new qualifying engagement triggered an initial filing; a continuing engagement triggered successive filings on the three-year cadence. The form is therefore event-initiated (entry into or continuation of a Rule 71(b) engagement) but periodic in cadence (a fixed three-year reporting window), rather than transactionally triggered.

A typical filing identifies the filer, the registered holding company and any subsidiary involved, the services rendered, and compensation received and estimated for the covered period.

U-12-IB versus U-12-IB/A trigger

• U-12-IB is the original three-year statement, filed at the start of a qualifying engagement and again at each successive three-year interval while the engagement continues.
• U-12-IB/A is an amendment to a specific prior U-12-IB, identified by accession number. It is filed when the earlier statement needs correction, supplementation, or restatement — for example, to revise compensation figures, correct identifying information, or expand the description of services. Amendments are triggered by the need to fix a prior filing, not by the arrival of a new three-year period.

Regulatory framework

The form sits inside PUHCA 1935. Section 12(i) authorized the SEC to regulate by rule the employment and retention of persons by registered holding companies and their subsidiaries. Rule 71 implemented that authority; Rule 71(b) carved out engagements involving only routine expenses, and Form U-12-IB served as the periodic disclosure vehicle for those engagements — allowing Commission monitoring without case-by-case applications or orders.

The Energy Policy Act of 2005 (EPAct 2005) repealed PUHCA 1935 effective February 8, 2006, and replaced it with PUHCA 2005, administered by the Federal Energy Regulatory Commission (FERC). PUHCA 2005 is a books-and-records and cost-allocation regime; it does not carry forward the SEC's registration, employment, or routine-expense disclosure structure, and it has no analogue to Form U-12-IB. As a result, the U-12-IB filing series closes at the 2006 transition and the dataset is a fixed historical record.

Important distinctions

• Filer vs. employer. The disclosing party is the engaged professional or firm. The registered holding company is the named employer in the filing but does not itself file U-12-IB. Holding-company-level reporting flowed through other PUHCA forms (e.g., U-5S annual reports, U-13 service-company reports).
• Inside vs. outside Rule 71(b). Engagements whose compensation or expense profile exceeded the routine-expenses threshold were ineligible for U-12-IB and required different PUHCA treatment, including Section 13 applications where applicable.
• Registered vs. exempt holding companies. Only professionals retained by holding companies actually registered under PUHCA 1935 produced U-12-IB filings. Engagements with holding companies exempt from registration (for example under Section 3) did not.
• Not a securities-ownership filing. Despite being on EDGAR, U-12-IB is a utility-regulatory disclosure under a now-repealed special-purpose statute, not a Securities Act, Exchange Act, or Investment Company Act report.
• Closed series. No new U-12-IB or U-12-IB/A filings have been made since February 8, 2006. EDGAR coverage runs from 1994 through early 2006; pre-1994 paper filings under PUHCA 1935 are outside the dataset's scope.

How This Dataset Differs From Similar Datasets or Filings

Form U-12-IB belongs to the closed family of filings created under PUHCA 1935. The most useful comparisons are other U-series forms that surrounded it on EDGAR, the FERC datasets that absorbed parts of PUHCA oversight after 2006, and a small set of lobbying disclosures that resemble it only on the surface.

Form U-12-IA — true peer

The single nearest neighbor and the only engagement-level analog. Both are Section 12(i) filings describing persons employed or retained by a registered holding company or its subsidiaries, but they are triggered by different rule paths:

• U-12-IA is the general statement, filed when the engagement is not confined to the routine expenses listed in Rule 71.
• U-12-IB is the narrower three-year statement permitted under Rule 71(b) when the engagement covers only those routine expenses.

The two cover overlapping populations of consultants, accountants, attorneys, and engineers but at different cadences and detail levels. Treat them as complementary: U-12-IB for multi-year, lower-detail routine engagements; U-12-IA for point-in-time, higher-detail non-routine ones.

Form U-13-1 and Form U-13-60 — entity-level service company

U-13-1 was the application to organize a mutual or subsidiary service company; U-13-60 was its annual report. Both are filed by the service company entity and report aggregate intra-system cost allocations and billings. U-12-IB is filed by an individual person or firm describing their own engagement and compensation. Use U-13-60 for system-level service-company economics; U-12-IB for the individual professionals being paid inside that system.

Form U5S — system-level annual report

The annual report of registered holding companies, filed by the parent. Form U5S consolidates financial, organizational, and intercompany data for the entire registered system. U-12-IB is a single individual's three-year compensation statement. Pair them: U5S for system context, U-12-IB to identify and quantify the professionals attached to it. Neither contains the other's content.

Form U-1 — transactional approvals

The application or declaration under PUHCA Sections 6 and 7 for SEC approval of securities issuances, acquisitions, and other corporate acts. Form U-1 is transactional and event-driven; U-12-IB is periodic and personnel-focused. Same legal framework, near-zero factual overlap.

Forms U5A and U5B — registration entry points

U5B is the registration statement filed by a holding company becoming subject to PUHCA registration; U5A is the related notification. They establish the registered status that later triggers U-12-IB obligations and are useful only as upstream context to identify which systems' professionals would subsequently appear in U-12-IB filings.

Form U-9C-3 — quarterly activity report

A quarterly report on energy-related and gas-related activities of registered holding companies under Rule 58 and related provisions. Activity-focused at the system level. Shares only the registered-system reporting universe with U-12-IB; content is otherwise unrelated.

Lobbying Disclosure Act filings (LD-1, LD-2) — surface similarity only

LD-1 (registration) and LD-2 (semiannual activity) look superficially like U-12-IB because a named person or firm discloses paid professional services and compensation. The resemblance ends there:

• Lobbying Disclosure Act filings cover lobbying contacts with federal officials, filed with Congress (House Clerk, Senate Secretary).
• U-12-IB covers routine professional services to a registered holding-company system under PUHCA Section 12(i), filed with the SEC on EDGAR.

Different statute, different filers, different counterparties, no shared identifiers, no continuity. Not a substitute or extension.

FERC Form 60 and FERC EQR — post-2006 successors

After PUHCA 1935 was repealed, SEC oversight of the U-series ceased and parts of the function moved to FERC.

• FERC Form 60 is the annual report of centralized service companies under PUHCA 2005. It is the closest functional descendant of U-13-60, not of U-12-IB; the post-2006 regime has no individual-professional analog. Analysts seeking continuity must drop down to system-level reporting.
• FERC EQR captures wholesale electric power transactions. It appears here only because researchers tracing utility-system economics across the 2005 boundary will encounter it. It shares no record structure or filer population with U-12-IB.

Key differences at a glance

Boundary summary

U-12-IB is distinct on four simultaneous axes: person-level (not entity-level) filer, Rule 71(b) routine-expense trigger (not general or transactional), three-year forward statement (not annual or event-driven), and engagement-level service-and-compensation content captured by no other PUHCA form. U-12-IA is its only true peer at the engagement level. U5S, U-13-60, and U5A/U5B provide system-level context. FERC Form 60 is the nearest post-2006 descendant but operates one level coarser. LD-1/LD-2 share only surface form and should not be merged with U-12-IB for analytical purposes.

Who Uses This Dataset

The Form U-12-IB Files Dataset is a closed, narrow corpus, and its user base is correspondingly small and specialist. Each record names a filer, the registered holding company that engaged them, services rendered, and compensation received plus estimated, supporting a discrete set of historical and regulatory workflows.

Energy regulatory historians

Academic historians of U.S. utility regulation use the filer name, holding-company employer, and services description to map the adviser ecosystem around registered holding-company systems in PUHCA's final decade. Output: journal articles, dissertations, and books on the 1994-2005 transition from SEC PUHCA oversight to post-2006 FERC supervision.

Energy regulatory lawyers and PUHCA scholars

Energy lawyers and PUHCA-focused academics treat the filings as primary source for the scope of Rule 71(b)'s routine-services carve-out. The "services rendered" narrative, compensation figures, and the difference between original filings and U-12-IB/A amendments support treatise sections, CLE materials, and doctrinal commentary on Section 12(i) practice.

Lobbying and influence researchers

Researchers reconstructing late-PUHCA adviser networks pull filer name, address, holding-company engager, and disclosed dollar amounts to build issuer-to-adviser graphs. The deliverable is influence maps and historical analyses of which lawyers, consultants, and lobbyists were closest to specific registered systems before repeal.

FERC and state-PUC bridging analysts

Analysts who need a continuous pre/post-2006 series join U-12-IB compensation and service-description fields onto FERC Form 60 service-company data and state PUC filings. Output: multi-decade panels of professional-services spend used in rate-case work, cost-allocation studies, and empirical regulatory research spanning the repeal boundary.

Investigative journalists on pre-collapse engagements

Reporters covering early-2000s utility failures and restructurings use filer identity, address, holding-company employer, and services description to identify who was retained inside or alongside a system in the years before a notable event. Output: archival investigations and adviser-network reconstructions tied to specific holding-company collapses.

PUHCA-era litigators and retrospective compliance counsel

Counsel handling residual PUHCA-era disputes or retrospective compliance reviews for successor entities use the filings to document who was retained, in what capacity, and at what cost during the statutory period. The U-12-IB/A amendment trail matters most for showing how disclosures were corrected. Used for discovery exhibits, expert reports, and reconstruction where issuer records are incomplete.

EDGAR data-engineering teams

Engineers building historical EDGAR pipelines use the corpus as a bounded test set for accession-number coverage, mixed-format parsing (TXT, HTML, PDF with JSON metadata), entity resolution across filer and holding-company identifiers, and original-vs-amendment deduplication. Output: validated ingestion logic and entity graphs linking individual filers to registered systems.

Specific Use Cases

1. Mapping the adviser network around each registered holding-company system

Group records by entities[].companyName carrying the (Subject) suffix and the PUHCA 070-NNNNN fileNo, then enumerate every paired (Filed by) entity to produce, per registered system, the full roster of outside attorneys, consultants, accountants, and tax advisers retained under Rule 71(b). Combined with the Item 4 services-rendered narrative, this yields a per-system adviser directory for the 1994-2005 window. Deliverable: a system-by-adviser matrix usable as an appendix in regulatory-history articles or as a discovery starting point in residual PUHCA litigation.

2. Quantifying disclosed routine-services spend, with explicit confidential-treatment accounting

Parse the Item 5 SGML <TABLE> to extract Received and To be received columns per recipient and paying entity, flagging cells that contain Rule 104 asterisks rather than dollar figures. The output is a long-format compensation panel with a confidential_treatment boolean column distinguishing disclosed amounts from withheld-via-Exhibit-A cells. Deliverable: a defensible spend table that does not silently coerce asterisks to zero and that can be merged onto FERC Form 60 service-company costs at the 2006 boundary for pre/post-repeal continuity studies.

3. Reconstructing amendment trails for individual engagements

Filter on metadata.json.formType == "U-12-IB/A", parse the cover-page "AMENDMENT NO. n" line, and use the Item 1 filer name plus the Item 3 served-system text and Item 5 paying-entity column to cluster /A filings to their original U-12-IB (no structured back-reference exists). Compare Item 4 narratives and Item 5 figures across the chain to identify what was corrected. Deliverable: a per-engagement amendment lineage suitable for litigation exhibits, expert-witness reports, or doctrinal commentary on how Section 12(i) restatements were used in practice.

4. Building a Rule 71(b) doctrinal taxonomy of "routine services"

Extract the Item 4 services-rendered narrative across all records and code it into recurring categories — PUHCA general counsel, Federal Power Act advice, tax advisory, accounting, energy-legislation lobbying-adjacent counsel, engineering consultation — cross-tabulated against Item 6 (Rule 71(b) expenses, typically the "(b) No other expenses" negative statement). Deliverable: an empirical taxonomy of what filers and their served systems treated as fitting inside the Rule 71(b) routine-expense ceiling, usable in CLE materials, treatise sections, or scholarly articles on the dividing line between U-12-IB and U-12-IA.

5. Pre-collapse adviser identification for early-2000s utility failures

For a named holding-company system implicated in an early-2000s collapse or restructuring, filter (Subject) entities[].cik to that system, then use filedAt to bound filings to the years before the event and read Item 1 (filer name and address), Item 2 (named partners performing the work), and Item 4 (services rendered) for each match. Deliverable: a dated roster of which law firms, consultancies, and named individuals were retained in the run-up to a specific utility failure, used as the source layer for investigative reporting and archival reconstruction.

6. Bounded test corpus for EDGAR ingestion of pre-XBRL SGML filings

Use the full record set as a fixed regression fixture for pipelines that must handle: EDGAR <DOCUMENT>/<PAGE>/<TABLE> SGML rather than HTML, empty linkToXbrl and dataFiles fields, mixed body file types (TXT dominant, with marginal HTML and PDF), filer-chosen body filenames resolved through documentFormatFiles[].documentUrl, multi-(Subject) entity arrays, role-suffix parsing on companyName, HTML-entity leakage in SIC labels, and original-vs-amendment deduplication via formType. Deliverable: validated parser and entity-resolution code with a small, closed gold set whose ground truth will not drift because no new records will be filed.

Dataset Access

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

This endpoint returns dataset metadata including the name, description, last updated timestamp, earliest sample date, total record and size counts, covered form types (U-12-IB and U-12-IB/A), container format (ZIP), and included file types (TXT, JSON, HTML, PDF). It also returns the full dataset download URL along with the list of individual container files, each with its size, record count, last updated timestamp, and direct download URL. This makes it possible to monitor which containers were updated in the most recent refresh run and to selectively download only the changed containers on a day-by-day basis. This endpoint does not require an API key.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-697e-8404-cfcdc0194dc1",
        

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

          4
            "name": "Form U-12-IB Files Dataset",
        

          5
            "updatedAt": "2026-04-15T08:08:00.631Z",
        

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

          7
            "totalRecords": 1580,
        

          8
            "totalSize": 4261584,
        

          9
            "formTypes": ["U-12-IB", "U-12-IB/A"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

          14
                "downloadUrl": "https://api.sec-api.io/datasets/form-u12ib-files/2005/2005-08.zip",
        

          15
                "key": "2005/2005-08.zip",
        

          16
                "size": 88421,
        

          17
                "records": 12,
        

          18
                "updatedAt": "2026-04-15T08:08:00.631Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

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

Downloads the complete dataset as a single ZIP archive covering all U-12-IB and U-12-IB/A filings from January 1994 through the form's discontinuation. This endpoint requires an API key.

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

Downloads one individual monthly container archive instead of the full dataset, useful when only a specific month's filings are needed. This endpoint requires an API key.

Frequently Asked Questions

What forms does this dataset cover?

The Form U-12-IB Files Dataset covers two form types: U-12-IB, the original three-year statement filed under Section 12(i) of PUHCA 1935 and Rule 71(b), and U-12-IB/A, an amendment to a previously filed U-12-IB. Both share an identical six-item template; the /A variant adds an "AMENDMENT NO. n" line on the cover and typically restates every item rather than presenting a delta.

What does one record in this dataset represent?

One record is a single EDGAR accession submitted on Form U-12-IB or U-12-IB/A, materialized on disk as one accession folder named after the 18-digit dash-stripped accession number. The folder bundles a metadata.json header projection with the original SGML-wrapped form body document(s); image attachments are stripped, and the accession folder — not any single file inside it — is the unit of record.

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

The form was filed by the engaged professional or firm — outside counsel, accountants, tax advisers, engineers, management consultants, lobbyists, or financial advisers — who was regularly employed or retained by a holding company registered under PUHCA 1935 (or by one of its subsidiaries) on terms that fell within the routine-expense scope of Rule 71(b). The registered holding company is named as the engager but does not itself file U-12-IB.

What time period does the dataset cover?

The dataset begins in 1994 with EDGAR's phase-in for PUHCA-related forms and closes in early 2006. The Energy Policy Act of 2005 repealed PUHCA 1935 effective February 8, 2006, removing the statutory basis for Section 12(i) and discontinuing Form U-12-IB; no new records have been filed since then, and the corpus is a fixed historical record.

Why are some compensation amounts shown as asterisks?

Form U-12-IB has a built-in confidential-treatment pathway under Rule 104. Where the filer or the served holding company prefers not to disclose individual dollar amounts publicly, the Item 5 compensation cells are filled with asterisks and footnoted to "Exhibit A", which is filed separately under a confidential-treatment request. Exhibit A is not part of the public submission and is therefore not in the dataset; asterisked cells should be treated as deliberately withheld figures, not as zeros, nulls, or data-quality artifacts.

How does this dataset differ from Form U-12-IA?

U-12-IA is the only true engagement-level peer of U-12-IB. Both are Section 12(i) filings describing persons retained by a Securities and Exchange Commission-registered holding company, but U-12-IA is the general statement filed when an engagement is not confined to routine expenses, while U-12-IB is the narrower three-year statement permitted under Rule 71(b) when the engagement covers only routine expenses. U-12-IB is multi-year and lower-detail; U-12-IA is point-in-time and higher-detail.

What file format is the dataset distributed in?

The dataset is distributed as ZIP container archives. Inside each container, individual records package a metadata.json header alongside body documents in TXT, HTML, or PDF — though for this form the dominant body format is plain ASCII text inside EDGAR's SGML <DOCUMENT> envelope, with <PAGE> markers and an SGML <TABLE> for the compensation schedule. The form was never brought into the structured-tagging regime, so linkToXbrl and dataFiles are empty for every record.