The California Agency Chart of Accounts (CACOA) is a voluntary, standards-aligned accounting framework designed to address these challenges by providing a shared structural foundation for public-sector accounting—without requiring agencies to abandon local practices, systems, or professional judgment.

CACOA is not a mandate, not a software product, and not a replacement for GAAP.
It is a reference framework that enables:

•  - consistent classification of financial activity across agencies,

•  - scalable adoption for agencies of varying size and complexity,

•  - explicit alignment with California Financial Transaction Report (FTR) requirements for municipalities, and

•  - compatibility with a broad range of special districts and public agencies not governed by the California Department of Education (CDE).

• 
  

• CACOA is published under the MIT License, permitting free use, modification, and redistribution of the framework materials. The license does not apply to agency financial data or proprietary systems.

CACOA is intended for use by:

•  - Cities and municipalities

•  - Special districts (enterprise, governmental, fiduciary, and hybrid)

•  - Joint powers authorities (JPAs)

•  - Public agencies and authorities not subject to CDE/SACS requirements

While CACOA is designed to be broadly applicable, its explicit reporting alignment is limited as follows:

•  - FTR mapping and validation are targeted specifically to municipalities

•  - Non-municipal agencies may adopt CACOA structures without FTR mapping requirements

This distinction is intentional and reflects the differing statutory reporting obligations across California public agencies.

Key Principles

•  - CACOA does not establish recognition, measurement, or disclosure rules

•  - CACOA does not supersede professional judgment

•  - CACOA provides structural consistency to help agencies apply GASB standards more effectively

In other words:

 - GASB defines what must be reported.
 - CACOA provides a consistent way to organize and report it.

CACOA’s design reflects:

•  - fund accounting principles,

•  - measurement focus distinctions,

•  - legal and budgetary compliance realities, and

•  - common public-sector reporting structures.

CACOA recognizes that agencies post transactions differently due to:

•  - legacy systems,

•  - historical practice,

•  - operational needs, and

•  - staffing constraints.

Rather than forcing uniform posting behavior, CACOA prioritizes:

•  - consistent reporting outcomes

•  - transparent mapping

•  - diagnostic visibility

This allows agencies to achieve comparability without disrupting operations.

---

2. Object-Centric Structure

CACOA emphasizes standardized object classifications (assets, liabilities, equity, revenue, expenditures) as the primary driver of comparability.

This approach:

•  - mirrors successful elements of SACS object discipline,

•  - supports FTR line mapping for municipalities,

•  - allows flexibility in funds, departments, and functions.

• 
  

Objects provide the strongest anchor for statewide comparability while remaining intuitive to finance professionals.

---

3. Multi-Dimensional and Extensible

CACOA separates accounting dimensions into:

•  - Funds

•  - Objects

•  - Functions

•  - Departments

•  - Reporting relationships

This separation:

•  - prevents overloading single codes with multiple meanings,

•  - allows local extensions without breaking rollups,

•  - supports future analytics and automation.

• 
  

Reserved ranges are intentionally included to accommodate:

•  - agency-specific programs,

•  - enterprise complexity,

•  - regulatory nuance.

4. Support for Reporting Profiles

CACOA implements flexible reporting profiles: 

 - Municipal FTR 

 - Budget Development 

 - ACFR/CAFR  

 - Custom Management/Operational Dashboarding. 

Profiles define how accounts are grouped and presented for specific reporting purposes and are reusable and transferable across agencies.

Each profile emphasizes unique group-level analytics, dashboarding, cost center analysis, and benchmarking.

5. Transferability and Shared Reporting

Reporting profiles, rollups, custom SQL may be shared across agencies without requiring identical charts of accounts. This enables peer benchmarking, shared dashboards, and reusable reporting logic while preserving local control.

1. Minimal Adoption (Rollup-Only)

Description

•  - Retain existing chart of accounts

•  - Map local accounts to CACOA objects and categories

•  - Produce standardized reports without changing posting practices

Best For

•  - Small agencies

•  - Agencies in audit backlog

•  - Initial pilots

Benefits

•  - No operational disruption

•  - Immediate reporting improvements

•  - Low implementation cost

• 
  

2. Mapped (Hybrid) Adoption

