FREQUENT FLYER MILES Sample Clauses

FREQUENT FLYER MILES. Notwithstanding any existing Company policy to the contrary, the Company shall allow the Executive to retain the Frequent Flyer miles acquired as a result of travel on behalf of the Company.
AutoNDA by SimpleDocs
FREQUENT FLYER MILES. A Company that charges a traveler who reserves a vehicle under the terms of this agreement for any of these items must refund the traveler or Government, as applicable, the cost of these items when the Company is presented with evidence of charges for these items for a traveler who reserved under the terms of this agreement in accordance with the instructions provided in Appendix F, “Repayment of Overcharges.” 10 Company Points of Contact The Company will identify the following points of contact for DTMO in Appendix C, “Company Points of Contact.” • Primary Company Point of Contact: A Company employee available to the DTMO for all rental vehicle collision, loss, or damage incidents, overcharges, and service complaints or commendations. • Secondary Company Point of Contact: A Company employee at the same reporting level or junior to the Primary Company Point of Contact authorized to manage the same issues as the Primary Company Point of Contact on a day-to-day basis or in the Primary Company Point of Contact’s absence. Identification of a Secondary Company Point of Contact is optional, but the Secondary Company Point of Contact may not be a retail or general customer service team. • Senior Company Point of Contact: A Company employee senior to the Primary Company Point of Contact available to DTMO for discussion of high-level concerns. Company Data Point of Contact: A Company employee available to DTMO for discussion of all matters concerning data reporting laid out in Appendix D, “Rental Car Reporting.” The Company Data Point of Contact will be responsible for receiving and responding to file processing reports and data validation error reports.
FREQUENT FLYER MILES. The Company will transfer of the Bonus Miles allocated to Client’s Frequent Flyer account based on purchases made by the booking Client, within 30 days of the completion of travel. The miles will be awarded under the terms and conditions of the partner airline’s Frequent Flyer Program. If it is determined that the Company or the Client does not meet the requirements of the program, Xxxxx will not be awarded and no compensation will be made to the Client. If the client fails to provide a correct Frequent Flyer account number, during the booking, the Client forfeits the right to miles earned from the purchase made. Stay Connected Program The Company offers the use of a local/regional mobile telephone and USB modem during all organized Tours, to all Clients that book a Tour with the Company via our website. The devices will be made available to the Client upon arrival in the Country/Region. Communication charges are the responsibility of the Client and are charged in the form of pre-paid credit, which can be purchased from local suppliers. At the end of the Tour the Client shall return the devices in good working order. Failure to return the telephone or modem, or damage to either item will result in a charge to the Client not to exceed $50 per item. The Company will not reimburse the Client for any unused communication credits. The Company requests that any Client not wishing to participate in the Stay Connected Program, to inform us of their desire prior to departure.

