Termination Receipts Sample Clauses

Termination Receipts. (a) (i) In the event of an “Early Termination Event” as defined under the Swap Agreement, (a) any Swap Termination Payment made by the Swap Counterparty to the Swap Account and paid pursuant to Section 4.02(e)(viii) (“Swap Termination Receipts”) will be deposited in a segregated non-interest bearing account which shall be an Eligible Account established by the Securities Administrator (the “Swap Termination Receipts Account”) and (b) any amounts received from a replacement swap counterparty (“Swap Replacement Receipts”) will be deposited in a segregated non-interest bearing account which shall be an Eligible Account established by the Securities Administrator (the “Swap Replacement Receipts Account”). The Securities Administrator shall invest, or cause to be invested, funds held in the Swap Termination Receipts Account and the Swap Replacement Receipts Account in time deposits of the Securities Administrator as permitted pursuant to clause (ii) of the definition of Permitted Investments or as otherwise directed in writing by a majority of the Certificateholders. All such Permitted Investments must be payable on demand or mature on a Distribution Date or such other date as directed by the Certificateholders. All such Eligible Investments will be made in the name of the Trustee of the Supplemental Interest Trust (in its capacity as such) or its nominee. All income and gain realized from any such investment shall be deposited in the Termination Receipts Account or the Replacement Receipts Account, as applicable, and all losses, if any, shall be borne by the related account.
Sample 1Sample 2Sample 3See All (117)
AutoNDA by SimpleDocs
Termination Receipts. (a) In the event of an “Early Termination Event” as defined under the related Basis Risk Cap Agreement, (i) any Basis Risk Cap Termination Payment made by the related Basis Risk Cap Provider to the related Basis Risk Cap Account (“Basis Risk Cap Termination Receipts”) shall be deposited in a segregated non-interest bearing account which shall be a subaccount of the Basis Risk Reserve Fund and which shall be an Eligible Account established by the Securities Administrator (the “Basis Risk Cap Termination Receipts Account”) and (ii) any amounts received from a replacement Basis Risk Cap Provider (“Basis Risk Cap Replacement Receipts”) will be deposited in a segregated non-interest bearing account which shall be a subaccount of the Basis Risk Reserve Fund and which shall be an Eligible Account established by the Securities Administrator (the “Basis Risk Cap Replacement Receipts Account”). In the absence of written instructions, such funds held in any Basis Risk Cap Termination Receipts Account and any Basis Risk Cap Replacement Receipts Account shall remain uninvested. (b) Unless otherwise permitted by the Rating Agencies as evidenced in a written confirmation, the Depositor shall arrange for replacement Basis Risk Cap Agreement(s) and the Securities Administrator shall promptly, with the assistance and cooperation of the Depositor, use amounts on deposit in the related Basis Risk Cap Termination Receipts Account, if necessary, to enter into replacement Basis Risk Cap Agreement(s) which shall be executed and delivered by the Securities Administrator on behalf of the Trust Fund upon receipt of written confirmation from each Rating Agency that such replacement Basis Risk Cap Agreement(s) will not result in the reduction or withdrawal of the rating of any outstanding Class of Certificates with respect to which it is a Rating Agency.
Sample 1
Termination Receipts. In the event of an “
Sample 1
Termination Receipts. In the event of an early termination of a Yield Maintenance Agreement, (i) any termination payment made by the Yield Maintenance Counterparty to the Issuer ("Termination Receipts") will be deposited in a segregated account which shall be an Eligible Account established by the Indenture Trustee (the "Termination Receipts Account") and (ii) any amounts
Sample 1
Termination Receipts. 99 Section 5.10. Capitalized Interest Account.............................................................100 Section 5.11. The Certificate Insurance Policy.........................................................101 Section 5.12. Class X Account..........................................................................103 ARTICLE VI CONCERNING THE TRUSTEE EVENTS OF DEFAULT............................................................104
Sample 1