Description

•  - Existing chart remains active

•  - New accounts follow CACOA where practical

•  - Legacy accounts mapped via rules

•  - Validation highlights unmapped or ambiguous items

Best For

•  - Mid-sized agencies

•  - Agencies preparing for system changes

•  - Agencies seeking gradual standardization

• 
  

3. Full Structural Adoption

Description

•  - CACOA becomes the primary chart

•  - Local detail implemented within reserved ranges

•  - Validation rules enforce consistency

•  - FTR reporting largely automated for municipalities

Best For

•  - Large cities

•  - New agencies

•  - ERP implementations

Event-Based Accounting

Some agencies track events (festivals, emergencies, special programs) as unique objects.

CACOA approach:

•  - Treats events as management or program dimensions, not object classes

•  - Recommends retaining standard expenditure objects

•  - Allows mapping and exception documentation where event-specific objects exist

• 
  

Development and Balance-Sheet-Driven Activity

Common examples include:

•  - developer deposits recorded as liabilities,

•  - reimbursements drawn down from balance sheet accounts,

•  - trust-like or pass-through arrangements.

CACOA approach:

•  - Recognizes these practices as potentially GAAP-compliant

•  - Supports explicit balance sheet object classes

•  - Uses documented exception handling rather than forced reclassification

•  - Preserves transparency for audit and reporting review

• 
  

FTR Alignment (Municipalities Only)

For cities and municipalities, CACOA includes:

•  - explicit object-to-FTR line mappings,

•  - validation rules for coverage,

•  - draft vs finalized reporting states,

•  - diagnostic views identifying unmapped activity.

For non-municipal agencies:

•  - CACOA structures remain valid

•  - FTR mapping is optional and not enforced

This distinction ensures relevance without overextension.

Workforce Mobility and Training

•  - Familiar structures across agencies

•  - Reduced onboarding time

•  - Transferable skills for staff

Recruitment and Retention

•  - Clear, professional accounting frameworks

•  - Reduced dependence on institutional memory

•  - Improved succession planning

Transparency and Public Trust

•  - Comparable reporting across agencies

•  - Improved interpretability for policymakers and the public

•  - Stronger foundation for open data initiatives

1.  - Practical for agencies of all sizes

2.  - Aligned with GASB principles

3.  - Explicit where statutory reporting applies

4.  - Flexible where professional judgment is required

CACOA does not seek to eliminate local nuance.
It seeks to make that nuance visible, understandable, and reportable within a shared framework.

Adoption can begin at any level and mature over time, allowing California public agencies to move toward greater consistency without sacrificing clarity or control.

1.1 Statutory Authority and Purpose of the FTR

The Financial Transactions Report (FTR) is authorized under California law and administered by the State Controller’s Office as the primary mechanism for collecting standardized financial data from California municipalities. The FTR is designed to support statewide fiscal monitoring, legislative analysis, intergovernmental comparisons, and public transparency.

Unlike audited financial statements, which focus on fair presentation in accordance with GAAP, the FTR emphasizes uniform classification and comparability. Its objective is not to replicate local financial statements, but to normalize financial activity across diverse accounting systems into a common analytical framework.

1.2 Intended Users and Uses of the FTR

FTR data is used by a broad range of stakeholders, including the Legislature, Department of Finance, bond analysts, researchers, journalists, and the general public. These users rely on consistent classification to evaluate fiscal trends, compare municipalities, and assess financial condition.

Because users do not have access to local charts of accounts or internal accounting policies, clarity and consistency in FTR classification are critical. CACOA is designed to preserve this consistency while allowing agencies to retain local flexibility.

1.3 Relationship to GASB and Audited Financial Statements

The FTR does not supersede GASB standards or replace audited financial statements. GASB standards govern recognition, measurement, and presentation for financial reporting, while the FTR governs classification for statewide data collection.

Differences between audited financial statements and FTR totals may arise due to timing, reclassification, or consolidation differences. CACOA explicitly supports reconciliation between local ledgers, audited statements, and FTR submissions by maintaining traceable mappings.

1.4 Structural Organization of the FTR

The FTR is organized around a small number of core dimensions: fund, revenue classification, expenditure function, expenditure object, other financing sources and uses, and balance sheet elements. Each dimension serves a distinct analytical purpose.

