Core Recurring Budget & Allocations from Campus Budget Office (CBO)


The Core Recurring Budget is the recurring approved annualized plan of operations for the university. It is adjusted during the annual budget process to reflect changes with continuing impact. Typically, only core funds have core recurring budgets. The core recurring budget was previously called the permanent budget. 

The focus of this article is to:

  • direct Oracle Financials Cloud (OFC) General Ledger (GL) report users to the CBO recurring allocation budget and actuals line items within the UCSD Budget vs Actual Report 
  • understand why the figures in the Budget and Actuals columns might differ from one another 
  • show the user how to isolate the account code 779400 – CBO Recurring Allocation within the UCSD Budget vs Actual Report which is the account code used for the monthly transfer of core recurring resources  


Q: Where can I find my core funds budget?

A: Access the UCSD Budget vs Actual Report (KB0032643) to view your core budget. To run the report for core funds only refer to KB0032643 Step #6. Once the report is generated, the total core budget can be seen in the Budget column. The Total core budget shown may include not only the recurring core budget but planned one-time resources expected as well. All budget plans loaded to OFC GL were derived from the Oracle Planning and Budgeting module.

Budget vs Actual Report Core Funds

Q: Where can I find my core recurring resource allocation? 

A: Access the UCSD Budget vs Actual Report (KB0032643) and follow step #6 to display the core funds budget only. The core resource allocations are located under the Internal Resources section of the report rows within the “CORERT – Core Resource Allocations” category. Drill into the category by clicking on the expansion triangle icon. This expansion will display all transfer account codes with planned budget and actuals grouped to this category. Locate the account code 774900 – CBO Recurring Allocation line and Actual column of the report. This intersection represents your core recurring allocation for the selected time period of the report.  

Budget vs Actual Report Core Recurring Resource Allocation Line

Q: Why does the figure in the 774900 - CBO recurring allocation Budget column differ from the figure in the Actual column when I run the report? 

The CBO recurring allocation actuals might not always align with the budget plan within account code 774900.  There are a few factors in combination to consider when comparing the CBO recurring allocation actuals to the recurring budget plan.

A: Monthly budget load versus equal 1/12th monthly core recurring resource transfers. The budget in OFC GL is loaded from Oracle Planning and Budgeting module as a monthly plan from which monthly variations can arise from the position budgeting process. While the budget is represented as a monthly plan, core recurring allocations are designed to smooth out any variation across months, resulting in a consistent monthly 1/12th allocation of the annual core recurring budget. When running the UCSD Budget vs Actual Report using any time period other than the full fiscal year Jul-20 through Jun-21, the budget plan versus actual core allocations could differ due to this variation of monthly budget spread vs equal 1/12th of the annual recurring budget allocation.  

As an example, within the Oracle Planning and Budgeting position budgeting module, variations to start and end dates for a position(s) may have varied from a standard fiscal year period of July 1 – June 30. For example: x position had a start date of January 1st and end date of June 30th. This would result in the monthly recurring budget during the months of July – December being lower than the second half of the fiscal year 21 (January-June). Subsequently monthly recurring resource transfers are based on 1/12th if the annual core recurring budget. This can cause mis-alignment of the budget and actual column.  

B: Compensation salary program and benfit rates. Incremental changes to core recurring budgets tied to compensation increases not yet finalized are not part of a unit base budget and for that reason are not funded as part of the base recurring allocations. For planning purposes, the Oracle Planning and Budgeting module calculates projected increases in expenditures due to salary program increases and projected expenditure changes due to benefit rate changes.  Both program increases and composite benefit rates used in the system are the best preliminary figures known at the time. These planning figures require approval from outside agencies like the UC Office of the President or Federal Cost Allocation Services. This makes the rates subject to change.  As part of the process these are held back during the allocation process, and funded when they are final through the compensation allocation process.

If you still have questions or need additional assistance, please submit a ticket