ARRA Requirements Sample Clauses

ARRA Requirements. The Recipient understands and acknowledges that financing pursuant to this Agreement is provided according to the American Recovery and Reinvestment Act of 2009 (ARRA). The Recipient agrees to perform its obligations under this Agreement in compliance with the letter and the spirit of ARRA. The Recipient understands and agrees that failure to comply with ARRA will automatically terminate this Agreement and repayment of any and all Project Funds disbursed to the Recipient will be due and payable immediately.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
ARRA Requirements. The Grantee understands and acknowledges that funding pursuant to this agreement is provided according to the ARRA. The Grantee agrees to perform its obligations under this Agreement in compliance with the letter and the spirit of ARRA. The Grantee understands and agrees that failure to comply with ARRA will automatically terminate any provisions of this Agreement. Upon termination of this Agreement for failure to comply with ARRA, any and all funds disbursed pursuant to this Agreement are to be repaid to the State Water Board immediately.
Sample 1Sample 2Sample 3
ARRA Requirements. The Contractor is notified that this project will be financed with American Recovery and Reinvestment Act of 2009 (hereinafter, “ARRA”) Funds. The Contractor shall ensure that all subcontracts and other contracts for goods and services for an ARRA-funded project have the mandated provisions of this directive in their contracts. Pursuant to Title XV, Section 1512 of the ARRA, the State shall require that the Contractor provide reports and other employment information as evidence to document the number of jobs created or jobs retained by this contract from the Contractor’s own workforce and any sub-contractors. No direct payment will be made for providing said reports, as the cost for same shall be included in the various items in the contract. Required Contract Provision to Implement ARRA Section 902 Section 902 of the ARRA requires that each contract awarded using ARRA funds must include a provision that provides the U.S. Comptroller General and his representatives with the authority to:
Sample 1
ARRA Requirements. This contract may involve vendor payments over $25,000 and funding under the American Recovery & Reinvestment Act of 2009 (“Recovery Act”). When Recovery Act funds are involved, University will advise vendor and vendor agrees to (1) comply with all terms and conditions of the Recovery Act (including but not limited to “Buy American”, “Wage Rate Requirements” and “Disclosure of Fraud or Misconduct”) and
Sample 1
ARRA Requirements. Community acknowledges that the Capacity Building Grant and the Performance Incentive, if any, awarded under this Agreement are or may be, in full or in part, funded by Clean Energy Works with EECBG award dollars. In addition to compliance with the American Recovery and Reinvestment Act of 2009, Pub. L. 111-5 requirements (“ARRA Requirements”) attached as Exhibit E, Community agrees (i) to make documents, papers, and records relevant to the work performed available to Clean Energy Works and/or DOE, or their duly authorized representative for examination, copying, or mechanical reproduction, and (ii) to be subject to the examination and audit of records related to the sub-grant award of ARRA-related funds, and (iii) to retain all financial records, supporting documents, statistical records, evaluation data, program performance data, member information and personnel records related to the sub-grant for a period of five (5) years after:
Sample 1

Related to ARRA Requirements

  • HIPAA Requirements The Parties agree that the provisions under HIPAA Rules that are required by law to be incorporated into this Amendment are hereby incorporated into this Agreement.

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

  • 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. Item Not Received additional requirements 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.

  • TITLE VI REQUIREMENTS H-GAC in accordance with the provisions of Title VI of the Civil Rights Act of 1964 (78 Xxxx. 000, 00 X.X.X. §§ 0000x to 2000d-4) and the Regulations, hereby notifies all bidders that it will affirmatively ensure that any disadvantaged business enterprises will be afforded full and fair opportunity to submit in response to this Agreement and will not be discriminated against on the grounds of race, color, or national origin in consideration for an award.

  • 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.

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

  • Match Requirements There is no match required on the part of the Grantee under this Agreement.

  • PJM Requirements The DS Supplier acknowledges and agrees that, as a member of PJM, the Company is bound by all PJM operating instructions, policies and procedures as are currently set forth in the PJM Operating Manual, which are available through the Internet on the PJM Home Page (xxxx://xxx.xxx.xxx), as may be revised from time to time, which are needed to maintain the integrity of the PJM system. The DS Supplier acknowledges and agrees that it will cooperate with the Company so that the Company will be in compliance with all PJM Emergency Operations Procedures, which include, but are not limited to, those procedures pertaining to minimum and maximum generation Emergencies, and measures requiring involuntary Customer participation, such as supply voltage reduction or full interruption of Customer load by either manual or automatic means.

  • Staff Requirements Contractor shall employ, at a minimum, the following:

  • Time Requirements The Independent Contractor will not be required to follow or establish a regular or daily work schedule, but shall devote during the term of this Agreement the time, energy and skill as necessary to perform the services of this engagement and shall, periodically or at any time upon the request of the Company, submit information as to the amount of time worked and scope of work performed.

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