The FTR structure intentionally limits dimensional complexity to promote comparability. CACOA respects these constraints by applying additional analytical dimensions only at the reporting and management layers.

1.5 CACOA’s Alignment Philosophy

CACOA is designed as a translation and alignment framework rather than a prescriptive accounting system. Agencies are not required to abandon their existing charts of accounts to achieve FTR compliance.

Instead, CACOA provides standardized object definitions, fund structures, functional guidance, and rollup logic that can be applied to existing data. This approach lowers adoption barriers and supports incremental implementation.

1.6 Common Misconceptions About the FTR

A common misconception is that the FTR represents a full financial statement or audit substitute. In reality, the FTR is a statistical and analytical report that complements, but does not replace, audited financial reporting.

Another misconception is that agencies must restructure their accounting systems to match the FTR. CACOA demonstrates that alignment can be achieved through mapping and rollups without disrupting local operations.

1.7 Role of CACOA in Statewide Standardization

CACOA provides a consistent reference structure that can be adopted voluntarily across agencies. By aligning CACOA structures with the FTR, agencies gain a shared vocabulary for financial reporting, training, benchmarking, and system design.

Over time, consistent CACOA adoption can reduce the cost of onboarding staff, improve data quality, and enable more advanced statewide analysis without imposing mandates.

1.8 Citations and References

• California State Controller’s Office – Financial Transactions Report Instructions
• California Government Code Sections governing municipal reporting
• GASB Concepts Statement No. 1 – Objectives of Financial Reporting

2.1 The Fund as the Primary Accountability Unit

In governmental accounting, the fund is the primary unit of fiscal accountability. Each fund represents a self-balancing set of accounts established to demonstrate legal compliance, financial stewardship, and operational accountability.

The FTR is explicitly fund-centric. All revenues, expenditures, assets, liabilities, other financing sources and uses, and fund balances are reported within a fund context. There is no concept of cross-fund netting or functional fund balances in statutory reporting.

2.2 Statutory and Reporting Expectations in the FTR

The SCO’s FTR instructions require agencies to report financial activity by individual fund, using standardized fund groupings for statewide analysis. These groupings distinguish among governmental, proprietary, fiduciary, and other fund types.

The FTR does not prescribe how agencies must structure their internal fund numbering systems. Instead, it requires that reported data be classified consistently for comparability across jurisdictions.

2.3 CACOA Fund Coding Structure

CACOA adopts a three-digit base fund coding structure to balance simplicity with scalability. This structure accommodates common municipal fund types while allowing larger agencies to extend fund codes for additional granularity without breaking rollup logic.

CACOA fund codes are intentionally neutral with respect to internal system design. Agencies may retain legacy fund numbers while mapping them to CACOA fund identifiers for reporting.

2.4 Fund Rollups and Reporting Views

Fund rollups are a core CACOA concept. A rollup is a defined aggregation of multiple funds for a specific reporting purpose. Rollups do not alter legal fund accounting and do not replace individual fund reporting.

CACOA supports multiple concurrent rollups, such as governmental funds for FTR reporting, enterprise fund groupings for rate analysis, or management-defined groupings for budgeting.

2.5 When to Create a Separate Fund

A separate fund should be established when required by law, regulation, bond covenant, or when necessary to demonstrate accountability for restricted or committed resources.

Common triggers for separate funds include legally restricted revenues, voter-approved taxes, grant requirements, rate-based activities, or material fiduciary responsibilities.

2.6 Fund vs Function vs Department

Confusion among funds, functions, and departments is a common source of reporting error. Funds represent accountability for resources, functions represent the purpose of spending, and departments represent organizational responsibility.

CACOA explicitly discourages using functions or departments to simulate fund restrictions or fund balance segregation. Separate funds should be used when accountability requires it.

2.7 Real-World Examples

Example 1 – General Fund vs Special Revenue Fund:

A city receiving a voter-approved public safety sales tax should establish a special revenue fund if the proceeds are legally restricted. Recording the revenue in the General Fund with a public safety function does not provide adequate accountability for statutory reporting.

Example 2 – Enterprise Utility Funds:

