Overview
This article describes the interim process for requesting a temporary extension on a Sponsored Project to allow for continued spending until Award modification is received.
Awards Waiting for Amendment:
- If a department is waiting for a modification from the agency to extend dates of the Award, the department can take the steps below to request a Date Extension:
Next Steps
1. While the Oracle PPM Award Temporary Extension Request Form is being modified to add the cognizant Vice Chancellor (VC) approval workflow, request Department and VC Approval via email by sending the request to your MSO/DBO and AVC in your area, who will secure required VC approval and indicate/include the following:
-
- Award Information:
- PI Name
- Award ID:
- Project #
-
- Request Type and Dates:
- 1st request (12 month total extension) or 2nd request (18 month total extension)
- Current End Date
- Temporary Extension/New End Date
c. Justification for the extension
d. Documentation and Commitment required by the cognizant VC:
-
-
- Written documentation of the funding agency’s commitment to awarding and prompt disbursal of anticipated funding. (Deans or VCs may determine that available documentation provides insufficient confidence of funding).
- Written commitment from the PI’s Dean that in the event of unanticipated delays in funding, the School will cover all costs associated with advance spending and/or temporary extensions, including the full costs of any personnel actions (such as layoffs or severance) that result from unreimbursed off-cycle spending approved through these processes.
- Advance spending or temporary extension of spending on any grant or contract with expenditures in multiple Schools or VC areas requires the approval of all Deans and VCs where expenditures will be located.
2. Once approval has been granted by the VC, submit an Oracle PPM Award Temporary Extension Request.
3. In the Description field you must indicate the following:
a. Indicate which of the following 2 extensions types you are requesting on the Oracle PPM Award:
1. Results in a one-time 12 month extension on the Award/Project but requires department leadership approval (MSO/DBO), cognizant VC approval and is subject to SPF review*
-
-
- For Flow Thru Awards where carry over requires prior approval or anytime the Contract requires separate yearly billing, a new Project will be created in most cases instead of extending current Project dates.
- The original proposal should refer to the projected length of work (departments can elaborate on exceptions).
2. Results in an additional 6 month extension on the Award/Project (18 months total), but requires MSO, PI, cognizant VC approval, and SPF Director approval.
-
-
- *SPF will review and extend current Project periods, or, with department partnership create a new Project under the same Award.
b. OFC Award Number
c. Project Number (7-numeric)
d. Brief Justification
-
- Example of Request Justification:
- Award xxxx is ending on xxxx
- However, we are expecting a modification on this Award and it is currently held up due to xxxx.
- Attached is the support from the PI that this work is continuing based on correspondence with the Sponsor.
- Also attached are approval by the cognizant Vice Chancellor
- Also attached is confirmation from the Business Officer that the department is responsible for any costs incurred beyond the Sponsor approved Award End Date.
- It is understood that if the modification is not received, the department will need to process Cost Transfers to a discretionary source.
- Costs would be moved to the department default Project if no other source is provided.
4. MSOs should certify understanding of the following in their approval, I certify my understanding that by approving this request, if the amendment is not made available, the department will be responsible for covering the costs with discretionary funds.
5. Attach approvals from sponsor, DBO and VC as required by the extension requested on the Oracle PPM Award e.g., Extension Request 1 or 2
Essential Information
Understanding Dates in Oracle PPM:
- Expenditure Item (EI) Date: Date a cost was incurred (service or good provided)
- Project End Date: Date Project ends
- Award End Date: Date Award ends this is derived from the Contract End Date.
- Our configuration has the Project End Date=Award End Date.
- Oracle functionality (not a configuration) is such that EI Date must be within:
- Project End Date, regardless of accounting posting date.
- Project End Dates cannot be backdated once sent.
- Budget Period Dates, regardless of accounting posting date.
- Budget Period Dates cannot be backdated once sent (Oracle functionality and is a highly rated enhancement request from the Grants community)
- Control Budget Dates.
- Contracts drive billing controls (dates and dollars)
- Contract (Award) Dates, regardless of accounting posting date.
- Award End Date will also stop transactions from posting, but we are able to manually adjust the end date to a future or past date.
- Sponsored Projects Expenses are allowable if they are incurred during the Award.
- In IFIS, if costs posted to the ledger after the Award End Date, departments had to justify they were incurred during the time of the Award.
- In Oracle, they just need to provide the correct EI Date, which is a system-driven control for Sponsored Research.
- PPM Costs that are not able to be posted for date issues are considered Unprocessed Costs.
Mid-month End Date Awards:
- OCGA will encourage negotiations to have end of month end dates.
- Promote that source systems are checking Project End Date changes that post to Projects within 14 days of the End Date of the Project.
- This would cause the costs to post to Unprocessed Costs and Sponsored Projects Finance (SPF) would review allowability and edit the EI date if the costs were reflective of the mid month end date.