Frequently Asked Questions

Find answers to common questions about Aggie Enterprise, including Chart of Accounts and Common Operating Fund Initiative, collected and shared below.

Aggie Enterprise 

About the Project

  • What is Aggie Enterprise?
  • Aggie Enterprise is a strategic business transformation initiative. This multi-year initiative encompasses the Common Operating Fund Initiative (COFI), the Chart of Accounts project (CoA), and the implementation of the new Oracle system, including business process and boundary systems review and redesign. Aggie Enterprise is also the name of the UC Davis implementation of Oracle Cloud Financials, which will go live July 1, 2023.

    This initiative marks a culture shift in our approach to launching a new system: Adopting an Out-of-the-Box System: Configuration over Customization

    > Configuration: As it relates to this project, configuration refers to optimizing our use of Oracle Cloud Services by reviewing, analyzing and updating current business processes. Contrary to the past practice of customizing a system to meet us where we are, we will instead realign our processes with industry best practices embedded in Oracle, making the best use of the system.
    > Customization: As it relates to this project, customization refers to the past practice of making complex system customizations to meet existing business processes. These customizations may not leverage best practices, and often result in system maintenance challenges, including significant manual work to keep systems updated. This project will mark a cultural shift in moving away from customization to configuration.
  • Why are we replacing our financial systems?
  • Our current financial systems have struggled to keep up with the growing complexity of the University’s financial landscape, planning and business needs. The customizations we have made in the past have created challenges around systems maintenance and updates. Additionally, Kuali is moving to a SaaS (software as a service) product, so our current system is not going to be supported going forward. 

    In order to achieve increased efficiency, streamline business processes, provide effective reporting, and meet regulatory requirements, UC Davis has decided to implement Oracle Cloud Financials.  When we looked at the capabilities of the Oracle Cloud versus Kuali cloud system, Kuali is years out from being able to deliver a solution that Oracle delivers today.

    The implementation of a modern, integrated financial system will deliver functionality that is currently distributed across multiple systems, providing UC Davis with one reliable, accessible source of truth for financial transactions, business process execution and reporting.

    The adoption of the new system will support a culture of innovation, efficiency, transparency, and data-driven decisions as we ‘Boldly Go’ into the future.

  • What is Oracle Cloud?
  • Oracle Cloud supports finance, financial project management, procurement, budget, and post-award research administration activities, among others, through a software as a service (SaaS) model. It is a modern, agile suite of integrated applications, which undergo periodic updates automatically to improve functionality.

  • I heard that there are consultants working on Aggie Enterprise. Who are they and what are they doing?
  • UC Davis has partnered with Deloitte to share co-responsibility for the implementation of Oracle at UC Davis. Deloitte is helping to provide functional and technical expertise for the implementation and integration of the new system, providing guidance on leading industry practices, sequence duration and key activities, as well as supporting the development of training and implementation schedules.

    UC Davis will maintain overall responsibility and authority for driving decisions, communications and securing required resources. The qualified, knowledgeable members of our project team, supported by engagement with our stakeholders, will lead the transformation of business processes.
  • How will stakeholders be involved in Aggie Enterprise?
  • Stakeholder engagement is crucial to the success of Aggie Enterprise, and collaboration with stakeholders is a key element of both our project and change management planning.

    Work stream and process design leads will bring together subject matter experts (SMEs) from across UC Davis to provide feedback around specific aspects of finance, budget, procurement, business operations and boundary applications.

    The Aggie Enterprise initiative also includes designated stakeholder groups with specific roles and responsibilities throughout the project’s lifecycle:
    > The Aggie Enterprise Advisory Board, led by our Academic Liaison, and comprised of stakeholder representatives from across the campus. Their role is to provide feedback on the overall strategic direction, business process changes and configuration, with a special focus on the impact to academic departments.
    > The Change Network, led by our Change, Communications and Training (CCT) team, brings together individuals from colleges, schools and units from campus, Health and ANR. Members of the Change Network will be our change champions, building awareness by facilitating cascading communications, advocating for the change, and serving as a liaison between their colleagues and the project team.
  • How does this benefit UC Davis?
  • The Aggie Enterprise initiative will align UC Davis with leading industry practices and replace outdated legacy systems with new, more robust technology, providing the infrastructure to deliver high-value, reliable, and easy-to-access financial, planning and business services.

    Aggie Enterprise benefits include:
    > UC Davis will have one reliable, accessible source of truth for financial transactions, business process execution, and reporting; this reduces risk associated with data integrity, compliance, and information security.
    > Consistent, standardized business processes, coupled with the structure provided by the new Chart of Accounts, will bolster cross-functional collaboration and increase transparency.
    > More robust and complete reporting functionality will reduce the need for manual data manipulation and enable informed, data-driven decision-making
    > Flexible and scalable to meet our financial needs as UC Davis continues to grow in size and complexity.
     

  • What are the plans for training?
  • Training starts by providing you relevant and timely information throughout the lifecycle of Aggie Enterprise. We aim to provide UC Davis with robust communication and change management activities in order to promote user confidence and adoption well before the new Aggie Enterprise system goes live in July 2023.

    We are dedicated to gathering change impacts – the difference between what each of the stakeholder groups do or see today, and what the future will be. We will work to validate those change impacts to refine and inform end-user training. As we near the go-live date, we will roll out job aids, quick reference guides, online and classroom training sessions and opportunities to drop in for an Open Lab to experience the system first hand. Aggie Enterprise Team members and Deloitte partners will provide end-user support - also known as hypercare - in the months immediately following go-live, to troubleshoot issues and assist units in fully adopting the system. 

    For now, stay informed about the project by signing up for The Spreadsheet newsletter, visiting the website often and watching for opportunities to engage in Town Halls, planned for the future. We also invite you to email your questions to us at aggieenterprise@ucdavis.edu.

