<p> COST TRANSFER REQUEST – (For Transfers to a Foundation “07” Account) CALIFORNIA STATE UNIVERSITY, LONG BEACH FOUNDATION (562)985-8147</p><p>Per the Foundation Cost Transfer Policy #4-120.1, this form should be used when you are requesting to transfer expenses to a Foundation 07 account.</p><p>Project # (8 digits) Requestor Date (requested) Phone Number</p><p>From: To: Detail of costs to be transferred: From GL # To GL # Post Reference # Description Amount (6 digits) (6 digits) Date (FDN REF#)</p><p>Justification: Transfers requested within 90 days of occurrence require that questions 1 and 2 are answered; transfers requested more than 90 days after occurance require that all 4 questions are answered. Please note that expenditure transfer should neer take place more than 60 days past the project end date. Please attach additional pages if necessary. See attached instructions for guidance in completing these sections.</p><p>(1) Why was this expense charged originally to the project from which is now being transferred?</p><p>(2) Why should this charge be transferred to the proposed receiving sponsored project?</p><p>(3) If the request for the cost(s) to be transferred is 90 days after the post date for the cost(s), explain why the corection was not made timely per Federal guidelines and Foundation policy.</p><p>(4) If the request for the cost(s) to be transferred is 90 days after the post date for the costs(s), explain what steps will be taken to assure that all cost transfers will be requested within the 90 day time period.</p><p>Certification: I certify that the above-mentioned costs are appropriate expenditure for the sponsored grant or contract charged and that the expenditure complies with the terms and restrictions governing that sponsored grant or contract.</p><p>Project Director for “To account” or Authorized Designee (Name and Signature) Date</p><p>Approval: Associate Director of Grants and Contracts Date</p><p>For Foundation Use Only: Grant and Contract Administrator reviewed: (initial and date)</p><p>Rev. January 2007 COST TRANSFER REQUEST INSTRUCTIONS CALIFORNIA STATE UNIVERSITY, LONG BEACH FOUNDATION</p><p>From project # - The project # (8 digits) where the charge is currently posted.</p><p>To project # - The project # (8 digits) where the charge should be posted.</p><p>Requestor - The name of the person completing the form.</p><p>Date requested - The date the form is completed.</p><p>From GL line item # - The GL (6 digits) line item of the original charge.</p><p>To GL line item # - The GL (6 digits) line item where the charge should be posted.</p><p>Post date - The posted date of the original expenditure on the General Ledger.</p><p>Reference Number - The primary reference number on the original transaction, which can be found on the Project Detail- Project Report in the FDN REF# column. If you don't provide the reference number (FDN REF#), attach a copy ofthe detail report with the expense(s) to be transferred highlighted.</p><p>Description - The Short Description on the original transaction.</p><p>Amount - The total direct amount to be transferred. Associated F&A costs will be automatically transferred. If only a portion of an expense item is being transferred, explain why in the justification section.</p><p>Justification -</p><p>(1) Per OMB Circular A-21 guidelines, expenses " . .. may not be shifted to other sponsored agreements in order to meet deficiencies caused by overruns or other fund considerations, to avoid restrictions imposed by or by terms of the sponsored agreement, or for other reasons of convenience."</p><p>The following are acceptable reasons for a cost transfer:</p><p> To move expenses to a new account created after the budget start date</p><p> To move appropriate and approved pre-award costs to an account</p><p> The administrator misunderstood the Project Director's instructions on how to allocate the cost</p><p> The Project Director has multiple funding sources for the same project and he/she provided the wrong account number to charge</p><p> To move a cost overrun to a non-sponsored account (e.g. to a Foundation (06) program account)</p><p> To move costs between NTH or NSF projects which have been designated as "closely related projects" by approving Grants Officer.</p><p>The following are not acceptable reasons for a cost transfer:</p><p> To transfer costs to cover a deficit on another award</p><p> To transfer costs to spend the balance of an award</p><p>(2) Ifan expense is being moved to a 07 account, it is necessary to explain how that cost benefits the project. If the cost is typically considered an F&A cost (See Direct Charging Policy 4-100.1), please also justify why it can be charged directly to the account.</p><p>Rev. January 2007 (3) Per Foundation policy, it is required that cost transfers be requested within 90 days of the original charge. Only in cases of exceptional circumstances will cost transfers be permitted more than 90 days after the original charge. Additional explanation is required here to document the reason for the lateness of the request.</p><p>(4) Per Foundation policy, if the cost transfer request is made more than 90 days after the original posting date of the expense, describe what steps will be taken to assure that transfer requests are made timely in the future.</p><p>Please see the Foundation Cost Transfer Policy 4-120.1 for further guidance.</p><p>Certification - This should be the signature of the Project Director (PD) assigned to the project the expense is being transferred to. The PD should review the request for completeness and accuracy. The PD's responsibility is to ensure that the University is in compliance with these regulations. The PO is responsible for ensuring that cost transfers are:</p><p> Made within 90 days after the month in which the cost was originally recorded on the Financial Accounting System but no later than 60 days after the project terminates, and</p><p> Supported by a written explanation that describes in detail why the transfer is necessary.</p><p>Approval - The Associate Director of Grants and Contracts will review the request for completeness and allowability.</p><p>Rev. January 2007</p>