Common use of Voluntary discontinuance Clause in Contracts

Voluntary discontinuance. 4.2.1 A User may at any time by giving notice ("Discontinuance Notice") to the Transporter apply to cease to be a User of or in relation to a System. 4.2.2 A User may not cease to be a User under this paragraph 4.2 until such time as: (a) all amounts payable or (other than in respect of any recurrent charge becoming payable by reason only of the lapse of time after the date on which the last of the other requirements of this paragraph 4.2.2 is satisfied) which may become payable by the User to the Transporter pursuant to any provision of the Code, the Shipper Framework Agreement or any Ancillary Agreement have been paid in full; (b) the User is not the Registered User in respect of any Supply Point and is not party to any Shared Supply Meter Notification; (c) under National Grid NTS's Network Code, there is no outstanding Daily Imbalance or NDM Reconciliation Quantity or DM Reconciliation Quantity in respect of the User; (d) any requirements under any Ancillary Agreement in respect of termination under this paragraph 4.2 have been complied with; (e) any outstanding breach, being a breach capable of remedy and of which the Transporter has given notice to the User, by the User of any provision of the Code or the Shipper Framework Agreement or any Ancillary Agreement shall have been remedied; and (f) the User (if a Shipper User) has satisfied the Withdrawal Requirements (as defined in the DSC, or (if a Trader User) has satisfied the requirements for voluntary termination of the UK Link User Agreement; and a User may not cease to be a User of the NTS until the User ceases to be a User of each LDZ. 4.2.3 Where a User has given notice under paragraph 4.2.1: (a) the User and the Transporter shall remain bound by the Code and the Shipper Framework Agreement and any Ancillary Agreement to which the User is party until the requirements of paragraph 4.2.2 are satisfied; (b) the System Capacity which the User is registered as holding shall not be reduced or cancelled other than in accordance with the relevant provisions of the Code (and the User will remain liable for payment of Transportation Charges in respect thereof but may elect to make prepayment thereof). 4.2.4 Where a User has given notice under paragraph 4.2.1, after the satisfaction of the last of the requirements of paragraph 4.2.2 to be satisfied: (a) with effect from the 5th Business Day following such satisfaction, the User will cease to be a User; (b) without prejudice to paragraph 4.2.5, the Transporter will as soon as reasonably practicable (and where possible before such date) inform the User of the date on which it ceases to be a User under paragraph (a). 4.2.5 Notwithstanding paragraph 4.2.4, without prejudice to paragraph 4.1.2(a), the Transporter or (as the case may be) the Discontinuing User shall remain liable, subject to and in accordance with the Code, to the other and (in the case of the Discontinuing User, subject to paragraph GT Section B2.4.2) to each other User, after the User Discontinuance Date: (a) for any amount which was or becomes payable under the Code or any Ancillary Agreement in respect of any period before the User Discontinuance Date; and (b) in respect of any outstanding breach of any provision of the Code, the Shipper Framework Agreement or any Ancillary Agreement where such breach was not (for the purposes of paragraph 4.2.2(e)) capable of remedy or (notwithstanding that paragraph) was capable of remedy but was not remedied.