Timeline and Scope

  • What is the schedule for Aggie Enterprise?
  • The Aggie Enterprise initiative kicked off in April 2021, and is slated for launch in July 2023. High-level details of the project phases are included in the Project Phases.
  • Why is go-live scheduled for July 2023?
  • All UC campuses and medical centers have been tasked with aligning their chart of accounts with the UCOP Common Chart of Accounts by July 2023. Implementing Oracle at the same time as the new Chart of Accounts allows us to make the most of the system configuration, while also avoiding costly rework. Going live at fiscal-close also provides a clean break from the old to new system.
  • Will there be a pilot?
  • No. We are targeting one rollout. No groups will get the system before others.
  • When will I be able to see a demo of Oracle Cloud Financials?  Can I see what the system looks like at UC Merced or UC San Diego?
  • The configuration of the Aggie Enterprise implementation of Oracle Cloud Financials will require a thorough review of our business processes and boundary applications in order to make key design decisions. 

    Oracle implementation is different for each campus because of the many configuration options, so viewing another campus' instance will not provide an accurate depiction of how the UC Davis Oracle environment will work.  In order to provide users with the most accurate view of the system and minimize retraining, we anticipate users will not interact with the system until mid-2022. 

    In the meantime, stakeholders will be engaged in the Chart of Accounts (CoA) project, the Common Operating Fund Initiative (COFI), boundary application discussions, and process redesign sessions. Additionally, our Advisory Board and Change Network will support cascading communications across UC Davis. All of which will build knowledge in preparation for training in the new system. 
  • What is in scope for the Aggie Enterprise initiative?
  • Aggie Enterprise encompasses the Common Operating Fund Initiative (COFI), the Chart of Accounts project (CoA), and the implementation of the new Oracle system, including business process and boundary applications review and redesign.
    All elements of the Aggie Enterprise initiative are supported by an integrated Project Management and Change Management strategy.

