Why the State Controller's report takes so long, and how to stop rebuilding it every year

Every California city files a Financial Transactions Report (FTR) with the State Controller each year. Special districts file their own version. The report is due seven months after the end of the fiscal year, so for most agencies the end of January, and the State Controller does not grant extensions. Refusing to file, or knowingly filing a false report, is a misdemeanor, and agencies can face a forfeiture of up to $5,000.

The data does not disappear into a filing cabinet. The State Controller publishes it at By the Numbers, where legislators, researchers, reporters, and residents compare one city with another.

So it matters, it is mandatory, and it is due in the middle of audit season. Why does it take so long?

The real work is translation

The FTR is not complicated accounting. Almost every number on it is already in the audited financial statements. What takes the time is translation: taking a chart of accounts designed by one agency and sorting it into several hundred lines designed by the state.

In practice that usually means:

• A spreadsheet that maps local accounts to FTR lines, inherited from last year and last year's preparer.
• New accounts created during the year that nobody mapped.
• Revenue that has to be split between the report's "general" and "functional" columns by hand.
• Capital assets, long-term debt, and pension balances pulled from separate year-end spreadsheets, because they never lived in the ledger.
• Audit adjustments typed into the report instead of posted to the books, and so retyped next year.

Every agency does this separately, every year, for the same state form. That is the part worth fixing.

What makes it fast

Agencies that finish the FTR quickly tend to share three habits.

1. They map accounts once, at the source. Every account in the ledger carries its reporting destination as an attribute, set when the account is created. The FTR becomes a sort of the trial balance, not a research project.

2. They code revenue correctly when it is recorded. The FTR splits governmental revenue into general revenue (usable for any purpose, like general property and sales taxes) and functional revenue (fees for services, and revenue tied to a service by a grant, statute, or bond agreement). If that distinction is recorded when the revenue is posted, nobody has to reconstruct it in January.

3. They keep year-end conversion entries in the ledger. Capital assets, long-term debt, compensated absences, and pension balances for governmental activities are not in the governmental funds. When they live only in a spreadsheet, the FTR's government-wide form has to be assembled by hand. When they are posted as journal entries in a separate ledger fund, the form reads straight from the trial balance.

Doing it once for everyone

The mapping step is identical in principle for every city, because every city files the same form. That is the argument for a common chart of accounts, and it is why GovGlider publishes the California Agency Chart of Accounts with the FTR crosswalk already built in. Each CACOA code has a published FTR line for every fund type, and the FTR finder shows where any combination lands.

An agency does not have to convert its whole ledger to benefit. Mapping existing accounts to CACOA codes once means the FTR mapping is inherited instead of rebuilt; only new accounts need attention after that.

A January that goes differently

A realistic target for an agency that adopts these habits:

• By October: accounts mapped, suspense accounts cleared, conversion entries posted.
• When the audit closes: audit adjustments posted as journal entries, post-closing trial balance run through the crosswalk.
• Two weeks later: forms reviewed against the audited statements, debt forms tied to the debt note, report filed.

The FTR routine walks through each step. The goal is not to make the FTR clever. It is to make it boring, the way a report generated from well-kept books should be.