EDIT – 5/16/26: Update: Oracle Cloud 26B – Project Resource Management Changes

Prior to the Oracle Cloud 26B release, we communicated updates related to Project Resource Management (specifically, the process for assigning project roles) below.

However, after 26b went live, the team noted differences between the test and live environments during the final review; consequently, they have not implemented the planned changes at this time.

This means that the existing method for assigning project roles will continue for the foreseeable future.

Manage Financial Project Settings -> Parties -> Team Members

We will notify you ahead of future Oracle updates should this change. Our apologies for the confusion and our appreciation for your understanding. Please feel free to reach out with any questions.


As part of the Oracle Cloud 26B release, Project Administrators will see an update to how project team members and resources are managed. 

What’s Changing

Project Administrators will transition from using the Team Members section on the Manage Financial Project Settings page to a new, enhanced page called Manage Project Resources.

Manage Financial Project Settings
Manage Project Resources

The Manage Project Resources page provides improved visibility and flexibility when managing project resources. 

Key Enhancements

  • You can view project resources using a tile view or an indexed list view, with enhanced filtering and navigation options.
  • You can add project resources: 
    • With future start dates
    • Who were terminated in the past
  • You can now add HCM persons as project resources even if they have missing or duplicate email addresses. 

You can access the new page using the following navigation path:
Projects → Manage Project Resources

Before 26B:

  • Project team members were maintained using the Team Members page in the Project Financial Management work area.
  • A single active Project Manager was displayed (for example, Mona Mantry).
Before 26b

After 26B:

  • Project resources are now managed through the Manage Project Resources page.
  • The previously active Project Manager (for example, Mona Mantry) is now identified as the Primary Project Manager.
  • Existing confirmed resources (such as Anna Julia) are retained with their original From and To dates.

After 26b

Upcoming Enhancements to the iO Journal Process

Please see this important announcement on the Controller’s Office blog regarding upcoming enhancements to the iO Journal Process (the product of an effort led by the Controller’s Office and Finance Systems and Accounting, and in partnership with the Budget Office and Technology Solutions & Services (formerly OIT)).

The enhancements will deliver meaningful improvements to how journals, balance transfers, and budget adjustments are entered, reviewed, approved, and reported.

The redesign includes a structured rollout with testing, training, and support, and is scheduled to go live in May 2026.

Before you Order International Equipment – Please Read

A Reminder on Pre‑Purchase Requirements
(from Strategic Sourcing & Procurement (SS&P)

Across campus, we continue to see an increasing number of avoidable import duty charges, some exceeding tens of thousands of dollars, simply because Strategic Sourcing and Procurement (SS&P) were not engaged early enough in the purchasing process. These costs directly impact the research budgets and, in many cases, could have been fully prevented.

To support our research community and ensure compliance, it is essential that all import‑related purchases involve SS&P at the time of purchase consideration, not after the fact. Engaging the team early enables proper review of the quote, warranty, incoterms, duty exposure, U.S. market availability, and eligibility for federal duty exemptions.

Why Early Engagement Matters

Strategic Sourcing & Procurement’s pre‑purchase review ensures that:

✓ All Incoterms and shipping terms are clarified up front
✓ Correct HTS codes are assigned on quotes and shipping documents
✓ Duty and tariff assessments are completed before any PO is issued
✓ The ITA 338 duty exemption application is submitted on time
✓ Import routing and documentation meet all compliance standards
✓ Departments avoid unnecessary or non‑recoverable costs

What You Should Do

If you are considering purchasing equipment, instrumentation, or materials from an international supplier, or from a U.S. distributor that may be drop‑shipping internationally, please reach out to SS&P when the purchase is being considered, before the quote is finalized or requisition filled out. The SS&P team can complete the vetting process and guide the next steps.

By engaging early, SS&P can help you:

✓ Protect your research budgets
✓ Facilitate duty‑free importing when eligible
✓ Ensure compliance and proper documentation is submitted to U.S. Customs
✓ Coordination with the brokers to ensure a smooth import process is facilitated

SS&Ps goal is to make the process smooth, compliant, and cost‑effective for the entire research community. Thank you for helping us ensure that these important steps are followed.

For questions or assistance, please contact:

Susan Correa, Strategic Sourcing Specialist Operations, Finance & Support – Strategic Sourcing & Procurement Office: 713‑348‑4737 | Email: sc318@rice.edu

Enhancement to Template Lookup Data: Daily Automated Updates

Since the launch of the PPM and COA single-form NLCT templates in May 2025, we have greatly appreciated your ongoing feedback. One of the most frequent requests we’ve heard from staff is the need for quicker, more frequent updates to the template lookup data. Until now, updating this reference data to the tool has been a manual process completed every few weeks.

We heard your feedback, and we are pleased to announce a significant improvement to this process.

As of today, the lookup data update is supported by a new Power Automate workflow. This automation ensures that the template reference data for both the COA and PPM templates is now updated daily.

What to Expect When Opening the Template

From the submitter’s point of view, the template will functionally work in exactly the same way as before. However, because the template is now dynamically pulling fresh data every day, you will notice a minor change to the experience when you first open the file.

Here is what you will see:

A Security Warning: When you access the template, a yellow banner will appear at the top of your screen stating: “SECURITY WARNING: This workbook includes external data connections…”

Please don’t worry! The ‘external’ data connection is simply linking to a Rice SharePoint folder. It is only “external” to this specific spreadsheet, but it remains entirely within Rice’s secure environment.

1. Click ‘Edit Anyway’: If your Excel opens in Protected View, click the button to allow editing.

2. Click ‘Enable Content’: Click this button on the security warning banner to allow the spreadsheet to communicate with SharePoint.

Image

3. Data Refresh: After enabling content, you will see a green ‘refreshing data’ loading bar at the bottom right of your screen.

Image

Once this green loading bar has disappeared, you can continue your work as normal.

You should see no differences in how the tool operates, other than the great benefit that newly set up projects will now be included in your lookup data much faster. (Almost always, newly set up projects will be there right away; if not, simply check back the next day).

Resources (SSO login)

Submission Guide for Non Labor Cost Transfers 

PPM NCLT Template.

COA NLCT Template.

FedEx charges and Service Center Billing Templates

There are some updates to the following cost processing templates that can be found in the following box folder.

FedEx Charges

RCA are releasing an updated template for FedEx charges. Specifically, it allocates FedEx costs that have been posted to a COA string (General Ledger) but need to be charged to a project (Subledger PPM). This allocation to a project is considered the primary project allocation and this process is therefore not a cost transfer process.

It should only be prepared and submitted by departments at Rice that hold an account with FedEx and to whose General Ledger, FedEx charges correspondingly post.

After this template has been used to charge the cost to a project, any further reallocations of it would be considered cost transfers, and must instead follow the NLCT process (justification for transfer, submission of NLCT via iO ticket etc.)

Service Center Billing

RCA have also updated the Service Center Billing template for generating cost and revenue transactions. By being the mechanism by which a cost is generated to post on a project, the template (and supporting ADFdi process) also meets the criteria of being the primary project allocation of a new cost and is not a cost transfer process.

It should only be prepared and submitted by service provider administrators who need to record revenue to a COA string while posting costs to a project. Note that this template will mostly be used by Service Center Administrators but it is also the default template for non service center departmental administrators to use when recording occasional revenue. See policy 836 for further details on what the minimum criteria are for a service center and note that if those criteria are met, you must approach RCA to discuss the creation of one.

As with FedEx charges, the same understanding also applies that after a new project (PPM) cost transactions have been generated using this process, any further reallocations of those PPM costs would be considered cost transfers and must be processed correspondingly.

Download the forms to populate them. Don’t try to edit them online from within the box folder. Each form contains step-by-step instructions on the third tab of the workbook.
Please complete either of these forms through the end of step one (i.e. populating the accounting tab).  The remaining processing steps for these forms (two through four on each template) will be processed by RCA. Please place the populated forms in this drop off folder.

Known Issue Impacting NLCTs. Microsoft SharePoint. ‘create a copy online’.

Several staff have reported to RCA that they are unable to ‘create a copy online’ of the NLCT templates within SharePoint/OneDrive.

This is not local to Rice and is a known issue for Microsoft, which is investigating the problem

https://learn.microsoft.com/en-us/answers/questions/5665155/unable-to-save-a-copy-any-more

As a workaround while waiting for a fix, try downloading a copy of the file from the web application and either working with the copy on your local machine or manually uploading the downloaded copy back to OneDrive to work with it there.

Introducing: AI support for Non-Labor Cost Transfer Compliance

Embracing Innovation: AI-Powered Support at Rice

Rice University is leaning into the future of research administration. Staff at Rice have been issued licensed access to advanced AI tools.


“…We’re excited to see how these tools will support the collective work of the campus community and how they might inspire new ways to collaborate and innovate,” said Kelly Fox, executive vice president for operations, finance and support. “This initiative reflects Rice’s commitment to integrating cutting-edge technology to empower our campus with advanced AI capabilities across teaching, research and administrative work.


Research and Cost Accounting (RCA) has been highly engaged in exploring ways to leverage these exciting new tools to streamline operations and ensure compliance, while also strictly adhering to Rice’s guidelines for responsible use, data privacy, and attribution.

Navigating the rules for Cost Transfers – especially involving federal funds – can be complex. One of the most important parts of ensuring that the justification text within cost transfers is compliant.

Crafting Stronger Justifications

Transactions involving federal funds are subject to strict scrutiny. This AI tool empowers you to evaluate and articulate the pillars of a strong justification – essential for RCA approval:

  1. Root Cause: Accurately identifying why the error occurred.

  2. Prevention: Articulating the corrective actions to stop recurrence.

  3. Allocability: Proving the expense directly benefits the destination project.

  4. Untimeliness: If a cost transfer is untimely, identify the extenuating circumstances and the changes you will make to internal controls.

What AI support is not?

This RCA support tool is not a final authority, nor is it a pre-approval of a cost transfer by RCA. It is designed to assist staff at Rice by assessing the narrative completeness of the justification.

How to Access?

These tools are integrated directly into your existing tools.

  • Via Templates: You will find a direct access link on the current versions of the Non-Labor Cost Transfer template cover page. There are two links to two different tools. One that can be used to review the completeness of the main justification, and one that can be used to review the completeness of supplementary justifications that are necessary when cost transfers are untimely.

  • Guidance on how to use the tools can be found here.

Secure and Private

We take security seriously. While the guidance documentation is open to all, access to this tool is strictly controlled via your Rice NetID. You can only access these tools if you are logged in to your browser with your Rice NetID.

  • Your Data is Yours: Each user has a persistent, private chat history. Your queries and findings are visible only to you; there is no “cross-pollination” of data between users of these tools.

Residual Balance Roadmap: Choosing Your Fixed Cost Project Transfer Pathway (Updated 1/27/26)

When a fixed price sponsored project wraps up with a residual balance, the transfer process is changing. Previously, we relied on a general, COA-level balance transfer, which lacked the PPM specificity needed for clear management and accounting control. With technical support from FIS, RCA has improved this process.

As of November 2025, when a fixed price sponsored project concludes with a residual balance that residual will be addressed through the generation of a non-billable cost that will post both to the sponsored project (debit) and to the destination location that the residual balance is being transferred to (credit).

What this means for the PI/Project Manager?

When interacting with RCA Grant Specialists during the closeout phase of such a fixed price award, the destination for the residual balance needs to be stated in either of the following ways to RCA.

  • Destination: Faculty Fund (PPM Project)

    • Required Data: The Faculty Fund Project Number and the Task Number.
    • Conditions:
      • Department must ensure the Faculty Fund destination (task line) is both (a) active AND (b) has an appropriate classification code that corresponds with the original award type. For example, if the original award type was research, then the classification segment should be set to 303.
      • Ensuring that the faculty fund line has this characteristic is an important requirement to support university-level reporting (HERD).

OR

  • Destination: General Ledger (COA String)

    • Required Data: The full COA string.
    • Condition: The Account segment (the fifth segment) must be 6800.

If the destination for the residual is a Faculty Fund, a negative expense (credit) will be posted there (Expenditure Type: TXF: Transfers – Inter / Intra Departmental)

If the destination for the residual is a COA, a negative expense (credit) will post to account code 6800. 

In either destination case, the negative expense will increase the balance there correspondingly. For clarity, the impact to the faculty fund is that cumulative costs (actuals) will be less, and the balance will thus be more.

There is no need for the administrator to increase the budget; the above achieves the same effect upon the Faculty Fund balance as a budget increase would. 

Customization Option for Budget to Actuals Detail SPFF (for viewing Faculty Funds)

OTBI dashboards (ROBI) developed in 2021 had the capacity to review Faculty Fund balances by task line. For those users who continue to use ROBI because of this view, and worry that this view will be lost to them when the tool is ultimately decommissioned, we have good news.

Faculty Fund balances by task line can be replicated exactly in iO using the SPFF Budget to Actuals Dashboard.

Image
To replicate the view, search for the faculty fund by project number.
Once the results of the analysis load, simply right click on the ‘Expenditure Category’ column and click ‘exclude’.
Image

Non Labor Cost Transfers. The Basics, an Update, and a Reminder

Processing NLCTs (The Basics)

When processing Non Labor Cost Transfers, the template you use to submit the transfer depends on the origin data.

When the origin data is a cost on a project, use the PPM template.

When the origin data is a cost that is not on a project, use the COA template.

Both templates have a similar appearance, and they operate very similarly, but their internal workings are different and are thus not interchangeable. For full step-by-step guidance use this guide.

COA Template. Version 1.12. (An Update)

Several submitters noticed a bug within earlier versions where uploaded lines to the ‘TNC2 data’ tab were not appearing in the ‘TNC2’ tab upon refresh. The cause of this rare issue has been identified and the template has now been fixed in version 1.12.

Cost Transfer Compliance (A Reminder)

Approvals for NLCTs MUST ALWAYS be added to iO tickets prior to submission (unless the submitter is also both the origin and destination approver in which case no approval is needed). The approvals should take the form of the adobe sign PDF, signed by both origin and destination approvers, as indicated in the instructions within in the templates.

As detailed in box 2 of the cover page of each of the templates, and in Rice policy 302, there are some clear compliance expectations that MUST ALWAYS be met by cost transfer submitters when justifying a cost transfer in box 3 of the cover page.

PPM Template (excerpts from cover page):

1) How were the original costs miscategorized, charged to the wrong project(s), or allocated to the wrong task(s)?

