FLY AMERICA REQUIREMENTS Sample Clauses

FLY AMERICA REQUIREMENTS. This provision applies to all Agreements that involve the transportation of persons or property, by air, between a place in the U.S. and a place outside the U.S., or between places outside the U.S. (a) The Contractor agrees to comply with 49 U.S.C. Section 40118 (the “Fly America Act”) in accordance with the General Services Administration’s regulations at 41 CFR Part 301-10, which provide that recipients and subrecipients of Federal funds and their contractors are required to use U.S. flag air carriers for U.S Government-financed international air travel and transportation of their personal effects or property, to the extent such service is available, unless travel by foreign air carrier is a matter of necessity, as defined by the Fly America Act. (b) The Contractor shall submit the “Fly America Certification” if the regulation is applicable to the particular Agreement.
Sample 1Sample 2Sample 3See All (11)
AutoNDA by SimpleDocs
FLY AMERICA REQUIREMENTS. The Contractor agrees to comply with 49 U.S.C. 40118 (the "Fly America" Act) in accordance with the General Services Administration's regulations at 41 CFR Part 301-10, which provide that recipients and subrecipients of Federal funds and their Contractors are required to use U.S. Flag air carriers for U.S Government-financed international air travel and transportation of their personal effects or property, to the extent such service is available, unless travel by foreign air carrier is a matter of necessity, as defined by the Fly America Act. The Contractor shall submit, if a foreign air carrier was used, an appropriate certification or memorandum adequately explaining why service by a U.S. flag air carrier was not available or why it was necessary to use a foreign air carrier and shall, in any event, provide a certificate of compliance with the Fly America requirements. The Contractor agrees to include the requirements of this section in all subcontracts that may involve international air transportation.
Sample 1Sample 2See All (10)
FLY AMERICA REQUIREMENTS. Applicability-All contracts involving transportation of persons or property, by air between the U.S. and/or places outside the U.S. These requirements do not apply to micro-purchases ($3,000 or less, except for construction contracts over $2,000). Contractor shall comply with 49 USC 40118 (the “Fly America” Act) in accordance with General Services Administration regulations 41 CFR 301-10, stating that recipients and subrecipients of Federal funds and their contractors are required to use US Flag air carriers for US Government-financed international air travel and transportation of their personal effects or property, to the extent such service is available, unless travel by foreign air carrier is a matter of necessity, as defined by the Fly America Act. Contractor shall submit, if a foreign air carrier was used, an appropriate certification or memorandum adequately explaining why service by a US flag air carrier was not available or why it was necessary to use a foreign air carrier and shall, in any event, provide a certificate of compliance with the Fly America requirements. Contractor shall include the requirements of this section in all subcontracts that may involve international air transportation.
Sample 1See All (4)
FLY AMERICA REQUIREMENTS. The Fly America requirements apply to all Contracts greater than $3,000 which include the transportation of persons or property, by air, between a place in the U.S. and a place outside the U.S., or between places outside the U.S. The Contractor agrees to comply with 49 U.S.C. 40118 (the “Fly America” Act) in accordance with the General Services Administration’s regulations at 41 CFR Part 301-10, which provide that recipients and sub-recipients of Federal funds and their Contractors are required to use U.S. Flag air carriers for U.S. Government-financed international air travel and transportation of their personal effects or property, to the extent such service is available, unless travel by foreign air carrier is a matter of necessity, as defined by the Fly America Act. The Contractor shall submit, if a foreign air carrier was used, an appropriate certification or memorandum adequately explaining why service by a U.S. flag air carrier was not available or why it was necessary to use a foreign air carrier and shall, in any event, provide a certificate of compliance with the Fly America requirements. The Contractor agrees to include the requirements of this section in all subcontracts that may involve international air transportation.
Sample 1Sample 2
FLY AMERICA REQUIREMENTS. The Federal Government will not participate in the costs of international air transportation of any persons involved in or property acquired for the Project unless that air transportation is provided by US flag air carriers to the extent service by these carriers is available, as required by the International Air Transportation Fair Competitive Practices Act of 1974, as amended, 49 USC § 40118, in accordance with US GAO regulations, "Uniform Standards and Procedures for Transportation Transactions." 4 CFR Part 52, and US GAO Guidelines for Implementation of the "Fly America Act," B‐138942, 1981 US Comp. Gen. LEXIS 2116, March 31, 1981.
Sample 1
FLY AMERICA REQUIREMENTS. In each contract under which funds provided under this award might be used to participate in costs of international air travel or transportation for people or property, you must include a clause to require the contractor to: a. Comply with the International Air Transportation Fair Competitive Practices Act of 1974 (49 U.S.C. 40118, also known as the "Fly America" Act), as implemented by the General Services Administration at 41 CFR 301-10.131 through 301-10.143, which provides that U.S Government-financed international air travel and transportation of personal effects or property must use a U.S. Flag air carrier or be performed under a cost-sharing arrangement with a U.S. carrier, if such service is available; and b. Include the requirements of the Fly America Act in all subcontracts that might involve international air transportation.
Sample 1
FLY AMERICA REQUIREMENTS 
Sample 1
AutoNDA by SimpleDocs

