Payment not Permitted Sample Clauses

Payment not Permitted. The annual leave provided for by this clause shall be allowed and shall be taken, and except as provided by Clauses 8.3(d) and (k) hereof, payment shall not be made or accepted in lieu of annual leave.
AutoNDA by SimpleDocs

Related to Payment not Permitted

  • Payment Not Final Approval Consultant understands and agrees that payment to the Consultant or reimbursement for any Consultant costs related to the performance of Required Services does not constitute a City final decision regarding whether such payment or cost reimbursement is allowable and eligible for payment under this Agreement, nor does it constitute a waiver of any violation by Consultant of the terms of this Agreement. If City determines that Consultant is not entitled to receive any amount of compensation already paid, City will notify Consultant in writing and Consultant shall promptly return such amount.

  • Agreement Not Evidence (1) The Parties agree that, whether or not it is finally approved, is terminated, or otherwise fails to take effect for any reason, this Settlement Agreement and anything contained herein, and any and all negotiations, documents, discussions and proceedings associated with this Settlement Agreement, and any action taken to carry out this Settlement Agreement, shall not be referred to, offered as evidence or received in evidence in any pending or future civil, criminal or administrative action or proceeding, except in a proceeding to approve and/or enforce this Settlement Agreement, to defend against the assertion of Released Claims, as necessary in any insurance-related proceeding, or as otherwise required by law.

  • Obligations of the Concessionaire 5.1.1 Subject to and on the terms and conditions of this Agreement, the Concessionaire shall, at its own cost and expense, procure finance for and undertake the design, engineering, procurement, construction, operation and maintenance of the Project and observe, fulfil, comply with and perform all its obligations set out in this Agreement or arising hereunder.

  • Operator’s Obligations The Operator agrees at all times during the Term:

  • Contractor’s Obligation with Regard to ISV (Third Party Product Where Contractor furnishes Existing Licensed Product(s) as a Project Deliverable, and sufficient rights necessary to effect the purposes of this section are not otherwise provided in the Contractor or ISV’s standard license agreement, Contractor shall be responsible for obtaining from the ISV third party proprietary owner/developer the rights set forth herein to the benefit of the Authorized User at Contractor’s sole cost and expense.

  • AGREEMENT NOT TRANSFERRABLE TO OTHER FACILITIES This agreement is valid for only the residential facilities assigned to the Student. This agreement cannot be transferred, nor can it be converted to any other type of lease or agreement without a written or electronically reproducible modification agreement submitted by the student and approved by the Executive Director or the Executive Director’s designee. There is no reciprocity of housing agreements with any other housing organization or complex, including but not limited to on-campus residence halls, on-campus apartments, Rosen, Towers, Northview, UCF affiliated housing, fraternity-sorority housing, or any other housing, residential, and/or apartment facilities both on- and off-campus. MOVE IN, RESIDENCE, MOVE OUT

  • Payments Not Received (a) Payments are due and payable on the date of issue indicated on the bill for collection. When a payment for timber cut and other charges is not received at the location designated by Forest Service by the date allowed in the bill for collection for receipt of payment, Contracting Officer will suspend all or any part of Purchaser’s Operations until payment or acceptable payment guarantee is received. Other charges include, but are not limited to:

  • Sole purpose of the Concessionaire The Concessionaire having been set up for the sole purpose of exercising the rights and observing and performing its obligations and liabilities under this Agreement, the Concessionaire or any of its subsidiaries shall not, except with the previous written consent of the Authority, be or become directly or indirectly engaged, concerned or interested in any business other than as envisaged herein.

  • Processor’s Obligations Except where expressly permitted by Article 28 (3)(a) GDPR, Processor shall process data subjects’ Data only within the scope of the Agreement and the instructions issued by Controller. Where Processor believes that an instruction would be in breach of applicable law, Processor shall notify Controller of such belief without undue delay. Processor shall be entitled to suspend performance on such instruction until Controller confirms or modifies such instruction. Processor shall, within Processor’s scope of responsibility, organize Processor’s internal organization so it satisfies the specific requirements of data protection. Processor shall implement technical and organizational measures to ensure the adequate protection of Controller’s Data, which measures shall fulfil the requirements of the GDPR and specifically its Article 32. Processor shall implement technical and organizational measures and safeguards that ensure ongoing confidentiality, integrity, availability and resilience of processing systems and services and shall implement a process for regularly testing, assessing and evaluating the effectiveness of technical and organizational measures for ensuring the security of the processing. Controller is familiar with these technical and organizational measures, and it shall be Controller’s responsibility that such measures ensure a level of security appropriate to the risk. The parties agree to refer to the existing certification of Processor by Kiwa International Cert GmbH in accordance with DIN ISO/IEC 27001:2015 which is considered sufficient evidence for these purposes by Controller and which is available on the website of Processor (xxx.xxxxxxx.xxx). Processor reserves the right to modify the measures and safeguards implemented, provided, however, that that the level of security shall not be less protective than initially agreed upon. Processor shall support Controller, insofar as is agreed upon by the parties, and where possible for Processor, in fulfilling data subjects’ requests and claims, as detailed in chapter III of the GDPR and in fulfilling the obligations enumerated in Articles 33 to 36 GDPR. Processor shall ensure that all employees involved in Contract Processing of Controller’s Data and other such persons as may be involved in Contract Processing within Processor’s scope of responsibility shall only do so within the scope of the instructions. Furthermore, Processor shall ensure that any person entitled to process Data on behalf of Controller has undertaken a commitment to confidentiality under terms similar to the confidentiality terms of the Agreement. All such confidentiality obligations shall survive the termination or expiration of such Contract Processing. Processor shall notify Controller without undue delay if Processor becomes aware of any Data breaches within Processor’s scope of responsibility. Processor shall implement the measures necessary for securing Data and for mitigating potential negative consequences for the data subject; the Processor shall coordinate such efforts with Controller without undue delay. Processor shall notify to Controller the point of contact for any issues related to data protection arising out of or in connection with the Agreement. The Exhibit provides for a list of the initially designated persons. Processor shall correct or erase Data if so instructed by Controller and where covered by the scope of the instructions permissible. Where an erasure, consistent with data protection requirements, or a corresponding restriction of processing is impossible, Processor shall, based on Controller’s instructions, and unless agreed upon differently in the Agreement, destroy, in compliance with data protection requirements, all carrier media and other material or return the same to Controller. In specific cases designated by Controller, such Data shall be stored or handed over. The associated cost for doing so and protective measures to put in place shall be agreed upon separately, unless already agreed upon in the Agreement. Processor shall, upon termination of Contract Processing and upon Controller’s instruction, return all Data, carrier media and other materials to Controller or delete the same. Where a data subject asserts any claims against Controller in accordance with Article 82 of the GDPR, Processor shall support Controller in defending against such claims, where possible at Controller’s cost as set out in Section 6 para. 3. § 4Controller’s Obligations Controller shall notify Processor without undue delay, and comprehensively, of any defect or irregularity with regard to provisions on data protection detected by Controller in the results of Processor’s work.

  • Obligations Owed to Third Parties The Contractor represents and warrants that all obligations owed to third parties with respect to the activities contemplated to be undertaken by the Contractor pursuant to the Contract are or will be fully satisfied by the Contractor so that the State and the State Entity will not have any obligations with respect thereto.

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