Resources 
Frequently Asked Questions (FAQs)
Electric Quarterly Reports (EQRs) for 3rd Quarter 2013 and Beyond
This Frequently Asked Questions document is provided by FERC staff and is meant to assist the public in complying with the requirements set forth in Order Nos. 768, 768-A, and 770 for EQRs to be filed for the third quarter of 2013 and later. Additional questions and answers may be added from time to time.
Will the EQR system accommodate sellers who changed their name during the filing quarter? (As of 09/29/2015)
Yes. The EQR System now allows quarter over quarter Name Changes validated against Company Registration, as well as mid-quarter Name Change (more than one Seller name per quarter) validated against Company Registration. Filers will be able to file for Seller Company Names active during that quarter in the Company Registration system.
Filing under multiple seller names is optional. Filers still have the choice of reporting the EQR only under the Seller name that is active at the end of the quarter.
Filing under multiple seller names is optional. Filers still have the choice of reporting the EQR only under the Seller name that is active at the end of the quarter.
How do I retrieve historical EQR data on a company if I don’t know the current or the previous name of a company in the EQR Report Viewer? (As of 09/29/2015)
Users now have the ability to search by Company Unique Identifier (CID) and Seller Company name within the EQR Report Viewer. Please see FERC’s Company Identifier 
section for the Seller’s CID.
section for the Seller’s CID.
How do I file the EQR for sellers with name changes during the quarter? (As of 09/29/2015)
Field No. 1 (FA1) must be the agent that is active at the date of the filing. Field No. 2 (Company Name) must be the active name of the Seller at the end of the filing quarter. Field Nos. 16 and 46 (Seller Company Name) can contain one or all the names of the Seller that were active during the quarter in the Company Registration system.
In the EQR User Interface, the Seller Page now contains options for the Seller Name to be used in that quarter’s filing. While filing using the CSV upload option, the filer has the option to file contracts and transactions associated with one or all Seller names active during that quarter. For filing using XML, please see the XML schema.
In the EQR User Interface, the Seller Page now contains options for the Seller Name to be used in that quarter’s filing. While filing using the CSV upload option, the filer has the option to file contracts and transactions associated with one or all Seller names active during that quarter. For filing using XML, please see the XML schema.
Will validation F.21.2.1 change with the EQR 3.3 release? (As of 09/29/2015)
No. Each contract must still be linked to a valid Seller. When filing using multiple Seller Company names, each contract must be linked to a valid Seller Company Name active during that quarter.
What is the EQR filing schedule? (As of 07/23/2013)
EQRs should be filed within a month after the end of a calendar quarter. (Source: 18 CFR § 35.10b)
- For the first quarter, from January 1 through March 31, file by April 30;
- For the second quarter, from April 1 through June 30, file by July 31;
- For the third quarter, July 1 through September 30, file by October 31; and
- For the fourth quarter, October 1 through December 31, file by January 31.
How do I request an EQR filing extension? (As of 07/23/2013)
Extension requests should cite the EQR docket number ER02-2001-000 and must be received by FERC prior to the EQR filing deadline to facilitate timely consideration. Extension requests must be in the form of a letter and include the current date, the docket number, the name of the company requesting an extension, a contact name and telephone number, and the proposed date by which the company will file the EQR. The request must clearly state the reason for which the extension is necessary and must be received by FERC prior to the EQR filing deadline. (Source: 18 CFR 385.2008(a), 18 CFR 385.212).
Extensions may be requested (a Procedural Motion) by using eFiling. The eFiling procedures can be found at http:www.ferc.gov/docs-filing/eqr/soft-tools.asp.
Extensions may be requested (a Procedural Motion) by using eFiling. The eFiling procedures can be found at http:www.ferc.gov/docs-filing/eqr/soft-tools.asp.
Can I file a letter or make an eFiling to FERC, including my EQR report, instead of using the EQR electronic process? (As of 07/23/2013)
No, Sellers (or their designated Agents) are required to file EQR reports electronically through the Commission’s website. (Source: Order No. 2001).
How long must records pertaining to EQR filings be maintained? (As of 07/23/2013)
Contracts must be retained and be available upon request. (Source: 18 CFR 35.1(g)) Transaction information (all data and information upon which an entity billed the prices it charged for electric energy or electric energy products it sold as well as the prices it reported to price indices) must be retained for five years. (Source: 18 CFR 35.41(d)).
What happens if a company is not in compliance? (As of 07/23/2013)
A non-compliant public utility is subject to Commission enforcement actions, which include civil penalties, revocation of market-based rate authority, or refunds. (Source: 16 U.S.C. § 825o-1(b)). Order No. 2001). A non-public utility is also subject to enforcement action if it fails to comply with the requirements of Order No. 768.
Will a unique EQR filing password be required that is different from the eTariff filing password within a company, or will it be shared? (Modified 12/13/2013)
Each company will have a Company Unique Identifier (CID) from the Commission’s new company registration that applies to EQR, eTariff, and other filings with the Commission. EQR filings starting with Q3 2013 require the use of a CID number and cannot be made until the Seller has registered in Company Registration. For more information, please see the FERC website section on Company Registration.
Our company has two Company IDs or CIDs – (1) the Company ID noted in an email we receive as an automatic response from FERC Forms Server confirming that our EQR filing has been received; and (2) the CID issued to use for the e-filing system. Which do we use? (Modified 12/13/2013)
For the new filing system, the Company Identifier will be a 6-digit integer preceded by the letter “C” obtained through the Commission’s Company Registration system and should be the same CID used for the e-filing system including eTariff.
Does the Agent need a Company Identifier or a Delegated Identifier? (Modified 12/13/2013)
The Agent may have a Delegated Identifier (DID) obtained through FERC’s Company Registration system. The Agent will need to have Seller’sauthorization within the FERC eRegistration system to be able to file on behalf of the Seller. The Seller is required to obtain a Company Identifier through FERC’s Company Registration system. For more information, please see the FERC website section on Company Registration.
Using the new EQR filing application, will a Seller be able to populate EQR data from multiple geographical locations? (As of 07/23/2013)
The EQR application can be accessed from multiple locations and by multiple Agents; however, only one eRegistered individual may view, append data, or edit the working copy of the EQR file for a specific Seller and quarter at any one time. Once an Agent has clicked on the Seller to view working data, all others are locked out until he/she exits. A Seller representative (or their designated Agent) can exit the session by logging out of the application, timing out, or filing the data with FERC. Once the Seller representative (or their designated Agent) exits, any other Seller representative (or their designated Agent) with access to that EQR can view the current working data.
If nothing changes in one of the files, can that file be carried forward? (Added 12/13/2013)
The “Prefill” option will copy data from the previous quarter in the user interface from last filing period; however, uploading CSV files will require manual changing of the filing quarter and re-upload each time.
If transactions are not reported to an index price publisher, is an Index Publisher file required to be filed even though it would be blank? (Added 12/13/2013)
No.
If a CSV file is uploaded but not filed and the system is logged out, how do I see my data? What function is utilized to revise the file? (Added 12/13/2013)
Once uploaded, data remains in the EQR system until filed. To access data uploaded before filing, a Seller contact or designee will need to log back in and select “Manual Edit” to update or file the data. (Note: Once filing is made, a date-time stamp will appear in the “Last Action Date” column.)
If a CSV file is uploaded but not filed and the system is logged out, how do I replace a previously uploaded CSV file? (Added 12/13/2013)
Once uploaded, data remains in the EQR system until filed. To replace uploaded data before filing, a Seller contact or designee will need to log back in and select “CSV New” to upload revised CSV data files. (Note: Once filing is made, a date-time stamp will appear in the “Last Action Date” column.)
If a CSV file is uploaded and filed before logging out, what should be selected in order to replace the data already filed? (Added 12/13/2013)
Select “CSV Replace.” Note: if there is not a date-time stamp in the “Last Action Date” column, then the filing was not received by FERC.
If a CSV file is uploaded and filed before logging out, what should be selected in order to edit the data already filed? (Added 12/13/2013)
Select “Manual Edit.” Note: if there is not a date-time stamp in the “Last Action Date” column, then the filing was not received by FERC.
If I find myself locked out of the EQR system because someone else is looking at the data, what can I do? (As of 07/23/2013)
If the system does not let a Seller representative (or their designated Agent) view data for filing, then that Seller representative (or their designated Agent) will receive a message stating which eRegistered user is currently viewing the data. Either a Seller (or their designated Agent) can contact the other specified eRegistered user to coordinate their work on the EQR or, if the other Seller representative (or their designated Agent) is away from his/her desk, the application will log them out automatically after the system times out after 20 minutes of non-use. (Note: After 15 minutes a pop up warning message lets users know they will be timing out unless they click the Ok button.) In the event that a Seller representative (or their designated Agent) is forcibly logged off (when the system times out), that data will be saved in its most current form.
If a non-public utility exceeds the de minimis market presence threshold but has no transactions to report for a particular quarter, does the non-public utility still need to file an EQR? (As of 07/23/2013)
Yes, at a minimum, a Seller is required to provide Identification Data every quarter even if they have no contracts or sales. Contracts and contract products are reported when sales under them begin and must continue to be reported in the EQR until they are terminated.
What sales by a non-public utility are included in the 4 million MWh market presence threshold used to determine if the utility is required to file EQRs? (As of 07/23/2013)
The threshold calculation is based on the average annual wholesale sales over the preceding three years, reported by the non-public utility as “Sales for Resale” in the Energy Information Administration (EIA) Form 861. (Source: Order No. 768 P46). EIA Form 861 instructions for Line 12 define “Sales for Resale” as the amount of electricity sold for resale purposes, including full and partial requirements customers, firm power customers, and non-firm customers. (Source: EIA, Annual Electric Power Industry Report Instructions 
).
For example, the threshold calculation should include:
).For example, the threshold calculation should include:
- Sales by a non-public utility, such as a cooperative or joint action agency, to its members. (However, these sales do not need to be reported in the EQR). (See Order No. 768 P2 and P19).
- Sales by a non--public utility under a long--term, cost-based agreement required to be made to certain customers under Federal or state statute. (However, these sales do not need to be reported in the EQR). (See Order No. 768 P2 and P19).
- Sales by a non-public utility to organized RTO/ISO markets. (These sales need to be reported in the EQR).)
What option do I choose in Company Registration for a Non-Public Utility (NPU)? (Modified 12/13/2013)
If your entity is a Non-Public Utility that is required to file an EQR but not an eTariff, you should select the public utilities with cost-based rates option. Your selection of this option is purely for the Commission’s administrative purposes and provides no indication as to how Non-Public Utilities set their rates. Please see Company Registration Manual 
.
.
How does a non-public utility populate the FERC Tariff Reference field? (As of 07/23/2013)
If the non-public utility is reporting contracts or transactions that occur outside a FERC tariff, the FERC Tariff Reference field should be populated with “NPU.”
If a non-public utility is selling ancillary services under the OATT or in connection with retail sales, how is the ancillary service sale reported in the EQR? (As of 07/23/2013)
Ancillary services that are sold under a transmission tariff are not reported in the EQR. Only ancillary services that are sold in connection with a wholesale power sale are reported in the EQR.
If a non-public utility has a formula posted on a web site, can they use a link to that site in their Rate Description field to describe the rate? (As of 12/13/2013)
Non-public utilities can provide a link to a webpage that contains a formula rate. If the webpage contains additional material, the Rate Description field must provide more detail regarding the location of the formula on the webpage. By contrast, public utilities must specify their formula rate in the EQR or reference a document in FERC’s eLibrary by Accession number. They cannot provide a link to any other webpage. (Source: Order No. 2001-H PP20-21).
Do PURPA Qualifying Facilities (QF) have to file EQRs? (Added 5/1/2014)
QFs that are required to file rates under section 205 of the Federal Power Act (FPA), 16 U.S.C. § 824d (2012), must also file EQRs, unless their sales are otherwise exempted from such requirements.
Most QF sales are likely to be sales for resale in interstate commerce, and thus would be subject to sections 205 and 206 of the FPA, 16 U.S.C. §§ 824d, 824e (2012). Such QF sales are exempt from sections 205 and 206 of the FPA, however, if they meet the criteria for exemption described in section 292.601(c)(1) of the Commission’s regulations, 18 C.F.R. § 292.601(c)(1) (2013), i.e., if they are sales from a QF 20 MW or smaller, if they are sales made pursuant to a state’s implementation of section 210 of the Public Utility Regulatory Policies Act of 1978, 16 U.S.C. § 824a-3 (2012), or if they are sales made from a contract entered into on or before March 17, 2006.1 With an exemption, such QF sales need not be reported on EQRs.
Thus, QF sales that are subject to the exemptions from sections 205 and 206 of the FPA that are listed in section 292.601(c) (1) of the Commission’s regulations do not have to be reported in EQRs. However, if the QF sales are sales for resale in interstate commerce, and if the QF sales are not subject to the exemptions, they would be subject to sections 205 and 206 of the FPA and would be reportable in EQRs.
1However, if the sales are made by a QF that is a small power production facility with a power production capacity greater than 30 MW, and if the QF uses a primary energy source other than geothermal resources, the sales and the QF are not subject to exemption from the FPA. See 18 C.F.R. § 292.601(b) (2013).
1However, if the sales are made by a QF that is a small power production facility with a power production capacity greater than 30 MW, and if the QF uses a primary energy source other than geothermal resources, the sales and the QF are not subject to exemption from the FPA. See 18 C.F.R. § 292.601(b) (2013).
Does a Seller with no contract or transaction data in a quarter need to report for that particular quarter? (Modified 12/13/2013)
Yes, at a minimum, a Seller is required to provide Identification Data every quarter even if it has no contracts or sales. Contracts and contract products are reported when sales under them begin and must continue to be reported in the EQR until they are terminated.
If an entity changes hands, which company is responsible for reporting the EQR for that quarter? (As of 07/23/2013)
Both are. Each company files the EQR for the portion of the quarter during which it owned the entity.
Do Exempt Wholesale Generators (EWG) have to file EQRs? (As of 07/23/2013)
Yes, exempt Wholesale Generators must file EQRs. The term “exempt wholesale generator” means any person engaged directly, or indirectly through one or more affiliates, and is exclusively in the business of owning or operating, or both owning and operating, all or part of one or more eligible facilities and selling electric energy at wholesale. EWGs are exempt from certain regulations implementing PUHCA 2005, but they are not exempt from FPA section 205.
May Sellers leave Trade Date (Field 53), Type of Rate (Field 55), Standardized Quantity (Field 67) and Standardized Price (Field 68) blank? (Added 04/01/2014)
Yes. The EQR system will allow these fields to be left blank. A warning message will be generated so that the Seller (or its designated Agent) can verify its intent to leave one or more of these fields blank.
Do I need to report power purchases? (As of 07/23/2013)
No, purchases are not reported. Only sales are reported in the EQR.
What should be reported in FERC Tariff Reference (Field 19) and FERC Tariff Reference (Field 48)? (As of 07/23/2013)
The Data Dictionary specifies that you may use unrestricted text (60 characters). The FERC tariff reference cites the document that specifies the terms and conditions under which a Seller is authorized to make transmission sales, power sales or sales of related jurisdictional services at cost-based rates or at market-based rates. If the sales are market-based, the tariff that is specified in the FERC order granting the Seller Market Based Rate Authority must be listed. Cost-based sales made under the WSPP Agreement should cite the WSPP tariff, and market-based sales made under the WSPP Agreement should cite the Seller’s market-based rate tariff. If a nonpublic utility does not have a FERC Tariff Reference, it should enter “NPU” for the FERC Tariff Reference.
The FERC Tariff Reference should be populated using either the tariff designation or a truncated version of the section title of the Sellers tariff document. For example, a section title using NAESB Business Names and adopted as FERC’s Business Names might include [Record Content Description]+[Tariff Record Title]+[Record Version Number]+[Option Code]. Each time a revision is made to the tariff being referenced, the FERC Tariff Reference field should be updated to reflect the updated tariff. The FERC Tariff Reference is not a docket number. If a contract refers to two tariffs, it should be identified as two separate contracts with two separate FERC Tariff References.
To look up a company’s tariff on the eTariff website, go to the eTariff homepage and enter your company’s name in the eTariff Viewer.
The FERC Tariff Reference should be populated using either the tariff designation or a truncated version of the section title of the Sellers tariff document. For example, a section title using NAESB Business Names and adopted as FERC’s Business Names might include [Record Content Description]+[Tariff Record Title]+[Record Version Number]+[Option Code]. Each time a revision is made to the tariff being referenced, the FERC Tariff Reference field should be updated to reflect the updated tariff. The FERC Tariff Reference is not a docket number. If a contract refers to two tariffs, it should be identified as two separate contracts with two separate FERC Tariff References.
To look up a company’s tariff on the eTariff website, go to the eTariff homepage and enter your company’s name in the eTariff Viewer.
We have made sales but do not have any Contracts or Contract Products. How do I report that information on the EQR? (As of 07/23/2013)
If a Seller has agreed to deliver a service or product, then the Seller has a contract, though it may be called by another name, such as a Service Agreement. Consequently, if a Seller has made power sales, then at least one Contract with at least one Contract Product must be reported in the EQR. Since the Seller has made sales, Transactions must also be report in the EQR.
What is a Contract Product? (As of 07/23/2013)
A Contract Product is the service or product that a company has agreed to provide or sell. For example, energy and capacity are Contract Products. All acceptable Contract Products are listed with check mark in the second column in Appendix A of the EQR Data Dictionary .
.
How do I report sales of Automatic Generation Control (AGC), an ancillary service? (As of 07/23/2013)
AGC is not in the EQR list of Products - Appendix A of the EQR Data Dictionary . A Seller (or their designated Agent) should use Regulation and Frequency Response as a product name for AGC.
. A Seller (or their designated Agent) should use Regulation and Frequency Response as a product name for AGC.
What product should I use for Mileage (per Order No. 755)? (As of 07/23/2013)
Mileage should be reported as Regulation & Frequency Response.
The EQR list of valid values for Contract Product Name does not include the service or product included in our contract. What should I enter in that field? (As of 07/23/2013)
A Seller (or their designated Agent) can list the product as other.
What is the definition of Booked Out Power? (As of 07/23/2013)
Booked Out Power is the offsetting of opposing buy-sell transactions at the same time and place. In other words, energy or capacity contractually committed bilaterally for delivery but not actually delivered due to some offsetting or countervailing trade. For example, if A sells 50MW of power to B, and for the same time period and location B sells 50MW of power back to A, the transactions would be booked out in their entirety and no transmission would be required. Nonetheless, the transactions must both be reported in Electric Quarterly Reports. Likewise, using the example given in Order No. 2001, if A sells 50MW to B and, for the same time period and location B sells 60MW back to A, then all of these separate transactions must be reported in Electric Quarterly Reports even though only 10MW would be transmitted to A. A would report a 50MW power sale to B, and B would report a 60MW power sale to A.
Note: Booked Out Power should never be reported in the contracts portion of the EQR. (Source: Order Nos. 2001, and 2011-E.) Offsetting transactions in RTO/ISO markets must be reported in the EQR in accordance with the Real Time/Day Ahead guidance document.
Note: Booked Out Power should never be reported in the contracts portion of the EQR. (Source: Order Nos. 2001, and 2011-E.) Offsetting transactions in RTO/ISO markets must be reported in the EQR in accordance with the Real Time/Day Ahead guidance document
.
Do I need to report virtual transactions in an RTO? (Added 08/23/2013)
No, purely financial transactions, including RTO virtual transactions, are not reported in the EQR. Consistent with the Commission’s prior precedent, contract data and transaction data on any wholesale power sales contract that provides for physical delivery must be reported by public utilities in Electric Quarterly Reports, either as delivered power or as a book out. By contrast, “purely financial transactions” need not be reported in Electric Quarterly Reports. When a power sales contract provides for physical delivery and has not been terminated prior to the commencement of service under the contract, transactions under the contract are to be reported in Electric Quarterly Reports. If such a contract is novated and replaced by a contract that does not provide for physical delivery of the power, consistent with the Commission’s precedent on this issue, the novated contract is purely financial and need not be reported in Electric Quarterly Reports. If the financial contract is re-novated to a contract that does provide for physical delivery, then transactions under the re-novated contract must be reported in Electric Quarterly Reports. Since a book out is a means to avoid physical delivery under a contract when a party appears twice in a delivery chain, see n.2 supra, it differs from a novation where a forward physical contract is terminated and replaced by a financial contract. (Source: Order No. 2001-F).
Should sales to Canada be reported in EQR? (Added 08/23/2013)
Yes, when:
-
(1) The sale originates in the United States and is delivered in the United States.
(2) The sale originates in the United States where title changes on the United States’ side of the United States-Canada border.
Should sales from Canada be reported in EQR? (Modified 08/23/2013)
Yes, when the sale originates in Canada and the title changes in the United States. (Source: Order No. 2001-G PP 64-65 regarding title transfer).
What is the naming convention for the EQR CSV files? (As of 07/23/2013)
The four CSV files should be named similar to:
-
XXXXX_ident.CSV
FEL_Q3_2013_contracts.CSV
Company_transactions.CSV
Your_Choice_indexpub.CSV
Text in bold print is mandatory.
Why am I having difficulty viewing/editing a CSV file? (Modified 12/13/2013)
Excel can cause incorrect conversion and storage of certain values in the file. CSV is a simple text file format. Therefore, only Notepad or WordPad should be used to edit and save the contents of a CSV file. One or the other is available on all Windows computers. Macs do not have Notepad specifically, but they do have a simple text editor that can save as CSV.
As an example, if you used MS Excel to enter data, excel automatically converts long numeric values into scientific values by default. Assorted reformatting issues are most common with Dates and Zip Code entries (particularly those beginning with "0") or any long numeric values. Please double check the formatting on these fields before converting to CSV and open in CSV to check that they are correctly formatted.
To edit data in Excel, changes must be made in the Excel (XLS) file, (not CSV). The Excel file is then saved and converted to CSV immediately before import. If there is a problem importing a CSV file, open the source Excel file to make changes and then re-save the Excel file in CSV format for import.
As an example, if you used MS Excel to enter data, excel automatically converts long numeric values into scientific values by default. Assorted reformatting issues are most common with Dates and Zip Code entries (particularly those beginning with "0") or any long numeric values. Please double check the formatting on these fields before converting to CSV and open in CSV to check that they are correctly formatted.
To edit data in Excel, changes must be made in the Excel (XLS) file, (not CSV). The Excel file is then saved and converted to CSV immediately before import. If there is a problem importing a CSV file, open the source Excel file to make changes and then re-save the Excel file in CSV format for import.
What can I enter into any required field when I do not have data for it? (As of 07/23/2013)
In non-numeric required fields, a Seller (or their designated Agent) can enter N/A or Other depending on the field. In required numeric fields, enter a zero. In a non-required field, leave it blank.
What is a Filer Unique Identifier (Field 1)? (Modified 08/23/2013)
Filer Unique Identifier is field number 1 in an EQR filing. It is use to identify contact information for the Seller and the Agent.
-
(1) A Filer Unique Identifier of FS# (where “#” is an integer) should be used to indicate a Seller's employee contact information.
(2) A Filer Unique Identifier of FA1 should be used to indicate the Agent contact Information. Agent may be a company employee or designated third party.
It appears that the contract file of the new system EQR Report is very similar to the file accepted in the old VFP software. Will FERC populate the new contract file with the data with the data from old files? (Modified 12/13/2013)
The format of the new (3rd-Qtr.) file is similar to the format of the current, but includes new field numbers and deletes a couple of columns as indicated in the Data Dictionary. On FERC's website, please see EQR Data Dictionary . The Seller (or their designated Agent) will need to populate the new contract file. The Seller (or their designated Agent) can use the previous quarter’s data as a starting point and make modifications to be uploaded in the new system web interface or via XML.
. The Seller (or their designated Agent) will need to populate the new contract file. The Seller (or their designated Agent) can use the previous quarter’s data as a starting point and make modifications to be uploaded in the new system web interface or via XML.
How do I report sales under the WSPP Agreement? (As of 07/23/2013)
Cost-based sales made under the WSPP Agreement should cite the WSPP tariff, and market-based sales made under the WSPP Agreement should cite the Seller’s market-based rate tariff. (Source: Order No. 2001-G 120 FERC ¶ 61,270, September 24, 2007 at P17) The Seller (or their designated Agent) will need to report the contract separately for each counterparty. The application of the WSPP contract to a given counterparty should be reported once a transaction occurs with the counterparty and should continue until the reporting company leaves the WSPP agreement or determines that it is unlikely to do a bilateral transaction with the counterparty under the WSPP. The Commencement and Execution Dates should be reported as the date that the Seller joined WSPP. (See Dec 2012 Tech Conference for RM10-12).
Why am I getting a date/time error when I file my contracts through EQR? (As of 07/23/2013)
One reason for a date/time error is the use of the characters N/A in the Begin Date and End Date (Fields 43 and 44) numeric fields of the contract product portion of the template. This is an error. If there is no data, leave them blank. The system is looking for a date and time in the YYYYMMDDHHMM format.
If a Company has a name change, should the Commencement Date (Field 22) of the new entry be reported the same as the original entry or is the Commencement Date changed to the effective date of the name change? (Added 08/23/2013)
The Commencement date should not change due to a new name.
The Commencement Date of Contract Terms is defined as, “The date the terms of the contract reported in fields 18, 23 and 25 through 44 (as defined in the data dictionary) became effective...” Since the Seller Company Name is Field 16 and the Customer Company Name is Field 17, a change in either of those fields does not cause a need to change the Commencement Date of Contract Terms.
The Commencement Date of Contract Terms is defined as, “The date the terms of the contract reported in fields 18, 23 and 25 through 44 (as defined in the data dictionary) became effective...” Since the Seller Company Name is Field 16 and the Customer Company Name is Field 17, a change in either of those fields does not cause a need to change the Commencement Date of Contract Terms.
When reporting contracts during a quarter in which the Seller name changed during the quarter do I use the same “Contract Unique Identifier” number for the contract under both names or should I use two different C numbers as I did below? (As of 07/23/2013)
Please use two unique numbers.
The Extension Provision Description (Field 25) in Contract Data is a required field. How do the contract Begin and End Dates differ from the Contract Execution Date, the Commencement Date of Contract Terms, the Contract Termination Date, and Actual Termination Date? (Modified 12/13/2013)
The Contract Execution Date, the Commencement Date of Contract Terms, the Contract Termination Date, and the Actual Termination Date refer to the entire contract. Contract Execution Date is the date the original contract was signed. If the parties signed on different dates, use the most recent date signed relative to the EQR being filed. Commencement Date of Contract Terms is the date the terms of the contract became effective relative to the EQR being filed. If those terms became effective on multiple dates (i.e., due to one or more amendments), the date to be reported in this field is the date the most recent amendment became effective. If the contract or the most recent reported amendment does not have an effective date, the date when service began pursuant to the contract or most recent reported amendment may be used.
The Contract Termination Date is the date that the contract expires; it is required, if specified in the contract. Actual Termination Date is the date the contract actually terminates and is required when the contract is terminated. (Source: Order 2001-H).
What do I enter if a contract does not have an Extension Provision (Field 25)? (As of 07/23/2013)
This is a free text field. Enter None or N/A.
What is the Contract Service Agreement ID (Field 20)? (As of 07/23/2013)
The Contract Service Agreement ID is an internal naming or numbering system that is used at a Seller company to identify the contract. It should be unique for that contract. If FERC were to request that contract from your company, you should be able to understand that name/number and identify the contract.
Are negative and $0 prices allowed for bilateral contracts? (As of 07/23/2013)
It is allowed, but the system will show a warning message informing you to double check this data. If you actually pay to deliver energy, you are reporting correctly using negative prices. However if you are not selling energy at a negative price, you might be misreporting a booked-out power transaction. If you are being PAID to sell energy, the price should be positive.
Do I report Conforming Service Agreements? (As of 07/23/2013)
The full text of agreement on file at FERC that conform to the standard service agreement and are reported in a company’s EQR need not be filed with the Commission. Unexecuted and non-conforming cost-based agreements still must be filed. All service agreements and contracts are required to be reported in the EQR once sales under them begin. They remain in the EQR from quarter to quarter, until they are terminated. All contracts must have at least one product. (Source: 18 CFR 35.10a (a); Order No. 2001).
Are Market-Based Rate Service Agreements reported? (As of 07/23/2013)
All market-based rate service agreements and contracts are required to be reported in the EQR once sales begin under them. (Source: Order No. 2001).
What Unexecuted and Nonstandard Non-Market-Based Rate Agreements must be reported? (As of 07/23/2013)
Agreements must be reported in the EQR once service under the agreement begins and must continue to be reported until terminated. (Source: Order No. 2001, 99 FERC ¶ 61, 107, April 25, 2002, Paragraphs 188 and 196).
Any individually executed service agreement for transmission, cost-based power sales, or other generally applicable services that deviates in any material respect from the applicable form of service agreement contained in the public utility's tariff and all unexecuted agreements under which service will commence at the request of the customer, are subject to the filing requirements under 18 CFR 35.1(g).
Any individually executed service agreement for transmission, cost-based power sales, or other generally applicable services that deviates in any material respect from the applicable form of service agreement contained in the public utility's tariff and all unexecuted agreements under which service will commence at the request of the customer, are subject to the filing requirements under 18 CFR 35.1(g).
What transmission contracts and transmission sales need to be reported in the EQR? (Modified 12/13/2013)
Transmission sales that are unbundled parts of a power sale need to be reported. Merchant transmission companies with a negotiated rate tariff must report Capacity Reassignments are reported in detail by the transmission provider in the Contract Data section of the EQR.
Does Capacity Reassignment Data need to be reported? (As of 07/23/2013)
Yes, all transmission capacity reassignments since the effective date of Order No. 890 (May 14, 2007) must be reported in the EQR according to the Commission’s Notice Providing Guidance on the Filing of Information on Transmission Capacity Reassignments in Electric Quarterly Reports . (Source: Order Nos. 890, 890-A, and 890-B).
. (Source: Order Nos. 890, 890-A, and 890-B).
How do I report Capacity Reassignment Agreements given that the Data Dictionary Fields have changed? (As of 07/23/2013)
The general definitions of the EQR Data Dictionary will apply to capacity reassignment agreement. Each capacity reassignment agreement should be reported in the Contract Data section (Fields 15-44) with the REASSIGNMENT AGREEMENT product name in Field 31. The Product Type Name (Field 30) should be CR – Capacity Reassignment and the Rate Description (Field 37) should be Transmission Reassignment Agreement. The required Class Name (Field 26), Term Name (Field 27), Increment Name (Field 28), Increment Peaking Name (Field 29) should be N/A. Fields 32 through 36 and 38 through 44 are to be left blank. As discussed below, no data in the transaction section of the EQR will be associated with these contracts. Note that Customer DUNS Number and Time Zone are no longer reported fields per Order No. 768. For convenience, the revised Special Conventions for Reporting Transmission Capacity Reassignment Agreements are below:
If no specific reporting conventions are indicated for particular fields, the general reporting requirements associated with the EQR Data Dictionary apply. Original information about the special reporting conventions associated with reporting capacity reassignment data in the EQR was issued on September 18, 2008, under RM-01-8-011, Notice Providing Guidance on the Filing of Information on Transmission Capacity Reassignments in Electric Quarterly Reports.
| Field # | Field | SPECIAL CONVENTIONS | Example |
15 |
Contract Unique ID | C1 | |
16 |
Seller Company Name | The transmission provider. | Transmission Provider X |
17 |
Customer Company Name | The assignee. | Company D |
18 |
Contract Affiliate | N | |
19 |
FERC Tariff Reference | FERC RateSchedule No. 30 | |
20 |
Contract Service Agreement ID | Must match the Contract Service Agreement ID for all transmission capacity reassignments under this contract. | TCR-1 |
21 |
Contract Execution Date | Refers to the date of the transmission capacity reassignment agreement between the transmission provider and the assignee. | 19900829 |
22 |
Contract Commencement Date | Refers to the date of the transmission capacity reassignment agreement between the transmission provider and the assignee. | 19900829 |
23 |
Contract Termination Date | ||
24 |
Actual Termination Date | ||
25 |
Extension Provision Description | Evergreen | |
26 |
Class Name | N/A | N/A |
27 |
Term Name | N/A | N/A |
28 |
Increment Name | N/A | N/A |
29 |
Increment Peaking Name | N/A | N/A |
30 |
Product Type Name | CR | CR |
31 |
Product Name | Only transmission capacity reassignment agreements should use the REASSIGNMENT AGREEMENT Product Name. | REASSIGNMENT AGREEMENT |
32 |
Quantity | Blank | |
33 |
Units | Blank | |
34 |
Rate | Blank | |
35 |
Rate Minimum | Blank | |
36 |
Rate Maximum | Blank | |
37 |
Rate Description | Transmission capacity reassignment agreement. | Transmission capacity reassignment agreement. |
38 |
Rate Units | Blank | |
39 |
Point of Receipt Balancing Authority(PORBA) | Blank | |
40 |
Point of Receipt Specific Location (PORSL) |
Blank | |
41 |
Point of Delivery Balancing Authority(PODBA) | Blank | |
42 |
Point of Delivery Specific Location (PODSL) |
Blank | |
43 |
Begin Date | Blank | |
44 |
End Date | Blank |
If no specific reporting conventions are indicated for particular fields, the general reporting requirements associated with the EQR Data Dictionary apply. Original information about the special reporting conventions associated with reporting capacity reassignment data in the EQR was issued on September 18, 2008, under RM-01-8-011, Notice Providing Guidance on the Filing of Information on Transmission Capacity Reassignments in Electric Quarterly Reports.
How do I report Transmission Capacity Reassignments (i.e. Point-to-Point Agreements) given that the Data Dictionary Fields have changed? (As of 07/23/2013)
Unique reporting conventions accommodate reporting of reassigned point-to-point transmission agreements in the Contract Data section (Fields 15-44). Transmission providers must provide the identity of the reSeller and the assignee for all transmission capacity reassignments. The transmission provider is responsible for reporting the terms of the initial transmission capacity reassignment as well as the terms of any subsequent transmission capacity reassignment of the same transmission capacity. Eeach transmission reassignment will be governed by its own agreement). Take, for example, a case where the transmission provider sells point-to-point transmission capacity to Company A for five years. Company A reassigns that transmission capacity to Company B for one month. Company B, in turn, reassigns the same transmission capacity to Company C for one day. In addition to the original sale of transmission capacity to Company A, the transmission provider must report the transmission capacity reassignment agreement and the transmission capacity reassignment with Company B as well as the transmission capacity reassignment agreement and the transmission capacity reassignment with Company C. Under a single transmission capacity reassignment agreement between a transmission provider and an assignee, several different transmission capacity reassignments may occur. Each of those reassignments must be reported separately. (Source: Order No. 890-B).
For convenience, the revised Special Conventions for Reporting Transmission Capacity Reassignments are below:
If no specific reporting conventions are indicated for particular fields, the general reporting requirements associated with the EQR Data Dictionary apply. Original information about the special reporting conventions associated with reporting capacity reassignment data in the EQR was issued on September 18, 2008, under RM-01-8-011, Notice Providing Guidance on the Filing of Information on Transmission Capacity Reassignments in Electric Quarterly Reports.
| Field # | Field | SPECIAL CONVENTIONS | Example |
15 |
Contract Unique ID | C2 | |
16 |
Seller Company Name | The transmission provider. | Transmission Provider X |
17 |
Customer Company Name | Both the reSeller and assignee must be identified. "R”: followed by the OATI webRegistry for reSeller followed by "/A:" followed by OATI webRegistry Entity Code for assignee. | R:COMC/A:COMD |
18 |
Contract Affiliate | Affiliation refers to whether the reSeller identified in Customer Company Name is an affiliate of the transmission provider identified in Seller Company Name. | N |
19 |
FERC Tariff Reference | All reassignments under the same transmission capacity reassignment agreement should have the same FERC Tariff Reference. |
FERC Rate Schedule No. 30 |
20 |
Contract Service Agreement ID | All reassignments under the same transmission capacity reassignment agreement should have the same Contract Service Agreement ID. |
TCR-1 |
21 |
Contract Execution Date | All reassignments under the same transmission capacity reassignment agreement should have the same C Contract Execution Date. |
19900829 |
22 |
Contract Commencement Date | All reassignments under the same transmission capacity reassignment agreement should have the same Contract Commencement Date. |
19900829 |
23 |
Contract Termination Date | All reassignments under the same transmission capacity reassignment agreement should have the same Contract Termination Date. |
|
24 |
Actual Termination Date | All reassignments under the same transmission capacity reassignment agreement should have the same Actual Termination Date. |
|
25 |
Extension Provision Description | All reassignments under the same transmission capacity reassignment agreement should have the same Extension Provision Description. |
Evergreen |
26 |
Class Name | F | |
27 |
Term Name | ST | |
28 |
Increment Name | N/A | |
29 |
Increment Peaking Name | P | |
30 |
Product Type Name | CR | CR |
31 |
Product Name | POINT-TO-POINT AGREEMENT | POINT-TO-POINT AGREEMENT |
32 |
Quantity | Required | 50 |
33 |
Units | Required | MW |
34 |
Rate | Required: The rate paid by the assignee to the transmission provider. NAESB rules require resale prices to be stated in $/MW-Hour reserved. (Source: Order No. 676-C) |
2.50 |
35 |
Rate Minimum | Must be blank. | |
36 |
Rate Maximum | Required: The rate that would have been charged under the transmission provider's OATT had the secondary customer purchased primary service from the transmission provider for the term of the transmission capacity reassignment. If the transmission provider does not offer primary service in a similar time increment, it will report the rate for the next highest time increment available. |
5.50 |
37 |
Rate Description | ||
38 |
Rate Units | Required: Rate unit for the rate provided in Field 36. | $/MW-Hour |
39 |
Point of Receipt Balancing Authority(PORBA) | Required | CISO |
40 |
Point of Receipt Specific Location (PORSL) |
Required | NP15 |
41 |
Point of Delivery Balancing Authority(PODBA) | Required | AZPS |
42 |
Point of Delivery Specific Location (PODSL) |
Required | Substation Q |
43 |
Begin Date | Required. First date/time of the transmission capacity reassignment reported. |
200803241100 |
44 |
End Date | Required. Last date/time of the transmission capacity reassignment reported. |
200803241600 |
If no specific reporting conventions are indicated for particular fields, the general reporting requirements associated with the EQR Data Dictionary apply. Original information about the special reporting conventions associated with reporting capacity reassignment data in the EQR was issued on September 18, 2008, under RM-01-8-011, Notice Providing Guidance on the Filing of Information on Transmission Capacity Reassignments in Electric Quarterly Reports
.
My company needs to report transmission data, what are the Standards of Conduct and Affiliation Restrictions? (As of 07/23/2013)
Please see the Commission’s regulations at 18 CFR 358.5, 358.6, and 358.7; 18 CFR 35.39(c) and (d).
Under the Standards of Conduct and Affiliation Restrictions, an employee of a wholesale merchant function/marketing affiliate may not receive non-public transmission contract information from the transmission provider to be formatted, entered, or filed in the EQR because that employee may be getting preferential access to transmission, and possibly customer, information before that information becomes available to the public.
Under the Standards of Conduct and Affiliation Restrictions, an employee of a transmission provider may receive power sales or contract information from an employee of a wholesale merchant function/marketing affiliate to be formatted, entered, or filed in the EQR although that employee would be getting access to market information before that information becomes public.
Under the Standards of Conduct and Affiliation Restrictions, a shared support-type employee, accountant, or contractor may receive non-public transmission contract information from the transmission provider and receive the power sales data from the wholesale merchant function/marketing affiliate, format the data, enter it into the EQR software and file the EQR with the Commission. That person is not allowed to be a conduit for sharing the non-public information with any wholesale merchant function/marketing affiliate.
Under the Standards of Conduct and Affiliation Restrictions, an employee of a wholesale merchant function/marketing affiliate may not receive non-public transmission contract information from the transmission provider to be formatted, entered, or filed in the EQR because that employee may be getting preferential access to transmission, and possibly customer, information before that information becomes available to the public.
Under the Standards of Conduct and Affiliation Restrictions, an employee of a transmission provider may receive power sales or contract information from an employee of a wholesale merchant function/marketing affiliate to be formatted, entered, or filed in the EQR although that employee would be getting access to market information before that information becomes public.
Under the Standards of Conduct and Affiliation Restrictions, a shared support-type employee, accountant, or contractor may receive non-public transmission contract information from the transmission provider and receive the power sales data from the wholesale merchant function/marketing affiliate, format the data, enter it into the EQR software and file the EQR with the Commission. That person is not allowed to be a conduit for sharing the non-public information with any wholesale merchant function/marketing affiliate.
What defines a need for a new Transaction Unique ID? (Added 08/23/2013)
Every transaction row requires its own Transaction Unique ID (Field 45).
What defines a new row for a transaction? (Added 08/23/2013)
A new transaction row should be used for each product. A new transaction row must be used every time a price changes in a sale.
What are the units for Standardized Quantity and the Standardized Price for booked out power?(Added 08/23/2013)
Both Energy and Capacity products can be booked out. If a Seller is reporting BOOKED OUT POWER of Energy, the units should be MWh and $/MWh for standardized quantity and standardized price respectively; if a Seller is reporting BOOKED OUT POWER of Capacity, the units should be MW-MO and $/MW-MO respectively. A Seller should be able to identify what product is sold or booked out.
The price for our service or product changed many times during the reporting quarter. Can I simply average the price for the quarter and list it on one row? (As of 07/23/2013)
No, data must specifically reflect the price changes per product per timeframe during a quarter. The price and time changes can be shown as several rows within one transaction or as separate transactions. If the price changed hourly, there will be a new row for each hour.
Is it acceptable to use the Time Zone as of the filing date of the report for monthly transactions that encompass a time zone change? (As of 07/23/2013)
No, please use prevailing Time Zone entries, such as Eastern Prevailing (EP), Central Prevailing (CP), etc., for transactions during time zone changes. See Time Zone Table, Appendix D of the EQR Data Dictionary for a full list of available options. Prevailing Time indicates that the time is adjusted according to the time of year for daylight savings. For example, Eastern Prevailing (EP) indicates the use of Eastern Standard (ES) between November and March and Eastern Daylight (ED) between March and November.
for a full list of available options. Prevailing Time indicates that the time is adjusted according to the time of year for daylight savings. For example, Eastern Prevailing (EP) indicates the use of Eastern Standard (ES) between November and March and Eastern Daylight (ED) between March and November.
How do I report Transactions that were made in one quarter but actually flowed in the subsequent quarter? (As of 07/23/2013)
Transactions should be reported for the quarter in which the power flowed or would have flowed, in the case of book outs.
How do I report a Transaction that begins in one quarter and ends in a later quarter? (Modified 12/13/2013)
If the same transaction occurs in multiple filing quarters, it must be reported in each applicable quarter.
How do the Transaction Unique ID (Field 45) and the Transaction Unique Identifier (Field 50) differ? (As of 07/23/2013)
When importing data into the application, the Transaction Unique ID must begin with the letter T. The Transaction Unique Identifier is a company assigned designation for each transaction and remains unchanged by the system after import.
What should we list as Transaction Increment Name (Field 61) for energy sales? Does it need to match the Contract Increment Name (Field 28)? (As of 07/23/2013)
The increment name should reflect the transaction length. If the transaction was executed in one period, it will be the difference between the start time and end time of that transaction. The increment name for energy sales to an ISO should always be H-Hourly. Notice in the data dictionary that there is a CONTRACT increment name and a TRANSACTION increment name. They are different and defined differently. It is possible to have an Hourly Contract Increment Name and have a D-Daily Transaction Increment Name for a transaction under that same contract. These two increment names do not have to be the same.
My transactions are settled in five or 10-minute increments in a given RTO, what Increment Name (Field 61) should I report? (Modified 12/13/2013)
Please continue to use the Hourly increment for all transactions for which the terms of the particular sale are set for up to six consecutive hours (≤ 6 consecutive hours) including LMP based sales in ISO/RTO markets.
I do not have any data to report in the Total Transmission Charge (Field 69). Can I enter N/A? (As of 07/23/2013)
Field 69 requires a numeric value. If there is no transmission charge to report, enter a 0 (zero) in the field.
Do Ancillary Services need to be reported in the EQR? (As of 07/23/2013)
Ancillary service transaction data associated with power sales are required to be filed. Ancillary service transaction data associated with transmission need not be reported when the transmission services are provided on an unbundled basis. (Source: Order 2001-I P271 & 272).
Are Purely Financial Transactions, including RTO virtual transactions, reported in the EQR? (As of 07/23/2013)
Contract data and transaction data on any wholesale power sales contract that provides for physical delivery must be reported in Electric Quarterly Reports, either as delivered power or as a book out. By contrast, “purely financial transactions” need not be reported. Applying these principles to power sales cleared by a CFTC-approved DCO, when a power sales contract provides for physical delivery and has not been terminated prior to the commencement of service under the contract, transactions under the contract are to be reported. (Source: Order No. 2001-F).
Regarding the transaction dates, if I have a sales contract that has an annual true-up, (i.e., at the end of the year the sum of actual delivered volumes for the year does not equal the contract volume), what date do I put for that true-up volume? (As of 07/23/2013)
If the true-up volume is delivered, please use the date of the transaction.
Are flat rate units acceptable for Energy? (As of 07/23/2013)
Transactions reported as FLAT RATE do not provide sufficient information regarding the price of a transaction and do not allow for conversion to a standardized unit. New fields for standardized prices and quantities are required for energy and capacity sales.
Do I need to report sales to my parent company? (As of 07/23/2013)
Yes, sales to parent companies should be marked as affiliate sales.
If the company sells to an ISO through the account of another company, who should they report as the buyer? (As of 07/23/2013)
If a facilitating entity takes title, the sale would be reported with the facilitating entity as the customer and the facilitating entity would report its sale to the ISO. (Source: Order Nos. 2001 and 2001-E).
What should the transaction Increment Name (Field 61) be if there are multiple daily flows over a month? (Modified 12/13/2013)
It depends on the terms of the particular sale. As outlined in the Data Dictionary, Field 61 Increment Name should be H-Hourly if the term is set for up to 6 consecutive hours (≤ 6 consecutive hours); D – Daily for more than 6 and up to 60 consecutive hours (>6 and ≤ 60 consecutive hours); W - Weekly if for over 60 consecutive hours and up to 168 consecutive hours (>60 and ≤ 168 consecutive hours); M - Monthly for more than 168 consecutive hours up to, but not including, one year (>168 consecutive hours and < 1 year); and Y - Yearly for one year or more (≥ 1 year).
How do I retire a company or cancel my MBR authority? How do I tell FERC that there has been a merger or a name change? (As of 07/23/2013)
When a Seller’s legal name changes or a Seller wishes to relinquish its market-based rate authority it is required to notify the Commission. In most instances, if a Seller’s name changes it must file a Notice of Succession. If the Seller desires to cancel its tariff, it must file a Notice of Cancellation. Please see http://www.ferc.gov/industries/electric/gen-info/mbr/filings/succession.asp.
What name do I use for a buyer or a Seller if the contract says one thing, but the actual company has changed names? (As of 07/23/2013)
When a Seller’s legal name changes, the company is required to notify the Commission. In most instances, if a Seller’s name changes it must file a Notice of Succession. Use the legal company name that is effective at the time of the transaction.
How do I report offsetting sales in an ISO/RTO? (Added 08/23/2013)
Offsetting transactions in ISO/RTO markets must be reported in the EQR in accordance with the Real Time/Day Ahead guidance document . ISO/RTO sales should not be reported as BOOKED OUT POWER.
. ISO/RTO sales should not be reported as BOOKED OUT POWER.
For a Transaction made with Counterparty A through ICE where the Seller pays a commission to ICE, what should Seller report in Exchange/Brokerage Service (Field 54): “Broker” or “ICE”? (Added 12/13/2013)
Exchange/Brokerage Service (Field 54) should be ICE.
If my Point of Delivery Balancing Authority is no longer listed as active for the filing period what should I use? (Added 02/01/2016)
The list of active and inactive Balancing Authorities is based on OATI’s webRegistry. This updated Balancing Authorities list can be viewed in the “Allowable Entries for PORBA, PODBA, and Hubs (Fields 39-42) XLS” document. Be aware that these entries may change; consequently, you may need to contact the Seller Company to determine the most active Balancing Authority or Hub if you receive an associated filing error.
What is the Trade Date for a generation offer into the day-ahead market that was cleared by the RTO/ISO? (As of 07/23/2013)
The Trade Date should be the date the offer cleared in the day-ahead market, i.e., the day before the power flowed.
What is the Trade Date for a real-time offset of a day-ahead bid? (As of 07/23/2013)
The Trade Date should be the date of the offset.
What is the Trade Date for ancillary credits, such as Uplift or Regulation & Frequency Response? (As of 07/23/2013)
The Trade Date should be the date the markets clear. For example, if a credit is related to a day-ahead energy sale to the RTO or ISO, the correct Trade Date for the uplift credit is the day before the power flowed. If a credit is related to a real-time energy sale to an RTO or ISO, the correct Trade Date for the regulation and frequency response credit is the day the power flowed.
What is the Trade Date for a product that is imported into a market? (As of 07/23/2013)
Imports should follow the same guidelines for Trade Date as noted above for other, similar transactions. As such, the Trade Date for a day-ahead import is the day before the power was imported; the Trade Date for a real-time import is the date of the import.
What is the Trade Date for an Internal Bilateral Transaction (in PJM)? (As of 07/23/2013)
In general, an Internal Bilateral Transaction is pursuant to a bilateral contract for the purchase or sale of electric energy separate from other transactions taking place in the organized energy market. The Trade Date for an Internal Bilateral Transaction should be the date upon which the parties made the legally binding agreement on the price of the transaction, not necessarily the date that the trade may have been reported to an RTO/ISO.
Should the “RTO/ISO” value for Type of Rate (Field 55) only be used if the sale is to the RTO/ISO? (As of 07/23/2013)
Yes, use “RTO/ISO” in the Type of Rate field if the rate is the result of an RTO/ISO market or a sale made to the RTO/ISO. The “RTO/ISO” Type of Rate will be used almost exclusively for sales in which an RTO/ISO is identified as the customer in the EQR. (Source: Order No. 768-A P47).
Would I use “Electric Index” if the RTO/ISO price is a component of the rate charged in a bilateral sale? (As of 07/23/2013)
Use “Electric Index” in the Type of Rate field if the RTO/ISO price is a component of the rate charged in a bilateral sale. In a situation where a formula is tied to an RTO/ISO price, the Type of Rate should be listed as “Electric Index.” It is not an “RTO/ISO” Type of Rate because it is not the result of an RTO/ISO market or a sale made to the RTO/ISO. (Source: Order No. 768-A P47).
Is Index Reporting Data compiled and reported as a separate EQR section, much like ID Data, Contract Data, and Transaction Data? (As of 07/23/2013)
Yes, the Index Reporting Data is a separate EQR section. If Sellers are reporting to an index publisher that is not listed in the EQR, Sellers (or their designated Agents) should notify Commission staff of the index publisher by emailing EQR@ferc.gov.
In Index Reporting Data, do I list each index to which I report and each product that I report to that index? (As of 07/23/2013)
Yes, list each index price publisher to which prices are reported on a separate line in the Index Reporting Data Section. If not all transactions or products are reported to that index, specify the types of transactions or products reported to the index (e.g., next day physical energy, balance of month physical energy) in Field Number 74 (Transactions Reported).
What notification will EQR Sellers (or their designated Agents) receive when an EQR has been sent to FERC for filing? (As of 12/13/2013)
- An automated email of receipt will be sent to the person who submitted the EQR.
- A notification of validation status will be sent via email to all company-appointed Seller and Agent contacts. This notice will include any “errors” (i.e., severe defects that will result in the automatic rejection of the filing) and “warnings” (i.e., minor defects that will not result in the automatic rejection of the filing).
- Once validation occurs, a notification of acceptance or rejection will be sent via email to all company- appointed Seller and Agent contacts. If you do not receive an email labeled “Acceptance of Filing,” then FERC has not received your filing and you need to resend the EQR to meet filing requirements. If you receive the “Acceptance of Filing” email, then you have successfully filed an EQR for the quarter. If you receive a rejection email, you will need to take corrective action with the data and resend the EQR.
Will Seller and Agent contacts be automatically added to the general EQR mailing list (i.e., the list used to provide general EQR-related information)? (As of 07/23/2013)
Yes, all Seller and Agent contacts will be automatically added to the general EQR mailing list as long as they have gone through the eRegistration process. In addition, Sellers and Agents will be able to add themselves to FERC’s RSS Feed.
Is e-Tag data compiled and reported as a separate EQR section? (As of 07/23/2013)
Under Order No. 768, the e-Tag Data is a separate EQR section; however, the compliance date for reporting e-Tag Data in the EQR has been extended. See Electricity Market Transparency Provisions of Section 220 of the Federal Power Act, 142 FERC ¶ 61,105 (2013).
Is FERC concerned that the quantities reported in the EQR may not match the quantities associated with the e-Tags? (As of 07/23/2013)
Staff will respond to this question at a later time because the compliance date for reporting e-Tag Data in the EQR has been extended. See Electricity Market Transparency Provisions of Section 220 of the Federal Power Act 142 FERC ¶ 61,105 (2013).
How will e-Tag IDs be reported for a transaction record that relates to four separate e-Tag IDs? (As of 07/23/2013)
Staff will respond to this question at a later time because the compliance date for reporting e-Tag Data in the EQR has been extended. See Electricity Market Transparency Provisions of Section 220 of the Federal Power Act, 142 FERC ¶ 61,105 (2013).
If I send my EQR filing and it is rejected by FERC, will I lose any changes I made to the data? (As of 07/23/2013)
No, if a Seller (or their designated Agent) creates an EQR submittal using the web client or edits information uploaded from the CSV file using the web client, the changes are stored in a working copy of the data on the FERC servers. Working data is not considered a filing; working data is retained until it is successfully filed and accepted by FERC.
XML submittals that are rejected are not retained by FERC.
If I need to correct an EQR that was filed prior to the second quarter 2013, do I use the FoxPro software or the new filing format? (Modified 12/13/2013)
Filings for the second quarter of 2013 and previous quarters will only be accepted in the current FoxPro software until further notice. Third quarter 2013 and beyond filings will only be accepted in the new system.
When refilling, can I just resend my contracts data? (Added 08/23/2013)
No, please resend the contracts data and the transaction data together. If not, it is likely that all of your transactions will be deleted.
