---
title: "Create the enrollment profile"
method: PUT
path: "/companies/{company}/enrollment_profile"
---

# Create the enrollment profile

`PUT /companies/{company}/enrollment_profile`

## Request

- Base URL: `https://sandbox.checkhq.com`
- URL: `https://sandbox.checkhq.com/companies/{company}/enrollment_profile`
- Auth: API key in header `Authorization`
- TypeScript: <https://skmtc.dev/checkhq/apis/check-api/docs/companies/:company/enrollment_profile/put.ts> (a function with typed inputs; its response is checked against the schema)

Create the enrollment profile for the company

## Request body

- object
  - `employee_count` integer: Number of payees who are W2 employees
  - `contractor_count` integer: Number of payees who are 1099 contractors
  - `pay_period_amount` string: Estimated total amount of money paid to employees and contractors per pay period
  - `previous_payroll_provider` 'accupay' | 'adp_enterprise' | 'adp_payforce' | 'adp_pcpw' | 'adp_run' | 'adp_totalsource' | 'adp_workforce_now' | 'benefit_mall_compupay' | 'cbiz' | 'ceridian' | 'emangrove' | 'evolution' | 'execupay' | 'gusto' | 'heartland_payroll' | 'isolved' | 'microsoft_dynamics_gp' | 'mint' | 'netpay' | 'onpay' | 'patriot' | 'paychex_flex' | 'paychex_go' | 'paychex_preview' | 'paycom' | 'paycor' | 'paydayonesource' | 'payrollmatters' | 'payroll_people' | 'paylocity' | 'payworks' | 'prime_pay' | 'proliant' | 'quickbooks_online' | 'quickbooks_desktop' | 'rasi' | 'rippling' | 'sage_100' | 'sage_300' | 'sage_hr' | 'square_payroll' | 'sure' | 'toast' | 'trinet' | 'trupay' | 'ultipro_online' | 'ultipro_pc' | 'wave' | 'zeal' | 'zendona' | 'zenefits' | 'manual' | 'accountant' | 'other': The payroll provider previously used by the company
  - `previous_payroll_provider_other` string: A custom label for the previous payroll provider, if the previous payroll provider is not available in the above set of options.
  - `first_payroll` boolean: Whether or not the company has ever paid people before.
  - `first_payroll_of_year` boolean: Whether or not this is the first payroll of the current calendar year for the company
  - `user_since` string, date: The date at which the company joined the partner's platform
  - `expected_first_payday` string, date: The company's expected first payday on Check
  - `approved_for_payment_processing` boolean: Whether or not the company has been approved for payment processing on the partner's platform
  - `existing_payroll_customer_processing_period` string: If business is already running payroll with you, the processing period they are currently using. One of `null`, `four_day`, `two_day`, or `one_day`.
  - `average_monthly_revenue` number, float: The average monthly revenue of the company
  - `earliest_known_revenue` string, date: The earliest known date that the company generated revenue
  - `months_on_previous_payroll_provider` integer: The number of months that the company used their previous payroll provider
  - `social_media` string[]: Any social media account URLs associated with the company
  - `products_actively_used` string[]: A list of the products offered by the partner's platform used by the associated company. Values must be one of `timetracking`, `payments`, or `scheduling`.
  - `account_contacts` string[]: A list of partner employee emails associated with the company
  - `fraud_score` number, float: A value between 0 and 100 representing the fraud risk presented by the company
  - `predicted_fraud` boolean: Whether the fraud score was over the expected threshold for fraud (the company is predicted to be fraudulent)
  - `paying_user` boolean: Whether the company pays the partner for services
  - `missed_payments_count` integer: The number of times that the company has failed to pay the partner
  - `payroll_history_access_method` 'authorized_access_to_previous_provider' | 'provided_credentials' | 'provided_reports': The mechanism by which Check Implementation Services will be able to access and migrate payroll history
  - `implementation_services_submission_comment` string: Optional comment for including additional context when submitting a company for Implementation Services

## Response `200`

200

## Other responses

- `400`: 400

## Changes

- **2026-11-03** `5a54f5eb888b`: 7 info
  - added the new `other` enum value to the request property `previous_payroll_provider`
  - added the new `paychex_go` enum value to the request property `previous_payroll_provider`
  - added the new `paydayonesource` enum value to the request property `previous_payroll_provider`
  - added the new `rasi` enum value to the request property `previous_payroll_provider`
  - …3 more

[Operation history](https://skmtc.dev/checkhq/apis/check-api/changes/companies/:company/enrollment_profile/put.md)

---

[API](https://skmtc.dev/checkhq/apis/check-api.md) - [All operations](https://skmtc.dev/checkhq/apis/check-api/llms.txt) - [OpenAPI document](https://skmtc.dev/checkhq/apis/check-api/revisions/5a54f5eb888b?raw)