Form U-7D Files Dataset — PUHCA Rule 7(d) Leveraged-Lease Exemption Certificates

The Form U-7D Files Dataset is the complete EDGAR-era population of Rule 7(d) certificates filed under the Public Utility Holding Company Act of 1935 (PUHCA) by equity-side participants in leveraged-lease financings of regulated utility assets. Each record is a single Form U-7D or Form U-7D/A submission — the certificate by which an owner participant or owner trustee attested that its passive lessor interest in a leased generating station, transmission system, or pipeline asset did not make it a "holding company" under Section 2(a)(7) of PUHCA. EDGAR coverage runs from January 1995 through February 8, 2006, the effective date on which the Energy Policy Act of 2005 repealed PUHCA and retired the form. Because the underlying transactions were 25- to 30-year leveraged leases, the certificates remain a working reference in 2026 for the lawyers, analysts, tax professionals, and trustees managing leases that are still live.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset assembles every Form U-7D and U-7D/A certificate accepted by EDGAR during the eleven-year window in which the form was both available and required, and packages each filing as a self-contained accession folder. The corpus is closed at the source: PUHCA was repealed effective February 8, 2006, the form became obsolete on that date, and no further U-7D or U-7D/A filings — including amendments to pre-2006 transactions — have been or are expected to be made. Pre-EDGAR U-7D certificates exist only in the Commission's paper records and are not included.

Form U-7D was used by owner participants and owner trustees that took title to public-utility facilities in leveraged-lease financing structures and then leased those facilities back to a regulated public-utility company. Its function was narrow and prescribed: to attest that the equity holders in the lessor structure satisfied the conditions of Rule 7(d) and were therefore exempt from registration as a "holding company" under PUHCA, despite holding legal or beneficial title to the leased utility asset. The U-7D/A amendment variant updates or restates a previously filed certificate — typically to reflect refinancings, assignments to a successor owner participant, restructurings of loan tranches, or corrections to the original.

The dataset is distributed as monthly ZIP archives. File types found across the corpus are TXT, HTM/HTML, and JSON. Because the form was filed only by a small population of leveraged-lease investors and trustees, monthly archives are tiny — many months hold only a handful of records, and months with no filings appear as essentially empty ZIPs whose index reports zero records.

Content Structure of a Single Record

What one record represents

One record in the Form U-7D Files Dataset is a single Form U-7D or Form U-7D/A submission as accepted by EDGAR, identified by its accession number and materialized as one folder containing exactly two artifacts: a metadata.json describing the submission header and one body document carrying the certificate itself. The folder name is the 18-digit zero-padded accession number with dashes stripped (for example 000095013003000269). Each record captures one Rule 7(d) certificate event — the lessee, the leveraged-lease transaction, the owner participant and owner trustee, the regulatory order, the financial terms, and the certification that the conditions for exemption from holding-company registration are satisfied.

Container and folder layout

The dataset is delivered as monthly ZIP archives organized under a <YEAR>/<YEAR>-<MM>.zip path scheme, one ZIP per calendar month. Inside each monthly ZIP is a single <YEAR>-<MM>/ directory whose immediate children are accession-numbered folders, one per U-7D or U-7D/A filing accepted that month.

          1
          <YEAR>/
        

          2
            <YEAR>-<MM>.zip
        

          3
              <YEAR>-<MM>/
        

          4
                <18-digit-accession-no>/
        

          5
                  metadata.json
        

          6
                  <primary-document>.{txt|htm|html}
        

There is no per-filer or per-form nesting beyond the accession folder, and the accession folder itself is flat: metadata.json and the body document sit side by side with no further hierarchy.

Per-accession folder contents

Every accession folder contains exactly one metadata.json and exactly one body document. The body document is the filer's primary U-7D submission and retains its original EDGAR filename: legacy filings carry filer-specific names such as formu-7djan16.txt, while modern filings almost universally use du7d.htm. Image files (graphics, scanned signature pages, logos) that may have accompanied the original EDGAR submission are excluded from the dataset; only the textual primary document is retained. The aggregated "complete submission text file" (<accession>.txt) that EDGAR generates by concatenating all parts of the submission within an SGML envelope is referenced from metadata.json via a URL but is not packaged inside the folder.

In practice each record is either one TXT body plus one JSON manifest (legacy filings) or one HTM/HTML body plus one JSON manifest (modern filings).

Shape and key fields of metadata.json

metadata.json is a flat JSON object capturing the EDGAR submission header in normalized form. Top-level fields:

• formType — "U-7D" for an original certificate, "U-7D/A" for an amendment.
• accessionNo — the canonical dashed accession number (for example "0000950130-03-000269"); the enclosing folder name is the same identifier with dashes removed.
• description — human-readable form description, typically "Form U-7D - Certificate, lease of utility facility [Rule 7(d)]", with : [Amend] appended for U-7D/A.
• filedAt — ISO-8601 timestamp with timezone offset capturing EDGAR acceptance (for example "2003-01-17T15:45:42-05:00").
• periodOfReport — YYYY-MM-DD date string, typically the execution date of the lease or financing transaction.
• linkToFilingDetails — URL to the primary document on www.sec.gov/Archives/edgar/data/<cik>/<accession-no-dashes>/.
• linkToTxt — URL to the complete submission text file (<accession>.txt).
• linkToHtml — URL to the EDGAR filing index page (<accession>-index.htm).
• linkToXbrl — empty string; U-7D carries no XBRL data.
• documentFormatFiles — array of objects, one per logical document in the submission. Each entry has sequence (string; "1" for the primary U-7D document, a single space " " for the synthetic complete-submission entry), size (string, byte count), documentUrl, optional description (for example "FORM U-7D" or "Complete submission text file"), and type ("U-7D", "U-7D/A", or " ").
• dataFiles — empty array; the form has no associated data exhibits.
• entities — array of entity objects describing the parties named in the EDGAR header (detailed below).
• id — opaque 32-character hexadecimal identifier assigned by the dataset publisher.

Within entities, each U-7D submission carries two entries that mirror EDGAR's filer-and-subject convention: one entity bears the (Filed by) suffix in companyName, and a second entity bears the (Subject) suffix. In practice the two entries typically describe the same legal person and CIK, with the suffix in companyName serving as the role marker — the owner participant files a certificate naming itself as the subject of the Rule 7(d) exemption claim. Per-entity fields include cik (zero-padded 10 digits), companyName (with the role suffix), irsNo, stateOfIncorporation (for example "MA", "DE"), and an optional fiscalYearEnd in MMDD form. The (Subject) entity additionally carries act ("35", the Public Utility Holding Company Act), fileNo (the PUHCA file number, for example "032-00532"), filmNo (the EDGAR film number assigned at acceptance), and a type field echoing the form type. SIC codes appear on entity objects only when EDGAR has one on file for the registrant and are formatted as "<code> <label>" (for example "6311 Life Insurance").

Anatomy of the U-7D body document

Both TXT and HTM body documents are wrapped in EDGAR's standard SGML <DOCUMENT> envelope — a short header announcing the document type, sequence position, filename, and human description, followed by the certificate payload between <TEXT> and </TEXT> tags:

          1
          <DOCUMENT>
        

          2
          <TYPE>U-7D
        

          3
          <SEQUENCE>1
        

          4
          <FILENAME>du7d.htm
        

          5
          <DESCRIPTION>FORM U-7D
        

          6
          <TEXT>
        

          7
          ... certificate body ...
        

          8
          </TEXT>
        

          9
          </DOCUMENT>
        

The payload follows a tightly prescribed template that has been stable across the form's lifespan. The structural elements appear in this fixed order:

Header block. Three centered title lines — FORM U-7D, CERTIFICATE PURSUANT TO RULE 7(d), and PUBLIC UTILITY HOLDING COMPANY ACT OF 1935 — followed by a marker reading either Initial Filing (original U-7D) or Amendment accompanied by the pre-existing PUHCA file number (U-7D/A).

Certifying paragraph. A short attestation, typically reading "The undersigned certify that this certificate accurately summarizes ... the lease identified herein and the transactions for the financing thereof", introduces the body and frames the items that follow as the certified summary required by Rule 7(d).

Preliminary Note. A narrative block situating the transaction. It typically describes the head-lease/leaseback structure, identifies the equity investor and any owner trustee, names the public-utility lessee, recites the lease term, and — for amendments — traces the chain of predecessor U-7D filings, which can span multiple owner participants over decades as 1980s leveraged-lease structures pass through assignments and refinancings.

Numbered items 1 through 11. The substantive body is a fixed list of eleven numbered disclosures, with letter sub-items that appear when the underlying transaction warrants them:

1. Lessee — the public-utility company that operates the leased facility, with name and principal address.
2. Date of lease — the effective date of the lease agreement. Sub-item 2a records the expected or actual in-service date of the facility when distinct from the lease date.
3. Regulatory authority and date of order — the federal or state regulatory body (for example FERC or the relevant state public utilities commission) that approved the lease and the date of its order; "Not Applicable" is recorded when no regulatory order was required.
4. Initial term of lease — the length of the basic lease term. Sub-item 4a enumerates renewal options, with each option's length and exercise mechanics.
5. Brief description of facility — a concrete identification of the leased asset, typically naming a specific generating unit, transmission system, or undivided fractional interest in such an asset (for example "530 MW (gross) coal-fired electric generating unit" or a percentage undivided interest in a named transmission system).
6. Manufacturer or supplier — the principal vendor of the facility or its major components.
7. Cost of facility — the original cost of the facility and, where the lease covers an undivided fractional interest, the proportional cost attributable to that interest.
8. Basic rent for the initial term — the aggregate basic rent payable over the initial term. Sub-item 8a details the periodic installment schedule, giving amount and frequency (for example semi-annual rent payments by amount and date).
9. Holder of legal title to facility — typically the owner trustee, a bank or trust company acting under an owner trust agreement, with full corporate name and address.
10. Holders of beneficial interests — the equity investors in the owner trust, listed by name and address along with dollar amount invested and percentage of equity; rendered as a multi-row table when multiple investors participate.
11. Loan financing details — the debt side of the leveraged-lease structure: aggregate amount borrowed, the interest rate or rate schedule for each series of nonrecourse notes, the number of lenders, and the principal-repayment terms.

Execution block. A Date executed line followed by signature lines for the holder of legal title (the owner trustee) and the holder of beneficial interest (the owner participant), with name, title, and entity-of-signature attestations.

Exhibits. Many filings append supporting documents inline within the same body file. The most common is EXHIBIT A, the form of the nonrecourse promissory note that evidences the leveraged-lease debt, frequently accompanied by a prepayment-price table indicating the make-whole or premium price payable on early redemption and a SCHEDULE 1 setting out the principal-amortization schedule by payment date. An ASSIGNMENT instrument transferring the note to a collateral trustee or indenture trustee often follows. Amendment filings (U-7D/A) commonly republish substantial portions of these exhibits to reflect amended terms.

Included content

Each record retains the full text of the primary U-7D or U-7D/A document as submitted to EDGAR — header block, certifying paragraph, Preliminary Note, all eleven numbered items with their sub-items, signature block, and any exhibits embedded within the same SGML document — together with the structured metadata.json describing the submission header. The SGML <DOCUMENT> wrapper is preserved verbatim around the payload so that the EDGAR-native type, sequence, filename, and description tags remain inspectable.

Excluded or separate content

Image files that may have accompanied the original EDGAR submission are omitted. The aggregated complete-submission text file (<accession>.txt) is referenced from metadata.json via linkToTxt but is not packaged in the folder, since it would only duplicate content already present in the primary document. There is no separate XBRL exhibit set — linkToXbrl is uniformly empty and dataFiles is uniformly an empty array, because U-7D never carried XBRL or other structured data exhibits.

The U-7D/A amendment variant

The amendment record uses the same folder layout, the same metadata.json shape, and the same body-document template as the original certificate. It differs in three observable ways. First, formType is "U-7D/A" rather than "U-7D", description ends with : [Amend], and the header block of the body document is marked Amendment together with the pre-existing PUHCA file number rather than Initial Filing. Second, the Preliminary Note typically expands into a chronicle of prior filings, identifying each predecessor owner participant or trustee and the chain of assignments, refinancings, or restructurings that led to the present amendment. Third, amendment filings frequently restate the supporting exhibits in full — most commonly the form of the amended nonrecourse promissory note with its prepayment-price tables and principal-amortization schedule — so that the amended terms stand as a self-contained record rather than a delta against the original certificate.

Format evolution from 1995 to 2006

Across the form's eleven-year EDGAR history, the body document migrated from plain-text to HTML while the substantive template remained unchanged.

The legacy plain-text variant, prevalent in the 1995-through-early-2000s era and still occasionally used by individual filers up to the form's discontinuation, is fixed-width ASCII inside an SGML <DOCUMENT> envelope. It uses <PAGE> markers to denote page breaks for paginated rendering, hand-drawn underline and dash sequences as section dividers, and EDGAR's SGML financial-table tagging — <TABLE>, <CAPTION>, <S>, and <C> — to wrap rent schedules, equity-investor listings, prepayment-price tables, and amortization schedules so that column alignment is preserved when EDGAR renders the submission.

The HTML variant, which became standard in the early 2000s, carries the identical numbered template inside the same SGML envelope but expresses each item-and-answer pair as a row in nested HTML tables, typically with <FONT FACE="Times New Roman" SIZE="2"> cells for body text. Pagination uses <p Style='page-break-before:always'> instead of <PAGE>, and dollar tables, signature blocks, and exhibit headings are wrapped in further nested HTML tables rather than fixed-width ASCII alignment. Substantive content, ordering, and item numbering are identical across the two formats; only the rendering convention changes.

Interpretation and extraction notes

Several recurring nuances matter for downstream interpretation.

