Consultant Compliance Issues Sample Clauses

Consultant Compliance Issues. The Consultant shall comply with all laws, whether federal, provincial or state, applicable to the Consulting Services provided by it and, when requested by the Company, will advise the Company of any particular compliance issues affecting any Consulting Services for which the Consultant’s services have been engaged. The Consultant may, at its option, retain persons experienced in these matters to work with the Consultant and, subject to the Company’s consent first given, the fees and disbursements of such persons will be paid for by the Company.
AutoNDA by SimpleDocs

Related to Consultant Compliance Issues

  • OFAC Compliance (a) Tenant represents and warrants that (a) Tenant and each person or entity owning an interest in Tenant is (i) not currently identified on the Specially Designated Nationals and Blocked Persons List maintained by the Office of Foreign Assets Control, Department of the Treasury (“OFAC”) and/or on any other similar list maintained by OFAC pursuant to any authorizing statute, executive order or regulation (collectively, the “List”), and (ii) not a person or entity with whom a citizen of the United States is prohibited to engage in transactions by any trade embargo, economic sanction, or other prohibition of United States law, regulation, or Executive Order of the President of the United States, (b) none of the funds or other assets of Tenant constitute property of, or are beneficially owned, directly or indirectly, by any Embargoed Person (as hereinafter defined), (c) no Embargoed Person has any interest of any nature whatsoever in Tenant (whether directly or indirectly), (d) none of the funds of Tenant have been derived from any unlawful activity with the result that the investment in Tenant is prohibited by law or that the Lease is in violation of law, and (e) Tenant has implemented procedures, and will consistently apply those procedures, to ensure the foregoing representations and warranties remain true and correct at all times. The term “Embargoed Person” means any person, entity or government subject to trade restrictions under U.S. law, including but not limited to, the International Emergency Economic Powers Act, 50 U.S.C. §1701 et seq., The Trading with the Enemy Act, 50 U.S.C. App. 1 et seq., and any Executive Orders or regulations promulgated thereunder with the result that the investment in Tenant is prohibited by law or Tenant is in violation of law.

  • OSHA Compliance To the extent applicable to the services to be performed under this Agreement, Contractor represents and warrants, that all articles and services furnished under this Agreement meet or exceed the safety standards established and promulgated under the Federal Occupational Safety and Health Law (Public Law 91-596) and its regulations in effect or proposed as of the date of this Agreement.

  • REIT Compliance The Company is organized in a manner that conforms with the requirements for qualification as a real estate investment trust (“REIT”) under the Internal Revenue Code of 1986, as amended (the “Code”), and the Company’s intended method of operation, as set forth in the Prospectus, would enable it to meet the requirements for taxation as a REIT under the Code. The Operating Partnership will be treated as a partnership for federal income tax purposes and not as a corporation or association taxable as a corporation.

  • ETHICS COMPLIANCE All Bidders/Contractors and their employees must comply with the requirements of Sections 73 and 74 of the Public Officers Law, other State codes, rules, regulations and executive orders establishing ethical standards for the conduct of business with New York State. In signing the Bid, Bidder certifies full compliance with those provisions for any present or future dealings, transactions, sales, contracts, services, offers, relationships, etc., involving New York State and/or its employees. Failure to comply with those provisions may result in disqualification from the Bidding process, termination of contract, and/or other civil or criminal proceedings as required by law.

  • 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:

  • 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.

  • FDA Compliance The Company: (A) is and at all times has been in material compliance with all statutes, rules or regulations of the FDA and other comparable governmental entities applicable to the ownership, testing, development, manufacture, packaging, processing, use, distribution, marketing, labeling, promotion, sale, offer for sale, storage, import, export or disposal of any product under development, manufactured or distributed by the Company (“Applicable Laws”); (B) has not received any FDA Form 483, notice of adverse finding, warning letter, untitled letter or other correspondence or notice from the FDA or any governmental entity alleging or asserting material noncompliance with any Applicable Laws or any licenses, certificates, approvals, clearances, exemptions, authorizations, permits and supplements or amendments thereto required by any such Applicable Laws (“Authorizations”); (C) possesses all material Authorizations and such Authorizations are valid and in full force and effect and the Company is not in material violation of any term of any such Authorizations; (D) has not received notice of any claim, action, suit, proceeding, hearing, enforcement, investigation, arbitration or other action from the FDA or any governmental entity or third party alleging that any product operation or activity is in material violation of any Applicable Laws or Authorizations and has no knowledge that the FDA or any governmental entity or third party is considering any such claim, litigation, arbitration, action, suit, investigation or proceeding; (E) has not received notice that the FDA or any governmental entity has taken, is taking or intends to take action to limit, suspend, modify or revoke any material Authorizations and has no knowledge that the FDA or any governmental entity is considering such action; and (F) has filed, obtained, maintained or submitted all material reports, documents, forms, notices, applications, records, claims, submissions and supplements or amendments as required by any Applicable Laws or Authorizations and that all such reports, documents, forms, notices, applications, records, claims, submissions and supplements or amendments were materially complete and correct on the date filed (or were corrected or supplemented by a subsequent submission).

  • HIPAA Compliance If this Contract involves services, activities or products subject to the Health Insurance Portability and Accountability Act of 1996 (HIPAA), the Contractor covenants that it will appropriately safeguard Protected Health Information (defined in 45 CFR 160.103), and agrees that it is subject to, and shall comply with, the provisions of 45 CFR 164 Subpart E regarding use and disclosure of Protected Health Information.

  • 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.

  • 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”).

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