AB 658 requires the California Department of Motor Vehicles to complete and post an "affordability impact analysis" on its website within six months in any year a vehicle registration fee increase under Section 9250 takes effect. The statute prescribes a 13‑item dataset the DMV must publish, including five‑year trends in average registration cost increases, delinquent registrations and debt, impounds and debt collections, referrals to the Franchise Tax Board, exemptions used, and an itemized list of Motor Vehicle Account (MVA) cost drivers.
The bill matters because it ties fee increases to a statutory transparency exercise: it forces agencies to quantify who bears the cost (by vehicle value and ZIP code) and to propose efficiency and mitigation options intended to minimize impacts on low‑ and middle‑income households. That combination creates new compliance work for the DMV and other collection entities, raises data‑integration and privacy questions, and gives policymakers a richer dataset to justify or resist future fee actions.
At a Glance
What It Does
The bill requires the DMV to publish a public affordability impact analysis within six months whenever a registration fee described in Section 9250 is increased. The analysis must report 13 specific items — from average cost increases to delinquent‑debt breakdowns and proposals to close the MVA shortfall.
Who It Affects
Primary obligations fall on the DMV but the bill pulls data from multiple programs and actors: the Franchise Tax Board (for collections data), local impound/sale records, and DMV enforcement and exemption records. Policymakers, consumer advocates, and households in ZIP codes with high delinquency rates will be the main users of the report.
Why It Matters
This creates a recurring, legislated transparency mechanism around registration fee hikes and MVA shortfalls. It standardizes the data policymakers can cite when considering fee policy and directs agencies to identify efficiency savings and mitigation strategies targeted at low‑ and middle‑income vehicle owners.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
AB 658 triggers a single, focused obligation: when the Legislature or state action produces an increase in the vehicle registration fee defined by Section 9250, the DMV must deliver and post an "affordability impact analysis" within six months of the fee taking effect. The bill does not cap fees or limit collections; it requires the DMV to quantify the financial effects of fee increases and the distribution of those effects across vehicle value classes and ZIP codes.
The bill prescribes the precise contents of the analysis. The DMV must calculate five‑year trends in average registration cost increases and show how those increases vary by vehicle value.
It must enumerate delinquent registrations, delinquency inflows year‑to‑year, and total delinquent registration debt — with breakdowns by vehicle value, length of delinquency, and the portion of debt that is original balance versus late penalties. The report must also list enforcement outcomes: numbers of impounds and sales tied to unpaid registrations, amounts collected through impound sales, referrals to the Franchise Tax Board for bank levies and wage garnishments, amounts collected by FTB and remitted to DMV, and civil actions the DMV initiated to collect debt.Beyond collections and delinquency, the analysis must account for related holds (parking and toll violations), the number of fee exemptions claimed under the referenced statutory sections, and an itemized list of cost increases that have driven MVA shortfalls.
AB 658 also asks the DMV to describe past efficiency efforts (automation, online transactions, reduced field visits), estimate savings from those efforts, and propose additional savings and alternative strategies that could eliminate the MVA deficit while minimizing impacts on low‑ and middle‑income families. Finally, the bill ties the vehicle value breakdown to the five classes established in Revenue and Taxation Code Section 11052, which standardizes how vehicles are grouped in the report.
The Five Things You Need to Know
The DMV must post the affordability impact analysis on its website within six months after a registration fee increase described in Section 9250 becomes effective.
The analysis must include 13 discrete items, among them five‑year trends on average registration cost increases, counts of delinquent registrations, and total delinquent registration debt with breakdowns by vehicle value and ZIP code.
Debt reporting must separate original balances from amounts attributable to late penalties and must show how long debts have been past due.
The bill requires the DMV to report enforcement outcomes: vehicles impounded and sold to collect registration debt, FTB referrals for levies/garnishments, civil collection actions, and the totals collected by these routes over five years.
Vehicle value classifications in the report must use the five classes defined in Revenue and Taxation Code Section 11052; the statute also mandates proposals for additional savings and alternative strategies to address the MVA shortfall while protecting low‑ and middle‑income families.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Trigger and deadline for the affordability analysis
Subdivision (a) sets the trigger: the analysis is required only in years when a registration fee increase described in Section 9250 is enacted. It imposes a concrete deadline — complete and post the report within six months after the increase becomes effective — creating a short, statutory production window for a multi‑agency data product.
Five‑year cost and delinquency metrics
Paragraphs (1)–(3) force the DMV to assemble historical analytics: average annual registration cost increases over five years (with vehicle‑value breakdowns), counts of delinquent registrations and new delinquencies by year and ZIP code, and a five‑year ledger of delinquent registration debt with splits by vehicle value, time past due, and principal versus late penalties. Practically, this requires cross‑referencing registration, billing, and penalty records and validating that the penalty/principal split is computable from existing systems.
Enforcement collections and interagency referrals
Paragraphs (4)–(6) require reporting on actions to enforce collections: numbers of vehicles impounded and sold under the cited chapter, amounts collected via impound sales, counts and amounts of registrations referred to the Franchise Tax Board for bank levies and wage garnishments (with ZIP and value breakdowns), and totals remitted by FTB back to DMV. These provisions formalize the linkage between DMV enforcement and FTB collection activity for transparency and evaluation.
Civil actions, holds, and exemptions
Paragraphs (7)–(9) expand the dataset to include the DMV's civil‑litigation activity to collect registration debt, the universe of vehicles subject to registration holds for unpaid parking or toll violations, and counts of vehicles granted statutory fee exemptions. The repeated ZIP code and vehicle value breakdowns require record matching across enforcement, parking/toll interfaces, and exemption registries.
MVA shortfall drivers, efficiency efforts, and definition of vehicle value
Paragraphs (10)–(13) require an itemized list of cost increases that contributed to MVA shortfalls, a recitation of prior efforts to improve efficiency and automation (with estimated budgetary savings), proposals for additional savings, and any alternative analyses that would minimize impacts on low‑ and middle‑income families. Subsection (c) defines "vehicle value" by referring to the five classes in Revenue and Taxation Code Section 11052, ensuring consistent categorization across reports.
This bill is one of many.
Codify tracks hundreds of bills on Transportation across all five countries.
Explore Transportation in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Low‑ and middle‑income vehicle owners — the analysis requires ZIP‑ and value‑level breakdowns and mitigation proposals that can expose concentrated affordability problems and support targeted relief or exemptions.
- Consumer and legal‑aid advocates — the standardized, public dataset gives advocates empirical footing to press for fee relief, exemption expansion, or policy reforms in high‑impact ZIP codes.
- State policymakers and legislative staff — the report supplies a repeatable, comparable evidence base (five‑year trends and enforcement outcomes) that legislators can use when weighing future fee proposals or drafting targeted assistance.
- Local governments and community planners — ZIP‑level delinquency and impound data will help local authorities measure how registration fee policy interacts with parking/toll enforcement and impound practices in their jurisdictions.
- DMV leadership and budget analysts — the requirement to document efficiency measures and projected savings creates a formal record DMV can use to prioritize modernization investments and defend budget requests.
Who Bears the Cost
- Department of Motor Vehicles — the DMV must compile, validate, and publish extensive cross‑program datasets within a six‑month window, creating significant administrative and IT workload and likely requiring staff time or system development.
- Franchise Tax Board and local enforcement entities — FTB, impound yards, and courts may need to extract and share historical collection data and reconcile figures with DMV records, imposing analytic and coordination costs.
- California taxpayers/state budget — if the analysis triggers additional exemptions or fee mitigation proposals, the state may need to absorb lost revenue or allocate funds to close MVA shortfalls, shifting costs elsewhere in the budget.
- Small impound operators and collection contractors — increased scrutiny and reporting requirements may impose operational recordkeeping burdens and require data sharing that they are not currently set up to provide.
- Privacy officers and legal teams — the mandated ZIP‑level and value‑class breakdowns raise privacy and data‑security responsibilities for agencies that must publish granular, potentially sensitive datasets.
Key Issues
The Core Tension
The bill pits two legitimate objectives against each other: the state's need to shore up the Motor Vehicle Account through reliable fee revenue versus the goal of protecting low‑ and middle‑income households from disproportionate fee burdens — and it tries to resolve that by demanding transparency, which creates its own administrative, privacy, and methodological costs without guaranteeing concrete relief.
AB 658 prescribes a wide-ranging dataset but leaves key implementation mechanics unspecified. The DMV will likely need to reconcile multiple legacy systems (registration, penalty accounting, impound sales, and FTB remittances) to produce consistent five‑year figures, and the statute does not specify standard definitions or reconciliation rules beyond referencing vehicle value classes.
That gap creates room for variation in methodology across reporting cycles and could make year‑to‑year comparisons difficult unless the DMV issues accompanying methodological notes. The six‑month deadline is short for multi‑system data extraction, cleaning, and cross‑agency reconciliation, so compliance may require upfront resource commitments.
The bill also creates a privacy‑versus‑transparency tension. ZIP‑level breakdowns improve targeting but can risk re‑identification in small ZIP codes or where rare vehicle‑value classes are concentrated.
The statute does not specify anonymization or minimum‑cell suppression rules. Finally, AB 658 mandates proposals and alternative analyses but does not attach binding remedies or funding to any proposed mitigation; the analysis is informational not prescriptive, so whether it changes policy outcomes depends on follow‑on legislative or administrative action.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.