Future State System and Data

  • Which existing systems are going away, and when will this happen?
  • The project team is actively compiling and assessing all systems across UC Davis. Systems are being assessed based on their functionality, as well as any upstream or downstream integrations with Kuali. Any boundary application that feeds financial data into KFS or receives financial data from KFS will need to be reviewed and adapted to the Chart of Accounts and to interface with Oracle, as applicable.

    Some of our current systems will no longer be needed to support UC Davis financial and business processes after the implementation of Oracle Cloud services. Our initial inventory has identified some of the systems that will be made redundant by the Aggie Enterprise initiative.

    Conversely, some of our current systems will still be required for other functions that the Aggie Enterprise system cannot accommodate. We will work closely with departments and system owners to determine which systems will be kept and which will not be retained.
  • Why do we need new system integrations?
  • The existing integrations to the financial system are based on the legacy system requirements. These cannot be translated to the new Oracle Cloud services and, therefore, are being evaluated on a case-by-case basis to determine the required future integrations.
  • What is refactoring?
  • Refactoring describes the effort required to ensure that the UC Davis systems we retain can continue to function with Oracle Cloud Financials. Specifically, this refactoring effort will include modifying systems that currently hold Full Accounting Unit (FAU) values or segments. Today’s FAU values and segments will need to be replaced with future-state Chart of Accounts (CoA) values and segments.
  • Will we have all our current data in the new system when we go live?
  • The data in the new financial system will be determined by our Conversion and Cutover strategy. All current financial data sources will undergo a thorough review and data clean-up effort to ensure that the new system is populated with relevant data. More information related to the scope of data to be converted will be shared as the strategy and plans are finalized.
  • How will we access historical data? How will we be able to compare and map new data to historical data?
  • Historical data will be available when Aggie Enterprise goes live, but the range of data and the system location is still to be determined.

    The implementation of our new Chart of Accounts will require complex data translation between our current FAU and the new CoA segment values.  We are working with Deloitte to determine the tools which will be available for departments to crosswalk the new CoA with the KFS string.

    Our current FAU includes embedded data within each segment, whereas the new Chart of Accounts will have distinct segments for these data elements; these translations may be many-to-one.
  • I heard that Oracle Cloud Services uses subledgers. What is a subledger? What are the benefits of using a system with subledgers?
  • A subledger is a low-level ledger that captures detailed transactional information to substantiate the monetary values stored in the general ledger. Examples of this detailed information include:
    > Supplier invoice numbers
    > Customer payment types
    > Asset acquisitions information (i.e. purchase date, purchase amount)

    In Oracle, the detailed activity within the subledger system then posts to the general ledger at a more summary level through an automated process, the subledger accounting engine. 

    Using a system with subledgers has several benefits:
       > Subledgers provide functionality to deep dive into the GL data, allowing reporting on detailed transactional information, making the data more
          meaningful
       > Subledgers make financial reporting from the general ledger more efficient because the data is already summarized at a general level

Send your question to the project team