Related to Termination Receipts

  • Termination by Contractor Contractor may, at its option, terminate this Contract upon the failure of MPS to pay any amount, which may become due hereunder for a period of sixty (60) days following submission of appropriate billing and supporting documentation. Upon said termination, Contractor shall be paid the compensation due for all services rendered through the date of termination including any retainage.

  • TERMINATION FOR CAUSE BY CONTRACTOR 4.06.1 Contractor may terminate its performance under this Agreement only if the City defaults and fails to cure the default after receiving written notice of it. Default by the City occurs if the City fails to perform one or more of its material duties under this Agreement. If a default occurs and Contractor wishes to terminate the Agreement, then Contractor must deliver a written notice to the Director describing the default and the proposed termination date. The date must be at least 30 days after the Director receives the notice. Contractor, at its sole option, may extend the proposed termination date to a later date. If the City cures the default before the proposed termination date, then the proposed termination is ineffective. If the City does not cure the default before the proposed termination date, then Contractor may terminate its performance under this Agreement on the termination date

  • Termination by ICANN (a) ICANN may, upon notice to Registry Operator, terminate this Agreement if: (i) Registry Operator fails to cure (A) any fundamental and material breach of Registry Operator’s representations and warranties set forth in Article 1 or covenants set forth in Article 2, or (B) any breach of Registry Operator’s payment obligations set forth in Article 6 of this Agreement, each within thirty (30) calendar days after ICANN gives Registry Operator notice of such breach, which notice will include with specificity the details of the alleged breach, (ii) an arbitrator or court of competent jurisdiction has finally determined that Registry Operator is in fundamental and material breach of such covenant(s) or in breach of its payment obligations, and (iii) Registry Operator fails to comply with such determination and cure such breach within ten (10) calendar days or such other time period as may be determined by the arbitrator or court of competent jurisdiction. (b) ICANN may, upon notice to Registry Operator, terminate this Agreement if Registry Operator fails to complete all testing and procedures (identified by ICANN in writing to Registry Operator prior to the date hereof) for delegation of the TLD into the root zone within twelve (12) months of the Effective Date. Registry Operator may request an extension for up to additional twelve (12) months for delegation if it can demonstrate, to ICANN’s reasonable satisfaction, that Registry Operator is working diligently and in good faith toward successfully completing the steps necessary for delegation of the TLD. Any fees paid by Registry Operator to ICANN prior to such termination date shall be retained by ICANN in full. (c) ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) Registry Operator fails to cure a material breach of Registry Operator’s obligations set forth in Section 2.12 of this Agreement within thirty (30) calendar days of delivery of notice of such breach by ICANN, or if the Continued Operations Instrument is not in effect for greater than sixty (60) consecutive calendar days at any time following the Effective Date, (ii) an arbitrator or court of competent jurisdiction has finally determined that Registry Operator is in material breach of such covenant, and (iii) Registry Operator fails to cure such breach within ten (10) calendar days or such other time period as may be determined by the arbitrator or court of competent jurisdiction. (d) ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) Registry Operator makes an assignment for the benefit of creditors or similar act, (ii) attachment, garnishment or similar proceedings are commenced against Registry Operator, which proceedings are a material threat to Registry Operator’s ability to operate the registry for the TLD, and are not dismissed within sixty (60) calendar days of their commencement, (iii) a trustee, receiver, liquidator or equivalent is appointed in place of Registry Operator or maintains control over any of Registry Operator’s property, (iv) execution is levied upon any material property of Registry Operator, (v) proceedings are instituted by or against Registry Operator under any bankruptcy, insolvency, reorganization or other laws relating to the relief of debtors and such proceedings are not dismissed within sixty (60) calendar days of their commencement, or (vi) Registry Operator files for protection under the United States Bankruptcy Code, 11 U.S.C. Section 101, et seq., or a foreign equivalent or liquidates, dissolves or otherwise discontinues its operations or the operation of the TLD. (e) ICANN may, upon thirty (30) calendar days’ notice to Registry Operator, terminate this Agreement pursuant to Section 2 of Specification 7 or Sections 2 and 3 of Specification 11, subject to Registry Operator’s right to challenge such termination as set forth in the applicable procedure described therein. (f) ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) Registry Operator knowingly employs any officer who is convicted of a misdemeanor related to financial activities or of any felony, or is judged by a court of competent jurisdiction to have committed fraud or breach of fiduciary duty, or is the subject of a judicial determination that ICANN reasonably deems as the substantive equivalent of any of the foregoing and such officer is not terminated within thirty (30) calendar days of Registry Operator’s knowledge of the foregoing, or (ii) any member of Registry Operator’s board of directors or similar governing body is convicted of a misdemeanor related to financial activities or of any felony, or is judged by a court of competent jurisdiction to have committed fraud or breach of fiduciary duty, or is the subject of a judicial determination that ICANN reasonably deems as the substantive equivalent of any of the foregoing and such member is not removed from Registry Operator’s board of directors or similar governing body within thirty (30) calendar days of Registry Operator’s knowledge of the foregoing. (g) ICANN may, upon thirty (30) calendar days’ notice to Registry Operator, terminate this Agreement as specified in Section 7.5. (h) [Applicable to intergovernmental organizations or governmental entities only.] ICANN may terminate this Agreement pursuant to Section 7.16.

  • TERMINATION BY MPS - BREACH BY CONTRACTOR If Contractor fails to fulfill its obligations under this Contract in a timely or proper manner, or violates any of its provisions, MPS shall thereupon have the right to terminate it by giving five (5) days written notice before the effective date of termination of the Contract, specifying the alleged violations, and effective date of termination. The Contract shall not be terminated if, upon receipt of the notice, Contractor promptly cures the alleged violation with five (5) days. In the event of termination, MPS will only be liable for services rendered through the date of termination and not for the uncompleted portion, or for any materials or services purchased or paid for by Contractor for use in completing the Contract.

  • Termination by Provider This Agreement may be terminated by Provider in accordance with the following: (a) except for SAP’s breach of its obligations under Sections 8 or 9, thirty (30) days after Provider gives SAP notice of SAP’s breach of any provision of the Agreement, unless SAP has cured such breach during such thirty (30) day period; (b) immediately if (1) SAP commences negotiations with one or more of its creditors with a view to rescheduling major parts of its indebtedness or (2) SAP files for bankruptcy, has a petition for bankruptcy filed on its behalf which is not dismissed within sixty days of filing, becomes insolvent, or makes an assignment for the benefit of creditors; and/or (3) SAP breaches its obligations under Sections 8 and/or 9 [Intellectual Property Ownership, Confidentiality].

  • Obligation after the termination of personal data processing services

  • Rights of Termination 10.1 The Company may in its sole discretion terminate this agreement by written notice to the Customer if: (a) The Customer defaults in performing its obligations under this agreement and the default, if capable of being remedied, is not remedied within seven (7) days from receiving a notice specifying the default and requiring remedy; or (b) The Customer defaults in the performance of its obligations under this agreement and the default is in the Company’s reasonable opinion incapable of being remedied; or (c) The Customer commits an act of insolvency including a compromise with creditors or appoints a voluntary administrator; or if a receiver is appointed in respect of the assets of the Customer; or if an arrangement with the Customer’s creditors is made or likely to be made; or if the Customer ceases or threatens to cease carrying on business; or if the ownership or effective control of the Customer is transferred or the nature of the Customer’s business is materially altered, or the Customer is adjudicated bankrupt. 10.2 Termination of this agreement will not prejudice or affect the rights, remedies and claims and/or any liabilities of the Company. The Company shall have no liability or responsibility whatsoever to the Customer for any loss or damage of any kind which may result directly or indirectly from such termination of this agreement.

  • Termination by Client Without prejudice to any rights or remedies of the Client, the Client may, by at least seven (7) days’ notice in writing to Deswik, terminate this Agreement if: (a) Deswik breaches its obligations under this Agreement and: (i) the breach is not capable of remedy; (ii) if capable of remedy, the breach is not remedied within 30 days of receipt of written notice by Deswik requiring the breach to be remedied; or (b) an Insolvency Event occurs in respect to Deswik.

  • Notification of Termination 22.3.2.1 Upon the occurrence at District's sole determination of any of the above conditions, or upon Developer’s failure to perform any material covenant, condition or agreement in this Facilities Lease, District may, without prejudice to any other right or remedy, serve written notice upon Developer and its Surety of District's termination of this Facilities Lease and/or Developer’s right to perform the Work of this Facilities Lease. This notice will contain the reasons for termination. 22.3.2.2 Unless, within fifteen (15) days after the service of the notice, any and all condition(s) shall cease, and any and all violation(s) shall cease, or arrangement satisfactory to District for the correction of the condition(s) and/or violation(s) be made, this Facilities Lease and the Site Lease shall cease and terminate; provided, however, if the failure stated in the notice cannot be corrected within fifteen (15) days after the service of notice, District may consent to an extension of time, provided Developer instituted and diligently pursued corrective action within the applicable fifteen (15)-day period and until the violation is corrected. Upon District determination, Developer shall not be entitled to receive any further payment until the entire Work is finished. 22.3.2.3 Upon Termination, District may immediately serve written notice of tender upon Surety whereby Surety shall have the right to take over and perform this Facilities Lease only if Surety: 22.3.2.3.1 Within three (3) days after service upon it of the notice of tender, gives District written notice of Surety’s intention to take over and perform this Facilities Lease; and 22.3.2.3.2 Commences performance of this Facilities Lease within three (3) days from date of serving of its notice to District. 22.3.2.4 Surety shall not utilize Developer in completing the Project if the District notifies Surety of the District’s objection to Developer’s further participation in the completion of the Project. Surety expressly agrees that any developer which Xxxxxx proposes to fulfill Surety’s obligations is subject to District’s approval. 22.3.2.5 If Surety fails to notify District or begin performance as indicated herein, District may take over the Work and execute the Work to completion by any method it may deem advisable at the expense of Developer and/or its Surety. Developer and its Surety shall be liable to District for any excess cost or other damages the District incurs thereby. Time is of the essence in this Facilities Lease. If the District takes over the Work as herein provided, District may, without liability for so doing, take possession of and utilize in completing the Work all materials, appliances, plan, and other property belonging to Developer as may be on the Site of the Work, in bonded storage, or previously paid for.

  • Termination by CAISO Subject to Section 5.2, the CAISO may terminate this Agreement by giving written notice of termination in the event that the Participating Load commits any material default under this Agreement and/or the CAISO Tariff which, if capable of being remedied, is not remedied within thirty (30) days after the CAISO has given, to the Participating Load, written notice of the default, unless excused by reason of Uncontrollable Forces in accordance with Article X of this Agreement. With respect to any notice of termination given pursuant to this Section, the CAISO must file a timely notice of termination with FERC, if this Agreement was filed with FERC, or must otherwise comply with the requirements of FERC Order No. 2001 and related FERC orders. The filing of the notice of termination by the CAISO with FERC will be considered timely if: (1) the filing of the notice of termination is made after the preconditions for termination have been met, and the CAISO files the notice of termination within sixty (60) days after issuance of the notice of default; or (2) the CAISO files the notice of termination in accordance with the requirements of FERC Order No. 2001. This Agreement shall terminate upon acceptance by FERC of such a notice of termination, if filed with FERC, or thirty (30) days after the date of the CAISO’s notice of default, if terminated in accordance with the requirements of FERC Order No. 2001 and related FERC orders.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!