Voluntary discontinuance. 4.2.1 A User may at any time by giving notice ("Discontinuance Notice") to the Transporter apply to cease to be a User of or in relation to a System. 4.2.2 A User may not cease to be a User under this paragraph 4.2 until such time as: (a) all amounts payable or (other than in respect of any recurrent charge becoming payable by reason only of the lapse of time after the date on which the last of the other requirements of this paragraph 4.2.2 is satisfied) which may become payable by the User to the Transporter pursuant to any provision of the Code, the Shipper Framework Agreement or any Ancillary Agreement have been paid in full; (b) the User is not the Registered User in respect of any Supply Point and is not party to any Shared Supply Meter Notification; (c) the User has complied with the requirements of Section U2.8; (d) under National Grid NTS's Network Code, there is no outstanding Daily Imbalance or NDM Reconciliation Quantity or DM Reconciliation Quantity in respect of the User; (de) any requirements under any Ancillary Agreement in respect of termination under this paragraph 4.2 have been complied with;; and (ef) any outstanding breach, being a breach capable of remedy and of which the Transporter has given notice to the User, by the User of any provision of the Code or the Shipper Framework Agreement or any Ancillary Agreement shall have been remedied; and (fg) the User (if a Shipper User) has satisfied the Withdrawal Requirements (as defined in the DSC, or (if a Trader User) has satisfied the requirements for voluntary termination of the UK Link User Agreement; and a User may not cease to be a User of the NTS until the User ceases to be a User of each LDZ. 4.2.3 Where a User has given notice under paragraph 4.2.1: (a) the User and the Transporter shall remain bound by the Code and the Shipper Framework Agreement and any Ancillary Agreement to which the User is party until the requirements of paragraph 4.2.2 are satisfied; (b) the System Capacity which the User is registered as holding shall not be reduced or cancelled other than in accordance with the relevant provisions of the Code (and the User will remain liable for payment of Transportation Charges in respect thereof but may elect to make prepayment thereof). 4.2.4 Where a User has given notice under paragraph 4.2.1, after the satisfaction of the last of the requirements of paragraph 4.2.2 to be satisfied: (a) with effect from the 5th Business Day following such satisfaction, the User will cease to be a User; (b) without prejudice to paragraph 4.2.5, the Transporter will as soon as reasonably practicable (and where possible before such date) inform the User of the date on which it ceases to be a User under paragraph (a). 4.2.5 Notwithstanding paragraph 4.2.4, without prejudice to paragraph 4.1.2(a), the Transporter or (as the case may be) the Discontinuing User shall remain liable, subject to and in accordance with the Code, to the other and (in the case of the Discontinuing User, subject to paragraph GT Section B2.4.2) to each other User, after the User Discontinuance Date: (a) for any amount which was or becomes payable under the Code or any Ancillary Agreement in respect of any period before the User Discontinuance Date; and (b) in respect of any outstanding breach of any provision of the Code, the Shipper Framework Agreement or any Ancillary Agreement where such breach was not (for the purposes of paragraph 4.2.2(e4.2.2(f)) capable of remedy or (notwithstanding that paragraph) was capable of remedy but was not remedied.

Voluntary discontinuance. 4.2.1 A User may at any time by giving notice ("Discontinuance Notice") to the Transporter apply to cease to be a User of or in relation to a System. 4.2.2 A User may not cease to be a User under this paragraph 4.2 until such time as: (a) all amounts payable or (other than in respect of any recurrent charge becoming payable by reason only of the lapse of time after the date on which the last of the other requirements of this paragraph 4.2.2 is satisfied) which may become payable by the User to the Transporter pursuant to any provision of the Code, the Shipper Framework Agreement or any Ancillary Agreement have been paid in full; (b) the User is not the Registered User in respect of any Supply Point and is not party to any Shared Supply Meter Notification; (c) under National Grid NTSGas Transmission's Network Code, there is no outstanding Daily Imbalance or NDM Reconciliation Quantity or DM Reconciliation Quantity in respect of the User; (d) any requirements under any Ancillary Agreement in respect of termination under this paragraph 4.2 have been complied with; (e) any outstanding breach, being a breach capable of remedy and of which the Transporter has given notice to the User, by the User of any provision of the Code or the Shipper Framework Agreement or any Ancillary Agreement shall have been remedied; and (f) the User (if a Shipper User) has satisfied the Withdrawal Requirements (as defined in the DSC, or (if a Trader User) has satisfied the requirements for voluntary termination of the UK Link User Agreement; and a User may not cease to be a User of the NTS until the User ceases to be a User of each LDZ. 4.2.3 Where a User has given notice under paragraph 4.2.1: (a) the User and the Transporter shall remain bound by the Code and the Shipper Framework Agreement and any Ancillary Agreement to which the User is party until the requirements of paragraph 4.2.2 are satisfied; (b) the System Capacity which the User is registered as holding shall not be reduced or cancelled other than in accordance with the relevant provisions of the Code (and the User will remain liable for payment of Transportation Charges in respect thereof but may elect to make prepayment thereof). 4.2.4 Where a User has given notice under paragraph 4.2.1, after the satisfaction of the last of the requirements of paragraph 4.2.2 to be satisfied: (a) with effect from the 5th Business Day following such satisfaction, the User will cease to be a User; (b) without prejudice to paragraph 4.2.5, the Transporter will as soon as reasonably practicable (and where possible before such date) inform the User of the date on which it ceases to be a User under paragraph (a). 4.2.5 Notwithstanding paragraph 4.2.4, without prejudice to paragraph 4.1.2(a), the Transporter or (as the case may be) the Discontinuing User shall remain liable, subject to and in accordance with the Code, to the other and (in the case of the Discontinuing User, subject to paragraph GT Section B2.4.2) to each other User, after the User Discontinuance Date: (a) for any amount which was or becomes payable under the Code or any Ancillary Agreement in respect of any period before the User Discontinuance Date; and (b) in respect of any outstanding breach of any provision of the Code, the Shipper Framework Agreement or any Ancillary Agreement where such breach was not (for the purposes of paragraph 4.2.2(e)) capable of remedy or (notwithstanding that paragraph) was capable of remedy but was not remedied.

