Mandatory rejection Sample Clauses

Mandatory rejection. A Seller shall not accept a rated order for delivery on a specific date if unable to fill the order by that date. However, the Seller must inform the Buyer of the earliest date on which delivery can be made and offer to accept the order on the basis of that date. Scheduling conflicts with previously accepted lower rated or unrated orders are not sufficient reason for rejection under this section.
Sample 1Sample 2
AutoNDA by SimpleDocs
Mandatory rejection. Unless other- wise directed by Commerce:
Sample 1Sample 2
Mandatory rejection. Unless other- wise directed by the Department of En- ergy for a rated order involving all forms of energy:
Sample 1
Mandatory rejection. Unless other- wise directed by the Department of Transportation for a rated order in- volving all forms of civil transpor- tation:
Sample 1

Related to Mandatory rejection

  • Mandatory Redemption The Company is not required to make mandatory redemption or sinking fund payments with respect to the Notes.

  • Mandatory Conditions (a) Should the Employee or the Union fail to comply with any time limit in the grievance procedure, the grievance will be considered to be abandoned, unless the Parties have mutually agreed in writing to extend the time limits.

  • Termination Warning Notice 5.B The Secretary of State may serve a Termination Warning Notice where he considers that:

  • Pack Rejection 6.4.1 <<customer_name>> will notify BellSouth within one business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (i.e. out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI Error Codes will be used. <<customer_name>> will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to <<customer_name>> by BellSouth.

  • Required Notice The Company will advise the appropriate committee or committees as soon as possible, and in any case not less than one hundred and eighty (180) days before the introduction thereof, of mechanization, technological changes and/or automation which the Company has decided to introduce and which will result in terminations or other significant changes in the employment status of employees. The Company will advise the appropriate committee or committees as soon as possible, and in any case not less than thirty (30) days before the expected date of the change of the anticipated time sequence of final installation and production start-up and the anticipated effect on the job status of individual employees.

  • Submitting False Claims The full text of San Francisco Administrative Code Chapter 21, Section 21.35, including the enforcement and penalty provisions, is incorporated into this Agreement. Pursuant to San Francisco Administrative Code §21.35, any contractor or subcontractor who submits a false claim shall be liable to the City for the statutory penalties set forth in that section. A contractor or subcontractor will be deemed to have submitted a false claim to the City if the contractor or subcontractor: (a) knowingly presents or causes to be presented to an officer or employee of the City a false claim or request for payment or approval;

  • PURPOSE/JUSTIFICATION OF RECOMMENDED ACTION The purpose of the Agreement is to provide the City with the services for one full-time equivalent senior criminalist from the Department to perform DNA testing, analysis, and forensic-related consulting as requested by the City, effective July 1, 2016 through June 30, 2021. The City’s current agreement with the County for this position expires on June 30, 2016. This Agreement will not result in the creation of an additional senior criminalist position, as the position was created during the previous agreement.

  • ODUF Pack Rejection 6.4.1 Image Access will notify BellSouth within one (1) business day of rejected packs (via the mutually agreed medium). Packs could be rejected because of pack sequencing discrepancies or a critical edit failure on the Pack Header or Pack Trailer records (e.g., out-of-balance condition on grand totals, invalid data populated). Standard ATIS EMI error codes will be used. Image Access will not be required to return the actual rejected data to BellSouth. Rejected packs will be corrected and retransmitted to Image Access by BellSouth.

  • Statutory Notice Pursuant to section 119.0701(2)(a), F.S., for contracts for services with a contractor acting on behalf of a public agency, as defined in section 119.011(2), F.S., the following applies: IF THE CONTRACTOR HAS QUESTIONS REGARDING THE APPLICATION OF CHAPTER 119, FLORIDA STATUTES, TO THE CONTRACTOR’S DUTY TO PROVIDE PUBLIC RECORDS RELATING TO THIS CONTRACT, CONTACT THE CUSTODIAN OF PUBLIC RECORDS AT THE TELEPHONE NUMBER, EMAIL ADDRESS, AND MAILING ADDRESS PROVIDED IN THE RESULTING CONTRACT OR PURCHASE ORDER. Pursuant to section 119.0701(2)(b), F.S., for contracts for services with a contractor acting on behalf of a public agency as defined in section 119.011(2), F.S., the Contractor shall:

  • Solicitation Exceptions/Deviations Explanation If the bidder intends to deviate from the General Conditions Standard Terms and Conditions or Item Specifications listed in this proposal invitation, all such deviations must be listed on this attribute, with complete and detailed conditions and information included or attached. TIPS will consider any deviations in its proposal award decisions, and TIPS reserves the right to accept or reject any bid based upon any deviations indicated below or in any attachments or inclusions. In the absence of any deviation entry on this attribute, the proposer assures TIPS of their full compliance with the Standard Terms and Conditions, Item Specifications, and all other information contained in this Solicitation.

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