Connecting Plan Sponsors with Multiple Entities in Relius

How a single Finch Connect link supports multi-entity plan sponsors in Relius, and when to generate additional connections.

A single Finch Connect link is sufficient for plan sponsors with multiple entities. An entity is a grouping of employees within a payroll system, such as an EIN, company code, division, or location, as configured by the employer in their payroll provider. During authentication, the plan sponsor selects which entities to connect. They can select one or more, depending on which entities have employees eligible for the plan. After the connection is established, you work with each entity individually within Relius using the entity selector on the Payroll Mapping, API Explorer, and Integration tabs.

How entity selection works in Finch Connect

When the plan sponsor goes through Finch Connect, they will see a list of entities available under their payroll provider credentials and select which ones to connect. They can select one or more entities in a single session.

Plan sponsors may choose not to select all entities. For example, if certain entities contain employees who are not eligible for the plan.

Once connected, each selected entity is available via the entity selector on the relevant tabs in Relius:

• Payroll Mapping — configure field mapping per entity

• API Explorer — view data for a specific entity

• Integration — manage settings per entity

Payroll mapping and configuration must be completed separately for each connected entity.

Files, Plan IDs, and Sequence IDs per entity

Each connected entity generates its own file containing only the employees associated with that entity. A connection with five entities will produce five separate files.

When completing payroll mapping and configuration for each entity, you can use the same Plan ID and Sequence ID across entities, or assign different values depending on your setup. Ensure that Relius is set up correctly to accept multiple files if they do have the same plan id, frequency, and sequence id.

When to generate additional Finch Connect links

One connection handles the typical multi-entity case. Generate a new Finch Connect link with a unique customer ID in these situations:

• Multiple payroll providers. If the plan sponsor's entities are spread across different providers, each provider requires a separate connection.

• Limited credentials. If the person completing Finch Connect does not have access to all entities under their credentials, they will need to complete the flow again with credentials that cover the remaining entities.

When creating additional links, the customer ID does not need to match anything in Relius or the payroll provider. It is only used to identify connections in your Finch Dashboard. Use whatever naming helps you distinguish them. A common pattern is to append the provider name or a sequence number to your existing customer ID (e.g., acme-adp, acme-gusto, or acme-001, acme-002).

Notes on customer ID and customer name

The customer name and customer ID you enter when creating a Finch Connect link are not visible to plan sponsors. They appear only in your Finch Dashboard, where you can use them to track connection progress. Once a plan sponsor has authenticated and data has synced, the Dashboard will also show the company name as it appears in their payroll provider.