Can I Charge That?
Below is Stanford's guidance for the most common uncommon expenses individuals ask if are allowable on sponsored projects and how to properly code them.
Whenever making a cost determination, whether at the time of proposal budget development or post award charging, apply the Cost Principles : allowability, allocablilty, reasonableness, and consistency in addition to Order of Precedence.
Participant Support Costs (PSC)
Faculty bonuses are NOT allowable on sponsored projects.
- Faculty bonuses must be paid from non-sponsored funds.
- Faculty bonus ETs 51905 and 51915 are blocked from being charged on all sponsored PTAs.
Staff bonuses may be allowable on sponsored projects.
- Generally, bonuses coded as follows would be allowable for staff on federal and non-federal awards, provided they are not prohibited by the specific sponsor and award (see below table)
- Performance bonuses should be allocated to the project(s) that benefitted from the extraordinary performance.
|Earn Code||Earn Code Description||Prescribed Usage||Allowable on Sponsored Projects?|
|BON||Bonus||Performance bonus award per Staff Pay Program Guide||Yes, allocate to the award(s) that directly benefitted|
|SPT||Bonus - Spot||Spot bonus per the Staff Pay Program Guide||Yes, allocate to the award(s) that directly benefitted|
|SIG||Bonus - Sign-on||Sign-on bonus per the Staff Pay Program Guide||Yes, allocate over all pay sources that will benefit from the staff's work|
|RTN||Bonus - Retention||Retention bonus per the Staff Pay Program Guide||Yes, allocate over all pay sources that will benefit from the staff's work|
|INC||Bonus - Incentive||No|
Post doc bonuses may be allowable on sponsored projects.
- If the postdoc has been consistently paid salary for work on a sponsored project, then a bonus can be allocated to the award that directly benefited from the postdoc's work.
- If the postdoc is receiving stipend, a bonus may not be charged to sponsored projects, including fellowships.
View the Bonus & Incentive Guidelines matrix (secure login required).
Participant Support Costs (PSC)
Per Uniform Guidance (UG), Participant Support Costs (PSC) are "direct costs for items such as stipends or subsistence allowances, travel allowances, and registration fees paid to or on behalf of participants or trainees (but not employees) in connection with conferences, or training projects". In some instances Stanford students and post docs may be participants. However, a Stanford student or post doc cannot be compensated as both an employee and as a participant on the same project.
Historically, the National Science Foundation (NSF) has been the primary federal sponsor that awards funds for PSC. However, we’re seeing more examples of PSC being proposed and awarded by other federal Sponsors such as the NIH, NASA, and ONR.
Federal proposals that seek to request funds for PSC should clearly state so and only request funds for participants as allowed by the given sponsor and program. The inclusion of PSC activities in proposals should be spoken to in the Statement of Work, listed as line item(s) in the budget, and described in detail in the budget justification that is submitted to the sponsor.
PSC must be explicitly awarded by a federal sponsor in order for the receiving PI/Dept to be able to code PSC qualifying costs as PSC in Stanford’s financial systems.
Key items of which to be mindful when budgeting and charging PSC:
Who qualifies as a participant?
- A participant is defined as a non-employee who is the recipient, not the provider, of a service or training associated with a workshop, conference, seminar, symposium, or other short-term instructional or information sharing activity. Participants are not interns with paid appointments. Participants should NOT be performing/providing similar services as other Stanford students (graduate or undergraduate) or Post Docs who are paid as employees, or anyone who has a deliverable or is primarily providing a service to the project. See Stanford's Administrative Guide sections 10.1.1 Undergraduate Student Employment and 10.2 Graduate Student Employment.
- Speakers and Trainers are generally not considered participants and should not be included in this section of the budget. However, if the primary purpose of the individual’s attendance at the conference is learning and receiving training as a participant e.g. a train the trainer type conference, then the costs may be included under participant support.
PSC Budgeting Considerations
- PSC is excluded from a project’s Modified Total Direct Cost (MTDC) base and will not accrue any F&A/IDC as per Uniform Guidance and Stanford’s most recent indirect cost rate agreement.
- Qualifying participant costs e.g., stipends or subsistence allowances, travel allowances, and registration fees should be budgeted under "Section E. Participant/Trainee Support Costs" of federal budgets. Participants costs should NOT be listed in the project budget under a personnel category. PSC funds awarded for participants do not have fringe benefits and F&A costs associated.
- It is unallowable for budgeted project personnel functioning as non-participants on a project to be re-categorized as participants to “save” on fringe and F&A costs.
- Costs related to a conference (e.g., venue rental fees, catering costs, supplies, etc.) that will be secured through a service agreement/contract are NOT PSC. These costs should be budgeted as "Other Direct Costs" to ensure appropriate allocation of indirect costs.
- Participant Support Costs are NOT incentive payments to research subjects. Human subject incentive payments should be included in federal budgets under “Other Direct Costs” to ensure appropriate allocation of indirect costs.
- PSC should NOT be used on a non-federal sponsored research project, unless required by the sponsor (very rare).
Participant Stipend Management
- A participant’s stipend should be a set amount of money to be paid directly to the participant. Conditions for receiving a stipend should be in writing and provided to participants prior to their participating in the program. Program completion should be attested to by the project PI. Granting agencies may have specific guidelines for participant stipends. Stipend payments should not be paid based upon the number of hours devoted to the project i.e., PSC payments are NOT salaries where individuals only receive payment for work performed.
- Participants are NOT required to provide any deliverable, other than meeting the program requirements (e.g., attendance, testing, etc.).
PTA Setup and Coding of PSC
- For ALL new PTA setups, the PSC ET, 52436, is by default blocked unless the sponsor has explicitly awarded funds in the PSC budget category. If PSC is an approved budget category on a project, the OSR Post Award Accountant will unblock the PSC ET during their portion of the account setup process. PSC must be budgeted into its own specific Task. PSC qualifying and coded expenses can only be charged to PSC Task of a project.
- If you have an existing project with sponsor approved PSC funds, but the PSC ET remains blocked on your project’s PTA, you can from within the given project record in SeRA submit a Central Office Request - Update Expenditure Type to request that your OSR Post Award Accountant unblock the PSC ET. If a separate PSC task has not already been created, one will be created.
- For projects with sponsor approved PSC budgets, use ET 52436 Participant Support Costs Uniform Guidance for PSC qualifying expenses.
- Note, there are a small number of older pre-Uniform Guidance awards (~12) still able to use the old Participant Support Costs NSF Only ET 52435.
- Stanford's Graduate Financial Services (GFS) system does not accept the PSC ET 52436. Thus, for projects that include PSC and where the participants will be Stanford graduate student and/or post docs, the receiving department as part of PTA setup for a project should indicate this in the comments of the New PTA setup transaction so that their OSR Post Award accountant can unblock the more general stipend ET that GFS will accept to allow the payment of PSC stipends to Stanford grad students and post docs who will be participants through GFS. If a department does NOT indicate that sponsor approved PSC stipend payments will be issued to Stanford grad students and/or post docs at the time of New PTA setup, they can after the initial PTA setup is complete, from within the given project record in SeRA, submit a Central Office Request - Update Expenditure Type to request that their OSR Post Award Accountant unblock the general stipend ET on the PSC task of the project.
When to Seek Prior Approval for PSC Rebudgeting
- For projects with sponsor approved PSC budget allocations, sponsor prior approval is required to rebudget any project funds out of the PSC budget category to another category. Sponsor prior approval is NOT required to rebudget project funds into the existing PSC budget category from another category, assuming there will be no change in the project's scope of work.
- If an award has not been approved by a sponsor for PSC, a PI/Depts should not be charging the PSC ET, and in most cases won’t be able to as a result of Stanford PTA setup limits. If an existing project without a sponsor approved PSC allocation would like to incur PSC qualifying costs and code them as PSC, sponsor prior approval for the addition of the PSC activity may be required. The determination of whether sponsor prior approval is required will be largely determined by if this change is representive of a change in the project’s scope of work and/or if there is a sponsor and/or award level restriction for incurring PSC.
Sponsor prior approval required Yes/No?
PSC is awarded
Rebudget into [to increase] the PSC Budget category and there is no change in the project's scope.
PSC is awarded
Rebudget out of the PSC Budget category
PSC is not awarded
Rebudget into the PSC Budget category
It depends...if there is also a change in scope and/or an agency or award level restriction, yes, prior approval is needed.
Not finding for what you're looking? Have other "Can I Charge That?" questions? Contact the Client Advocacy & Education Team. We’re here to help!