Overview
HRIS syncing enables an organization to automatically sync your employee directory from your HR system to Teampay.
Attributes that should sync:
- First, Last Name
- Job Title
- Work Email
- Active Status (Onboarding/Offboarding)
- Location*
- Department*
- Auth Type
- Manager
- Role
*Will only sync if they already exist in the accounting integration
Compatibility
The following HRIS systems are supported for integration:
Getting started
As an Admin, navigate to the top right corner of Teampay to select 'Organization Settings'. From here, you'll see the option to Connect within the 'HRIS System Connect' section.
From here, you can select the HRIS system you will be integrating with Teampay.
Once connected, user attributes and requester groups will sync over to Teampay every 6 hours once the connection is established. HRIS syncing attributes can vary depending on the system, so if you have specific questions reach out to support@teampay.co.
Automated Rule Creation
Teampay can create automated rules for the following HRIS software:
- BambooHR
- AlexisHR
- Breathe
- Ceridian Dayforce
- Charlie
- Charthop
- CyberArk
- Deel
- Employment Hero
- Factorial
- Freshteam
- Gusto
- Hibob
- HRCloud
- HR Partner
- Humaans
- Insperity Premier
- IntelliHR
- JumpCloud
- Kallidus
- Keka
- Kenjo
- Lucca
- Namely
- Officient
- OneLogin
- Paychex
- Paycor
- Paylocity
- PeopleHR
- Personio
- Proliant
- SageHR
- SAPSuccess
- TriNet
- TriNetHR
- UKGPro
- UKG Workforce Management
- UKGReady
- Workday
Automated Rule Behavior
Building rules in Teampay can be manual and take some time. That is why we can automate the first step of approvals for you!
Any time any employee puts in a request, it will go to their manager first. We will keep this dynamically updated based on what your org chart says so you don’t have to worry about keeping that up to date on the Teampay side!
For example, without rules automation, you may have groups created in Teampay for each department. With this automated first level of approvals, you don’t need them!
Comments
0 comments
Article is closed for comments.