Schema record
@proseid v2026.07.26 US

California pay-data reporting determination

Determines whether a private employer must file a Payroll Employee Report, a Labor Contractor Employee Report, or both, and records the annual deadline, California workforce data, certification, and contractor-data controls.

Compatible with
FormGuided assessmentDeterminationCompliance checklistAPI
Use Schema in a Flow
Publication
Protocol
Proseid_v1.0
Version
v2026.07.26
Applies in
United States
Fields
21
Flow price
$0.20
Publisher fee
None
Standard base $0.20 · exact total is frozen when a Flow is created
Legal history

Time periods

ca_pay_data_20262026-01-01 → continues indefinitely
Current
Controlling sources
California Government Code § 12999
Source ↗
California Civil Rights Department Pay Data Reporting guidance Current reporting-year handbook and FAQ
Source ↗

Schema fields

21 fields
Pay, demographic, hours, weeks worked, exemption status, and employment-type data are complete
Boolean
—
Opt
Integrated-enterprise assessment
Select
Choices: Not an integrated enterprise, Integrated enterprise, Uncertain
Opt
Calculated reporting position
Select
Choices: Check current crd materials, Resolve integrated enterprise status, No report identified, Payroll report required, Labor contractor report required, Both reports required, Document late pay data submission, Complete pay data controls, Pay data record current
Opt
Required labor-contractor data has been obtained and checked
Boolean
—
Opt
The Labor Contractor Employee Report has been submitted
Boolean
—
Opt
The required report or reports were submitted by the second Wednesday in May
Boolean
—
Opt
The Payroll Employee Report has been submitted
Boolean
—
Opt
Employer
String
—
Req
An authorized official certified the required report or reports
Boolean
—
Opt
Labor-contractor employees during the selected snapshot period, including integrated affiliates and workers outside California
Number
—
Opt
Calendar year covered by the report
Number
—
Req
Reason the pay-data submission was late
String
—
Opt
Labor-contractor employees supplied on a recurring basis, including integrated affiliates and workers outside California
Number
—
Opt
At least one labor-contractor employee worked in California
Boolean
—
Opt
The organisation is a private employer
Boolean
—
Req
The California employee rows and establishment assignments are complete
Boolean
—
Opt
At least one payroll employee was assigned to a California establishment or regularly worked in California
Boolean
—
Opt
Payroll employees during the selected snapshot period, including integrated affiliates and workers outside California
Number
—
Opt
Payroll employees employed on a recurring basis, including integrated affiliates and workers outside California
Number
—
Opt
The business used workers supplied by a labor contractor
Boolean
—
Opt
The current CRD handbook, FAQ, templates, and deadline have been checked
Boolean
—
Req

Example payload

JSON 
{
  "responses": {
    "pay_demographic_hours_and_status_data_complete": false,
    "integrated_enterprise_status": "",
    "labor_contractor_data_obtained": false,
    "labor_contractor_report_submitted": false,
    "submitted_by_second_wednesday_in_may": false,
    "payroll_report_submitted": false,
    "employer_name": "",
    "reports_certified": false,
    "labor_contractor_employees_in_snapshot_period": null,
    "reporting_year": null,
    "submission_delay_reason": "",
    "labor_contractor_employees_regularly_employed": null,
    "at_least_one_california_labor_contractor_employee": false,
    "private_employer": false,
    "california_rows_and_establishments_complete": false,
    "at_least_one_california_payroll_employee": false,
    "payroll_employees_in_snapshot_period": null,
    "payroll_employees_regularly_employed": null,
    "client_employer": false,
    "current_crd_handbook_checked": false
  },
  "effective_at": "2026-07-26"
}

The request body this schema expects. Fill in responses and keep the field IDs unchanged. Validation becomes callable after you use this release in a published Flow.

API usage

Create a Flow from this schema, then replace the route placeholders with that Flow's organization and address. Validation is free and runs against the exact release bound to the Flow. It returns the engine's resolved fields and legal time period when ready, or a structured error with field-level issues.

cURL 
curl -X POST https://proseid.com/api/v1/validate/{your-org}/{flow-slug} \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d @payload.json
200 OK
{
  "valid": true,
  "status": "READY",
  "definitions": { ... },
  "issues": [],
  "effective_at": "2026-07-19",
  "temporal_context": {
    "logic_version": "current",
    "valid_range": ["2026-01-01", null]
  }
}
422 Invalid
{
  "error": {
    "code": "validation_failed",
    "message": "the document did not pass validation",
    "details": {
      "status": "INCOMPLETE",
      "issues": [{
        "field_id": "pay_demographic_hours_and_status_data_complete",
        "kind": "missing_required",
        "severity": "error",
        "trigger": "completion",
        "message": "Required field is missing"
      }]
    }
  }
}
A completed webhook also depends on the Flow's experience, signing, pricing, and delivery settings. Create a Flow with this schema, then use Send sample completion in its delivery settings to receive the full signed JSON without using your balance. Webhook guide

Published versions

Permanent, attributable versions
Loading published versions…

Trust ledger

Crowd → credentialed
P
Provenance
Community publisher (unverified)
@proseid · latest v2026.07.26
Community signal
0
0 votes

No votes yet.

Attestations · by version
0 total

No attestations yet. A verified professional can vouch for a specific version.

Discussion

0 comments
to join the discussion.
Continue exploring
Browse all records →
v2026.07.26

FDA food-facility registration determination

@proseid · 17 fields

 v2026.06.19

EU right-of-withdrawal record

@proseid · 25 fields

 v2026.07.24

EU whistleblowing internal-report deadlines

@proseid · 48 fields

 v1.0.0

OSHA fatality or severe-injury reporting determination

@proseid · 19 fields