• The two-entity pattern in metadata.json — one (Filed by) entry and one (Subject) entry, typically sharing the same CIK and differing only by the suffix in companyName — reflects the form's mechanics rather than two distinct legal persons; the PUHCA-specific fields (act, fileNo, filmNo) appear on the (Subject) side only.
• Parallel sibling filings on the same date by the same filer agent referencing the same underlying utility facility are common, because leveraged-lease structures frequently divide an undivided interest in a generating station or transmission system across multiple owner-participant vehicles, each of which files its own U-7D. These sibling filings share lessee, facility description, and periodOfReport, and differ only in the equity investor, percentage of equity, and dollar amounts.
• Reading the financing side requires items 9 and 10 together to reconstruct the full lessor side of the transaction (legal-title holder versus beneficial holders), and item 11 should be read against item 7 to reconcile the debt and equity components of the financing against the cost of the facility.
• Embedded exhibits (Exhibit A promissory note, Schedule 1 amortization, assignment instruments) sit inside the same body file and are not separately indexed in documentFormatFiles; extraction pipelines must parse them out of the primary document's text rather than expect them as discrete files.
• Format detection for a given record can be inferred from the body filename extension and the SGML <FILENAME> header, but parsers should treat the SGML <DOCUMENT> envelope as authoritative and strip it before applying TXT- or HTML-specific extraction logic to the <TEXT> payload.
• Closure of the series. Because the form was discontinued upon the February 2006 repeal of PUHCA, no U-7D record postdates that effective date and no new records will be added.

Who Files or Publishes This Dataset, and When

Who files

Each record is filed with the SEC by an equity-side participant in a leveraged-lease financing of public utility assets. The filer is never the utility itself and is not filing as a securities issuer. Two filer types appear:

• Owner participant — the equity investor in the lease, contributing roughly 20 to 40 percent of the asset's purchase price and taking the residual economic and tax position. In practice these were institutional investors: insurance companies, bank leasing subsidiaries, finance companies, and special-purpose vehicles formed by such institutions.
• Owner trustee — a trust company or bank that holds legal title to the leased facility (or an undivided interest in it) for the benefit of the owner participant, executes the head lease and the indenture securing the lease debt, and is named as lessor to the utility. Typically Delaware trust companies or the corporate trust departments of major U.S. banks.

The lessee utility and the non-recourse lenders/noteholders (who supply the remaining 60 to 80 percent of capital) are transaction parties only and do not file U-7D. A single closing commonly produces parallel U-7D certificates from the owner participant and the owner trustee, each separately certifying its own reliance on the exemption.

Regulatory framework: PUHCA 1935 and Rule 7(d)

Form U-7D existed solely to administer an exemption under PUHCA. Section 2(a)(7) of the Act defined a "holding company" to include any person that owns, controls, or holds with power to vote 10 percent or more of the voting securities of a public utility company or another holding company. On a literal reading, an owner participant or owner trustee in a leveraged lease of an entire generating station, transmission line, or comparable utility facility could be swept into that definition by virtue of holding the leased asset, and would itself become subject to PUHCA registration, structural, and reporting requirements.

Rule 7(d) provided a self-executing exemption for owner participants and owner trustees in qualifying leveraged-lease transactions, conditioned on factors including: the lessee being a regulated utility, continuing regulatory jurisdiction over the leased property, no holding of voting equity in the utility, structural separation of the lease investor from utility operations, and proper leveraged-lease documentation. Form U-7D was the certificate by which the filer represented to the Commission that those conditions were satisfied. It required no Commission approval; it was a notice-style certification supporting reliance on the exemption.

Triggering event

Form U-7D is event-driven, not periodic. The trigger is the closing of a qualifying leveraged-lease transaction in which the prospective filer would, absent Rule 7(d), be deemed under Section 2(a)(7) to hold a 10-percent-or-greater voting-equivalent interest in a public utility company through ownership of the leased asset. The owner participant and owner trustee each file at or shortly after closing to perfect their reliance on the exemption.

There is no recurring U-7D obligation. Once the certificate is on file, no further U-7D is required so long as the transaction stays within the scope of the original certification. The dataset is correspondingly sparse: each record reflects a discrete closing or a later amendment, not an ongoing reporting cycle.

When U-7D/A is filed

A U-7D/A is filed to amend a previously filed U-7D — for material modifications to the lease or financing, refinancings of the lease debt, secondary-market transfers of the beneficial interest from one owner participant to another, substitutions of the owner trustee, or corrections to the original certificate. A given underlying transaction may appear as a single U-7D, or as a U-7D plus one or more U-7D/A records spread across the life of the lease.

Closed dataset window