2) If type is PPM-PPM, are the costs allowable and allocable to the receiving project(s)? (i.e does each line of the transfer meet cost principles, funder rules, and is within bounds of funder approved budget categories)?

3) What steps will be taken to prevent recurrence?

COA Template (excerpts from cover page):

1) Why were the original costs mischarged?

2) Are the costs allowable and allocable to the receiving project(s) and/or COA string locations? Does each line of the transfer that has a PPM destination meet corresponding cost principles, funder rules, and remain within bounds of funder approved budget categories)?

3) What steps will be taken to prevent recurrence?

Policy 302 (excerpts from policy page)

“Unallowable or inappropriate charges that appear on a sponsored project fund must be moved promptly to an appropriate fund. Cost transfers must be timely, well-documented and properly approved.”

“Charges to a sponsored project fund should be reviewed periodically by the PI and reconciled regularly by staff within each department or school so that erroneous charges may be identified and corrected promptly. Timely means that a transfer should be initiated as soon as an error is detected but normally within 90 days following the last day of the month in which the charge first appears on the fund.”

Why the COA String Entered Isn’t Always the One That Gets Used?

Purchase Order Perspectives

As a submitter of a purchase request, you may have found yourself entering two different pieces of accounting information. You diligently entered the Account Number (COA) you thought was correct—say, one for General Operations (Fund Type 101). But because the expense was project-related (a faculty fund), you also linked it to a specific Project. You may have wondered, “Which one does the system actually use?” The good news is, by including the Project information, you’ve done everything correctly, even if the COA you entered was technically wrong.

As an approver viewing the transaction in the Purchasing and Payments dashboard, you may notice this confusing dual entry. Perhaps you see both the COA string (Fund Type 101) and the Project information (Faculty Fund – which you know to actually be Fund Type 109) listed…an apparent contradiction. This can lead to the question: Did the system make a mistake? Is there a glitch that will mess up the final reports? Absolutely not! This is a common situation, but it’s actually a sign that your finance system is working exactly as it should, following a strict set of data hierarchy rules.

Data Hierarchy

1. The Requisition

When you create a requisition, think of it as if you are making a request to where the ‘address’ for the cost will be sent to?

  • You can enter two kinds of addresses: You might put in both the COA string (ZIP code) and the Project (street address) information.
  • The Dashboard View: When you look at the transaction in the Purchasing and Payments dashboard, you are simply seeing your original input. The system is just showing you what the requester submitted, even if they put in two conflicting addresses.
  • The Golden Rule: At this stage, the system doesn’t try to correct you. It just accepts the dual input and focuses on getting the purchase approved.

2. The Data Hierarchy

Once the purchase is approved and the bill is ready to be paid, the system has to decide which “address” to use for the final accounting record. This is where the hierarchy kicks in.

In iO, the Project information always wins. Why? Because Project accounting is the most specific (street address is more specific than ZIP code) and has the strictest rules.

Your Input iO’s Decision Why?
Project Information is Present IGNORE the Account String (COA) for final accounting. The specific Project Rules are more important than the general COA string rules. The cost must follow the Project.
Project Information is Missing USE the Account String (COA). There are no special rules, so it defaults to the general address.

The Core Principle: If you link a cost to a Project, that Project acts like a powerful magnet that pulls the cost into its specific set of accounts, completely ignoring the weaker COA string you originally typed.

Finding the Truth: Where the Money Really Goes

The whole purpose of this system is financial integrity. We don’t want someone accidentally charging a restricted grant expense to the general operating fund just because they typed the wrong account number on a request form.

The system uses a set of automatic rules, called Sub-Ledger Accounting (SLA), to determine the correct and final account number based on the Project’s setup.

Your Source of Truth

To stop guessing and see the final, audited truth, do not rely on the COA you see in the Purchasing and Payments dashboard. That dashboard only shows the initial input.

Instead, go directly to the Project Costs Module (which is part of the Project/Grant system).

  1. Find your transaction within the Project Costs Module.
  2. Look for an option called “View Accounting.”

When you click this, you will see the final, derived account number. This is the real account (Fund 109 in our example) that received the charge—proof that the system correctly followed the specific Project rules and ignored the conflicting number you saw on the requisition dashboard.

Net Zero Costs in PPM. What They Are & Why They Matter?