Water and sewer operations are typically reported in separate enterprise funds. CACOA allows these funds to be grouped for FTR reporting while preserving individual fund integrity for rate-setting and bond compliance.

2.8 Common Errors and CACOA Diagnostics

Common errors include excessive fund proliferation, using departments to mimic funds, and inconsistent fund definitions across reporting periods. CACOA diagnostics identify unmapped funds, incomplete rollups, and inconsistencies prior to FTR submission.

2.9 Audit and Reconciliation Considerations

Auditors evaluate fund structure for consistency, legal compliance, and clarity. CACOA supports audit review by preserving traceability from individual fund activity to FTR rollups and audited financial statements.

2.10 Citations and References

• California State Controller’s Office – Financial Transactions Report Instructions
• GASB Statement No. 34 – Basic Financial Statements
• GASB Concepts Statement No. 1 – Objectives of Financial Reporting

3.1 Purpose and Scope of Revenue Reporting in the FTR

Revenue reporting in the FTR is designed to identify the source, legal character, and economic nature of inflows to a governmental entity. The FTR emphasizes comparability across jurisdictions by standardizing revenue classifications while allowing agencies to retain local detail internally.

Revenues are reported by fund and revenue classification. Functional classification is not applied to revenues in the FTR, reflecting the principle that revenues describe sources of financing rather than purposes of spending.

3.2 Relationship to GASB Revenue Recognition Standards

GASB standards govern when and how revenues are recognized, while the FTR governs how recognized revenues are classified for statewide reporting. GASB Statement No. 33 establishes the framework for recognizing nonexchange revenues, including taxes and intergovernmental revenues.

CACOA respects GASB recognition principles by separating recognition and measurement from classification. Revenue objects and rollups are applied at the reporting layer and do not alter GAAP-based accounting.

3.3 CACOA Revenue Object Structure and FTR Alignment

CACOA revenue objects are organized within the 3000–3999 range and mapped directly to FTR revenue lines. Objects distinguish among major categories such as taxes, licenses and permits, intergovernmental revenues, charges for services, fines and forfeitures, use of money and property, and other revenues.

This structure ensures deterministic rollups to FTR categories while allowing agencies to define additional local detail beneath standardized object classes.

3.4 General Revenues vs Program Revenues

GASB Statement No. 34 distinguishes between general revenues and program revenues for government-wide financial reporting. While the FTR does not require explicit identification of program revenues, understanding this distinction is critical for consistent reporting.

CACOA supports program revenue analysis through analytical linkages rather than functional revenue posting, preserving statutory compliance while enabling meaningful internal reporting.

3.5 Functional Revenue: Prohibition and Management Alternatives

Functional classification describes the purpose of expenditures and is not a statutory dimension for revenue reporting. Assigning revenues to functions can obscure legal restrictions and distort fund-level accountability.

CACOA prohibits functional revenue classification in the FTR profile. Agencies seeking functional revenue analysis for management purposes should use program codes, grant identifiers, or reporting views rather than ledger postings.

3.6 When to Use Separate Funds for Revenue Accountability

Separate funds should be used when revenues are legally restricted, voter-approved, rate-based, or otherwise require discrete accountability. Using functional revenue coding as a substitute for separate funds is discouraged.

CACOA provides guidance for identifying when fund segregation is appropriate and supports rollups to maintain comparability without sacrificing accountability.

3.7 Real-World Examples

Example 1 – Property Tax Revenue (General Fund):

Property tax revenues are recorded in the General Fund using the appropriate revenue object. No functional classification is applied. Expenditures funded by property taxes are later reported by function in the expenditure section of the FTR.

Example 2 – Grant-Funded Program:

Grant revenues are recorded in the applicable fund using intergovernmental revenue objects. Expenditures are charged to the appropriate functions and objects. Program-level analysis links revenues and expenditures analytically.

Example 3 – Enterprise Utility Charges:

Charges for water or sewer services are recorded in enterprise funds using charges-for-services objects. No functional revenue classification is applied. Functional analysis may occur at the expenditure level for management purposes.

3.8 Common Errors and CACOA Diagnostics

