@proseid v2026.07.26 SE

Swedish posted-worker reporting determination

Determines the immediate reporting, contact-person, proof-delivery, recipient-notice, update, and long-term-posting actions for a worker sent to perform a service in Sweden.

Compatible with

FormGuided assessmentDeterminationCompliance checklistAPI

Use Schema in a Flow

Publication

Protocol: Proseid_v1.0
Version: v2026.07.26
Applies in: Sweden
Fields: 17
Flow price: $0.20
Publisher fee: None

Legal history

Time periods

se_posting_20262026-01-01 → continues indefinitely

Current

Controlling sources

Legal references

Lag (1999:678) om utstationering av arbetstagare 4–5 f §§ and 29–33 §§

Source ↗

Förordning (2017:319) om utstationering av arbetstagare 7–13 §§

Source ↗

Swedish Work Environment Authority — posting guidance Report a posting; recipient and contact-person duties

Source ↗

Schema fields

17 fields

Field

Type

Description

Req

A reasoned notice extending the 12-month point was submitted on time

Boolean

—

Opt

The recipient notified the Authority that proof was missing

Boolean

—

Opt

The recipient is a private individual receiving the service for personal use

Boolean

—

Opt

The employee will perform a service for a recipient in Sweden

Boolean

—

Req

The employer reported the posting

Boolean

—

Opt

Whose duty are you checking?

Select

Choices: Foreign employer, Swedish service recipient

Req

First day of work in Sweden

Date

—

Req

The recipient received proof that the posting was reported

Boolean

—

Opt

A contact person available in Sweden has been appointed

Boolean

—

Opt

Total posting period in months

Number

—

Req

Information in the posting report has changed

Boolean

—

Opt

Calculated next action

Select

Choices: Outside ordinary posting scope, Use road transport assessment, Report before work starts, Appoint contact person, Give proof to recipient, Recipient notify within three days, Update posting report, Review long term conditions, Posting record current

Opt

The worker's employer is established outside Sweden

Boolean

—

Req

The work in Sweden has a planned start and end

Boolean

—

Req

The person is an employee rather than self-employed

Boolean

—

Req

The posting report was updated without delay

Boolean

—

Opt

How is the worker being sent?

Select

Choices: Service contract, Within company group, Hired out, Road transport driver, None of these

Req

Example payload

JSON

{
  "responses": {
    "reasoned_extension_notice_submitted": false,
    "recipient_notice_submitted": false,
    "recipient_is_private_personal_customer": false,
    "paid_service_in_sweden": false,
    "employer_report_submitted": false,
    "assessment_role": "",
    "work_start_date": "",
    "proof_given_to_recipient": false,
    "contact_person_appointed": false,
    "posting_months": null,
    "report_information_changed": false,
    "foreign_employer": false,
    "limited_period": false,
    "worker_is_employee": false,
    "report_updated": false,
    "posting_arrangement": ""
  },
  "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": "reasoned_extension_notice_submitted",
        "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

Provenance

Community publisher (unverified)

@proseid · latest v2026.07.26

Community signal

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.

Time periods

Legal references

Schema fields

Example payload

API usage

Published versions

Trust ledger

Discussion

FDA food-facility registration determination

EU right-of-withdrawal record

EU whistleblowing internal-report deadlines

OSHA fatality or severe-injury reporting determination