Cost Transfers 101 and Net Zero Costs. Summary

  • A cost transfer is the process of moving a transaction (the financial record) from one funding source (e.g., a specific grant (PPM) or departmental account (COA) to another after the initial transaction has been recorded.
  • When you initiate a cost transfer, you are creating an offset transaction in the original location (zeroing out the expense) and generating a corresponding, consistent transaction in the destination location, effectively relocating the expense’s financial record.
  • Before transferring a cost check to see if there’s an equivalent opposite polarity cost (either negative or positive) that has the same Expenditure Type and Item Date. If such a cost exists, it might be a Net Zero transaction and thus not transferrable. See the ‘Identification of Net Zero Costs’ below on how to confirm for sure if it is or is not?

Maintaining Financial Compliance

Administrative staff engaged in project financial management occasionally need to adjust and transfer project costs. However, a specific transaction type—the Net Zero Cost—is systematically restricted from further transfers or manipulation.

This restriction is not a system error; it is a critical automated safeguard. The principle of the Net Zero Cost ensures that the Project Portfolio Management (PPM) subledger maintains absolute synchronization and balance with the General Ledger (GL). Identifying the Net Zero Item flag is essential for administrative efficiency, as attempting to adjust these items will result in immediate system rejection, confirming that the transaction’s accounting role has already been fulfilled as a cancellation record

The Three Part Transaction Model

A Net Zero Cost transaction is a specialized, negative accounting entry generated automatically by the system to execute the formal reversal of a prior expenditure item. Its function is cancellation; it does not represent an actual, allocable expense.

Cost corrections in PPM always utilize a three-part transaction model :

  • Original Cost: The initial expense containing the incorrect allocation.

Image

  • Reversal Cost (The Net Zero Item): The negative entry that mathematically and functionally cancels the Original Cost.
  • New Cost: The corrected charge applied to the appropriate project elements.

Image

The Net Zero Item attribute is the field that explicitly identifies the Reversal Cost as True. This confirms that the transaction is the necessary offset, designed to create a zero balance for the pair.

Net Zero Costs cannot be transferred because they are defined as reversed expenditure items and are explicitly disallowed from further adjustment.

Protecting the Audit Trail

The Net Zero transaction’s sole purpose is cancellation. If a transfer were permitted on the Net Zero transaction, the original charge would become effectively uncanceled at its source. The transfer is rejected to maintain the integrity of the audit sequence, as the Net Zero entry is the immutable record linking the cancellation back to the original source charge. Disruption of this linkage results in the system issuing a mandatory rejection message stating that adjustments are not allowed on a reversed expenditure item.

Identification of Net Zero Costs

Right now, there’s only one place in iO where you can confirm the status of a transaction relative to it being part of a net zero pair.

Go to Grants Management/Awards

Image

Click on the Page icon on the right of the page

Image

Search for the award that contains the project that contains the cost. Click on the drop down next to the project that contains the cost. Select Manage Project Costs

Image

If this is the first time that you’ve ever looked at this Project Costs view, you may need to ensure that the net zero column is selected.

Image

When examining the row with the cost that you are considering transferring, you can see the net zero column that indicates if it is or isn’t a net zero transaction.

When you see an x, it is not a net zero transaction and is transferrable. If you see a tick mark, it is a net zero transaction and it is not transferrable.

Tired of Guessing Who Has Access? We Are Too! Introducing Org-Level Award Personnel Spring Cleaning.

The Research and Cost Accounting (RCA) office is happy to announce an upcoming upgrade to how we manage personnel roles in sponsored awards within iO. If you’ve ever wondered why someone who left three years ago still appears to have access to your grant data, you’ll be happy to hear that we’re giving everyone a structured way to clean up!

The Old Way

When an award is first set up, we determine the key roles: the PI, Co-PI(s), Project Manager, and Award Participant(s) are all correctly added to the iO award. 

But then things change. People move, responsibilities shift, and suddenly, you need to add someone or, more importantly, remove someone. Currently, these adjustments are handled one by one via individual iO tickets (Category = Access Permissions).

This process made good award hygiene an absolute chore:

  • It’s inconvenient to audit every single award regularly to see who should stay and who should go.
  • Department managers responsible for oversight haven’t had an easy way to get a big-picture view of all personnel on all their awards simultaneously.

The result? We’ve sometimes been operating with a slight (or not-so-slight) disconnect between the data in iO and reality, leaving us asking, “Who exactly is supposed to be seeing this data?”

The New Way

To finally make data management manageable, RCA is implementing a new process that takes advantage of a superb FIS-developed tool that enables organizational-level batch adjustments for award personnel. Consider it your mandatory, but very helpful, data “spring cleaning” session.

How Will This Work?

  1. Bi-Annual Data Drop: Twice a year, the Cost Center Manager for your department will receive a comprehensive data table from RCA. This table lists every award owned by your Organization (Cost Center).
  2. Full Personnel Disclosure: For each award, the table will clearly list every person currently assigned an award role. You’ll have the option right there to change the status of existing people (i.e., remove them) or add new personnel.
  3. The One-Month Window: Your department will have one month to coordinate a full review, make the necessary amendments, and return the updated table to RCA.
  4. The Great Cleanup: RCA will process these Org-level batch updates, ensuring your awards are instantly populated with the correct, current personnel.

The Best Part: Pristine Data and Focused Effort

  • Pristine Data: You get rid of all the ghost users and make sure everyone who should have access actually does. Your data will reflect the people currently managing the work.
  • Focused Effort: By scheduling this process twice a year, we create a dedicated, focused time slot for data hygiene. While you will still be able to use the old iO ticket method for urgent, one-off changes, this mandatory schedule will keep your award personnel data accurate and compliant.

What’s Next?!

This new process is scheduled to be rolled out during Calendar Year 2025, with a likely implementation in early November. We’ll share more detailed instructions and dates as we get closer.

If you have any questions, concerns, or suggestions about this upcoming process, please let us know! Email RCA directly at jth6@rice.edu.

Enhancement to Project Cost and Revenue Accounting at Rice (for Service Centers and Auxiliaries)

RCA are rolling out important, mandatory updates to how service centers and auxiliary units charge costs to sponsored projects and faculty funds, and how the corresponding revenue is recorded. These changes are the result of work by the Service Center Task Force and are designed to prevent transaction errors, eliminate duplicate entries, and significantly simplify your monthly and period-end reconciliation processes.

Please read this communication carefully, as these new protocols are effective immediately.

1. The Core Change: Two Distinct Accounting Paths

The biggest change involves separating transactions into two distinct methods based on where the cost is being charged (the destination).

Scenario A: Cost to a COA (General Ledger) String

  • Destination: General Ledger (Chart of Accounts – COA)
  • Method: FBDI (File-Based Data Import)
  • Rule: The FBDI template must only be used for COA-COA transactions. This includes both cost transfers and the traditional cost/revenue accounting where the cost and the corresponding revenue are recorded as two separate lines within the COA.

Scenario B: Cost to a Project/Task (Sponsored Project or Faculty Fund)

  • Destination: Project Portfolio Management (PPM – Project/Task)
  • Method: New ADFdi (Application Desktop Integrator) Tool
  • Rule: This is the new, all-in-one method. Using the dedicated ADFdi tool will now automatically:
    1. Generate the cost to the specified Project/Task.
    2. Simultaneously and automatically record the corresponding revenue to your service center or auxiliary unit.
  • Crucial Note: FBDI templates can no longer be used to create GL costs or revenue relative to any PPM/Project transactions created (using 1087 account code). Any FBDI submission that attempts to record revenue or a cost transfer to a Project/Task (1087 account code) will be rejected by General Accounting.

The ADFdi method ensures that the cost and its corresponding revenue are successfully linked and posted together, which is the key to accurate and easy reconciliation.

2. Introducing the Pre-Submission Validation Tool

To ensure a smooth transition to the new ADFdi process (Scenario B), we’ve incorporated a powerful pre-submission validation tool directly into the template. Before you attempt to post a transaction, the tool will perform critical checks, including:

  • Period of Performance: Verifies the transaction date is within the eligible project period.
  • Task Number Viability: Confirms the Task number is valid for the selected Project or Faculty Fund.
  • Project Status: Checks that the Project is Active and not Closed.

This validation will save your teams significant time by catching common errors before a failed posting attempt, allowing you to quickly communicate accurate information to your customers.

3. Training and Next Steps

We understand these are significant procedural changes.

An introductory training session will take place via zoom on October 15th at 11am.

[EDIT – see video recording of this session]

This change is going to primarily impact Service Centers (SEA, Chem Stockroom etc.) and Auxiliaries (Housing & Dining, Post Office etc.) but attendance is not limited. All are welcome.

Link for 27th at 11.30

Following this zoom training, there will also be an in person training session in Moody 205 (11.30-13.00) where we will do a walk through of the new ADFdi template, submission process, and validation tool. Details on this training will be added to this post, and communicated via the research-l listserve as soon as they are known.

If you have an urgent need to use the new ADFdi template to generate a cost/revenue transaction in the next two weeks, please reach out to James Hayward (jth6) in the Controller’s Office for assistance. Otherwise, please save your questions for the scheduled training session.

Thank you for your cooperation as we implement these necessary controls for more accurate and efficient accounting at Rice.

NLCT Template 1.09 Update Notes

The NLCT template has updated from 1.08 to 1.09.

Here’s what changed and why.

Image

A Note on Training

Some people have reached out to to RCA ask if they can get 1-1 training, or if there will be office hours for NLCT?

Most of these queries could have been addressed by applying the instructions, or watching the videos.

The ideal scenario is that should there be user need, then a combination of these resources along with colleagues training other colleagues would be the first choice.

This is not always possible of course and please do reach out in either the event that this first choice is not an option, or in the event of encountering any technical issue.

Upcoming Changes to Internally Funded Projects (Cost Share)

Overview of Changes

Effective July 1, 2025 (FY26), we’re changing how we account for certain research awards to improve tracking. Instead of using the single 012000 (Internal Projects) fund source, new projects will use specific, dedicated fund sources that better reflect their purpose.

Here are the new fund sources:

  • 012100 for Cost Share projects
  • 012110 for Deficit Projects
  • 012120 for Salary Cap Projects
  • 012130 for Interest Earned Projects

This means that a new Cost Share project, for example, will now be set up with its own fund source: 012100.

Impact on Current Projects

The new fund sources apply only to projects with a start date of July 1, 2025, or later. Projects created before this date cannot be converted.

To ensure consistency, Research and Cost Accounting will take the following steps for all 59 active awards with an existing cost share component:

  1. A new project with the 012100 fund source will be created for each affected award.
  2. The project number for this new project will be communicated to the Project Manager (PM) and the Principal Investigator (PI).
  3. Any costs posted to the old project on or after July 1, 2025, will be transferred to the new project.
  4. The old project will be closed.

It’s important to remember that for reporting purposes, you will need to consider the budgets and costs of both the old and new projects together. Both projects will be accessible within the same award for easy data retrieval.

Project Transition & Budget Management

The old “Internal” cost share project will remain open until its award closes or until September 30, 2025, whichever comes first.

  • All cost transfers related to the old project must be completed and posted in iO before the project closes.
  • Once the old project is closed, its budget balance will be calculated. If the balance is negative, the project will be closed, and the PI and department will need to communicate a management plan to Research and Cost Accounting before it can be reopened.
  • If the balance is positive, the remaining budget will be transferred to the new “Cost Share” project.

For active labor distributions on old projects, Payroll will automatically update them to apply to the new “Cost Share” project starting July 1, 2025.

Project Managers for impacted awards have been contacted directly by e-mail with the above message. If you have any questions, please feel free to respond to that e-mail or to contact Research and Cost Accounting (rchacctg@rice.edu).

OAC Dashboards (Finance Dashboard and Sponsored Projects and Faculty Funds Dashboard)

Image
EDIT (8/19/25. 3.14PM) While the dashboards have returned and can be used, we are aware that there are issues across SPFF with dashboard prompts not running analyses in the way they should. The cause of this issue has been diagnosed and the team is on it. It will very likely not be before tomorrow (8/20/25) that we are able to say how long this will take to fix. I will update this post with information as it becomes available.

EDIT (8/20/25. 8.59 AM) Dashboards are now operational.

Proposed FY26 Rates

Please be advised that Rice’s submitted Fringe rates are 25.8% for faculty and staff and 2.6% for students.

These rates are PROPOSED and may be used for FY26 grant applications (with a start date of 7/1/25 or later) but this are subject to change upon negotiation and execution of the official rates.

When more information becomes available, it will be added here.

How to select a Faculty Fund as a Destination for a Cost Transfer?

During the recent cost transfer training, there were a number of unanswered chat questions. The most frequent one of these related to Faculty Funds and how to process cost transfers to them?

Here’s the answer

1) Leave the ‘New Award’ field totally blank (i.e. delete all content from the cell)