Related to FLY AMERICA REQUIREMENTS

  • Basic Requirements To be eligible for PayPal’s Seller Protection program, all of the following basic requirements must be met, as well as any applicable additional requirements: • The primary address for your PayPal account must be in the United States. • The item must be a physical, tangible good that can be shipped, except for items subject to the Intangible Goods Additional Requirements. Transactions involving items that you deliver in person in connection with payment made in your physical store, may also be eligible for PayPal’s Seller Protection program so long as the buyer paid for the transaction in person by using a PayPal goods and services QR code. • You must ship the item to the shipping address on the Transaction Details page in your PayPal account for the transaction. If you originally ship the item to the recipient’s shipping address on the Transaction Details page but the item is later redirected to a different address, you will not be eligible for PayPal’s Seller Protection program. We therefore recommend not using a shipping service that is arranged by the buyer, so that you will be able to provide valid proof of shipping and delivery. • The shipping requirement does not apply to eligible transactions involving items that you deliver in person; provided, however, that you agree to provide us with alternative evidence of delivery or such additional documentation or information relating to the transaction that we may request. • You must respond to PayPal’s requests for documentation and other information in a timely manner as requested in our email correspondence with you or in our correspondence with you through the Resolution Center. If you do not respond to PayPal’s request for documentation and other information in the time requested, you may not be eligible for PayPal’s Seller Protection program. • If the sale involves pre-ordered or made-to-order goods, you must ship within the timeframe you specified in the listing. Otherwise, it is recommended that you ship all items within 7 days after receipt of payment. • You provide us with valid proof of shipment or delivery. • The payment must be marked “eligible” or “partially eligible” in the case of Unauthorized Transaction claims, or “eligible” in the case of Item Not Received claims, for PayPal’s Seller Protection program on the Transaction Details page. • In the case of an Unauthorized Transaction claim, you must provide valid proof of shipment or proof of delivery that demonstrates that the item was shipped or provided to the buyer no later than two days after PayPal notified you of the dispute or reversal. For example, if PayPal notifies you of an Unauthorized Transaction claim on September 1, the valid proof of shipment must indicate that the item was shipped to the buyer no later than September 3 to be eligible for PayPal’s Seller Protection program. PayPal determines, in its sole discretion, whether your claim is eligible for PayPal’s Seller Protection program. PayPal will make a decision, in its sole discretion, based on the eligibility requirements, any information or documentation provided during the resolution process, or any other information PayPal deems relevant and appropriate under the circumstances. To be eligible for PayPal’s Seller Protection program for a buyer’s Item Not Received claim, you must meet both the basic requirements and the additional requirements listed below: • Where a buyer files a chargeback with the issuer for a card-funded transaction, the payment must be marked “eligible” for PayPal’s Seller Protection on the Transaction Details page. • You must provide proof of delivery as described below.

  • W-9 Requirement Alongside a signed copy of this Agreement, Grantee will provide Florida Housing with a properly completed Internal Revenue Service (“IRS”) Form W-9. The purpose of the W-9 form is to document the SS# or FEIN# per the IRS. Note: W-9s submitted for any other entity name other than the Grantee’s will not be accepted.

  • E-Verify Requirements To the extent applicable under ARIZ. REV. STAT. § 41- 4401, the Contractor and its subcontractors warrant compliance with all federal immigration laws and regulations that relate to their employees and their compliance with the E-verify requirements under ARIZ. REV. STAT. § 23-214(A). Contractor’s or its subcontractor’s failure to comply with such warranty shall be deemed a material breach of this Agreement and may result in the termination of this Agreement by the City.

  • Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

  • Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.

  • Personnel Requirements a. The CONTRACTOR shall secure, at the CONTRACTOR'S own expense, all personnel required to perform this Contract. b. The CONTRACTOR shall ensure that the CONTRACTOR'S employees or agents are experienced and fully qualified to engage in the activities and perform the services required under this Contract, and that all applicable licensing and operating requirements imposed or required under federal, state, or county law, and all applicable accreditation and other standards of quality generally accepted in the field of the activities of such employees and agents are complied with and satisfied.

  • Data Requirements ‌ • The data referred to in this document are encounter data – a record of health care services, health conditions and products delivered for Massachusetts Medicaid managed care beneficiaries. An encounter is defined as a visit with a unique set of services/procedures performed for an eligible recipient. Each service should be documented on a separate encounter claim detail line completed with all the data elements including date of service, revenue and/or procedure code and/or NDC number, units, and MCE payments/cost of care for a service or product. • All encounter claim information must be for the member identified on the claim by Medicaid ID. Claims must not be submitted with another member’s identification (e.g., xxxxxxx claims must not be submitted under the Mom’s ID). • All claims should reflect the final status of the claim on the date it is pulled from the MCE’s Data Warehouse. • For MassHealth, only the latest version of the claim line submitted to MassHealth is “active”. Previously submitted versions of claim lines get offset (no longer “active” with MassHealth) and payments are not netted. • An encounter is a fully adjudicated service (with all associated claim lines) where the MCE incurred the cost either through direct payment or sub-contracted payment. Generally, at least one line would be adjudicated as “paid”. All adjudicated claims must have a complete set of billing codes. There may also be fully adjudicated claims where the MCE did not incur a cost but would otherwise like to inform MassHealth of covered services provided to Enrollees/Members, such as for quality measure reporting (e.g., CPT category 2 codes for A1c lab tests and care/patient management). • All claim lines should be submitted for each Paid claim, including zero paid claim lines (e.g., bundled services paid at an encounter level and patient copays that exceeded the fee schedule). Denied lines should not be included in the Paid submission. Submit one encounter record/claim line for each service performed (i.e., if a claim consisted of five services or products, each service should have a separate encounter record). Pursuant to contract, an encounter record must be submitted for all covered services provided to all enrollees. Payment amounts must be greater than or equal to zero. There should not be negative payments, including on voided claim lines. • Records/services of the same encounter claim must be submitted with same claim number. There should not be more than one active claim number for the same encounter. All paid claim lines within an encounter must share the same active claim number. If there is a replacement claim with a new version of the claim number, all former claim lines must be replaced by the new claim number or be voided. The claim number, which creates the encounter, and all replacement encounters must retain the same billing provider ID or be completely voided. • Plans are expected to use current MassHealth MCE enrollment assignments to attribute Members to the MassHealth assigned MCE. The integrity of the family of claims should be maintained when submitting claims for multiple MCEs (ACOs/MCO). Entity PIDSL, New Member ID, and the claim number should be consistent across all lines of the same claim. • Data should conform to the Record Layout specified in Section 3.0 of this document. Any deviations from this format will result in claim line or file rejections. Each row in a submitted file should have a unique Claim Number + Suffix combination. • A feed should consist of new (Original) claims, Amendments, Replacements (a.k.a. Adjustments) and/or Voids. The replacements and voids should have a former claim number and former suffix to associate them with the claim + suffix they are voiding or replacing. See Section 2.0, Data Element Clarifications, for more information. • While processing a submission, MassHealth scans the files for the errors. Rejected records are sent back to the MCEs in error reports in a format of the input files with two additional columns to indicate an error code and the field with the error. • Unless otherwise directed or allowed by XxxxXxxxxx, all routine monthly encounter submissions must be successfully loaded to the MH DW on or before the last day of each month with corrected rejections successfully loaded within 5 business days of the subsequent month for that routine monthly encounter submission to be considered timely and included in downstream MassHealth processes. Routine monthly encounter submissions should contain claims with paid/transaction dates through the end of the previous month.

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • Check Requirements Any image of a check that I transmit to you must accurately and legibly provide all the information on the front and back of the check at the time presented to me by the drawer. Prior to capturing the original check, I will indorse the back of the original check. My endorsement will include "For Directions E- Deposit Only" in addition to my signature. The image of the check transmitted to you must accurately and legibly provide, among other things, the following information: (1) the information identifying the drawer and the paying bank that is preprinted on the check, including complete and accurate MICR information and the signature(s); and (2) other information placed on the check prior to the time an image of the check is captured, such as any required identification written on the front of the check and any endorsements applied to the back of the check. The image quality for the check will meet the standards for image quality established by the American National Standards Institute ("ANSI"), the Board of Governors of the Federal Reserve, and any other regulatory agency, clearing house or association. Rejection of Deposit. You are not liable for any service or late charges levied against me due to your rejection of any item. In all cases, I am responsible for any loss or overdraft plus any applicable fees to my Account due to an item being returned. Items Returned Unpaid. A written notice will be sent to me of transactions you are unable to process because of returned items. With respect to any item that I transmit to you for remote deposit that you credit to my Account, in the event such item is dishonored, I authorize you to debit the amount of such item from the Account.

  • Network Requirements Customer shall be responsible for ensuring that all aspects of the applicable network environment(s) adhere to the applicable standards and requirements specified in the Documentation and are configured appropriately to its proposed use of Ordered SaaS Services.

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