Developer FAQs

Employee Sync

What is the value of syncing employees between our platform and Gusto?

Employee sync is a tremendous value add as it allows users to easily onboard new staff members in either system, simplifying their workflows and saving them time. This reliable and quick sync of staff info between the two systems creates a more robust product offering leading to additional customer adds

What is ‘Employee Reconciliation’? Why do you require that employees be matched between the two systems?

Employee reconciliation is the ability to match the same employees between your system and Gusto. We require that employees be matched based on at least 2 criteria to ensure we are talking about the same people (email address, date of birth, or full name).

Why do you require the ability for user’s to manually match or review the employee reconciliation done by the API in the UX?

This allows users to confirm the right people are matched and make changes, ignore, or create based on what the integration originally suggested. We’ve found that this cuts down on the number of errors and drastically improves the user experience.

Once an employee is created in Gusto via the API, what happens next?

Once an employee is created, they will appear under the Hiring tab in Gusto for a company admin to complete their onboarding. Onboarding must be completed prior to paying an employee through Gusto since we need specific information to process payroll (e.g W-4 tax info and payment preferences).

Do you support multiple jobs and pay rates?

Yes, we do. Jobs for each employee can be pulled, updated, or created (key for time tracking and pay rates). Information includes: Work Location, Hire date, Title (or Role), Pay rate, Compensations or effective dating of pay rates (great for budgeting, calculating staff costs) .

Our concept of a “job” may be different from yours and this needs to be accounted for in your integration build. In Gusto, jobs are essentially the intersection of an employee, a compensation, and a company work location. All jobs will also have corresponding IDs associated with the aforementioned employee ID numbers. Each job will have a corresponding compensation amount/ID. One Job ID will not span across multiple employees – each Job ID is unique to an employee ID.

How can I create a job ID and compensation for an employee?

A job ID is unique to an employee ID so in order to create a job ID for an employee, send a POST request to /v1/employees/:employee_id/jobs. You can include “title,” “hire date”, “payment_unit”, “flsa_status”, and “location_id” in your body, among other things. Use “payment_unit”: “Hour” for hourly and “payment_unit”: “Year” for salary. The return response will include a “rate” of ‘0.00’ which you can then update via PUT request to /v1/compensations/:compensation_id.

Previous: Production Access | Next: PUT Payrolls

Main Menu