After FERC Order No. 917
The most significant overhaul of FERC’s Electric Quarterly Report in over two decades is here. Here’s what changed, why it matters, and how to stay ahead of it.
On March 19, 2026, the Federal Energy Regulatory Commission issued Order No. 917, the long-awaited final rule that overhauls the Electric Quarterly Report (EQR) filing process. After nearly three years of engaging stakeholders, holding technical conferences, and gathering industry feedback, FERC has made its most significant changes to EQR reporting since Order 2001 established the mechanism in 2002.
For CFOs, Controllers, FERC Analysts, and Compliance Managers at utilities, independent power producers, and RTO/ISO market participants, this is more than just a routine regulatory update. It fundamentally changes how to file, what format to use, and when to have data ready. The shift to an XBRL-CSV-based reporting system introduces technology needs that many organizations are not ready yet.
This post explains what led to the reform, what Order No. 917 requires, and how modern cloud-based compliance solutions, particularly those already XBRL-ready, can help your organization adapt to the new mandate without interruptions.
20+Years since last major EQR overhaul | 3 yrsFERC stakeholder engagement before Order 917 | May 262026 effective date | XBRL-CSVNew mandatory filing standard |
What Brought the Change: Why the Old EQR System Broke Down
The EQR has been FERC’s main tool for public utilities to meet their obligations under Sections 205 and 220 of the Federal Power Act, keeping rates, terms, and conditions in a public format. It worked well for over two decades, but the energy market it served has changed dramatically. The rise of RTO and ISO-administered markets brought complex, multi-party transaction structures that the original XML-based filing system could not handle. Data inconsistencies grew. Sellers often had to resubmit filings multiple times to fix errors that the existing system could not catch until after submission. As FERC noted in the final rule, the old framework was “not equipped to handle” the complexity that modern wholesale power markets generate.
Three key problems led FERC to act:
- Data quality issues: Inconsistent field definitions and submission formats created an unreliable data environment that weakened FERC’s ability to monitor market behavior.
- Technical limits: The XML-based system had no pre-submission error checks, leading to repeated refilings and heavy compliance team workloads.
- Market growth outpacing infrastructure: The expansion of RTO/ISO markets meant that individual sellers depended on data from independent system operators, data that the old system couldn’t integrate effectively.
The Three Changes That Will Reshape Your Filing Process
1. XBRL-CSV Becomes the Mandatory Filing Standard
This is the big change. FERC is replacing the current XML submission format with an XBRL-CSV-based reporting system. The new system will rely on EQR taxonomies and validation rules published by FERC, allowing sellers to catch errors before submission instead of after repeated rejections.
FERC will provide pre-formatted XBRL-CSV templates for sellers who prefer not to create their own submission systems. These templates are designed to maintain a familiar, spreadsheet-like workflow while ensuring compliance with XBRL formatting rules.
Not familiar with the XBRL-CSV format? Read our explainer: Improvements to the Open Information Model: xBRL-CSV and xBRL-JSON Explained
TECHNOLOGY READINESS WARNING
FERC has issued the final rule before the new XBRL-CSV system is fully developed. Sellers must coordinate with software vendors now. Organisations using legacy XML-only solutions or manual processes will face a hard technology transition with limited lead time.
2. Extended Filing Deadlines, But Only After Full Implementation
In response to widespread industry feedback, particularly from sellers in ISO/RTO markets who needed more time for resettlement data to be finalized, FERC has extended EQR filing deadlines to four months after the close of each quarter, from 30 days. The new schedule:
| Quarter | Reporting Period | Current Deadline | New Deadline |
| Q1 | Jan 1 – Mar 31 | April 30 | July 31 |
| Q2 | Apr 1 – Jun 30 | July 31 | October 31 |
| Q3 | Jul 1 – Sep 30 | October 31 | January 31 |
| Q4 | Oct 1 – Dec 31 | January 31 | April 30 |
Note: these new deadlines will only take effect once the XBRL-CSV system transition is complete. Implementation is expected to roll out over the following 12 to 24 months from the effective date May 2026.
3. RTO/ISO Transaction Data Becomes the Authoritative Source
Order No. 917 requires RTOs and ISOs to generate EQR transaction data reports for market participants, aligned with FERC’s XBRL-CSV taxonomies. This change impacts sellers working in organized markets: ISO-provided data will be the standard reference for EQR transaction filings.
Sellers that used to rely on internal data checks against ISO settlement statements now face a new data governance challenge: how to ensure accuracy and audit readiness when the main data source is held by the RTO.
Read about the full revisions here: Order No. 917: Final Rule
The CFO’s New Mandate: Data Integrity Is Now a C-Suite Responsibility
There is a larger shift happening, with the EQR reform being a clear example. The CFO role has evolved fundamentally. Today’s energy finance leader is responsible for more than just closing the books and managing costs. They are stewards of enterprise data integrity, regulatory risk, and reporting accuracy, responsibilities that can have serious consequences if the compliance systems do not keep up with regulatory changes.
85%
of organisations globally report that compliance requirements have become more complex in the past three years
Source: PwC 2025 Global Compliance Survey
For FERC-regulated entities, this complexity is now clearly defined and formalized in Order No. 917. The CFO’s mandate now includes:
- Technology governance: Making sure the organization’s filing system can shift to XBRL-CSV on time, without breaks in the quarterly submission cycle.
- Data integrity: Creating a single source of truth that can match internal records against RTO/ISO transaction data reports, every quarter, at scale.
- Risk identification: Using pre-submission checks not just to avoid rejections but to find data quality issues before they lead to significant errors that require refilings.
- Materiality judgement: Under the new refiling policy, sellers must use “reasonable judgement” on what qualifies as a material error. This is both a compliance and financial governance issue, not just an operational one.
Regulatory expectations continue to tighten, with increased scrutiny around disclosure timelines, data protection, and governance practices. These are not abstract technology issues, they are financial realities that now sit squarely within the modern CFO’s remit.
Organizations that manage Order No. 917 with the least friction will be those where the CFO has already invested in compliance systems that expose data issues early, keep an auditable record of changes, and can adjust to changing taxonomy and validation requirements without extensive manual work.
The Hidden Risks of Manual and Legacy Filing Approaches
Many FERC filers still depend on a mix of spreadsheets, manual data processing, and outdated XML-based filing software. While this has worked for the current EQR system, it has been inefficient. Under Order No. 917, it poses a significant risk.
What Manual Processes Can No Longer Absorb
- XBRL-CSV formatting errors undetected until post-submission
- Taxonomy updates requiring manual template revisions
- RTO/ISO data reconciliation without audit trail
- No version comparison across reporting periods
- Multi-entity filing without role-based access controls
- Inability to filter and navigate thousands of validation results
Consider the implications for refiling. The 12-quarter lookback period remains in Order No. 917. A data quality problem found today could need corrected submissions going back three full years. In a manual process, identifying the scope, fixing the data, and resubmitting accurately, while keeping a proper record of notes that explain the error, takes significant resources.
For a deeper look at why compliance depends on speed and data governance, see: FERC XBRL Reporting — Data Validation & Granular Audit Trail
Why XBRL Readiness Is Now a Competitive Compliance Advantage
XBRL is not new. FERC began using XBRL for financial reporting in 2021, and it has been mandatory for SEC filings for over ten years. But changing the EQR, the most high-volume, operationally intense FERC filing requirement, to XBRL-CSV marks a critical moment.
Organizations that already have an XBRL-native platform will have considerable advantages during this transition. Those without one will face a technology gap that must be closed under tight deadlines.
This distinction is more important than it might seem. Building XBRL capability from scratch or adding it to an outdated system requires taxonomy expertise, managing validation rules, and ongoing updates as FERC refines the EQR taxonomy after implementation. These are not one-time tasks; they are continuous operational requirements that the right platform should handle automatically.
WHAT XBRL-READY LOOKS LIKE IN PRACTICE: A CHECKLIST
- Pre-submission validation against FERC EQR taxonomies
- Automatic taxonomy and validation rule updates without manual installation
- Direct FERC portal submission from within the platform
- Audit trail at the data point level with user and timestamp
- Version comparison across quarters
- Role-based access for multi-user review workflows
How DataTracks Glacier Is Built for Exactly This Moment
DataTracks Glacier is a purpose-built, cloud-based FERC reporting platform designed around the XBRL filing requirements that Order No. 917 now mandates for all EQR submissions. It is not a general-purpose compliance tool adapted for FERC, it was built specifically for the operational reality of FERC reporting: high data volumes, template-driven workflows, and the need for comprehensive validation before submission.
XBRL-Native Architecture Glacier’s Data Point Model (DPM) generates validated XBRL-CSV output natively. Taxonomies and validation rules update automatically as FERC releases new versions, no manual installation required. | Full Data-Point Audit Trail Every data change is captured at the cell level with user, date, and timestamp. The log is exportable, critical for refiling notes and regulatory review under Order No. 917. |
Spreadsheet-Native Workflow The interface mirrors the structure of FERC templates, familiar to analysts already working in Excel, enabling rapid adoption without a lengthy platform learning curve. | Version Compare Compare two versions of the same period, or across reporting periods, to identify and validate corrections before submission. Essential for managing the 12-quarter lookback. |
Comprehensive Validation Engine Glacier processes 5,000+ FERC validation rules and displays results inline. Users filter, search, and navigate directly to the relevant template from any error result. | Direct FERC Portal Submission Authorised users connect to the FERC portal from within Glacier and submit XBRL reports without exporting or manually uploading files, preserving data integrity through the entire filing chain. |
What Modern Compliance Looks Like Under Order No. 917
Cloud-based compliance platforms have shifted from being an “emerging option” to being the “operational baseline” for regulatory filing teams. The reasons for this change are now structural rather than aspirational:
- Regulatory speed: FERC’s implementation of Order No. 917 will involve continual taxonomy and validation rule updates after the effective date. Cloud-hosted platforms updates automatically, while on-premise or old tools require manual installations that slow down readiness.
- Multi-user workflows: Preparing the EQR involves data analysts, compliance managers, and senior reviewers across different roles. Role-based cloud access avoids the version control issues that trouble spreadsheet-based handoffs.
- Scalability: FERC-regulated entities often manage filings for multiple reporting entities. A scalable cloud setup can handle volume without needing extra infrastructure investment.
- Security and availability: ISO 27001:2022-certified cloud hosting offers the security measures and high availability that quarterly regulatory deadlines require, without depending on internal IT support.
64%
of CEOs say the regulatory environment is a barrier to value creation
Source: PwC 27th Global CEO Survey
See also: Understanding XBRL for Regulatory Filing — A Complete Guide
Five Actions Finance and Compliance Leaders Should Take Now
Order No. 917 is effective May 26, 2026. The XBRL-CSV system transition will follow over the subsequent 12–24 months. The window to prepare is open, but it will close faster than it appears.
01 | Audit your current EQR filing technology Determine whether your current solution supports XBRL-CSV output natively or requires an upgrade. If your vendor has not communicated a transition plan for Order No. 917, that is a signal worth acting on. |
02 | Establish your RTO/ISO data reconciliation workflow Under the new rules, ISO/RTO-sourced transaction data becomes authoritative. Map how your internal records align with RTO settlement data and identify any reconciliation gaps before they become refiling triggers. |
03 | Review your materiality and refiling policy Order No. 917 requires a materiality judgement for refilings, along with a written note explaining the error. Establish internal guidelines so your team can apply a consistent standard before FERC asks the question. |
04 | Engage your CFO in the technology decision This is not solely a compliance team project. The CFO’s accountability for data integrity, audit readiness, and regulatory risk makes them the right executive sponsor for the EQR platform transition. |
05 | Monitor FERC’s taxonomy and guidance releases FERC will convene technical conferences and publish draft taxonomies before the XBRL-CSV system goes live. Your compliance platform should incorporate these updates automatically, if yours does not, factor that into your vendor evaluation. |
The Bottom Line
FERC Order No. 917 is not a compliance inconvenience. It is a structural shift in how the energy sector’s financial data flows to regulators, and it arrives at a moment when the expectations of CFOs and compliance leaders are already at their highest point in a generation. The transition to XBRL-CSV is both a technical migration and an opportunity: organisations that invest in the right infrastructure will file more accurately, audit more cleanly, and carry significantly less refile risk over the 12-quarter lookback window.
Platforms that are already XBRL-native, and built specifically for the template-driven, high-volume reality of FERC reporting, are positioned to absorb this transition without disruption. Organisations still relying on legacy approaches will face a harder path, under more time pressure than they may currently appreciate.
The question for every CFO and compliance leader responsible for EQR filings is a simple one: is your filing infrastructure ready for May 2026, or are you building that readiness under deadline?
See DataTracks Glacier in Action
Purpose-built for FERC reporting. XBRL-native from day one. Ready for Order No. 917. Talk to a FERC compliance specialist about your transition requirements.