The dataset is finite and historically closed. EDGAR coverage of Form U-7D begins in January 1995; pre-EDGAR U-7D certificates exist only in the Commission's paper records. The Energy Policy Act of 2005 repealed PUHCA 1935 effective February 8, 2006. Because Form U-7D existed solely to support a PUHCA exemption, the form became obsolete on that date. No new U-7D or U-7D/A filings have been made on EDGAR since the repeal, and none — including amendments to pre-2006 transactions — are expected. The records in this dataset constitute the complete EDGAR-era population, spanning the roughly eleven-year window of regulated U.S. utility leveraged-lease activity that EDGAR captured.

Important distinctions

• Filer is not the utility. The lessee public utility does not file U-7D. Utility-side PUHCA filings used other U-series forms (for example U5S annual reports for registered holding companies, U-1 declarations for transactions requiring Commission approval). U-7D records name the utility only as a transaction party.
• Filer is not acting as a securities issuer. Owner participants and owner trustees file U-7D in their capacity as lease parties; the certificate is unrelated to any Securities Act or Exchange Act reporting they may have for unrelated reasons.
• Parallel filings per closing. Both the owner participant and the owner trustee independently rely on Rule 7(d), so one closing can produce multiple U-7D filings under different filer identities. These are separate certifications, not duplicates.
• Secondary-market transfers. When an original owner participant sold its beneficial interest in the trust, the successor institutional investor typically filed its own U-7D (or caused a U-7D/A to be filed) to perfect its own exemption. A single underlying utility asset can therefore generate filings across successive owner-participant generations.
• Outside the U-7D population. Registered holding companies and transactions requiring Commission approval used other U-series forms; investors whose structures did not implicate the Section 2(a)(7) holding-company definition had no U-7D obligation. U-7D is narrowly limited to the Rule 7(d) leveraged-lease exemption population.

How This Dataset Differs From Similar Datasets or Filings

Because PUHCA had its own dedicated U-series and was repealed in 2005, the relevant comparison set for the Form U-7D Files Dataset is narrow: other U-series forms, other Rule 7 exemption mechanisms, post-repeal FERC reporting, lessee-side accounting disclosures inside 10-Ks, and the U-7D/A amendment.

Closest related PUHCA U-series forms

Form U5S — Annual report of registered holding companies. Filed by the holding company itself; periodic; system-wide in scope (intercompany transactions, service-company allocations, consolidated financials). U-7D is event-driven, filed by lessor parties, and limited to the facts supporting one Rule 7(d) certification. U5S documents the inside of the holding-company perimeter; U-7D documents staying outside it.

Form U-1 — Application or declaration. Used by registered holding companies to seek affirmative SEC approval of acquisitions, securities issuances, and intra-system financings under PUHCA Sections 6, 7, 9, 10, and 12. U-1 initiates a noticed approval proceeding that produces a Commission order; U-7D is a self-executing certification that requires no SEC action. Direction of the regulatory burden is reversed: U-1 asks permission, U-7D asserts that permission is not needed.

Form U-3A-2 — Annual exemption statement for predominantly intrastate holding companies. Recurring, entity-level, filed by the holding company to reaffirm a Section 3(a) exemption based on intrastate operations. U-7D is one-time per transaction, filed by lessor parties, and certifies a transaction-level exemption under Rule 7(d). Different exemption pathway, different filer, different cadence.

Form U-13E-1 — Mutual service company application. An organizational/approval filing under Section 13 governing service-company structure inside a holding-company system. Unrelated to lease financings; included here only because the U-13 family is sometimes lumped with U-7D by accession-prefix searches.

Form U-9C-3 — Quarterly report on services, sales, and construction contracts. Periodic intra-system commerce reporting by entities already inside the regulatory perimeter. U-7D shares no content overlap; the only commonality is the U-prefix.

Broader U-9 family and adjacent forms (U-12-IB, U-R-1, etc.). These implement reporting or approval mechanics for entities already subject to PUHCA registration. U-7D is structurally opposite: its purpose is to keep the filer out of that regime for one defined transaction.

Other Rule 7 exemption mechanisms

Rule 7 contained several subparagraphs creating exemptions from holding-company status for specific structural relationships. Only Rule 7(d) — covering passive lessor interests in leveraged leases of utility property — produced a dedicated EDGAR form. Other Rule 7 paragraphs (for example 7(c)) addressed incidental ownership situations and generated no separately filed certificate. The U-7D dataset therefore captures only the leveraged-lease subset of Rule 7 activity, not the universe of Rule 7 exemptions.

Post-repeal FERC filings (no SEC successor)

PUHCA 1935 was repealed by the Energy Policy Act of 2005, effective February 2006; PUHCA 2005 transferred holding-company oversight to FERC. None of the FERC datasets is an SEC dataset, and none continues the U-7D series:

• FERC Form 1 — annual financial/operational report by major electric utilities; operating-company side, not lessor-side, and not exemption-related.
• FERC EQR — wholesale electricity transactions and contracts; market activity, not holding-company status.
• FERC books-and-records access under PUHCA 2005 — replaced SEC registration but produced no public form analogous to U-7D.

No SEC form filed after February 2006 continues U-7D. The dataset is closed.

Leveraged-lease footnotes in operating-company 10-Ks

The same transaction typically appears, from the lessee side, in the utility operating company's 10-K under SFAS 13 / ASC 840 / ASC 842 — future minimum payments, residual values, and (historically) off-balance-sheet treatment. These are accounting disclosures for financial-statement users; U-7D is a regulatory disclosure certifying lessor non-holding-company status. A 10-K footnote rarely identifies the owner participant or owner trustee with Rule 7(d) specificity; a U-7D contains no cash-flow profile. The two sources are complementary, not substitutable.

U-7D versus U-7D/A

U-7D/A amendments do not represent new transactions or new exemption claims; they correct, supplement, or update a prior certificate (for example participant-interest transfers, financing modifications, curative disclosure). For longitudinal analysis, originals and amendments should be linked by accession-number lineage and treated as a single transaction record. In this small dataset, the U-7D/A subset often carries the most current description of the leased facility and financing terms.

Boundary summary

Form U-7D is the only EDGAR form certifying a Rule 7(d) exemption from PUHCA holding-company status for a leveraged-lease financing of utility assets. It is transaction-level (not entity-level), lessor-side (not lessee-side), self-executing (not approval-seeking), and confined to January 1995 through the February 2006 PUHCA repeal. No adjacent U-series form, no other Rule 7 mechanism, no FERC report, and no 10-K footnote substitutes for it.

Who Uses This Dataset

The Form U-7D corpus is small and historically bounded, but most of the 25- to 30-year leveraged leases it documents are still live in 2026, so a narrow set of professionals continues to consult it as the authoritative contemporaneous record of those transactions.

Regulatory historians

Scholars of late-PUHCA utility finance treat the corpus as a near-complete enumeration of EDGAR-era Rule 7(d) certificates. They use the filer-entity blocks (owner participants and owner trustees), periodOfReport to build a chronology, and the item 5 facility descriptions to map how the SEC administered Section 2(a)(7)(B) exemptions in the years before authority moved to FERC. Question answered: how did exemption practice evolve across the Act's final decade.

Energy-finance lawyers

Counsel structuring sale-leaseback, leveraged-lease, or refinancing deals on regulated generation, transmission, and pipeline assets pull prior U-7Ds as transaction precedent. They read the item 5 facility description and undivided-interest fraction, the item 8 basic-rent schedule, the item 11 loan terms (principal, maturity, rate, amortization), and attached participation, trust, and lease exhibits to model representations, opinions, and amendments. The filer block also tells them which firms and trustee institutions worked the original deal.

Utility equity analysts

Sell-side and buy-side analysts covering integrated utilities and merchant generators reconcile 10-K leveraged-lease footnotes against the underlying certificates. Item 5 confirms the asset and undivided interest, item 8 supports rent-expense and remaining-obligation models, and item 11 reveals the leveraged debt at the trust. Question answered: what is the residual off-balance-sheet exposure on a named generating station.

Tax professionals

Corporate and partnership tax practitioners working early-buyout, restructuring, termination, or audit-defense matters use the certificates to reconstruct the deal economics behind a long-running tax position. They focus on the item 5 cost basis and undivided-interest percentage, the item 8 rent stream, the item 11 nonrecourse-debt terms, and the owner-participant identity to support tax-basis reconstruction, Section 467 rent-leveling, and remaining-benefit calculations.

Trust bankers

Institutional trust departments that act as owner trustees use the filer-entity fields to inventory their own and competitors' prior appointments, item 5 to gauge operational complexity, and item 11 to size the underlying debt. The dataset feeds market-share analysis, fee benchmarking, and pitch decks for successor-trustee work on leases still running.

Litigation and forensic teams

Disputes over early-buyout valuations, casualty losses, defaults, and residual sharing surface decades after closing. Forensic accountants and litigation-support analysts treat the certificates as a contemporaneous, SEC-filed record of parties, facility, and original economics. They lean on filer identifications, periodOfReport, item 5, item 8, item 11, and exhibit summaries for damages models, party-in-interest analysis, and discovery planning when private document retention has degraded.

Securities-law researchers

Scholars studying PUHCA exemption practice and the pre-modernization SEC disclosure regime use the corpus as a self-contained illustration of a narrow, rule-specific certificate. They focus on the certification language, item structure, and variation in disclosure practice across filers and years to support comparative work on exemption regimes and teaching materials on utility holding-company regulation before 2006.

Synthesis