Common revenue reporting errors include misclassifying transfers as revenues, embedding functional meaning in revenue objects, and using revenue classification to simulate fund restrictions. CACOA diagnostics identify these issues prior to FTR submission.

3.9 Audit and Reconciliation Considerations

Auditors evaluate revenue classification for consistency, legal compliance, and reconciliation to audited financial statements. CACOA preserves traceability from detailed revenue objects to FTR rollups and GASB-based disclosures.

3.10 Citations and References

• California State Controller’s Office – Financial Transactions Report Instructions
• GASB Statement No. 33 – Accounting and Financial Reporting for Nonexchange Transactions
• GASB Statement No. 34 – Basic Financial Statements and Management’s Discussion and Analysis

4.1 Purpose and Scope of Expenditure Reporting in the FTR

Expenditure reporting in the FTR is designed to answer two fundamental questions: why resources were spent and what was acquired. These questions are addressed through the combined use of functional and object classifications.

Unlike revenue reporting, functional classification is mandatory for expenditures in the FTR. This requirement reflects the central role of expenditure data in evaluating service delivery, policy priorities, and cost structures across municipalities.

4.2 Functional Classification: Purpose of Spending

Functions describe the purpose or objective of an expenditure, such as public safety, public works, community development, or general government. Functional classification enables statewide comparisons of how resources are allocated among services.

CACOA adopts a four-digit function structure modeled on widely recognized governmental reporting standards. Function 0000 is reserved as a silent or non-applicable value and should not be used for expenditure reporting in the FTR profile.

4.3 Object Classification: Nature of Spending

Object classification describes the nature of what was purchased or paid, such as salaries, benefits, supplies, services, or capital assets. Object codes provide insight into cost drivers and spending behavior.

CACOA expenditure objects are organized within the 4000–4999 range and grouped into standardized object classes that roll up deterministically to FTR expenditure categories.

4.4 Relationship Between Function and Object

Function and object classifications are complementary, not interchangeable. Functions answer why money was spent; objects answer what the money was spent on. Both dimensions are required to fully describe an expenditure in statutory reporting.

CACOA enforces this separation to prevent misuse of objects to simulate functional reporting or functions to simulate spending categories.

4.5 Departments and Cost Centers

Departments represent organizational responsibility and are optional for FTR reporting. While not required by the FTR, departments are critical for internal management, budgeting, and cost control.

CACOA supports department coding as a parallel analytical dimension that does not interfere with statutory classification. Department rollups enable dashboarding and performance analysis.

4.6 Shared Costs and Cost Allocation

Many municipal costs support multiple functions or programs. Shared costs may include information technology, fleet services, human resources, or administrative overhead.

CACOA supports cost allocation methodologies while preserving FTR integrity. Allocations should be documented, applied consistently, and reviewed periodically. Allocated costs must retain appropriate functional and object classifications.

4.7 Capital Outlay vs Operating Expenditures

Capital outlay expenditures represent the acquisition or construction of capital assets and are distinct from operating expenditures. Proper classification is essential for meaningful financial analysis.

CACOA distinguishes capital outlay objects from operating objects while recognizing that capital assets are later reported on the balance sheet in accordance with capitalization policies.

4.8 Real-World Examples

Example 1 – Police Department Salaries:

Police salaries are recorded in the appropriate fund using a public safety function and salary-related expenditure objects. Department codes may be used for management analysis but do not affect FTR classification.

Example 2 – Shared IT Services Allocation:

Information technology costs incurred centrally may be allocated to multiple functions using a documented allocation methodology. Each allocated expenditure retains its functional and object classification for FTR reporting.

Example 3 – Capital Project Expenditures:

Expenditures for infrastructure construction are recorded using capital outlay objects and the appropriate function. The resulting asset is capitalized and reported separately on the balance sheet.

4.9 Common Errors and CACOA Diagnostics

Common errors include using departments in place of functions, misclassifying capital outlay as operating expense, and inconsistent allocation practices. CACOA diagnostics identify these issues prior to FTR submission.

4.10 Audit and Reconciliation Considerations

Auditors assess expenditure classification for consistency, appropriateness, and compliance with GASB and statutory requirements. CACOA preserves traceability from detailed postings to FTR rollups and audited financial statements.

4.11 Citations and References