2) Select or enter the Faculty Fund project number (must begin with the letter F) in the New Project Number(s) field.

3) Take care to confirm you have added the desired task number (which will default to ‘1’) in the New Task Number field.

Frequently-used RCA ticket categories

Using the correct category can improve processing times for tickets because it allows us to quickly assign the ticket to the correct RCA staff member.  Please note that the “Controller’s Office Use Only” and “RCA Use Only – Cash” categories should not be used by the departments.

Whenever possible, please include an iO award or project number in the Summary field.

Below are some of the most frequently-used categories.

Image

Expenditure Type for Undergraduate Fellows

We have received several inquiries regarding the correct expenditure type to use when paying for undergraduate fellowships.  This situation will be most prevalent on Research Experiences for Undergraduate (REU) projects, but can also arise for other types of projects.  These payments are processed through Payables and should use expenditure type ODC: Teacher / Trainee Allowance.

Please note that graduate fellowships are still processed through Payroll.  Information on graduate fellowship payments can be found on the GPS website: https://graduate.rice.edu/fellows-to-payroll.

SPFF encumbrance calculation revamp

Below are the changes happening with the Encumbrance calculation revamp:

• Encumbrance costs will be relieved when actuals are posted. They used to be relieved based on calendar days. The change addresses the issue of payroll costs being posted before the end of the pay period, which caused the remaining balance to be understated as both actuals and encumbrances were posted for the same pay period.

• The new encumbrance calculation now supports automatic calculation of fringe based on the assignment category. This eliminates the need to maintain a fringe line for all assignments. The Labor Distribution Administrator will be required to create a fringe rule only when the fringe costs do not follow the salaries and wages costing.

• The hourly employee pay period amount will now be correct. It was overstated.

• F&A on Tuition remission costs for the MTDC burden schedule projects will stop being calculated.

• The award overview page will stop duplicating projects with encumbrance costs.

• Added the LD comment field to the labor distribution details

Bridge Funding

Rice University remains committed to research, scientific discovery and creative works. In light of changing external funding priorities, a long-term sustainability approach is necessary to deliver on our strategic plan and increased impact. As a result, we are pleased to announce that we are launching a Bridge Funding Program for faculty whose federally sponsored research support has been unexpectedly terminated or reduced.

https://rice.infoready4.com/#freeformCompetitionDetail/1975820

Guidance on Distinguishing Sponsored Projects from Fee-for-Service Agreements

While both sponsored projects and fee-for-service activities involve external funding to the University in exchange for work performed by University personnel, they differ significantly in purpose, scope, and administrative requirements. Proper classification is essential for ensuring compliance with University policy and sponsor expectations.

If you are uncertain about how to classify a specific proposal, project, or agreement, please contact RchAcctg@Rice.edu for guidance and final determination.

Sponsored Projects

Sponsored projects are scholarly activities that directly support Rice University’s mission in research, teaching, and public service. These agreements—typically structured as grants, contracts, or cooperative agreements—require substantive intellectual input from Rice personnel and are subject to sponsor terms and conditions.

Sponsored projects must be processed through the Office of Sponsored Projects (OSP) and submitted via Cayuse.

Common characteristics of sponsored projects include:

  1. The project requires significant intellectual or scholarly contribution by Rice personnel.
  2. A formal proposal or award agreement is submitted and typically requires institutional approval or endorsement.
  3. The budget is itemized and may include sponsor-imposed restrictions on spending or rebudgeting.
  4. Cost-sharing or matching funds may be required.
  5. There is a specified level of effort or commitment from project personnel.
  6. Financial, technical, or progress reports—and sometimes audits—are required by the sponsor.
  7. The agreement outlines ownership or disposition of tangible or intangible property, such as data or inventions.
  8. Any unspent funds may need to be returned to the sponsor at the project’s end.
  9. The agreement includes terms for compliance with federal, state, or institutional policies (e.g., human subjects, export control, conflict of interest).

Fee-for-Service Activities

Fee-for-service activities involve providing routine, defined services using established methods or procedures, often under the direction or specifications of the external entity. These activities do not involve research, scholarly inquiry, or significant intellectual contribution and are not expected to generate new knowledge or result in publications.

Fee-for-service activities typically have these characteristics:

  1. The work involves routine, repetitive, or standardized services.
  2. Rice personnel provide minimal intellectual or scholarly input.
  3. No new intellectual property or research findings are expected to result from the work.
  4. There is no scientific uncertainty or hypothesis being tested—the deliverables are clearly defined.
  5. Data collected is provided without interpretation, and there is no expectation for publication or analysis by Rice personnel.

This guidance is intended to assist faculty and staff in appropriately classifying externally funded activities and ensuring that proper administrative and compliance protocols are followed. For case-by-case questions or complex situations, please reach out to RchAcctg@Rice.edu.

Relevant Policies
Policy for the Submission and Administration of Sponsored Projects https://policy.rice.edu/301

Signature and Approval Authority
https://policy.rice.edu/810

Award Setup Form information

We often get inquiries from departments about how to fill out the Award Setup Form, particularly with selecting the correct Field of Study (FOS), THECB Category, and Special Interest (SI).  While the form does provide some guidance on these sections, it isn’t easily accessible until the Adobe workflow has been started.  To assist, we’ve provided links to documents that explain what options are available for sections 5, 6, and 7 of the form.  Please note that two of these documents are in Box and will require Rice credentials to access.

HERD Fields of Study (FOS):
https://rice.app.box.com/file/1140270835436

THECB Categories:
https://rice.app.box.com/file/1140277639377

Special Interest (SI):
https://rice.box.com/shared/static/gs2tgke4vjq6h58mnot73es9jhnt8pc4.pdf

HR/Finance Service Requests for RCA

Creating a service request through iO’s HR/Finance Help Desk means you need information or support quickly. In order for RCA to route your request to the staff member who can help, we are updating the ticketing categories for RCA effective Monday, April 6, 2025. 

Need a quick way to access the right category? 

1.  Select the file folder icon to at the right of the category menu to access the “view in hierarchy” menu.
2.  Select the Category Name: Research and Cost Accounting (RCA).
3.  Select the specific drop-down category and item, then select OK at the top right of the screen.

Image

Please remember to include the iO Award/Project number, invoice number, or other reference information in the Summary field.

PPM Roles refresher

We frequently get questions and requests involving the various roles that are used in the Project Portfolio Management (PPM) system.  Below are the current roles, where they are applicable, and their purpose.

Image

Please note that role changes should be requested via the Help Desk ticket system.  Requests to add roles for personnel not in the Award Org should be approved by the Department Administrator.

Treatment of overspent awards

Updated 6/2/2026

Try as we might to stay within the sponsor’s budget, sometimes it simply costs more to complete the scope of work, and the award ends up being overspent.  When this happens, you might be tempted to move expenses off the award in order to bring it back within budget.  However, please keep in mind that any expenses associated with the SOW should remain where they are, even if it causes a negative balance.

Excess expenditures will be moved to the deficit project based on the expenditure type.

  • If the overspent amount includes expenses such as ODC and/or Travel, RCA will move these direct expenses to the deficit project
  • If the overspent amount includes expenses such as Salaries, Fringe Benefits, and Tuition Remission, the department will need to process an LD to move those overspent amounts to the deficit project.
  • If the overspent amount includes all types above, RCA will move ODC, and Travel and Department will move Salaries, Fringe Benefits, and Tuition Remission via LD.

Note: ODC: Excess Costs expenditure type is no longer used as it causes issues with invoicing, especially for Federal Awards.

After moving the direct costs to the Deficit project, the department will need to process a balance transfer to fund it.

Information on balance transfers can be found here: https://rchcostacctng.blogs.rice.edu/2021/08/18/balance-transfers-in-io/

Information on the correct Fund Types and Fund Sources for these balance transfers can be found here: https://rchcostacctng.blogs.rice.edu/2025/01/29/update-to-frequently-used-fund-types-and-fund-sources/

Attention Rice Research Administrators: Help Us Streamline Faculty Departures

As research administrators, you play a vital role in ensuring the smooth management of sponsored projects at Rice University. When a faculty member decides to leave the institution, it is crucial to notify both Research and Cost Accounting (RCA) and the Office of Sponsored Projects (OSP) as soon as possible. This early communication allows us to properly manage the relinquishment, closure, or transfer of awards, ensuring compliance with sponsor and university requirements.

Why Early Notification Matters:

  • Award Transfers or Relinquishments – Some awards may need to be transferred to the faculty member’s new institution or officially relinquished to the sponsor. This process takes time and requires coordination.
  • Final Invoicing & Financial Reporting – RCA must ensure all allowable expenses are recorded, final invoices are submitted, and financial reports are completed in accordance with sponsor deadlines.
  • Effort Certification & Payroll Adjustments – Proper documentation and certification of faculty effort must be finalized before departure to ensure compliance with federal and institutional guidelines.

How You Can Help: If you become aware that a faculty member is planning to leave Rice, please promptly notify both RCA and OSP. This proactive approach allows us to:

  • Assess the status of existing awards and determine next steps
  • Coordinate with sponsors on award relinquishment or transfer requirements
  • Ensure timely and accurate financial reconciliation and reporting
  • Address any outstanding compliance matters, including effort certification

Your partnership is invaluable in maintaining the integrity of Rice’s research enterprise. By working together, we can ensure a seamless transition for departing faculty and uphold our commitment to responsible research administration.

If you have any questions or need guidance on this process, please reach out to RCA and OSP. We appreciate your diligence and cooperation!

SPFF Dashboard Improvements – Co-PI and F&A rate

Search for PI/Co-PI has been combined for comprehensive reporting

What: The PI/Co-PI prompt has replaced the Award PI prompt, and the Co-PI name field has been added to all dashboard views except Labor Distribution Details and Labor Encumbrance Details.

Why:  This combined prompt allows faculty and administrators to prepare a comprehensive grants report for a PI whether they serve as PI or Co-PI on a project/award.

