Standards Compliance Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).
Compliance Monitoring Grantee must be subject to compliance monitoring during the period of performance in which funds are Expended and up to three years following the closeout of all funds. In order to assure that the program can be adequately monitored, the following is required of Grantee: a. Grantee must maintain a financial tracking system provided by Florida Housing that ensures that CRF funds are Expended in accordance with the requirements in this Agreement. b. Grantee must maintain records on all awards to Eligible Persons or Households. These records must include, but are not limited to: i. Proof of income compliance (documentation from submission month, including but not limited to paystub, Florida unemployment statement, social security and/or disability statement, etc.); ii. Lease; and iii. Documentation of rental assistance payments made.
Monitoring Compliance Upon the request of the Lender, but without incurring any liability beyond the Guaranteed Obligations, from time to time, Guarantor shall promptly provide to the Lender such documents, certificates and other information as may be deemed reasonably necessary to enable the Lender to perform its functions under the Servicing Agreement as the same relates to the Guarantor.
Compliance Audits D. 4.1 Compliance Audit(s). Without limiting the generality of section A.7.4 (Records Review), if requested by the Province from time to time, which request shall be at the Province’s sole discretion, the Recipient, at its own expense, will forthwith retain an independent third party auditor to conduct one or more compliance audits of the Recipient or any Project. The audit will be conducted in accordance with Canadian Generally Accepted Auditing Standards, as adopted by the Canadian Institute of Chartered Accountants, applicable as of the date on which a record is kept or required to be kept under such standards. In addition, the audit will assess the Recipient’s compliance with the terms of the Agreement and will address, with respect to each Project, without limitation, the following: (a) whether the Funds were spent in accordance with the Agreement and with due regard to economy, efficiency, and effectiveness; (b) the Project’s progress or state of completion; (c) whether the financial information the Recipient provided is complete, accurate, and timely, and in accordance with the Agreement; (d) whether the Recipient’s information and monitoring processes and systems are adequate to identify, capture, validate, and monitor the achievement of intended benefits of the Project; (e) the overall management and administration of the Project; (f) recommendations for improvement or redress; and (g) whether prompt and timely corrective action is taken on prior audit findings.
Compliance Audit LEA shall have the right but shall be under no obligation to conduct audit(s), from time to time, of Provider’s records concerning its compliance obligations as set forth in this Article V. Provider shall make such records and other documents available to LEA upon request.
DBE/HUB Compliance The Engineer’s subcontracting program shall comply with the requirements of Attachment H of the contract (DBE/HUB Requirements).
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.
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:
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.
Contractual and Operational Compliance Audits (a) ICANN may from time to time (not to exceed twice per calendar year) conduct, or engage a third party to conduct, contractual compliance audits to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. Such audits shall be tailored to achieve the purpose of assessing compliance, and ICANN will (a) give reasonable advance notice of any such audit, which notice shall specify in reasonable detail the categories of documents, data and other information requested by ICANN, and (b) use commercially reasonable efforts to conduct such audit during regular business hours and in such a manner as to not unreasonably disrupt the operations of Registry Operator. As part of such audit and upon request by ICANN, Registry Operator shall timely provide all responsive documents, data and any other information reasonably necessary to demonstrate Registry Operator’s compliance with this Agreement. Upon no less than ten (10) calendar days notice (unless otherwise agreed to by Registry Operator), ICANN may, as part of any contractual compliance audit, conduct site visits during regular business hours to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. ICANN will treat any information obtained in connection with such audits that is appropriately marked as confidential (as required by Section 7.15) as Confidential Information of Registry Operator in accordance with Section 7.15.