Loading
Company hierarchies link parent companies to their subsidiaries, regional entities and sites. In Treepie Flow each company in the tree keeps its own owner, contacts, contracts and invoices, while pipeline, revenue, outstanding balances and open tickets can be rolled up to any level. You can read a subsidiary on its own or see the whole group as one customer.
Because a group bought through five subsidiaries looks like five mid-sized customers. Nobody notices it is the largest relationship you have until somebody adds it up by hand for a board pack.
A hierarchy links company records as parent and child to any depth, so subsidiaries stay separate operating records while the group can be read as one customer.
Each company keeps its own deals, tickets and invoices. Reporting can be run at the node or rolled up through it, and the rollup is a view of the same rows rather than a second set of totals.
Cavendish Group holds four subsidiaries. Individually the largest is a £40,000 account; rolled up the group is £310,000 across eleven deals, with two subsidiaries buying nothing at all.
It is a commercial hierarchy, not a legal one. It records how you sell to and report on a group, and makes no claim about ownership or consolidation for statutory accounts.
Books can consolidate billing or keep it separate per entity, pipeline reports roll up through it, and Desk can escalate on group standing rather than on the size of the entity raising the ticket.
| Flat list of companies | One merged account | Treepie Flow | |
|---|---|---|---|
| Subsidiary owners | Separate, but unrelated | Lost — one owner for all | Each keeps its own |
| Group totals | Added up by hand | Automatic, but nothing else is separate | Rolled up while each entity stays separate |
| Invoicing | Per entity | Wrong entity invoiced | Per legal entity, group total reported |
| Acquisitions & disposals | Nothing to update | Untangle a merged record | Move or unlink; history travels |
| Reporting | By entity only | By group only | Either, from the same data |
As deep as the group. Reporting rolls up through every level.
Yes. Billing entity and hierarchy position are separate decisions in Books.
Yes. Ownership is per company record, which is usually how group accounts actually work.
Open pipeline, weighted pipeline, lifetime revenue, outstanding balance and open tickets. Custom number fields can roll up too.
Yes. Each company keeps its own deals, owner and account team.
Yes. Include a parent reference in the import file, or link companies in bulk afterwards.
Not by default. You can grant a role access to a whole group, or keep entities separate.
No. A company has one parent at a time, so roll-ups never double-count.
Enrichment can suggest a parent company from registry data. Suggestions wait for a person to accept them.
Yes. Any report can group by immediate parent or by the top of the tree.
Merging combines two records for the same entity. A hierarchy links different entities that belong together.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.