Articles on: Data audit and adjustment
This article is also available in:

Manage parent/child hierarchies

What is the parent / child relationship for?


Some of your customers belong to the same group: a parent company and its subsidiaries, several legal entities of the same company, or distinct brands billed separately. In Fincome, you can link these entities by associating a parent customer with one or more child entities.


Once the relationship is created, all calculations (MRR, ARR, churn, etc.) are performed at the parent customer level. You thus get a consolidated view of the group, without losing the detail: each child remains viewable, and the parent record displays the breakdown of its MRR entity by entity.



How to link an entity to a parent


The logic is always the same: a child entity is attached to a parent customer. If the parent does not yet exist as a customer in Fincome, create it first, then make the link. You can proceed in four ways.


1. From the interface, customer by customer


This is the quickest method for a one-off attachment (the principle is the same as for merging customers). Two entry points are possible.


From the customer list:

  1. Go to Data > Customers.
  2. Hover over the customer to attach (the child): an "Edit" button appears.
  3. Click the "…" located next to the customer's name.
  4. Enter the ID or the name of the relevant parent customer.
  5. Validate: the entity becomes a child of the indicated parent.


From the customer record:

  1. Open the record of the customer to attach (the child).
  2. At the top right, click "Set a parent".
  3. Enter the ID or the name of the relevant parent customer, then validate.


2. Via the enrichment file


Handy for attaching several customers at once on an existing base:

  1. Go to Data > Customers > Enrich my data.
  2. Enter the parent customer's ID as the value in the parent_id column.
  3. Import the file.


3. Via the data import file


If you import your data by file, simply add a parent_id column containing the parent customer's ID for each child to attach.


4. Via the API


The attachment can also be managed by API. Refer to the API documentation for the details of the fields.



Good to know — In all these methods, it is the parent customer's ID (or its name in the interface) that serves as the reference. So make sure the parent exists before starting the attachment.



Where to find your child customers and the MRR breakdown


Consolidation does not make the detail disappear. You can find the information at any time in two places:


On a child customer's record, the relationship is clearly displayed: you see which parent the entity is attached to. Conversely, the record makes it easy to go back up to the parent.


On the parent customer's record, you will find:

  • the group's total MRR (consolidated sum of all attached entities);
  • just below, the breakdown of MRR by child, detailing each entity's contribution to total revenue.


You therefore keep both the group overview and the granularity by subsidiary.



Important rules to know


A child can only have one parent. An entity cannot be attached to several parents simultaneously. If you try to link an already attached entity, you will first have to modify the existing relationship.


Beware of consistency between customer merging and the parent / child relationship. These two mechanisms serve different needs:

  • the parent / child relationship keeps distinct customers and consolidates their revenue at the parent level;
  • customer merging brings two customer records together into one when they actually refer to the same entity.


Concretely, you cannot merge a parent with one of its children: since a child can only have one parent, merging the two records would create an inconsistency in the relationship. Choose the right tool for the case: merging when it is the same customer duplicated, the parent / child relationship when they are distinct customers of the same group.


Also, note that:

  • the parent's attributes take precedence. When an entity is attached to a parent, the attributes (custom dimensions) defined on the child are no longer used: they are overwritten by the parent's. So make sure to fill in the custom dimensions at the parent customer level, since these are the ones that will be used for analysis;
  • the number of customers is counted at the parent level. Once the relationship is created, the group is counted as a single customer (the parent): children are not counted separately in the total number of customers.


FAQ and common errors


Can I attach several children to the same parent?
Yes. A parent can group as many child entities as needed. That is precisely the point of the feature for groups made up of several subsidiaries.


What happens to my KPIs after linking an entity?
Calculations switch to the parent level. MRR, ARR, and the other indicators are consolidated at the group level, but the breakdown by child remains visible on the parent record.


I linked the wrong entity, how do I fix it?
Proceed as for linking: in Data > Customers, hover over the child customer, click "Edit" then the "…" next to its name. Instead of the linking option, you will this time see "Cancel the parent". The attachment is then removed. Since a child can only have one parent, remember to cancel the existing link before attaching the entity to another parent.


Are my customers counted by parent or by child?
At the parent level. After attachment, a group counts as a single customer in your total; child entities are not counted individually.


What happens to my children's attributes (custom dimensions)?
They are not kept: the child's attributes are overwritten by the parent's. Remember to fill in your custom dimensions at the parent level, as these are the ones that will be taken into account in the analysis.


What is the difference with customer merging?
The parent / child relationship keeps distinct customers and consolidates their revenue at the parent level. Customer merging, on the other hand, brings two records together into one when they refer to the same entity. Note: you cannot merge a parent with one of its children.


Is the child level available in the API export?
Once finalized, the API export will expose the same information as what is already available in the interface: you will therefore find both the parent level and the detail of the children.

Updated on: 03/07/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!