Across all seven groups, the same handful of fields do the work: filer identities, periodOfReport, item 5 facility descriptions, item 8 basic rent, item 11 loan terms, and exhibit summaries. The dataset is small and closed, but it remains the authoritative contemporaneous record of leveraged-lease transactions whose legal, tax, and financial consequences run well past 2026.

Specific Use Cases

1. Reconciling a 10-K leveraged-lease footnote to the original certificate

Equity analysts and audit teams covering an integrated utility match an SFAS 13 / ASC 842 footnote — future minimum lease payments and residual exposure on a named generating unit — against the underlying U-7D. Item 5 (facility and undivided-interest fraction), item 7 (cost), item 8 / 8a (basic rent and installment schedule), and item 11 (nonrecourse debt terms) supply the contemporaneous numbers the 10-K aggregates. Output: a reconciled remaining-obligation model and identification of any disclosure that drifted from the original deal.

2. Building a precedent index for new sale-leaseback and refinancing deals

Energy-finance counsel structuring a current sale-leaseback or refinancing on regulated generation, transmission, or pipeline assets pull prior U-7Ds as transaction precedent. They harvest item 4 (initial term and renewal options), item 8 (rent), item 11 (loan tranches, rate, amortization), and the embedded Exhibit A note form, Schedule 1 amortization, and assignment instruments to seed term sheets, opinions, and amendment drafts. Filer-entity blocks identify which arranger, trustee, and counsel worked the original.

3. Supporting litigation and arbitration on still-running leases

Disputes over early-buyout pricing, casualty loss, default, or residual sharing arise decades after closing. Forensic accountants and litigation-support teams treat the certificate as the contemporaneous SEC-filed record of parties, facility, and economics: (Subject) and (Filed by) entities for party-in-interest analysis, periodOfReport and item 2 for the closing chronology, items 5, 7, 8, and 11 for the damages model, and embedded prepayment-price tables for make-whole calculations when private deal binders no longer exist.

4. Tax-basis reconstruction and Section 467 work on long-dated positions

Corporate and partnership tax practitioners defending or restructuring a leveraged-lease tax position use item 7 (cost) and item 5 (undivided-interest percentage) to rebuild original tax basis, item 8 / 8a to drive Section 467 rent-leveling schedules, and item 11 to recover the nonrecourse-debt profile. Owner-participant identity from item 10 anchors the partnership audit trail when interests have been assigned across successive U-7D/A amendments.

5. Mapping owner-trustee and owner-participant market share by year

Trust bankers and competitive-intelligence teams aggregate item 9 (legal-title holder, typically a bank or trust company), item 10 (beneficial-interest holders, equity amount, and percentage), and periodOfReport across the corpus to produce market-share tables of owner-trustee and owner-participant appointments by calendar year, asset class, and deal size. Output feeds pitch decks for successor-trustee mandates and refinancing assignments on leases still in their basic term.

6. Geographic and asset-type mapping of leveraged-leased utility facilities

Researchers and infrastructure analysts extract item 1 (lessee and principal address), item 3 (regulatory authority — FERC or named state PUC), item 5 (facility type: coal-fired generating unit, transmission system, etc.), and item 6 (manufacturer) to build a facility-level inventory of which regulated assets were financed via Rule 7(d) leveraged leases, by state, by FERC versus state jurisdiction, and by technology.

7. Reconstructing transaction history through U-7D/A amendment chains

For a single underlying lease, U-7D/A amendments are linked back to the initial U-7D via the PUHCA fileNo on the (Subject) entity and the predecessor-filing chronology in the Preliminary Note. Practitioners walk that chain to track participant-interest transfers, refinancings, and restated note terms — producing a single longitudinal transaction record from which the most current rent schedule, debt terms, and equity holders can be read off the latest amendment.

8. Reassembling syndicated undivided-interest deals from sibling filings

Multiple owner-participant vehicles in a syndicated leveraged lease each file their own U-7D on the same date for the same facility, differing only in equity amount and percentage. Grouping records by periodOfReport, item 1 lessee, and item 5 facility description (then differencing item 10 entries) reconstructs the full equity stack of a single syndicated deal — useful for residual-value modeling, party-in-interest mapping, and confirming that disclosed undivided-interest percentages sum as expected.

Dataset Access

The Form U-7D Files Dataset is available through three access methods: a public JSON index for metadata and discovery, a single archive download for the entire dataset, and per-container downloads for individual monthly ZIPs. Because this is a closed historical dataset covering filings from January 1995 until the form was discontinued in February 2006, the contents are stable and no new records are being added.

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