F&A Rates now included on the Award Overview report

What: Project/Award F&A rate will be included as a column on the Award Overview page. F&A Rate is also included as a hidden field on the Balance Details, Award Overview, and PI Project Summary pages.

Dashboard tip: Columns can be hidden or displayed using the right-click feature and selecting include or exclude. View more tips on the Dashboard Tips and Tools QRG.

Why: Displaying the F&A rate on the reports allows faculty and administrators to more easily validate the Project/Award F&A rate while reviewing financial reports.

Skills Training for Administrative Research Staff (STARS) Registration

Hello Research Administrators,

We are pleased to share that registration for the Skills Training for Administrative Research Staff (STARS) program is now open! STARS is a new training program offered to research administrators across Rice University. The program intends to enhance collective expertise, develop new skills, and promote professional growth. Through the duration of ten workshops, a variety of subject matter experts across campus will cover topics encompassing the grant lifecycle, including the pre-award process, sub-award process, personnel, compliance, and much more. The program is an opportunity to create true communities of practice and contribute to the Rice research enterprise.

Registration opens today, Thursday, August 1st, via Learning in iO. Please use this link if you have any questions on how to register.  It is crucial to attend all ten sessions in person to fully reap the benefits of the program and build connections. Registration will close Wednesday, August 28th at 5:00 p.m. or when the cohort is filled. Below you will find the direct link to register and a registration guide.

STARS Registration link: Click here

Enrollment Guide: Click here

The STARS program is a great opportunity to learn something new, refresh your understanding of the grant lifecycle and connect with other research administrators across Rice. Please join us!

All the best,

STARS Training Group

Updated dates for first and second close and final reports

Basically everything is pushed back two days due to hurricane Beryl:

July 12   Original entries to be submitted

July 15   First close reports available on dashboards

July 19   Second close – final day for corrections to be submitted

July 29   Final reports available on dashboards after 10 p.m.

Please contact crystald@rice.edu if you have questions.

Cost Share F&A Adjustments and Future Process Change

Effective February 15, 2024, RCA will adjust the accounting process for Cost Share F&A.

Currently F&A is being charged on cost share projects where no specific exclusion was requested in the award cost share agreement.  F&A on cost share charges is being recorded in the Cost Share Project and debited to COA with an expectation for the department to fund.

F&A for the cost share charges will be recorded in the Cost Share Project.  However, there will be no debit to the CoA, effectively forgiving the obligation for the department to fund.

F&A charges on cost share projects made prior to February 15 and that have already debited CoA accounts will be reversed by RCA prior to the end of FY24.

SPFF Date Issues

