Bill comparison · Status as of October 22, 2026
Data center electricity bills: a breakdown and comparison
Compare H.R. 9340, S. 5199 and S. 5653: what each proposes, who it covers and where it stands.
More of our data center coverage
Start here: a two-minute summary
As of October 22, 2026, none of these bills is law. This comparison does not establish how much a household’s electricity bill would change.
Three federal bills address who pays for the grid costs of serving very large new electricity loads such as data centers. If enacted, the bills would take different approaches:
H.R. 9340, Ratepayer Protection Act: state utility regulators would have to consider a cost-recovery standard for data centers of 100 MW or more. They would not have to adopt it.
S. 5199, GRID Savings Act: the Federal Energy Regulatory Commission (FERC) would have to issue rules for connecting covered large loads of 150 MW or more to interstate transmission. The customer would pay 100% of specified connection-facility costs (Interconnection Facilities and Direct Assignment Facilities).
- Network-upgrade costs allocated to the customer would be credited back against transmission service charges. Transmission wholly within ERCOT (Texas) would be excluded. (New FPA §224(a)(3), (b)–(c), (d)(2)(B)–(C), (f)(2))
S. 5653, Bipartisan American Affordability and Jobs Act: Congress would write a cost-recovery floor directly into the Federal Power Act for data center loads of 20 MW or more.
It would also require FERC to rewrite transmission pricing for computing loads. EIA would have to revise its Form 861 survey to include load from data center entities.
The 20 MW threshold applies only to new FPA §228 (the cost floor and the related state-authority provisions); the transmission-pricing (Sec. 2107(a)) and data (Sec. 2114) provisions set no MW threshold.
Explore the comparison
This page compares three selected federal bills, as of October 22, 2026, for use in research conversations with reporters. It does not cover all data center legislation; other bills are listed under "Additional legislation outside this three-bill comparison."
This comparison does not establish how much a household's electricity bill would change.
Side by side
Where things stand, as of October 22, 2026: None is law. H.R. 9340 passed the House and remains on the Senate calendar; S. 5199 and S. 5653 were referred to Senate Energy and Natural Resources.
On a narrow screen, scroll the table sideways. Numbered references lead to the source guide.
| Topic | H.R. 9340 (EH) · Ratepayer Protection ActEngrossed in House (EH) | S. 5199 (IS) · GRID Savings Act of 2026Introduced in Senate (IS) | S. 5653 (IS) · Bipartisan American Affordability and Jobs Act of 2026 (data center sections)Introduced in Senate (IS) |
|---|---|---|---|
| Proposed change | States would have to consider (and decide on) a federal standard. Each state regulator (and nonregulated utility) would decide whether to adopt it. | FERC would have to write binding interconnection rules [1] | Cost allocation: Sec. 2107(b) Congress would set a cost floor directly in statute [2]. The utility would estimate incremental cost, subject to approval by FERC or a State, as appropriate [3]. How the floor would be enforced against state-set retail rates is an open question (see below). Transmission pricing: Sec. 2107(a) FERC would run a transmission-pricing process. Data collection: Sec. 2114 EIA would collect data. |
| Covered customers | Non-residential customers that, on or after enactment, request to enter into, or enter into, a contract or other agreement for the sale of electric energy for facilities that primarily run IT infrastructure for data storage and computing, with combined peak demand of 100 MW or more at a single site or campus [4] | Any new or expanded nonresidential load (not only data centers) of 150 MW or more behind one point of interconnection; on-site generation or storage is not netted out [5] | Cost allocation: Sec. 2107(b) 20 MW or more from data centers or high-density computing (AI, cloud, crypto mining) at one site or commonly owned sites, or expected to reach 20 MW at full buildout [6] Transmission pricing: Sec. 2107(a) No MW threshold; covers computing sites connected to the bulk-power system [7] Data collection: Sec. 2114 No MW threshold; load from "data center entities" [8] |
| Costs covered and limits | Standard to be considered: rates designed to recover the large-load customer's "full, incremental cost" of generation, transmission or distribution upgrades, including if it walks away; financial assurances before upgrades [9] Limits and exceptions: PURPA §112(b) and (c) (the deadlines to begin and finish considering the standard, and the fallback requirement to consider it in the next rate proceeding if those deadlines are missed) do not apply to the new standard for a particular electric utility if, before enactment, its State had implemented the standard (or a comparable one) for that utility, the State regulator (or, for a nonregulated utility, the utility itself) had conducted a proceeding to consider implementing it for that utility, or the State legislature had voted on implementing it for that utility [10]. | FERC jurisdiction over large-load interconnection to interstate transmission [11]; 100% of Interconnection Facilities and Direct Assignment Facilities costs directly assigned to the customer [12]; Network Upgrade costs allocated to the customer and then credited back against transmission charges [13]; payment and financial security rules [14] Limits and exceptions: Would not apply to transmission wholly within ERCOT (Texas) [15] | Cost allocation: Sec. 2107(b) "No portion of the incremental cost" could be allocated to or recovered from other customers, subject to the section's rules of construction [16]; recovery would continue if the load exits early [17]; financial assurance before generation, transmission or distribution upgrades [18]. Limits and exceptions: The floor [19] and state-authority provisions [20] would apply only to covered loads that interconnect on or after enactment. Arrangements approved by FERC or a State before enactment would remain in effect [21]. §228(c)–(d) state that States may charge more than cost, use open seasons or competitive solicitations, require new generation, require limited or non-firm transmission service, and treat covered loads as a separate class on terms less favorable than other large industrial, manufacturing or commercial loads. §228(e)(2) says the subsection (c)(1) powers are reserved state authority that the section recognizes rather than creates. Transmission pricing: Sec. 2107(a) FERC would have to revise its 1994 transmission pricing policy statement so utilities charge customers seeking transmission service on behalf of computing-load owners/operators both embedded and incremental transmission cost, with incremental payments credited to the utility's annual transmission revenue requirement [22] Data collection: Sec. 2114 EIA would have to revise Form 861 to include load from data center entities [23] |
| Current status | Passed the House 417–3 under suspension of the rules (two-thirds required), Sept 16 (Roll Call 312). Remains on the Senate calendar (Cal. No. 684). No further action through Oct 22. Senate history is under "Status and procedural history" below. | Introduced July 30; referred to Senate Energy and Natural Resources | Introduced Sept 30; referred to Senate Energy and Natural Resources |
Sources for the table: H.R. 9340 as passed by the House (EH); identical text placed on the Senate calendar [24] · S. 5199 as introduced · S. 5653 as introduced · Status data from the official bill status files (H.R. 9340, S. 5199, S. 5653) · House Roll Call 312.
1. H.R. 9340: states would have to consider a standard
What it would do. It would add a new federal "standard" to the Public Utility Regulatory Policies Act (PURPA). State utility regulators (and nonregulated utilities) would have to consider the standard but would not have to adopt it (see "Why 'consider' matters" below).
Under the standard, rates for a large-load customer "shall be designed to recover" the full, incremental cost of any generation, transmission or distribution upgrade needed to serve it, including if the customer ends its contract or stops buying power.
The standard also provides that, before building the upgrade, the utility require financial assurances or contributions. [25]
Why "consider" matters. PURPA standards work differently from direct mandates. Under existing law, each state regulator "shall consider each standard … and make a determination concerning whether or not it is appropriate to implement" it. The law also says "nothing in this subsection prohibits" a state from deciding it is not appropriate, and a state "may, to the extent consistent with otherwise applicable State law, … decline to implement" a standard.
Its determination must be in writing after public notice and a hearing. If it declines a standard it found appropriate, it must state its reasons in writing. [26] H.R. 9340 would set the clock: start within 1 year, finish and decide within 2 years. [27]
Who is covered. Non-residential customers that, on or after enactment, request to enter into, or enter into, a contract or other agreement for the sale of electric energy for facilities that primarily run IT infrastructure for data storage and computing, with combined peak demand of 100 MW or more at a single site or campus. [28]
Exception. PURPA §112(b) and (c) (the deadlines to begin and finish considering the standard, and the fallback requirement to consider it in the next rate proceeding if those deadlines are missed) do not apply to the new standard for a particular electric utility if, before enactment, its State had implemented the standard (or a comparable one) for that utility, the State regulator (or, for a nonregulated utility, the utility itself) had conducted a proceeding to consider implementing it for that utility, or the State legislature had voted on implementing it for that utility [29]. [30]
2. S. 5199: FERC would set large-load interconnection rules
What it would do. It would add a new section 224 to the Federal Power Act. FERC would get jurisdiction over connecting any "covered large load" to interstate transmission, and it would have to issue a final rule within 1 year setting standards and procedures. [31]
Who pays for what. The FERC rule would have to:
- Assign 100% of the costs of "Interconnection Facilities" and "Direct Assignment Facilities" directly to the large-load customer. [32]
- Allocate "Network Upgrade" costs to the large-load customer, with those costs "credited back against transmission service charges," following the model of FERC's existing interconnection procedures. [33]
- Require payment of allocated costs and financial security to protect any customer from unrecovered costs if a covered large load fails to proceed or perform. [34]
- Require cost disclosure to the customer, state commissions and FERC, and a study process that protects other customers from speculative requests. [35]
Who is covered. Any new or expanded nonresidential load, or group of such loads under common ownership, control or affiliation at one site or at contiguous or adjacent sites sharing electric infrastructure (including phased development), with requested or projected peak demand of 150 MW or more behind a single point of interconnection. Co-located generation or storage would not reduce the count. The bill is not limited to data centers. [36]
Limits. It would not apply to transmission wholly within ERCOT [37].
Its cost-allocation rules would cover transmission-side facilities (Interconnection Facilities, Direct Assignment Facilities and Network Upgrades). The text contains no provision on retail rates or local distribution costs.
Associated generation, storage or flexibility would enter only through the interconnection and study process [38].
3. S. 5653: a statutory cost-recovery floor and transmission pricing (Secs. 2107 and 2114)
S. 5653 is a broad permitting bill. The data center provisions are in Division B, Title I (Electric Transmission). [39]
Sec. 2107(b): a statutory floor [40].
- Covered load: data center or high-density computing load (AI training or inference, cloud or hosting, crypto mining) of 20 MW or more at a single site or commonly owned sites, or expected to reach 20 MW at full buildout. Computing that is ancillary to some other industrial or commercial use is excluded. [41]
- Limits on charging other customers: "No portion of the incremental cost may be allocated to, or recovered in the rates of, any customer other than a covered load, subject to the limitations described in subsection (e)." "Incremental cost" covers generation or storage and transmission and distribution costs that would have been avoided without the load. The utility would estimate it at or around the time the load begins operating, subject to approval by FERC or a State, as appropriate. [42]
- Exit and assurances: cost recovery would continue if the load leaves early, and financial assurance would be required before building generation, transmission or distribution for it. [43]
- State powers: states could charge more than cost and credit the surplus to other customers, run open seasons or competitive solicitations, require the load to bring its own new generation, require limited or non-firm transmission service, and treat covered loads as a separate class with terms less favorable than those for other large industrial, manufacturing or commercial loads [44]. The section says the subsection (c)(1) powers are reserved state authority over retail electric service that it recognizes rather than creates [45].
- Timing: the floor and state-authority provisions (subsections (b) and (c)) would apply to covered loads that interconnect on or after enactment. Arrangements approved by FERC or a State before enactment would remain in effect [46].
Sec. 2107(a): FERC transmission pricing. Congress would find it "not just and reasonable" for utilities to charge customers seeking transmission service for computing-load owners or operators less than embedded and incremental expansion costs.
FERC would have to revise its 1994 transmission pricing policy statement within 270 days so that utilities charge customers seeking transmission service on behalf of computing-load owners or operators both embedded and incremental cost, with incremental payments credited to the utility's annual transmission revenue requirement to prevent double recovery from other customers. Non-firm service would get a lower cost.
A proposed rule would have to follow within 270 days after the revised policy statement is published in the Federal Register, and a final rule within 1 year after the proposal.
This subsection sets no MW threshold; it covers computing sites connected to the bulk-power system [47].
Sec. 2114: data. EIA would have to revise Form 861 to include load from "data center entities," no later than 90 days before the first April 1 after enactment. There is no MW threshold. [48]
Savings clause. Nothing in the title would give FERC authority over retail sales or local distribution. [49]
Sponsors and cosponsors
- H.R. 9340: Sponsored by Rep. Gabe Evans (R-CO-8). 42 cosponsors, including original cosponsor Rep. Kathy Castor (D-FL-14). [50]
- S. 5199: Sponsored by Sen. Martin Heinrich (D-NM). 2 cosponsors: Sens. Duckworth (D-IL) and Cortez Masto (D-NV). [51]
- S. 5653: Sponsored by Sen. Capito (R-WV), the Environment and Public Works chair [52]. Cosponsored by Sens. Lee (R-UT), Whitehouse (D-RI) and Heinrich (D-NM). [53]
Deadlines if enacted
- H.R. 9340: start considering within 1 year; finish and decide within 2 years (new PURPA §112(b)(9)). [54]
- S. 5199: FERC final rule within 1 year of enactment (new FPA §224(c)(1)). [55]
- S. 5653: FERC policy revision within 270 days of enactment; proposed rule within 270 days after the revised policy is published in the Federal Register; final rule within 1 year after the proposed rule (Sec. 2107(a)(3)–(4)). EIA would have to revise Form 861 no later than 90 days before the first April 1 after enactment (Sec. 2114(b)). [56]
Status and procedural history
H.R. 9340. After House passage, senators sought in September to bring the bill up in the Senate; it did not get past the motion to proceed.
- Sept 16: passed the House 417–3 under suspension of the rules (two-thirds required) [57].
- Sept 17: a unanimous-consent request to pass it drew an objection [58].
- Sept 28–30: the motion to proceed was made three times [59].
- Sept 30: a vote to limit debate on the motion to proceed was not invoked, 57–43, with three-fifths of senators (60) required [60]. The motion to proceed was then withdrawn [61].
- It remains on the Senate calendar (Cal. No. 684) [62]. No further action through Oct 22 [63].
S. 5199. Introduced July 30; referred to Senate Energy and Natural Resources [64]. A request to pass it by unanimous consent drew an objection on Sept 17 [65].
S. 5653. Introduced Sept 30; referred to Senate Energy and Natural Resources [66].
Federal cost estimates
CBO estimated H.R. 9340 (as ordered reported July 21, 2026, which is the same text the House passed) would not affect the federal budget. It would impose an intergovernmental mandate on state commissions. CBO called the costs small and well below the UMRA threshold ($107 million in 2026). It would impose no private-sector mandate [67].
As of October 22, 2026, the official bill status records list no CBO cost estimate for S. 5199 or S. 5653.
Neither the bill texts nor CBO give a household bill-savings figure.
Open questions (not settled by the official texts)
- S. 5199 network upgrades: costs are allocated to the customer but "credited back against transmission service charges." How much a large load would pay in the end would depend on the FERC rule. The net effect is not settled by the text.
- S. 5653 enforcement: new FPA §228(b)(1) bars shifting incremental cost onto other customers, while Sec. 2115(b) withholds FERC authority over retail sales and distribution. Who would enforce the floor on a state-regulated utility's retail rates? The text does not settle this.
- Which utilities would new PURPA §112(i) exempt from H.R. 9340's deadlines? The test is utility by utility: whether, before enactment, the utility's State had implemented the standard (or a comparable one) for it, its regulator (or the nonregulated utility) had conducted a proceeding to consider implementing one for it, or the State legislature had voted on implementing one for it. No official record checked for this comparison counts these utilities, so the number is not established.
- S. 5653 text may change. The official record shows no committee action beyond referral (Sept 30).
Additional legislation outside this three-bill comparison
Related Senate bill. Sen. Jon Husted (R-OH) introduced S. 5028, also titled the Ratepayer Protection Act, on July 16, 2026 (16 cosponsors; referred to Energy and Natural Resources). Its text is substantially similar to, but not identical with, the House-passed H.R. 9340. (bill status; S. 5028 as introduced)
Related House bill. H.R. 10322, Data Center Fair Share Act (Rep. Subramanyam, D-VA-10, introduced Sept 8, 2026), is listed as related to H.R. 9340 [68]. Its text is not summarized in this comparison.
A fourth approach, briefly: pause construction
The Artificial Intelligence Data Center Moratorium Act (S. 4214, Sen. Sanders, I-VT, introduced Mar 25, 2026, no cosponsors; H.R. 9442, Rep. Ocasio-Cortez, D-NY-14, introduced June 24, 2026, 20 cosponsors) is listed as an identical bill pair. It would bar starting or continuing construction or upgrades of new or existing "artificial intelligence data centers" until laws are enacted that provide for federal pre-release review of AI products, sharing AI's economic gains with workers, and conditions on post-moratorium data centers (no increase in consumer utility bills, no added climate or environmental harm, community approval, no subsidies, union jobs), and that expressly end the moratorium (Sec. 3(b)).
It would also require the Commerce Secretary to bar exports of computing hardware for use in AI data centers or large-scale AI training or deployment to countries that lack laws comparable to those the moratorium requires (Sec. 4).
It covers commonly owned or controlled facilities either used for developing or operating AI models at scale (no MW threshold), or exceeding 20 MW and designed for 20 kW or more per server rack or for liquid cooling (Sec. 3(a)). Both bills are in committee. (S. 4214 text; H.R. 9442 text; bill status for S. 4214 and H.R. 9442)
Attributed statements (not findings about bill effects)
These are senators' floor remarks, quoted from the Congressional Record.
- Sen. Husted (R-OH) said H.R. 9340 "would require State utility regulators to consider standards" so large loads pay the full incremental costs, and called it "pro-growth and pro-innovation." [69]
- Sen. Heinrich (D-NM), sponsor of S. 5199 and a cosponsor of S. 5653, said on Sept 17 that "it is not enough for us to tell States to consider making data centers pay for grid updates" [70]. On Sept 30, opposing the motion to proceed, he called H.R. 9340 "nothing more than a messaging bill on the eve of an election" [71].
- Sen. Moreno (R-OH) said of S. 5199: "the last thing we need is a new Federal interconnection queue," and called its FERC rulemaking route "bureaucratic nonsense." [72]
Official source guide
Expand a document to see its official link and cited passages. “Reference” numbers identify citations on this page; “Within the document” identifies bill sections or record pages. Official links open in a new tab.
S. 5199 · Introduced bill text
S. 5199 · Introduced bill text ↗- Reference 1Within the document: new FPA §224(b)–(c)
- Reference 5Within the document: Sec. 2(a), new FPA §224(a)(3)
- Reference 11Within the document: new FPA §224(b)
- Reference 12Within the document: §224(d)(2)(B)
- Reference 13Within the document: §224(d)(2)(C)
- Reference 14Within the document: §224(d)(3)
- Reference 15Within the document: §224(f)(2)
- Reference 31Within the document: Sec. 2(a), new FPA §224(b)–(c)
- Reference 32Within the document: §224(d)(2)(B)
- Reference 33Within the document: §224(d)(2)(C)
- Reference 34Within the document: §224(d)(3)
- Reference 35Within the document: §224(d)(1), (d)(4)
- Reference 36Within the document: §224(a)(3)
- Reference 37Within the document: §224(f)(2)
- Reference 38Within the document: §224(b)(3)
- Reference 55Within the document: bill text
S. 5653 · Introduced bill text
S. 5653 · Introduced bill text ↗- Reference 2Within the document: new FPA §228
- Reference 3Within the document: §228(a)(5)
- Reference 6Within the document: Sec. 2107(b), new FPA §228(a)(2)–(3)
- Reference 7Within the document: Sec. 2107(a)(1)–(4)
- Reference 8Within the document: Sec. 2114
- Reference 16Within the document: §228(b)(1), (e)
- Reference 17Within the document: §228(b)(3)
- Reference 18Within the document: §228(b)(4)
- Reference 19Within the document: §228(b)
- Reference 20Within the document: §228(c)
- Reference 21Within the document: §228(f)
- Reference 22Within the document: Sec. 2107(a)(3)(A)
- Reference 23Within the document: Sec. 2114(b)
- Reference 39Within the document: bill text
- Reference 40Within the document: new FPA §228
- Reference 41Within the document: §228(a)(2)–(3)
- Reference 42Within the document: §228(a)(5), (b)(1)
- Reference 43Within the document: §228(b)(3)–(4)
- Reference 44Within the document: §228(b)(2), (c)–(d)
- Reference 45Within the document: §228(e)(2)
- Reference 46Within the document: §228(f)
- Reference 47Within the document: Sec. 2107(a)(1)–(4)
- Reference 48Within the document: Sec. 2114
- Reference 49Within the document: Sec. 2115(b)
- Reference 56Within the document: bill text
H.R. 9340 · House-passed bill text
H.R. 9340 · House-passed bill text ↗- Reference 4Within the document: Sec. 2(a), new PURPA §111(d)(22)(C)
- Reference 9Within the document: new PURPA §111(d)(22)(A)–(B)
- Reference 10Within the document: new PURPA §112(i)
- Reference 25Within the document: Sec. 2(a), new PURPA §111(d)(22)(A)–(B)
- Reference 27Within the document: Sec. 2(b)(1), new PURPA §112(b)(9)
- Reference 28Within the document: new PURPA §111(d)(22)(C)
- Reference 29Within the document: new PURPA §112(i)
- Reference 30Within the document: new PURPA §112(i)
- Reference 54Within the document: bill text
H.R. 9340 · Senate calendar text
H.R. 9340 · Senate calendar text ↗- Reference 24Within the document: PCS
- Reference 62Within the document: PCS
U.S. Code · Existing PURPA law (2024)
U.S. Code · Existing PURPA law (2024) ↗- Reference 26Within the document: 16 U.S.C. 2621(a)–(c), 2024 ed.
H.R. 9340 · Status record (XML)
H.R. 9340 · Status record (XML) ↗- Reference 50Within the document: bill status
- Reference 59Within the document: bill status
- Reference 63Within the document: bill status
S. 5199 · Status record (XML)
S. 5199 · Status record (XML) ↗- Reference 51Within the document: bill status
- Reference 64Within the document: bill status
Senate committee membership (XML)
Senate committee membership (XML) ↗- Reference 52Within the document: committee membership
S. 5653 · Status record (XML)
S. 5653 · Status record (XML) ↗- Reference 53Within the document: bill status
- Reference 66Within the document: bill status
House vote 312 · H.R. 9340
House vote 312 · H.R. 9340 ↗- Reference 57Within the document: House Roll Call 312
Congressional Record · September 17
Congressional Record · September 17 ↗- Reference 58Within the document: Cong. Rec. S4775–S4776
- Reference 65Within the document: Cong. Rec. S4775–S4776
- Reference 69Within the document: Cong. Rec. S4775
- Reference 70Within the document: Cong. Rec. S4776
- Reference 72Within the document: Cong. Rec. S4776
Senate vote 254 · H.R. 9340
Senate vote 254 · H.R. 9340 ↗- Reference 60Within the document: Senate Roll Call 254
Congressional Record · September 30, S5241
Congressional Record · September 30, S5241 ↗- Reference 61Within the document: Cong. Rec. S5241
House Report 119-814 · Includes CBO estimate
House Report 119-814 · Includes CBO estimate ↗- Reference 67Within the document: H. Rept. 119-814, CBO estimate, pp. 9–10
H.R. 10322 · Status record (XML)
H.R. 10322 · Status record (XML) ↗- Reference 68Within the document: bill status
Congressional Record · September 30, S5198
Congressional Record · September 30, S5198 ↗- Reference 71Within the document: Cong. Rec. S5198
Want more explanations like this? Subscribe to Political Oversight Weekly.