Instructions to Complete & Submit a DCF (Non-Labor AP Transaction)
EFFECTIVE DECEMBER 1, 2024
Step 1: Budget Performance Report: Download your BPR (Budget Performance Report) to show your posted transaction. You will use this information to fill out the FROM section (examples: GL Report (GL324) for departmental transactions and PI Dashboard or GM (GM139) reports for Sponsored Projects transactions)
Step 2. Non-Labor Cost Transfer Justification Form: Complete the Non-Labor Cost Transfer Justification Form. Questions 1-4 should be answered for all cost transfers and the School/Dept/Center should sign.
If question 5 ((a) More than 90 days after posting (b) After a final financial report/invoice has been completed (c) If there is a cost overrun on the sponsored project) is completed then the PI and Pod Manager need to sign as well (this will then be processed though GCAS where the GCAS SPFA and GCAS Controller Designee will review and sign).
Please answer all questions with a detailed response. Make sure the CTJF is signed by all of the appropriate individuals.
Submitting the Form in Concur Request
- Log in to iBuy website: https://ibuy.gwu.edu/ and select IBUY+CONCUR PORTAL (blue box).
- Sign in to Concur.
Select Requests from the Home dropdown menu.
ImageSelect Create New Request.
ImageSelect DCF from the Type of Request dropdown menu.
ImageName of Requestor, Grant Indicator and Home Org will autofill. You will need to fill in the sections: Is this a Grant Request, A/P Detail (Vendor + Invoice) & JE Desc and Comments. Then select Create Request (bottom right).
Image
Your request has now been created and you can move to the From and To portions. You can use multiple From and To sections as needed.
Remember that only one invoice can be used per submission!!
Select Add.
ImageSelect DCF FROM.
Image
All of the information for the FROM section will be taken directly from your BPR (Budget Performance Report) backup documentation (GL324B, GM139, PI Dashboard, etc.). Please see below:
Account (GL: Account/GM: Resource Detail Number)
BPR Date (GL: Effective Date/GM: PA Date)
Grant/Non-Grant (GL: Non-Grant/GM: Grant)
Oracle Alias (GL: Org/GM: PTA)
Location (not currently used)
Foreign Activity (if applicable enter Region)
Category/Source (GL&GM Purchase Invoices)
Amount (GL&GM Amount)
Currency (will default to US Dollar)
JE Line Description (GL: AP/Procurement Detail & JE Description/GM: Transaction Detail).
Select Save.
ImageSelect DCF TO.
Image
Complete in the TO section:
Account (GL: Account/GM: Resource Detail Number)
BPR Date (GL: Effective Date/GM: PA Date) same as FROM
Grant/Non-Grant (GL: Non-Grant/GM: Grant)
Oracle Alias (GL: Org/GM: PTA)
Location (not currently used)
Foreign Activity (if applicable enter Region)
Category/Source (GL&GM Purchase Invoices)
Amount (GL&GM Amount)
Currency (will default to US Dollar)
JE Line Description (GL: AP/Procurement Detail & JE Description/GM: Transaction Detail).
Select Save.
Image
Once the FROM and TO sections are complete your ticket will look like this:
- Next you will add the attachments. You will be required to add the below:
- 1. Non-Labor Cost Transfer Justification form
- 2. BPR Backup documentation
- 3. Invoice/Receipts
You will select Attachments, Attach Documents and then in the pop up window you will Upload and Attach these documents.
- Finally, you will need to add your department approver.
In the pop up window under DCF Approver you can select your approver.
If you need to add an additional Approver you will select Add Step under DCF Approver and then select (you will notice that GCAS and AP are auto filled in).
You can then select Save.
- Double check your expected expenses and make sure your attachments are in place then select submit Request.
Approvals
There are two ways to review the approvals that come through to you for requests.
- On your iBuy home page you will see an Approval section under tasks
- You can access Approvals directly by going to Approvals in the dropdown menu.
Your approvals will be under requests. Select the approval, review, and approve.
Helpful Tips
- DCFs can only be submitted for grants-related transactions processed by University Payables. On the BPR, Payables activity is identified in the Category/Source as 'Purchase Invoices'.
- The DCF with a legible copy of the BPR must be submitted to University Payables.
- It is the responsibility of the individual that is creating the DCF to ensure the following:
- All data elements in Concur and on the CTJF are entered.
- The combination of the organization to be charged or relieved, the expense account code, the award number, the expense effective date and the current GL/GM date must all be accurate. If not, the DCF will be returned to the DCF originator for corrective action. University Payables will not hold the DCF in a pending status awaiting responses for requisite corrective action to be taken.
- All CTJFs must be approved with a legible signature of the approver with his/her printed name underneath the signature. To minimize the risk of an issue with the signature, Payables recommends using a digital signature.
- No one individual can act in both the role of the preparer and the approver for a CTJF submission.
- No one individual can approve a DCF to adjust activity for his/her own iBuy+ expense report.
- Only one DCF may be submitted per each submission unless the DCFs are adjusting the identical invoice transaction.
- DCF/CTJFs may not be submitted in the Adobe portfolio format.
- DCF/CTJF adjustments will not be processed for transactions that cross the university's fiscal year.
Please note: Adjustments submitted more than 60 days after the original posting date must include Section III with the appropriate signatures. The Section III must detail why a more timely submission did not occur and what actions are being taken to avoid these instances in the future.
To avoid a delay in processing a DCF/CTJF or minimize the risk of a DCF/CTJF being rejected, you are encouraged to read and become familiar with the Financial Transactions Adjustment Policy.
All requirements must be met before University Payables can process the request.