
Where the Ratepayer Protection Act stands in the Senate
The bill is stuck at the first step in the Senate: a motion to start debate on it got 57 votes on September 30, 2026, and needed 60. Senators voted on "cloture on the motion to proceed" to H.R. 9340. Cloture is a vote to cut off debate, and this one decided whether the Senate would start debating the bill at all.
A cloture motion needs 3/5 of the Senate, which is 60 of 100 senators. This one got 57 yeas and 43 nays and was rejected.
This was not a vote on the bill itself. Because the motion failed, the Senate did not begin floor consideration of the bill.
The roll call (Vote 254) shows every Republican voting yea. Four Democrats joined them: Hassan, Klobuchar, Ossoff and Warnock. All other Democrats and both Independents, King and Sanders, voted nay.
A faster route had already been tried. According to McGuireWoods Consulting (MWC), Republican leadership asked on September 17 to pass the House bill by unanimous consent. That request succeeds only if no senator objects, and MWC says Senator Heinrich of New Mexico objected.
| Date (2026) | What happened |
|---|---|
| June 18 | Rep. Evans of Colorado and Rep. Castor of Florida introduce the bill; it goes to the House Energy and Commerce Committee |
| July 21 | The committee forwards it to the full House, as amended, 52-0 |
| September 10 | The committee report is filed, according to Legis1 |
| September 16 | The House passes the bill 417-3, according to the sponsors and the committee |
| September 17 | The unanimous consent request in the Senate is blocked, according to MWC |
| September 24 | The bill is placed on the Senate Legislative Calendar as Calendar No. 684, according to Legis1 |
| September 30 | The Senate rejects cloture on the motion to proceed, 57-43 |
"Vote Date: September 30, 2026, 12:51 PM"/"Required For Majority: 3/5"/"Vote Result: Cloture on the Motion to Proceed Rejected"/"YEAs 57"/"NAYs 43"— from the Senate roll call recordView official source →
"applauded House passage of H.R. 9340, the Ratepayer Protection Act, by a vote of 417 to 3."— from the committee's press releaseView official source →
"Republican leadership sought expedited passage by unanimous consent on Sept. 17, but the effort was blocked by an objection from Sen. Martin Heinrich, D-NM."— from the MWC blog postView official source →
"It was formally reported as H. Rept. 119-814 on Sept. 10"/"The Senate received the measure the following day and, after two readings, placed it on the Senate Legislative Calendar under General Orders as Calendar No. 684 on Sept. 24."— from the Legis1 articleView official source →
"H.R. 9340, the Ratepayer Protection Act, was forwarded to the Full House, as amended, by a roll call vote of 52 yeas - 0 nays."— from the committee's vote summaryView official source →
What the standard says about data center electricity costs
The bill's standard says that when a utility has to build more grid for a very large customer, the rates charged to that customer must be designed to recover the full cost. Picture a utility asked to build a new substation for a data center campus. If the company cancels the project a few years later, the substation is already built and its cost could fall on the remaining households through their rates, and the standard is written to prevent that.
The bill works by amending Section 111(d) of the Public Utility Regulatory Policies Act of 1978 (PURPA), a federal law under which state regulators must consider standards that Congress sets. It adds a paragraph (22) with three parts. “What paragraph (22) requires” follows the bill as introduced on June 18.
What paragraph (22) requires
| Provision | What it does |
|---|---|
| Full incremental cost | Rates charged to a large-load customer must be designed to recover the full, incremental cost of any generation, transmission, or distribution upgrade needed to serve that load |
| Financial assurances | Before building the upgrade, the utility must require assurances or contributions from the customer covering its cost |
| Who is covered | A non-residential consumer with 100 MW or more of aggregate peak demand at one site or campus |
In plain terms, a large-load customer is a very large power user. The end of the first row matters most: recovery applies even if the customer terminates the contract or stops buying power. That keeps the upgrade cost with the customer the upgrade was built to serve.
The committee changed the scope after introduction. NACo reports that Energy and Commerce members amended the bill to target data centers more narrowly, whereas the introduced text covered any non-residential customer at the 100 MW line. “What paragraph (22) requires” therefore describes the introduced text, not the amended one.
"A rate charged, or entered into, by an electric utility for providing electric service to a large-load customer shall be designed to recover from the large-load customer the full, incremental cost of any generation, transmission, or distribution upgrade necessary to serve the load of such large-load customer, including in the event of such large-load customer terminating a contract or other agreement with the electric utility pertaining to the sale of electric energy, or otherwise ceasing the purchase of electric energy from the electric utility."/"Before making any generation, transmission, or distribution upgrade that is necessary to serve the load of a large-load customer, an electric utility shall require the large-load customer provide to the electric utility financial assurances or contributions to cover the cost of such upgrade."/"Mr. Evans of Colorado (for himself and Ms. Castor of Florida) introduced the following bill; which was referred to the Committee on Energy and Commerce" (June 18, 2026)— from the bill as introduced, on Congress.govView official source →
"This vote comes after E&C members amended the legislation to more narrowly target data centers."/"Originally, the legislation applied to projects with a peak electricity demand of 100 megawatts or more."— from the NACo articleView official source →
Why states can still decline the standard
A state does not have to adopt the standard. Section 112 tells each state regulator to hold a proceeding on a PURPA standard and reach a determination. The bill as introduced sets one year to start that proceeding and two years to finish it.
A determination is not an adoption: PURPA Section 111(a) says nothing in it prevents a state authority from deciding that a standard is not appropriate to implement under its own state law. A commission can run the full proceeding and say no. Utilities outside state ratemaking jurisdiction carry the same duty themselves.
An exemption can also remove the duty before it starts under the introduced text. Sections 112(b) and (c) do not apply to a utility whose State acted before enactment, by implementing the standard or a comparable one, holding a proceeding on it, or voting on it in the legislature. The test is applied to each electric utility in a State, not to the State as a whole.
"Not later than 1 year after the date of enactment of this paragraph, each State regulatory authority (with respect to each electric utility for which the State has ratemaking authority) and each nonregulated electric utility shall commence consideration under section 111, or set a hearing date for consideration, with respect to the standard established by paragraph (22) of section 111(d)."/"Subsections (b) and (c) shall not apply to the standard established by paragraph (22) of section 111(d) in the case of any electric utility in a State if, before the date of enactment of this subsection—"/"(1) the State has implemented for the electric utility the standard (or a comparable standard);"/"(2) the State regulatory authority for the State or the relevant nonregulated electric utility has conducted a proceeding to consider implementation of the standard (or a comparable standard) for the electric utility; or"/"(3) the State legislature has voted on the implementation of the standard (or a comparable standard) for the electric utility."— from the bill as introduced, on Congress.govView official source →
"Nothing in this subsection prohibits any State regulatory authority or nonregulated electric utility from making any determination that it is not appropriate to implement any such standard, pursuant to its authority under otherwise applicable State law."— from the United States Code on GPOView official source →
Who pays for data center power: the sponsors and the objection
The committee says the bill would have state regulators consider making data centers pay their own way, while Senator Heinrich objects, according to MWC, that leaving it to states is not enough. Representatives Evans of Colorado and Castor of Florida introduced the bill together. The committee forwarded it 52-0, and the House passed it 417-3.
Subcommittee Chairman Latta pointed out that numerous states, Ohio among them, already have large-load tariffs for data centers. That bears on the exemption above, which can lift the duty where a state has already acted. Chairman Guthrie tied the bill to protecting Americans from rising electricity costs while positioning the United States to win the race for AI dominance.
MWC reports that Sen. Heinrich argued that the state-led approach does not go far enough, and that he backs his own GRID Savings Act, which would set stronger federal requirements on large electricity users. The Georgia Municipal Association's summary describes a similar criticism: critics call the standards voluntary rather than mandatory, and argue they may duplicate policies already in place in some states.
"Numerous states already have large load tariffs in place for data centers, including Ohio. I urge the House to bring the Ratepayer Protection Act to the floor as soon as possible so we can get this commonsense legislation across the finish line." (Chairman Latta)/"Thank you to Congressman Gabe Evans for leading this vital legislation that will protect Americans from rising electricity costs while ensuring the United States is positioned to win the race for AI dominance." (Chairman Guthrie)— from the committee's press releaseView official source →
"Heinrich has argued that the state-led approach does not go far enough to protect ratepayers and has instead backed his own Guarding Ratepayers from Increased Demand‑costs (GRID) Savings Act, which would impose stronger federal requirements on large electricity users."— from the MWC blog postView official source →
"Critics argue the bill falls short because its standards are voluntary rather than mandatory, and may duplicate policies already in place in some states."— from the Georgia Municipal Association articleView official source →
What to watch next after the failed Senate vote
The next step is Senate passage, which has not started. A bill becomes law only after the Senate passes it and the president signs it. As of the September 30 vote, the Senate had not begun floor debate on this one.
MWC wrote that further action was unlikely until after the November midterm elections. It noted that the Senate is scheduled to return on November 9, when the chamber could take up the bill in the regular way or try unanimous consent again. That is MWC's outlook, not a schedule the Senate has announced for this bill.
The White House Ratepayer Protection Pledge is a separate matter from H.R. 9340. It is a voluntary commitment by data center and technology companies. Another bill, on shutting down AI systems, is covered in AI Kill Switch Act: DHS Shutdown Power and Scope.
"further action is not likely until after the November midterm elections. The Senate is scheduled to return to regular session on Nov. 9, at which time the chamber could still take up the legislation through the regular legislative process or revisit an agreement to advance it by unanimous consent."— from the MWC blog postView official source →
"It would still need Senate approval and the president's signature to become law."— from the Legis1 articleView official source →
FAQ
- Did the Senate vote down the Ratepayer Protection Act?
- No. On September 30 the Senate voted on a motion to end debate on the question of taking up the bill, and the motion was rejected 57-43 because it needed 3/5 of the Senate. That vote was not on passing the bill. It only meant the Senate did not begin floor consideration.
- Does the bill force states to make data centers pay?
- No. As introduced, the bill adds the standard to PURPA and obligates each state regulatory authority to run a proceeding about it, beginning within one year of enactment and finishing within two. PURPA itself preserves the right to end that proceeding by determining the standard is not appropriate to implement.
- What counts as a large-load customer?
- In the bill as introduced, it is a non-residential electricity consumer that signs, or asks to sign, a power contract for one or more facilities with 100 megawatts or more of peak demand in aggregate at a single site or campus. The aggregation matters: a campus of smaller buildings can cross the line together. The committee later amended the bill to focus on data centers.