• California State Controller’s Office – Financial Transactions Report Instructions
• GASB Statement No. 34 – Basic Financial Statements
• GASB Concepts Statement No. 1 – Objectives of Financial Reporting

5.1 Purpose and Conceptual Framework of OFS/OFU

Other Financing Sources and Uses represent inflows and outflows that are not revenues or expenditures. They reflect changes in financial resources arising from financing decisions rather than operations.

5.2 Relationship to GASB Standards

GASB standards distinguish operating activity from financing activity across governmental and proprietary fund reporting. GASB Statement No. 34 establishes the framework for reporting other financing sources and uses in governmental funds.

5.3 CACOA Object Structure for OFS/OFU

CACOA reserves dedicated object ranges for Other Financing Sources and Uses, distinct from revenue and expenditure object ranges.

5.4 Interfund Transfers

Interfund transfers represent flows of financial resources between funds without expectation of repayment.

5.5 Debt Proceeds

Proceeds from issuing bonds or notes are reported as Other Financing Sources in governmental funds.

5.6 Capital Contributions

Capital contributions may be reported as Other Financing Sources depending on legal structure.

5.7 Real-World Examples

Examples include General Fund transfers to Capital Projects Funds and bond issuance proceeds.

5.8 Common Errors and Diagnostics

Common errors include misclassifying transfers as revenues and failing to record symmetrical entries.

5.9 Audit and Reconciliation

Auditors closely review OFS/OFU because misclassification can materially affect reported results.

5.10 Citations

• SCO Financial Transactions Report Instructions
• GASB Statement No. 34

6.1 Purpose and Scope of Balance Sheet Reporting in the FTR

Balance sheet reporting in the FTR is designed to provide statewide visibility into the financial position of municipalities. While the FTR is not a substitute for audited financial statements, its balance sheet categories allow comparability across agencies by applying standardized classification at the fund level.

Unlike expenditure reporting, balance sheet reporting does not use functional classification. Assets and liabilities are reported solely by fund and object classification.

6.2 Relationship to GASB: Governmental vs Proprietary Reporting

GASB Statement No. 34 requires governments to present both governmental fund financial statements and government-wide statements. Governmental funds use the modified accrual basis and generally focus on short-term financial resources, while proprietary funds use full accrual and focus on economic resources.

The FTR balance sheet consolidates key balance sheet categories by fund but does not replicate all GAAP presentation nuances. CACOA supports both bases by maintaining consistent object definitions while allowing reporting profiles to tailor presentation.

6.3 CACOA Asset Classification and FTR Alignment

CACOA asset objects are organized within the 1000–1999 range and mapped to FTR balance sheet lines. Asset classes are structured to distinguish current assets (cash, receivables, inventories, prepaid items) from noncurrent assets (capital assets, restricted assets, long-term receivables).

CACOA supports additional detail beneath standardized asset categories, provided that rollups remain deterministic and traceable.

6.4 CACOA Liability Classification and FTR Alignment

CACOA liability objects are organized within the 2000–2899 range and mapped to FTR balance sheet lines. Liabilities are structured to distinguish current liabilities (accounts payable, accrued liabilities, current portions of long-term debt) from long-term liabilities (bonds, leases, pensions, OPEB).

Proper liability classification is critical for comparability and audit review, particularly for pension and OPEB obligations, lease liabilities, and debt-related balances.

6.5 Equity and Fund Balance: Governmental and Proprietary Concepts

In governmental funds, equity is typically reported as fund balance, which GASB Statement No. 54 requires to be classified into nonspendable, restricted, committed, assigned, and unassigned categories. In proprietary funds, equity is reported as net position, classified into net investment in capital assets, restricted, and unrestricted categories.

The FTR reports equity/fund balance at the fund level, focusing on standardized categories that support statewide analysis. CACOA provides equity objects within the 2900–2999 range and supports GASB-aligned subclassification through reference tables and rollups.

6.6 Prohibition on Functional Balances and Improper Segmentation

A common structural error is attempting to track fund balance by function or department. Fund balance represents the residual of assets and liabilities within a fund and must be maintained at the fund level. Functions describe the purpose of expenditures and do not apply to balance sheet accounts.

