Use this glossary to familiarize yourself with terminology used in Finch’s documentation and API reference.
payroll_provider_id
.
connection_id
. If an employer has multiple sub-entities within their payroll system, these may be represented as multiple connections with different connection_id
. You can use the EIN or Legal Name that returns in the /company
endpoint to reconcile your records internally.
individual_id
. Contractors are also considered individuals.
connection_id
. Therefore, an employer may have one or many connections depending on if the employer is made up of sub-entities.
client_id
and client_secret
credentials that enable you to launch Finch Connect and receive access tokens. An application essentially groups your connections with your Finch “environment”. Finch has three environments: sandbox, testing, and production. The sandbox application connects only mock providers. The testing application connects live providers, but in a limited capacity. The production application connects live providers without any limitations.
authentication_methods
field on the Providers endpoint of the API.
job_id
.
payment_id
.
payment_id
.
gross_pay
found on the pay statement.