Plenty of legitimate practices do not fit neatly into a textbook. The CACOA handles them by giving each one a clear home rather than forcing a reclassification.
Events and special programs
Some agencies track festivals, emergencies, or one-time programs as their own accounts. In the CACOA an event is a project or program attribute, not an object: the costs keep their normal objects (salaries, supplies, contracts) and the event is tracked alongside them. Emergency costs keep their true function (usually disaster preparedness, function 2400) so they report correctly and can be claimed for reimbursement.
Developer deposits and pass-through money
Developer deposits, refundable fees, and money collected for other agencies are liabilities, not revenue. The CACOA provides deposit (2130, 2290) and due-to-other-governments (2120) codes, and custodial funds (810-849) for money the agency holds for others. Revenue is recognized only as the agency earns it.
Reimbursements and overhead
When one fund pays a cost that belongs to another, the fund that bears the cost records the expenditure and the fund that paid first records a reduction of expenditures, not revenue. The State Controller's instructions treat cost allocation plans the same way. Objects 5600 (cost allocation) and 5610 (internal service charges) identify these charges in the fund that pays them.
Suspense and clearing accounts
Payroll clearing (4980), expenditure clearing (5980), and asset and liability suspense codes (1080, 2180) exist because real systems need them. They should be empty at year end. The crosswalk still places any leftover balance, so nothing disappears from the report, and validation flags the balance for cleanup.
When something truly does not fit
Use a local-detail code, describe it, and declare the FTR line it belongs on. Then suggest a universal code. The next release may add it.