Grant - Transfer Corrections Sample Clauses

Grant - Transfer Corrections. If the amount previously reported during a transfer was incorrect, a Grant - Transfer Correction may be requested. This type of variation request should be reported to RGS via email. This variation type is commonly used when: there are additional funds to be transferred to the new Administering Organisation that were not included in the original transfer (i.e. funds located at another organisation on the grant) there are funds to be returned to the previous Administering Organisation as costs associated with the Grant were not identified at the time of transfer. Note: if the previous Administering Organisation is requesting that funds be returned to them, they must first communicate with the new Administering Organisation and seek their agreement. The Funding Entity will not process this type of request unless both organisations have agreed to the request in writing, and it is provided to the Funding Entity. To submit a Grant - Transfer Correction the Funding Entity will require the following: The email should include Agreement from the Administering Organisation/s The Funding Entity requires agreement from both organisations if funds are to be moved from the current organisation to the previous organisation. If the previous Administering Organisation wishes to provide additional funds to the new Administering Organisation, then an email from the previous Administering Organisation will suffice. Details of the correct transfer amount to be transferred Details of the exact amount that should have been reported as spent in total. Up to 500 words should be provided outlining why the transfer correction is required. For these variations, Research Offices must email the relevant details/documentation to RGS at xxx-xxxxxx@xxx.xxx.xx for processing.
Sample 1
AutoNDA by SimpleDocs

Related to Grant - Transfer Corrections

  • Contract Transition Upon Contract expiration or termination, the Contractor shall ensure a seamless transfer of Contract responsibilities with any subsequent Contractor necessary to transition the Products and services of the Contract. The incumbent Contractor assumes all expenses related to the contract transition.

  • MASTER CONTRACT TRANSITION Contractor represents and warrants that, in the event this Master Contract or a similar contract, is transitioned to another contractor (e.g., Master Contract expiration or termination), Contractor shall use commercially reasonable efforts to assist Enterprise Services for a period of sixty (60) days to effectuate a smooth transition to another contractor to minimize disruption of service and/or costs to the State of Washington.

  • Deliverables for an Authorized User Agreement (Transaction Deliverables must be identified, as a measure of progress in the Authorized User Agreement. A Deliverable as a bulk number of hours is not permissible under the OGS Centralized Contract. Retainage As part of the Mini-Bid, the Authorized User may elect to retain a percentage of each individual Deliverable payment of no more than 20% until the acceptance of the complete Deliverable or project. This retainage may be reduced as described in the Mini-Bid, when the Contractor substantially reduces the time required from the timeframes negotiated between the Authorized User and the Contractor for the completion and acceptance of a Deliverable.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Modifications and Updates to the Wire Center List and Subsequent Transition Periods 2.1.4.12.1 In the event BellSouth identifies additional wire centers that meet the criteria set forth in Section 2.1.4.5, but that were not included in the Initial Wire Center List, BellSouth shall include such additional wire centers in a carrier notification letter (CNL). Each such list of additional wire centers shall be considered a “Subsequent Wire Center List”.

  • Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except:

  • EFFECTIVE DATE OF CONTRACT This contract shall not become effective until and unless approved by the City of Nashua.

  • TIME OF CONTRACT This Contract shall commence on , and shall terminate on . Certificate(s) of Insurance must be current on day Contract commences and if scheduled to lapse prior to termination date, must be automatically updated before final payment may be made to Contractor. The final invoice must be submitted within 30 days of completion of the stated scope of services.

  • Sole Source as Grounds for Rejection of a Change Order If a Change Order is submitted to Contractor for the purposes of adding a Bulletin to this Contract and said Bulletin designates a Sole Source from which Contractor is required to procure goods or services necessary to perform the Work, which Sole Source has not been designated previously, Contractor shall be entitled to reject the proposed Change Order if the designated Sole Source refuses to provide to Contractor the warranties, bonds, terms or schedule required under the Contract Documents, including any warranty or terms or schedule required by Bulletins referenced in the proposed Change Order. In such event, Contractor shall give written notice to the Owner rejecting the proposed Change Order and, if possible, shall accompany said written notice with a proposal from Contractor for changes or modifications to the Bulletin so as to eliminate the Sole Source designation but to achieve goods or services equal in quality or function. The Owner may then require the Design Professional to revise the subject Bulletin so as to eliminate the designation of the Sole Source by incorporation of Contractor's proposal or otherwise. Upon revision of the Bulletin by the Design Professional and approval thereof by the Owner, the Owner shall again submit to the Contractor a proposed Change Order for the purpose of adding the revised Bulletin to this Contract. If the Owner decides to retain the Sole Source in the Change Order and Contractor cannot acquire the full contractually required warranties from the Sole Source, Contractor shall be held only to the warranty terms and schedule obtainable from the Sole Source.

  • ASSIGNMENT, TRANSFER, AND SUBCONTRACTING Contractor may not assign, transfer, or subcontract any portion of this contract without the Department's prior written consent. (18-4-141, MCA) Contractor is responsible to the Department for the acts and omissions of all subcontractors or agents and of persons directly or indirectly employed by such subcontractors, and for the acts and omissions of persons employed directly by Contractor. No contractual relationships exist between any subcontractor and the Department under this contract.

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