Documentation

Guidance on the usage of REMIT Relax.

UTI Handling

The UTI is generated according to the ACER algorithm published in the Transaction Reporting User Manual (TRUM), after which some extra validation rules apply. You can ignore these rules if you create your own UTI and do not use REMIT Relax to generate one.

Please make sure all fields are formatted as “Text”—otherwise formatting errors with date and number fields (especially decimal separators) are very likely to occur.

You have the option to write generated UTIs and Contract IDs back into the Excel sheet by ticking “Write generated UTIs back into input Excel?”.

Reporting On Behalf of Others (ROBO): The UTI algorithm contains a running number at the end that counts up when the same trade is entered twice—which happens when you enter the trade both for yourself and for your counterparty. The result would be that the UTIs do not match, since the first ends with 001 and the second with 002. If you want to use REMIT Relax for ROBO and want it to create the UTI for you, it is therefore important to copy the generated UTI into the counterparty's trade as well.

On the History screen, where the latest generated files are shown, you can click the Info button at the end of a row to also retrieve the UTI base string that was used to generate the UTI.

Validation Rules for UTI (T1) Generation

The same rules apply for the UTI generation for Executions (T1).

Excel ColumnACER Table 1 DataACER Field No.Remarks
BID of Market Participant1Mandatory; must be an ACER code ([A-Za-z0-9_]+\.[A-Z][A-Z]) with a length of 12.
DID of Other MP4Mandatory; must be an ACER code ([A-Za-z0-9_]+\.[A-Z][A-Z]) with a length of 12.
KContract Type23Mandatory; must be one of: FW, OP, OP_FW, OP_SW, SP, SW, OT.
LEnergy Commodity24Mandatory; must be one of: EL, NG.
NSettlement Method26Mandatory; must be one of: P, C, O.
TTrade Date30Mandatory; must be in YYYY-MM-DD format. The algorithm takes the first 10 characters of the transaction timestamp.
VPrice35Optional; must be a valid decimal number, up to 20 digits total, with a dot (.) as the decimal mark and 5 decimal places (fill with zeros if necessary).
WCurrency37Optional; must be one of: BGN, CHF, CZK, DKK, EUR, GBP, HRK, HUF, ISK, NOK, PCT, PLN, RON, SEK, USD, OTH.
ZQuantity Volume4Optional; must be a valid decimal number, up to 20 digits total, with a dot (.) as the decimal mark and 5 decimal places (fill with zeros if necessary).
AAQuantity Unit42Optional; must be one of: KWh/h, KWh/d, MWh/h, MWh/d, GWh/h, GWh/d, Therm/d, KTherm/d, MTherm/d, cm/d, mcm/d, Btu/d, MMBtu/d, MJ/d, 100MJ/d, MMJ/d, GJ/d. Do not simply use MW—always use MWh/h.
ODelivery Point or Zone48Mandatory; must match [0-9][0-9][XYZTWV].+ with a length of 16. For T2: must be a single value—multiple values are not allowed.
PDelivery Start Date49Mandatory; must be in YYYY-MM-DD format.
QDelivery End Date50Mandatory; must be in YYYY-MM-DD format.

Validation Rules for Contract ID (T2) Generation

Excel ColumnACER Table 2 DataACER Field No.Remarks
BID of Market Participant1Mandatory; must be an ACER code ([A-Za-z0-9_]+\.[A-Z][A-Z]) with a length of 12.
CID of Other MP3Mandatory; must be an ACER code ([A-Za-z0-9_]+\.[A-Z][A-Z]) with a length of 12. Must be a single value—multiple values are not allowed.
JContract Type13Mandatory; must be one of: FW, OP, OP_FW, OP_SW, SP, SW, OT.
KEnergy Commodity14Mandatory; must be one of: EL, NG.
VSettlement Method31Mandatory; must be one of: P, C, O.
ITrade Date12Mandatory; must be in YYYY-MM-DD format.
LPrice15Optional; must be a valid decimal number, up to 20 digits total, with a dot (.) as the decimal mark and 5 decimal places (fill with zeros if necessary).
MCurrency15Mandatory if Price is given; must be one of: BGN, CHF, CZK, DKK, EUR, GBP, HRK, HUF, ISK, NOK, PCT, PLN, RON, SEK, USD, OTH.
QQuantity Volume18Optional; must be a valid decimal number, up to 20 digits total, with a dot (.) as the decimal mark and 5 decimal places (fill with zeros if necessary).
RQuantity Unit18Mandatory if Quantity Volume is given; must be one of: KWh/h, KWh/d, MWh/h, MWh/d, GWh/h, GWh/d, Therm/d, KTherm/d, MTherm/d, cm/d, mcm/d, Btu/d, MMBtu/d, MJ/d, 100MJ/d, MMJ/d, GJ/d. Do not simply use MW—always use MWh/h.
WDelivery Point or Zone41Mandatory; must match [0-9][0-9][XYZTWV].+ with a length of 16. Must be a single value—multiple values are not allowed.
XDelivery Start Date42Mandatory; must be in YYYY-MM-DD format.
YDelivery End Date43Mandatory; must be in YYYY-MM-DD format.

Still have questions?

Check our FAQ or get in touch directly.

Contact Us