Certification of Performance Threshold; Financial Covenants Sample Clauses

Certification of Performance Threshold; Financial Covenants. By the ----------------------------------------------------------- twentieth (20th) day of each month commencing with the twenty-fifth (25th) full month subsequent to the Completion Date, Developer shall deliver to the City Developer's certificate stating (i) whether the Performance Threshold, Debt Coverage Ratio and Leverage Ratio have or have not each been met for the previous twelve (12) month period ending on the last day of the preceding month; and (ii) the amount of Net Worth as of the last day of the preceding month. If Developer shall fail to deliver such certificate within ten (10) Business Days after Developer's receipt of written notice of City's failure to receive such certificate, Developer shall be deemed to be in breach of Section 3.2 and shall be deemed to have failed to meet the Performance ----------- Threshold. The obligations of Developer under this Section 7.16 shall lapse and ------------ be of no further force or effect ten (10) years after the Execution Date.
AutoNDA by SimpleDocs
Certification of Performance Threshold; Financial Covenants. By the twentieth (20th) day of each month commencing with the twenty-fifth (25th) full month subsequent to the Completion Date, Developer shall deliver to the City Developer s certificate stating (i) whether the Performance Threshold, Debt Coverage Ratio, and Leverage Ratio {and Tangible Net Worth} have or have not each been met for the previous twelve (12) month period ending on the last day of the preceding month and (ii) the amount of Net Worth as of the last day of the preceding month. If Developer shall fail to deliver such certificate within ten (10) Business Days after Developer s receipt of written notice of City s failure to receive such certificate, Developer shall be deemed to be in breach of Section 3.2 and shall be deemed to have failed to meet the Performance Threshold. The obligations of Developer to include in such certificate a statement as to the Debt Coverage Ratio, Leverage Ratio or Net Worth shall lapse and be of no further force or effect seven (7) years after the Execution Date. 61. After correction, Section 7.17 of the Agreement shall state: Use of Project Premises. So long as casino gaming activities would be permitted by law to operate on the Project Premises (assuming the existence of a valid Casino License), the primary business to be operated on the Project Premises shall include casino gaming activities. The obligations of Developer under this Section 7.17 shall lapse and be of no further force or effect thirty-five (35) years after the Execution Date. {, provided however that Developer shall have the right at any time after thirty-five (35) years subsequent to the Completion Date, to request that City consent to waive such restriction, which consent shall not be unreasonably withheld; and provided further that Developer shall have no right to make any such request as long as there exists any uncured Event of Default. In the event such consent is granted, the parties hereto shall negotiate in good faith any changes to this Agreement necessary to conform this Agreement to such change in use.}
Certification of Performance Threshold; Financial Covenants. By the twentieth (20th) day of each month commencing with the twenty- fifth (25th) full month subsequent to the Completion Date, Developer shall deliver to the City Developer s certificate stating whether the Performance Threshold, Debt Coverage Ratio, Leverage Ratio and Tangible Net Worth have or have not each been met for the previous twelve (12) month period ending on the last day of the preceding month. If Developer shall fail to deliver such certificate within ten (10) Business Days after Developer s receipt of written notice of City s failure to receive such certificate, Developer shall be deemed to be in breach of Section 3.2 and shall be deemed to have failed to meet the Performance Threshold.