Voluntary discontinuance. 4.2.1 A User may at any time by giving notice ("Discontinuance Notice") to the Transporter apply to cease to be a User of or in relation to a System. 4.2.2 A User may not cease to be a User under this paragraph 4.2 until such time as: (a) all amounts payable or (other than in respect of any recurrent charge becoming payable by reason only of the lapse of time after the date on which the last of the other requirements of this paragraph 4.2.2 is satisfied) which may become payable by the User to the Transporter pursuant to any provision of the Code, the Shipper Framework Agreement or any Ancillary Agreement have been paid in full; (b) the User is not the Registered User in respect of any Supply Point and is not party to any Shared Supply Meter Notification; (c) under National Grid NTS's Network Code, there is no outstanding Daily Imbalance or NDM Reconciliation Quantity or DM Reconciliation Quantity in respect of the User; (d) any requirements under any Ancillary Agreement in respect of termination under this paragraph 4.2 have been complied with; (e) any outstanding breach, being a breach capable of remedy and of which the Transporter has given notice to the User, by the User of any provision of the Code or the Shipper Framework Agreement or any Ancillary Agreement shall have been remedied; and (f) the User (if a Shipper User) has satisfied the Withdrawal Requirements (as defined in the DSC, or (if a Trader User) has satisfied the requirements for voluntary termination of the UK Link User Agreement; and a User may not cease to be a User of the NTS until the User ceases to be a User of each LDZ. 4.2.3 Where a User has given notice under paragraph 4.2.1: (a) the User and the Transporter shall remain bound by the Code and the Shipper Framework Agreement and any Ancillary Agreement to which the User is party until the requirements of paragraph 4.2.2 are satisfied; (b) the System Capacity which the User is registered as holding shall not be reduced or cancelled other than in accordance with the relevant provisions of the Code (and the User will remain liable for payment of Transportation Charges in respect thereof but may elect to make prepayment thereof). 4.2.4 Where a User has given notice under paragraph 4.2.1, after the satisfaction of the last of the requirements of paragraph 4.2.2 to be satisfied: : Uniform Network Code – Transportation Principal Document Section V (a) with effect from the 5th Business Day following such satisfaction, the User will cease to be a User; (b) without prejudice to paragraph 4.2.5, the Transporter will as soon as reasonably practicable (and where possible before such date) inform the User of the date on which it ceases to be a User under paragraph (a). 4.2.5 Notwithstanding paragraph 4.2.4, without prejudice to paragraph 4.1.2(a), the Transporter or (as the case may be) the Discontinuing User shall remain liable, subject to and in accordance with the Code, to the other and (in the case of the Discontinuing User, subject to paragraph GT Section B2.4.2) to each other User, after the User Discontinuance Date: (a) for any amount which was or becomes payable under the Code or any Ancillary Agreement in respect of any period before the User Discontinuance Date; and (b) in respect of any outstanding breach of any provision of the Code, the Shipper Framework Agreement or any Ancillary Agreement where such breach was not (for the purposes of paragraph 4.2.2(e)) capable of remedy or (notwithstanding that paragraph) was capable of remedy but was not remedied.

