SB 346 defines “short‑term rental facilitator” broadly and requires those facilitators, on request by a local agency, to report identifying information for each short‑term rental they facilitate. Local agencies may set the format and frequency of reporting and can impose administrative penalties for failures to comply.
The bill matters because it moves the practical ability to identify taxable stays from scattered hosts to centralized online marketplaces and related intermediaries. For compliance officers and platform operators, SB 346 creates a predictable legal hook that local tax offices can use to obtain unit‑level data — and it also raises questions about implementation, privacy, and the scope of who counts as a facilitator.
At a Glance
What It Does
SB 346 obliges short‑term rental facilitators to report, upon a local agency’s request and in the form the agency prescribes, identifying information about each short‑term rental they facilitate. It also supplies statutory definitions for key terms, including a broad definition of “short‑term rental facilitator.”
Who It Affects
Online marketplaces and related entities that list, price, brand, process payments for, or otherwise bring guests and hosts together for stays of 30 days or less; hosts and operators who use those platforms; and city and county tax departments that administer transient occupancy taxes. Hotels are explicitly excluded from the facilitator definition.
Why It Matters
The bill creates a clear statutory path for local governments to obtain unit‑level data needed to enforce transient occupancy taxes, potentially increasing tax collection and compliance. For platforms and hosts, it imposes a new compliance vector that may require reporting workflows, data mapping, and policy changes.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
SB 346 starts by drawing a map of the regulated territory. It defines a “short‑term rental” as occupancy of a dwelling or similar non‑hotel lodging for 30 consecutive days or less, as local ordinances may further specify.
The bill intentionally separates hotels from the new facilitator rules: a commercial hotel, motel, or bed‑and‑breakfast remains governed by existing tax law, not the facilitator regime this bill creates.
The core obligation lands on entities the bill calls “short‑term rental facilitators.” The definition is deliberately broad: it covers enterprises that transmit offers between guest and host, operate the electronic or physical infrastructure that connects them, provide payment processing, list non‑hotel lodgings for short stays, set prices, brand listings, accept reservations, or even provide virtual currency used in transactions. The definition also reaches related persons and certain software development activities when those activities directly support the facilitation of short‑term rentals.
Practically, that sweep captures full‑service platforms, many channel managers, some payment processors tied closely to a marketplace, and possibly companies that provide proprietary booking infrastructure.On the reporting side, a local agency must request the information before a facilitator has an obligation to provide it; the facilitator then must report in the form and manner the agency prescribes. The bill requires that facilitators disclose the physical address (including nine‑digit ZIP Code) of each short‑term rental within the reporting period.
If that address is insufficient to identify a particular unit, a local agency can ask for the assessor parcel number (APN), the listing’s URL, or unit‑level identifiers that distinguish accessory dwelling units, guest houses, timeshare units, or individual multifamily units at the same address.SB 346 limits the frequency of mandatory reporting to no more than every three months within a 12‑month period, unless a local agency requires monthly remittance of the transient occupancy tax — in that case, monthly reporting is permitted. Enforcement is left to local agencies: they may attach an administrative fine or penalty for failure to produce the requested information, using the enforcement authority authorized under existing Government Code Section 53069.4.
The practical effect is to give local tax offices a statutory route to pull unit‑level data from platforms, while leaving the details of formats, timelines, and penalties to local ordinances and administrative practice.
The Five Things You Need to Know
SB 346 requires a short‑term rental facilitator to provide the physical address (with nine‑digit ZIP Code) for each short‑term rental it facilitated during the reporting period when a local agency requests that information.
If an address alone does not identify the specific rental unit, the local agency can request the assessor parcel number (APN), the listing’s URL, or unit‑level information distinguishing ADUs, guest houses, or individual timeshare/multifamily units.
The bill caps reporting frequency at once every three months during any 12‑month period, but allows monthly reporting if the local agency already requires monthly tax remittance.
“Short‑term rental facilitator” is defined broadly to include entities that list units, set prices, take reservations, process payments, operate the marketplace infrastructure, brand listings, or provide virtual currency tied to stays — and it reaches related persons.
Local agencies may make noncompliance subject to an administrative fine or penalty under Government Code Section 53069.4, but SB 346 leaves the penalty level and procedural details to local ordinance and administrative action.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Defines the covered terms and scope
This section establishes the statutory vocabulary that structures the bill: what counts as a hotel (which is excluded from the facilitator regime), what a local agency is, what a marketplace is, who the purchaser is, and how “short‑term rental” is defined (30 days or less, plus local ordinance variations). That language sets the perimeter for who must comply and clarifies that the facilitator regime targets non‑hotel, short‑duration stays.
Broad, activity‑based definition of ‘short‑term rental facilitator’
Subdivision (g) is the operative catch: it defines a facilitator by the activities it or its related persons undertake. The list mixes connective functions (transmitting offers, owning marketplace infrastructure), transactional functions (payment processing, taking reservations, setting prices), commercial branding, and even virtual currency provision. Including related persons and qualifying software development activities gives regulators flexibility to treat vertically integrated marketplaces, channel managers, and some technology vendors as within scope — an important drafting choice that increases the universe of entities that may face reporting requests.
Data local agencies can request and when more detail is required
This provision requires facilitators, upon a local agency’s request, to report the physical address and nine‑digit ZIP for each short‑term rental during the reporting period. If the address won’t uniquely identify the unit, the statute authorizes follow‑up requests for APN, listing URL, or unit‑specific identifiers for ADUs, guest houses, timeshare units, or individual multifamily units. The bill leaves the initial trigger as a local request rather than an automatic reporting obligation, but gives agencies a clear menu of unit‑level identifiers they can demand to match records to parcels and roll‑based tax systems.
Reporting cadence and enforcement authority
SB 346 limits reporting to intervals no more frequent than every three months within a 12‑month period, but it permits monthly reporting when the local agency already requires monthly remittance of transient occupancy tax. For compliance, local agencies may subject failures to report to administrative fines under Government Code Section 53069.4 — meaning the statute creates enforcement authority but delegates the specific penalty amounts and procedures to local ordinances and administrative rules. The combination of flexible timing and local enforcement control will shape how aggressively jurisdictions pursue platform data.
This bill is one of many.
Codify tracks hundreds of bills on Finance across all five countries.
Explore Finance 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
- City and county tax departments — Gain statutory authority and a clear list of data elements (address with 9‑digit ZIP, APN, URL, unit identifiers) to identify taxable short‑term stays and reduce leakage from unregistered hosts.
- Compliant short‑term rental hosts — Benefit indirectly from a level playing field if platforms’ data access leads to higher enforcement of transient occupancy taxes on noncompliant competitors.
- Residents and local service budgets — Stand to benefit from improved tax collection that can be allocated to local services, infrastructure, or tourism mitigation funds, depending on how jurisdictions deploy newly captured revenue.
- Vendors of tax‑compliance and data‑mapping services — Create a commercial opportunity to package address‑to‑APN matching, reporting automation, and platform compliance tools for marketplaces and local governments.
Who Bears the Cost
- Marketplace platforms and related tech providers — Face engineering, legal, and operational costs to identify, map, and export unit‑level data in the forms local agencies prescribe, and to assess whether their operations (or those of related persons) fall within the facilitator definition.
- Small hosts and operators — May incur indirect costs if platforms change terms, implement new verification steps, or delist listings to avoid compliance risk, and may face additional scrutiny if local enforcement increases.
- Local tax offices — While benefitting from better data, they must absorb intake, matching, and enforcement costs unless jurisdictions budget for new staffing or buy third‑party tools.
- Privacy and compliance teams — Must reconcile disclosure obligations under SB 346 with state privacy requirements and platform privacy policies, potentially requiring contract revisions and privacy notices.
Key Issues
The Core Tension
The central dilemma is straightforward: local governments need unit‑level data to enforce transient occupancy taxes and ensure fairness, but requiring marketplaces to become de facto tax reporters raises privacy, operational, and scope‑of‑liability concerns — and the more broadly the law defines a facilitator, the greater the compliance burden and the larger the pool of entities that may justifiably resist or litigate the requirement.
SB 346 gives local agencies a useful toolbox for matching listings to parcel records, but it leaves key implementation choices to local practice — the form and manner of reporting, the cadence of requests, and the level of fines. That delegation increases flexibility across diverse jurisdictions, but it also risks a patchwork of formats and enforcement standards that will drive operational complexity for platforms that operate statewide or nationally.
Platforms will need to map listings to nine‑digit ZIPs and APNs, maintain URLs and unit identifiers, and build responsive reporting pipelines that can handle ad hoc local requests.
The facilitator definition’s breadth is a double‑edged sword. Its activity‑based approach captures many marketplace functions intentionally, but language like “related person,” “owns or operates the infrastructure,” and inclusion of narrowly described software development activities may bring unexpected vendors and payment processors into scope.
That creates litigation and compliance risk around the degree of integration required to qualify as a facilitator. There are also privacy and contractual tensions: the bill requires sharing granular location data and listing identifiers that may implicate the California Privacy Rights Act (CPRA) and platforms’ existing privacy notices or host agreements.
Finally, because enforcement under Section 53069.4 depends on local ordinance and administrative action, penalty levels and procedural protections will vary by jurisdiction, leaving uncertain the practical deterrent effect and the rights available to platforms contesting requests.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.