Customers can connect their HRIS integration to AllVoices. Common HRIS systems include: Workday, BambooHR, ADP, UKG, Rippling, Gusto, Namely, Oracle HCM, Paylocity.
If you're having any issues with your integration, use this guide to troubleshoot the most common HRIS (Human Resources Information System) issues in AllVoices.
If your employee data isn’t syncing as expected, you're receiving errors, or need help diagnosing an issue with your integration, this guide applies.
What Usually Causes Integration Issues
Most HRIS integration issues are caused by:
- Permission settings in your HRIS
- Field mapping or configuration
- Sync timing and processing delays
Use the steps below to diagnose and resolve the issue.
Step 1: Confirm the HRIS Integration Is Fully Connected
First, confirm that the integration itself is active.
Check in AllVoices:
- The HRIS integration shows as Connected
- No authentication or permission errors are displayed
If the integration is not connected:
- Re-authenticate the HRIS connection
- Confirm credentials were entered by an HRIS administrator
If the integration cannot be connected after re-authentication, contact AllVoices Support.
Step 2: Understand Sync Timing
HRIS data does not sync instantly.
What to expect:
- Initial syncs may take several hours
- Ongoing updates sync on a scheduled interval
- New employees or field changes may not appear immediately
If you’re not seeing data yet:
- Wait at least 24 hours after initial setup or major HRIS changes
- Confirm no errors appear in the integration status
If data still does not appear after 24 hours, continue to Step 3.
Step 3: Check HRIS Permissions & Scoping
If some employees or fields appear but others do not, this is almost always a permission or scoping issue in your HRIS.
In your HRIS, confirm:
- All relevant employee records are included in the integration scope
- Required fields (such as department, region, or cost center) are accessible
- The integration user has permission to read those fields
Common reasons data is missing:
- Field-level permissions are restricted
- Custom fields are not enabled for integrations
- Scoping rules exclude certain employee groups
If permissions or scoping were updated, allow time for the next scheduled sync.
Step 4: Validate Field Mapping Expectations
AllVoices can only ingest data that:
- Exists in your HRIS
- Is populated consistently
- Was mapped during integration setup
Important notes:
- Blank fields in your HRIS will remain blank in AllVoices
- Renaming fields in your HRIS does not automatically remap them
- Structural changes may require reconfiguration
If field mappings need to be adjusted, contact AllVoices Support.
What’s Expected vs. Not Expected
This is expected behavior:
- New employees do not appear immediately
- Changes take time to reflect
- Some fields sync while others do not due to permissions
This is not expected behavior:
- The integration shows as connected but no data ever appears
- Syncs fail repeatedly with errors
- Data appears incorrect or corrupted across all records
If you’re experiencing one of the issues above, contact AllVoices Support with details about your HRIS system and what you’re seeing.