Network Tariff Notification

The Network Tariff Notification (NTN) transaction type can be created with the bulk import option only. the contents of every line in the CSV file must use the following format:

<nmi>, <ntn_proposed_date>, <notice_end_date>, <proposed_ntc>, <reason_for_change>

Note:  No header row is required for the NTN CSV file.

Field Format Mandatory Definition
nmi Text (10 characters) Yes NMI for the connection point (meter) where the Network Tariff change is to occur, excluding the checksum.
ntn_proposed_date CCYYMMDD Yes This is the proposed date of the Network Tariff change by the LNSP.
notice_end_date CCYYMMDD No This is the latest date the LNSP can effect a Network Tariff change without initiating a new NTN.Where application of this procedure is mandatory this date must be provided.
proposed_ntc Text (10 characters) Yes This is the new Network Tariff Code being proposed for that NMI.
reason_for_change Text (20 characters) Yes This is the reason for Network Tariff change. The following values are allowable:
  • No Change
  • DNSP Review
  • Change of NMI Classification
  • Retailer/MC Meter Roll Out
  • Regulator Review
  • Cust Request
  • Other
Note: MTS does not validate the reason_for_change. It is the responsibility of the user to ensure that only valid reasons according to the procedures are included in the file.

MTS will apply the following validation rules to the entire file. If any of these conditions are met, the entire file will be rejected. In the case of multiple errors, only the first one encountered is reported.

Order Validation Description Message
1 Too many columns A row has too many columns specified. Too many columns (i.e. extra commas)
2 Too few columns A row does not have enough columns specified. Too few columns
3 Too many rows The file has more than 1000 rows. Too many rows (> 1000)