PeopleMatter Support: 1-877-354-2266
Monday-Friday 8:30 AM-8:30 PM EST

Knowledge Base

Hi! We've moved the Knowledge Base to make it better for you. Check it out here.

This site isn't being updated anymore but will be available until January 24.

I need help with…

What is meant by mapping separations for MICROS

Nick -

When configuring your MICROS integration with PeopleMatter the support representative may ask if you wish to map separations. This process allows someone who is separated from PeopleMatter to then be seamlessly separated from MICROS. MICROS refers to these as reasons FOR termination within its system. 

In order for this to work the native separation reasons within PeopleMatter must be mapped correctly with the termination reasons in MICROS. PeopleMatter has 32 separation reasons available to choose from. Mapping these properly require that a termination reason number (from MICROS) be assigned to each reason from PeopleMatter.

This does not need to be a strict 1:1 match, however it can be. The only requirement is that a reason from MICROS is assigned to every row from PeopleMatter. 


1) In the example below we have three sample separations from People Matter matched with the termination reason numbers from MICROS. The MICROS administrator has decided to create termination reasons labeled; Abandoned Job #4, New Job #1, and Compensation #5. To align these reasons up with the corresponding PeopleMatter reason the number is assigned on the same row in the next column. 

2) In the example below the same three separation reasons from PeopleMatter have been matched with only one termination reason from MICROS. The administrator has created only one termination reason labeled Inactive #1. With only one reason created, the same number will be used on every row. 

The main point is that as long as a reason in attached with the PeopleMatter reason, any MICROS termination reason(s) can be assigned.