Voluntary discontinuance. 4.2.1 A User may at any time by giving notice ("Discontinuance Notice") to the Transporter apply to cease to be a User of or in relation to a System. 4.2.2 A User may not cease to be a User under this paragraph 4.2 until such time as: (a) all amounts payable or (other than in respect of any recurrent charge becoming payable by reason only of the lapse of time after the date on which the last of the other requirements of this paragraph 4.2.2 is satisfied) which may become payable by the User to the Transporter pursuant to any provision of the Code, the Shipper Framework Agreement or any Ancillary Agreement have been paid in full; (b) the User is not the Registered User in respect of any Supply Point and is not party to any Shared Supply Meter Notification; (c) the User has complied with the requirements of Section U2.8; (d) under National Grid Transco NTS's Network Code, there is no outstanding Daily Imbalance or NDM Reconciliation Quantity or DM Reconciliation Quantity in respect of the User; (de) any requirements under any Ancillary Agreement in respect of termination under this paragraph 4.2 have been complied with;; and (ef) any outstanding breach, being a breach capable of remedy and of which the Transporter has given notice to the User, by the User of any provision of the Code or the Shipper Framework Agreement or any Ancillary Agreement shall have been remedied; and (f) the User (if a Shipper User) has satisfied the Withdrawal Requirements (as defined in the DSC, or (if a Trader User) has satisfied the requirements for voluntary termination of the UK Link User Agreement; remedied and a User may not cease to be a User of the NTS until the User ceases to be a User of each LDZ. 4.2.3 Where a User has given notice under paragraph 4.2.1: (a) the User and the Transporter shall remain bound by the Code and the Shipper Framework Agreement and any Ancillary Agreement to which the User is party until the requirements of paragraph 4.2.2 are satisfied; (b) the System Capacity which the User is registered as holding shall not be reduced or cancelled other than in accordance with the relevant provisions of the Code (and the User will remain liable for payment of Transportation Charges in respect thereof but may elect to make prepayment thereof). 4.2.4 Where a User has given notice under paragraph 4.2.1, after the satisfaction of the last of the requirements of paragraph 4.2.2 to be satisfied: (a) with effect from the 5th Business Day following such satisfaction, the User will cease to be a User; (b) without prejudice to paragraph 4.2.5, the Transporter will as soon as reasonably practicable (and where possible before such date) inform the User of the date on which it ceases to be a User under paragraph (a). 4.2.5 Notwithstanding paragraph 4.2.4, without prejudice to paragraph 4.1.2(a), the Transporter or (as the case may be) the Discontinuing User shall remain liable, subject to and in accordance with the Code, to the other and (in the case of the Discontinuing User, subject to paragraph GT Section B2.4.2) to each other User, after the User Discontinuance Date: (a) for any amount which was or becomes payable under the Code or any Ancillary Agreement in respect of any period before the User Discontinuance Date; and (b) in respect of any outstanding breach of any provision of the Code, the Shipper Framework Agreement or any Ancillary Agreement where such breach was not (for the purposes of paragraph 4.2.2(e4.2.2(f)) capable of remedy or (notwithstanding that paragraph) was capable of remedy but was not remedied.

