Terms related to Payroll hub settings, statuses, and integrations.
FYI: This module is available only for accounts that have purchased Payroll hub. To learn more, see Payroll hub.
Set up a pay cycle
Set up one or more pay cycles to fit your company's needs. To learn more, see Set up a pay cycle.
Cycle starts on date
The first day of the pay cycle.
Pay cycle owner
The person or people in your organization who will receive the notification to review the specific pay cycle notifications before it closes.
The day the organization pays the employees included in the specific pay cycle set as a certain number of days after the cycle ends. This cycle is included in the Open cycles page, after the pay day, it will be moved to the Closed cycles page.
How often the pay cycle is completed, which can be either monthly, semi-monthly, bi-weekly, or weekly.
The day set on or before the cycle’s end date for the pay cycle owner(s) to manage and sync the data between Bob and the payroll system.
The system to which you’ll send the payroll information from Bob. You send your information to either an out-of-the-box integration or a custom connection via Bob’s Payroll Connect
Three types of reports can be synced to the target payroll system.
People who recently joined your organization.
Updates to personal, employment, or payroll information.
People who are permanently leaving your organization and need to be removed from the payroll system.
Pay cycle settings
A pay cycle accessible in the Payroll hub that will be filled with employee data.
A pay cycle not accessible in the Payroll hub that will not be filled with employee data, but can be restored to a pay cycle later if needed.
A pay cycle not accessible in the Payroll hub that will not be filled with employee data, and cannot be restored to a pay cycle later.
A pay cycle not accessible in the Payroll hub that will not be filled with employee data.
Payroll hub cycle statuses
Payroll dashboards show the cycle name, status, cycle range, review date, and pay day.
A cycle range is the first to the last date of each pay cycle. The cycle opens on the range’s first day and closes on the last day. Once the pay day of the cycle has passed, it will move to Closed cycles, where it can still be synced to the payroll system.
A cycle that has ended and can no longer be acted upon but can be reviewed via a downloadable report. Its data may still be synced to the payroll system or reviewed via a downloadable report.
A cycle to which relevant employee data is inputted into the appropriate pay cycle reports.
Pending review status
A cycle that is about to close and requires the pay cycle owner’s review and action before its end date.
These fields or values need to match between Bob and your payroll integration.
A constant value used by your payroll system, e.g., a company code that will be the same value in every employee’s mapped field in your payroll system.
A blank value if the field needs to transfer an empty value to the payroll system each time the data transfers.
A field in your payroll system settings that should have the exact match with a Bob field, e.g., email field in the payroll system should get the value of the email field in Bob.
Source in Bob
The employee field(s) from the Bob list values are derived from.
A value mapping list that has been mapped in the previous value mapping step that best matches the field, e.g., Job title value mapping list for mapping the job titles in Bob to the list of job titles in the payroll system.
Test API connection notifications
When you test the connection of a Payroll API integration, you will receive a notification on the connection status.
The integration is connected, and employee information will be synchronized with the integration.
The integration is not connected, so employee information will not be synchronized with the integration.
Couldn’t Connect all Companies
One or more organizations using the integration are not connected, meaning there is only a partial connection.