Related to FREQUENT FLYER MILES

  • Payment Frequency As of the Cutoff Date and as shown on the books of CNHCA: (A) Receivables having an aggregate Statistical Contract Value equal to 76.88% of the Aggregate Statistical Contract Value had annual scheduled payments, (B) Receivables having an aggregate Statistical Contract Value equal to 2.70% of the Aggregate Statistical Contract Value had semi-annual scheduled payments, (C) Receivables having an aggregate Statistical Contract Value equal to 0.79% of the Aggregate Statistical Contract Value had quarterly scheduled payments, (D) Receivables having an aggregate Statistical Contract Value equal to 17.19% of the Aggregate Statistical Contract Value had monthly scheduled payments, and (E) Receivables having an aggregate Statistical Contract Value equal to 2.45% of the Aggregate Statistical Contract Value had irregularly scheduled payments.

  • Adjustment of Minimum Quarterly Distribution and Target Distribution Levels (a) The Minimum Quarterly Distribution, First Target Distribution, Second Target Distribution, Third Target Distribution, Common Unit Arrearages and Cumulative Common Unit Arrearages shall be proportionately adjusted in the event of any distribution, combination or subdivision (whether effected by a distribution payable in Units or otherwise) of Units or other Partnership Securities in accordance with Section 5.10. In the event of a distribution of Available Cash that is deemed to be from Capital Surplus, the then applicable Minimum Quarterly Distribution, First Target Distribution, Second Target Distribution and Third Target Distribution, shall be adjusted proportionately downward to equal the product obtained by multiplying the otherwise applicable Minimum Quarterly Distribution, First Target Distribution, Second Target Distribution and Third Target Distribution, as the case may be, by a fraction of which the numerator is the Unrecovered Capital of the Common Units immediately after giving effect to such distribution and of which the denominator is the Unrecovered Capital of the Common Units immediately prior to giving effect to such distribution.

  • Sales Milestones Subject to the terms and conditions set forth in the Agreement, in the event that the Annual Net Sales made by or on behalf of a Selling Entity for all Licensed Products in a given calendar year first exceeds a threshold set forth in the table immediately below, Pyxis shall pay to LCB the following one-time, non-refundable, non-creditable milestone payments. Annual Net Sales Milestone Threshold Payment (US Dollars) [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] In the event that in a given calendar year more than one (1) Annual Net Sales milestone threshold is achieved, Pyxis shall pay to LCB each separate Annual Net Sales milestone payment with respect to each Annual Net Sales milestone threshold that is achieved in such calendar year. Pyxis shall notify LCB in writing upon the first achievement, in respect of a Licensed Product, by or on behalf of Pyxis or its Affiliate or Sublicensee, of each of the Milestones set forth in Section 5.2 (Development Milestones), Section 5.3 (Regulatory Milestones) and Section 5.4 (Sales Milestones) no later than [***] of Pyxis’s knowledge of achievement thereof, and in any event, each of the Milestones set forth in Section 5.4 (Sales Milestones) no later than [***] after the end of the applicable calendar year in which such Milestone is achieved. No later than [***] of receipt of an appropriate invoice from LCB, Pyxis shall pay the applicable payment due upon achievement of the corresponding Milestone Event. Each Milestone Event shall be deemed to be achieved once for all Licensed Products and shall be payable only once.

  • Development Milestones In addition to its obligations under Paragraph 7.1, LICENSEE specifically commits to achieving the following development milestones in its diligence activities under this AGREEMENT: (a) (b).

  • HSR Waiting Period The waiting period applicable to the consummation of the Merger under the HSR Act shall have expired or been terminated.

  • Distribution Compliance Period The Purchaser agrees not to resell, pledge or transfer any Purchased Shares within the United States or to any U.S. Person, as each of those terms is defined in Regulation S, during the 40 days following the Closing Date.

  • Tax Periods Beginning Before and Ending After the Closing Date The Company or the Purchaser shall prepare or cause to be prepared and file or cause to be filed any Returns of the Company for Tax periods that begin before the Closing Date and end after the Closing Date. To the extent such Taxes are not fully reserved for in the Company’s financial statements, the Sellers shall pay to the Company an amount equal to the unreserved portion of such Taxes that relates to the portion of the Tax period ending on the Closing Date. Such payment, if any, shall be paid by the Sellers within fifteen (15) days after receipt of written notice from the Company or the Purchaser that such Taxes were paid by the Company or the Purchaser for a period beginning prior to the Closing Date. For purposes of this Section, in the case of any Taxes that are imposed on a periodic basis and are payable for a Taxable period that includes (but does not end on) the Closing Date, the portion of such Tax that relates to the portion of such Tax period ending on the Closing Date shall (i) in the case of any Taxes other than Taxes based upon or related to income or receipts, be deemed to be the amount of such Tax for the entire Tax period multiplied by a fraction the numerator of which is the number of days in the Tax period ending on the Closing Date and the denominator of which is the number of days in the entire Tax period (the “Pro Rata Amount”), and (ii) in the case of any Tax based upon or related to income or receipts, be deemed equal to the amount that would be payable if the relevant Tax period ended on the Closing Date. The Sellers shall pay to the Company with the payment of any taxes due hereunder, the Sellers’ Pro Rata Amount of the costs and expenses incurred by the Purchaser or the Company in the preparation and filing of the Tax Returns. Any net operating losses or credits relating to a Tax period that begins before and ends after the Closing Date shall be taken into account as though the relevant Tax period ended on the Closing Date. All determinations necessary to give effect to the foregoing allocations shall be made in a reasonable manner as agreed to by the parties.

  • Development Milestone Payments In partial consideration for the rights and licenses granted to Coya hereunder, within ten days after the first achievement of each milestone event in a given Indication set forth in this Section 5.2 (Development Milestone Payments) with respect to a Product (each, a “Development Milestone Event”) by or on behalf of Coya or any of its Affiliates or Sublicensees, Coya shall provide ARScience Bio written notice to ARScience Bio identifying the Development Milestone Event achieved. Upon receipt of any such notice of first achievement of a Development Milestone Event by Coya or its Affiliates or Sublicensees, ARScience Bio will promptly invoice Coya for the applicable Development Milestone Event and Coya will make a milestone payment to ARScience Bio in the amount set forth in this Section 5.2 (Development Milestone Payments) corresponding to such Development Milestone Event (each, a “Development Milestone Payment”) within 45 days of receipt of such invoice. On an Indication-by-Indication basis, each Development Milestone Payment shall be payable only upon the first achievement of the corresponding Development Milestone Event by a Product, in any given Indication for which the Development Milestone Events have not been previously achieved (each such Indication, a “New Indication”). No amounts shall be due for subsequent or repeated achievements of such Development Milestone Event with respect to the same or different Mono Product or Combination Product, as applicable, in such Indication. Accordingly and for clarity, the Development Milestone Payment shall be paid only once, when first achieved by Coya, an Affiliate or a Sublicensee, but no payment shall be due if the same milestone is subsequently achieved by one of Coya, an Affiliate or a Sublicensee. For clarity, the amounts owed in Column (a) below shall be due for the first Combination Product to achieve the Development Milestone Events in a New Indication and the amounts owned in Column (c) below shall be due for the first Mono Product to achieve the Development Milestone Events in a New Indication. Any Combination Product or Mono Product to achieve the Development Milestone Events in a New Indication after the first achievement of the Development Milestone Events as described in the foregoing sentence will cause the amounts in Column (b) with respect to a Combination Product and Column (d) with respect to a Mono Product to be due and payable by Coya upon each such occurrence. If the first Product to achieve a Development Milestone Event in any Indication is a Combination Product, the amounts in Column (a) below shall be due and payable by Coya. If the next Product to achieve a Development Milestone Event in a New Indication is a Mono Product, the amounts in Column (c) below would be due and payable by Coya; provided, that if such next Product to achieve a Development Milestone Event in a New Indication is a Combination Product, the amounts in Column (b) would be due and payable by Coya. By way of example, if a Combination Product achieves IND Acceptance in ALS, and is the first Product to achieve a Development Milestone Event under this Agreement, [***] will be due and payable by Coya. If subsequently a Mono Product achieves IND Acceptance in ALS, no Development Milestone Payments will be due and payable by Coya under this Agreement. However, if subsequently any Combination Product achieves IND Acceptance in Alzheimer’s disease, [***] would be due and payable by Coya.

  • Milestone Event Milestone Payment [***] [***]

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