Company Instances & Multiple EINs

In Everee, each legal business entity runs in a dedicated Company instance. That means each EIN (Employer Identification Number, used for tax and compliance purposes) has one Company instance.

Clients who operate multiple legal business entities (multiple EINs) will be set up with one Company instance for each entity/EIN, with different API tokens for each entity/EIN.

This allows us to isolate data associated with each EIN into its own instance, which allows each EIN to run different configurations and report data in a clear and straightforward way. Any time a client operates multiple EINs (and therefore has multiple Everee instances), all instances are listed in the "Company picker" dropdown menu in the upper right of the admin portal.

Managing API access for multiple Company instances

From an integration perspective, this scenario means each Company instance has a separate API token and x-everee-tenant-id header value. See Authentication & API Tokens for more information about these values.

An API token is tied to one company instance and grants access only to that instance. When you're building your integration, if you want to support multiple EINs (or Company instances), you must store an Everee API token and an ID for each EIN, and select the appropriate API token and ID for each request to perform operations for each EIN (or Company instance).

That may mean that you need to create additional links in worker data tables, timesheet data tables, and other areas of your platform, to correctly associate worker and wage data with its EIN and Everee Company instance.

📘

We can help you plan for this!

We help clients design their Everee integrations all the time. If you need to account for multiple EINs in your integration, please reach out to your account manager or [email protected] and we'll be happy to help.