Audit of the Recipient. Except as the Federal Government determines otherwise in writing, the Recipient agrees that:
Audit of the Recipient Sample Clauses
Related to Audit of the Recipient
Final Report Outline The Recipient shall Prepare a Final Report Outline in accordance with the Energy Commission Style Manual provided by the CAM. Recipient Products: • Final Report Outline (draft and final) CAM Product: • Energy Commission Style Manual • Comments on Draft Final Report Outline • Acceptance of Final Report Outline
Responsibilities of the Recipient Section 3.01. The Recipient shall cooperate with the Administrator, the Bank and the Consultants to ensure that the Technical Assistance is carried out promptly and effectively and, for this purpose, shall issue appropriate instructions to its officials, agents and representatives.
Final Report The Recipient shall Prepare a Final Report for this Agreement in accordance with the approved Final Report Outline, Style Manual, and Final Report Template provided by the CAM with the following considerations: o Ensure that the report includes the following items, in the following order: Cover page (required) Credits page on the reverse side of cover with legal disclaimer (required) Acknowledgements page (optional) Preface (required) Abstract, keywords, and citation page (required) Table of Contents (required, followed by List of Figures and List of Tables, if needed) Executive summary (required) Body of the report (required) References (if applicable) Glossary/Acronyms (If more than 10 acronyms or abbreviations are used, it is required.) Bibliography (if applicable) Appendices (if applicable) (Create a separate volume if very large.) Attachments (if applicable) o Ensure that the document is written in the third person. o Ensure that the Executive Summary is understandable to the lay public. Briefly summarize the completed work. Succinctly describe the project results and whether or not the project goals were accomplished. Identify which specific ratepayers can benefit from the project results and how they can achieve the benefits. If it’s necessary to use a technical term in the Executive Summary, provide a brief definition or explanation when the technical term is first used.
Obligations of the Recipient In consideration of the payment received under Section 3 below, the RECIPIENT shall perform the Activities and provide SANOFI with the Counterpart in good faith and accordance with the provisions of this Agreement, the laws and practices applicable to the Activities. The RECIPIENT certifies that it has the status of sponsorship recipient. The RECIPIENT shall immediately inform SANOFI if the funds (donation and/or other contribution) provided by SANOFI and all its Affiliates to the RECIPIENT exceeds the threshold of one hundred and fifty thousand euros (150.000€) during the calendar year of this Agreement. If due to the changed circumstances, the RECIPIENT loses his right to receive the funding, the RECIPIENT must immediately notify SANOFI in writing and the Agreement will automatically terminate. In invitations to the Activities, it must be clear to the recipients of such invitations that the Activities are sponsored by SANOFI and, if other pharmaceutical companies sponsor the Activities as well, it must be clear to the HCPs that the Activities are also sponsored by such other pharmaceutical companies.
Representative of the Recipient; Addresses Section 7.01. The Minister of Finance of the Recipient is designated as representative of the Recipient for the purposes of Section 11.03 of the General Conditions.
Other Directory Services 73.10.1 Both parties acknowledge that CenturyLink’s directory publisher is not a party to this Agreement and that the provisions contained in this Agreement are not binding upon CenturyLink’s directory publisher.
ENGAGEMENT OF THE PROVIDER The OAG engages the Provider to perform services as specified in this Agreement. All services are to be performed solely by the Provider and may not be subcontracted or assigned without prior written consent of the OAG. The consent of the OAG does not vest any rights in the subcontractor or create any obligation on behalf of the OAG to the subcontractor. All subcontract agreements will contain a disclosure to this effect. This Agreement will be performed in accordance with the rules implementing the provisions of VOCA, 34 U.S.C. § 20103, Crime Control and Law Enforcement, 28 C.F.R. §§ 94.101 through 94.122, the federal government-wide grant rules as set forth in 2 C.F.R. § 200, et. seq., and the U.S. Department of Justice, (DOJ), Office of Justice Programs, DOJ Grants Financial Guide, (Financial Guide), and any other regulations or guidelines currently or subsequently required by the U.S. Department of Justice and State or Federal laws.
Independent Service Provider The services to be performed by Service Provider are those of an independent service provider and not of an employee of the City of Fort Xxxxxxx. The City shall not be responsible for withholding any portion of Service Provider's compensation hereunder for the payment of FICA, Workmen's Compensation or other taxes or benefits or for any other purpose.
Independent Subrecipient Subrecipient shall be considered an independent contractor and neither Subrecipient, its employees, nor anyone working under Subrecipient shall be considered an agent or an employee of County. Neither Subrecipient, its employees nor anyone working under Subrecipient shall qualify for workers’ compensation or other fringe benefits of any kind through County.
Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-‐based Directory Service at <whois.nic.TLD> providing free public query-‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.
