How to fix unmapped time off errors

Prerequisites 

• You have Admin access to your organization’s HRIS account.
• You are logged in to the Oyster Platform with your admin credentials.
• You have connected your HRIS to Oyster.

What are unmapped time off errors

Unmapped time off errors happen when Oyster imports a time off request where there is no match between the time off policy types in Oyster and your HRIS. Unmapped requests lead to payroll issues since there is not enough information for our payroll team to properly process the leave. This is why they need to be addressed before the 15th of the month. 

How to resolve unmapped time off errors 

1. On the Oyster Platform, click Company > Integrations.
2. Select the My integrations tab.
3. Click Settings for your HRIS integration. 
4. Go to the Mapping tab and click edit
5. To see which time off types are unmapped, simply click into any of “type” boxes 
   
   • The types without a check are the ones currently unmapped. In the example above the three unmapped types are Bereavement, Comp in lieu time, Fmla.
6. Map your HRIS type to closest Oyster type
7. If there is no match, you can create a custom match only for the “Other (paid)” and “Unpaid leave” types in Oyster 
8. Expand the subtype for the corresponding type, scroll to the bottom and click Create custom subtype
9. Select the fields you’d like to create a custom subtype for and click create
   

10. Once you’ve created the necessary custom subtypes, click Save changes
    

    Pay special attention to whether the custom subtypes you’re creating are for the “Other (paid)” or “Unpaid leave” types. Creating a custom subtype for the incorrect type will lead to payroll error for your Team Members!

11. Once you have mapped all the necessary fields, the error will be resolved. This will be confirmed since you’ll no longer see a warning badge

Additional information

• Every time Oyster receives an unmapped time off request we send an email notification to all company admins to alert them of the error
  • If the error has not been addressed, a reminder notification is sent 
• If one of your HRIS policy types is “other” please try to match it to the closest subtype in Oyster instead of creating a new custom subtype that uses the term “other”
• Please remember to match even time off types that are not currently being used in your HRIS with any Oyster type. This will help prevent unnecessary notifications and allow for easy access if they are needed at a later time.
• You might notice a discrepancy between the time of types you see in your HRIS and what options you see to map in Oyster. We do not import the entire policy list directly from your HRIS, Oyster only receives time off types from your HRIS once a request has been made using that policy type. For example if you have a time off type called "Long term sick leave" and no requests have ever been made with that type before, it won't be visible to map in Oyster. Once a team member requests leave with that type, we'll import that as unmapped. Once you've mapped it all future requests with "Long term sick leave" will be properly mapped in Oyster.

Ready to Learn More?

• Sign up for Free
• Preview the Platform