Daily Transaction Reporting Requirements for California Secondhand Dealers

California secondhand dealers need a repeatable daily reporting workflow: capture the transaction correctly, transmit the report through CAPSS on time, and track corrections or follow-up items without losing the connection between the Customer, property, store, and transaction record.

Important: This page is general educational information, not legal advice. Daily transaction reporting duties can depend on the transaction type, current California law, DOJ/CAPSS technical requirements, store license status, system availability, and local licensing-authority expectations. Confirm requirements with official sources, your local licensing authority, or qualified counsel.

Quick answer

BPC § 21628 describes daily reporting to CAPSS, or reporting no later than the next business day excluding weekends and holidays after receipt or purchase of secondhand tangible personal property. BPC § 21630 separately states that a secondhand dealer shall electronically transmit the report to CAPSS no later than the next business day after the date of transaction, excluding weekends and holidays, or as soon as reasonable thereafter if transmission is not possible because of an electrical, telecommunications, or other malfunction.

What “daily” means operationally

For store operations, “daily” should be treated as a workflow standard, not just a legal phrase. Each business day should include a review of reportable transactions, missing fields, failed submissions, and items that require follow-up before transmission or correction.

Capture first: collect Customer, property, store, transaction, signature/fingerprint, and item data during intake.
Review before submission: check for obvious missing fields, unclear descriptions, unavailable identifiers, or image/signature/fingerprint issues.
Transmit through CAPSS: submit through the available CAPSS path your store uses.
Track response and corrections: retain confirmation, notice, error, omission, or follow-up status in the store workflow.

CAPSS submission paths

The California DOJ CAPSS materials describe several ways stores may work with CAPSS, including online reporting, bulk upload/XML workflows, and an optional API path. The DOJ API overview states that the API is an optional service and not mandatory; the existing web-based bulk import and online form remain available.

Online form / JUS 123-style workflow: direct entry for individual property transaction reports.
Bulk upload / XML workflow: one XML file may contain one or more property transaction reports, and each report may contain multiple property transaction items.
API workflow: optional automation pathway for uploading XML property transaction reports via web service.

What must be connected before reporting

A daily reporting workflow should keep these pieces connected before transmission:

Transaction date and type: the reporting timeline is tied to the transaction date / receipt or purchase event.
Customer information: this guide uses “Customer,” while official sources may use seller, pledger, or intended seller/pledger.
Property information: complete and reasonably accurate item description, serial number or unique identifier, brand/model, and other available details.
Store/license data: the reporting store and license information needed by the CAPSS workflow.
Images and signatures: signature, thumbprint/fingerprint, employee signature, item image, or other image data when required by the reporting workflow.
CAPSS status: whether the report submitted, failed validation, needs correction, or requires follow-up.

Electrical, telecommunications, or other malfunction

BPC § 21630 recognizes that timely electronic transmission may not always be possible because of an electrical, telecommunications, or other malfunction. In that circumstance, the statute refers to transmitting as soon as reasonable thereafter. Stores should treat this as a continuity and documentation issue: preserve the data, document the interruption, and transmit promptly when the system or connection is available.

Errors, omissions, and correction workflow

BPC § 21628 includes a good-faith acceptance concept and describes DOJ notice of an error or omission. The reporting dealer has three business days from that notice to amend or correct the report. A practical workflow should therefore include a daily review of CAPSS responses and a clear responsible manager for correction follow-up.

Review notices or validation responses from CAPSS.
Assign corrections to a responsible staff member or manager.
Keep the corrected record tied to the original transaction.
Document what changed and when the correction was submitted.

Daily reporting checklist

Use this as a store workflow checklist for staff training:

Review all reportable transactions from the business day.
Confirm Customer, store, item, transaction, and image/signature/fingerprint data are complete for the workflow.
Confirm item descriptions, serial numbers, IMEI/MEID, and other unique identifiers are captured where applicable.
Submit through the store’s CAPSS workflow no later than the applicable deadline.
Save confirmation or response details.
Review failed submissions, errors, omissions, or unresolved follow-up items.
Document outages or malfunctions and transmit as soon as reasonable thereafter.

Related guides

Where EZ-CAPSS can help

EZ-CAPSS helps stores organize transaction intake, Customer data, property descriptions, serial numbers, signature/fingerprint capture, offline-capable work, and JUS 123 generation from acquired data. It supports a more disciplined daily workflow, but it does not provide legal advice, guarantee compliance, or replace DOJ/CAPSS instructions.

Review your daily reporting workflow

If your store needs a more reliable daily transaction reporting process, request a walkthrough of how EZ-CAPSS supports intake, review, and CAPSS-ready reporting data.

REQUEST A DEMO

Official sources

Official sources referenced for this guide: