Documentation
Guidance on the usage of REMIT Relax.
Processing an Excel File
Enter or copy your trade data into the predefined Excel template and upload it to REMIT Relax. The templates contain no macros—all validation and processing happen securely within the service.
Each column header carries a number, and that number corresponds directly to the matching field number in the ACER Transaction Reporting User Manual (TRUM), so existing exports from other systems can usually be mapped in with minimal effort.
Where to Get Templates From
Templates are available to logged-in users under the Templates section. There are two main templates: an Excel template for ACER Table 1, Table 2, and Executions, and a separate Excel template for ACER Table 4 Fundamental Reports.
The Templates section also contains example files for each process, which help you test the process and understand how the references within a trade fit together.
Walking Through an Upload
- From the menu, select Generate ACER XML.
- Drag and drop your Excel file into the Upload Excel File area, or select it manually.
- Click Next to see a summary of the uploaded file. REMIT Relax automatically detects the target format, e.g. REMIT Table 1 or REMIT Table 2.
- On this screen, you can activate the Write-back UTI option—if enabled, the generated UTI is written into the corresponding column of your Excel file.
- Click Process to generate the ACER XML file.
- You'll see a success message, or a failure message with a short description if, for example, a business rule validation fails.
- From this page, you can download the generated XML file, the adjusted Excel file (with the UTI added, if selected), or all relevant files together as a ZIP.
- All recently generated XML files remain available in the History section of REMIT Relax, where you can review the details of any run via the eye icon at any time.
1. Fill Out the Excel File
- Before you open the Excel file, review the legal section carefully.
- Go to the main input sheet for the type of REMIT report you want to generate an XML file for.
- Fill in a few rows with sample deals, using the most prevalent transaction types.
- A few things to avoid, as they would prevent a successful XML generation:
- Do not change the order of columns in any sheet.
- Do not change the worksheet names.
- Do not change the format of the fields to anything other than “Standard”.
- See the field reference tables for further instructions on how to fill in each Excel sheet.
Standard Contracts (T1)
- Columns with a darker shaded background and bold text are mandatory input fields—these need to be filled in for every record.
- Columns with a darker shaded background but without bold text are conditional fields. The price, for example, can be given as either a fixed or an index price, but one of the two must be filled in—the same logic applies to quantity.
- Columns with a lighter shaded background are optional. If left empty, the resulting XML will simply not contain the associated opening and closing tags.
- Two reference columns on the right of the sheet link to reference sheets for nested XML substructures: “Ref. Delivery Profiles” is mandatory, and “Ref. Price Interval Quantity Details” should be filled in where applicable—that sheet in turn links to “Interval Times”.
Executions (T1)
- Identical to the “Standard Contracts (T1)” sheet, except for the “Linked transaction ID” column, which links the execution to its associated Non-Standard Contract (T2) by that contract's ID.
- Executions (T1) use the same reference sheets as Standard Contracts (T1).
Non-Standard Contracts (T2)
- Columns with a darker shaded background and bold text are mandatory for every record.
- There are no conditional fields—both price and quantity may be unknown at the time of execution, which is the essence of a Non-Standard Contract. If either one is known, however, it must be filled in.
- Columns with a lighter shaded background are optional; if left empty, the resulting XML will not contain the associated tags.
- Three reference columns—“Ref. Volume Optionality Intervals”, “Ref. Fixing Index Details”, and “Ref. Option Details”—link to reference sheets for nested XML substructures where needed. Once linked, those reference sheets must be completed as well.
UTI Generation (T1) and Contract ID Generation (T2)
- UTIs and Contract IDs are generated according to the ACER UTI Algorithm published in the Transaction Reporting User Manual (TRUM).
- If the UTI or Contract ID field is left empty, it is generated automatically from the other values you entered.
- Tick “Write generated UTIs back into input Excel?” during processing to write the generated value back into your Excel file.
- For Contract ID generation, quantity and price are optional and simply ignored if left empty.
- The ACER validation rules for UTIs apply—any violation results in an invalid XML, unless you supply your own UTI instead of letting REMIT Relax generate one.
Secondary Gas Capacity (T4)
- Columns with a darker shaded background and bold text are mandatory for every record.
- Columns with a lighter shaded background are optional; if left empty, the resulting XML will not contain the associated tags.
- Reference columns on the right of the sheet link to the relevant reference sheets for nested XML substructures where applicable—fill in the linked sheets whenever you use them.
- Not every field included in the ACER schema is documented in the TRUM, so a small number of fields are missing from the field reference tables.
Fundamental LNG Reports
- Columns with a darker shaded background and bold text are mandatory for every record.
- Columns with a lighter shaded background are optional; if left empty, the resulting XML will not contain the associated tags.
- Planned Usage and Participant Activity each have their own Excel template.
Fundamental Gas Storage Reports
- Columns with a darker shaded background and bold text are mandatory for every record.
- Columns with a lighter shaded background are optional; if left empty, the resulting XML will not contain the associated tags.
- There is a single Excel template for Participant Activity.
2. Generate an XML
- Generate a test XML file for each trade type you need to report from your Excel file.
- Review the details of the run on the History page (click the eye icon next to the run)—if it contains errors or warnings, correct the relevant columns in the working sheet and generate again.
Review the generated XML file carefully before testing it or reporting it to ACER.
3. Test the Generated Transactions
- Testing requires a contract with Equias for eRR (Accession Agreement) and technical set-up as a user—or any other RRM that accepts ACER XML files.
- To set up a contract or user access, contact Equias at equias.org.
- If you use eRR lite (no Ponton X/P installed, trading system not connected system-to-system), you only have web access to the CMS:
- Go to the Equias CMS UAT (test) instance at www.cms-test.equias.org.
- Use the upload function under the “REMIT Files IN” menu to upload your ACER XML file with the sample transactions.
- This menu requires Pseudo-OMP access, which must be enabled in your Joiner Form (the OMP-Partner ID field needs to be filled in).
- Testing via Ponton X/P is also possible, but the web access route is generally easier for this purpose.
- As an Equias eRR user, you can choose any file name for your ACER XML uploads—eRR renames the files itself before the report is submitted to ACER.
- Review the feedback carefully, either in the CMS or in the box results.
4. Ready for Reporting
- Repeat the same steps in the LIVE CMS system—either uploading the trades in the CMS directly or sending them via Ponton X/P.
- If you run into problems with the CMS, contact EFETnet at support@equias.org.
Excel Fields
The following sections describe the Excel fields and columns in detail. Each section corresponds to a specific tab in the Excel template.
ISO 8601 date format:[YYYY]-[MM]-[DD] or [YYYY]-[MM]-[DD]T[HH]:[MM]:[SS] or [HH]:[MM]:[SS].
The following tabs belong to the Excel template
REMIT-EXCEL-Tables-Template.xlsx, which includes sections for Table 1, Table 1 Executions, and Table 2 (Non-Standard), as well as all of their subsections. Standard Contracts (T1)
| Excel Col. | ACER Table 1 Data | ACER Field No. | Remarks | Implementation Notes |
|---|---|---|---|---|
| A | Record Sequence Number | — | Number consecutively. | Used from Excel, mandatory. |
| B | ID of Market Participant | 1, 2 | Has to be one of: ACER Code(12), LEI(20), BIC(11), EIC(16) or GLN(13). | Used from Excel, mandatory. Type of code used is filled automatically by REMIT Relax. |
| C | Trader ID for Organised Market or Trader ID for Market Participant | 3a/3b | ID which identifies the exact trader who made the deal. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| D | ID of Other Market Participant or Counterparty | 4, 5 | Has to be one of: ACER Code(12), LEI(20), BIC(11), EIC(16) or GLN(13). | Used from Excel, optional. If not filled, no tag will appear in the generated XML. If filled, the type of code used is filled automatically by REMIT Relax. |
| E | Reporting Entity ID | 6, 7 | Entity ID type: use “ACER”. Entity ID: use B00001014.NL for EFETnet. | Mandatory and static; the XML always adapts the ID that was entered with the trade in the first column. |
| F | Beneficiary ID | 8, 9 | Use the same ACER code type as for Entity ID. If Beneficiary ID = MP, leave blank. Has to be one of: ACER Code(12), LEI(20), BIC(11), EIC(16) or GLN(13). | Used from Excel, optional. If not filled, no tag will appear in the generated XML. If filled, the type of code used is filled automatically by REMIT Relax. |
| G | Trading Capacity | 10 | Use ‘P’=Principal or ‘A’=Agent. | Used from Excel, mandatory. |
| H | Buy/Sell Indicator | 11 | Use ‘B’=Buy, ‘S’=Sell, or ‘C’=Buy and Sell. | Used from Excel, mandatory. |
| I | Initiator/Aggressor | 12 | Use ‘A’=Aggressor, ‘I’=Initiator, or ‘S’=Sleeve. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| J | Contract ID | 21 | Unique code that identifies the contract. | Used from Excel, mandatory. |
| K | Contract Name | 22 | Fill in “BACKLOADING” in case the trade is relevant for backloading. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| L | Contract Type | 23 | Fill in one of: AU=Auction, CO=Continuous, FW=Forward style contract, FU=Future style contract, OP=Option style contract, OP_FW=Option on a forward, OP_FU=Option on a future, OP_SW=Option on a swap, SP=Spread, SW=Swap (financial), OT=Other, OP_SP=Option on spread, SWG=Swings. | Used from Excel, mandatory. |
| M | Energy Commodity | 24 | Use ‘NG’=Gas, ‘EL’=Electricity. | Used from Excel, mandatory. |
| N | Fixing Index or Reference Price | 25 | Alphanumerical field. | Used from Excel, conditional. If not filled, no tag will appear in the generated XML. |
| O | Settlement Method | 26 | Use ‘P’=Physical, ‘C’=Cash, ‘O’=Optional for counterparty. | Used from Excel, mandatory. |
| — | OMP ID | 27 | This field does not appear in the Excel, as OMP ID is not given per the definition of Phase 2 reporting. | Default value “XBIL” will appear in the XML. |
| P | Delivery Point or Zone | 48 | EIC code for the delivery point or market area. | Used from Excel, mandatory. |
| Q | Delivery Start Date | 49 | Local time in ISO 8601 date format. | Used from Excel, mandatory. |
| R | Delivery End Date | 50 | Local time in ISO 8601 date format. | Used from Excel, mandatory. |
| S | Load Type | 52 | Fill in one of: BL=Base load, PL=Peak load, OP=Off-Peak load, BH=Hour/Block Hours, SH=Shaped, GD=Gas Day, OT=Other. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| T | Transaction Timestamp | 30 | Date and time of the transaction in UTC time, in ISO 8601 date format. | Used from Excel, mandatory. |
| U | Unique Transaction ID (UTI) | 31 | Unique identifier of the transaction; generated automatically if the field is empty. | Used from Excel, mandatory. |
| W | Voice-Brokered | 34 | ‘true’, ‘false’ or ‘Y’=Yes, leave blank otherwise. | Used from Excel, optional. If not filled, the XML states not voice-brokered. |
| X | Price | 35 | Price per unit. | Used from Excel, conditional. If not filled, no tag will appear in the generated XML. |
| Y | Index Value | 36 | Value of the index. | Used from Excel, conditional. If not filled, no tag will appear in the generated XML. |
| Z | Price Currency | 37 | ISO 4217 currency code, 3 alphabetical digits (e.g. EUR, CHF, USD). | Used from Excel, conditional. If not filled, no tag will appear in the generated XML. |
| AA | Notional Amount | 38 | Value of the contract. | Used from Excel, conditional. If not filled, no tag will appear in the generated XML. |
| AB | Notional Currency | 39 | ISO 4217 currency code, 3 alphabetical digits (e.g. EUR, CHF, USD). | Used from Excel, conditional. If not filled, no tag will appear in the generated XML. |
| AC | Quantity/Volume | 40 | Total number of units included in the contract. | Used from Excel, conditional. If not filled, no tag will appear in the generated XML. |
| AD | Quantity Unit | 42a | E.g. ‘KW’, ‘MWh/h’. See the ACER TRUM for more. | Used from Excel, conditional. If not filled, no tag will appear in the generated XML. |
| AE | Total Notional Contract Quantity | 41 | Total number of units of the wholesale energy product. | Used from Excel, conditional. If not filled, no tag will appear in the generated XML. |
| AF | Total Notional Quantity Unit | 42b | E.g. ‘KWh’, ‘MWh’, ‘Therm’. See the ACER TRUM for more. | Used from Excel, conditional. If not filled, no tag will appear in the generated XML. |
| AG | Action Type | 58 | Fill in one of: N=New, M=Modify, E=Error, C=Cancel. | Used from Excel, mandatory. |
| AH | Ref. Delivery Profiles | — | Link to the “Delivery Profiles” sheet; fill in consecutive reference numbers. | Used from Excel, mandatory. |
| AI | Ref. Price Interval Quantity Details | — | Link to the “Price Interval Quantity Details” sheet; fill in consecutive reference numbers. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
Executions (T1)
Executions fit in the same table as “Standard Contracts (T1)” with two differences:
- There is no field 22 Contract Name, as Executions are not affected by the backloading obligation.
- One extra field needs to be filled:
| Excel Col. | ACER Table 1 Data | ACER Field No. | Remarks | Implementation Notes |
|---|---|---|---|---|
| U | Linked Transaction ID | 32 | Links the Execution to the associated Non-Standard Contract (T2); fill in the Contract ID of the T2 contract. | Used from Excel, mandatory. |
Delivery Profiles
| Excel Col. | ACER Table 1 Data | ACER Field No. | Remarks | Implementation Notes |
|---|---|---|---|---|
| A | Link to ‘Ref. Delivery Profiles’ | — | Link to the trade in sheet “Standard Contracts (T1)”; fill in reference numbers. These numbers can be repetitive if there is more than one delivery profile for one trade. | Mandatory. |
| B | Days of the Week | 53 | Use the following: “ ”=All days, MO=Monday, TU=Tuesday, WE=Wednesday, TH=Thursday, FR=Friday, SA=Saturday, SU=Sunday, XB=Excluding bank holidays, WN=Weekend, WD=weekdays. | Used from Excel, mandatory. |
| C | Delivery Start Time | 54a | Time expressed in local time of the delivery point/area, in ISO 8601 date format. | Used from Excel, mandatory. |
| D | Delivery End Time | 54b | Time expressed in local time of the delivery point/area, in ISO 8601 date format. | Used from Excel, mandatory. |
Price Interval Quantity Details
| Excel Col. | ACER Table 1 Data | ACER Field No. | Remarks | Implementation Notes |
|---|---|---|---|---|
| A | Link to ‘Ref. Price Interval Quantity Details’ | — | Link to the trade in sheet “Standard Contracts (T1)”; fill in reference numbers. These numbers can be repetitive if there is more than one delivery profile for one trade. | Mandatory, if used. |
| B | Interval Start Date | 49 | ISO 8601 date format. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| C | Interval End Date | 50 | ISO 8601 date format. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| D | Days of the Week | 53 | Use the following: “ ”=All days, MO=Monday, TU=Tuesday, WE=Wednesday, TH=Thursday, FR=Friday, SA=Saturday, SU=Sunday, XB=Excluding bank holidays, WN=Weekend, WD=weekdays. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| E | Delivery Capacity | 55 | Number of units included in the transaction, per delivery time interval. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| F | Quantity Unit of Field 55 | 56 | Unit of measurement used. | Used from Excel, conditional. If not filled, no tag will appear in the generated XML. |
| G | Price Time Interval Quantity Price | 57a | Put in the price of the interval. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| H | Price Time Interval Quantity Currency | 57b | Put in the currency of the interval. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| I | Ref. Interval Times | — | Link to the “Interval Times” sheet; fill in consecutive reference numbers. | Optional, use only if needed. |
Interval Times
| Excel Col. | ACER Table 1 Data | ACER Field No. | Remarks | Implementation Notes |
|---|---|---|---|---|
| A | Link to ‘Price Interval Quantity Details!Ref Interval Times’ | — | Link to the “Price Interval Quantity Details” sheet; fill in reference numbers. These numbers can be repetitive if there is more than one delivery profile for one trade. | Mandatory, if used. Numbers can be repetitive if there is more than one delivery profile for one trade. |
| B | Delivery Start Time | 54a | Time expressed in local time of the delivery point/area, in ISO 8601 date format. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| C | Delivery End Time | 54b | Time expressed in local time of the delivery point/area, in ISO 8601 date format. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
Non-Standard Contracts (T2)
| Excel Col. | ACER Table 2 Data | ACER Field No. | Remarks | Implementation Notes |
|---|---|---|---|---|
| A | Record Sequence Number | — | Number consecutively. | Used from Excel, mandatory. |
| B | ID of Market Participant | 1, 2 | Has to be one of: ACER Code(12), LEI(20), BIC(11), EIC(16) or GLN(13). | Used from Excel, mandatory. Type of code used is filled automatically by REMIT Relax. |
| C | ID of Other Market Participant or Counterparty | 3, 4 | Has to be one of: ACER Code(12), LEI(20), BIC(11), EIC(16) or GLN(13). If more than one, separate by semicolon. | Used from Excel, mandatory. Type of code used is filled automatically by REMIT Relax. |
| D | Reporting Entity ID | 5, 6 | Entity ID type: use “ACER”. Entity ID: use B00001014.NL for EFETnet. | Mandatory and static; the XML always adapts the ID that was entered with the trade in the first column. |
| E | Beneficiary ID(s) | 7 | Use the same ACER code type as for Entity ID. If Beneficiary ID = MP, leave blank. Has to be one of: ACER Code(12), LEI(20), BIC(11), EIC(16) or GLN(13). If more than one, separate by semicolon. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. If filled, the type of code used is filled automatically by REMIT Relax. |
| F | Trading Capacity | 9 | Use ‘P’=Principal or ‘A’=Agent. | Used from Excel, mandatory. |
| G | Buy/Sell Indicator | 10 | Use ‘B’=Buy, ‘S’=Sell, or ‘C’=Buy and Sell. | Used from Excel, mandatory. |
| H | Contract ID | 11 | Unique identifier of the transaction; generated automatically if the field is empty. | Used from Excel, mandatory. |
| I | Contract Date | 12 | Date the contract was agreed on, in ISO 8601 format. | Used from Excel, mandatory. |
| J | Contract Type | 13 | Fill in one of: AU=Auction, CO=Continuous, FW=Forward style contract, FU=Future style contract, OP=Option style contract, OP_FW=Option on a forward, OP_FU=Option on a future, OP_SW=Option on a swap, SP=Spread, SW=Swap (financial), OT=Other. | Used from Excel, mandatory. |
| K | Energy Commodity | 14 | Use ‘NG’=Gas, ‘EL’=Electricity. | Used from Excel, mandatory. |
| L | Price or Price Formula | 15a | Fill in if price is fixed. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| M | Price Currency | 15b | ISO 4217 currency code, 3 alphabetical digits (e.g. EUR, CHF, USD); fill only if price is fixed. | Used from Excel, conditional. If not filled, no tag will appear in the generated XML. |
| N | Price Formula | 15c | Fill in if price is a formula. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| O | Estimated Notional Amount | 16 | Value of the contract. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| P | Notional Currency | 17 | ISO 4217 currency code, 3 alphabetical digits (e.g. EUR, CHF, USD). | Used from Excel, conditional. If not filled, no tag will appear in the generated XML. |
| Q | Total Notional Contract Quantity | 18a | Estimated total number of units of wholesale energy product (calculated figure). | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| R | Notional Quantity Unit | 18b | E.g. ‘KWh’, ‘MWh’, ‘Therm’. | Used from Excel, conditional. If not filled, no tag will appear in the generated XML. |
| S | Volume Optionality | 21 | Volume classification; fill in one of: V=Variable, F=Fix, M=Min/Max, C=Complex, O=Other. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| T | Volume Optionality Frequency | 22 | Fill in one of: H=Hourly, D=Daily, W=Weekly, M=Monthly, Q=Quarterly, S=Season, A=Annual, O=Other. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| U | Type of Index Price | 24 | Fill in one of: F=Fixed, I=Simple Index, C=Complex Price Formula, O=Other. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| V | Settlement Method | 31 | Fill in one of: P=Physical, C=Cash, O=Optional for counterparty. | Used from Excel, mandatory. |
| W | Delivery Point or Zone | 41 | EIC code(s) for the delivery point(s) or market area(s). If more than one, separate by semicolon. | Used from Excel, mandatory. |
| X | Delivery Start | 42 | Local date and time of transaction, in ISO 8601 date format. | Used from Excel, mandatory. |
| Y | Delivery End | 43 | Local date and time of transaction, in ISO 8601 date format. | Used from Excel, mandatory. |
| Z | Load Type | 44 | Fill in one of: BL=Base load, PL=Peak load, OP=Off-Peak load, BH=Hour/Block Hours, SH=Shaped, GD=Gas Day, OT=Other. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| AA | Action Type | 45 | Fill in one of: N=New, M=Modify, E=Error, C=Cancel. | Used from Excel, mandatory. |
| AB | Ref. Volume Optionality Intervals | — | Link to the “Volume Optionality Intervals” sheet; fill in consecutive reference numbers. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| AC | Ref. Fixing Index Details | — | Fill in the reference number to “Fixing Index Details”. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| AD | Ref. Option Details | — | Fill in the reference number to “Option Details”. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
Volume Optionality Intervals
| Excel Col. | ACER Table 2 Data | ACER Field No. | Remarks | Implementation Notes |
|---|---|---|---|---|
| A | Link to ‘Ref. Volume Optionality Intervals’ | — | Link to map “Non-Standard Contracts (T2)”; fill in reference numbers. | Mandatory, if used. |
| B | Volume Optionality Capacity Value | 19 | Capacity value. | Used from Excel, mandatory. |
| C | Volume Optionality Unit | 19 | Unit of the capacity, e.g. ‘KW’, ‘KWh/h’. | Used from Excel, mandatory. |
| D | Start Date | 23a | ISO 8601 date format. | Used from Excel, mandatory. |
| E | End Date | 23b | ISO 8601 date format. | Used from Excel, mandatory. |
Fixing Index Details
| Excel Col. | ACER Table 2 Data | ACER Field No. | Remarks | Implementation Notes |
|---|---|---|---|---|
| A | Link to ‘Ref. Fixing Index Details’ | — | Link to map “Non-Standard Contracts (T2)”; fill in reference numbers. | Mandatory, if used. |
| B | Fixing Index | 25 | List of indices determining the price in the contract. For each index, specify the name. In case of a basket of indices for which no unique identifier exists, the basket or the index shall be indicated. | Used from Excel, mandatory. |
| C | Fixing Index Type | 26 | Fill in one of: FW=Forward style contract, FU=Future style contract, OP=Option style contract, OP_FW=Option on a forward, OP_FU=Option on a future, OP_SW=Option on a swap, SP=Spread, SW=Swap (financial), OT=Other. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| D | Fixing Index Source | 27 | Specify the source of publication, or put e.g. ‘INTERNAL’. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| E | First Fixing Date | 28 | ISO 8601 date format. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| F | Last Fixing Date | 29 | ISO 8601 date format. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| G | Frequency | 30 | Fill in one of: X=Half hourly, D=Daily, W=Weekly, M=Monthly, Q=Quarterly, S=Seasonal, A=Annual, O=Other. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
Option Details
| Excel Col. | ACER Table 2 Data | ACER Field No. | Remarks | Implementation Notes |
|---|---|---|---|---|
| A | Link to ‘Ref. Fixing Index Details’ | — | Link to map “Non-Standard Contracts (T2)”; fill in reference numbers. | Mandatory, if used. |
| B | Option Style | 32 | Indicates the exercising possibilities of the option; fill in one of: A=American (at any time during life of contract), B=Bermudan (series of pre-defined dates), E=European (at a fixed date), S=Asian (at a fixed date), O=Other. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| C | Option Type | 33 | Fill in one of: P=Put, C=Call, O=Other. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| D | First Exercise Date | 34 | ISO 8601 date format. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| E | Last Exercise Date | 35 | ISO 8601 date format. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| F | Exercise Frequency | 36 | Fill in one of: D=Daily, W=Weekly, M=Monthly, S=Seasonal, A=Annual, O=Other. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| G | Strike Index | 37 | For each index, specify the name. In case of a basket of indices for which no unique identifier exists, the basket or the index shall be indicated. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| H | Index Type | 38 | Fill in one of: FW=Forward style contract, FU=Future style contract, OP=Option style contract, OP_FW=Option on a forward, OP_FU=Option on a future, OP_SW=Option on a swap, SP=Spread, SW=Swap (financial), OT=Other. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| I | Strike Index Source | 39 | Specify the fixing type or specify the source. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| J | Strike Price | 40a | Alphanumerical field. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| K | Currency | 40b | ISO 4217 currency code, 3 alphabetical digits (e.g. EUR, CHF, USD). | Used from Excel, conditional. If not filled, no tag will appear in the generated XML. |
The following tabs belong to the Excel template
REMIT Table 4, Fund. Data Complete-Template.xlsx, which includes the formats Table 4 and Fundamentals for LNG and Gas. Secondary Gas Capacity (T4)
| Excel Col. | ACER Table 4 Data | ACER Field No. | Remarks | Implementation Notes |
|---|---|---|---|---|
| — | Coding Scheme | — | 305 by definition. | Generated by REMIT Relax automatically. |
| A | Sender Identification | 1 | ID of Market Participant, use EIC (16). | Used from Excel, mandatory. |
| B | Version | Non-existent | Version number of the contract. | Used from Excel, mandatory. |
| — | Type | Non-existent | ANI by definition. | Generated by REMIT Relax. |
| C | Creation Date and Time | Non-existent | Date and time of creation, in UTC time, in ISO 8601 format. | Used from Excel, mandatory. |
| D | Validity Period | Non-existent | Validity period in UTC time; use format [YYYY]-[MM]-[DD]T[HH]:[MM]Z/[YYYY]-[MM]-[DD]T[HH]:[MM]. | Used from Excel, mandatory. |
| E | Contract Reference | Non-existent | As the field is optional and no ACER specification is given, it is advisable to leave it empty. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| F | Contract Type | Non-existent | As the field is optional and no ACER specification is given, it is advisable to leave it empty. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| G | Issuer Market Participant Identification | Non-existent | EIC code of the Market Participant. | Used from Excel, mandatory. |
| H | Issuer MP Market Role Code | Non-existent | Refer to the EDIGAS Codelist, e.g. put in ‘ZUF’ for Capacity Platform Responsible. Note that Buyer (‘BY’) and Seller (‘SE’) are currently not supported by the ACER schema. | Used from Excel, mandatory. |
| I | Receiver Market Participant Identification | Non-existent | EIC code of the receiving party; use 10X1001B1001B61Q for ACER (has to be an ACER EIC code—all other codes get rejected). | Used from Excel, mandatory. |
| J | Receiver MP Market Role Code | Non-existent | Refer to the EDIGAS Codelist, e.g. put in ‘ZUA’ for Market Information Aggregator. | Used from Excel, mandatory. |
| K | Application Context | Non-existent | As the field is optional and no ACER specification is given, it is advisable to leave it empty. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| L | OMP Identification | 2 | Always 21X-XXXXXXXXXXXY, because there is no OMP by definition of Phase 2 reporting. | Used from Excel, mandatory. |
| M | Offered Capacity | 12 | Only for primary allocation processes. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| N | Currency Code | 17 | Refer to the EDIGAS code list; at the moment only ‘EUR’ is accepted by ACER. | Used from Excel, mandatory. |
| O | Quantity Measure Unit | 16 | Fill in one of: KWH=Kilowatt hour, GWH=Gigawatt hour, KW1=Kilowatt-hour per hour (kWh/h), KW2=Kilowatt-hour per day (kWh/d). Refer to the ACER TRUM for more. | Used from Excel, mandatory. |
| P | Process Identification | 3 | Identification of the process, e.g. a UTI. | Used from Excel, mandatory. |
| Q | Transportation Transaction Type | 9 | Refer to the EDIGAS Codelist; fill in ‘ZSZ’ for secondary market procedure. | Used from Excel, mandatory. |
| R | Network Point Identification | 22 | Put in the EIC code of the Network Point. | Used from Excel, mandatory. |
| S | Responsible TSO Identification | 25 | Put in the EIC code of the primary TSO. | Used from Excel, mandatory. |
| T | Adjacent TSO Identification | 26 | Put in the EIC code of the counter TSO. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| U | Transaction Date and Time | 6 | Date and time of the transaction, in UTC time, in ISO 8601 format. | Used from Excel, mandatory. |
| V | Auction Open Date and Time | 7 | Opening date and time of the auction. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| W | Auction End Date and Time | 8 | Closing date and time of the auction. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| X | Action Type | 14 | Provides the status of the document. Fill in one of: 62G=Active, 63G=Cancelled, 66G=Changed. | Used from Excel, mandatory. |
| Y | Capacity Type (Bundling) | 23 | Specification of bundling. Fill in one of: ZEO=Bundled, ZEP=Unbundled. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| Z | Taxonomy Energy Product Type | 4 | Mandatory for auction. Type of gas. Fill in one of: HC1=High Calorific, LC1=Low Calorific. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| AA | Capacity Category | 13 | Mandatory for auction. Fill in one of: Z06=Firm (booked), ZES=Restricted-allocable capacity (BZK), ZET=Dynamically allocable (DZK), ZEU=Temperature related and restricted capacity (TAK). Refer to the ACER TRUM for more. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| AB | Secondary Market Procedure | — | Refer to the EDIGAS Codelist. Fill in one of: A03=OTC, A04=Sublet. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| AC | Ref. Transportation Transaction | — | Link to the “Transportation Transaction” sheet; fill in consecutive reference numbers. | Mandatory. |
Transportation Transaction
| Excel Col. | ACER Table 4 Data | ACER Field No. | Remarks | Implementation Notes |
|---|---|---|---|---|
| A | Link to ‘Ref. Transportation Transaction’ | — | Link to the trade in sheet “Secondary Gas Capacity (T4)” with the reference number. | Mandatory; numbers can be repetitive if there is more than one Transportation Transaction. |
| B | Transportation Transaction Identification | 5 | Identification of the transaction, e.g. Prisma ID. | Used from Excel, mandatory. |
| C | Primary Market Participant Identification | 27 | Market Participant to which the capacity is assigned, use EIC (16). | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| D | Balancing Group or Portfolio Code | 28 | BG to which the shipper belongs, or the portfolio code used by the shipper if a BG is not applicable; use EIC (16). | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| E | Transferor Market Participant Identification | 36 | ID of the MP giving up the capacity, use EIC (16). | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| F | Transferee Market Participant Identification | 37 | ID of the MP receiving the capacity, use EIC (16). | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| G | Ref. Transportation Period | — | Link to the “Transportation Period” sheet; fill in consecutive reference numbers. | Mandatory. |
| H | Ref. Auction Round Characteristics | — | Link to the “Auction Round Characteristics” sheet; fill in consecutive reference numbers. | Optional. |
Transportation Period
| Excel Col. | ACER Table 4 Data | ACER Field No. | Remarks | Implementation Notes |
|---|---|---|---|---|
| A | Link to ‘Ref. Transportation Period’ in sheet Transportation Transaction | — | Link to the “Transportation Transaction” sheet; fill in reference numbers. | Mandatory; numbers can be repetitive if there is more than one Transportation Transaction. |
| B | Start and End Date and Time | 10+11 | In UTC time, in ISO 8601 format without seconds: [YYYY-MM-DD]T[HH:MM]Z/[YYYY-MM-DD]T[HH:MM]Z. | Used from Excel, mandatory. |
| C | Direction | 24 | Refer to the EDIGAS Codelist. Fill in: Z02=Input Quantity, Z03=Output Quantity. | Used from Excel, mandatory. |
| D | Contract Quantity | 15 | Total number of units allocated with the transportation transaction, as expressed in the measure unit. | Used from Excel, mandatory. |
| E | Total Price | 18 | Reserve price at the time of the auction, plus the auction premium, or the regulated tariff in case of an allocation mechanism other than auction. | Used from Excel, mandatory. |
| F | Reserve Price | 20 | Fill in the reserve price. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| G | Reserve Price Type | 19 | Refer to the EDIGAS Codelist. Fill in: Z07=Fixed Price, Z08=Floating Price. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| H | Premium Price | 21 | Fill in the premium price for the auction. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| I | Price Transferee Pays to Transferor | 35 | Price expressed in the currency per measure unit, which must be KWh/h. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| J | Price Paid to TSO (Underlying Price) | 34 | Only applicable when there is an assignment, expressed in the currency per measure unit, which must be KWh/h. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
Auction Round Characteristic
| Excel Col. | ACER Table 4 Data | ACER Field No. | Remarks | Implementation Notes |
|---|---|---|---|---|
| A | Link to ‘Ref. Auction Round Characteristics Transaction’ in sheet Transportation Transaction | — | Link to the “Transportation Transaction” sheet; fill in reference numbers. | Optional; numbers can be repetitive if there is more than one Auction Round Characteristics. |
| B | Auction Round Number | 39 | Integer that increments every time an auction achieves no result and is re-run with different parameters, starting at 1. To be left blank in case of auctions without binding rounds, e.g. day-ahead auctions. Maximum 3 digits. | Used from Excel, mandatory. |
| C | Ref. Bid | — | Link to the “Bid” sheet; fill in consecutive reference numbers. | Mandatory, if “Auction Round Characteristics” is used. |
Bid
| Excel Col. | ACER Table 4 Data | ACER Field No. | Remarks | Implementation Notes |
|---|---|---|---|---|
| A | Link to ‘Ref. Bid’ in sheet Auction Round Characteristic | — | Link to map “Auction Round Characteristics”; fill in reference numbers. | Mandatory (if “Auction Round Characteristics” is used); numbers can be repetitive if there is more than one Bid. |
| B | Bid ID | 38 | Numerical identifier of the bid, as assigned by the reporting entity. | Used from Excel, mandatory. |
| C | Bid Quantity | 41 | Quantity being bid for. | Used from Excel, mandatory. |
| D | Minimum Bid Quantity | 33 | Minimum the transferee/transferor would be willing to acquire/sell on creating the trade proposal. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| E | Maximum Bid Quantity | 32 | Maximum the transferee/transferor would be willing to acquire/sell on creating the trade proposal. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| F | Bid Price | 40 | Price being bid for each unit of capacity, excluding the reserve price. | Used from Excel, mandatory. |
| G | Minimum Bid Amount | 31 | Minimum the transferee would be willing to offer, expressed in currency per measure unit. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| H | Maximum Bid Amount | 30 | Maximum the transferor would be willing to offer, expressed in currency per measure unit. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
Fundamental LNG Report Participant Activity
| Excel Col. | ACER Data | ACER Field No. | Remarks | Implementation Notes |
|---|---|---|---|---|
| A | Reporting Entity ID | Non-existent | ACER code (12) of the MP submitting the report. | Used from Excel, mandatory. |
| B | Submission Date and Time | Non-existent | Date and time of submission of the trade, in UTC time, in ISO 8601 format. | Used from Excel, mandatory. |
| C | Gas Day Start | Non-existent | Date and time, in UTC time, in ISO 8601 format. | Used from Excel, mandatory. |
| D | Gas Day End | Non-existent | Date and time, in UTC time, in ISO 8601 format. | Used from Excel, mandatory. |
| E | LNG Facility ID | Non-existent | Has to be one of: ACER Code(12), LEI(20), EIC(16). | Used from Excel, mandatory. Type of code used is filled automatically by REMIT Relax. |
| F | Market Participant ID | Non-existent | Has to be one of: ACER Code(12), LEI(20), EIC(16). | Used from Excel, mandatory. Type of code used is filled automatically by REMIT Relax. |
| G | Terminal Customer ID | Non-existent | Fill only if different than Market Participant ID. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| H | Reporting Entity Reference ID | Non-existent | GIE RRM record-level identifier to be included in the ACER return receipt. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| I | Ship Size | Non-existent | Indicate the ship size value. | Used from Excel, mandatory. |
| J | Ship Size Unit | Non-existent | Fill in one of: cm, cm/d, mcm, mcm/d, kWh, kWh/h, kWh/d, GW, GWh, GWh/h, GWh/d, MW, MWh, MWh/h, MWh/d, TWh, Therm/d, kTherm/d, MTherm/d, Therm, kTherm, MTherm, %. | Used from Excel, mandatory. |
| K | Ship Name | Non-existent | Use the IMO number; as it has to be 10 digits long, use format IMO1234567. | Used from Excel, mandatory. |
| L | Reloaded Volume | Non-existent | Indicate the reloaded volume. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| M | Reloaded Volume Unit | Non-existent | Fill in one of: cm, cm/d, mcm, mcm/d, kWh, kWh/h, kWh/d, GW, GWh, GWh/h, GWh/d, MW, MWh, MWh/h, MWh/d, TWh, Therm/d, kTherm/d, MTherm/d, Therm, kTherm, MTherm, %. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| N | Unloaded Volume | Non-existent | Indicate the unloaded volume. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| O | Unloaded Volume Unit | Non-existent | Fill in one of: cm, cm/d, mcm, mcm/d, kWh, kWh/h, kWh/d, GW, GWh, GWh/h, GWh/d, MW, MWh, MWh/h, MWh/d, TWh, Therm/d, kTherm/d, MTherm/d, Therm, kTherm, MTherm, %. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
Fundamental LNG Report Planned Usage
| Excel Col. | ACER Data | ACER Field No. | Remarks | Implementation Notes |
|---|---|---|---|---|
| A | Reporting Entity ID | Non-existent | ACER code (12) of the MP submitting the report. | Used from Excel, mandatory. |
| B | Submission Date and Time | Non-existent | Date and time of submission of the trade, in UTC time, in ISO 8601 format. | Used from Excel, mandatory. |
| C | Gas Day Start | Non-existent | Date and time, in UTC time, in ISO 8601 format. | Used from Excel, mandatory. |
| D | Gas Day End | Non-existent | Date and time, in UTC time, in ISO 8601 format. | Used from Excel, mandatory. |
| E | LNG Facility ID | Non-existent | Has to be one of: ACER Code(12), LEI(20), EIC(16). | Used from Excel, mandatory. Type of code used is filled automatically by REMIT Relax. |
| F | Market Participant ID | Non-existent | Has to be one of: ACER Code(12), LEI(20), EIC(16). | Used from Excel, mandatory. Type of code used is filled automatically by REMIT Relax. |
| G | Terminal Customer ID | Non-existent | Fill only if different than Market Participant ID. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| H | Reporting Entity Reference ID | Non-existent | GIE RRM record-level identifier to be included in the ACER return receipt. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| I | Delivery Volume | Non-existent | Indicate the volume of the delivery. | Used from Excel, mandatory. |
| J | Delivery Volume Unit | Non-existent | Fill in one of: cm, cm/d, mcm, mcm/d, kWh, kWh/h, kWh/d, GW, GWh, GWh/h, GWh/d, MW, MWh, MWh/h, MWh/d, TWh, Therm/d, kTherm/d, MTherm/d, Therm, kTherm, MTherm, %. | Used from Excel, mandatory. |
Fundamental Gas Storage Report Participant Activity
| Excel Col. | ACER Data | ACER Field No. | Remarks | Implementation Notes |
|---|---|---|---|---|
| A | Reporting Entity ID | Non-existent | ACER code (12) of the MP submitting the report. | Used from Excel, mandatory. |
| B | Submission Date and Time | Non-existent | Date and time of submission of the trade, in UTC time, in ISO 8601 format. | Used from Excel, mandatory. |
| C | Gas Day Start | Non-existent | Date and time, in UTC time, in ISO 8601 format. | Used from Excel, mandatory. |
| D | Gas Day End | Non-existent | Date and time, in UTC time, in ISO 8601 format. | Used from Excel, mandatory. |
| E | Storage Facility ID | Non-existent | Has to be one of: ACER Code(12), LEI(20), EIC(16). | Used from Excel, mandatory. Type of code used is filled automatically by REMIT Relax. |
| F | Storage Facility Operator ID | Non-existent | Can be the facility operator or the market participant. Has to be one of: ACER Code(12), LEI(20), EIC(16). | Used from Excel, mandatory. Type of code used is filled automatically by REMIT Relax. |
| G | Market Participant ID | Non-existent | Can be the facility operator or the market participant. Has to be one of: ACER Code(12), LEI(20), EIC(16). | Used from Excel, optional. If not filled, no tag will appear in the generated XML. If filled, type of code used is filled automatically by REMIT Relax. |
| H | Reporting Entity Reference ID | Non-existent | GIE RRM record-level identifier to be included in the ACER return receipt. | Used from Excel, optional. If not filled, no tag will appear in the generated XML. |
| I | Storage Value | Non-existent | Indicate the storage volume. | Used from Excel, mandatory. |
| J | Storage Value Unit | Non-existent | Fill in one of: cm, cm/d, mcm, mcm/d, kWh, kWh/h, kWh/d, GW, GWh, GWh/h, GWh/d, MW, MWh, MWh/h, MWh/d, TWh, Therm/d, kTherm/d, MTherm/d, Therm, kTherm, MTherm, %. | Used from Excel, mandatory. |
Additional info is available in the FAQ.