We have received multiple emails and helpdesk tickets regarding the ability to access FY24 dates in SPFF.  The GL Accounting Period filters are not functioning as expected on the Admin and PI SPFF Dashboards.  The iO support team is working to reset the filters.  The target date for a resolution is 02/16/24.  Please check the Known Issues page (https://ioevolution.rice.edu/known-issues) for updates.

Finance Dashboard

The Finance Dashboard Redesign Committee is excited to share the launch of the redesigned Finance Dashboard that will improve your experience and streamline financial reporting. The committee has been testing the dashboard for several weeks and think you will appreciate their favorite new features:

  • Faster response time and smoother navigation
  • Ability to view and filter on the Full Chart String or individual segments
  • Classification has been added to the table and filter options
  • Drill-down capabilities take you directly to details of the expenses
  • Updated CoA hierarchy makes it easy to view remaining budget in Supplies and Expenses categories separate from Salaries and Wages.

Training

Crystal Davis will host a webinar to preview the faster and enhanced design on Wednesday, January 31, at 3:00 pm.  After you attend or view the recording of the webinar, which will be posted on the iOEvolutiOn website, sign up for a hands-on workshop February 12 – 16 or in mid-March.  All details can be found on the iO EvolutiOn events page.

Corrected: expense reports not following approval workflow

The expense workflow issue causing reports to not route correctly has been identified and corrected.  With the correction comes a long-awaited feature:  negative expense reports can now be processed.  You no longer have to wait for offsetting charges to process a credit to your p-card.

Emails were sent to Cost Center and Project Managers to announce both the issue and correction (see December 11 email here and December 20 email here).

Oracle bug affecting labor cost reporting

An Oracle bug was introduced with the November 17th Quarterly Update that has caused all labor costs between 7/1/23 and 12/5/23 to be redistributed multiple times. This is visible in the Wages and Fellow Payments reports in the Finance Dashboard (Payroll Actuals, Gross Pay, and Graduate Student Pay reports). This issue does NOT impact actual pay to employees. The detailed email sent to Cost Center Managers, Project Managers and HCM initiators is viewable on the iO EvolutiOn Communications page.

Important notice: Some expense reports not following approval workflow

There is a bug in the Expense work flow that has caused reports submitted in November/December to not proceed to approvers.

Cost Center and Project Managers have received communications listing impacted reports and providing a temporary approval solution. Please see your department administrator for more details.

We apologize for the inconvenience. The iO Support Team is working closely with Oracle to address the issue as soon as possible. Watch the Known Issues Page for updates.

PTO (Vacation) Pay Charged to Grants

Why is PTO paid on the grant, rather than charged as a fringe benefit?

Rice’s annual fringe benefit agreement with the Federal government addresses the way Rice charges paid absences versus fringe benefits.  Excerpts below are from our FY24 agreement.

TREATMENT OF FRINGE BENEFITS:
The fringe benefits are charged using the rate(s) listed in the Fringe Benefits Section of this Agreement. The fringe benefits included in the rate(s) are listed below.

TREATMENT OF PAID ABSENCES:
Vacation, holiday, sick leave pay and other paid absences are included in salaries and wages and are claimed on grants, contracts and other agreements as part of the normal cost for salaries and wages. Separate claims are not made for the cost of these paid absences.

FRINGE BENEFITS:
FICA, Retirement, Disability, Life Insurance, Tuition Remission, Worker’s Compensation, Unemployment Insurance, Health Insurance, Sabbaticals, Parking, Employee Assistance, Child Care, Medical Administration, Flu Shots, Financial Planning, Wellness Program.

The rationale for this treatment is that the fringe benefit rate would be much higher if the costs for paid absences were included.

When an employee is paid on a grant and they leave Rice, does their vacation payout go on the award?

Yes, according to Rice Policy 405 Paid Time Off, III.D., “Payout of PTO at Termination”, the payout of unused PTO to a staff member (other than a postdoctoral research associate as described in IIIA above) with at least six months of continuous benefits-eligible service who terminates from Rice for any reason will be no more than one year’s accumulation based on FTE and years of service (e.g., a maximum of 26 days, or 208 hours, for a full-time staff member with fifteen years of service.) Staff members on research grants are eligible for the payout of unused PTO. However, if the grants from which they are paid do not allow the payout of terminal PTO, principal investigators and departments must identify another appropriate source of funds for the payout.”

https://policy.rice.edu/405

Additional background:

The same applies if a person changes employment types, such as staff becomes faculty.  In this case, different benefits and policies apply, so the prior assignment is terminated in HR and the person is treated as a new hire.  Therefore, accrued PTO is paid out.

Rice’s DS-2 (Cost Accounting Standards Board Disclosure Statement) Part V, 5.1.0 is consistent with Policy 405.  Excerpt below:

Method of Charging Leave Costs. Do you charge vacation, sick, holiday and sabbatical leave costs to sponsored agreements on the cash basis of accounting (i.e., when the leave is taken or paid), or on the accrual basis of accounting (when the leave is earned)? (Mark applicable line(s))

A. _X_ Cash
B. ___ Accrual

September RCA Office Hours and SPFF Training

RCA office hour for the month of September has been cancelled.  However, we will still be holding hands-on SPFF training.

SPFF Dashboard Virtual Hands-on Training

Join Teia Wright and the RCA Team for an on-line walk through of the SPFF Dashboard. Follow along on your own dashboard and ask questions along the way as you learn dashboard navigation and best practices for grants management.

If you would like a demo at your department faculty or staff meeting, please email iOEvolution@rice.edu and we will contact you to arrange a time.

Friday, September 29th 10:00 AM – 11:30AM

Zoom Link: https://riceuniversity.zoom.us/j/3133585535?pwd=T3RkenpjRVE4ZWJpUGpqZ3VYOGg1QT09

Meeting ID: 9313 358 5535 Passcode: 556994

New fund type for faculty funds

Based on user requests presented to and approved by the iO Finance and Research Functional Committee, we are making a change to the Faculty Fund Types to facilitate department reconciliation.  

Starting on September 15, 2023, the General Ledger Fund Type for Faculty Funds will change from Fund Type 101 to Fund Type 109. This impacts Fund Sources 010000, 010010, 010020, 010030, and 010040. Because this is a General Ledger change, it will not impact Faculty Fund reporting in the Projects module or on the SPFF Dashboard. 

Why Are We Making This Change? Currently, both Faculty Funds and other departmental unrestricted designated funds fall within Fund Type 101, making management of both challenging. Adding an independent fund type for Faculty Funds:

  • facilitates reconciliation between Faculty Fund projects and the associated GL transfers
  • ensures that Faculty Fund projects are funded appropriately from GL accounts
  • enables clear insight into tracking transactions between Projects and the General Ledger

Important Details: 

  • This change will not impact the way FF balances and transactions are presented in PPM or on the SPFF dashboard; it only affects general ledger accounting. 
  • Transactions from FY22 and FY23 will remain in Fund Type 101 as they are currently recorded and displayed. 
  • Transactions from FY24 will appear in Fund Type 109. 
  • Transactions between July 1, 2023, and September 15, 2023, will be moved to Fund Type 109 on September 15, 2023. Crystal Davis will monitor “in-flight” transactions that post the week of September 18-22 and make any necessary corrections. 

What Do You Need to Do? 

Finance and RCA are working to make all necessary transitions behind the scenes, but it is important for you review your funds for the following:

  • If you have Faculty Funds pointing to fund sources other than 010000, 010010, 010020, 010030, or 010040, contact Crystal Davis before September 15, 2023, to ensure those transactions are included in the transition. 
  • Between September 15 and September 28, review transactions in Fund Type 101 and Fund Type 109 and work with Crystal to resolve any unexpected results. 

We appreciate your cooperation during this system update, which will help streamline your financial processes and reporting. If you have any questions or concerns, please do not hesitate to reach out to Crystal Davis or the finance team.

SPFF Dashboard Hands-on Training

Thursday, August 24 from 2:00 pm – 3:30 pm
Wednesday, September 6 from 10:00 am – 11:30 am

Registration is required using this link due to limited space. You will receive additional information about the location after registration. If these times don’t work in your schedule, add your name to the Waiting List tab.

If you would like a demo at your department faculty or staff meeting, please email ioEvolution@rice.edu and we will contact you to arrange a time.

Enhanced SPFF Dashboard Office Hours

The new Faculty/PI SPFF Dashboard and new Administrator SPFF Dashboard will be moved to production starting at 5:00 pm on Thursday, June 1 and will be available on Monday, June 5.  In order to ensure sufficient time for the transition and testing, the SPFF dashboard will not be available during this time.

SPFF Dashboard Training

Via Zoom
Thursday, May 18  2:00 – 3 pm
– Intro to Enhanced Sponsored Projects and Faculty Funds Dashboard

In-Person, Hands-on Guided Workshops @ COB 4th floor OIT Office Suite
Friday, May 19  1:00 – 2:30 pm
Monday, May 22  1:00 – 2:30 pm
Monday, May 22  3:00 – 4:30 pm
Tuesday, May 23  1:00 – 2:30 pm
Tuesday, May 23  3:00 – 4:30 pm

Register for an in-person guided workshop using this link
Hands-on training will be conducted in a Test environment with data as of 5/8/23.

The Rice Payment Reference Guide

This is a handy guide to employee and student payments that covers which office pays, which tax forms the payee completes, and what type of IRS reporting (if any) happens afterwards.  The guide is a joint effort of Payroll and Procure to Pay that can be found on both websites and is also downloadable here: Rice Payment Reference Guide

If you would like to do further reading about payments to employees and students, you might like IRS Publication 525 on taxable and non-taxable income, which you can review here: https://www.irs.gov/publications/p525

March 22nd Office Hours update

We had hoped to discuss the new Faculty/PI SPFF Dashboard during our next office hours.  However, the launch of the new dashboard has been delayed while some technical issues are worked out.  Therefore, the topic for the March 22nd office hour will be Cost Transfers.  Office hour this time around will be at 10:00 am.

For those of you who had signed up for the in-person guided workshops on the new dashboard, please be aware that they have also been postponed.  The registration link has been deactivated and will go live again once we have new dates available.

March RCA Office Hours

RCA office hour series continues with the following topics:

Thursday, March 2nd from 2:00-3:00 – Cost Share
Wednesday, March 22nd from 10:00-11:00 – Intro to Faculty/PI SPFF Dashboard

The link to the Zoom meeting can be found in the iO website.

We will also offer in-person SPFF guided workshops in the Cambridge Office Building 4th floor.

Monday, March 27th from 2:30-3:30
Tuesday, March 28th from 2:30-3:30
Thursday, March 30th from 9:00-10:00

Register for an in-person guided workshop here!

Payroll Office Hours: Encumbrances

By popular request, the Payroll Office is hosting a special topics office hours focused on Encumbrance Calculations and Management.

Materials were prepared in conjunction with the RCA, Finance, Enterprise Systems and HR teams who will also be in attendance.

Payroll Office Hours: Encumbrance Calculations and Management
Wednesday, January 18, 2023
11 am – noon

Join Zoom Meeting
https://riceuniversity.zoom.us/j/99356972751?pwd=YmI3Mjc1VENrN1BmWTBPeHdFVzlIQT09

Meeting ID: 993 5697 2751
Passcode: 140274

Office hours materials will be made available in the iO Training Catalog by January 27, 2023.

Using the SPFF to prepare for sponsored award closeouts

Most of you have been using the SPFF for over a year in order to see expenses and commitments on your sponsored awards, University awards, and faculty fund projects.  I would like to point out another useful feature that was created in order to assist the departments with closeout preparations.

In the Awards Overview tab, there are two tiles at the far right indicating how many awards will be ending in the next 30 – 90 days.

Image

Clicking on the tiles will take you to a list of the respective awards.  Please use this list to determine which awards require your prompt attention.   Any missing expenses or other corrections should be made quickly in order to assure they are captured in the final report or invoice.  Please note that any expenses not included in the final invoice are at risk of not being reimbursed by the sponsor and will have to be covered by departmental funding.

Award Setup Form

New Feature: Award Setup Form added to SPARC award notification emails

iO has the capacity to store information about awards that is not captured in the Cayuse documents, but is significant for reporting and analytics.  Until now, RCA has been collecting this information through informal communications.  In order to streamline the process, we have designed a simple, one-page Adobe Sign form that allows departments and PIs to provide all this data before setup begins.

As of this week, the SPARC award notice email will contain a link to the form in the Comments section (see below).

4. ***NEW*** Please complete the Award Setup form https://tinyurl.com/492j5e93 so RCA has the information necessary to create the award in iO.  For best results, log in to your Adobe Sign account before clicking the link.  You only need an Adobe Sign account if you will be initiating these forms. If you do not currently have a Rice Adobe Sign, send a request to mailto:helpdesk@rice.edu.  More information about Adobe Sign can be found here: https://kb.rice.edu/page.php?id=85738

The Department Administrator, Project Manager, or PI who receives the SPARC notification and has a Rice Adobe Sign account can initiate the form and add others to the routing as needed. There are no required approvals, and the form is configured to include RCA as the final stop.  Please note the brief instructions for how to fill out the workflow at the top of the page.  For more information about Adobe Sign, please visit https://kb.rice.edu/page.php?id=85738.

Detailed information on how to fill out the form itself can be found in the Award Information Help Document.

Non-Billable projects

Updated 6/02/2026

We’d like to share information about the different Non-Billable projects available to departments in iO.  Some of these are created based on information contained in OSP notices, while others require a help desk ticket to the RCA queue in order to be created.

Advance Spending award

  1. Used when an initial agreement has not been received from sponsor
  2. Processed through OSP
  3. RCA will create an award and an associated project
    1. Award and project names will include “Adv Spdg”
    2. Duration will be six months
    3. Project will have an external funding source
    4. F&A rate will be MTDC
    5. Budget will be set up for $1
  4. Once agreement is received through OSP, RCA will update iO
    1. Award and project names will be changed to reflect sponsor information
    2. Duration will be extended per agreement
    3. Budget will be amended per agreement
    4. Award will be set to Billable

Cost Share project

  1. Used when a proposal includes Rice cost-share
  2. Signed cost-share form should be included in OSP award notification packet
  3. RCA will create a new project while setting up a new award
    1. Project name will include “C/S”
    2. Duration will be the same as award
    3. Project will have “Cost-Share” funding source (balance transfer required)
    4. F&A rate will be the same as the signed cost-share form
    5. Budget will be set up for the amount on the cost-share form
    6. Department will use the project number on LD submissions for cost-shared salary
    7. All travel and ODC expenses that are to be cost-shared should be coded to this project

Salary Cap project

  1. Used when a faculty member’s salary is above the limit set by NIH or CPRIT
  2. Department will submit a help desk ticket (non-billable projects)
  3. RCA will create a new project within the existing award
    1. Project name will include “Salary Cap.”
    2. Duration will be the same as award
    3. Project will have Salary Cap” funding source (balance transfer required)
    4. F&A rate will be 0%
    5. Budget will be set up for $1 until one is provided by the department
    6. Department will use project number on LD submissions

Pending Amendment project

  1. Used when the existing award period is ending, but we are expecting an amendment for more time
  2. Department will submit a help desk ticket (non-billable projects)
    1. Department will attach request form found on RCA website
  3. RCA will create a new project within the award
    1. Project name will include “Pending Amd”
    2. Project will begin the day after the award end date, and will have a duration of six months
    3. Project will have same external funding source as Base project
    4. F&A rate will be same as current project(s)
    5. Budget will be set up for $1
    6. Department revise LDs to reflect new project number
    7. All new travel and ODC expenses are coded to the new project
  4. When an amendment is received, RCA will process it under this new project
    1. Project name will be changed to “Year 2” or other applicable identifier
    2. Expenditures posted will then become billable

Deficit Project 

  1. Used when project expenses are more than allowed by the sponsor
  2. Department will submit help desk ticket (non-billable projects)
  3. RCA will create a new project within the award
    1. Project name will include “Deficit”
    2. Duration will be the same as award
    3. Project will have “Deficit Project” funding source
      1. Department will process balance transfer
    4. F&A rate will be 0%
    5. Budget will be set up for the direct portion of the overage amount
    6. RCA will process cost transfer to move the direct portion of the overage to the new project if the overage includes ODC and/or Travel Expense Categories
    7. The department will initiate an LD to move these expenses to the deficit project if overage includes Salaries, Fringe Benefits, and Tuition Remission,

Update to FBDI folder

In order to make the structure more consistent and easier for users, we’re restructuring some of the sub-folders in Box.

Currently, you see:

Image

We are going to move all of the drop off locations to “drop off here” and all of the processed / in progress files to “processed”.

Within “drop off here” you will now see these choices:

Image

The template for each folder is listed, and all of these are available under templates, which will look like this:

Image

The FBDI box folder will continue to host the Labor Distribution template and instructions and the budget transfer memo job aid, but both of these are submitted through AdobeSign processes and completed templates should not be dropped off in Box.

Please name your general ledger entries with your name and date.  Please name your sponsored project cost transfers using the following naming convention:

Image

These naming conventions will make it easier for RCA to answer questions when people inquire about progress (i.e. “did my entry post?” or “did my cost transfer for project XYZ get processed?”).

Expense Report Costs Posting to Incorrect GL Strings on a Sponsored Project

Hello, everyone:

We have received several inquiries lately regarding expenses that posted incorrectly to a department’s Central Operating Fund (100.000000) instead of posting to the appropriate Fund Type and Fund Source for a sponsored project (e.g. 104.040000 or 104.047000).

The Fund Source value is derived with a mapping set based on the Award Type for Rice Sponsored Projects.  PPM has a version of the mapping set, and it contains 23 Award Type values.  Payables also has a version of the mapping set, but it only contained 9 Award Type values.  When the system can’t find a match, it maps to an employee’s Default Expense Account.  Typically it would be the Central Operating Fund, but it doesn’t necessarily have to be the case.

The Payables mapping set has been updated and should now include all Award Types for Sponsored Projects.  In order to correct any existing error on your GL, please create an GL entry to credit expenses on the incorrect COA string and debit expenses on correct COA string.

Cornucopia of Useful Information

Hello,

Below are a few things to keep in mind when managing your sponsored projects.

Close Date- iO utilizes the close dates to control spending on projects. The close dates are typically set to 45-60 days after the award ends to allow departments adequate time to post adjustments. Note that the expenditure item date of the expense must be within the project period. Expenses must be posted on or before the close date to report the expense via invoice and/or financial report to your sponsor.

Advance Spending- New advance spending awards will be setup initially in iO as an award, and not a Faculty Fund Project task anymore. Once the award has been executed, RCA will update the award budget and project end dates and allow iO to process invoicing.

Deficit/Overspent Projects- Costs in excess of the award amount will be moved to another project on the award. RCA will create the deficit project and move the expense. Essentially, the excess costs will be accounted for and reported as uncommitted cost share. Funding for these costs are managed the same way as your cost share expenses.

Project Tasks and Subtasks– For sponsored projects, all tasks are “Task 1”. For Faculty Funds, there can be multiple tasks and subtasks. Note: When you add subtasks to a task, it makes the original, primary task nonchargeable. If you have expenses, including labor distributions charging to a primary task, but you created subtasks, that expense will not be processed since the expending must occur at the subtask. A new labor distribution schedule will need to be created and sent to Payroll for processing.

Subaward Requisitions- Beginning in January, subawards requisitions are now split into two lines. One line for the amount up to $25K, and the second line for the amount over $25k. This way, when you do your receiving, you can select the first line on the requisition to be paid first, then the remainder on line 2. This will correct the F&A calculation challenges some departments were having on subawards. Correcting F&A on subawards prior to January require submission of a cost transfer form.

Communication– When contacting RCA via the helpdesk, please include the award/project number and your Org number so we can route the request to your accountant for a prompt reply.

 

Awards, Projects, and Tasks (oh, my)

There’s a lot of new terminology that we’re all having to learn with the iO system.  Three of the more important terms are Award, Project, and Task.  Let’s take a quick look at what each one means and what it’s used for.

Sponsored Projects

Award is only used for sponsored projects.

  • Award number for externally-funded sponsored projects start with 1
  • Award number for University-funded sponsored projects start with 9
  • The award contains the demographic information, such as sponsor name, start and end dates, PI, Co-PI, terms & conditions, etc.
  • Each sponsored project gets one award number for the duration of the research being done
  • Expenses do not post to awards

Project is what you should enter when charging to sponsored projects.

  • Project numbers for sponsored projects start with G.
  • There can be multiple projects associated with a single award.

Task is where budget and expenses live.

  • Sponsored projects are not managed by task, thus the task for sponsored projects is always Task 1.

Faculty Funds

Project number for Faculty Funds start with F.

  • In addition to budget and expenses, FF projects contain the demographic information since there is no award associated with them.

Task is where budgets and expenses for faculty funds live.

  • When a FF project is created, it automatically has four tasks, but the departments can set up more as they see fit.

Early Project Spending Options

In situations requiring work to begin before an award’s official start date, you have two mechanisms for incurring costs early: Advance Spending and Pre-Award Spending.


Advance Spending

Use when: The sponsor has not yet issued the official award (it is still being negotiated).

This mechanism creates an early award fund to allow work to begin and prevent the need for cost transfers. It is also used for awards with restricted carry-forward that receive an annual Purchase Order (PO) from the sponsor.

How to Request: Work with the Office of Sponsored Programs (OSP) to submit a Pre-Award/Early Setup Request via Cayuse.

  • You will need to specify the exact amount of direct and F&A costs needed and provide a rationale.
  • Risk Note: If the award is not granted, is for a lower amount, or has a start date outside the 90-day pre-award window (for federal funds), the responsible Dean’s office will work with the department and PI to identify an alternate fund to cover any unallowable charges.

Pre-Award Spending

Use when: The sponsor has already issued the official award.

Most federal sponsors allow recipients of grants and cooperative agreements under Uniform Guidance to incur costs up to 90 calendar days before the official start date without prior approval. For non-federal sponsors, you must provide written approval from the sponsor.

If your OSP-received federal award has allowable costs that fall within this 90-day window, you may request Pre-Award Spending.

How to Request: Work with OSP to submit a Pre-Award/Early Setup Request via Cayuse to adjust the award’s official start date.

Note on Travel Expenses

Rice/Oracle (iO) posts actual travel costs after a travel expense report is completed.

Therefore, if travel is booked before the award start date but the travel itself occurs during the period of performance, the final cost (posted when the expense report clears) will be allocable to the project.

  • Should this rare scenario occur, the cost must be initially posted to a departmental COA. Once the award period begins, the cost can be transferred to the sponsored project and must be clearly documented to confirm its allocability.

[Post Updated on 10.16.25]

Expenses Troubleshooting

Hello,

Several people have contacted RCA and P2P concerning issues when charging a sponsored project. Most of the issues have been corrected by doing the following tasks:

  • For requisitions, configure your Favorite Charge to Account.
  • Enter an expenditure item date and budget date that is within the project period and task finish date.
  • For Faculty Funds, ensure there is an active budget created on the project.
  • For Faculty Funds Discretionary Task, charge to Task 2.2
    • Tasks are not chargeable if there is a subtask (i.e task 2 is not chargeable because task 2.2 is the chargeable task)

Viewing Sponsored Project Expenses and Funding at the COA Level

For Sponsored Projects, the following funding sources are used to map the iO projects to the COA. The fund source mapping is based on the Award/Project Type and Task of the Project. Navigating on the Finance Dashboard and selecting the Award/Project Org and Fund Source to see the transactions.

Below are the Funding Sources for PPM Projects:

The Fund Source for Sponsored Projects are:

  • 040000 Federal-Direct
  • 041000 State & Local Gov – Fed Prime
  • 042000 Industry-Fed Prime
  • 043000 Other-Federal Prime
  • 045000 State & Local Gov – Direct
  • 046000 Industry-Direct
  • 047000 Other-Direct
  • 048000 Federal Pass Through

For Cost Share and University Award Projects, the Fund Source defaults to the values below. For Faculty Funds, the funding source is derived from each task on the Faculty Fund. To see the expenses that need to be funded for University Awards, Cost Share, and Faculty Fund projects, navigate to the fund balance report on the dashboard to see the expense and funding activity.

For Cost Share Projects, Deficit Projects, and Salary Cap Projects, the Fund Source is:

  • 012100 Cost Share

For University Awards, the Fund Source is

  • 012000 Internal Projects

For Faculty Funds, the Funding Sources are:

  • 010000 Faculty Discretionary
  • 010010 Faculty Start-Up
  • 010020 Faculty Non-Sponsored Research Funds
  • 010030 Faculty Retention

Navigating in the Finance Dashboard- Budget to Actuals

Image

Enter the Period Name, Organization, and Fund Source to see the Budget to Actuals information. You can see the beginning fund balance on the fund balance report.

Fund Balance Report

Image

This report shows the beginning balance by Fund Source for a particular Org. The Period Net shows the expense activity in the Period (September 2021) $2,305.50 for an Internal Award.

 

2 New FAQs

FAQ 1: What is the process for managing overspent awards in iO?

Once the award has ended, any expenses that are in excess of the award budget are transferred to a Deficit project. RCA will create the Deficit project as needed and move the total deficit amount there.  Please create a help desk ticket for this request.

FAQ 2: What is the process in iO to manage the residual balances of fixed price awards?

  1. Research and Cost Accounting (RCA) will confirm the final expenditure amounts with the PI / department administrator (DA). The DA will alert RCA when the sponsor confirms satisfactory completion of all deliverables.
  2. Full Facilities and Administrative costs (F&A) will be applied to the award prior to transferring the residual funds in order to ensure all F&A costs associated with the award are fully funded.
  3. The award project end date will be extended by 1 year to allow time for the funding to be spent by the department. F&A charging will also be turned off by RCA to ensure new expenses do not incur F&A.
  4. The funding remainder may be moved to the faculty’s faculty fund research task if there are no further expenses related to the project’s scope of work.

The procedure for residual funds has been updated on the RCA website. https://controller.rice.edu/rca-fixed-price-funds

These FAQs, and others, can be found at https://controller.rice.edu/rca-faqs

Nick

POETAF vs COA

Many of you have reached out to RCA with questions about what COA information you should enter when charging expenses to a project.  We discussed it with the experts, and we have an easy answer for you: the COA information is there as a pass-through only, so you don’t need to worry about it.

While the current Procurement: Order by Quantity or Amount job aid does indicate that a COA string is required to be entered for every purchase, including project-funded purchases, it fails to mention that the COA information will be overridden by any POETAF information entered.  P2P will work on getting the job aid updated to explain this aspect of the process.

So if you enter POET information for your purchases and a COA pops up, please leave it with whatever information defaults in there.  If you edit the COA information for any reason afterwards, it will override the POET information and your charge will not post to PPM.

University Award Procedure

University Awards

Rice‐funded awards that are made to faculty or staff through a competitive process (such as: Faculty Initiative Fund; Enhancing Rice Through Information Technology program; Shell Center; and similar seed funding programs managed by different units) will be established in iO as University Awards.

Each Rice‐funded award will have a unique Award number and be established in iO in the organization of the recipient. RCA establishes the award in iO. The recipient of the Award is responsible for ensuring the funding is transferred to their Org’s funding source. At the closing of the award, unspent funds will need to be returned to the funder of the award.

Setup of University Awards

For RCA to establish the University Award in iO, please provide the following information in a helpdesk ticket in iO:

  • PI Name
  • Project Manager
  • Award Participants
  • Award Title
  • Award Amount
  • Award Org
  • Start and End Date
  • Award Purpose (Research or Instruction)
  • Award Category (Basic, Applied, or Experimental research)
  • Field of Study
  • Award Agreement

https://controller.rice.edu/rca-university-awards

 

Cost Transfer Procedure for Sponsored Projects

Good Morning,

The procedure for performing cost transfers in iO has been updated on RCA’s website. The information below can be found at this link https://controller.rice.edu/rca-cost-transfer

Cost Transfer Process in iO

The process for cost transfers in iO is dependent on the transaction source (converted or iO created) and the transaction type (labor and non-labor).

Cost Transfers for Costs Incurred Prior to July 1, 2021 (Both Labor and Non-Labor Converted Costs)

  • Converted costs will be managed in iO using the NON-LABOR COST TRANSFER FORM. For the costs to be transferred, a description of the cost transfer as well as the invoice information must be entered, as well as the current and new COA and POET accounting information. RCA will enter the information into the PPM Project Costs ADFDI template and upload into iO.
  • Converted costs cost transfers are to be requested by the Department Administrator and uploaded to BOX for processing.

Cost Transfers for Non-Labor Costs Incurred After July 1, 2021

  • Cost transfers for non-labor costs will be managed in iO using the NON-LABOR COST TRANSFER FORM. For the costs to be transferred, a description of the cost transfer as well as the invoice information must be entered, as well as the current and new COA and POET accounting information. RCA will enter the information into the PPM Project Costs ADFDI template and upload into iO.
  • Non labor cost transfers are to be requested by the Department Administrator and uploaded to BOX for processing.

Labor Cost Transfers for Costs Posted Beginning July 1, 2021

  • Labor cost transfers will follow the general iO process for Labor Distribution changes. For changes to sponsored projects entered 90 days after the end date of the original labor distribution, the following is required:
    • The field “Includes sponsored projects over 90 days:” must be marked “Yes” on the Labor Distribution form.
    • A comment must be entered on the form explaining the reason for the cost transfers.
    • Include the Department Chair as an Optional Approver on the LD template so the required department chair approval is obtained.
    • Labor cost transfers are to be requested by the Department Administrator and forwarded to Payroll for processing via Adobe Sign.

Balance Transfers in iO

For those who missed it, last week the Budget Office sent out the following information  about how to process balance transfers in the new system:

There is now a new interim transfer process for handling fund balance transfers, formerly called budget transfers.  This process entails completing an AdobeSign form that is routed for workflow approvals (see attached job aid) and posts in iO.  This process is for temporary (operating year) balance transfers between fund types or between departments.  You will need to contact the Budget Office for base (permanent) budget adjustments as they will not be processed using this interim process.

Important things to note:

  • All transfers will be processed as Year-to-Date entries in iO, using the Transfers – Inter/Intra Departmental account code (6800).
  • Because of the end-of-year carryover process for the Unrestricted General Operating fund (000000) and because unspent fringe benefits budgets do not carryover, the Budget Office will need to capture fund balance transfers associated with salary and fringe benefits accounts (including Faculty Academic Year Time transfers).
  • To capture the fringe benefits, the Adobe Sign form will contain a drop-down list of valid accounts (including faculty, staff, student, and fringe accounts) that will be written to a database file for use during the year-end analysis of carryover funds.
  • Use of Salary and Fringe accounts is only permitted on the Unrestricted General Operating fund (000000).
  • Faculty Academic Year Time transfers will require a separate action by the Project Administrators to update the PPM faculty/task budgets of any faculty receiving AYT funds.
  • Faculty fund transfers will be a two-step process.  First, there will need to be a transfer to the receiving department’s designated fund with the appropriate fund source code (Faculty Discretionary – 010000, Faculty Start-up – 010010, Faculty Non-Sponsored Research Funds – 010020, or Faculty Retention – 010030).  Second, a separate action by the Project Administrators will need to be performed to update the PPM faculty/task budgets for the faculty receiving the additional funds.

Job Aid:  AdobeSign iO Balance Transfer

Sponsored Projects Expenditure Types

We’ve had several departmental folks reach out to us asking what “account code” to use for their Sponsored Projects expenses in PPM.  I know we’re all used to having to enter an account code number as part of the FOAPAL in Banner.  However, in the iO system, we use expenditure types instead of account codes, and we no longer need to memorize the corresponding numbers.  Yay!

In PPM, Sponsored Projects expenditure types are broken down into 8 expenditure categories:  Salaries & Wages (S&W), Fringe Benefits (FRB), Tuition Remission (TUR), Other Direct Costs (ODC), Travel (TRV), Subawards (SUB), Equipment (EQP), and Facilities & Administrative Cost (F&A).  Each of those expenditure categories has multiple expenditure types associated with it.

So for example, if you want to charge lab supplies to a sponsored project, you would search for “supplies” in the expenditure type field and it will give you a list of all the ones that have the word supplies in them.  Then you just pick the one called ODC: Supplies Laboratory.

Please see the attached list for expenditure types allowed on Sponsored Projects.

ET List: Expenditure Types

Dates in iO

Expenditures associated with Sponsored Projects, Faculty Funds and Capital Projects created and managed via PPM in iO have multiple associated dates.  These dates allow for tracking of costs from both a compliance and financial reporting perspective.

Expenditure Item Date

The Expenditure Item Date is the date that a transaction occurs.  For sponsored projects, the Expenditure Item Date of a transaction must be within the period of the grant in order to comply with the terms of the award.   Expenses with an expenditure item date outside of the project period will fail to post on the project in iO.

Creation Date and Accounting Date

A transaction’s Creation Date is the date the transaction is loaded into PPM, while the Accounting Date is the date the transaction is recorded in the General Ledger (GL).  These dates are used for financial management and reporting purposes.  These dates may differ depending on the timing of the accounting process for each module.

Example:

Assume that following completion of a business trip, a staff member has created and submitted an expense report, and all of the approvals (departmental and central) are completed as of June 15.  Assume also that the related accounting processes for both PPM and the GL are run on June 15.

If this report contains an expense of $300 for an airline ticket that was paid via credit card on May 15, then the Expenditure Item Date for that $300 in travel expense will be May 15.  However, the Creation Date and Accounting Date for that $300 travel expense will be June 15, as that is the date the accounting process for the expense was completed.

PPM Basics for Sponsored Projects Administrators

Because there’s so much new terminology and information we’re all having to learn, I thought it would help if we had one place to list some of the basic concepts of Project Portfolio Management (PPM).  Please keep in mind that this presentation is not all-inclusive and is only meant to be an overview of PPM for departmental research administrators.  The presentation will most likely be updated from time to time as we determine what information is most helpful for PPM users.

Presentation:  PPM basics

Financial Management Guidebook

Shared per request of iO Change Management Team

The Financial Management Guidebook and Chart of Accounts (CoA) Quick Reference Guides (QRGs) are now available to you on the imagineOne website under the Chart of Accounts Redesign menu. These resources will provide you with an opportunity to support your learning and think about the way we do business as we approach go-live July 1, 2021.

The Financial Management Guidebook is intended to serve as a reference document for financial administrators across campus as we transition from the Banner FOAPAL to the Oracle CoA. The Guidebook contains an overview of and instruction on use of the CoA and will provide direction on key concepts of fund and program management along with transaction level description and examples. The QRGs, on the other hand, highlight a handful of key concepts from the Guidebook in a simple, summarized format for quick reference.

You can also find recordings of the imagineOne Roadshows and that will provide you with an opportunity to see how the new CoA works in practice and help prepare you for training. If you have questions surrounding the Guidebook or QRGs, please reach out to the imagineOne Project Team at  imagineOne@rice.edu.

iO RCA Updates June 30 (Sent via listserv)

Hello,

On the eve of iO go live, I wanted to take this opportunity to provide information regarding many changes that may impact your organization.

  1. RCA accountant responsibilities are now managed by Org (Dept). Attached is the new assignment list. The new assignment list is also on our website.
  2. Please use the new iO HR/Finance helpdesk for all your correspondence with RCA. Navigate to this page for instructions on how to use the helpdesk. The configured RCA categories in the helpdesk are:
    1. New Faculty Fund Projects
    2. Cash Management Questions
    3. Budget Revisions
    4. University Awards (U funds)
    5. General Questions
  3. Advanced Spending procedures have been updated on RCA’s website. PLEASE READ
  4. Faculty Fund procedures have been created and posted on RCA’s website. PLEASE READ
  5. June activities will begin to be entered in iO on July 5th, in this order:
    1. New Awards
    2. Date Extensions
    3. Other Amendments
    4. Budget Revisions
  6. Patience- Please be patient with us as we catch up on June activities while also learning iO. We will continue to provide the same excellent customer service that you have come to expect from RCA.

New Subaward Process in iO (Sent via listserv on July 15)

Hello,

We are pleased to announce the new subaward process. RCA will now be creating requisitions (reqs) and P2P will be creating the purchase orders to manage subawards in iO. New subawards issued by SPARC after 05/31/21 will need a requisition and purchase order created, but unlike Banner, they will not be set up as separate projects in iO.

All existing subawards were converted from Banner as separate projects, and we are working diligently to create requisitions for them.  The available balance of the subaward subfund in Banner will be the new requisition budget amount in iO.  We are prioritizing the creation of reqs for invoices that are ready to be paid.  If you get a notification to approve a requisition, please do so, otherwise a purchase order will not be created, and you will not be able to pay your invoice.  Refer to this job aid on how to process your invoices.

For the approval of new subaward invoices in iO, a subaward workflow has been set up in AdobeSign to quickly route a subaward invoice from RCA to the Project Manager for review and the PI for approval.

The following steps outline the subaward process (https://controller.rice.edu/rca-faqs):

  1. SPARC sends draft subaward agreement to RCA
  2. If necessary, RCA requests that P2P create a new supplier
  3. RCA creates and submits requisition based on draft agreement, which is routed to the Cost Center Manager. The Project Manager is entered as the requestor.
  4. Cost Center Manager approves requisition
  5. P2P creates PO based on approved requisition
  6. RCA provides PO number to SPARC to be included in final subaward agreement
  7. Subawardees are instructed to submit invoices to subinvoices@rice.edu, which is monitored by RCA
  8. Invoices are logged and entered into AdobeSign by RCA, which sends the invoice to the appropriate approvers (including PI)
  9. Project Managers are responsible for getting PI signature/approval on the invoice
  10. Project Manager will complete receiving process in iO
  11. P2P will process invoice for payment

Farewell to Marissa

Marissa Gonzalez, Research Accountant III, is departing Rice University to work at Stanford University. Marissa’s last day is this Friday, July 30th.

Marissa began working in the Controller’s office, in RCA. in 2017. Since then, Marissa has continued to grow and develop into a very strong sponsored projects accountant. She was often relied upon by the departments and her peers in RCA for her extensive knowledge and experience in sponsored projects. Marissa could always be counted on to complete her work responsibilities without fail. Marissa’s calm demeanor, hard work ethic, and positive attitude will certainly be missed as well.

We are sincerely grateful in Marissa’s dedication and hard work she has given to our office and the University. We wish Marissa good luck in her new role!