Skip to main content
Question

Customer Hierarchy

  • March 19, 2026
  • 2 replies
  • 32 views

Forum|alt.badge.img+1

R25.1 Update 3 On customer hierachy i can create hierarchy levels but I cannot connect customers to a level. The hierarchy is then defined by which customer are connected to which 
Ex. Hierarchy Root level = Main
Connected customer, concern cusotmer becomes level 1
one or more connected customer to the concern then becomes level 2
A customer can be connected to a customer in level 2 and then becomes level 3

But in Rebate agreements I can only connect to the Root level and the calculation does not work. In the tabel rebate_transaction the invoiced line is added, but without any calculation. 
It works when I dont use customer hierarchy. 
For my example I have used a very limited setup. Part based on one specific part, and with Amount on sold quantity. 
Any idea as to what the problem might be?

2 replies

Lingesan08
Hero (Partner)
Forum|alt.badge.img+9
  • Hero (Partner)
  • April 6, 2026

R25.1 Update 3 On customer hierachy i can create hierarchy levels but I cannot connect customers to a level. The hierarchy is then defined by which customer are connected to which 
Ex. Hierarchy Root level = Main
Connected customer, concern cusotmer becomes level 1
one or more connected customer to the concern then becomes level 2
A customer can be connected to a customer in level 2 and then becomes level 3

But in Rebate agreements I can only connect to the Root level and the calculation does not work. In the tabel rebate_transaction the invoiced line is added, but without any calculation. 
It works when I dont use customer hierarchy. 
For my example I have used a very limited setup. Part based on one specific part, and with Amount on sold quantity. 
Any idea as to what the problem might be?

@BenteRas ,

From what you describe, this is likely due to how rebate agreements are evaluated in IFS.

Customer hierarchy itself can be defined with multiple levels, but rebate calculation does not automatically consider hierarchy relationships. The engine typically evaluates transactions based on the specific customer linked to the agreement, not parent/child relationships.

This is why:

  • Transactions are created in rebate_transaction

  • But no calculation is triggered when using hierarchy

A common approach is to use Customer Groups instead of hierarchy for rebate agreements, assigning all relevant customers to the same group and linking the agreement to that group.

Alternatively, agreements need to be defined per customer if hierarchy is required, or a custom solution would be needed to support hierarchy-based evaluation.

Would be good to hear if others have handled this differently.

Thanks


Forum|alt.badge.img+1
  • Author
  • Do Gooder (Partner)
  • April 8, 2026

@Lingesan08 

I found out that you can actually use Customer Hierarchy but the setup of the Hierarchy is a bit strange.

Ex. Hierarchy Root level = Main
Connected customer, concern customer becomes level 1
One or more connected customer to the concern then becomes level 2
Now you have to go the the Hierarchy Root level and add hierarchy levels matching the levels 1-2- 



Then on the Rebate setup
Agreement type must be chosen - in my case it is All Sales Parts
Use Hierarchy must be set to Yes and a hierarchy must be chosen. 
and finally on the tab for Deals you have to setup the Rebate per level in the hierarchy. 


On the Receivers tab the Customer owning the hierarchy must be setup. 
And now it works.

The problem, it turned out, was just the hierarchy setup as the hierarchy levels is not a demanded setup, but without them you cannot allocate the rebate.

Thanks for your input, I hope my solution can be of any help.