Chart of Accounts

  • What is the Chart of Accounts? What’s changing?
  • The Chart of Accounts, or CoA, is the basic structure that UC Davis uses to record and organize financial transactions to facilitate financial reporting. The future state Chart of Accounts will:
    > Replace the Full Accounting Unit (FAU) structure.
    > Organize UC Davis finances by separating assets, liabilities, net position, expenses and revenues to provide a clear understanding of the university’s financial status. 
    > Organize and report data out of the financial system.
    > Support financial and management reporting by serving as the basis for the fiscal administration of UC Davis funds, programs, projects, organizations and activities.
    > Serve as the common language for financial transactions whether they are created directly in the financial system, generated in another major university system, or created through a local third-party application. However, it may not support the detailed fiscal tracking of all institutional activities. Some detailed information currently stored in the FAU will instead be captured within other modules or functionality of the new financial system. 
  • Why does UC Davis need a new Chart of Accounts?
  • The new Chart of Accounts (CoA) will align with the new UC Common Chart of Accounts (CCoA) mandated by UC Office of the President.

    Redesigning the Chart of Accounts will help resolve many of the financial management and reporting challenges faced by UC Davis today.

    Full Accounting Unit (FAU) values are used inconsistently across UC Davis. The segments within the new CoA will be strictly defined and administered to maintain institutional integrity. 

    The new CoA will serve as the foundation of a new Oracle Cloud Financials implementation, Aggie Enterprise. Implementing these two efforts - the new CoA and the new system - concurrently, allows us to maximize system configuration and functionality while avoiding costly rework in the future. 

    Watch our sponsor video to learn more. 
  • How did we arrive at the Chart of Accounts structure?
  • The Chart of Accounts (CoA) structure is based on the UC Common Chart of Accounts (CCoA), developed and approved by the UC Office of the President in 2014.

    To arrive at the final CoA structure for UC Davis, the Chart of Accounts project team deployed a phased approach to engage with stakeholders and subject matter experts (SMEs):
         > Discovery: Information and requirements gathering sessions with units across UC Davis
         > Proof of Concept: Scenario demonstration and validation of prototype CoA
         > CoA Advisory Group: Meetings with SMEs from across UC Davis who provided feedback on key design decisions and critical UC Davis specific 
             requirements

    In addition to stakeholder feedback, the segment design and definitions were vetted against leading industry practices and lessons learned from other higher ed institutions, including UC San Diego and UC Merced.

    As the foundation of the Aggie Enterprise system, our final Chart of Accounts structure was designed to make the most of Oracle Cloud Financials configuration and functionality.
  • Who is impacted by the new Chart of Accounts?
  • The new Chart of Accounts will impact everyone who submits financial transactions in Kuali.
    Additional systems that will be impacted include:
    > AggieBuy
    > Banner
    > CASHNet
  • Why are there so many chart segments in the new Chart of Accounts?
  • The use of eleven chart segments allows greater flexibility in how we use the Chart of Accounts to support our business and reporting needs.
       > The Entity, Fund, Financial Department, (Natural) Account, Purpose, Program, and Project segments are aligned with the UCOP Common Chart of
           Accounts.
       >  The Activity segment was added for UC Davis business and reporting requirements, informed by our stakeholder outreach.
       >  The Inter-Entity segment is a system-generated segment used to support balancing functionality in Oracle.
       >  Two Future segments are designated for future use by UCOP, as needed.

    Each segment has a single use with a clear and consistent definition, and use criteria.  When combined, these segments will tell the unique story of each individual transaction.

    The new Chart of Accounts maximizes the concept of a matrix-type chart by reducing duplicate values and allowing the use of common values across multiple units.
  • Are all segments required?
  • All segments will require a value in Oracle, but not all of those values require entry by transactors.

    Segments that require transactor entry include:
       > Entity
       > Fund
       > Financial Department
       > (Natural) Account)

    Segments that are conditionally required include:
       > Purpose (required for expense transactions only)
       > Program (required for transactions associated with UCOP and UC Davis sanctioned programs)
    These segments will populate with a system-generated default value when no value is entered.

    Segments that are optional for transactor entry include:
       > Project**
       > Activity
    These segments will populate with a system-generated default value when no value is entered.

    System-generated segments include:
       > Inter-Entity
       > Future 1 (unless and until a use is defined by UCOP)
       > Future 2 (unless and until a use is defined by UCOP)

    ** Transactions related to a contract, grant, capital, Faculty project or other PPM designated project will require processing in the PPM module, which will populate a Project segment value.  We will share additional information on the PPM module as the project progresses.
  • Currently, UC Davis uses several charts (3,L,S,H,M,P, etc.). Will we continue to use multiple charts of accounts?
  • The current chart structure will be changing, so the information we currently think of as “charts” will now be built into the “entity” segment. "Entity" will delineate operational units with their own Federal Tax Payer Identification number, including UC Davis Campus, UC Davis Medical Center, Agriculture and Natural Resources (ANR), UC Davis Foundation, etc.
  • Will assignment of Principal Investigator (PI) still be a component/attribute of the Chart of Accounts?
  • The Chart of Accounts project team will be listening and recording the needs and requirements of groups across UC Davis. Those needs will be assessed to determine whether they are best met in the chart of accounts design or through the delivered functionality of the finance system.

    In the case of Principal Investigator, tracking and management of that attribute will likely be met through the system, rather than as a component of the new chart.
  • Will the existing chart cleanup be part of the Chart of Accounts mapping project, or a separate work stream?
  • There will be two separate work streams, though there may be potential overlap between the two.

    The work stream for data cleanup will include departments evaluating their existing data for:
    > Confirmation of accurate account balances
    > Accounts that may be appropriate to deactivate due to lack of use
    > Opportunities to close out accounts with small balances

    Additionally, there will be a mapping work stream where the Chart of Accounts (CoA) project team will engage with departments to:
    > Understand the current use of chart elements to ensure accurate translation from the legacy CoA to the future CoA
    > Validate that mapping rules are correct once we move data into the future chart
    > Develop crosswalk tables to aid departments in identifying mapping of the legacy CoA to the future CoA
  • Is there consideration to how we will look at historical data under the current Chart of Accounts compared to the new Chart of Accounts going forward?
  • The Chart of Accounts project team will be mapping historical data into the future chart structure, so there will be the ability to compare historical data to future data. However, this will be a very different structure for chart of accounts, so it may be more complex than a one-to-one translation.

    The mapping work stream includes engaging with departments to understand how the current chart elements are being used in order to make the mapping of historical data to the future chart as accurate as possible.

    Maintenance and access of detailed historical data is still to be determined.
  • How will Chart of Accounts values be determined?
  • Value Development starts with considering the UCOP Common Chart of Accounts, which has defined certain levels and values that are commonly used across all UC campuses.  The CoA team will begin with an analysis of existing FAU values against the UCOP Common Chart of Accounts value requirements and hierarchy.  This review will include identifying potential gaps, as well as opportunities for value consolidation and data cleanup.  

    From that analysis, the CoA team will develop baseline values, which will focus on mostly shared, or common, values to be used across UC Davis.  These baseline values will account for approximately 80% of the total values for the new Chart of Accounts.

    Once baseline values have been developed, the CoA team will reach out to units across UC Davis to validate baseline values and deep-dive into the remaining 20% of values needed to address individual department business requirements.

    Additionally, the Aggie Enterprise project team is developing a process for units to request new values post "Go Live".  The Aggie Enterprise Advisory Board and Change Network will provide feedback and support cascading communications as decisions are made.

  • Can we utilize a segment in the new Chart of Accounts to display historical KFS values (i.e. the KFS Account number) to help us map new transactions to historical data?
  • The new Chart of Accounts will not contain any KFS values.  With such varied use of KFS segments across UC Davis, and the embedded attributes in the KFS FAU, it will not be possible to have a meaningful link between a single KFS value and the new matrix-style Chart of Accounts.

    The CoA team recognizes the need to be able to crosswalk between legacy KFS data and Oracle.  We are researching the various mapping tools that can be utilized to address that need.

    When a solution has been identified, we will share it with stakeholders.
  • How will Chart of Account values be managed?  Can departments create their own values for the various segments?
  • Given the complexities of Oracle, the new Chart of Accounts values will be centrally managed under the guidance of a new Data Governance Policy.  This central administration of the Chart of Accounts will ensure segments are being used consistently across the campus and provide for more accurate financial reporting.

    The Aggie Enterprise team is working on a process, approval structure, criteria, and service level agreements for units to request new values.  Governance levels for each segment will be defined separately. 

    The Aggie Enterprise Advisory Board and Change Network will provide feedback and support cascading communications as decisions are made.    

  • How will the Chart of Accounts effort interface with the new accounting system planning? How might this impact CoA design, including character limitations, coding requirements and any aspects of the elements themselves that have been pre-defined by the UC Office of the President?
  • Our future state Chart of Accounts (CoA) has been designed and developed to meet our local needs within the parameters of the UC Office of the President's delivered structure, the Common Chart of Accounts (CCoA). The actual character values are, at some level, determined by UCOP for reporting across the UC system.

    Like UCOP, UC Davis will be implementing Oracle Cloud, so the character elements and numbering system structure will be similar. For segment values unique to UC Davis, we will keep flexibility and scalability in mind as we design segment lengths to accommodate future growth. 

    The new CoA will also serve as the foundation of the new Oracle Cloud Financials implementation, Aggie Enterprise.  Implementing these two efforts - the new CoA and the new system - concurrently, allows us to maximize system configuration and functionality while avoiding costly rework in the future.

