Proposed 401(k) Regulations Compliance Sample Clauses

Proposed 401(k) Regulations Compliance. Effective January 18, 2017, the Plan was amended to remove any provisions that would prevent utilizing forfeitures to fund any 401(k) Safe Harbor Matching Employer Contribution, 401(k) Safe Harbor Nonelective Employer Contribution, Qualified Matching Employer Contribution, or Qualified Nonelective Employer Contribution. Pre-Approved Defined Contribution Plan – 06/30/2020 PS Plan 01904-1621562718AA Participation Agreement is required to be executed and retained by Employer for each un-Related Employer, but is optional for use with any Related Employers. PARTICIPATION AGREEMENT for Plan Name: Informatica LLC 401(k) Retirement Plan By executing this Participation Agreement, the Employer identified below (“Participating Employer”) agrees to be bound by the terms of the Plan and the Trust Agreement as adopted by the Plan Sponsor, including any amendments thereto. Participating Employer: (name) (EIN) Effective date of participation: (month/day/year) This Participation Agreement must be signed and dated below by the Participating Employer to be effective.
Sample 1
AutoNDA by SimpleDocs

Related to Proposed 401(k) Regulations Compliance

  • BUY AMERICAN PROVISIONS COMPLIANCE To the extent applicable, Supplier must comply with all applicable provisions of the Buy American Act. Purchases made in accordance with the Buy American Act must follow the applicable procurement rules calling for free and open competition.

  • PCI-DSS Compliance Merchant shall be in full compliance with rules, regulations, guidelines and procedures adopted by any Card Association or Payment Network relating to the privacy and security of Cardholder and Card transaction data, including without limitation the most up-to-date version of the Payment Card Industry Data Security Standard (PCI-DSS), as amended from time to time by the Payment Card Industry Security Standards Council. Detailed information pertaining to aforementioned requirements may be found at xxxxx://xxx.xxxxxxxxxxxxxxxxxxxx.xxx. Additional information regarding security requirements may be found on the Card Association’s respective web sites.

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

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

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

  • Permit Compliance Such Party fails to obtain and maintain in full force and effect any Permit (other than the Regulatory Approval) necessary for such Party to perform its obligations under this Agreement.

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

  • Local Law Requirements Spain. With respect to Customers domiciled in Spain, in the event of any conflict between any statutory law in Spain applicable to Customer, and the terms and conditions of this Agreement, the applicable statutory law shall prevail.

  • Ethics and Compliance This trial will be conducted in accordance with the ethical principles that have their origin in the Declaration of Helsinki and the referenced directives, regulations, guidelines, and/or standards.

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