1 / 18

Common Government-wide Accounting Classification (CGAC) Structure

Common Government-wide Accounting Classification (CGAC) Structure. Dianne Copeland NoVA Chapter AGA December 5, 2007. Agenda. Why CGAC is needed Desired outcomes The CGAC elements Next steps. Several sources touch on accounting classification. Treasury FMS

Download Presentation

Common Government-wide Accounting Classification (CGAC) Structure

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Common Government-wide Accounting Classification (CGAC) Structure Dianne Copeland NoVA Chapter AGA December 5, 2007

  2. Agenda • Why CGAC is needed • Desired outcomes • The CGAC elements • Next steps

  3. Several sources touch on accounting classification • Treasury FMS • Treasury Financial Manual – Central Accounting & Reporting • U.S. Standard General Ledger • OMB • Circular A-136 – PAR, CFS • Circular A-11 • Circular A-127 – Financial Management Systems • FSIO • Framework for Federal Financial Management Systems • Federal Financial Management System Requirements • Core Financial System Requirements

  4. Starting point for CGACCore Financial System Requirement (SMA-01): • Accounting classification—Maintain an accounting classification structure that includes the following elements: • Treasury Account Symbol • Budget fiscal year • Internal fund code • Organization • Program • Project • Activity • Cost center • Object class • Revenue source • Budget function • Budget sub-function code • Accounting period. • Maintain each classification element independently. For example, budget fiscal year must be maintained as a separate value from the period of availability component in the TAFS.

  5. These sources provide agencies considerable latitude • Agencies that have similar fields call them by different names, or use different logic to drive similar business rules. • Software implemented in each agency becomes a unique implementation, increasing risk and cost.

  6. Flexibility resulted in different structures at each agency

  7. Purpose of CGAC project Project Description: Develop a common government accounting code structure, including an applicable set of definitions, which all federal agencies will adopt. • Develop a standard structure • Accommodate both standard government-wide and critical agency-mission-specific accounting data • Validate it with the financial management community

  8. Desired outcomes from implementing CGAC • Short term • Promote a universal understanding of data elements • Increase awareness of best practices for handling complex classification elements – Relationship/FX • Help agencies standardize accounting codes internally • Longer term • Aid in the evolution of standardizing financial management throughout the federal government • Increase opportunities for a “baseline” software product configuration – Uniform configuration • Reduce the effort required to implement a new financial management system • Increase the likelihood that the system configurations of an SSPs will fit all customers • Ease the transition when an agency moves to a new SSP • Aid in the aggregation and comparison of data across the government • Establish the accounting classification elements needed on information exchanged between core financial management systems and other agency systems

  9. Approach • Obtained concurrence on definition and format for every element • Initiated efforts to align data with multiple sources, particularly to align a number of different sources for agency codes • Encouraged central agencies to begin eliminating disparities within their systems

  10. Universe of elements

  11. FundCategory

  12. Organization Category

  13. Program Category

  14. General Accounting Category

  15. Critical Agency Mission-Specific and Future Use Category

  16. Cost Category

  17. Next Steps • FMLoB • Work with OMB, Treasury and Agencies to develop sequencing Plan • Agency • Gain an understanding of the CGAC structure, and begin to adopt standard terminology and definitions; • Identify and inventory the systems which will be affected by the CGAC structure; • Begin analyzing the gap between existing accounting classification structures and the CGAC structure; • For system implementation projects (in process) that have not yet finalized the classification structure, use the CGAC structure as a framework to the extent possible.

  18. Contact Information • CGAC Structure available at • FSIO Website: www.fsio.gov • Questions: fsio@gsa.gov • Dianne E. Copeland • FSIO DirectorGeneral Services AdministrationOffice: 202-219-0550    Fax: 202 219-0549 • E-Mail: dianne.copeland@gsa.gov

More Related