Send your question to the project team


Common Operating Fund Initiative

  • What is COFI?
  • UC Davis is implementing the Common Operating Fund Initiative (COFI), an effort to reduce the complexity in management of unrestricted campus resources both centrally and in units. COFI is designed to simplify our campus accounting and reporting processes by allocating most Central Campus funding from a single common fund.

    COFI represents a simplification of  campus funding streams; it does not result in budget reductions, change budget decisions, or change budget allocation methodologies. COFI does not include funds with externally imposed restrictions, such as contracts and grants, clinical trials, or private gifts and endowment earnings.

  • How does COFI benefit UC Davis?
  • By allocating central resources from a single fund, COFI will help simplify campus accounting and reporting processes.

    Benefits include:
    >Simplicity: Easier to use and transfer funds within and across units (greatly reducing or eliminating the need for fund swaps)
    >Strategic spend: using the "first dollar principle" ensures full expense of General and Tuition funds in support of the academic mission
    >Flexible and responsive to external requirements: COFI relieves units of specific fund restrictions; central campus will make fund-specific information at an aggregate level by mapping expenditures back to appropriate fund sources.

    Additionally, the time and effort invested in COFI will help prepare the campus to transition to a new Chart of Accounts. 
  • What is being done now to prepare for COFI?
  • The COFI project team is currently engaged in design and testing activities to understand the technical and business impacts to campus units and central campus.  Over the next several months, the COFI team will be available to work with units to review how this new process might influence each unit’s account structure and how it fits into the larger Common Chart of Accounts project.  They will also coordinate with UCPath, Finance and other stakeholders to minimize disruption to ongoing operations and required reporting activity. Starting September 2021, conversion of unit accounts and UCPath distributions will be done in three waves, with COFI fully implemented by December 2021.

  • Can we still use the Higher Education Function Code (HEFC) to identify AES funds, that are also 19900?
  • The HEFC will not change and you will still be able to use it to identify AES funds, that are also 19900.

  • Will self-supporting funds be included in COFI?
  • No, self-supporting funds are not included in the COFI model.
  • Will campus-based fees be included in COFI?
  • No, campus-based fees have specific restrictions and will not be included in the COFI model.

  • Will Student Services Fees be included in COFI?
  • No, student service fees will not be included under COFI. 

  • Some units fund benefits for faculty and staff on 19900 for the academic units, running quarterly reports based on actual expenses and then transferring budget to the academic departments. How does COFI affect this process?
  • The COFI project team can work with individual units to identify options.

  • How will we know when our unit is scheduled for COFI implementation?
  • The COFI project team has developed the schedule for implementation and will work with each unit to address various business needs and timing issues.

  • Does this mean we no longer have to track the carryforward funds by dean's office, department and faculty for 19900?
  • We likely will ask units to continue this practice for COFI fund balances. We will continue to review, and will update units as appropriate.

  • Will funding of academic salary and benefits increases be affected by COFI?
  • The process for funding academic salary and benefits increases will go unchanged as that is determined by title and not funding source.
  • How will the block grant funding for staff salary and benefits increases be handled in COFI?
  • We haven’t fully determined the process for this yet, but we believe the transition to COFI will have a minor (positive) impact on unit funding. The block grant funding for staff salary increases will be based, as it has been the past 2 budget cycles, on the salary increases of core-funded career staff eligible to receive a salary increase through any systemwide salary programs or negotiated agreements. However, as these core funds will be converted to the COFI model this year, we will base the block grant calculation instead on eligible staff paid on the COFI fund (99100). There are a few more funds included in the COFI model than in our current definition of “core” funds, so it will slightly expand the pool of eligible salaries for some units. We have done some preliminary analysis of this and believe it to be the best option, but a final decision has not yet been made.  
  • Will COFI include charts H or L?
  • No. COFI will be limited to Charts 3 and S only.
  • What if my unit wants to transfer funds to a different unit during the COFI conversion and we’re in different implementation groups (waves)?
  • It would be preferable during the conversion process for units to delay any inter-unit budget transfers until both units have converted to COFI. If a critical need arises, units can work with BIA to do essentially a fund swap. This request should be channeled to BIA through the respective Dean/VC Office. The sending unit would transfer COFI funds to BIA, and BIA in turn would transfer that amount to the recipient unit in an appropriate legacy fund (or vice versa).  
  • Why isn’t fund xxxxx included in COFI?
  • The COFI model is limited to funds that are more or less discretionary/unrestricted and centrally managed by campus. For that reason, it excludes:
    > Funds that are neither received in nor allocated by central campus (Finance/BIA)
    > Funds with restrictions imposed by entities external to the UC, such as specific state programs, contracts and grants, private gifts, and endowment earnings
    > Funds for the UCD medical center, auxiliaries, student fees and self-supporting programs
  • How do I handle X’ and y funding?
  • Units with x’ and y salary components will not be prohibited from charging the salary components to the COFI fund, since there are no restrictions. Central campus will use the Earn Code associated with these payments to properly allocate the corresponding expense to the appropriate legacy fund.
  • How will COFI affect my AggieBudget reports?
  • Data converted to COFI in the KFS test environment was imported to the AggieBudget test environment to determine how it would impact reporting. No problems or errors were detected, but changes to the reporting format were required. A new fund category for COFI was created “1300 – Common Operating Fund.” The COFI fund category is available as a filterable attribute in any report with fund category filters. The S&U reports (1YR,3YR,5YR) have been updated so they will display COFI in its own column (instead of lumping it in with the miscellaneous fund category column). The Carryforward balance report is also being updated to show COFI on its own. AggieBudget always displays past actuals in the current org hierarchy and current account fund assignments.
  • I get an error message about Account Assessment Types (Self-Support Accounts) when I submit a COFI-related Account doc in KFS. How do I resolve this so I can submit the doc? 
  • This error is a function of the COFI fund being in Sub Fund Group Type (SFGT) "M." Even though COFI fund accounts should not post income or recharge, Kuali requires that field for accounts associated with funds in the SFGT. Entering an assessment type NUDZ, CAIZ, or CARZ will allow you to proceed and complete the doc.
  • When transferring funds to/from another campus that is using a legacy fund (e.g., 19900), what fund should I use on the Intercampus Transfer Form (ITF)?
  • When transferring to other campuses, units should provide their 99100 account and the Campus Budget Office will be able to properly address the funding transfer to the other campus. When receiving a transfer from another campus, provide them with your KFS account and appropriate legacy fund (e.g., 19900). The Budget Office will be flagged when the ITF is received and will manually process it as COFI.

Send your question to the project team