Overview

In the Paylocity product suite, companies are classified in two ways: Company Sets and Companies.

1. Companies: These are individual entities within Paylocity software, each identified by a unique Company ID (COID). A Company ID is specific to each Payroll Entity, meaning each company that uses Paylocity software to manage payroll has its own distinct identifier.
   1. Not all Companies are part of a Company Set: Companies that operate independently without the need to manage separate locations or entities do not belong to a Company Set. These companies use a single EIN and handle payroll and other functions within the Paylocity application suite without the need for additional separation.
2. Company Sets: These are groups of companies that share a central location for management. Each Company Set is identified by a unique Company Set ID (CSID). A key feature of a Company Set is that it allows users to access multiple companies with a single login, simplifying navigation for Multi-Company Admin users.
   1. Why use a Company Set?
      1. If a company needs to manage payroll separately for different Employer Identification Numbers (EINs) within the same group. Please note: some companies within a company set use all of the same EINs or a few different EINs.
      2. If a company operates multiple locations (e.g., a fast-food franchise with each location having its own Company ID) and requires distinct functionalities for each location.

Important Note on API Integrations: Onboarding Company IDs

For certain integrations, such as the Background Check API and the Assessments API, each Company ID within a Company Set must be onboarded individually to ensure proper functionality within the Paylocity suite.

• Why this matters:
  • These APIs do not accept Company Set IDs (CSIDs) as valid identifiers.
  • Attempting to use a Company Set ID will result in an error, preventing the API from functioning correctly.

Action Required: Partners must work closely with clients to obtain and onboard every relevant Company ID within the Company Set. This step is crucial for the successful implementation of these integrations.

Example flow for Partner APIs

Understanding company set use-cases

Some examples of reasons a client-team might want to introduce a Company Set structure instead of a single Company ID:
• A franchise might want to differentiate per “Work Location” (brick and mortar building)
• An organization might want to differentiate per Financial Cost-Center or Labor Allocation (Factory Workers vs. Office Workers)
• An organization might want to delineate their Employee Types (W2 vs 1099s vs K1)
• An enterprise organization might want to differentiate per “Region”
• An enterprise organization might want to delineate their “Hourly” vs “Salary” records
• An enterprise organization might want to differentiate per “Tax Entity/FEIN”

Test Scenarios