CACOA explicitly prohibits functional classification of balance sheet accounts in the FTR profile and provides diagnostics to identify improper postings.

6.7 Special Situations and Real-World Examples

Example 1 – Developer Deposits and Drawdowns:

A city may receive deposits from developers for plan review or inspection services. These deposits are not revenue at receipt; they represent a liability (deposit payable). As services are provided, the city recognizes revenue or reduces the liability depending on the policy and legal structure. CACOA supports this by providing distinct liability objects for deposits and appropriate revenue objects for earned amounts.

Example 2 – Advances Between Funds:

Interfund advances differ from transfers. Advances are balance sheet receivables/payables expected to be repaid. Transfers are other financing sources/uses and do not create receivables. CACOA distinguishes advances using asset and liability objects, while transfers are recorded in OFS/OFU ranges.

Example 3 – Restricted Cash in Enterprise Funds:

Enterprise funds may hold restricted cash for bond covenants or capital reserves. CACOA supports restricted asset objects that roll up to FTR categories while preserving detail for covenant compliance.

6.8 Common Errors and CACOA Diagnostics

Common balance sheet reporting errors include treating deposits as revenue, misclassifying advances as transfers, failing to separate current and long-term portions of liabilities, and mixing restricted and unrestricted assets without adequate detail. CACOA diagnostics identify these issues through mapping completeness checks and classification validation rules.

6.9 Audit and Reconciliation Considerations

Balance sheet accounts are frequently subject to audit emphasis because they affect financial position and long-term obligations. CACOA supports audit review by providing consistent definitions, GASB-aligned descriptions, and traceable rollups from detailed objects to FTR categories.

Reconciliation between local ledgers, audited statements, and FTR reporting should be performed at the fund level. CACOA’s reporting views are designed to facilitate this reconciliation by preserving fund integrity and deterministic rollups.

6.10 Citations and References

• California State Controller’s Office – Financial Transactions Report Instructions
• GASB Statement No. 34 – Basic Financial Statements and Management’s Discussion and Analysis
• GASB Statement No. 54 – Fund Balance Reporting and Governmental Fund Type Definitions
• GASB Statement No. 68 – Accounting and Financial Reporting for Pensions
• GASB Statement No. 75 – Accounting and Financial Reporting for Postemployment Benefits Other Than Pensions
• GASB Statement No. 87 – Leases

7.1 Purpose of Functional Classification

Functional classification exists to describe the purpose of expenditures. It allows statewide comparison of how resources are allocated among services such as public safety, public works, community development, and general government.

7.2 When Functional Classification Is Required

Functional classification is required for all operating and capital expenditures reported in the FTR.

7.3 When Functional Classification Is Prohibited

Functional classification must not be applied to revenues, balance sheet accounts, or other financing sources and uses.

7.4 Primary Function Selection

Agencies must assign a primary function or allocate costs across functions using documented methodologies.

7.5 Cost Allocation and Shared Services

Shared services may be allocated to benefiting functions using rational, consistent methodologies.

7.6 Departments vs Functions

Departments represent organizational responsibility and must not be used as substitutes for functions.

7.7 Special Cases

Certain expenditures may require documented exceptions while preserving standardized rollups.

7.8 Real-World Examples

Examples include election costs, emergency operations, and improper functional revenue use.

7.9 Common Errors and Diagnostics

CACOA diagnostics identify missing or improper functional classification.

7.10 Audit Considerations

Auditors evaluate functional classification for consistency and appropriateness.

7.11 Citations

• SCO Financial Transactions Report Instructions
• GASB Statement No. 34

8.1 Purpose of Diagnostics and Validation

Diagnostics and validation exist to ensure that financial data is structurally sound, internally consistent, and compliant with statutory reporting requirements. Unlike transactional controls that prevent posting, CACOA diagnostics are designed to identify issues early while preserving the ability to analyze and review data.

This approach supports iterative improvement, transparency, and informed decision-making prior to final FTR submission.

8.2 Validation Philosophy: Prevent vs Detect

CACOA distinguishes between preventative controls and detective controls. Preventative controls block structurally invalid combinations, such as applying functional codes to balance sheet accounts. Detective controls identify issues that require judgment or correction.

