Intercampus Order/Charge (IOC)

An Intercampus Order/Charge (IOC) is used to record financial transactions between UC campuses. These transactions include revenue for goods or services UCR provides to another UC campus, reimbursements for expenses, and other interlocation transfers. IOCs ensure accurate financial reporting across the UC system.


Tasks Supported by an IOC

  • Charging another UC campus for services provided by UCR
  • Recognizing revenue for intercampus activity
  • Reimbursing UCR for expenses paid on behalf of another UC campus
  • Recording valid intercampus financial transactions requiring UC system-level accounting

Tasks NOT Supported by an IOC

  • Transactions between UCR departments (use recharge processes instead)
  • Payments to or from external organizations
  • Sponsored project or grant transfers (handled through RED)
  • Payments normally processed through Procurement, PCard, or Concur Travel & Expense

Who Initiates the IOC?

The UC campus receiving the financial credit must initiate the IOC. For example:

  • If UCR provides services and will receive revenue → UCR initiates the IOC
  • If UCR is being reimbursed by another UC campus → UCR initiates the IOC
  • If UCR is paying another UC for goods or services → the other UC campus initiates the IOC

Information Required for IOC Submission

Category
Details Required
UCR Initiator Name, phone number, optional IOC Number for departmental tracking, and the date the IOC is needed (only after all goods/services have been fully provided).
Other UC Campus Contact Campus name, department, contact name, phone number, email address, and any notes needed for processing.
Other UC COA Segments The other UC campus must provide its full COA, including required Entity and any campus-specific segments required by their Accounting Office.
Description Limited to 30 characters or fewer; this text is copied directly into the Oracle Journal Line Description field.
Amount Details Can be submitted as a lump sum or itemized. Optional fields include quantity, unit price, and reference/invoice number.
UCR COA to Credit Full COA including Entity, Fund, Activity, Account, Function, Program, Project, Flex 1, and Flex 2. Defaults must be used where applicable (e.g., Project = “0000000000”).

IOC Transaction Types

1. Goods or Services Provided to Another UC Campus

The IOC must credit:

  • A Sales & Service Educ (1200C) fund starting with “6” (excluding 60600–60660), OR
  • An Other Unrestricted Fund (1300C) using account 775000 (recharge revenue)

2. Reimbursements from Another UC Campus

  • The IOC must credit the exact COA originally charged for the expense
  • Must include the full account number

Best Practices for Successful IOC Processing

  • Ensure all services or goods have been delivered before submitting an IOC
  • Verify the other UC campus provides correct COA segments and full contact information
  • Use concise and meaningful 30-character descriptions
  • Double-check all UCR COA segments to avoid delays
  • Include any internal departmental approvals, if required
  • Maintain a departmental log using the optional IOC Number

Submitting the IOC

The completed Intercampus Order/Charge Form should be emailed to: ioc@ucr.edu

Accounting will:

  • Review the form for completeness
  • Verify COA accuracy
  • Contact the other UC campus if additional information is required
  • Process the IOC in Oracle Financials following UC systemwide interlocation accounting guidelines