Limitations on Future Obligations Secured by Net Revenues Sample Clauses

Limitations on Future Obligations Secured by Net Revenues. (a) No Obligations Superior to Bonds or Parity Obligations. In order to protect further the availability of the Net Revenues and the security for the Bonds and any Parity Obligations, the Authority covenants that no additional bonds or other indebtedness will be issued or incurred on a senior basis to the Bonds or such Parity Obligations that are payable out of the Net Revenues in whole or in part.
AutoNDA by SimpleDocs
Limitations on Future Obligations Secured by Net Revenues 

Related to Limitations on Future Obligations Secured by Net Revenues

  • Limitations on Shared-Loss Payment The Receiver shall not be required to make any payments pursuant to Section 2.1(d) with respect to any Foreclosure Loss, Restructuring Loss, Short Sale Loss, Deficient Loss, or Portfolio Loss that the Receiver determines, based upon the criteria set forth in this Single Family Shared-Loss Agreement (including the analysis and documentation requirements of Section 2.1(a)) or Customary Servicing Procedures, should not have been effected by the Assuming Institution; provided, however, (x) the Receiver must provide notice to the Assuming Institution detailing the grounds for not making such payment, (y) the Receiver must provide the Assuming Institution with a reasonable opportunity to cure any such deficiency and (z) (1) to the extent curable, if cured, the Receiver shall make payment with respect to the properly effected Loss, and (2) to the extent not curable, shall not constitute grounds for the Receiver to withhold payment as to all other Losses (or portion of Losses) that are properly payable pursuant to the terms of this Single Family Shared-Loss Agreement. In the event that the Receiver does not make any payment with respect to Losses claimed pursuant to Section 2.1(d), the Receiver and Assuming Institution shall, upon final resolution, make the necessary adjustments to the Monthly Shared-Loss Amount for that Monthly Certificate and the payment pursuant to Section 2.1(d) above shall be adjusted accordingly.

  • Obligations on Termination If this Agreement is completed, expires, or is terminated in whole or in part for any reason, then:

  • Limitations on Our Liability We try to ensure that you can always use your card. Occasionally, however, you may not be able to do so because of systems or communication problems involving a merchant, the network or us. We may also block use of your card or a particular type of transaction for any reason and without telling you, including in cases where we suspect unauthorized or fraudulent use of the card. Under no circumstances are we liable to you if you cannot use your card.

  • Supplier’s Obligations on Termination Unless otherwise specified by Buyer, upon Supplier’s receipt of a notice of termination of this Order, Supplier shall promptly: (a) stop work as directed in the notice; (b) place no further subcontracts/orders related to the terminated portion of this Order; (c) terminate, or if requested by Buyer assign, all subcontracts/orders to the extent they relate to work terminated; (d) deliver all completed work, work in process, designs, drawings, specifications, documentation and material required and/or produced in connection with such work; and (e) return or destroy all Confidential Information as set forth in Section 16(d).

  • Restrictions on Payments An employee shall not be entitled to payment for inclement weather as provided for in this clause unless the employee remains on the job until the provisions set out in this clause have been observed.

  • Obligation to Make Payments Any Interconnection Party's obligation to make payments for services shall not be suspended by Force Majeure.

  • Sub-processor Obligations MailChimp shall: (i) enter into a written agreement with the Sub-processor imposing data protection terms that require the Sub-processor to protect the Customer Data to the standard required by Data Protection Laws; and (ii) remain responsible for its compliance with the obligations of this DPA and for any acts or omissions of the Sub-processor that cause MailChimp to breach any of its obligations under this DPA.

  • Disclosure Obligations LAUSD expects Contractors and their Representatives to satisfy the following public disclosure obligations:

  • Additional Indemnity Obligations Consultant shall defend, with counsel of Town’s choosing and at Consultant's own cost, expense and risk, any and all claims, suits, actions or other proceedings of every kind covered by Section 3.5.6.1 that may be brought or instituted against Town or its directors, officials, officers, employees, volunteers and agents. Consultant shall pay and satisfy any judgment, award or decree that may be rendered against Town or its directors, officials, officers, employees, volunteers and agents as part of any such claim, suit, action or other proceeding. Consultant shall also reimburse Town for the cost of any settlement paid by Town or its directors, officials, officers, employees, agents or volunteers as part of any such claim, suit, action or other proceeding. Such reimbursement shall include payment for Town's attorney's fees and costs, including expert witness fees. Consultant shall reimburse Town and its directors, officials, officers, employees, agents, and/or volunteers, for any and all legal expenses and costs incurred by each of them in connection therewith or in enforcing the indemnity herein provided. Consultant's obligation to indemnify shall not be restricted to insurance proceeds, if any, received by the Town, its directors, officials officers, employees, agents, or volunteers.

  • Security Rule Obligations The following provisions of this section apply to the extent that Business Associate creates, receives, maintains or transmits Electronic PHI on behalf of Covered Entity.

Time is Money Join Law Insider Premium to draft better contracts faster.