CSV Hiccup (Paylocity HRs)

Avalon Toth

Any other users in here also use Paylocity? I would love to pick your CSV brain if so.

We have had to sadly manually manage more and more due to issues repeating on the HRS side so I am curious if anyone else has worked out that hiccup?

 

0

Comments

1 comment

Date Votes
  • Comment author
    Mark Rini
    • Official comment

    Hi Avalon, 

    CSV hurdles with Paylocity often boil down to specific Mapping settings, or data validation that is unique to your account setup. Based on common issues we see with HRIS data imports, here are a few things that might be causing issues:

    • Unique Identifier (UID) Gaps: Whether Bridge is trying to use an "Email" field or another unique ID string, any blank entries in that column will raise an error for that row/User.
    • Mapping Mismatches: If you recently transitioned from another HRIS or changed how IDs are structured, Bridge can help update Users to their new IDs and prevent issues such as duplicate users. 
    • Automation Settings: Even if moving away from AutoCSV, Bridge can help you ensure that ‘manual’ CSV imports are mapped to align with your intentions. Or, maybe you are finding some gaps in the information available from your Paylocity data, but that doesn't mean that other automation options aren't available to admins for managing enrollments. 

    Below are some helpful Bridge community resources -- if you are an Account Admin I'd recommend reaching out to Support or your Account Manager for more assistance with specific errors. Or hop into Office Hours to strategize on new enrollment logic with the data you have available from Paylocity!

    CSV Requirements + Best Practices

    AutoCSV Documentation

Please sign in to leave a comment.