This endpoint returns dataset-level metadata — name, description, updatedAt, earliestSampleDate, totalRecords, totalSize, formTypes (U-7D, U-7D/A), containerFormat (ZIP), and fileTypes — together with the full dataset download URL and a containers array listing each monthly ZIP with its key, size, records, updatedAt, and downloadUrl. Although this dataset is closed, the index can still be polled to detect any back-corrections or refreshes to existing containers. This endpoint does not require an API key.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-6a0a-8749-f3011fc856a3",
        

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

          4
            "name": "Form U-7D Files Dataset",
        

          5
            "updatedAt": "2026-04-15T18:23:14.893Z",
        

          6
            "earliestSampleDate": "1995-01-01",
        

          7
            "totalRecords": 69,
        

          8
            "totalSize": 308346,
        

          9
            "formTypes": ["U-7D", "U-7D/A"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

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

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

          16
                "size": 14237,
        

          17
                "records": 3,
        

          18
                "updatedAt": "2026-04-15T18:23:14.893Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

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

The complete dataset is small enough to retrieve in a single request and contains every Form U-7D and U-7D/A filing along with its metadata file and EDGAR submission documents (excluding image files). This endpoint requires an API key, supplied either as the token query parameter shown above or via the standard Authorization header.

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

Containers are organized by year and month (<YEAR>/<YEAR>-<MONTH>.zip). To fetch a specific monthly archive, use the downloadUrl provided for that container in the index's containers array. This endpoint also requires an API key via the token query parameter or the Authorization header.

Frequently Asked Questions

Is the Form U-7D Files Dataset still being updated?

No. PUHCA 1935 was repealed by the Energy Policy Act of 2005 effective February 8, 2006, and Form U-7D existed solely to support a Rule 7(d) exemption under that Act. No new U-7D or U-7D/A filings have been made on EDGAR since the repeal, and none — including amendments to pre-2006 transactions — are expected. The dataset is closed at the source.

What does one record in this dataset represent?

One record is a single Form U-7D or Form U-7D/A submission as accepted by EDGAR, identified by its accession number and materialized as one folder containing exactly two artifacts: a metadata.json describing the submission header and one body document carrying the certificate itself. Each record captures one Rule 7(d) certificate event — the lessee, the leveraged-lease transaction, the owner participant and owner trustee, the regulatory order, the financial terms, and the certification that the conditions for exemption from holding-company registration are satisfied.

What is the difference between U-7D and U-7D/A?

U-7D is the original certificate filed at or shortly after the closing of a qualifying leveraged-lease transaction. U-7D/A is the amendment variant, filed to update or restate a previously filed certificate — typically for material modifications to the lease or financing, refinancings of the lease debt, secondary-market transfers of the beneficial interest, substitutions of the owner trustee, or corrections to the original. Amendments do not represent new transactions; for longitudinal analysis, originals and amendments should be linked by accession-number lineage and treated as a single transaction record.

Do these filings contain the full underlying lease agreement?

No. A U-7D is a certificate, not the lease itself. It summarizes the lease and the financing in eleven prescribed numbered items — lessee, dates, regulatory order, term, facility description, manufacturer, cost, basic rent, legal-title holder, beneficial holders, and loan terms — and frequently appends supporting exhibits such as the form of the nonrecourse promissory note (EXHIBIT A), a prepayment-price table, and a SCHEDULE 1 principal-amortization schedule. The underlying head lease, participation agreement, indenture, and trust agreement are not included.

Why does the same transaction sometimes appear as multiple filings?

Two patterns produce parallel records. First, both the owner participant and the owner trustee independently rely on Rule 7(d), so a single closing commonly yields two separate certifications under different filer identities. Second, syndicated leveraged-lease structures divide an undivided interest in a generating station or transmission system across multiple owner-participant vehicles, each of which files its own U-7D on the same date for the same facility — sibling filings that share lessee, facility description, and periodOfReport and differ only in the equity investor, percentage of equity, and dollar amounts.

What file format is the dataset distributed in?

The dataset is distributed as monthly ZIP archives organized under a <YEAR>/<YEAR>-<MM>.zip path scheme. Inside each ZIP, every accession folder contains a metadata.json manifest plus one body document — a TXT for legacy filings or HTM/HTML for modern filings, both wrapped in EDGAR's standard SGML <DOCUMENT> envelope. The file types found across the corpus are TXT, HTM/HTML, and JSON; image files that accompanied the original EDGAR submissions are excluded.

How does this dataset differ from FERC filings on the same utilities?

PUHCA 2005 transferred holding-company oversight from the SEC to FERC after the 2006 repeal, but no FERC report continues the U-7D series. FERC Form 1 is operating-company financial and operational reporting; the FERC EQR captures wholesale electricity transactions; FERC books-and-records access under PUHCA 2005 produced no public form analogous to U-7D. These are operating-side or market-side disclosures, whereas U-7D is a lessor-side, transaction-level exemption certification — complementary but not substitutable.