Eventbrite Agreement Sample Clauses

Eventbrite Agreement. Notwithstanding anything to the contrary set forth in this Section 2.8, the Parties agree that if an Acquiring Party makes any payment to Eventbrite required by the Eventbrite Agreement, then Parent shall be entitled to cancel, in the manner set forth in Section 9.9, a number of fully paid non-assessable shares of Parent Common Stock equal to the amount of such payment divided by the Per Share Price; provided, however, that if SFX elects to cancel shares of Parent Common Stock to satisfy obligations of the Transferor Parties under this Section 2.8(f), the Transferor Parties may instead elect to pay cash to satisfy such obligations. The Parties acknowledge and agree that Transferor Parties have made additional investments in festivals and shows occurring subsequent to Closing in an amount totaling approximately $700,000 to which Parent is entitled, and to the extent any of such investments, whether through the repayment of a loan or otherwise, are recouped by or repaid to a Transferor Party, such Transferor Party shall immediately pay such funds over to Parent.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Eventbrite Agreement

  • Master Services Agreement This Agreement is a master agreement governing the relationship between the Parties solely with regard to State Street’s provision of Services to each BTC Recipient under the applicable Service Modules.

  • Client Agreement We are not required to enter into a written agreement complying with the Code relating to the services that are to be provided to you.

  • One Agreement This Agreement and any related security or other agreements required by this Agreement, collectively: (a) represent the sum of the understandings and agreements between the Bank and the Borrower concerning this credit; (b) replace any prior oral or written agreements between the Bank and the Borrower concerning this credit; and (c) are intended by the Bank and the Borrower as the final, complete and exclusive statement of the terms agreed to by them. In the event of any conflict between this Agreement and any other agreements required by this Agreement, this Agreement will prevail.

  • FRAMEWORK AGREEMENT MANAGEMENT The Parties shall manage this Framework Agreement in accordance with Schedule 14 (Framework Management).

  • Service Agreement Refers to the Contract, Purchase Order or Terms of Service or Terms of Use. Student Data: Student Data includes any data, whether gathered by Provider or provided by LEA or its users, students, or students’ parents/guardians, that is descriptive of the student including, but not limited to,

  • Cooperation Agreement If a Cooperating Institution is appointed, the Fund shall enter into a Cooperation Agreement with the Cooperating Institution setting forth the terms and conditions of its appointment.

  • Services Agreement “Services Agreement” shall mean any present or future agreements, either written or oral, between Covered Entity and Business Associate under which Business Associate provides services to Covered Entity which involve the use or disclosure of Protected Health Information. The Services Agreement is amended by and incorporates the terms of this BA Agreement.

  • Arrangement Agreement This Plan of Arrangement is made pursuant to, and is subject to the provisions of, the Arrangement Agreement, except in respect of the sequence of the steps comprising the Arrangement, which shall occur in the order set forth herein.

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Generator Deactivation Solution, the ISO shall tender to the Developer that proposed the selected transmission Generator Deactivation Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its reliability planning process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Generator Deactivation Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Generator Deactivation Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.

  • Maintenance Agreement The parties will abide by the terms of the Maintenance Agreement including the capacity to dispute the classification in accordance with the Maintenance Agreement (Information Appendix C).

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