Member Compliance Sample Clauses

Member Compliance. Member certifies that:
Sample 1Sample 2
AutoNDA by SimpleDocs
Member Compliance. The Affiliate agrees to advise its members of, obtain their agreement to and take all reasonable steps to ensure their compliance with, the following: That no ownership rights to HL7 International Material or HL7 International Trademarks are transferred to any other party. When participating in HL7 International activities, to abide by the prevailing HL7 International Governance and Operations Manual (GOM), available at the HL7 International website (see Appendix B).
Sample 1Sample 2
Member Compliance. By execution of this Agreement, Member agrees to comply with and abide by the Bylaws, applicable Coverage Documents, and the rules and regulations of the Pool, as now in effect and as hereafter amended.
Sample 1
Member Compliance. Xxxxxx Nutrition may review Member Product purchases to determine if Member is meeting the purchase commitment requirements defined in this Letter of Commitment. To complete a compliance review, Xxxxxx Nutrition may request and Member shall supply a usage report, including Xxxxxx Nutrition and competitive product utilization. The report shall be provided in excel to Xxxxxx Nutrition's sales representative and shall contain the following: (i). supplier name; (ii). product name; (iii). product code (or item number); and (iv). case quantity for each product. The report shall include direct purchases from Xxxxxx Nutrition and indirect purchases through Member’s distributor. If a Member is not meeting the purchase commitment requirements set forth in this Letter of Commitment, then Xxxxxx Nutrition shall have the right to change Member’s pricing upon 30 days prior written notice.
Sample 1
Member Compliance. Upon UPR’s reasonable request, Member shall allow in- spection of Station facilities and provide UPR with reasonable access to all records relating to Member’s compliance with this Agreement and UPR policies. Member shall notify UPR immediately if it no longer complies with any applicable UPR policy. From time to time upon UPR’s reasonable request, Member shall provide UPR with copies of the Programming as broadcast by its Station(s).
Sample 1
Member Compliance. Each Member and former Member agrees that, upon request of the Tax Representative, such Member shall (i) take such actions as may be necessary or desirable (as determined by the Board) to allow the Company to comply with the provisions of Code section 6226 so that any “partnership adjustments” are taken into account by the Members rather than the Company or (ii) file amended tax returns with respect to any “reviewed year” (within the meaning of Code section 6225(d)(1)) to reduce the amount of any “partnership adjustment” otherwise required to be taken into account by the Company.
Sample 1
Member Compliance. Abbott Nutrition may review Member Product purchases to determine if Member is meeting the purchase commitment requirements defined in this Letter of Commitment. To complete a compliance review, Abbott Nutrition may request and Member shall supply a usage report, including Abbott Nutrition and competitive product utilization. The report shall be provided in excel to Abbott Nutrition's sales representative and shall contain the following: (i). supplier name; (ii). product name; (iii). product code (or item number); and (iv). case quantity for each product. The report shall include direct purchases from Abbott Nutrition and indirect purchases through Member’s distributor. If a Member is not meeting the purchase commitment requirements set forth in this Letter of Commitment, then Abbott Nutrition shall have the right to change Member’s pricing upon 30 days prior written notice.
Sample 1
AutoNDA by SimpleDocs

Related to Member Compliance

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

  • FUND COMPLIANCE 3.1 The Fund and the Adviser acknowledge that any failure (whether intentional or in good faith or otherwise) to comply with the requirements of Subchapter M of the Code or the diversification requirements of Section 817(h) of the Code may result in the Contracts not being treated as variable contracts for federal income tax purposes, which would have adverse tax consequences for Contract owners and could also adversely affect the Company's corporate tax liability. The Fund and the Adviser further acknowledge that any such failure may result in costs and expenses being incurred by the Company in obtaining whatever regulatory authorizations are required to substitute shares of another investment company for those of the failed Fund or as well as fees and expenses of legal counsel and other advisors to the Company and any federal income taxes, interest or tax penalties incurred by the Company in connection with any such failure.

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

  • PCI Compliance A. The Acquiring Bank will provide The Merchant with appropriate training on PCI PED and/or DSS rules and regulations in respect of The Merchants obligations. Initial training will be provided and at appropriate intervals as and when relevant changes are made to such rules and regulations.

  • CRA Compliance Neither Buyer nor any Buyer Subsidiary has received any notice of non-compliance with the applicable provisions of the CRA and the regulations promulgated thereunder. As of the date hereof, Buyer’s and each Buyer Subsidiary’s most recent examination rating under the CRA was “satisfactory” or better. Buyer knows of no fact or circumstance or set of facts or circumstances which would be reasonably likely to cause Buyer or any Buyer Subsidiary to receive any notice of non-compliance with such provisions of the CRA or cause the CRA rating of Buyer or any Buyer Subsidiary to decrease below the “satisfactory” level.

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

  • FCPA Compliance The Company has not and, to the Company’s actual knowledge, none of its employees or agents at any time during the last five years have (i) made any unlawful contribution to any candidate for foreign office, or failed to disclose fully any contribution in violation of law, or (ii) made any payment to any federal or state governmental officer or official, or other person charged with similar public or quasi-public duties, other than payments required or permitted by the laws of the United States or any jurisdiction thereof.

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

  • Program Compliance The School Board shall be responsible for monitoring the program to provide technical assistance and to ensure program compliance.

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

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