CACOA manual
Why a common chart matters, how the codes work, and a line-by-line guide to the Cities FTR.
About the CACOA
- Why a common chart of accountsWhat the California Agency Chart of Accounts is, who it is for, and the problem it solves.
- Relationship to GASB and GAAPThe CACOA organizes accounts; GASB decides what is recognized and reported.
- Design principlesReporting first, objects as the anchor, one meaning per code, and room for local detail.
- Adoption pathsMap, blend, or convert. Each path produces a better FTR than the one before it.
- Real-world practicesEvents, deposits, pass-throughs, and other practices that do not fit textbook examples.
Using the chart
FTR guide
- How the Cities FTR is builtWhat the State Controller asks for, when it is due, and how the report is organized.
- Revenues (forms 15-23)General versus functional revenue, and how the object and function codes pick the line and column.
- Expenditures (forms 24-29)The function code picks the line on forms 24-28; the object code picks the line on form 29.
- Other financing and fund balance (form 30)Transfers, debt proceeds, lease financing, asset sales, special items, and the fund balance rollforward.
- Balance sheets (forms 37, 38, 39, 40)Four balance sheet forms, and why governmental capital assets and long-term debt belong in fund 980.
- Enterprise, internal service, and fiduciary funds (forms 03-13, 30.5)One operating statement per enterprise type, chosen by the fund block.
- How the crosswalk worksRules, axes, priorities, signs, and the coverage test, for anyone building reports or software on the CACOA.
- Review and submissionA repeatable routine for finishing the FTR on time, from audited numbers.
- Other State Controller reportsCounties, special districts, transit operators, planning agencies, retirement systems, and the street and road reports, from the same codes.