Negotiated Charge Sample Clauses

Negotiated Charge. As to health care coverage, other than Prescribed Medicine Expense coverage: As to Prescribed Medicine Expense coverage:
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Negotiated Charge. This is the maximum charge a Preferred Care Provider has agreed to make as to any service or supply for the purpose of the benefits under the Plan.
Sample 1
Negotiated Charge. For health coverage:
Sample 1
Negotiated Charge. As to the coverage provided under this Prescription Plan Rider, the amount HMO has established for each prescription drug obtained from a Participating Retail, Mail Order, or Specialty Pharmacy Network Pharmacy. The Negotiated Charge may reflect amounts HMO has agreed to pay directly to the Participating Retail, Mail Order, or Specialty Pharmacy Network Pharmacy, or to a third party vendor for the prescription drug, and may include an additional service or risk charge set by HMO. The Negotiated Charge does not include or reflect any amount HMO, an affiliate, or a third party vendor, may receive under a rebate arrangement between HMO, an affiliate or a third party vendor and a drug manufacturer for any prescription drug, including prescription drugs on the Drug Formulary. Based on its overall drug purchasing, HMO may receive rebates from the manufacturers of prescription drugs and may receive or pay additional amounts from or to third parties under price guarantees. These amounts will not change the Negotiated Charge under this Prescription Plan Rider. • Non-Formulary Prescription Drug(s). A product or drug not listed on the Drug Formulary which includes drugs listed on the Drug Formulary Exclusions List. • Participating Mail Order Pharmacy. A pharmacy, which has contracted with HMO, an affiliate, or a third party vendor, to provide covered outpatient prescription drugs or medicines, and insulin to Members by mail or other carrier.
Sample 1

