Disputed Amount Resolution Mechanism Sample Clauses

Disputed Amount Resolution Mechanism. With respect to the Disputed Amount as provided under Section 4.2 above, if Spikes disagrees with Company’s calculation of the Net Cash Receipt, the Parties will attempt to resolve such dispute promptly in an amicable manner by a meeting (which may be executed also by means of video conferencing) of authorized representatives of both Parties and either party may provide additional documents and/or accounting opinion to support its calculation. Only if the dispute has not been resolved within 5 Business Days following such meeting, then the dispute shall be settled by arbitration in accordance with the Israeli Arbitration Law, 1968 held by one agreed arbitrator, and shall take place in Tel Aviv. If the Parties do not reach an agreement with respect to the identity of the arbitrator, the arbitrator will be appointed by the Arbitration Institute of the Israel Bar Association. This Section 4.3 is an arbitration agreement in accordance with the Israeli Arbitration Law 1968.
AutoNDA by SimpleDocs

Related to Disputed Amount Resolution Mechanism

  • Full Settlement; Resolution of Disputes (a) The Company's obligation to make the payments provided for in this Agreement and otherwise to perform its obligations hereunder shall not be affected by any set-off, counterclaim, recoupment, defense or other claim, right or action which the Company may have against the Executive or others. In no event shall the Executive be obligated to seek other employment or take any other action by way of mitigation of the amounts payable to the Executive under any of the provisions of this Agreement and, except as provided in Section 6(a)(ii) of this Agreement, such amounts shall not be reduced whether or not the Executive obtains other employment. The Company agrees to pay promptly as incurred, to the full extent permitted by law, all legal fees and expenses which the Executive may reasonably incur as a result of any contest (regardless of the outcome thereof) by the Company, the Executive or others of the validity or enforceability of, or liability under, any provision of this Agreement or any guarantee of performance thereof (including as a result of any contest by the Executive about the amount of any payment pursuant to this Agreement), plus in each case interest on any delayed payment at the applicable Federal rate provided for in Section 7872(f)(2)(A) of the Code. (b) If there shall be any dispute between the Company and the Executive (i) in the event of any termination of the Executive's employment by the Company, whether such termination was for Cause, or (ii) in the event of any termination of employment by the Executive, whether Good Reason existed, then, unless and until there is a final, nonappealable judgment by a court of competent jurisdiction declaring that such termination was for Cause or that the determination by the Executive of the existence of Good Reason was not made in good faith, the Company shall pay all amounts, and provide all benefits, to the Executive and/or the Executive's family or other beneficiaries, as the case may be, that the Company would be required to pay or provide pursuant to Section 6(a) of this Agreement as though such termination were by the Company without Cause or by the Executive with Good Reason; provided, however, that the Company shall not be required to pay any disputed amounts pursuant to this paragraph except upon receipt of an undertaking by or on behalf of the Executive to repay all such amounts to which the Executive is ultimately adjudged by such court not to be entitled.

  • ERROR RESOLUTION NOTICE In Case of Errors or Questions About Your Electronic Transfers, Call or Write us at the telephone number or address listed in this disclosure, as soon as you can, if you think your statement or receipt is wrong or if you need more information about a transfer listed on the statement or receipt. We must hear from you no later than 60 days after we sent the FIRST statement on which the problem or error appeared.

  • Dispute Resolution Mechanism a. Any dispute regarding the administration of the Institute at the Company or plant level shall be subject to expedited resolution by the Chairs of the Union and Company Negotiating Committees and the Executive Director of ICD who shall apply the policies, rules and regulations of the Governing Board and the provisions of this Section in ruling on any such dispute. Rulings of the Executive Director may be appealed to the Governing Board, but shall become and remain effective unless stayed or reversed by the Governing Board. b. Within sixty (60) days of the Effective Date, the parties will develop an expedited dispute resolution mechanism that resolves disputes within two (2) weeks.

  • Amicable Resolution (a) Save where expressly stated to the contrary in this Agreement, any dispute, difference or controversy of whatever nature between the Parties, howsoever arising under, out of or in relation to this Agreement (the "Dispute") shall in the first instance be attempted to be resolved amicably in accordance with the procedure set forth in Clause 12.1 (b). (b) Either Party may require such Dispute to be referred to the Authority, and the Chief Executive Officer/Director/Partner of the Developer for the time being, for amicable settlement. Upon such reference, the two shall meet at the earliest mutual convenience and in any event within 15 days of such reference to discuss and attempt to amicably resolve the Dispute. If the Dispute is not amicably settled within 15 (fifteen) days of such meeting between the two, either Party may refer the Dispute to arbitration in accordance with the provisions of Clause 12.2.

  • Dispute Resolution Mechanisms Registry Operator will comply with the following dispute resolution mechanisms as they may be revised from time to time: the Trademark Post-Delegation Dispute Resolution Procedure (PDDRP) and the Registration Restriction Dispute Resolution Procedure (RRDRP) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/pddrp and xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp, respectively). Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PDDRP or RRDRP panel and to be bound by any such determination; and the Uniform Rapid Suspension system (“URS”) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/urs), including the implementation of determinations issued by URS examiners. CONTINUED OPERATIONS INSTRUMENT The Continued Operations Instrument shall (a) provide for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period of one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6th) anniversary of the Effective Date, and (b) be in the form of either (i) an irrevocable standby letter of credit, or (ii) an irrevocable cash escrow deposit, each meeting the requirements set forth in item 50(b) of Attachment to Module 2 – Evaluation Questions and Criteria – of the gTLD Applicant Guidebook, as published and supplemented by ICANN prior to the date hereof (which is hereby incorporated by reference into this Specification 8). Registry Operator shall use its best efforts to take all actions necessary or advisable to maintain in effect the Continued Operations Instrument for a period of six (6) years from the Effective Date, and to maintain ICANN as a third party beneficiary thereof. If Registry Operator elects to obtain an irrevocable standby letter of credit but the term required above is unobtainable, Registry Operator may obtain a letter of credit with a one-year term and an “evergreen provision,” providing for annual extensions, without amendment, for an indefinite number of additional periods until the issuing bank informs ICANN of its final expiration or until ICANN releases the letter of credit as evidenced in writing, if the letter of credit otherwise meets the requirements set forth in item 50(b) of Attachment to Module 2 – Evaluation Questions and Criteria – of the gTLD Applicant Guidebook, as published and supplemented by ICANN prior to the date hereof; provided, however, that if the issuing bank informs ICANN of the expiration of such letter of credit prior to the sixth (6th) anniversary of the Effective Date, such letter of credit must provide that ICANN is entitled to draw the funds secured by the letter of credit prior to such expiration. The letter of credit must require the issuing bank to give ICANN at least thirty (30) calendar days’ notice of any such expiration or non-renewal. If the letter of credit expires or is terminated at any time prior to the sixth (6th) anniversary of the Effective Date, Registry Operator will be required to obtain a replacement Continued Operations Instrument. ICANN may draw the funds under the original letter of credit, if the replacement Continued Operations Instrument is not in place prior to the expiration of the original letter of credit. Registry Operator shall provide to ICANN copies of all final documents relating to the Continued Operations Instrument and shall keep ICANN reasonably informed of material developments relating to the Continued Operations Instrument. Registry Operator shall not agree to, or permit, any amendment of, or waiver under, the Continued Operations Instrument or other documentation relating thereto without the prior written consent of ICANN (such consent not to be unreasonably withheld). If, notwithstanding the use of best efforts by Registry Operator to satisfy its obligations under the preceding paragraph, the Continued Operations Instrument expires or is terminated by another party thereto, in whole or in part, for any reason, prior to the sixth anniversary of the Effective Date, Registry Operator shall promptly (i) notify ICANN of such expiration or termination and the reasons therefor and (ii) arrange for an alternative instrument that provides for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period of one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6) anniversary of the Effective Date (an “Alternative Instrument”). Any such Alternative Instrument shall be on terms no less favorable to ICANN than the Continued Operations Instrument and shall otherwise be in form and substance reasonably acceptable to ICANN. Notwithstanding anything to the contrary contained in this Specification 8, at any time, Registry Operator may replace the Continued Operations Instrument with an Alternative Instrument that (i) provides for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6) anniversary of the Effective Date, and (ii) contains terms no less favorable to ICANN than the Continued Operations Instrument and is otherwise in form and substance reasonably acceptable to ICANN. In the event Registry Operator replaces the Continued Operations Instrument either pursuant to paragraph 2 or this paragraph 3, the terms of this Specification 8 shall no longer apply with respect to the original Continuing Operations Instrument, but shall thereafter apply with respect to such Alternative Instrument(s), and such instrument shall thereafter be considered the Continued Operations Instrument for purposes of this Agreement. REGISTRY OPERATOR CODE OF CONDUCT In connection with the operation of the registry for the TLD, Registry Operator will not, and will not allow any parent, subsidiary, Affiliate, subcontractor or other related entity, to the extent such party is engaged in the provision of Registry Services with respect to the TLD (each, a “Registry Related Party”), to: directly or indirectly show any preference or provide any special consideration to any registrar with respect to operational access to registry systems and related registry services, unless comparable opportunities to qualify for such preferences or considerations are made available to all registrars on substantially similar terms and subject to substantially similar conditions; register domain names in its own right, except for names registered through an ICANN accredited registrar; provided, however, that Registry Operator may (a) reserve names from registration pursuant to Section 2.6 of the Agreement and (b) may withhold from registration or allocate to Registry Operator up to one hundred (100) names pursuant to Section 3.2 of Specification 5; register names in the TLD or sub-domains of the TLD based upon proprietary access to information about searches or resolution requests by consumers for domain names not yet registered (commonly known as, “front-running”); or allow any Affiliated registrar to disclose Personal Data about registrants to Registry Operator or any Registry Related Party, except as reasonably necessary for the management and operations of the TLD, unless all unrelated third parties (including other registry operators) are given equivalent access to such user data on substantially similar terms and subject to substantially similar conditions. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will, or will cause such Registry Related Party to, ensure that such services are offered through a legal entity separate from Registry Operator, and maintain separate books of accounts with respect to its registrar or registrar-reseller operations. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will conduct internal reviews at least once per calendar year to ensure compliance with this Code of Conduct. Within twenty (20) calendar days following the end of each calendar year, Registry Operator will provide the results of the internal review, along with a certification executed by an executive officer of Registry Operator certifying as to Registry Operator’s compliance with this Code of Conduct, via email to an address to be provided by ICANN. (ICANN may specify in the future the form and contents of such reports or that the reports be delivered by other reasonable means.) Registry Operator agrees that ICANN may publicly post such results and certification; provided, however, ICANN shall not disclose Confidential Information contained in such results except in accordance with Section 7.15 of the Agreement. Nothing set forth herein shall: (i) limit ICANN from conducting investigations of claims of Registry Operator’s non-compliance with this Code of Conduct; or (ii) provide grounds for Registry Operator to refuse to cooperate with ICANN investigations of claims of Registry Operator’s non-compliance with this Code of Conduct. Nothing set forth herein shall limit the ability of Registry Operator or any Registry Related Party, to enter into arms-length transactions in the ordinary course of business with a registrar or reseller with respect to products and services unrelated in all respects to the TLD. Registry Operator may request an exemption to this Code of Conduct, and such exemption may be granted by ICANN in ICANN’s reasonable discretion, if Registry Operator demonstrates to ICANN’s reasonable satisfaction that (i) all domain name registrations in the TLD are registered to, and maintained by, Registry Operator for the exclusive use of Registry Operator or its Affiliates, (ii) Registry Operator does not sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not an Affiliate of Registry Operator, and (iii) application of this Code of Conduct to the TLD is not necessary to protect the public interest. REGISTRY PERFORMANCE SPECIFICATIONS DNS. Refers to the Domain Name System as specified in RFCs 1034, 1035, and related RFCs. DNSSEC proper resolution. There is a valid DNSSEC chain of trust from the root trust anchor to a particular domain name, e.g., a TLD, a domain name registered under a TLD, etc.

  • Disputed Amounts 28.1.1 If any portion of an amount due to a Party (the “Billing Party”) under this Agreement is subject to a bona fide dispute between the Parties, the Party billed (the “Non-Paying Party”) shall, prior to the Xxxx Due Date, give written notice to the Billing Party of the amounts it disputes (“Disputed Amounts”) and include in such written notice the specific details and reasons for disputing each item; provided, however, a failure to provide such notice by that date shall not preclude a Party from subsequently challenging billed charges provided that such charges were paid. The Non-Paying Party shall pay when due all undisputed amounts to the Billing Party. Notwithstanding the foregoing, except as provided in Section 28.2, a Party shall be entitled to dispute only those charges for which the Date was within the immediately preceding eighteen (18) months of the date on which the other Party received notice of such Disputed Amounts. 28.1.2 If the Non-Paying Party disputes charges and the dispute is resolved in favor of such Non-Paying Party, the Billing Party shall credit the invoice of the Non-Paying Party for the amount of the Disputed Amounts along with any applicable late payment charges no later than the second Xxxx Due Date after the resolution of the Dispute. Accordingly, if a Non-Paying Party disputes charges and the dispute is resolved in favor of the Billing Party, the Non-Paying Party shall pay the Billing Party the amount of the Disputed Amounts and any associated late payment charges no later than the second Xxxx Due Date after the resolution of the Dispute. Late payment charges shall be assessed as set forth in Section 27.8. 28.1.3 If the Parties are unable to resolve the issues related to the Disputed Amounts in the normal course of business within sixty (60) days after delivery to the Billing Party of notice of the Disputed Amounts, each of the Parties shall appoint a designated representative who has authority to settle the Dispute and who is at a higher level of management than the persons with direct responsibility for administration of this Agreement. The designated representatives shall meet as often as they reasonably deem necessary in order to discuss the Dispute and negotiate in good faith in an effort to resolve such Dispute. The specific format for such discussions will be left to the discretion of the designated representatives; however all reasonable requests for relevant information made by one Party to the other Party shall be honored. 28.1.4 If the Parties are unable to resolve issues related to the Disputed Amounts within forty-five (45) days after the Parties' appointment of designated representatives pursuant to Section 28.3, then either Party may file a complaint with the Commission to resolve such issues or proceed with any other remedy pursuant to law or equity. The Commission or the FCC may direct payment of any or all Disputed Amounts (including any accrued interest) thereon or additional amounts awarded, plus applicable late fees, to be paid to either Party. 28.1.5 The Parties agree that all negotiations pursuant to this Section 28.1 shall remain confidential in accordance with Article XX and shall be treated as compromise and settlement negotiations for purposes of the Federal Rules of Evidence and state rules of evidence.

  • Resolution Procedure a. Step 1 i. The complainant, if comfortable with that approach, may choose to speak to or correspond directly with the alleged harasser to express their feelings about the situation. ii. Before proceeding to Step 2, the complainant may approach their administrative officer, staff rep or other contact person to discuss potential means of resolving the complaint and to request assistance in resolving the matter. If the matter is resolved to the complainant's satisfaction the matter is deemed to be resolved. Refer to Article E.

  • Methods of Resolution of Disputes In the event of any dispute with respect to the construction and performance of this Agreement, the Parties shall first resolve the dispute through friendly negotiations. In the event the Parties fail to reach an agreement on the dispute within 30 days after either Party’s request to the other Parties for resolution of the dispute through negotiations, either Party may submit the relevant dispute to the China International Economic and Trade Arbitration Commission for arbitration, in accordance with its arbitration rules. The arbitration shall be conducted in Beijing. The arbitration award shall be final and binding on all Parties.

  • DISPUTES RESOLUTION PROCEDURE 10.1 A major objective of this Agreement is to eliminate lost time and/or production arising out of disputes or grievances. The Parties to this Agreement are committed to complying with the terms of this procedure.

  • TCP DNS resolution RTT Refers to the RTT of the sequence of packets from the start of the TCP connection to its end, including the reception of the DNS response for only one DNS query. If the RTT is 5 times greater than the time specified in the relevant SLR, the RTT will be considered undefined.

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