Voluntary discontinuance. 4.2.1 A User may at any time by giving notice ("Discontinuance Notice") to the Transcothe Transporter apply to cease to be a User of or in relation to a SystemUser. 4.2.2 A User may not cease to be a User under this paragraph 4.2 until such time as: (a) all amounts payable or (other than in respect of any recurrent charge becoming payable by reason only of the lapse of time after the date on which the last of the other requirements of this paragraph 4.2.2 is satisfied) which may become payable by the User to the Transcothe Transporter pursuant to any provision of the Code, the Shipper Framework Agreement or any Ancillary Agreement have been paid in full; (b) the User is not the Registered User in respect of any Supply Point and is not party to any Shared Supply Meter Notification; (c) the User has complied with the requirements of Section U2.8; (d) under National Grid Transco NTS's Network Code, there is no outstanding Daily Imbalance or NDM Reconciliation Quantity or DM Reconciliation Quantity in respect of the User; (de) any requirements under any Ancillary Agreement in respect of termination under this paragraph 4.2 have been complied with;; and (ef) any outstanding breach, being a breach capable of remedy and of which the Transcothe Transporter has given notice to the User, by the User of any provision of the Code or the Shipper Framework Agreement or any Ancillary Agreement shall have been remedied; and (fg) under Transco NTS's Code, the User (if a Shipper User) has satisfied the Withdrawal Requirements (as defined in the DSC, or (if a Trader User) has satisfied the requirements for voluntary termination of the UK Link User Agreement; and a User may not cease ceased to be a User of the NTS until the User ceases to be a User of bound each LDZother Transporter's Code. 4.2.3 Where a User has given notice under paragraph 4.2.1: (a) the User and the Transcothe Transporter shall remain bound by the Code and the Shipper Framework Agreement and any Ancillary Agreement to which the User is party until the requirements of paragraph 4.2.2 are satisfied; (b) the System Capacity which the User is registered as holding shall not be reduced or cancelled other than in accordance with the relevant provisions of the Code (and the User will remain liable for payment of Transportation Charges in respect thereof but may elect to make prepayment thereof). 4.2.4 Where a User has given notice under paragraph 4.2.1, after the satisfaction of the last of the requirements of paragraph 4.2.2 to be satisfied: (a) with effect from the 5th Business Day following such satisfaction, the User will cease to be a User; (b) without prejudice to paragraph 4.2.5, the Transporter will as soon as reasonably practicable (and where possible before such date) inform the User of the date on which it ceases to be a User under paragraph (a). 4.2.5 Notwithstanding paragraph 4.2.4, without prejudice to paragraph 4.1.2(a), the Transporter or (as the case may be) the Discontinuing User shall remain liable, subject to and in accordance with the Code, to the other and (in the case of the Discontinuing User, subject to paragraph GT Section B2.4.2) to each other User, after the User Discontinuance Date: (a) for any amount which was or becomes payable under the Code or any Ancillary Agreement in respect of any period before the User Discontinuance Date; and (b) in respect of any outstanding breach of any provision of the Code, the Shipper Framework Agreement or any Ancillary Agreement where such breach was not (for the purposes of paragraph 4.2.2(e)) capable of remedy or (notwithstanding that paragraph) was capable of remedy but was not remedied.

Voluntary discontinuance. 4.2.1 A User may at any time by giving notice ("Discontinuance Notice") to the Transporter apply to cease to be a User of or in relation to a SystemUser. 4.2.2 A User may not cease to be a User under this paragraph 4.2 until such time as: (a) all amounts payable or (other than in respect of any recurrent charge becoming payable by reason only of the lapse of time after the date on which the last of the other requirements of this paragraph 4.2.2 is satisfied) which may become payable by the User to the Transporter pursuant to any provision of the Code, the Shipper Framework Agreement or any Ancillary Agreement have been paid in full; (b) the User is not the Registered User in respect of any Supply Point and is not party to any Shared Supply Meter Notification; (c) the User has complied with the requirements of Section U2.8; (d) under National Grid Transco NTS's Network Code, there is no outstanding Daily Imbalance or NDM Reconciliation Quantity or DM Reconciliation Quantity in respect of the User; (de) any requirements under any Ancillary Agreement in respect of termination under this paragraph 4.2 have been complied with; (ef) any outstanding breach, being a breach capable of remedy and of which the Transporter has given notice to the User, by the User of any provision of the Code or the Shipper Framework Agreement or any Ancillary Agreement shall have been remedied; and (fg) under Transco NTS's Code, the User (if a Shipper User) has satisfied the Withdrawal Requirements (as defined in the DSC, or (if a Trader User) has satisfied the requirements for voluntary termination of the UK Link User Agreement; and a User may not cease ceased to be a User of the NTS until the User ceases to be a User of bound each LDZother Transporter's Code. 4.2.3 Where a User has given notice under paragraph 4.2.1: (a) the User and the Transporter shall remain bound by the Code and the Shipper Framework Agreement and any Ancillary Agreement to which the User is party until the requirements of paragraph 4.2.2 are satisfied; (b) the System Capacity which the User is registered as holding shall not be reduced or cancelled other than in accordance with the relevant provisions of the Code (and the User will remain liable for payment of Transportation Charges in respect thereof but may elect to make prepayment thereof). 4.2.4 Where a User has given notice under paragraph 4.2.1, after the satisfaction of the last of the requirements of paragraph 4.2.2 to be satisfied: (a) with effect from the 5th Business Day following such satisfaction, the User will cease to be a User; (b) without prejudice to paragraph 4.2.5, the Transporter will as soon as reasonably practicable (and where possible before such date) inform the User of the date on which it ceases to be a User under paragraph (a). 4.2.5 Notwithstanding paragraph 4.2.4, without prejudice to paragraph 4.1.2(a), the Transporter or (as the case may be) the Discontinuing User shall remain liable, subject to and in accordance with the Code, to the other and (in the case of the Discontinuing User, subject to paragraph GT Section B2.4.2) to each other User, after the User Discontinuance Date: (a) for any amount which was or becomes payable under the Code or any Ancillary Agreement in respect of any period before the User Discontinuance Date; and (b) in respect of any outstanding breach of any provision of the Code, the Shipper Framework Agreement or any Ancillary Agreement where such breach was not (for the purposes of paragraph 4.2.2(e4.2.2(vii)) capable of remedy or (notwithstanding that paragraph) was capable of remedy but was not remedied.

Voluntary discontinuance. 4.2.1 A User may at any time by giving notice ("Discontinuance Notice") to the Transporter apply to cease to be a User of or in relation to a System. 4.2.2 A User may not cease to be a User under this paragraph 4.2 until such time as: (a) all amounts payable or (other than in respect of any recurrent charge becoming payable by reason only of the lapse of time after the date on which the last of the other requirements of this paragraph 4.2.2 is satisfied) which may become payable by the User to the Transporter pursuant to any provision of the Code, the Shipper Framework Agreement or any Ancillary Agreement have been paid in full; (b) the User is not the Registered User in respect of any Supply Point and is not party to any Shared Supply Meter Notification; (c) the User has complied with the requirements of Section U2.8; (d) under National Grid NTS's Network Code, there is no outstanding Daily Imbalance or NDM Reconciliation Quantity or DM Reconciliation Quantity in respect of the User; (de) any requirements under any Ancillary Agreement in respect of termination under this paragraph 4.2 have been complied with;; and (ef) any outstanding breach, being a breach capable of remedy and of which the Transporter has given notice to the User, by the User of any provision of the Code or the Shipper Framework Agreement or any Ancillary Agreement shall have been remedied; andremedied 2 Implementation of modification 0195AV, effective 06:00hrs on 01 April 2009, will amend paragraph 4.1.6. (fg) the User (if a Shipper User) has satisfied the Withdrawal Requirements (as defined in the DSC, or (if a Trader User) has satisfied the requirements for voluntary termination of the UK Link User Agreement; and a User may not cease to be a User of the NTS until the User ceases to be a User of each LDZ. 4.2.3 Where a User has given notice under paragraph 4.2.1: (a) the User and the Transporter shall remain bound by the Code and the Shipper Framework Agreement and any Ancillary Agreement to which the User is party until the requirements of paragraph 4.2.2 are satisfied; (b) the System Capacity which the User is registered as holding shall not be reduced or cancelled other than in accordance with the relevant provisions of the Code (and the User will remain liable for payment of Transportation Charges in respect thereof but may elect to make prepayment thereof). 4.2.4 Where a User has given notice under paragraph 4.2.1, after the satisfaction of the last of the requirements of paragraph 4.2.2 to be satisfied: (a) with effect from the 5th Business Day following such satisfaction, the User will cease to be a User; (b) without prejudice to paragraph 4.2.5, the Transporter will as soon as reasonably practicable (and where possible before such date) inform the User of the date on which it ceases to be a User under paragraph (a). 4.2.5 Notwithstanding paragraph 4.2.4, without prejudice to paragraph 4.1.2(a), the Transporter or (as the case may be) the Discontinuing User shall remain liable, subject to and in accordance with the Code, to the other and (in the case of the Discontinuing User, subject to paragraph GT Section B2.4.2) to each other User, after the User Discontinuance Date: (a) for any amount which was or becomes payable under the Code or any Ancillary Agreement in respect of any period before the User Discontinuance Date; and (b) in respect of any outstanding breach of any provision of the Code, the Shipper Framework Agreement or any Ancillary Agreement where such breach was not (for the purposes of paragraph 4.2.2(e4.2.2(f)) capable of remedy or (notwithstanding that paragraph) was capable of remedy but was not remedied.