Affordability Compliance, Covenant and Tax Exemption Reporting Sample Clauses

Affordability Compliance, Covenant and Tax Exemption Reporting. Within 120 days after the end of each Fiscal Year, Borrower shall deliver to Bondowner Representative the Compliance Certificate described in Section 7.10. Within 90 days after the Closing Date and thereafter within 120 days after the end of each tax year, Borrower shall deliver to Bondowner Representative evidence of tax exemption as required pursuant to Section 7.7.2.
AutoNDA by SimpleDocs

Related to Affordability Compliance, Covenant and Tax Exemption Reporting

  • GAAP Compliance Contractor maintains an adequate system of accounting and internal controls that meets Generally Accepted Accounting Principles.

  • AML Compliance The Dealer Manager represents to the Company that it has established and implemented anti-money laundering compliance programs in accordance with applicable law, including applicable FINRA Conduct Rules, Exchange Act Regulations and the USA PATRIOT Act, specifically including, but not limited to, Section 352 of the International Money Laundering Abatement and Anti-Terrorist Financing Act of 2001 (the “Money Laundering Abatement Act,” and together with the USA PATRIOT Act, the “AML Rules”) reasonably expected to detect and cause the reporting of suspicious transactions in connection with the offering and sale of the Offered Shares. The Dealer Manager further represents that it is currently in compliance with all AML Rules, specifically including, but not limited to, the Customer Identification Program requirements under Section 326 of the Money Laundering Abatement Act, and the Dealer Manager hereby covenants to remain in compliance with such requirements and shall, upon request by the Company, provide a certification to the Company that, as of the date of such certification (a) its AML Program is consistent with the AML Rules and (b) it is currently in compliance with all AML Rules, specifically including, but not limited to, the Customer Identification Program requirements under Section 326 of the Money Laundering Abatement Act.

  • Compliance Covenant The Company will not become a party to any Common Stock Change Event unless its terms are consistent with this Section 5.09.

  • FERPA Compliance In connection with all FERPA Records that Contractor may create, receive or maintain on behalf of University pursuant to the Underlying Agreement, Contractor is designated as a University Official with a legitimate educational interest in and with respect to such FERPA Records, only to the extent to which Contractor (a) is required to create, receive or maintain FERPA Records to carry out the Underlying Agreement, and (b) understands and agrees to all of the following terms and conditions without reservation:

  • Reporting Compliance The Company is subject to, and is in compliance in all material respects with, the reporting requirements of Section 13 and Section 15(d), as applicable, of the Exchange Act.

  • Policy Compliance Violations The Requester and Approved Users acknowledge that the NIH may terminate the DAR, including this Agreement and immediately revoke or suspend access to all controlled-access datasets subject to the NIH GDS Policy at any time if the Requester is found to be no longer in agreement with the principles outlined in the NIH GDS Policy, the terms described in this Agreement, or the Genomic Data User Code of Conduct. The Requester and PI agree to notify the NIH of any violations of the NIH GDS Policy, this Agreement, or the Genomic Data User Code of Conduct data within 24 hours of when the incident is identified. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification(s), the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.

  • SOX Compliance The Company has taken all actions it deems reasonably necessary or advisable to take on or prior to the date of this Agreement to assure that, upon and at all times after the Effective Date, it will be in compliance in all material respects with all applicable provisions of the Sxxxxxxx-Xxxxx Act of 2002 and all rules and regulations promulgated thereunder or implementing the provisions thereof. (the “Sxxxxxxx-Xxxxx Act”) that are then in effect and will take all action it deems reasonably necessary or advisable to assure that it will be in compliance in all material respects with other applicable provisions of the Sxxxxxxx-Xxxxx Act not currently in effect upon it and at all times after the effectiveness of such provisions.

  • CONTRACT COMPLIANCE REQUIREMENT The HUB requirement on this Contract is 0%. The student engagement requirement of this Contract is 0 hours. The Career Education requirement for this Contract is 0 hours. Failure to achieve these requirements may result in the application of some or all of the sanctions set forth in Administrative Policy 3.10, which is hereby incorporated by reference.

  • Compliance Reporting a. Provide reports to the Securities and Exchange Commission, the National Association of Securities Dealers and the States in which the Fund is registered. b. Prepare and distribute appropriate Internal Revenue Service forms for corresponding Fund and shareholder income and capital gains. c. Issue tax withholding reports to the Internal Revenue Service.

  • CEQA Compliance The District has complied with all assessment requirements imposed upon it by the California Environmental Quality Act (Public Resource Code Section 21000 et seq. (“CEQA”) in connection with the Project, and no further environmental review of the Project is necessary pursuant to CEQA before the construction of the Project may commence.

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