California's $500,000 remote-seller threshold needs a scoped sales ledger

The direct answer

A California remote-seller review needs a dated, reproducible sales ledger whose population matches the state's published threshold language. A top-line company revenue figure cannot show which transactions were sales of tangible personal property for delivery in California, whether related-person sales were included, or which calendar-year test was applied.

CDTFA's Wayfair guidance records that Assembly Bill 147 amended California Revenue and Taxation Code section 6203. The agency describes a threshold of more than $500,000 in combined California-delivery sales during the preceding or current calendar year. That official statement is the authority for the operating question; software, a dashboard, or this analysis is not the source of the rule.

Build the calculation from transaction evidence

The calculation record should identify the legal seller, any related persons included, invoice or order identifier, transaction date, ship-to or delivery evidence, product classification, gross amount, adjustments, exemption treatment, and the rule version used. It should also preserve the query time and source-system extracts so a later reviewer can reproduce both the population and the result.

The period matters. A current-year calculation changes as transactions post, cancel, return, or receive credit adjustments, while a preceding-year calculation should remain tied to a closed population and documented correction policy. Teams should not silently switch between booking date, invoice date, shipment date, and delivery date; the chosen treatment and unresolved data gaps need explicit review.

Keep separate obligations separate

CDTFA's guidance distinguishes the seller's registration and collection discussion from district use-tax collection and notes different operative dates in the Wayfair implementation history. The practical control is therefore not a single nexus flag. It is a chain from the threshold result to the specific registration, tax-determination, invoice, return, payment, and evidence processes that accountable tax personnel approve.

Physical presence also remains relevant under the agency's guidance. A remote-sales test should not overwrite records for inventory, personnel, affiliates, trade shows, marketplace activity, or other contacts. Marketplace-facilitator facts and exempt transactions may require their own analysis. Unknown locations, inconsistent customer addresses, and missing related-party mappings should remain exceptions rather than being forced into a confident result.

What to retain for review

A defensible file should retain the CDTFA guidance reviewed, access date, statutory or guidance version, seller and related-party scope, transaction inclusion logic, excluded populations with reasons, threshold result, first crossing date if applicable, reviewer, approval, and downstream actions. Changes to tax content or configuration should create a new version rather than rewrite the earlier decision record.

This is an operational reading of public guidance, not tax advice or an applicability determination. California treatment can turn on facts absent from a public article, and CDTFA itself directs taxpayers to its written-advice process for fact-specific guidance. The useful outcome is a scoped evidence package that lets qualified tax personnel decide what the seller must do and explain why.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Indirect Tax Monitor will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.