Related to Certification of Performance Threshold; Financial Covenants

  • Covenants of Performance Measurement No interference. Registry Operator shall not interfere with measurement Probes, including any form of preferential treatment of the requests for the monitored services. Registry Operator shall respond to the measurement tests described in this Specification as it would to any other request from an Internet user (for DNS and RDDS) or registrar (for EPP). ICANN testing registrar. Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. PUBLIC INTEREST COMMITMENTS Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.) Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-discrimination by establishing, publishing and adhering to clear registration policies.

  • Financial Covenant Required Actual Complies Maintain as indicated:

  • Specific Financial Covenants During the term of this Agreement, and thereafter for so long as there are any Obligations to Lender, Borrower covenants that, unless otherwise consented to by Lender in writing, it shall:

  • Financial Covenant Calculations The parties hereto acknowledge and agree that, for purposes of all calculations made in determining compliance for any applicable period with the financial covenants set forth in Section 5.9 and for purposes of determining the Applicable Percentage, (i) after consummation of any Permitted Acquisition, (A) income statement items and other balance sheet items (whether positive or negative) attributable to the Target acquired in such transaction shall be included in such calculations to the extent relating to such applicable period, subject to adjustments mutually acceptable to the Borrower and the Administrative Agent and (B) Indebtedness of a Target which is retired in connection with a Permitted Acquisition shall be excluded from such calculations and deemed to have been retired as of the first day of such applicable period and (ii) after any asset disposition permitted by Section 6.4, (A) income statement items, cash flow statement items and balance sheet items (whether positive or negative) attributable to the property or assets disposed of shall be excluded in such calculations to the extent relating to such applicable period, subject to adjustments mutually acceptable to the Borrower and the Administrative Agent and (B) Indebtedness that is repaid with the proceeds of such asset disposition shall be excluded from such calculations and deemed to have been repaid as of the first day of such applicable period.

  • Certain Financial Covenants In addition to the covenants described in Section 5.1 and Section 5.2, so long as any Commitment remains in effect, any Advance is outstanding or any amount is owing to any Lender hereunder or under any other Loan Document, the Borrower will perform and comply with each of the covenants set forth on Schedule VI.

  • Prohibition of Performance Requirements 1. The provisions of the Agreement on Trade-Related Investment Measures in Annex 1A to the WTO Agreement (TRIMs), which are not specifically mentioned in or modified by this Agreement, shall apply, mutatis mutandis, to this Agreement. 2. Member States shall undertake joint assessment on performance requirements no later than 2 years from the date of entry into force of this Agreement. The aim of such assessment shall include reviewing existing performance requirements and considering the need for additional commitments under this Article.

  • Availability of Performance Order If, and to the extent that, a breach of this contract has been caused by a Relevant Force Majeure Event, the Non-affected Party shall not be entitled to a Performance Order except to secure performance by the Affected Party of its obligations under this Clause 17.

  • Financial Covenants (a) The Borrower shall maintain or cause to be maintained records and accounts adequate to reflect in accordance with sound accounting practices the operations, resources and expenditures in respect of the Project of the departments or agencies of the Borrower responsible for carrying out the Project or any part thereof. (b) The Borrower shall: (i) have the records and accounts referred to in paragraph (a) of this Section including those for the Special Account for each fiscal year audited, in accordance with appropriate auditing principles consistently applied, by independent auditors acceptable to the Association; (ii) furnish to the Association, as soon as available, but in any case not later than six months after the end of each such year, a certified copy of the report of such audit by said auditors, of such scope and in such detail as the Association shall have reasonably requested; and (iii) furnish to the Association such other information concerning said records, accounts and the audit thereof as the Association shall from time to time reasonably request. (c) For all expenditures with respect to which withdrawals from the Credit Account were made on the basis of statements of expenditure, the Borrower shall: (i) maintain or cause to be maintained, in accordance with paragraph (a) of this Section, records and accounts reflecting such expenditures; (ii) retain, until at least one year after the Association has received the audit report for the fiscal year in which the last withdrawal from the Credit Account or payment out of the Special Account was made, all records (contracts, orders, invoices, bills, receipts and other documents) evidencing such expenditures; (iii) enable the Association’s representatives to examine such records; and (iv) ensure that such records and accounts are included in the annual audit referred to in paragraph (b) of this Section and that the report of such audit contains a separate opinion by said auditors as to whether the statements of expenditure submitted during such fiscal year, together with the procedures and internal controls involved in their preparation, can be relied upon to support the related withdrawals.

  • Compliance with Financial Covenants Schedule A attached hereto sets forth financial data and computations evidencing the Borrower’s compliance with certain covenants of the Agreement, all of which data and computations are true, complete and correct.

  • Financial Performance Covenants Notwithstanding anything to the contrary contained in Section 7.01, in the event that the U.S. Borrower fails to comply with the requirements of any Financial Performance Covenant, until the expiration of the 10th day subsequent to the date the certificate calculating such Financial Performance Covenant is required to be delivered pursuant to Section 5.04(c), Holdings shall have the right to issue Permitted Cure Securities for cash or otherwise receive cash contributions to the capital of Holdings, and, in each case, to contribute any such cash to the capital of Intermediate Holdings (which shall contribute all such cash to the capital of the U.S. Borrower) (collectively, the "Cure Right"), and upon the receipt by U.S. Borrower of such cash (the "Cure Amount") pursuant to the exercise by Holdings of such Cure Right such Financial Performance Covenant shall be recalculated giving effect to the following pro forma adjustments: (i) EBITDA shall be increased, solely for the purpose of measuring the Financial Performance Covenants and not for any other purpose under this Agreement, by an amount equal to the Cure Amount; and (ii) If, after giving effect to the foregoing recalculations, the U.S. Borrower shall then be in compliance with the requirements of all Financial Performance Covenants, the U.S. Borrower shall be deemed to have satisfied the requirements of the Financial Performance Covenants as of the relevant date of determination with the same effect as though there had been no failure to comply therewith at such date, and the applicable breach or default of the Financial Performance Covenants that had occurred shall be deemed cured for this purposes of the Agreement.

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