Cost center inheritance

Updated 3 weeks ago by Nilas Hedin

In Quinyx, it's possible to select a cost center manually on shifts and punches. This is a way of overriding the automatic cost center inheritance logic that's applied when extracting salary files or reports. The automatically inherited cost center is also visible in Schedule items in the Time card.

If the punch is connected to a shift and cost center has not been selected manually on the punch, cost center should be inherited from the first hierarchical entity on which it has been defined, in this order:

  • The cost center selected on the shift
  • The section the shift belongs to
  • The unit the shift belongs to
  • The employee (as specified in the employee card)
  • The section the employee belongs to
  • The unit the employee belongs to
  • The region the employee belongs to

If the punch is not connected to a shift, cost center should be inherited in this order:

  • The employee (as specified in the employee card)
  • From the unit the punch belongs to, through the employee
  • The section the employee belongs to
  • The unit the employee belongs to
Base schedule exception

The cost center inheritance logic does not apply if the user has a base schedule rolled out that does not have a cost center connected to the shifts.

This means that the cost center inheritance logic above does not apply at all if the user has a base schedule rolled out.

Scenario

An employee has rolled out shifts that are all missing a cost center. In this case, the unit card's cost center does not display on the shifts because the base schedule doesn't have any cost centers connected to the employee's shifts.


How Did We Do?