Related to Negotiated Charge

  • Negotiated Contract This Contract has been arrived at through negotiation between the parties. Neither party is to be deemed the party which prepared this Contract within the meaning of California Civil Code Section 1654. Each party hereby represents and warrants that in executing this Contract it does so with full knowledge of the rights and duties it may have with respect to the other. Each party also represents and warrants that it has received independent legal advice from its attorney with respect to the matters set forth in this Contract and the rights and duties arising out of this Contract, or that such party willingly foregoes any such consultation.

  • Service Charge The Tenant must pay the Service Charge in accordance with Part 1 of Schedule 3. The Tenant must pay: VAT on any consideration in respect of a VAT Supply to the Tenant by the Landlord at the same time as the consideration is paid; and on demand VAT (and interest, penalties and costs where these are incurred because of anything the Tenant does or fails to do) charged in respect of any VAT Supply to the Landlord in respect of the Premises where that VAT is not recoverable by the Landlord from HM Revenue & Customs. The Tenant must not do anything that would result in the disapplication of the option to tax in respect of the Landlord’s interest in the Building. The Tenant must pay interest on the Rents and on all other sums not paid on or by the due date (or, if no date is specified, not paid within 10 Business Days after the date of demand). Interest will be payable at the Interest Rate for the period starting on the due date (or date of demand) and ending on the date of payment. The Tenant must pay on demand the Landlord’s costs (including legal and surveyor’s charges and bailiff’s and enforcement agent’s fees) and disbursements in connection with: any breach of the Tenant’s obligations in this Lease, including the preparation and service of a notice under section 146 of the 1925 Act; any application by the Tenant for consent under this Lease, whether that application is withdrawn or consent is granted or lawfully refused, except in cases where the Landlord is required to act reasonably and the Landlord unreasonably refuses to give consent; [and] [carrying out works to the Premises to improve their Environmental Performance where the Tenant, in its absolute discretion, has consented to the Landlord doing so; and]31 the preparation and service of a schedule of dilapidations served no later than six months after the End Date. Third party indemnity32 The Tenant must indemnify the Landlord against all actions, claims, demands made by a third party, all costs, damages, expenses, charges and taxes payable to a third party and the Landlord’s own liabilities, costs and expenses incurred in defending or settling any action, claim or demand in respect of any personal injury or death, damage to any property and any infringement of any right, in each case arising from: the state and condition of the Premises or the Tenant’s use of them; the exercise of the Tenant’s rights; or the carrying out of any Permitted Works. In respect of any claim covered by the indemnity in clause 4.7.1, the Landlord must: give formal notice to the Tenant of the claim as soon as reasonably practicable after receiving notice of it; provide the Tenant with any information and assistance in relation to the claim that the Tenant may reasonably require and the Landlord is lawfully able to provide, subject to the Tenant paying to the Landlord all costs incurred by the Landlord in providing that information and assistance; and mitigate its loss (at the Tenant’s cost) where it is reasonable for the Landlord to do so.

  • Disputed Charges GP MAY, WITHIN 90 DAYS AFTER RECEIPT OF A CHARGE FROM CVR, TAKE WRITTEN EXCEPTION TO SUCH CHARGE, ON THE GROUND THAT THE SAME WAS NOT A REASONABLE COST INCURRED BY CVR OR ITS AFFILIATES IN CONNECTION WITH THE SERVICES. GP SHALL NEVERTHELESS PAY OR CAUSE MLP OR FERTILIZER TO PAY IN FULL WHEN DUE THE FULL PAYMENT AMOUNT OWED TO CVR. SUCH PAYMENT SHALL NOT BE DEEMED A WAIVER OF THE RIGHT OF THE SERVICES RECIPIENT TO RECOUP ANY CONTESTED PORTION OF ANY AMOUNT SO PAID. HOWEVER, IF THE AMOUNT AS TO WHICH SUCH WRITTEN EXCEPTION IS TAKEN, OR ANY PART THEREOF, IS ULTIMATELY DETERMINED NOT TO BE A REASONABLE COST INCURRED BY CVR OR ITS AFFILIATES IN CONNECTION WITH ITS PROVIDING THE SERVICES HEREUNDER, SUCH AMOUNT OR PORTION THEREOF (AS THE CASE MAY BE) SHALL BE REFUNDED BY CVR TO THE SERVICES RECIPIENTS TOGETHER WITH INTEREST THEREON AT THE DEFAULT RATE DURING THE PERIOD FROM THE DATE OF PAYMENT BY THE SERVICES RECIPIENTS TO THE DATE OF REFUND BY CVR.

  • Negotiated Agreement This Agreement has been arrived at through negotiation between the parties. Neither party is the party that prepared this Agreement for purposes of construing this Agreement under California Civil Code section 1654.

  • Negotiation Process (a) If either the Chief Executive Officer of ICANN (“CEO”) or the Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”). Notwithstanding the foregoing, neither the CEO nor the Chair may (i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014. (b) Following receipt of the Negotiation Notice by either the CEO or the Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”). (c) If, following the conclusion of the Discussion Period, an agreement is reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (d) If, following the conclusion of the Discussion Period, an agreement is not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-­‐evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website. (i) The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i). (ii) The mediator shall conduct the mediation in accordance with the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute. (iii) Each party shall bear its own costs in the mediation. The parties shall share equally the fees and expenses of the mediator. (iv) If an agreement is reached during the mediation, ICANN shall post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (v) If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below. (e) If, following mediation, ICANN and the Working Group have not reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e). (i) If an Arbitration Notice is sent, the mediator’s definition of issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person arbitrator panel. Each party may modify its Proposed Revisions before and after the Posting Period. The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2. (ii) No dispute regarding the Proposed Revisions may be submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles 1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6, 7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11. (iii) The mediator will brief the arbitrator panel regarding ICANN and the Working Group’s respective proposals relating to the Proposed Revisions. (iv) No amendment to this Agreement relating to the Proposed Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors. (v) In order for the arbitrator panel to approve either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder. (f) With respect to an Approved Amendment relating to an amendment proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6. (g) Notwithstanding anything in this Section 7.7 to the contrary, (a) if Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-­‐hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).

  • ASSIGNMENT/SUB-CONTRACTING The Contractor agrees that he will not sell, assign or transfer this Agreement or any part thereof or interest therein without the prior written consent of the Owner.

  • Returned Check Charge A Customer whose payment by check is returned for insufficient funds, or is otherwise not processed for payment, will be subject to a returned check charge. Such charge will be applicable on each occasion when a check is returned or not processed. If the returned check was for a combined interstate and international balance, only a single returned check charge will apply.

  • Subcontracting; Assignment The Contractor may not subcontract any portion of the services provided under this Contract without obtaining the prior written approval of the Procurement Officer, nor may the Contractor assign this Contract or any of its rights or obligations hereunder, without the prior written approval of the Procurement Officer provided, however, that a contractor may assign monies receivable under a contract after due notice to the State. Any subcontracts shall include such language as may be required in various clauses contained within this Contract, exhibits, and attachments. The Contract shall not be assigned until all approvals, documents, and affidavits are completed and properly registered. The State shall not be responsible for fulfillment of the Contractor’s obligations to its subcontractors.

  • No Service Charge None of the Issuer, the Note Registrar or the Indenture Trustee will impose a service charge on a Noteholder for the registration of transfer or exchange of Notes. The Issuer, the Note Registrar or the Indenture Trustee may require the Noteholder to pay an amount to cover taxes or other governmental charges that may be imposed for the registration of transfer or exchange of the Notes.

  • SUB-CONTRACTING 34.1. The Purchaser approves the appointment of the sub-contractors specified in Schedule 5.6 (Approved Sub-contractors) in respect of the obligations specified in that Schedule. 34.2. The Service Provider may not sub-contract its obligations under the Contract to other sub-contractors without the prior written consent of the Purchaser. Sub-contracting of any part of the Contract shall not relieve the Service Provider of any obligation or duty attributable to the Service Provider under the Contract. The Service Provider shall be responsible for the acts and omissions of its sub-contractors as though they are its own. 34.3. Where the Service Provider enters into a sub-contract the Service Provider must ensure that a provision is included which: 34.3.1. requires payment to be made of all sums due by the Service Provider to the sub- contractor within a specified period not exceeding 30 days from the receipt of a valid invoice as defined by the sub-contract requirements and provides that, where the Purchaser has made payment to the Service Provider in respect of Services and the sub-contractor’s invoice relates to such Services then, to that extent, the invoice must be treated as valid and, provided the Service Provider is not exercising a right of retention or set-off in respect of a breach of contract by the sub-contractor or in respect of a sum otherwise due by the sub-contractor to the Service Provider, payment must be made to the sub-contractor without deduction; 34.3.2. notifies the sub-contractor that the sub-contract forms part of a larger contract for the benefit of the Purchaser and that should the sub-contractor have any difficulty in securing the timely payment of an invoice, that matter may be referred by the sub-contractor to the Purchaser; 34.3.3. requires that all contracts with sub-contractors and suppliers which the sub- contractor intends to procure, and which the sub-contractor has not before the date of this Contract, already planned to award to a particular supplier are advertised through the Public Contracts Scotland procurement portal (xxx.xxxxxxxxxxxxxxxxxxxxxxx.xxx.xx) and awarded following a fair, open, transparent and competitive process proportionate to the nature and value of the contract; and 34.3.4. is in the same terms as that set out in this clause 34.3 (including for the avoidance of doubt this clause 34.3.4 subject only to modification to refer to the correct designation of the equivalent party as the Service Provider and sub-contractor as the case may be. 34.4. The Service Provider shall also include in every sub-contract: 34.4.1 a right for the Service Provider to terminate that sub-contract if the relevant sub- contractor fails to comply in the performance of its contract with legal obligations in the fields of environmental, social or employment law or if any of the termination events (involving substantial modification of the Contract, contract award despite the existence of exclusion grounds or a serious infringement of EU legal obligations) specified in clause 56.3 occur; and 34.4.2 a requirement that the sub-contractor includes a provision having the same effect as 34.4.1 in any sub-contract which it awards. In this clause 34.4, ‘sub-contract’ means a contract between two or more service providers, at any stage of remoteness from the Purchaser in a sub-contracting chain, made wholly or substantially for the purpose of performing (or contributing to the performance of) the whole or any part of this Contract. 34.5. Where requested by the Purchaser, copies of any sub-contract must be sent by the Service Provider to the Purchaser as soon as reasonably practicable. 34.6. Where the Service Provider proposes to enter into a sub-contract it must: 34.6.1 advertise its intention to do so in at least one trade journal, [at least one newspaper circulating in [refer to locality]] and the Public Contracts Scotland Portal; and 34.6.2 follow a procedure leading to the selection of the sub-contractor which ensures reasonable competition following principles of equal treatment, non-discrimination and transparency and which ensures that such procedure is accessible by small and medium enterprises.

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