This distinction allows agencies to preview results, understand unmapped items, and address exceptions without suppressing meaningful information.

8.3 Core Validation Rules

Core validation rules enforce non-negotiable statutory requirements. Examples include requiring function codes on expenditures, prohibiting function codes on revenues and balance sheet objects, and enforcing fund-level integrity for equity balances.

8.4 Mapping Completeness and Draft States

CACOA supports explicit mapping states that indicate whether a chart element is fully mapped, partially mapped, or unmapped for FTR reporting. Draft states allow agencies to review preliminary rollups while clearly identifying gaps.

This design avoids the false choice between blocking reports and submitting incomplete data.

8.5 Unmapped and Exception Handling

Unmapped items may arise from locally defined codes, newly introduced activity, or unusual transactions. CACOA provides exception tables and diagnostic views to capture these items without forcing premature classification.

8.6 Symmetry and Cross-Fund Validation

Certain transactions require symmetrical treatment across funds, such as interfund transfers and advances. CACOA diagnostics identify unmatched pairs and imbalances prior to FTR submission.

8.7 Rollup Integrity and Range Validation

CACOA relies on deterministic rollups based on code ranges and class definitions. Validation rules ensure that all detail codes fall within defined ranges and that rollups do not overlap in ways that compromise comparability.

8.8 Diagnostic Reporting and Review Workflow

Diagnostic reports present validation results in a structured, review-friendly format. Agencies should review diagnostics iteratively, resolve high-risk issues, and document exceptions prior to finalizing FTR submissions.

8.9 Audit Readiness and Documentation

Well-documented diagnostics and exception handling support audit review by demonstrating intentional classification decisions, consistent application of rules, and continuous improvement.

8.10 Citations and References

• California State Controller’s Office – Financial Transactions Report Instructions
• GASB Concepts Statement No. 1 – Objectives of Financial Reporting
• GASB Statement No. 34 – Basic Financial Statements

9.1 Purpose of Reconciliation and Review

Reconciliation ensures that data reported in the FTR is complete, accurate, and consistent with the agency’s accounting records and audited financial statements. Review processes provide assurance that classification decisions are intentional, documented, and compliant.

9.2 Relationship Between FTR and Audited Financial Statements

The FTR is not a replacement for audited financial statements. Rather, it is a standardized statutory report derived from those statements and the underlying accounting records.

CACOA facilitates reconciliation by maintaining deterministic rollups from detailed chart elements to FTR categories, allowing agencies to trace reported amounts back to source data.

9.3 Reconciliation at the Fund Level

Reconciliation should be performed at the fund level, consistent with the unit of accountability used in the FTR. Agencies should reconcile fund revenues, expenditures, other financing sources and uses, and ending fund balances to audited figures.

9.4 Timing and Sequencing of Reconciliation Activities

Reconciliation is an iterative process. Preliminary reconciliation may occur prior to audit completion, with final reconciliation performed after audited balances are available.

9.5 Use of Diagnostics in Final Review

Diagnostics developed under CACOA play a critical role in final review. Agencies should resolve high-severity issues, review remaining exceptions, and document rationale for any unresolved items prior to submission.

9.6 Internal Review and Approval Workflow

Agencies should establish a formal internal review process that includes accounting staff, finance leadership, and, where appropriate, external advisors. Documentation of review and approval supports accountability and audit readiness.

9.7 Submission to the State Controller’s Office

The SCO establishes deadlines and submission formats for the FTR. Agencies are responsible for ensuring timely submission and responding to follow-up inquiries or correction requests.

9.8 Responding to SCO Review and Inquiries

SCO staff may request clarification or correction of reported data. CACOA supports efficient response by preserving traceability and providing documentation of classification and mapping decisions.

9.9 Post-Submission Review and Continuous Improvement

Following submission, agencies should review diagnostic results, SCO feedback, and audit findings to identify opportunities for improvement. CACOA supports continuous refinement of mappings and validation rules without disrupting historical comparability.

9.10 Citations and References

• California State Controller’s Office – Financial Transactions Report Instructions
• GASB Concepts Statement No. 1 – Objectives of Financial Reporting
• GASB Statement No. 34 – Basic Financial Statements and Management’s Discussion and Analysis